Bug 991380 - Resource-adapter archive with ironjacamar.xml, containing recovery configuration isn't registered for recovery
Summary: Resource-adapter archive with ironjacamar.xml, containing recovery configurat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JCA
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.2.0
Assignee: Jesper Pedersen
QA Contact: Vladimir Rastseluev
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: 999522
TreeView+ depends on / blocked
 
Reported: 2013-08-02 09:53 UTC by Vladimir Rastseluev
Modified: 2014-01-13 00:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:15:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
generic-jms-ra.rar (125.46 KB, application/x-rar)
2013-08-02 09:53 UTC, Vladimir Rastseluev
no flags Details
module (593.90 KB, application/zip)
2013-08-02 09:58 UTC, Vladimir Rastseluev
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBJCA-1073 0 Critical Closed Resource adapter needs an explicit <xa-pool> in order to enable XA functionality 2017-04-26 19:25:47 UTC

Description Vladimir Rastseluev 2013-08-02 09:53:53 UTC
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:

Comment 1 Vladimir Rastseluev 2013-08-02 09:58:52 UTC
Created attachment 781904 [details]
module

Comment 2 Jesper Pedersen 2013-08-28 19:12:41 UTC
Workaround: Add <xa-pool> element with f.ex. <min-pool-size>

Comment 3 JBoss JIRA Server 2013-08-29 12:50:15 UTC
Jesper Pedersen <jpederse> updated the status of jira JBJCA-1073 to Resolved

Comment 4 JBoss JIRA Server 2013-08-29 13:34:54 UTC
Jesper Pedersen <jpederse> updated the status of jira JBJCA-1073 to Closed

Comment 5 Jesper Pedersen 2013-09-05 15:09:45 UTC
Fixed in EAP 6.2.0

Comment 7 Vladimir Rastseluev 2013-09-11 07:00:56 UTC
Verified on EAP 6.2.0 ER1


Note You need to log in before you can comment on or make changes to this bug.