RE: connection pool - DBCP error
yes, I believe soI added some other param attributes that I think will properly kill off abandoned connections if they didn't before get killed off. -Original Message- From: Tim Lucia [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 4:22 PM To: 'Tomcat Users List' Subject: RE: connection pool - DBCP error > -Original Message- > From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] > Sent: Monday, February 26, 2007 4:48 PM > To: Tomcat Users List > Subject: connection pool - DBCP error > > AbandonedObjectPool is used > ( [EMAIL PROTECTED]) > >LogAbandoned: true >RemoveAbandoned: true >RemoveAbandonedTimeout: 60 Isn't this just an informational message saying that abandoned objects will be detected? It appears on startup when I configure DBCP to evict abandoned connections... Tim - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: connection pool - DBCP error
Thats purely informational. On 2/27/07, Tim Lucia <[EMAIL PROTECTED]> wrote: > -Original Message- > From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] > Sent: Monday, February 26, 2007 4:48 PM > To: Tomcat Users List > Subject: connection pool - DBCP error > > AbandonedObjectPool is used > ( [EMAIL PROTECTED]) > >LogAbandoned: true >RemoveAbandoned: true >RemoveAbandonedTimeout: 60 Isn't this just an informational message saying that abandoned objects will be detected? It appears on startup when I configure DBCP to evict abandoned connections... Tim - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: connection pool - DBCP error
> -Original Message- > From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] > Sent: Monday, February 26, 2007 4:48 PM > To: Tomcat Users List > Subject: connection pool - DBCP error > > AbandonedObjectPool is used > ( [EMAIL PROTECTED]) > >LogAbandoned: true >RemoveAbandoned: true >RemoveAbandonedTimeout: 60 Isn't this just an informational message saying that abandoned objects will be detected? It appears on startup when I configure DBCP to evict abandoned connections... Tim - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: connection pool - DBCP error
The pooling in tomcat is a refactored copy of Commons-DBCP (http://jakarta.apache.org/commons/dbcp). See the javadocs for org.apache.commons.dbcp.BasicDataSource for all the options settable. minEvictableIdleTimeMillis="" translates to setMinEvictableIdleTimeMillis(). --David Propes, Barry L [GCG-NAOT] wrote: >Daniel, > >I scoured the APIs for that method and couldn't find anywhere, but I added to >my server.xml file any way. > >Without something like lamda probe, would I see any connections dropping, or >would I need a third party tool like that to see it logged? > >ORwould I just not get any errors like before and assume that that >addition and revision has successfully addressed it? > >Thanks! > >Barry > >-Original Message- >From: Stephens, Daniel [mailto:[EMAIL PROTECTED] >Sent: Monday, February 26, 2007 4:55 PM >To: Tomcat Users List >Subject: RE: connection pool - DBCP error > > >I had to add the following before I saw that behavior. You'll have to check >the API, to make sure the minEvictableIdleTimeMillis and >timeBetweenEvictionRunsMillis are set correctly for your pool. But once I >added these, I would see abandoned connections get dropped. > >I put these settings in, because I found that the DBCP pool only evalutes >connections on a check-in/out basis. > > >minEvictableIdleTimeMillis5000eter> > >timeBetweenEvictionRunsMillis1arameter> > testWhileIdletrue > validationQueryselect count(*) from >dual > > >-Original Message- >From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] >Sent: Monday, February 26, 2007 3:48 PM >To: Tomcat Users List >Subject: connection pool - DBCP error > >I am getting a slight error with regards to my connection pool >configuration. > >I may not have totally closed the connection properly, but shouldn't the >following account for it? > > > >AbandonedObjectPool is used ( >[EMAIL PROTECTED]) > > LogAbandoned: true > RemoveAbandoned: true > RemoveAbandonedTimeout: 60 > > >in other words, if I have the following configured like so, > > > maxWait > 7000 > > > removeAbandoned > true > > > removeAbandonedTimeout > 60 > > > logAbandoned > true > > >shouldn't the RemoveAbandoned params account for an open or vagrant >connection and kill it off properly? >Am I wrong in the assumption this attribute should have? > >Thanks, > >Barry > > >- >The information in this message may be proprietary and/or >confidential, and protected from disclosure. If the reader of this >message is not the intended recipient, or an employee or agent >responsible for delivering this message to the intended recipient, >you are hereby notified that any dissemination, distribution or >copying of this communication is strictly prohibited. If you have >received this communication in error, please notify First Data >immediately by replying to this message and deleting it from your >computer. > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: connection pool - DBCP error
ok, thanks, David! -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 1:06 PM To: Tomcat Users List Subject: Re: connection pool - DBCP error The pooling in tomcat is a refactored copy of Commons-DBCP (http://jakarta.apache.org/commons/dbcp). See the javadocs for org.apache.commons.dbcp.BasicDataSource for all the options settable. minEvictableIdleTimeMillis="" translates to setMinEvictableIdleTimeMillis(). --David Propes, Barry L [GCG-NAOT] wrote: >Daniel, > >I scoured the APIs for that method and couldn't find anywhere, but I added to >my server.xml file any way. > >Without something like lamda probe, would I see any connections dropping, or >would I need a third party tool like that to see it logged? > >ORwould I just not get any errors like before and assume that that >addition and revision has successfully addressed it? > >Thanks! > >Barry > >-Original Message- >From: Stephens, Daniel [mailto:[EMAIL PROTECTED] >Sent: Monday, February 26, 2007 4:55 PM >To: Tomcat Users List >Subject: RE: connection pool - DBCP error > > >I had to add the following before I saw that behavior. You'll have to check >the API, to make sure the minEvictableIdleTimeMillis and >timeBetweenEvictionRunsMillis are set correctly for your pool. But once I >added these, I would see abandoned connections get dropped. > >I put these settings in, because I found that the DBCP pool only evalutes >connections on a check-in/out basis. > > >minEvictableIdleTimeMillis5000eter> > >timeBetweenEvictionRunsMillis1arameter> > testWhileIdletrue > validationQueryselect count(*) from >dual > > >-Original Message- >From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] >Sent: Monday, February 26, 2007 3:48 PM >To: Tomcat Users List >Subject: connection pool - DBCP error > >I am getting a slight error with regards to my connection pool >configuration. > >I may not have totally closed the connection properly, but shouldn't the >following account for it? > > > >AbandonedObjectPool is used ( >[EMAIL PROTECTED]) > > LogAbandoned: true > RemoveAbandoned: true > RemoveAbandonedTimeout: 60 > > >in other words, if I have the following configured like so, > > > maxWait > 7000 > > > removeAbandoned > true > > > removeAbandonedTimeout > 60 > > > logAbandoned > true > > >shouldn't the RemoveAbandoned params account for an open or vagrant >connection and kill it off properly? >Am I wrong in the assumption this attribute should have? > >Thanks, > >Barry > > >- >The information in this message may be proprietary and/or >confidential, and protected from disclosure. If the reader of this >message is not the intended recipient, or an employee or agent >responsible for delivering this message to the intended recipient, >you are hereby notified that any dissemination, distribution or >copying of this communication is strictly prohibited. If you have >received this communication in error, please notify First Data >immediately by replying to this message and deleting it from your >computer. > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: connection pool - DBCP error
Daniel, I scoured the APIs for that method and couldn't find anywhere, but I added to my server.xml file any way. Without something like lamda probe, would I see any connections dropping, or would I need a third party tool like that to see it logged? ORwould I just not get any errors like before and assume that that addition and revision has successfully addressed it? Thanks! Barry -Original Message- From: Stephens, Daniel [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 4:55 PM To: Tomcat Users List Subject: RE: connection pool - DBCP error I had to add the following before I saw that behavior. You'll have to check the API, to make sure the minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis are set correctly for your pool. But once I added these, I would see abandoned connections get dropped. I put these settings in, because I found that the DBCP pool only evalutes connections on a check-in/out basis. minEvictableIdleTimeMillis5000 timeBetweenEvictionRunsMillis1 testWhileIdletrue validationQueryselect count(*) from dual -Original Message- From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 3:48 PM To: Tomcat Users List Subject: connection pool - DBCP error I am getting a slight error with regards to my connection pool configuration. I may not have totally closed the connection properly, but shouldn't the following account for it? AbandonedObjectPool is used ( [EMAIL PROTECTED]) LogAbandoned: true RemoveAbandoned: true RemoveAbandonedTimeout: 60 in other words, if I have the following configured like so, maxWait 7000 removeAbandoned true removeAbandonedTimeout 60 logAbandoned true shouldn't the RemoveAbandoned params account for an open or vagrant connection and kill it off properly? Am I wrong in the assumption this attribute should have? Thanks, Barry - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
RE: connection pool - DBCP error
thanks, Daniel!! I"ll try to plug that in and see if my version will accept those params! -Original Message- From: Stephens, Daniel [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 4:55 PM To: Tomcat Users List Subject: RE: connection pool - DBCP error I had to add the following before I saw that behavior. You'll have to check the API, to make sure the minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis are set correctly for your pool. But once I added these, I would see abandoned connections get dropped. I put these settings in, because I found that the DBCP pool only evalutes connections on a check-in/out basis. minEvictableIdleTimeMillis5000 timeBetweenEvictionRunsMillis1 testWhileIdletrue validationQueryselect count(*) from dual -Original Message- From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 3:48 PM To: Tomcat Users List Subject: connection pool - DBCP error I am getting a slight error with regards to my connection pool configuration. I may not have totally closed the connection properly, but shouldn't the following account for it? AbandonedObjectPool is used ( [EMAIL PROTECTED]) LogAbandoned: true RemoveAbandoned: true RemoveAbandonedTimeout: 60 in other words, if I have the following configured like so, maxWait 7000 removeAbandoned true removeAbandonedTimeout 60 logAbandoned true shouldn't the RemoveAbandoned params account for an open or vagrant connection and kill it off properly? Am I wrong in the assumption this attribute should have? Thanks, Barry - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
RE: connection pool - DBCP error
I had to add the following before I saw that behavior. You'll have to check the API, to make sure the minEvictableIdleTimeMillis and timeBetweenEvictionRunsMillis are set correctly for your pool. But once I added these, I would see abandoned connections get dropped. I put these settings in, because I found that the DBCP pool only evalutes connections on a check-in/out basis. minEvictableIdleTimeMillis5000 timeBetweenEvictionRunsMillis1 testWhileIdletrue validationQueryselect count(*) from dual -Original Message- From: Propes, Barry L [GCG-NAOT] [mailto:[EMAIL PROTECTED] Sent: Monday, February 26, 2007 3:48 PM To: Tomcat Users List Subject: connection pool - DBCP error I am getting a slight error with regards to my connection pool configuration. I may not have totally closed the connection properly, but shouldn't the following account for it? AbandonedObjectPool is used ( [EMAIL PROTECTED]) LogAbandoned: true RemoveAbandoned: true RemoveAbandonedTimeout: 60 in other words, if I have the following configured like so, maxWait 7000 removeAbandoned true removeAbandonedTimeout 60 logAbandoned true shouldn't the RemoveAbandoned params account for an open or vagrant connection and kill it off properly? Am I wrong in the assumption this attribute should have? Thanks, Barry - The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer.
connection pool - DBCP error
I am getting a slight error with regards to my connection pool configuration. I may not have totally closed the connection properly, but shouldn't the following account for it? AbandonedObjectPool is used ( [EMAIL PROTECTED]) LogAbandoned: true RemoveAbandoned: true RemoveAbandonedTimeout: 60 in other words, if I have the following configured like so, maxWait 7000 removeAbandoned true removeAbandonedTimeout 60 logAbandoned true shouldn't the RemoveAbandoned params account for an open or vagrant connection and kill it off properly? Am I wrong in the assumption this attribute should have? Thanks, Barry
