-
1. Re: JDBC connection and several calls of the same session be
kocher Feb 4, 2003 11:56 PM (in response to kocher)JBoss versions: 3.0.0 (Tomcat), 3.0.2 (Jetty), 3.0.4 (Jetty)
-
2. Re: JDBC connection and several calls of the same session be
juhalindfors Feb 5, 2003 10:08 AM (in response to kocher)what are your transaction settings?
-
3. Re: JDBC connection and several calls of the same session be
kocher Feb 10, 2003 3:35 AM (in response to 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> -
4. Re: JDBC connection and several calls of the same session be
srouil Feb 12, 2003 7:30 AM (in response to kocher)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. -
5. Re: JDBC connection and several calls of the same session be
juhalindfors Feb 12, 2003 8:37 AM (in response to kocher)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?
-
6. Re: JDBC connection and several calls of the same session be
kocher Feb 16, 2003 11:51 PM (in response to 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).