Regarding the No ManagedConnection error in jboss-4.0.3SP1

[ottran75]

We are developing a application using Oracle 9i, Linux Environment ,
Jboss-4.0.3SP1

We are frequently getting the no managedconnection error.
We have closed all the connection etc properly and not only that we are monitoring the server to see for any open connection .
Please advise/ suggest ways by which we can rectify this error.
Your help will be highly useful for us.

Thanks
Ottran

[weston.price]

Getting the NoManagedConnections error is not necessarily a bad thing. It really just says that the pool needs to probably be tuned.

Please post your *-ds.xml file.

[ottran75]

Please find the oracle-ds.xml file



<local-tx-datasource>
<jndi-name>OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@url</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>USER</user-name>
Pswd

<min-pool-size>50</min-pool-size>
<max-pool-size>75</max-pool-size>
<idle-timeout-minutes>1</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>

[jaikiran]

<min-pool-size>50</min-pool-size>
<max-pool-size>75</max-pool-size>

Thats a good enough pool size. What does your application do? Does it heavily use connections. How long are these connections kept open? If i remember correctly, using the jmx-console there is a way to find out the number of connection currently in use, for your datasource. Have you checked this current connection count when this exception occurs?