Hi All,
We are running JBoss 3.2.1 with Tomcat and experiencing a strange
problem:
Our ManagedConnectionPool parameters are configured as follows:
MaxSize = 20
MinSize = 0
IdleTimeoutMinutes = 15
BlockingTimeoutMillis = 5000
ManagedConnectionFactoryName =
jboss.jca:service=ManagedConnectionFactory,name=MSSQLDS
Criteria = ByNothing
And the unexpected behaviour:
1 hour after JBoss restart parameters were:
ConnectionCreatedCount = 4
ConnectionDestroyedCount = 1
AvailableConnectionCount = 20
21 hours after JBoss restart parameters were:
ConnectionCreatedCount = 59
ConnectionDestroyedCount = 46
AvailableConnectionCount = 9
ConnectionCount = 13
25 hours after JBoss restart parameters were:
ConnectionCreatedCount = 71
ConnectionDestroyedCount = 51
AvailableConnectionCount = 2
ConnectionCount = 20
After 26 hours AvailableConnectionCount was 0, and exception occured
"org.jboss.util.NestedSQLException: No ManagedConnections Available!; -
nested throwable: (javax.resource.ResourceException: No
ManagedConnections Available!)
at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:106)
"
Question: what is causing us to lose available connections?
Second Question: what's the difference between AvailableConnectionCount
and ConnectionCount?
Best Regards,
Joel
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
