-
Bug
-
Resolution: Done
-
Major
-
14.0.0.Final
-
None
If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>):
<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>
then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with null. See JNDI view:
[standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view ... "jms" => { "class-name" => "javax.naming.Context", "children" => { "RemoteConnectionFactory" => { "class-name" => "java.lang.Object", "value" => "null" },
Result:
If EE deployment looks up or injects such CF then it fails on NullPointerException.
- is cloned by
-
JBEAP-15806 Look up of RemoteConnectionFactory with discovery-group is null
- Closed