SQLException not propagated during connection manager commit

[tkale]

Version: jboss-3.0.2_tomcat-4.0.4
DB: Oracle 8i (8.1.7.1.0)

I'm trying to create several CMP entity beans with CMR. We are using deferred constraints, and I suspect that one of the deferred constraints is the cause of my problem.

However, I can't tell what the specifics are on the SQLException that is being thrown by the connection manager during the commit. Any ideas on how I can get the detail message on the SQLException?

2002-10-02 21:11:56,674 WARN [org.jboss.tm.TxCapsule] XAException: tx=XidImpl [FormatId=257, GlobalId=tkale//25, BranchQual=] errorCode=XA_UNKNOWN(0)
javax.transaction.xa.XAException: could not commit local txjavax.resource.ResourceException: SQLException
at org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener.commit(LocalTxConnectionManager.java:563)
at org.jboss.tm.TxCapsule.commitResources(TxCapsule.java:1682)
at org.jboss.tm.TxCapsule.commit(TxCapsule.java:361)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:73)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:201)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203)
at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:313)
at org.jboss.ejb.Container.invoke(Container.java:720)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:370)
at java.lang.reflect.Method.invoke(Native Method)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:236)
at sun.rmi.transport.Transport$1.run(Transport.java:147)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:143)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:479)

[tkale]

The exception in my previous post was caused by a deferred constraint error.

Two things I think are wrong with JBoss' connection manager's behavior:

1. The failed commit should not be a warning, it should propagate the exception so the application can take action.

2. The detail message (and perhaps the stack trace) of the underlying SQLException should be logged.

[tkale]

I found the following open bug in SourceForge for JBoss that covers the problem with the commit failure not being propagated:

[ 575966 ] JCA - commit failure not reported