Error transaction no longer active, no further JDBC access allowed

Question

Hello
Our application uses WLS 6.0 SP2, TopLink 3.5.3, WebLogic JMS. A
(pooled) JMS driven message bean invokes other application components
(stateless session beans). Also, application components use JMS to send
messages. JMS and application (through TopLink) use the same JDBC
connection pool. TopLink connects through javax.sql.DataSource and
external transaction controller. 2PC transactions are required to
integrate JMS and TopLink DB access (see data source definition below).
All components run in a single JVM, there is not distributed transaction
between JVMs.
When pushing > 5 concurrent messages into the system I get an error that
somehow indicates TopLink access to a connection that is no longer
associated with a WebLogic transaction.
I can consistently reproduce this error with the Oracle thin, Oracle OCI
and WebLogic OCI JDBC drivers. It seems to occur independent from the
maximum number of connections in the pool (tested between 1 and 30).
Also, when serializing the message supply with a pause in between the
error does not seem to occur.
Has anybody seen this type of problem before?
Are there possibly known issues with the external transaction controller
integration?
Any help greatly appreciated.
Thanks,
Thomas
EXCEPTION [TOPLINK-4002] (3.5.3 JDK1.2):
TOPLink.Public.Exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: The transaction is no
longer active (status = Committing). No further JDBC access is allowed
within this transaction.
INTERNAL EXCEPTION: java.sql.SQLException: The transaction is no longer
active (status = Committing). No further JDBC access is allowed within
this transaction.
ERROR CODE: 0
### WebLogic config.xml ###
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="1"
MaxCapacity="15" Name="oraclePool"
Properties="user=wlpi20;password=wlpi20;dll=ocijdbc8;protocol=thin"
Targets="appserver"
URL="jdbc:oracle:thin:@10.3.209.35:1521:wcdevdb"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="com.bea.wlpi.TXDataSource" Name="TXDataSource"
PoolName="oraclePool" Targets="appserver"/>
<JMSJDBCStore ConnectionPool="oraclePool" Name="oraclePool"/>
### TopLink session/login setup for external transaction controller ###
DatabaseLogin login = project.getLogin();
login.setConnector(new TOPLink.Public.JNDI.JNDIConnector(
initialContext, jdbcDataSource));
login.setUserName(jdbcUser);
login.setPassword(jdbcPasswd);
ServerSession session = new ServerSession(project);
login.useExternalConnectionPooling();
login.useExternalTransactionController();
final String tmname = "weblogic/transaction/TransactionManager";
javax.transaction.TransactionManager transMgr =
(javax.transaction.TransactionManager)
initialContext.lookup(tmname);
JTSSynchronizationListener.setTransactionManager(transMgr);
session.setExternalTransactionController(
new TOPLink.Public.JTS.JTSExternalTransactionController());
logger.fine("registered external transaction controller");

Answer 1

Better to ask on a hibernate forum, but you seem to
be trying to reuse a closed transaction. If you have
auto-commit set to ttrue, try changing it to false,
the explicitly calling commit when you are done.Might be worth finding out why something is trying to use a closed transaction first, before changing your entire transaction management idiom, though