2 Replies Latest reply on Nov 4, 2002 2:44 PM by soeiro

    How to find out what is behind a transaction Exception?

    soeiro

      Hello All

      Is there any way (log file, message, debug code, whatever) fo find out the real cause for a transaction Excpetion at commit time?

      I have a complex scenario in which every now and then we are faced with this kind of erros:

      2002-11-01 14:15:42,886 WARN [org.jboss.tm.TxCapsule] XAException: tx=XidImpl [FormatId=257, GlobalId=R1SV//10, 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)
      ...

      The problem is that we have no clue to the reason of the failure. We now have a setup with about 68 Session Beans plus 62 Entity Beans, all using CMT, CMP and CMR. It is just impossible to find out what went wrong without at least a clue...Isn't there a message somewhere of the kind "invalid column name, unique error, etc"?

      Thanks for your help,

      Luis JB Soeiro

        • 1. Re: How to find out what is behind a transaction Exception?

          server/default/log/server.log

          You change the logging in

          server/default/conf/log4j.xml

          Regards,
          Adrian

          • 2. Re: How to find out what is behind a transaction Exception?
            soeiro

            Adrian

            I've already set the logging mode to TRACE and I've also enabled it to the transaction and sql related trees. I can see all SQL code, beginning and ending of transaction and so forth. However, there is no further message than "SQL Error". It would be nice to know a little more, for example, the original DB error message.

            I also would like to know what bean caused an EJB-QL error. We have to go trhough all finder methods in all beans whenever something cames up. Is there any easier way to do it (for exemple, enabling some kind of information to the error location in the XML file).

            Thanks y'all for your help,

            Luís JB