proxool-developer — Developer's discussion list

Re: [Proxool-developer] Closed Connection and Rollback of a transaction

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

On 01/24/2007 06:51 PM, Mahendra KC wrote:
> I am facing a tricky situation when I am inside a jdbc transaction 
> and the connection is closed by Proxool because of timeout. As 
> expected, My method throws an exception and in my catch I normally do 
> rollback(). Because the connection is closed, as expected, now my 
> rollback is throwing a null pointer exception.
>  
> My understanding is that there is no standard specified in JDBC  
> API to determine the transactional behavior when the underlying 
> connection is closed before commit/rollback. Probably it is more of a 
> database/driver vendor specific implementation to decide rollback or 
> commit in the situation where connection is closed.
> I am using Oracle 10g, oracle thin driver ( with Hibernate as ORM 
> layer) and my default in the above scenario happens to be "commit" 
> instead of "rollback".
>  
> Is there a way in Proxool to intercept connection when it is about to 
> be automatically closed so that I can rollback before that? The 
> closest I can find is the onDeath() method from the ConnectionListener 
> but that method will be always called irrespective of a 
> natural/unnatural death.
> I am hoping there must be a way to get around this common problem.

I don't think this is possible, but it should be easy enough to add a 
new hook for a listener. It seems like a wise thing to do. Are you 
willing to do some testing of the code in CVS if I make some changes for 
you?

-
Bill

[Proxool-developer] Closed Connection and Rollback of a transaction

[Mahendra KC <mah...@ho...>]

Hello all,=20
I am facing a tricky situation when I am inside a jdbc transaction and the =
connection is closed by Proxool because of timeout. As expected, My method =
throws an exception and in my catch I normally do rollback(). Because the c=
onnection is closed, as expected, now my rollback is throwing a null pointe=
r exception.
=20
My understanding is that there is no standard specified in JDBC  API to det=
ermine the transactional behavior when the underlying connection is closed =
before commit/rollback. Probably it is more of a database/driver vendor spe=
cific implementation to decide rollback or commit in the situation where co=
nnection is closed.
I am using Oracle 10g, oracle thin driver ( with Hibernate as ORM layer) an=
d my default in the above scenario happens to be "commit" instead of "rollb=
ack".
=20
Is there a way in Proxool to intercept connection when it is about to be au=
tomatically closed so that I can rollback before that? The closest I can fi=
nd is the onDeath() method from the ConnectionListener but that method will=
 be always called irrespective of a natural/unnatural death.=20
I am hoping there must be a way to get around this common problem.
=20
Thanks
MKC
=20
=20
_________________________________________________________________
Try amazing new 3D maps
http://maps.live.com/?wip=3D51=

Re: [Proxool-developer] Possible bug with CallableStatment

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

On 01/10/2007 10:57 PM, Neil Miller wrote:
> I'm not sure if the bug tracker on Sourceforge is used much, so I 
> thought I'd post this here. We're getting a warnings in our logs when 
> using CallableStatements (I added a stack trace for additional info):
>
> Jan 10, 2007 3:17:59 PM org.logicalcobwebs.proxool.ProxyConnection 
> registerClosedStatement
> WARNING: 001210 (01/02/00) - #16 registered a statement as closed 
> which wasn't known to be open.
That warning message could probably be improved because it could also 
indicate a statement that has been closed twice. Are you sure you don't 
close the statement inside the main try block as well as the finally block?

-
Bill

[Proxool-developer] Possible bug with CallableStatment

[Neil M. <nm...@pr...>]

I'm not sure if the bug tracker on Sourceforge is used much, so I  
thought I'd post this here. We're getting a warnings in our logs when  
using CallableStatements (I added a stack trace for additional info):

Jan 10, 2007 3:17:59 PM org.logicalcobwebs.proxool.ProxyConnection  
registerClosedStatement
WARNING: 001210 (01/02/00) - #16 registered a statement as closed  
which wasn't known to be open.
java.lang.Exception: Trace
         at  
org.logicalcobwebs.proxool.ProxyConnection.registerClosedStatement 
(ProxyConnection.java:181)
         at org.logicalcobwebs.proxool.AbstractProxyStatement.close 
(AbstractProxyStatement.java:116)
         at org.logicalcobwebs.proxool.ProxyStatement.invoke 
(ProxyStatement.java:93)
         at org.logicalcobwebs.proxool.ProxyStatement.intercept 
(ProxyStatement.java:57)
         at oracle.jdbc.internal.OraclePreparedStatement$ 
$EnhancerByCGLIB$$3f1a29db.close(<generated>)
         [local code]

Our code looks like this (the connection has already be gotten from  
Proxool and is passed to this method):

     public void execute(Connection con, String callSQL, Parameter[]  
params)
         throws SQLException
     {
         CallableStatement call = null;
	        try {
             call = con.prepareCall(callSQL);

             [... add parameters to the statement ...]

             call.execute();

             [... read returned parameters ...]
         }
         finally {
             if (call != null) {
                 call.close(); <-- exception is thrown here.
             }
         }
     }

We're using Oracle 10g and the lastest JDBC drivers from oracle.  
Can't see why this should cause a warning.

-n

Re: [Proxool-developer] Long time of getting connections

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

Hi Yaroshinsky,

On 11/14/2006 11:23 AM, Yaroshinsky Valentin wrote:

> /Good day,/
> // 
> /I'm using Proxool and I 've investigated the problem of long time of 
> getting connection/
> // 
> /Code:/
> *                long s1=System.currentTimeMillis();
>                 connection = DriverManager.getConnection("oracle_logging");
>                 long s2=System.currentTimeMillis();
>                 log.info("Time of getting connection:"+(s2-s1));*

What version of Proxool are you using? Have you tried switching 
statistics off? Omit it from your config to see if that helps.

Have you got any log evidence that Proxool is in fact being used for 
serving connections? You're using "oracle_logging" as your connection 
URL and I'd expect you to use "proxool.oracle_logging".

If you're using Proxool 0.8.3, switch to 0.9.0RC2 and see how you get on.

-
Bill

[Proxool-developer] Long time of getting connections

[Yaroshinsky V. <Val...@in...>]

Good day,
=20
I'm using Proxool and I 've investigated the problem of long time of =
getting connection
=20
Code:
                long s1=3DSystem.currentTimeMillis();
                connection =3D =
DriverManager.getConnection("oracle_logging");
                long s2=3DSystem.currentTimeMillis();
                log.info("Time of getting connection:"+(s2-s1));
=20
=20
In properties I configured 25 of max connections and 12 of min =
connections:
=20
<proxool> =20
  <alias>oracle_logging</alias>  =20
  =
<driver-url>jdbc:oracle:thin:@//172.18.64.30:1521/SIEBEL78</driver-url>  =

  <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> =20
  <driver-properties>    =20
  <property name=3D"user" value=3D"IVRUS"/>   =20
  <property name=3D"password" value=3D"IVRUS"/>   =20
  </driver-properties>   =20
  <prototype-count>12</prototype-count>
  <minimum-connection-count>12</minimum-connection-count>
  <maximum-connection-count>25</maximum-connection-count>   =20
   <statistics>1m,15m,1d</statistics> =20
   <statistics-log-level>INFO</statistics-log-level>
  <house-keeping-test-sql>select 1</house-keeping-test-sql> =20
<house-keeping-sleep-time>300</house-keeping-sleep-time>
  </proxool>
=20
=20
In logs I have sometimes 19 seconds of executing method getConnection.
=20
Main Question IS : How I can avoid this trouble???
=20
log file:
=20
14 =CC=C9=D3=D4 2006 12:51:00,401 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:79
14 =CC=C9=D3=D4 2006 12:51:01,323 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:51:02,338 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:51:02,338 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:51:09,791 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:51:10,807 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:51:16,698 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:51:18,214 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:16
14 =CC=C9=D3=D4 2006 12:51:55,324 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:02,465 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:03,746 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:05,012 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:32
14 =CC=C9=D3=D4 2006 12:52:08,496 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:30,762 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:15625
14 =CC=C9=D3=D4 2006 12:52:30,809 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:14672
14 =CC=C9=D3=D4 2006 12:52:30,809 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:13657
14 =CC=C9=D3=D4 2006 12:52:30,840 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:13688
14 =CC=C9=D3=D4 2006 12:52:30,840 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:7281
14 =CC=C9=D3=D4 2006 12:52:30,840 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:6250
14 =CC=C9=D3=D4 2006 12:52:30,872 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:5688
14 =CC=C9=D3=D4 2006 12:52:30,872 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:4672
14 =CC=C9=D3=D4 2006 12:52:30,872 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:4563
14 =CC=C9=D3=D4 2006 12:52:30,872 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:3547
14 =CC=C9=D3=D4 2006 12:52:30,887 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:3453
14 =CC=C9=D3=D4 2006 12:52:30,887 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:3453
14 =CC=C9=D3=D4 2006 12:52:30,887 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:1125
14 =CC=C9=D3=D4 2006 12:52:40,872 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:41,887 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:45,325 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:48,325 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:49,028 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:49,513 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:50,622 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:31
14 =CC=C9=D3=D4 2006 12:52:50,622 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:31
14 =CC=C9=D3=D4 2006 12:52:50,653 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:47
14 =CC=C9=D3=D4 2006 12:52:52,247 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:52,981 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:56,607 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:52:59,388 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:53:00,607 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 12:53:21,857 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:19266
14 =CC=C9=D3=D4 2006 12:53:21,904 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:17469
14 =CC=C9=D3=D4 2006 12:53:21,904 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:17469
14 =CC=C9=D3=D4 2006 12:53:21,935 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:16016
14 =CC=C9=D3=D4 2006 12:53:21,935 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:14484
14 =CC=C9=D3=D4 2006 13:02:41,074 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:359
14 =CC=C9=D3=D4 2006 13:02:43,871 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:2141
14 =CC=C9=D3=D4 2006 13:02:43,871 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:1125
14 =CC=C9=D3=D4 2006 13:02:43,871 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:1125
14 =CC=C9=D3=D4 2006 13:09:01,552 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 13:09:02,552 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 13:09:03,583 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 13:09:29,131 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:18891
14 =CC=C9=D3=D4 2006 13:14:40,764 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 13:14:41,779 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 13:14:42,779 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:0
14 =CC=C9=D3=D4 2006 13:14:47,436 [INFO ] com.incom.proxool.DBBroker =
{DBLogBroker_.java:51} - Time of getting connection:16

Re: [Proxool-developer] Newbie introduction to proxool under servlet environment

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

Hi Morton,

On 06/27/2006 07:22 AM, Morten Andersen wrote:

>  <servlet>
>         <servlet-name>ServletConfigurator</servlet-name>
>         
> <servlet-class>org.logicalcobwebs.proxool.configuration.ServletConfigurator</servlet-class>
>         <init-param>
>             <param-name>xmlFile</param-name>
>             <param-value>WEB-INF/conf/proxool.xml</param-value>
>         </init-param>
>     </servlet>

You left out the load-on-startup element.

-
Bill

[Proxool-developer] Newbie introduction to proxool under servlet environment

[Morten A. <mo...@bl...>]

I'm new to proxool and tries to get it to work under a servlet environment.

I've registered the configuration servlet in my web.xml file as described:

 <servlet>
        <servlet-name>ServletConfigurator</servlet-name>
        
<servlet-class>org.logicalcobwebs.proxool.configuration.ServletConfigurator</servlet-class>
        <init-param>
            <param-name>xmlFile</param-name>
            <param-value>WEB-INF/conf/proxool.xml</param-value>
        </init-param>
    </servlet>

Adn put my proxool.xml file in the folder:  "WEB-INF/conf" in the web 
application. I would then expect the pool to be registered as I reload 
the application, but it is not.

The administration servlet respons is:

Proxool 0.9.0RC2 (23-Mar-2006 23:39)

No pools have been registered.

I've successfully set up a connection pool in the very same environment 
where I've set the properties using java.

Please give a hint to where I can find the log statements or how I can 
figure out what went wrong. I have a few ideas:

 - The connection pool is not set up automatically as I reload the 
application.
 - I've somehow made a mistake as I initiated the connection pool, but 
can't see what.

Thanks

Morten Andersen   

Re: [Proxool-developer] (no subject)

[biglaughing <big...@gm...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=GB2312" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,Mr Wang<br>
<br>
read this link <br>
<br>
<a class="moz-txt-link-freetext" href="http://proxool.sourceforge.net/properties.html">http://proxool.sourceforge.net/properties.html</a><br>
<br>
I am from China too.<br>
<br>
<br>
<br>
王鹏 wrote:
<blockquote cite="mid...@sm..." type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta name="Generator" content="Microsoft Word 11 (filtered medium)">
  <o:SmartTagType
 namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="country-region">
  <o:SmartTagType
 namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
  <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:宋体;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@宋体";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:宋体;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
-->
  </style></o:SmartTagType></o:SmartTagType>
  <div class="Section1" style="">
  <p class="MsoNormal"><font face="Arial" size="1"><span
 style="font-size: 9pt; font-family: Arial;" lang="EN-US">Hello<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font face="Arial" size="1"><span
 style="font-size: 9pt; font-family: Arial;" lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How
do you do , I come from <st1:place w:st="on"><st1:country-region
 w:st="on">China</st1:country-region></st1:place>
, I want to ask some questions .<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font face="Arial" size="1"><span
 style="font-size: 9pt; font-family: Arial;" lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When
I use the Proxool , I donw’t know how to set the DB timeout at the
properties
file , I hope get the help from you .<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font face="Arial" size="1"><span
 style="font-size: 9pt; font-family: Arial;" lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Thanks
very much !<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font face="Arial" size="1"><span
 style="font-size: 9pt; font-family: Arial;" lang="EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; My
English is so bad , very very Sorry !<o:p></o:p></span></font></p>
  <p class="MsoNormal"><font face="Arial" size="1"><span
 style="font-size: 9pt; font-family: Arial;" lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  <p class="MsoNormal"><font face="Times New Roman" size="2"><span
 lang="EN-US"><o:p>&nbsp;</o:p></span></font></p>
  </div>
  <br>
  <font size="2">
  <hr color="#000099"> <font color="#000099"><strong>Confidentiality
Notice:</strong> The information contained in this e-mail and any
accompanying attachment(s) is intended only for the use of the intended
recipient and may be confidential and/or privileged of Neusoft Group
Ltd., its subsidiaries and/or its affiliates. If any reader of this
communication is not the intended recipient, unauthorized use,
forwarding, printing, storing, disclosure or copying is strictly
prohibited, and may be unlawful. If you have received this
communication in error, please immediately notify the sender by return
e-mail, and delete the original message and all copies from your
system. Thank you. </font>
  <hr color="#000099"> </font>
  <pre wrap="">
<hr size="4" width="90%">
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
<a class="moz-txt-link-freetext" href="http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642">http://sel.as-us.falkag.net/sel?cmd=lnk&amp;kid=120709&amp;bid=263057&amp;dat=121642</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Proxool-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pro...@li...">Pro...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/proxool-developer">https://lists.sourceforge.net/lists/listinfo/proxool-developer</a>
  </pre>
</blockquote>
<br>
</body>
</html>

[Proxool-developer] (no subject)

[<wan...@ne...>]

Hello

         How do you do , I come from China , I want to ask some questions .

         When I use the Proxool , I donw=A1=AFt know how to set the DB time=
out
at the properties file , I hope get the help from you .

         Thanks very much !

         My English is so bad , very very Sorry !

=20

=20



---------------------------------------------------------------------------=
-------------------
Confidentiality Notice: The information contained in this e-mail and any ac=
companying attachment(s) is intended only for the use of the intended recip=
ient and may be confidential and/or privileged of Neusoft Group Ltd., its s=
ubsidiaries and/or its affiliates. If any reader of this communication is n=
ot the intended recipient, unauthorized use, forwarding, printing, storing,=
 disclosure or copying is strictly prohibited, and may be unlawful. If you =
have received this communication in error, please immediately notify the se=
nder by return e-mail, and delete the original message and all copies from =
your system. Thank you.=20
---------------------------------------------------------------------------=
--------------------

[Proxool-developer] Hi,everyone,I got a prob with proxool

[openlis <big...@gm...>]

hi,everyone.

our system runs on weblogic 8.1 server.
and the system use the weblogic jdbc-connection-pool.
http://e-docs.bea.com/wls/docs81/ConsoleHelp/jdbc_connection_pools.html

we use this way to call the weblogic connection pool

Driver myDriver = (Driver)
(Class.forName("weblogic.jdbc.pool.Driver").newInstance());
con = myDriver.connect(JUrl.getJdbcUrl(), null);


So,if i integrate proxool-connection-pool with the jdbc-connection-pool.
will it work ?
i am confused by double connection pool .

if i use 2 connection pool will that work?
if i call a connection ,where will the connection come from ?



thanks,all
[==free as freedom==]

[Proxool-developer] Latest proxool cglib issue with Hibernate 3.2

[Christian M. <chr...@ma...>]

Hi, i recently tried proxool within my webapp and suddently, i got some 
weird issues from Hibernate:

java.lang.LinkageError: duplicate class definition: 
$java/lang/Object$$FastClassByCGLIB$$3f697993
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    ... 115 more

As soon as i switched back to C3P0 or JNDI, all the issues were "fixed".
Knowing that Proxool embeded cglib, something must going on with this.

Regards
Chris

Re: [Proxool-developer] Proxool with Hibernate/Spring

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

Hi Mahendra,

On 04/03/2006 10:29 PM, Mahendra KC wrote:

> Under User Guide-> Configuration section, Wouldn't it be nice to add the 
> documentation on configuring Proxool with Hibernate/Spring?

It's an excellent idea. We'll definitely include that in 0.9.0. I'll try 
and investigate that soon. (If anyone else can help out with this I'd 
appreciate it).

-
Bill

[Proxool-developer] Proxool with Hibernate/Spring

[Mahendra K. <mah...@ho...>]

Hello all,

I am not sure if this is more of a Hibernate question or a proxool qouestion 
but here is my scenario.

I am trying to configure proxool with Hibernate/Spring ( I am using 
Hibernate 3.0) . I have all the proxool properties in the database table. 
Before Hibernate, the way I used to do was create a class called DBUtilities 
that would instantiate a Properties object in a static block by reading all 
the properties from the database. Every request to Connection would pass 
this parameter. With Hibernate, is there a way to programmatically give the 
property instead of fetching externally from flat/xml file?

I came across http://www.hibernate.org/222.html but not sure how much 
updated the document is. Should we require  'hibernate" prefix or not for 
Hibernate 3 and above?

Under User Guide-> Configuration section, Wouldn't it be nice to add the 
documentation on configuring Proxool with Hibernate/Spring?

Thanks in advance
Mahendra

[Proxool-developer] 0.9.0RC1

[Bill H. <bil...@gm...>]

Hi,

The alert amongst you will notice that I released 0.9.0RC1 last 
Thursday. Hopefully we can get 0.9.0 final out of the door quite soon. 
If anyone has any feedback then I'd be interested to hear it.

Kristian Eide has brought to my attention the fact that Proxool doesn't 
work with the later betas of JDK 1.6. This is because we use an old 
version of Cglib. I've done a bit of investigation and the later version 
(2.1_3) does appear to solve the problem. I've also started to use a 
project called JarJar which will automatically repackage an external 
project for us. This makes it a lot easier to stay up to date.

So, I'm considering making a 0.9.0RC2 release in the next few days with 
Cglib 2.1_3. Let me know what you think about that.

Note that I am still proposing to repackage Cglib and ASM into the 
org.logicalcobwebs domain.

-
Bill

[Proxool-developer] (no subject)

[Buller, J. <jef...@et...>]

confirm 524091

[Proxool-developer] Unbundling commons-logging

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

Hi all,

I'm considering unbundling commons-logging from the upcoming release of 
Proxool 0.9.0. I had some class loader issues when I tried to deployed 
the latest code into Tomcat 5.5 and switching to the external 
commons-logging was the only option.

For the record, we copied the commons-logging 1.02 code into Proxool in 
February 2003 for Proxool 0.7. We created a new package called 
org.logicalcobwebs.logging. We did this along with a couple other 
components: cglib and asm.

The case for cglib and asm is a good one since changes they made to the 
code could break Proxool and we didn't want to have to make emergency 
releases of Proxool to keep in step with cglib and asm.

But commons-logging is unlikely to break Proxool I feel and the only 
benefit we get is not having to have that dependency. However, there are 
some serious drawbacks to bundling our own version of commons-logging:

1. There is a class loader problem in some situationns.

2. Logging is often done by the container or by the application and 
problems arise if Proxool is logging to some classes whilst other code 
is logging elsewhere.

So I'm proposing that we remove the commons-logging code from Proxool 
and list commons-logging as a dependency.

Any comments?

-
Bill

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Hrvoje N. <hn...@xe...>]

Bill Horsman <arc...@gm...> writes:

> 2005-09-27 01:36:56 WARN  [poolname] [HouseKeeper]: #1660 was active
>   for 144709 milliseconds and has been removed automaticaly. The Thread
>   responsible was named 'Thread-18'.
> [...]
> 2005-09-27 01:36:57 DEBUG [poolname] [Thread-18]: 1003445 -000257
>   (04/32/00) - #1660 removed because it couldn't be reset.
>
>   The connection #1660 has been removed twice, which means it could have
>   decremented connectionCount twice as well.
>
>   What do you think?
>
> I think you're on to something there. I had a first look at this on
> the train this morning and I'm starting to get my head round it. I'm
> trying to reproduce the problem in a unit test at the moment. It's
> tricky getting the connection reset to fail but I can get round
> that.

Thanks for looking into it.  Please let me know if you need more
information.

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Bill H. <arc...@gm...>]

Hi Hrvoje,

On 10/1/05, Hrvoje Niksic <hn...@xe...> wrote:

> Note especially these two lines:
>
> 2005-09-27 01:36:56 WARN [poolname] [HouseKeeper]: #1660 was active for
> 144709 milliseconds and has been removed automaticaly. The Thread
> responsible was named 'Thread-18'.
> [...]
> 2005-09-27 01:36:57 DEBUG [poolname] [Thread-18]: 1003445 -000257
> (04/32/00) - #1660 removed because it couldn't be reset.
>
> The connection #1660 has been removed twice, which means it could have
> decremented connectionCount twice as well.
>
> What do you think?


I think you're on to something there. I had a first look at this on the
train this morning and I'm starting to get my head round it. I'm trying to
reproduce the problem in a unit test at the moment. It's tricky getting the
connection reset to fail but I can get round that.

-
Bill

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Hrvoje N. <hn...@xe...>]

Bill Horsman <arc...@gm...> writes:

>   Isn't there a hint on how I could fix the problem with the
>   Prototyper's connectionCount?  Is the protection from calling
>   reallyClose() twice the correct approach?
>
> I'm not sure. Does the number of extra connections created
> correspond with the number of reported connections that were closed
> automatically?

The additional connections apparently coincide with the occurrence of
this messag:

2005-09-27 01:36:57 WARN  [poolname] [Thread-18]: #1660 - There were some problems resetting the connection (see debug output for details). It will not be used again (just in case). The thread that is responsible is named 'Thread-18'

It seems to occur after the HouseKeeper forcibly removes the
connection.  In our logs the number of these messages equals the
number of additional connections in the pool.

An example:

2005-09-27 01:36:56 DEBUG [poolname] [HouseKeeper]: 1003445 -000257 (04/31/00) - #1660 removed because it has been active for too long.
2005-09-27 01:36:56 WARN  [poolname] [HouseKeeper]: #1660 was active for 144709 milliseconds and has been removed automaticaly. The Thread responsible was named 'Thread-18'.
2005-09-27 01:36:56 DEBUG [poolname] [Prototyper]: 1003445 -000257 (04/32/00) - Connection #1665 created to achieve minimum of 2 = AVAILABLE
2005-09-27 01:36:57 WARN  [poolname] [Thread-18]: #1660 - There were some problems resetting the connection (see debug output for details). It will not be used again (just in case). The thread that is responsible is named 'Thread-18'
2005-09-27 01:36:57 WARN  [poolname] [Thread-18]: #1660 - The connection was closed with autoCommit=false. That is fine, but it might indicate that the problems that happened whilst trying to reset it were because a transaction is still in progress.
2005-09-27 01:36:57 DEBUG [poolname] [Thread-18]: 1003445 -000257 (04/32/00) - #1660 removed because it couldn't be reset.
2005-09-27 01:36:57 WARN  [poolname] [Thread-18]: Unable to set status of connection 1660 from ACTIVEto AVAILABLE. It remains NULL

Note especially these two lines:

    2005-09-27 01:36:56 WARN  [poolname] [HouseKeeper]: #1660 was active for 144709 milliseconds and has been removed automaticaly. The Thread responsible was named 'Thread-18'.
    [...]
    2005-09-27 01:36:57 DEBUG [poolname] [Thread-18]: 1003445 -000257 (04/32/00) - #1660 removed because it couldn't be reset.

The connection #1660 has been removed twice, which means it could have
decremented connectionCount twice as well.

What do you think?

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Bill H. <arc...@gm...>]

Hi Hrvoje,

On 9/30/05, Hrvoje Niksic <hn...@xe...> wrote:

> > Mitch's patch does make sense. You might want to consider making it
> > thread safe.
>
> I can do that. Is the additional ++connectionCount in the last hunk
> of his patch also in your opinion correct?


Hmm. That /is/ a bug. And it's still in the latest code :( That variable
only comes into effect in turning away requests quickly which is why it
hasn't been spotted before. If it's wrong (too low) then it means that the
"triage" stage will accept the connection but will refuse it when it
discovers isn't aren't any.

I think I would increment that count in a slightly different place.
ConnectionPool.addProxyConnection to be precise

protected void addProxyConnection(ProxyConnectionIF proxyConnection) {
try {
acquireConnectionStatusWriteLock();
proxyConnections.add(proxyConnection);
connectionCountByState[proxyConnection.getStatus()]++;
connectionCount++; // Patch
} finally {
releaseConnectionStatusWriteLock();
}
}

However, I haven't tested that. The connectionCount isn't displayed in the
logs and it's not used when deciding whether to build a new connection so i=
t
isn't helpful to your solution. (Although, I agree it should be fixed).

Back to the problem that you are experiencing. My simple unit test didn't
track it down. But I have some ideas that I'll try out over the next few
days. Feel free to bug me about that.

-
Bill

-
Bill

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Hrvoje N. <hn...@xe...>]

Bill Horsman <arc...@gm...> writes:

> 0.8.9b6 is shortly to become RC1. There are no known problems. If
> you are able to test it in a non-production environment that would
> be very helpful.

As you're probably guessing, the problem is that we cannot reproduce
the problem in a non-production environment.  Testbeds typically don't
have that kind of heavy load and the same database access conditions.
Faithfully duplicating production workload in a testing environment is
a notoriously difficult problem.

What we can do, however, is provide the (excerpts from) Proxool logs
and the contents of AdminServlet, or any other data that can help you
locate the problem.  Just tell me if you need additional info.

>   Isn't there a hint on how I could fix the problem with the
>   Prototyper's connectionCount?  Is the protection from calling
>   reallyClose() twice the correct approach?
>
> I'm not sure. Does the number of extra connections created
> correspond with the number of reported connections that were closed
> automatically?

It's in the same ballpark, but it's hard to prove reliably because the
logs are huge and scattered over several days, and I don't have them
all at the moment.  I'll look into it and get back to you on that.

> Mitch's patch does make sense.  You might want to consider making it
> thread safe.

I can do that.  Is the additional ++connectionCount in the last hunk
of his patch also in your opinion correct?

Thanks for your help and the quick response!

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Bill H. <arc...@gm...>]

Hi Hrvoje,

On 9/30/05, Hrvoje Niksic <hn...@xe...> wrote:

> It doesn't seem like a good idea to try out the unofficial beta on a
> server already in production and used by thousands of simultaneous
> users.


I agree. It wasn't my suggestion.

0.8.9b6 is shortly to become RC1. There are no known problems. If you are
able to test it in a non-production environment that would be very helpful.

Isn't there a hint on how I could fix the problem with the
> Prototyper's connectionCount? Is the protection from calling
> reallyClose() twice the correct approach?


I'm not sure. Does the number of extra connections created correspond with
the number of reported connections that were closed automatically?

Mitch's patch does make sense. You might want to consider making it thread
safe.

I cannot find the source of 0.8.9b6.


It is /very/ similar to the latest code from CVS. (The only class that is
different is AdminServlet and that has no bearing on this). That one class
being different is what makes it unofficial.

-
Bill

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Hrvoje N. <hn...@xe...>]

Bill Horsman <arc...@gm...> writes:

> On 9/30/05, Hrvoje Niksic <hn...@xe...> wrote:
>
>   So proxool should maintain no less than 2 and no more than 30
>   connections to the database.  But, over time, it appears that proxool
>   opens more connections, eventually exhausting Oracle's
>   SESSIONS_PER_USER limit.  
>
> That is strange. We've made this a lot more robust in the latest
> code - all connections are wrapped and specifically protect
> themselves against multiple closures. Perhaps you'd like to try out
> the latest, unofficial beta version?

It doesn't seem like a good idea to try out the unofficial beta on a
server already in production and used by thousands of simultaneous
users.  Isn't there a hint on how I could fix the problem with the
Prototyper's connectionCount?  Is the protection from calling
reallyClose() twice the correct approach?

I cannot find the source of 0.8.9b6.  The sources at
http://proxool.sourceforge.net/download/proxool-cvs-20050504.tgz don't
seem to do things much differently from 0.8.3 -- but I could be
missing something.

Re: [Proxool-developer] Spurious connections caused by Prototyper's apparently wrong connectionCount

[Bill H. <arc...@gm...>]

Hi Hrvoje,

On 9/30/05, Hrvoje Niksic <hn...@xe...> wrote:

> So proxool should maintain no less than 2 and no more than 30
> connections to the database. But, over time, it appears that proxool
> opens more connections, eventually exhausting Oracle's
> SESSIONS_PER_USER limit.


That is strange. We've made this a lot more robust in the latest code - all
connections are wrapped and specifically protect themselves against multipl=
e
closures. Perhaps you'd like to try out the latest, unofficial beta version=
?

http://proxool.sourceforge.net/download/proxool-0.8.9b6.jar

I'd be interested in your results.

-
Bill