[jboss-jira] [JBoss JIRA] (WFLY-1968) Connection factory isn't activated in generic-jms-ra.rar resource adapter after server reload with jts transactions mode set.

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-1968:
-----------------------------------

    Component/s: JCA

    
> Connection factory isn't activated in generic-jms-ra.rar resource adapter after server reload with jts transactions mode set. 
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1968
>                 URL: https://issues.jboss.org/browse/WFLY-1968
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA
>    Affects Versions: 8.0.0.Alpha4
>            Reporter: Vladimir Rastseluev
>            Assignee: Stefano Maestri
>             Fix For: 9.0.0.CR1
>
>
> Description of problem:
> Start server with configured resource adapter and deployed generic-jms-ra.rar. After server started we can see registered and bound connection factory.
> Then we add some changes to the server to set up jts transactions mode by CLI utility. Reload the server. Connection factory isn't registered.
> 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.configure resource-adapters subsystem this way:
> <subsystem xmlns="urn:jboss:domain:resource-adapters:1.1">
>             <resource-adapters>
>                 <resource-adapter id="generic-jms-ra.rar">
>                     <archive>
>                         generic-jms-ra.rar
>                     </archive>
>                     <transaction-support>XATransaction</transaction-support>
>                     <connection-definitions>
>                         <connection-definition class-name="org.jboss.resource.adapter.jms.JmsManagedConnectionFactory" jndi-name="java:/jms/QueueConnectionFactory" pool-name="CF" use-java-context="false">
>                             <config-property name="JndiParameters">
>                                 java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory;java.naming.provider.url=tcp://tibco01.mw.lab.eng.bos.redhat.com:7222
>                             </config-property>
>                             <config-property name="ConnectionFactory">
>                                 XAQCF
>                             </config-property>
>                             <security>
> 				<application/>
>                             </security>
> 			    <recovery>
> 			      <recover-credential>
> 				<user-name>tibco</user-name>
> 				<password>tibco</password>
> 			      </recover-credential>
> 			    </recovery>
>                         </connection-definition>
>                     </connection-definitions>
>                 </resource-adapter>
>             </resource-adapters>
>         </subsystem>
> 6. run server $JBOSS_HOME/bin/standalone.sh
> see - java:/jms/QueueConnectionFactory is registered
> 7. run $JBOSS_HOME/bin/cli.sh
> 8. execute commands in cli:
> -->/subsystem=jacorb/:write-attribute(name=transactions,value=on)
> -->/subsystem=transactions/:write-attribute(name=recovery-listener,value=true)
> -->/subsystem=transactions/:write-attribute(name=jts,value=true)
> -->:reload
> Actual results:
> connection factory java:/jms/QueueConnectionFactory isn't registered
> Expected results:
> connection factory java:/jms/QueueConnectionFactory is registered

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira