I currently have not manipulated any transaction settings in my application (no transaction-related annotations and nothing in ejb-jar.xml). If I need to, could you point me in the right direction?
My simple test from my post just a few minutes ago does not use any other EJBs, but yet is able to reproduce the problem. So chaining EJB invokations together doesn't seem to have anything to do with the problem
My persistence.xml:
<persistence xmlns="
http://java.sun.com/xml/ns/persistence" version="1.0">
<persistence-unit name="application">
<jta-data-source>${jta-data-source}</jta-data-source>
<jar-file>common-entities-1.0-SNAPSHOT.jar</jar-file>
<jar-file>land-entities-1.0-SNAPSHOT.jar</jar-file>
<properties>
<property name="toplink.ddl-generation" value="create-tables"/>
</properties>
</persistence-unit>
</persistence>
The datasource settings in glassfish:
<jdbc-connection-pool allow-non-component-callers="false"
associate-with-thread="false"
connection-creation-retry-attempts="0"
connection-creation-retry-interval-in-seconds="10"
connection-leak-reclaim="false"
connection-leak-timeout-in-seconds="0"
connection-validation-method="auto-commit"
datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource"
fail-all-connections="false"
idle-timeout-in-seconds="300"
is-connection-validation-required="false"
is-isolation-level-guaranteed="false"
lazy-connection-association="false"
lazy-connection-enlistment="false"
match-connections="false"
max-connection-usage-count="0"
max-pool-size="32"
max-wait-time-in-millis="60000"
name="SalestaxPool"
non-transactional-connections="false"
pool-resize-quantity="2"
res-type="javax.sql.ConnectionPoolDataSource"
statement-timeout-in-seconds="-1"
steady-pool-size="8"
validate-atmost-once-period-in-seconds="0"
wrap-jdbc-objects="false">
BTW, thanks for the quick responses. Its very much appreciated.
[Message sent by forum member 'bhar99328' (bhar99328)]
http://forums.java.net/jive/thread.jspa?messageID=212162