aspose file tools*
The moose likes JBoss/WildFly and the fly likes No ManagedConnections available within configured blocking timeout ( 5000 [ms] ) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "No ManagedConnections available within configured blocking timeout ( 5000 [ms] )" Watch "No ManagedConnections available within configured blocking timeout ( 5000 [ms] )" New topic
Author

No ManagedConnections available within configured blocking timeout ( 5000 [ms] )

Saravanakumar Jeyavel
Greenhorn

Joined: Aug 20, 2012
Posts: 6
Hi,

I am getting the below error when i run my application in jboss 4.0.2 with oracle11g.

org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 5000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 5000 [ms] ))
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:107)


my configuration in oracle-ds is as below




any suggestion/help would be really appreciated.

Thanks
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10289
    
168

See https://community.jboss.org/wiki/WhatDoesTheMessageNoManagedConnectionsAvailableMean

[My Blog] [JavaRanch Journal]
Saravanakumar Jeyavel
Greenhorn

Joined: Aug 20, 2012
Posts: 6
Thanks Jaikiran ... i noticed that after closing db connection in java code, i don't see any effect on the number of opened connection and available connection thru jboss jmx-console. if i increase the connection pool size to 100 or 200, wouldn't i get the same issue after reaching the max-pool-size because there is no decrease in connection size after closing the db connection in the finally block. why the jboss is not handling the internal db connection pooling ?

i will implement what have suggested.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: No ManagedConnections available within configured blocking timeout ( 5000 [ms] )