During the initialization of an Oracle XA datasource in JBoss EAP, the oracle.net.jndi.LDAPSSLSocketFactory class is being searched for in the IronJacamar module's classloader instead of the Oracle driver module's classloader.

This results in a ClassNotFoundException and prevents the XA datasource from functioning as expected.

This behavior suggests that the TCCL is not being appropriately set during the process. While a non-XA datasource using the same Oracle driver works correctly, the XA datasource fails due to this classloading issue.

The correct classloader (associated with the Oracle driver module) should be used when initializing the XA datasource to ensure all required classes are loaded properly. The TCCL should be explicitly set to the Oracle driver module’s classloader during this process.

A workaround does exist for this issue, which involves manually adding Oracle-specific dependencies to the IronJacamar module, which is not a suitable long-term fix.