JDBC connection and several calls of the same session bean

[kocher]

Why JBoss allocates a new connection for each session call (within the single HTTP request processing - if it can be important)?
Code:
Session1 session = SessionBeanHelper.createSession1();
for(Iterator i = ...) {
session.doATransaction((TransactionData)i.next());
}
session.remove();

If cycle iterates more times than connection pool size limit then JBoss stops processing due it cannot allocate a connection.

[kocher]

JBoss versions: 3.0.0 (Tomcat), 3.0.2 (Jetty), 3.0.4 (Jetty)

[juhalindfors]

what are your transaction settings?

[kocher]

Details:
db - MSSQL
session is simple stateless session bean
<ejb-jar>
<enterprise-beans>

<ejb-name>Session1</ejb-name>
<local-home>test.Session1Home</local-home>
test.Session1
<ejb-class>test.Session1Bean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>

...
</enterprise-beans>
...
<assembly-descriptor>
<container-transaction>

<ejb-name>Session1</ejb-name>
<method-name>*</method-name>

</container-transaction>
...
</assembly-descriptor>
</ejb-jar>



<enterprise-beans>

<ejb-name>Session1</ejb-name>
<local-jndi-name>comp/ejb/Session1</local-jndi-name>
<configuration-name>Standard Stateless SessionBean</configuration-name>

</enterprise-beans>

[srouil]

Have you solved your problem? It looks like I am facing a similar one (exhausting the connection pool whith a combination of stateless session beans and CMP entity beans.

From you transaction configuration I can see that you omit the transaction attribute.

[juhalindfors]

what is the tx attribute for the session bean doTransaction method? In other words, is each doTransaction call executed within the same transaction or are they separate transactions?

[kocher]

> From you transaction configuration I can see that you
> omit the transaction attribute.
Oops
<trans-attribute>Required</trans-attribute>

And:
session.doATransaction
is called not within a transaction thus each call is a separated transaction. I think that JBoss creates transaction then calls the method and then commit transaction but does not close the connection (that should return to the connection pool).