Hi
We use GF 3.1.1 and Informix Innovator-C as database in a new project.
The codebase have run on a different Informix version for years.
We use container-managed transactions.
I THINK that Innovator does NOT support XA transactions (ie it does not
support distributed SQL
I have tried with javax.sql.ConnectionPoolDataSource as Resource Type wich
should give a local transaction with no luck.
JDBC driver is XA complient.
Is I read it GF is using a XA transaction to access the database and that is
not supported.
Is there any way to make GF not using XA ? Is it any way to have a non-xa
compliant database with GF ?
When I try to connect to the database I get the following stacktrace:
Datum/klockslag
- PC: 2012-01-19 15:41:57
Titel: Plis
Meddelande: java.rmi.RemoteException: Unable to complete container-managed
transaction.;
nested exception is:
javax.ejb.EJBException: Unable to complete
container-managed transaction.
Anropssekvens:
java.rmi.RemoteException: Unable to complete container-managed transaction.;
nested exception is:
javax.ejb.EJBException: Unable to complete container-managed
transaction.
at
com.sun.ejb.containers.BaseContainer.mapRemoteException(BaseContainer.java:2281)
at
com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:2077)
at
com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1990)
at
com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:213)
at
com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:123)
at $Proxy288.initUserInfo(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie.dispatchToMethod(ReflectiveTie.java:144)
at
com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:174)
at
com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:528)
at
com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:199)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1624)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1486)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:990)
at
com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:214)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:742)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.dispatch(CorbaMessageMediatorImpl.java:539)
at
com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.doWork(CorbaMessageMediatorImpl.java:2324)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:497)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:540)
Caused by: javax.ejb.EJBException: Unable to complete container-managed
transaction.
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:5125)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:4879)
at
com.sun.ejb.containers.StatefulSessionContainer.postInvokeTx(StatefulSessionContainer.java:1653)
at
com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:2039)
... 21 more
Caused by: javax.transaction.SystemException
at
com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:518)
at
com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:842)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:5114)
... 24 more
Caused by: javax.transaction.xa.XAException:
com.sun.appserv.connectors.internal.api.PoolingException:
javax.resource.spi.LocalTransactionException: Transactions not supported
at
com.sun.enterprise.resource.ConnectorXAResource.handleResourceException(ConnectorXAResource.java:115)
at
com.sun.enterprise.resource.ConnectorXAResource.resetAssociation(ConnectorXAResource.java:287)
at
com.sun.enterprise.resource.ConnectorXAResource.commit(ConnectorXAResource.java:128)
at
com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:501)
... 26 more
Versionsinformation:
Infra: 2.21.12016 2012-01-16 19:23
Java Runtime Environment: 1.6.0_29
PlisClient: 2.44.12017 2012-01-17 15:14
PlisLogin: 2.2.12016 2012-01-16 19:09
PlisServer: 2.16.12016 2012-01-16 18:27
PvLib: 2.49.12012 2012-01-12 17:20
appclient.security: 3.1.1
common-util: 3.1.1
config-api: 3.1.1
config-types: 1.1.6
connectors-internal-api: 3.1.1
connectors-runtime: 3.1.1
container-common: 3.1.1
deployment-common: 3.1.1
dol: 3.1.1
ejb-container: 3.1.1
ejb.security: 3.1.1
glassfish-api: 3.1.1
glassfish-naming: 3.1.1
internal-api: 3.1.1
jta: 3.1.1
jts: 3.1.1
kernel: 3.1.1
orb-connector: 3.1.1
orb-iiop: 3.1.1
security: 3.1.1
ssl-impl: 3.1.1
transaction-internal-api: 3.1.1
--
[Message sent by forum member 'plis']
View Post: http://forums.java.net/node/882841