Status: Verified (View Workflow)
Affects Version/s: 7.1.0.ER3
Fix Version/s: 7.1.0.CR1
Steps to Reproduce:
The issue was hit with EAP version fb15909332d951460eea0114afd7852587b38d9b
The issue was hit with EAP version fb15909332d951460eea0114afd7852587b38d9b Build and zip the EAP. Run following commands: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=file: ///path/to/your/custom/build PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=RemoteJcaTestCase#testRemoteJcaWihtDefaultJGroupsCluster -DfailIfNoTests= false -Deap=7x | tee log
- Build and zip the EAP.
- Run following commands:
Git Pull Request:
- There are 4 EAP servers.
- Servers 1, 3 are in cluster. They hold messages and they will be referenced in this text as JMS servers.
- Servers 2, 4 are not in cluster. They have RA configured to connect to servers 1 and 3 using discovery-group, which uses JGroups. They have MDBs which resend messages from InQueue to OutQueue. Servers 2, 4 will be referenced in this text as MDB servers.
Expectation: MDBs on MDB servers are able to discover and conenct to JMS servers.
Reality: During activation of resource adapter on MDB servers, NPE is thrown.
Customer impact: Resource adapter cannot be configured to dynamically discover JMS servers.
This is regression against 7.0.z.
This issue wasn't hit before, because with EAP 7.1.0.ER3 the server did not start with this configuration. See
JBEAP-12526 for details.
Detail description of issue
The following NPE arises when MDBs on MDB servers tries to connect to JMS servers via pooled-connection-factory configured to use JGroups for discovery.