Hi jaikiran ,
thanks for the prompt reply but I had already taken care of the oracle-ds.xml file attributes and everything looks fine over there to me here is the snapshot of the same
Are you sure that you dont have any connection leaks in your application? Also, you say that you are running a 15+ hour test on JBoss, so is 100 max-pool-size sufficient for your application? And the logs that you posted show a blocking timeout of 5000 ms where as the -ds.xml configuration that you posted has 30000 ms. So are you sure you did the changes at the right place and they are being picked up?
yeah I had checked the application for any connection leaks they are perfectly alright we had closed connection properly in the finally block.....also I had later on changed the value from <blocking-timeout-millis>5000</blocking-timeout-millis> to <blocking-timeout-millis>30000</blocking-timeout-millis> to see if it serves our purpose....(and ofcourse restarted the system)...I thnk 100 connections will be fine enough as we are also releasing connections properly...this test is carried out on solaris machines
Monitor the number of connections in use, especially when this exception occurs, through the jmx-console. Access jmx-console at http://localhost:8080/jmx-console. On this page under jboss.jca, you will find a link like name=myDS,service=ManagedConnectionPool (where myDS is the jndi-name of your datasource). Click on this link and you will be forwarded to a page which will have the connection count and other details about this connection pool.
Check out the number of connections that are in use.
Yeah I am viewing the same.... the test is started since then I am frequenty viweing the status...also this happens after 9 to 10 hours....dunno Y....one more thing we also have hsqldb sharing the connections for message persistence....