proxool-developer — Developer's discussion list

RE: [Proxool-developer] Specifying extra parameters

[<chr...@em...>]

Specifying extra parametersThe properties prefixed with "proxool." will be
used by Proxool while the properties that are not prefixed will be passed on
to the delegate JDBC driver. So just add this line:

jdbc-0.libraries=CHOBJ1R,CHDATAR,CHOBJ1

CHR

  -----Original Message-----
  From: pro...@li...
[mailto:pro...@li...]On Behalf Of
Prigozhin, Roman
  Sent: 8. oktober 2004 23:35
  To: pro...@li...
  Subject: [Proxool-developer] Specifying extra parameters


  HI All,
          I'm using com.ibm.db2.jdbc.app.DB2Driver  ( AS400 native JDBC
driver ). It has parameter called
  "libraries". Here is my question. How  I can specify this parameter in
Proxool configuration ?

  Thanks,
  Roman

  P.S
  Here is my configuration :

  jdbc-0.proxool.alias=CPS
  jdbc-0.proxool.driver-url=jdbc:db2://localhost
  jdbc-0.proxool.driver-class=com.ibm.db2.jdbc.app.DB2Driver
  jdbc-0.user=test
  jdbc-0.password=test
  jdbc-0.proxool.maximum-connection-count=10
  jdbc-0.proxool.house-keeping-test-sql=select CURRENT_DATE
  jdbc-0.proxool.verbose=false
  jdbc-0.proxool.maximum-active-time=60000000
  jdbc-0.proxool.maximum-connection-lifetime=180000000



  here what I need to specify :
  jdbcProperties.put("libraries", "CHOBJ1R,CHDATAR,CHOBJ1");



  ###########################################

  This message has been scanned by F-Secure Anti-Virus for Microsoft
Exchange.
  For more information, connect to http://www.F-Secure.com/

[Proxool-developer] Specifying extra parameters

[Prigozhin, R. <Rom...@ob...>]

HI All,
	I'm using com.ibm.db2.jdbc.app.DB2Driver  ( AS400 native JDBC driver ). =
It has parameter called=20
"libraries". Here is my question. How  I can specify this parameter in =
Proxool configuration ?

Thanks,
Roman
=20
P.S
Here is my configuration :

jdbc-0.proxool.alias=3DCPS
jdbc-0.proxool.driver-url=3Djdbc:db2://localhost
jdbc-0.proxool.driver-class=3Dcom.ibm.db2.jdbc.app.DB2Driver
jdbc-0.user=3Dtest
jdbc-0.password=3Dtest
jdbc-0.proxool.maximum-connection-count=3D10
jdbc-0.proxool.house-keeping-test-sql=3Dselect CURRENT_DATE
jdbc-0.proxool.verbose=3Dfalse
jdbc-0.proxool.maximum-active-time=3D60000000
jdbc-0.proxool.maximum-connection-lifetime=3D180000000


here what I need to specify :
jdbcProperties.put("libraries", "CHOBJ1R,CHDATAR,CHOBJ1");=20



###########################################=0A=
=0A=
This message has been scanned by F-Secure Anti-Virus for Microsoft =
Exchange.=0A=
For more information, connect to http://www.F-Secure.com/

[Proxool-developer] Re: Proxool behavior when max connection reached

[Craig S. <cs...@cr...>]

I am following up on an old thread about causing calling threads to wait for a 
connection rather than getting an Exception.  It looks like this has not been 
done in CVS yet.

Has anyone looked at doing this?  If not, since I need the behavior, I will 
try to work on it.  But, I do not want to repeat work so I thought I would 
ask before I tried to add that feature.

Craig


On Saturday 15 May 2004 03:40 pm, Bertrand Renuart wrote:
> Thanks for your information Craig.
>
> Work has already started on this feature together with some other
> refactoring.
> I don't know yet when it will be released but part of it may be available
> soon in CVS. Keep listening on proxool-dev mailing list - I'll post a
> message when it will start becoming available.
>
> -bertrand
>
>
> -----Original Message-----
> From: pro...@li...
> [mailto:pro...@li...] On Behalf Of Craig
> Servin
> Sent: samedi 15 mai 2004 21:45
> To: pro...@li...
> Subject: [Proxool-developer] Re: Proxool behavior when max connection
> reached
>
>
> Has any work been done on this.  I need a similar behavior and might try to
> implement it, but I do not want to duplicate effort.
>
> It seems that you would not need to more settings you would just need an
> allowed to wait count which if it was not 0 would make your normal limit
> your
> soft limit and then add to it for the hard limit.
>
> It looks like there are only 2 spots in the code that would need to be
> changed, but since the current code tries very hard not to synchronize I am
> not sure of the best way to do this.  It would seem that if you would allow
> for threads to wait you would want to synchronize at that point and then
> notify the threads as a connection is returned.  You could  simply check
> for
>
> that feature being tunred on and only synchronize then, but you would have
> to
> make sure that if you hot change the settings to disable the waiting that
> you
> notify the waiting threads.
>
>
>
> Craig

Re: [Proxool-developer] New to Proxool (encrypted passwords)

[Bill H. <bi...@lo...>]

Hi Sriram,

Sriram Chittathoor wrote:

> I am new to proxool. I am trying to use proxool as the connection pool=20
> mechanism inside hibernate ORM package. My question is whether
>
> there is any way for me to specify the DB =93password=94 in an encrypte=
d=20
> form rather than clear text in the configuration file.
>
This was discussed on the user list a while back.

http://sourceforge.net/mailarchive/message.php?msg_id=3D8942658

One of the improvements in the pipeline is a pluggable connection=20
builder. The default one just builds connections in the normal way, but=20
it would be possible to plug in your own builder to do whatever=20
decryption is necessary. You can only do this at the moment by delving=20
into the code but we hope to make that a configuration setting.

BTW, I changed the subject line of your email from "New to Proxool" to=20
"New to Proxool (encrypted passwords)" to make it easier for other=20
people to search through the archives ;-)

- Bill

[Proxool-developer] New to Proxool

[Sriram C. <sri...@no...>]

Hi:

=20

I am new to proxool.  I am trying to use proxool as the connection pool
mechanism inside hibernate ORM package.  My question is whether=20

there is any way for me to specify  the DB  "password"  in an encrypted
form rather than clear text in the configuration file.=20

=20

Thx

=20

Sriram Chittathoor

[Proxool-developer] Improvement of JAXPConfigurator

[<rom...@as...>]

Hi,
 i have problem with configuration via xml file in servlet environment. My
application uses Proxool in Hibernate which is configurated in the
Springframework.

<property name="hibernateProperties">
			<props>
				<prop
key="hibernate.dialect">net.sf.hibernate.dialect.SQLServerDialect</prop>
				<prop key="hibernate.show_sql">true</prop>
				<prop key="hibernate.proxool.xml">proxool.xml</prop>
				<prop key="hibernate.proxool.pool_alias">issp</prop>
			</props>
</property>

Proxool configuration is stored in proxool.xml, but this doesn't work.
JAXPConfigurator cannot find proxool.xml. When i tried to change path to
./WEB-INF/proxool.xml, /WEB-INF/proxool.xml, /WEB-INF/classes/proxool.xml,
the result was the same.

I think that JAXPConfigurator should test if xml file exists and if not then
try look into the classpath. Little improvement of method configure made
JAXPConfigurator working and helped me. See below the patched method.

public static void configure(String xmlFileName, boolean validate) throws
ProxoolException {
        try {
            if (LOG.isDebugEnabled()) {
                LOG.debug("Configuring from xml file: " + xmlFileName);
            }
            File xmlFile = new File(xmlFileName);

)){                
                configure(new InputSource(new FileReader(xmlFileName)), validate);
            }else{                
                //try look up to classpath
                InputStream s = JAXPConfigurator.class.getClassLoader().getResourceAsStream(xmlFileName);
                if(s == null){                   
                    throw new FileNotFoundException(xmlFileName);
                }
                configure(new InputSource(s), validate);                
            }
        } catch (FileNotFoundException e) {
            throw new ProxoolException(e);
        }
    }


Regards,
 Roman "Dagi" Pichlik
 

Re: [Proxool-developer] Connection timeout

[Bill H. <bi...@lo...>]

Hi Roman,

Prigozhin, Roman wrote:

> 21 Sep 2004 21:25:38,148 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} 
> - Recognised proxool property: proxool.maximum-active-time=6000
>
Sorry, the doc isn't very clear on this. That value is in milliseconds.

The web site now says "(in milliseconds)":

  http://proxool.sourceforge.net/properties.html#maximum-active-time

- Bill

[Proxool-developer] Connection timeout

[Prigozhin, R. <Rom...@ob...>]

  I'm reusing connection within 1 class 3 times. Stored procedures are =
slow and sometimes take about 5 - 10 min each to get data. I'm getting =
this message from the pool :

21 Sep 2004 21:26:46,053 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
000001 (00/00/00) - #0001 removed because it has been active for too =
long.
21 Sep 2004 21:26:46,059 [WARN ] org.logicalcobwebs.proxool.CPS {?:?} - =
#0001 was active for 10330 milliseconds and has been removed =
automaticaly. The Thread responsible was named 'Thread-4'.
21 Sep 2004 21:26:46,071 [DEBUG] =
org.logicalcobwebs.proxool.SmartConnection {?:?} - 000001 (00/00/00) - =
#0001 removed because it has been active for too long.
21 Sep 2004 21:26:46,074 [FATAL] ocs.app.smartconn.Package {?:?} - =
TransferPackages(BatchId =3D 47621) - Failed
com.ibm.db2.jdbc.app.DB2JDBCException: Internal driver error.
      java/lang/Throwable.<init>(Ljava/lang/String;)V+4 =
(Throwable.java:85)=20
      java/lang/Exception.<init>(Ljava/lang/String;)V+1 =
(Exception.java:33)=20
      =
java/sql/SQLException.<init>(Ljava/lang/String;Ljava/lang/String;I)V+1 =
(SQLException.java:34)=20
      =
com/ibm/db2/jdbc/app/DB2Exception.<init>(Ljava/lang/String;Ljava/lang/Str=
ing;I)V+1 (DB2Exception.java:49)=20
      =
com/ibm/db2/jdbc/app/DB2JDBCException.<init>(Ljava/lang/String;)V+1 =
(DB2JDBCException.java:121)=20
      =
com/ibm/db2/jdbc/app/DB2CallableStatementRuntimeImpl.getRealType(II)I+43 =
(DB2CallableStatementRuntimeImpl.java:319)=20
      com/ibm/db2/jdbc/app/DB2CallableStatement.getInt(I)I+74 =
(DB2CallableStatement.java:845)=20
      =
org/logicalcobwebs/proxool/ProxyStatement.invoke(Ljava/lang/Object;Ljava/=
lang/reflect/Method;[Ljava/lang/Object;)Ljava/lang/Object;+89 =
(ProxyStatement.java:68)=20
      =
org/logicalcobwebs/cglib/proxy/Proxy$ProxyImpl$$EnhancerByCGLIB$$eb57bddb=
.getInt(I)I+47 (<generated>:0)=20
      ocs/app/smartconn/Package.TransferPackages(I)Z+105 =
(Package.java:479)=20
      ocs/app/smartconn/Package.StartTransfer(I)Z+109 (Package.java:66)=20
      ocs/app/smartconn/MainThread.run()V+333 (MainThread.java:105)=20
      ocs/util/lang/WorkerThread.run()V+14 (ThreadPool.java:152)=20
21 Sep 2004 21:26:46,106 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Closing statement 6f8bf22b automatically
21 Sep 2004 21:26:46,110 [WARN ] org.logicalcobwebs.proxool.CPS {?:?} - =
Unable to set status of connection 1 from ACTIVEto AVAILABLE. It remains =
NULL
21 Sep 2004 21:26:46,113 [WARN ] =
org.logicalcobwebs.proxool.SmartConnection {?:?} - Unable to set status =
of connection 1 from ACTIVEto AVAILABLE. It remains NULL

I've tried to setup bigger timeout but it doesn't look like it works , =
here is the configuration :

21 Sep 2004 21:25:38,143 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Recognised proxool property: =
proxool.driver=3Dcom.ibm.db2.jdbc.app.DB2Driver
21 Sep 2004 21:25:38,146 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Recognised proxool property: proxool.url=3Djdbc:db2://localhost
21 Sep 2004 21:25:38,148 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Recognised proxool property: proxool.maximum-active-time=3D6000
21 Sep 2004 21:25:38,151 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Delegating property to driver: user=3Droman
21 Sep 2004 21:25:38,153 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Delegating property to driver: password=3D********
21 Sep 2004 21:25:38,155 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Recognised proxool property: proxool.maximum-connection-count=3D10
21 Sep 2004 21:25:38,157 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Recognised proxool property: proxool.house-keeping-test-sql=3Dselect =
CURRENT_DATE
21 Sep 2004 21:25:38,256 [DEBUG] org.logicalcobwebs.proxool.CPS {?:?} - =
Ignoring attempt to map reset method getHoldability (probably because it =
isn't implemented in this JDK)


Any thoughts ?=20

Thanks,
Roman

###########################################=0A=
=0A=
This message has been scanned by F-Secure Anti-Virus for Microsoft =
Exchange.=0A=
For more information, connect to http://www.F-Secure.com/

Re: [Proxool-developer] #1 registered a statement as closed which wasn't known to be open.

[Bill H. <bi...@lo...>]

Hi Roman,

Prigozhin, Roman wrote:

> I'm getting message from proxool :  000001 (01/01/00) - #1 registered 
> a statement as closed which wasn't known to be open.
>
> I suspect that it happens when I'm closing PreparedStatement ( JDBC ) 
> in finally block even if it was never open , I just check if it's not 
> null and execute .close() statement just to be on the safe side.
>
> Question :
>         Is it ok ? or proxool will leak memory / connections etc ?
>
Yes, it's okay. It's exactly as you say: you're closing a statement 
twice. There's nothing wrong with that (according to the JDBC spec.).

>         How to avoid this message ?
>
Hmm, that would be tricky. I think maybe we should make Proxool be a 
little quieter in that respect. It's a bit over cautious. Now that bit 
of code is pretty mature we can be sure what is going on there. I'll see 
what I can do.

- Bill

[Proxool-developer] #1 registered a statement as closed which wasn't known to be open.

[Prigozhin, R. <Rom...@ob...>]

Hi All,
	I'm new to the Proxool, I've been using it only for a month.
I'm getting message from proxool :  000001 (01/01/00) - #1 registered a =
statement as closed which wasn't known to be open.
I suspect that it happens when I'm closing PreparedStatement ( JDBC ) in =
finally block even if it was never open , I just check if it's not null =
and execute .close() statement just to be on the safe side.

Question :
	Is it ok ? or proxool will leak memory / connections etc ?
	How to avoid this message ?


Thanks,
Roman
###########################################=0A=
=0A=
This message has been scanned by F-Secure Anti-Virus for Microsoft =
Exchange.=0A=
For more information, connect to http://www.F-Secure.com/

[Proxool-developer] Re: "get connection from pool on create statement" AND "return connection to pool when statement is closed"

[Mark <ma...@te...>]

thank you guys for your replies.  i have decided that we will just get a 
connection from the pool every page and after each page, close the 
connection to return it to the pool.  creating a shortcut will only 
complicate things in the future.  :-D

regards,
mark

>    Connection c = getConnection(); // Either using a wrapper or JDBC 
> direct
>    Statement s = c.prepareStatement(sql);
>    s.execute();
>    s.close();
>    c.close();
>
> (You would do smarter exception handling than that of course).
>
> Cheers,
> Bill
>
>
>
> --__--__--
>
> _______________________________________________
> Proxool-developer mailing list
> Pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proxool-developer
>
>
> End of Proxool-developer Digest 

Re: [Proxool-developer] "get connection from pool on create statement" AND "return connection to pool when statement is closed"

[Bill H. <bi...@lo...>]

Hi Mark,

> we designed our JSP application 4 years ago such that it uses 1 
> connection object per user session.  now, we are having a problem 
> because the JSP application is hitting the maximum connections our 
> database can support.  this would not be a problem if each JSP gets a 
> connection from the pool and closes it afterwards.  we now have more 
> than 500 JSP pages.

I think you're right to want to change from that approach ;)

> now, im thinking that it would be nice if the connection is returned 
> to the pool everytime a statement is closed.  and a connection is 
> retrieved from the pool if a statement is created.  do you think this 
> is a worthwhile addition to proxool ?  or is this already supported?  
> or are there alternatives?

That would mean some code changes. And it would be deviating from JDBC 
standards, wouldn't it? Closing a statement should not close the 
connection. Can I ask why you want to do that?

Why not just write a wrapper in your own application. You ask it for a 
statement and it goes off and gets a connection for you and creates the 
statement on your behalf. Then you hand the statement back to the 
wrapper and it closes the statement and then the conneciton.

But if I was looking at some code that said:

    Statement s = MyWrapper.getStatement(sql);
    s.execute();
    s.close();

I would wonder about what connection it was using.

In order for me to understand your problem, please explain what is 
inappropriate with:

    Connection c = getConnection(); // Either using a wrapper or JDBC direct
    Statement s = c.prepareStatement(sql);
    s.execute();
    s.close();
    c.close();

(You would do smarter exception handling than that of course).

Cheers,
Bill

[Proxool-developer] "get connection from pool on create statement" AND "return connection to pool when statement is closed"

[Mark <ma...@te...>]

hi proxool developers,

i am interested in using proxool as a solution to easily supporting =
database connection pooling without changes in our JSP application.  i =
need advice from you guys on a requirement because it seems that there =
is no way of doing it given the current proxool version after reading =
through the documents and mailing list archive.

we designed our JSP application 4 years ago such that it uses 1 =
connection object per user session.  now, we are having a problem =
because the JSP application is hitting the maximum connections our =
database can support.  this would not be a problem if each JSP gets a =
connection from the pool and closes it afterwards.  we now have more =
than 500 JSP pages.

now, im thinking that it would be nice if the connection is returned to =
the pool everytime a statement is closed.  and a connection is retrieved =
from the pool if a statement is created.  do you think this is a =
worthwhile addition to proxool ?  or is this already supported?  or are =
there alternatives?

i don't mind contributing code to proxool to achieve this.  i just want =
to know alternative solutions for our problem.  ill also appreciate if =
you can point me to another project offering this kind of feature.

thanks in advance,

mark

[Proxool-developer] Debugging with Websphere (WSAD 5.2)

[Kiran T <mah...@ho...>]

Hello Bill,
I recently tried using Proxool with WebSphere ( WSAD 5.2). The  application 
runs fine in the regular mode but when I try to run it in the debug mode, 
websphere crashes.
In the error log below, I can see some Proxool related errors but I am not 
sure whether Proxool is causing Websphere to crash or vice versa. Looking at 
the trace below, would you be able to provide any information?

Thanks
Kiran

9/7/04 13:14:54:845 CDT] 64b764b7 SystemErr     R 0 
[Servlet.Engine.Transports : 0] INFO proxool.ProxoolFacade  - Proxool 0.8.2 
(05-Nov-2003 10:48)
Unhandled exception
Type=GPF vmState=0xffffffff
Target=20030915 (Windows XP 5.1 build 2600 Service Pack 1 x86)
ExceptionCode=0xc0000005 ExceptionAddress=0x10012982 ContextFlags=0x0001003f
Handler1=0x111016c0 Handler2=0x10019730
Module=C:\Program Files\IBM\WebSphere Studio\Application 
Developer\v5.1.2\runtimes\base_v51\java\jre\bin\j9vm21.dll
Module_base_address=0x10000000
Offset_in_DLL=0x00012982
EDI=0x00000000 ESI=0x0008aa28 EAX=0x10005cd8
EBX=0x03d000b4 ECX=0x07b2ac24 EDX=0x00119678
EBP=0x0767d500 ESP=0x09d6f9d8 EIP=0x10012982

Generating crash dump: C:\Documents and Settings\user345\j9.dmp

Thread: Prototyper (priority 5) (daemon) (LOCATION OF ERROR)
NATV 
sun/reflect/NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;
0072 
sun/reflect/NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;
002d 
sun/reflect/DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object; 
  (@08a73f79)
0166 
java/lang/reflect/Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object; 
  (@08a73e32)
00db 
org/logicalcobwebs/proxool/ConnectionResetter.initialise(Ljava/sql/Connection;)V
0005 
org/logicalcobwebs/proxool/ConnectionPool.initialiseConnectionResetter(Ljava/sql/Connection;)V
005f 
org/logicalcobwebs/proxool/AbstractProxyConnection.<init>(Ljava/sql/Connection;JLjava/lang/String;Lorg/logicalcobwebs/proxool/ConnectionPool;I)V
0009 
org/logicalcobwebs/proxool/ProxyConnection.<init>(Ljava/sql/Connection;JLjava/lang/String;Lorg/logicalcobwebs/proxool/ConnectionPool;I)V
0032 
org/logicalcobwebs/proxool/ProxyFactory.buildProxyConnection(JLorg/logicalcobwebs/proxool/ConnectionPool;I)Lorg/logicalcobwebs/proxool/ProxyConnection;
008a 
org/logicalcobwebs/proxool/Prototyper.buildConnection(ILjava/lang/String;)Lorg/logicalcobwebs/proxool/ProxyConnectionIF;
0097 org/logicalcobwebs/proxool/Prototyper.sweep()Z
003b org/logicalcobwebs/proxool/PrototyperThread.run()V

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

[Proxool-developer] Proxool - HB987 - proxool allows only one instance of itself

[Bertrand R. <ber...@mo...>]

In issue HB-987
(http://opensource.atlassian.com/projects/hibernate/browse/HB-987), Gavin
reports:
 
(3) Since proxool only allows one instance of itself with a particular
name, hbm2ddl.auto does not really work

The proxool dev team is aware of this issue and is currently working on
it. 
We would be glad if someone could explain us a bit more how this affects
Hibernate and its hbm2ddl utility. Just to make sure we address the same
problem and will provide the correct solution ;)
 
Thx
 
-bertrand

Re: [Proxool-developer] On the number of connections in a pool during its lifetime

[Jean-Henry B. <ber...@ne...>]

I missed the maximum conn. lifetime, which I set, by default,
to 14400000 (exactly 4 hours). The problem is that I see the
connection cleaning after the lifetime expires not every 4 hours,
but every day.
I will try to set this to lower values to see what happens.

Thanks,
Jean


bi...@lo... wrote:

>Jean,
>
>On Tue, 6 Jul 2004, Jean-Henry Berevoescu wrote:
>
>  
>
>>These are the parameters I use (connecting to a PostgreSQL database):
>>
>>proxool.maximum-connection-count 1000
>>proxool.minimum-connection-count 30
>>proxool.prototype-count 1
>>proxool.house-keeping-sleep-time 60000
>>proxool.maximum-active-time 4000
>>proxool.house-keeping-test-sql "select 0;"
>>    
>>
>
>Nothing wrong with that. I see you don't set the
>maximum-connection-lifetime so it will be the 4 hour default.
>
>Do you have any summarised log output? I'm expecting to see events showing
>that a connection had been killed because it was over 4 hours old. You
>could always set maximum-connection-count to something like 60000 (1
>minute) to see this happening more quickly.
>
>Does the connection count ever go down?
>
>- Bill
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by Black Hat Briefings & Training.
>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>digital self defense, top technical experts, no vendor pitches, 
>unmatched networking opportunities. Visit www.blackhat.com
>_______________________________________________
>Proxool-developer mailing list
>Pro...@li...
>https://lists.sourceforge.net/lists/listinfo/proxool-developer
>  
>

Re: [Proxool-developer] On the number of connections in a pool during its lifetime

[Bill H. <bi...@lo...>]

Jean,

On Tue, 6 Jul 2004, Jean-Henry Berevoescu wrote:

> These are the parameters I use (connecting to a PostgreSQL database):
>
> proxool.maximum-connection-count 1000
> proxool.minimum-connection-count 30
> proxool.prototype-count 1
> proxool.house-keeping-sleep-time 60000
> proxool.maximum-active-time 4000
> proxool.house-keeping-test-sql "select 0;"

Nothing wrong with that. I see you don't set the
maximum-connection-lifetime so it will be the 4 hour default.

Do you have any summarised log output? I'm expecting to see events showing
that a connection had been killed because it was over 4 hours old. You
could always set maximum-connection-count to something like 60000 (1
minute) to see this happening more quickly.

Does the connection count ever go down?

- Bill

Re: [Proxool-developer] On the number of connections in a pool during its lifetime

[Jean-Henry B. <ber...@ne...>]

Hi,
These are the parameters I use (connecting to a PostgreSQL database):

proxool.maximum-connection-count 1000
proxool.minimum-connection-count 30
proxool.prototype-count 1
proxool.house-keeping-sleep-time 60000
proxool.maximum-active-time 4000
proxool.house-keeping-test-sql "select 0;"

Jean


bi...@lo... wrote:

>Jean,
>
>On Fri, 2 Jul 2004, Jean-Henry Berevoescu wrote:
>
>  
>
>>I somehow lived with the impression that once a pool is defined and
>>started, is will go on and create connections on demand (limited by the
>>maximum number of connections and guided by the values of
>>prototype-count and maximum-new-connections), but if the activity in the
>>system gets low, it will go back to the minimum number of connections
>>(of course, after the lifetime of each connection goes of).
>>    
>>
>
>That sounds right.
>
>  
>
>>In my latest long run tests on my system I noticed that this is not the
>>case and rechecking the docs I realize that there's actually no direct
>>reference to this type of behavior. Then, was my assumption wrong? If
>>not, then I must miss something in the configuration somehow. If yes,
>>what would be a workaround? To programatically shut down the pools and
>>restart them from time to time?
>>    
>>
>
>Can you send your configuration? You're absolutely right, the connection
>count should drop down to the minimum level after a period of inactivity.
>The maximum-connection-lifetime property (in milliseconds) should be
>killing off connections. The default is 4 hours, so after 4 hours all of
>your initial connections should be killed off. Then Proxool will make new
>ones (guided, like you say, by minimum-connection-count and
>prototype-count).
>
>- Bill
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by Black Hat Briefings & Training.
>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>digital self defense, top technical experts, no vendor pitches, 
>unmatched networking opportunities. Visit www.blackhat.com
>_______________________________________________
>Proxool-developer mailing list
>Pro...@li...
>https://lists.sourceforge.net/lists/listinfo/proxool-developer
>  
>

Re: [Proxool-developer] On the number of connections in a pool during its lifetime

[Bill H. <bi...@lo...>]

Jean,

On Fri, 2 Jul 2004, Jean-Henry Berevoescu wrote:

> I somehow lived with the impression that once a pool is defined and
> started, is will go on and create connections on demand (limited by the
> maximum number of connections and guided by the values of
> prototype-count and maximum-new-connections), but if the activity in the
> system gets low, it will go back to the minimum number of connections
> (of course, after the lifetime of each connection goes of).

That sounds right.

> In my latest long run tests on my system I noticed that this is not the
> case and rechecking the docs I realize that there's actually no direct
> reference to this type of behavior. Then, was my assumption wrong? If
> not, then I must miss something in the configuration somehow. If yes,
> what would be a workaround? To programatically shut down the pools and
> restart them from time to time?

Can you send your configuration? You're absolutely right, the connection
count should drop down to the minimum level after a period of inactivity.
The maximum-connection-lifetime property (in milliseconds) should be
killing off connections. The default is 4 hours, so after 4 hours all of
your initial connections should be killed off. Then Proxool will make new
ones (guided, like you say, by minimum-connection-count and
prototype-count).

- Bill

[Proxool-developer] On the number of connections in a pool during its lifetime

[Jean-Henry B. <ber...@ne...>]

Hi,
I somehow lived with the impression that once a pool is defined and 
started, is will go
on and create connections on demand (limited by the maximum number of 
connections
and guided by the values of prototype-count and 
maximum-new-connections), but if the
activity in the system gets low, it will go back to the minimum number 
of connections
(of course, after the lifetime of each connection goes of). In my latest 
long run tests
on my system I noticed that this is not the case and rechecking the docs 
I realize that
there's actually no direct reference to this type of behavior.
Then, was my assumption wrong? If not, then I must miss something in the 
configuration
somehow. If yes, what would be a workaround? To programatically shut 
down the
pools and restart them from time to time?

Jean

Re: [Proxool-developer] Externalize JdbcDriver instanciation and/or give the JdbcDriverPath

[Bill H. <bi...@lo...>]

Hi Arnaud,

On Wed, 2004-06-23 at 10:20, Lefour Arnaud wrote:

> So, if  we want to use a JdbcDriver jarFile that is not in the
> ClassPath, it would be a good idea to add new methods like :
> 
> 1/ adding the driver instance in parameter :
> "registerConnectionPool(String url, Driver jdbcDriver, Properties
> info)".
> or
> 2/ adding the path of the JdbcDriver jarFile, letting proxool make the
> ClassLoader
> "registerConnectionPool(String url, String jdbcDriverPath, Properties
> info)".

I'd like to avoid Proxool getting involved in ClassLoader issues. And,
actually, I don't think it's necessary. The only thing that Proxool does
with the driver is load it (using Class.forName()). 

If the client (you) loads it before you register the pool does that make
the problem go away?

We could change Proxool so that if there are problems loading the driver
(in Class.forName()) then it logged it as a warning but carried on
anyway. 

> If this is something that can be rolled out to 1.0, is there a
> temporary solution to tackle this issue?

Temporary workarounds:

1. Try loading the class yourself before you register the pool.

2. Patch the code so that an exception thrown by the Class.forName()
call is logged but we continue registration.

- Bill

[Proxool-developer] Externalize JdbcDriver instanciation and/or give the JdbcDriverPath

[Lefour A. <al...@ax...>]

Hello all,
Externalize JdbcDriver instanciation and/or give the JdbcDriverPath
First, ProxoolFacade provides the following method :
"registerConnectionPool(String url, Properties info)".
 It is well worth mentionning that the JdbcDriver url is a subString of =
the url string, and proxool, more precisely the ConnectionPool Class, =
instanciates the JdbcDriver searching the jarFile in the ClassPath.

So, if  we want to use a JdbcDriver jarFile that is not in the =
ClassPath, it would be a good idea to add new methods like :

1/ adding the driver instance in parameter :
"registerConnectionPool(String url, Driver jdbcDriver, Properties =
info)".
or
2/ adding the path of the JdbcDriver jarFile, letting proxool make the =
ClassLoader
"registerConnectionPool(String url, String jdbcDriverPath, Properties =
info)".

If this is something that can be rolled out to 1.0, is there a temporary =
solution to tackle this issue?
Thanks all in advance. Arnaud L


> Arnaud LEFOUR
> R&D B.A.M.
>=20
> AXWAY.=20
> a Sopra Group company
Tel: +33 (0) 4 50 10 35 70
> Email : al...@ax...
>=20

[Proxool-developer] Fw: [ANNOUNCEMENT] Commons DBCP 1.2 released

[Christian N. <chr...@em...>]

----- Original Message -----
From: Dirk Verbeeck <di...@ap...>
Date: Tue, 08 Jun 2004 22:15:05 +0200
To: ann...@ja...,Jakarta Commons Developers List <com...@ja...>,Jakarta Commons Users List <com...@ja...>
Subject: [ANNOUNCEMENT] Commons DBCP 1.2 released

> The Jakarta Commons team is pleased to announce the release of version 
> 1.2 of the Jakarta Commons DBCP component.
> 
> Commons-DBCP provides database connection pooling services. Together 
> with Commons-Pool it is the default JNDI datasource provider for Tomcat.
> 
> There were some new features were added since the 1.1 release on 20 
> October 2003.
> 
>      * Performance optimizations for the PoolableConnectionFactory of 
> 
>        BasicDataSource.
>      * Add BasicDataSourceFactory.createDataSource(Properties
>        properties) for creating a BasicDataSource.
>      * Add initialSize parameter to do pre-loading of the connection.
>      * Refactoring of the DelegatingStatement classes.
>      * Make some properties dynamic (changeble at runtime), this will
>        be completed in next release.
>      * Improvements to the prepared statement pooling.
>      * Driver specific changes/optimizations for: Oracle, Informix,
>        DaffodilDB.
>      * Several fixes for PerUserPoolDataSource
>      * PoolingDriver uses now a PoolGuardConnectionWrapper by default.
>        If access to the underlying connection is needed, you have to
>        enable it:
>        PoolingDriver.setAccessToUnderlyingConnectionAllowed(true)
>      * This release contains bug fixes to all known issues.
>        (see release notes for more info)
> 
> The latest binary release is always available on the Jakarta Binary 
> Downloads page, its source is available from Jakarta Source Downloads 
> page.
> 
> -- Dirk Verbeeck
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ann...@ja...
> For additional commands, e-mail: ann...@ja...
> 

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

RE: [Proxool-developer] Analyzing SQL Queries

[Bertrand R. <bre...@us...>]

There is an easier solution - just make use of the P6Spy JDBC driver... =
See
http://www.p6spy.com/

Just configure Proxool to use it instead of your actual database driver.

-bertrand


-----Original Message-----
From: pro...@li...
[mailto:pro...@li...] On Behalf Of =
Kiran T
Sent: mardi 1 juin 2004 22:28
To: pro...@li...
Subject: [Proxool-developer] Analyzing SQL Queries


Hello all,

In order to improve the efficiency of the website, I need to analyze all =
the

SQL Queries and find the top 10 slowest( in terms of time it takes to=20
complete execution)SQL queries. Is there a way to acheive this using =
Proxool

?

I remeber this being discussed few months ago.

One solution would be split the existing OnExecute() method into=20
OnExecuteStart() and OnExecuteEnd(). If changing an existing public =
method=20
in the Proxool API is a concern, can a new method be added and let the=20
existing OnExecute() do the function of either start or end event?( I am =

assuming OnExecute() currently gets executed at the beginning of the =
query=20
execution.)

If this is something that can be rolled out to 1.0, is there a temporary =

solution to tackle this issue?

Thanks all in advance.

Kiran T

_________________________________________________________________
Express yourself with the new version of MSN Messenger! Download today - =

it's FREE! =
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and =
evaluate
today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Proxool-developer mailing list Pro...@li...
https://lists.sourceforge.net/lists/listinfo/proxool-developer

Re: [Proxool-developer] Analyzing SQL Queries

[Bill H. <bi...@lo...>]

Kiran,

On Tue, 2004-06-01 at 21:27, Kiran T wrote:

> One solution would be split the existing OnExecute() method into 
> OnExecuteStart() and OnExecuteEnd(). If changing an existing public method 
> in the Proxool API is a concern, can a new method be added and let the 
> existing OnExecute() do the function of either start or end event?

Changing the public API is a concern. And adding additional methods is
not trivial since it would break all implementing classes that,
presumably, wouldn't implement that method.

However, your suggestion is a good one. Especially since in some trouble
shooting scenarios an afterExecute() might happen a long time after a
beforeExecute().

> If this is something that can be rolled out to 1.0, is there a temporary 
> solution to tackle this issue?

The onExecute already contains the execution time. 

http://proxool.sourceforge.net/api/org/logicalcobwebs/proxool/ConnectionListenerIF.html#onExecute(java.lang.String,%20long)

public void onExecute(java.lang.String command, long elapsedTime)

Happens after every successful execute. Note that the command is not
fully implemented at this stage. At some point it might represent the
SQL that is sent to the database (or the procedure call that was used). 
        
Parameters:
  command - what command was being executed
  elapsedTime - how long the call took (in milliseconds)

Would that help?

- Bill