0 Replies Latest reply on Apr 5, 2003 2:43 PM by samart

    Sybase: SET CHAINED command not allowe

    samart Newbie

      Hi, please help, i'm really at the end of my ropes on this one. i'm trying to move my whole dev group to jboss, and then i cant even move my own app over!! This is the only thing in our way.

      i'm consistently getting these errors after moving my app from Weblogic to Jboss. i've tried jboss 3.0.1 - 3.0.6.

      I can run the same query a number of times, then on the 3rd or so query, the dreaded SET CHAINED not allowed pops up. i can repeat that pattern consitently. i've dug through all my db code (again), and cannot find anything wrong. i'm not explicity calling con.setAutoCommit/getAutoCommit myself anywhere.

      any help would be greatly appreciated, thanks!
      -Trevor

      com.sybase.jdbc2.jdbc.SybSQLException: SET CHAINED command not allowed within multi-
      statement transaction.

      AND

      14:26:13,313 WARN [TxCapsule] XAException: tx=XidImpl [FormatId=257, GlobalId=FWRGNB//15,
      BranchQual=] errorCode=XA_UNKNOWN(0)
      javax.transaction.xa.XAException: wrong xid in commit: expected: null, got: XidImpl [Forma
      tId=257, GlobalId=FWRGNB//15, BranchQual=1]
      at org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEv
      entListener.commit(LocalTxConnectionManager.java:548)
      at org.jboss.tm.TxCapsule.commitResources(TxCapsule.java:1714)
      at org.jboss.tm.TxCapsule.commit(TxCapsule.java:393)
      at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:73)
      at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.jav
      a:251)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:92)
      at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204)
      at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:3