Created attachment 781903 [details] generic-jms-ra.rar Description of problem: Deployed .rar with ironjacamar.xml inside. File ironjacamar.xml contains recovery element like: <recovery> <recover-credential> <user-name>tibco</user-name> <password>tibco</password> </recover-credential> </recovery> After deployment, a message appears in server.log : 11:36:20,589 WARN [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/jms/QueueConnectionFactory and this resource adapter really isn't registered in XA recovery process. Version-Release number of selected component (if applicable): EAP 6.1.1.ER4 generic resource adapter: https://github.com/jbertram/generic-jms-ra How reproducible: easy Steps to Reproduce: 1. add applied generic-jms-ra.rar file to the $JBOSS_HOME/standalone/deployments directory 2. unpack applied module and add it to $JBOSS_HOME/modules directory 3. update module.xml file from org.jboss.as.ee module, adding a new dependency: "<module name="com.tibco.tibjms"/>" 4. update $JBOSS_HOME/standalone/configuration/standalone.xml, adding global modules to <subsystem xmlns="urn:jboss:domain:ee:1.1">: <global-modules> <module name="com.tibco.tibjms" slot="main"/> <module name="org.jboss.common-core" slot="main"/> </global-modules> 5. run server $JBOSS_HOME/bin/standalone.sh Actual results: a message appears in server.log : 11:36:20,589 WARN [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/jms/QueueConnectionFactory Expected results: resource adapter really is registered in XA recovery process Additional info:
Created attachment 781904 [details] module
Workaround: Add <xa-pool> element with f.ex. <min-pool-size>
Jesper Pedersen <jpederse> updated the status of jira JBJCA-1073 to Resolved
Jesper Pedersen <jpederse> updated the status of jira JBJCA-1073 to Closed
Fixed in EAP 6.2.0
Verified on EAP 6.2.0 ER1