-
1. Re: JBoss 5.1.2 support xa-datasource?
Hi Surendra,
Unfortunately you have not provided enough information to help diagnose the fault. It certainly doesn't look like a transaction manager issue. It looks like you are using a driver that is incompatible with the version of the app server you are using.
If you are reporting this against an EAP version I would encourage you to use any commercial support entitlements you may have. If you are reporting this against the community version of the app server I would encourage you to try to replicate this on WildFly and if you have an issue create a discussion on the WildFly forums. They will need at least:
1. Your config
2. Version of your driver
3. The stack trace
Thanks for your interest,
Tom
-
2. Re: JBoss 5.1.2 support xa-datasource?
Hi Tom,
Please find more details as per below:
xa-datasource properties
<xa-datasource-property name="oracle.net.encryption_client">required</xa-datasource-property>
<xa-datasource-property name="oracle.net.encryption_types_client">(RC4_256)</xa-datasource-property>
Error stdout.log
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Could not find accessor on XADataSource: ; - nested throwable: (java.lang.NoSuchMethodException: oracle.jdbc.xa.client.OracleXADataSource.setOracle.net.encryption_types_client(java.lang.String)))
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:474)
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:418)
at org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment.createManagedConnection(ManagedConnectionFactoryDeployment.java:1125)
at org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment.open(ManagedConnectionFactoryDeployment.java:775)
at org.jboss.resource.connectionmanager.ManagedConnectionFactoryDeployment.getXAResources(ManagedConnectionFactoryDeployment.java:565)
at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:703)
at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:201)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:799)
at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:412)
Caused by: org.jboss.resource.JBossResourceException: Could not find accessor on XADataSource: ; - nested throwable: (java.lang.NoSuchMethodException: oracle.jdbc.xa.client.OracleXADataSource.setOracle.net.encryption_types_client(java.lang.String))
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:621)
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:458) -
3. Re: JBoss 5.1.2 support xa-datasource?
Hi Surendra,
As I say, this isn't a JBoss Transactions issue so I can't really help you too much. I think you need to ask over here: IronJacamar
I mentioned before but to remind you that if you are using the commercial JBoss EAP product you should use your support entitlements as the version of the app server you are using is really old and many enhancements are available in more current versions.
Tom
-
4. Re: JBoss 5.1.2 support xa-datasource?
If you aren't using JBoss EAP - upgrade to WildFly 8.1 and try again
-
5. Re: JBoss 5.1.2 support xa-datasource?
Hi All,
We are using jboss-eap-5.1.2 and now can not upgrade to WildFly 8.1. Just want to jboss-eap-5.1.2 support xa-datasource, if yes what we need to do for that.
Thanks
-
6. Re: JBoss 5.1.2 support xa-datasource?
Hi Surendra,
Thank you for clarifying that you are using EAP. To answer your question on what you need to do, I suggest you speak to the contact on your support contract and they will be able to assist you better.
Tom