Thanks for updating the ticket. anonymous wrote : | This means that the TX timeout occurs in your application code , you either need to fine tune the SQL or configure the TX timeout |
None of the queries we fire take more then 5-10 ms. Also all the connections are already closed in a finally block. So no way that we aren't closing the connections. anonymous wrote : | Does AvailableConnectionCount+InUseConnectionCount exceeds max connection , looks like subpools are getting created . | Paste the contents of your oracle-ds.xml file , let me have a look at it . | Actually AvailableConnectionCount + InUseConnectionCount is lesser then max-pool-size configured in oracle-ds.xml. Below is the oracle-ds.xml. anonymous wrote : | <?xml version="1.0" encoding="UTF-8"?> | | <!-- ===================================================================== --> | <!-- --> | <!-- JBoss Server Configuration --> | <!-- --> | <!-- ===================================================================== --> | | <!-- $Id: oracle-ds.xml.template,v 1.1.2.1 2006/01/25 19:39:32 akocic Exp $ --> | <!-- ==================================================================== --> | <!-- Datasource config for Oracle originally from Steven Coy --> | <!-- ==================================================================== --> | | | | <local-tx-datasource> | <jndi-name>jdbc/oraSAM</jndi-name> | <connection-url>jdbc:oracle:thin:@15.112.12.145:1521:sid</connection-url> | <!-- | | Here are a couple of the possible OCI configurations. | For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.920/a96654/toc.htm | | <connection-url>jdbc:oracle:oci:@youroracle-tns-name</connection-url> | or | <connection-url>jdbc:oracle:oci:@(description=(address=(host=youroraclehost)(protocol=tcp)(port=1521))(connect_data=(SERVICE_NAME=yourservicename)))</connection-url> | | Clearly, its better to have TNS set up properly. | --> | <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> | <user-name>testuser</user-name> | testuser <min-pool-size>0</min-pool-size> <max-pool-size>130</max-pool-size> <blocking-timeout-millis>5000</blocking-timeout-millis> <idle-timeout-minutes>3 </idle-timeout-minutes> | <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool --> | <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name--> | <!-- Checks the Oracle error codes and messages for fatal errors --> | <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name> | <!-- sql to call when connection is created | <new-connection-sql>some arbitrary sql</new-connection-sql> | --> | | <!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered | <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql> | --> | | <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> | | <type-mapping>Oracle9i</type-mapping> | | | </local-tx-datasource> | | | Does the pool for oracle DB conns is related with queueing feature(by this i mean the pool for hypersonic DB). Several times we have seen these 2 problems going hand in hand. Thanking in advance. Suds View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066589#4066589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066589 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
