Bugs item #690506, was opened at 2003-02-21 05:28
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=690506&group_id=22866

Category: JBossTX
Group: v3.2
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Marc Prud'hommeaux (mprudhom)
>Assigned to: David Jencks (d_jencks)
Summary: 3.2.0RC2 xa_start error -8 with SQLServer

Initial Comment:
When attempting to commit an XA transaction using
SQLServer (using the MS driver, configured using the
mssql-xa-ds.xml DS configured in the examples), it
works fine the first time. The second time, it throws
"javax.transaction.xa.XAException:
[Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]xa_start (0) returns -8".

According to section 4.5 of the X/Open XA
specification, -8 indicates "the XID already exists",
which indicates that JBoss may be re-using XIDs
inappropriately.

The exact same code worked for JBoss 3.2.0 beta 3.


System info:

[chance mprudhom]$ java -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.3.1-root_1.3.1_020714-12:46)
Java HotSpot(TM) Client VM (build 1.3.1_03-69, mixed mode)
[chance mprudhom]$ uname -a
Darwin chance.local. 6.4 Darwin Kernel Version 6.4: Wed
Jan 29 18:50:42 PST 2003;
root:xnu/xnu-344.26.obj~1/RELEASE_PPC  Power Macintosh
powerpc

Stack trace:

19:29:19,487 WARN  [TransactionImpl] XAException:
tx=TransactionImpl:XidImpl [FormatId=257,
GlobalId=chance.local.//8, BranchQual=]
errorCode=XAER_RMERR
javax.transaction.xa.XAException: [Microsoft][SQLServer
2000 Driver for JDBC][SQLServer]xa_start (0) returns -8
        at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown
Source)
        at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResource.start(Unknown
Source)
        at
com.microsoft.jdbcx.base.BaseXAResource.start(Unknown
Source)
        at
org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.start(XAManagedConnection.java:110)
        at
org.jboss.tm.TransactionImpl.startResource(TransactionImpl.java:1137)
        at
org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:624)
        at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConnectionManager.java:461)
        at
org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:359)
        at
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:546)
        at
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:837)
        at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102)
        at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(DataSourceConnector.java:61)
        at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFactory.java:179)
        at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfiguration.java:336)
        at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassInternal(JDBCPersistenceManagerFactory.java:454)
        at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(JDBCPersistenceManagerFactory.java:337)
        at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListener.java:53)
        at
javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
        at
com.solarmetric.kodo.runtime.AllFieldTypesTest.<clinit>(AllFieldTypesTest.java)
        at
XAEnvironmentTest.testXATransaction(XAEnvironmentTest.java:99)
        at
XAEnvironmentTest.testXATransaction(XAEnvironmentTest.java:72)
        at
XAEnvironmentTest.start(XAEnvironmentTest.java:323)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
        at $Proxy11.start(Unknown Source)
        at
org.jboss.system.ServiceController.start(ServiceController.java:392)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
        at $Proxy5.start(Unknown Source)
        at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:231)
        at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:827)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:612)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
        at $Proxy7.deploy(Unknown Source)
        at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:404)
        at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:545)
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:195)
        at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:268)
        at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
        at $Proxy0.start(Unknown Source)
        at
org.jboss.system.ServiceController.start(ServiceController.java:392)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
        at $Proxy5.start(Unknown Source)
        at
org.jboss.deployment.SARDeployer.start(SARDeployer.java:231)
        at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:827)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:612)
        at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:596)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
        at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
        at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
        at $Proxy6.deploy(Unknown Source)
        at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:332)
        at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:239)
        at org.jboss.Main.boot(Main.java:155)
        at org.jboss.Main$1.run(Main.java:393)
        at java.lang.Thread.run(Thread.java:491)


----------------------------------------------------------------------

>Comment By: David Jencks (d_jencks)
Date: 2003-02-25 02:55

Message:
Logged In: YES 
user_id=60525

OK, I'm closing it.  Who is not reporting the exception? 3.2 rc2 should announce all 
exceptions somehow to your application, even if wrapped in several layers.

It is quite possible jboss is reusing xid numbers.  There is no facility to avoid this 
until jboss 4.

----------------------------------------------------------------------

Comment By: Marc Prud'hommeaux (mprudhom)
Date: 2003-02-24 22:31

Message:
Logged In: YES 
user_id=33016

Actually, I think this is user error on my part; an
underlying SQL exception occured and was not being reported.
Recommend that this bug be closed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=690506&group_id=22866


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to