[
https://issues.jboss.org/browse/WFLY-11290?page=com.atlassian.jira.plugin...
]
Miroslav Novak updated WFLY-11290:
----------------------------------
Steps to Reproduce:
Steps to reproduce:
{code}
git clone
git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout master
groovy
-DEAP_ZIP_URL=http://download.jboss.org/wildfly/14.0.1.Final/wildfly-14.0.1.Final.zip
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=RemoteBrokerTestCase#testConnectionFactoryWithDiscoveryGroup
-Deap7.org.jboss.qa.hornetq.apps.clients.version=7.2.0.CD14.CR2 | tee log
{code}
Look up of RemoteConnectionFactory with discovery-group is null
---------------------------------------------------------------
Key: WFLY-11290
URL:
https://issues.jboss.org/browse/WFLY-11290
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.0.Final
Reporter: Miroslav Novak
Assignee: ehsavoie Hugonnet
Priority: Major
If RemoteConnectionFactory is defined with discovery-group like (note that it's
defined directly in messaging subsystem, not in <server>...</server>):
{code}
<subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
<discovery-group name="dg-group1" jgroups-channel="ee"
jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/>
<connection-factory name="RemoteConnectionFactory"
discovery-group="dg-group1"
entries="java:jboss/exported/jms/RemoteConnectionFactory
java:/jms/RemoteConnectionFactory"/>
</subsystem>
{code}
then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with
{{null}}. See JNDI view:
{code}
[standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view
...
"jms" => {
"class-name" => "javax.naming.Context",
"children" => {
"RemoteConnectionFactory" => {
"class-name" => "java.lang.Object",
"value" => "null"
},
{code}
Result:
If EE deployment looks up or injects such CF then it fails on NullPointerException.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)