-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.0.0.ER7
-
None
If connection factory is with JGroups discovery group like:
<discovery-group name="dg-group1" refresh-timeout="10000" jgroups-channel="udp" jgroups-stack="udp"/> ... <connection-factory name="JGroupsConnectionFactory" entries="java:jboss/exported/jms/JGroupsConnectionFactory" discovery-group="dg-group1"/>
then remote JNDI lookup fails with:
org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.NotSerializableException: org.apache.activemq.artemis.api.core.ChannelBroadcastEndpointFactory@4d267ed4not serializable] at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49) at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104) at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95) at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276) at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:137) at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.jboss.jms.client.TestProducerSimple.startClient(TestProducerSimple.java:69) at org.jboss.jms.client.TestProducerSimple.main(TestProducerSimple.java:39) Caused by: java.io.NotSerializableException: org.apache.activemq.artemis.api.core.ChannelBroadcastEndpointFactory@4d267ed4not serializable at org.apache.activemq.artemis.uri.JGroupsSchema.internalNewURI(JGroupsSchema.java:70) at org.apache.activemq.artemis.uri.JGroupsSchema.internalNewURI(JGroupsSchema.java:33) at org.apache.activemq.artemis.utils.uri.URISchema.newURI(URISchema.java:46) at org.apache.activemq.artemis.utils.uri.URIFactory.createSchema(URIFactory.java:78) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.toURI(ActiveMQConnectionFactory.java:119) at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.writeExternal(ActiveMQConnectionFactory.java:83) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:842) at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58) at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111) at org.jboss.naming.remote.protocol.v1.Protocol$1$2.write(Protocol.java:138) at org.jboss.naming.remote.protocol.v1.WriteUtil.write(WriteUtil.java:61) at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:128) at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: an exception which occurred: in object org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory@41e2b36d
- is related to
-
ENTMQBR-2146 Sync JGroups version between AMQ 7.2 and EAP 7.2 aka NoSuchMethodError: org.jgroups.JChannel.setReceiver when using JMS standalone client with jboss-client
- Closed
-
JBEAP-15733 NoSuchMethodError: org.jgroups.JChannel.setReceiver when using JMS standalone client with jboss-client
- Closed
-
JBEAP-16398 Release Notes - Deprecate use of discovery groups with JGroups in standalone JMS client in Release Notes
- Closed