Blocking by too many (100) connections used

Question

Oracle9iAS (9.0.3.0.0) Containers for J2EE (build 020927.1699)
I have a container managed transaction and within it I get several connections from an emulated datasource. These connections are supposed to be created within the scope of the transaction and in fact they are.
The problem takes place when the transaction has many actions to perform and OrionCMTDataSource seems to block at 100. This is tested through the following command:
java -jar admin.jar ormi://localhost admin *** -application default -dataSourceInfoDataSource info:
com.evermind.sql.DriverManagerXADataSource/default/jdbc/xa/OracleXADS - cached:
4 used: 1 total: 5
com.evermind.sql.OrionPooledDataSource/default/jdbc/OraclePooledDS - cached: 0 u
sed: 0 total: 0
com.evermind.sql.OrionCMTDataSource/default/jdbc/OracleDS - cached: 0 used: 100
total: 100
Is there a limit of 100 connections defined anywhere?
Is it configurable?
Why does OC4J block if number 100 is reached?
Isn't ejb-location (which i'm using) not supposed to be pooled?
Any help would be appreciated. My data-source follows:
     <data-source
          class="com.evermind.sql.DriverManagerDataSource"
          name="OracleDS"
location="jdbc/OracleCoreDS"
          pooled-location="jdbc/OraclePooledDS"
          xa-location="jdbc/xa/OracleXADS"
          ejb-location="jdbc/OracleDS"
          connection-driver="oracle.jdbc.driver.OracleDriver"
username="1234"
password="1234"
url="jdbc:oracle:thin:@systelab.izasa.es:1521:matrix"
min-connections="5"
max-connections="10"
stmt-cache-size="200"
          inactivity-timeout="30"
     >
               <property name="cacheScheme" value="FIXED_WAIT_SCHEME"/>
     </data-source>
Thanks in advance.

Answer 1

1) Are you using ejb-location for your lookup? If
not, could you try that?Yes, I am always using ejb-location as was mentioned on the first message.
2) Could you try the non-emulated data source
instead?Ok. I've tried the non-emulated data source.
It forces me to remove the property from data-sources.xml:
<property name="cacheScheme" value="FIXED_WAIT_SCHEME"/>
Running the same blocking code with the non-emulated data source causes:
javax.ejb.NoSuchObjectLocalException: Session has timed out
at com.evermind.server.ejb.StatefulSessionEJBObject.throwLocalPassivisat
ionException(StatefulSessionEJBObject.java:213)
at RequestSession_StatefulSessionBeanWrapper2.getList(RequestSession_StatefulSessionBeanWrapper2.java:1508)
which is strange as there is no session timeout error when using the emulated data source.
Maybe some additional details about the bean implementation will help. The SFSB has a member which has a Connection member. This could be dangerous, but I see no problem with it as calls to the bean always force creating and closing a new connection (so, an open connection is maintained just within a single call to the bean).
Also, I do not understand the passivation exception. I see no need for the bean to be passivated immediately after call.
I also got dataSourceInfo after exception:
java -jar admin.jar ormi://localhost admin admin -application default -dataSourceInfo
DataSource info:
com.evermind.sql.OrionCMTDataSource/default/jdbc/OracleCoreDS - cached: 0 used: 0 total: 0
com.evermind.sql.DriverManagerXADataSource/default/jdbc/xa/OracleXADS - cached: 4 used: 1 total: 5
com.evermind.sql.OrionPooledDataSource/default/jdbc/OraclePooledDS - cached: 0 used: 0 total: 0
com.evermind.sql.OrionCMTDataSource/default/jdbc/OracleDS - cached: 0 used: 2 total: 2
I have performed an additional test on this issue. I changed SFSB for SLSB. I did this before, with emulated data source, and nothing changed. Different behaviour now:
***Creating new Instance of SessionBean
***Creating new Instance of SessionBean
***Creating new Instance of SessionBean
***Creating new Instance of SessionBean
javax.ejb.EJBException: Transaction was rolled back: javax.transaction.SystemException: com.evermind.transaction.MarshallingXAException: Error closing connection for this TX: calling setAutoCommit(true) is not allowed on a container-managed transactions Connection
at RequestSession_StatelessSessionBeanWrapper8.getList(RequestSession_StatelessSessionBeanWrapper8.java:1431)
I do not explicitly call setAutoCommit on my code, so I assume the call is implicit.
Getting dataSourceInfo again:
java -jar admin.jar ormi://localhost admin admin -application default -dataSourceInfoDataSource info:
com.evermind.sql.OrionCMTDataSource/default/jdbc/OracleCoreDS - cached: 0 used:0 total: 0
com.evermind.sql.DriverManagerXADataSource/default/jdbc/xa/OracleXADS - cached:1 used: 4 total: 5
com.evermind.sql.OrionPooledDataSource/default/jdbc/OraclePooledDS - cached: 0 used: 0 total: 0
com.evermind.sql.OrionCMTDataSource/default/jdbc/OracleDS - cached: 0 used: 8 total: 8
Thanks for help.
Modulab