[ 
https://issues.apache.org/jira/browse/POOL-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737761#comment-13737761
 ] 

Phil Steitz commented on POOL-237:
----------------------------------

You can tell the actual version by unpacking the jar and looking at the 
manifest, which for what you attached is 1.6.  The line numbers in the stack 
traces match 1.3, however.  I suggest you check carefully the actual classpath 
in use.  Unless you can provide a test case of some kind indicating an actual 
commons pool bug, I am inclined to close this as INVALID and refer you to the 
user list for further help.
                
> returnObject call is stuck for more than 11 mins
> ------------------------------------------------
>
>                 Key: POOL-237
>                 URL: https://issues.apache.org/jira/browse/POOL-237
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.6
>         Environment: Its our Production environment
>            Reporter: samjna
>         Attachments: commons-pool-1.6.jar
>
>
> Hi,
> I recently upgraded from Commons-pool.1.3 API to 1.6, I use this 
> GenericObjectPool for Corba connection pooling. But today I noticed that my 
> server thread was stuck because of returnObject. I thought it was resolved 
> already, but doesnt look like.
> ####<8-Aug-2013 9:14:09 o'clock PM UTC> <Error> <WebLogicServer> 
> <sedm3216.ent.agt.ab.ca> <XXXXXXXSrv1> <[ACTIVE] ExecuteThread:
>  '177' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> 
> <> <1375996449633> <BEA-000337> <[STUCK] ExecuteThread:
>  '73' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for 
> "629" seconds working on the request "com.xxxxx.services.
> xxxxxxxxx.service.impl.XxxxxxxEJB_mwazfy_EOImpl", which is more than the 
> configured time (StuckThreadMaxTime) of "600" seconds
> . Stack trace:
>         
> org.apache.commons.pool.impl.GenericObjectPool.returnObject(GenericObjectPool.java:916)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to