Anthony Vanelverdinghe created WFLY-6807: -------------------------------------------- Summary: XA Datasource wizard does not add <xa-datasource-class> element in configuration when using deployed JDBC driver Key: WFLY-6807 URL: https://issues.jboss.org/browse/WFLY-6807 Project: WildFly Issue Type: Bug Components: Web Console Affects Versions: 10.0.0.Final Reporter: Anthony Vanelverdinghe Assignee: Harald Pehl When creating an Oracle XA Datasource using the wizard in the Administration Console, and specifying a JDBC driver which was uploaded as a new deployment, the wizard does not add the element <xa-datasource-class> in the datasource configuration, which causes Test Connection to fail with: "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid", and the stack trace below. The wizard ought to either ask to provide the class name, or inspect the .jar to find it by itself (I'd assume most JDBC drivers come with at most 1 implementation of javax.sql.XADataSource). 11:24:01,853 ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: java:/XAOracleDS (IJ0310 84: Unable to create connection): javax.resource.ResourceException: IJ031084: Unable to create connection at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:509) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1$1.run(XAManagedConnectionFactory.java:395) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1$1.run(XAManagedConnectionFactory.java:392) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1.run(XAManagedConnectionFactory.java:391) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory$1.run(XAManagedConnectionFactory.java:388) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:387) at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.open(XAResourceRecoveryImpl.java:355) at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:193) at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:519) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:185) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:747) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375) Caused by: javax.resource.ResourceException: IJ031101: XADataSourceClass is undefined at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:621) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:492) ... 15 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)