[jboss-jira] [JBoss JIRA] (WFLY-10835) Connection factory with discovery-group doesn't work
ehsavoie Hugonnet (JIRA)
issues at jboss.org
Tue Aug 14 12:12:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619036#comment-13619036 ]
ehsavoie Hugonnet commented on WFLY-10835:
------------------------------------------
The serverside issue:
18:11:09,711 ERROR [stderr] (default task-2) java.io.NotSerializableException: org.wildfly.extension.messaging.activemq.broadcast.CommandDispatcherBroadcastEndpointFactory at 556a2e52not serializable
18:11:09,712 ERROR [stderr] (default task-2) at org.apache.activemq.artemis at 1.5.5.jbossorg-012//org.apache.activemq.artemis.uri.JGroupsSchema.internalNewURI(JGroupsSchema.java:68)
18:11:09,712 ERROR [stderr] (default task-2) at org.apache.activemq.artemis at 1.5.5.jbossorg-012//org.apache.activemq.artemis.uri.JGroupsSchema.internalNewURI(JGroupsSchema.java:34)
18:11:09,713 ERROR [stderr] (default task-2) at org.apache.activemq.artemis.journal at 1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.uri.URISchema.newURI(URISchema.java:38)
18:11:09,713 ERROR [stderr] (default task-2) at org.apache.activemq.artemis.journal at 1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.uri.URIFactory.createSchema(URIFactory.java:86)
18:11:09,713 ERROR [stderr] (default task-2) at org.apache.activemq.artemis at 1.5.5.jbossorg-012//org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.toURI(ActiveMQConnectionFactory.java:123)
18:11:09,714 ERROR [stderr] (default task-2) at org.apache.activemq.artemis at 1.5.5.jbossorg-012//org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.writeExternal(ActiveMQConnectionFactory.java:91)
18:11:09,714 ERROR [stderr] (default task-2) at org.jboss.marshalling.river at 2.0.5.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:908)
18:11:09,714 ERROR [stderr] (default task-2) at org.jboss.marshalling at 2.0.5.Final//org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)
18:11:09,715 ERROR [stderr] (default task-2) at org.jboss.marshalling at 2.0.5.Final//org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)
18:11:09,716 ERROR [stderr] (default task-2) at org.wildfly.naming-client at 1.0.9.Final//org.wildfly.naming.client.remote.RemoteServerTransport.writeSuccessResponse(RemoteServerTransport.java:461)
18:11:09,716 ERROR [stderr] (default task-2) at org.wildfly.naming-client at 1.0.9.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:192)
18:11:09,716 ERROR [stderr] (default task-2) at org.wildfly.naming-client at 1.0.9.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:106)
18:11:09,717 ERROR [stderr] (default task-2) at org.jboss.remoting at 5.0.8.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
18:11:09,717 ERROR [stderr] (default task-2) at org.jboss.remoting at 5.0.8.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
18:11:09,717 ERROR [stderr] (default task-2) at org.jboss.threads at 2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
18:11:09,717 ERROR [stderr] (default task-2) at org.jboss.threads at 2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
18:11:09,717 ERROR [stderr] (default task-2) at org.jboss.threads at 2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
18:11:09,717 ERROR [stderr] (default task-2) at org.jboss.threads at 2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
18:11:09,717 ERROR [stderr] (default task-2) at java.base/java.lang.Thread.run(Thread.java:844)
> Connection factory with discovery-group doesn't work
> ----------------------------------------------------
>
> Key: WFLY-10835
> URL: https://issues.jboss.org/browse/WFLY-10835
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 13.0.0.Final
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: server-trace.log, standalone-full-ha.xml
>
>
> Jms client can not use remote connection factory defined as follows
> {noformat}
> <discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" discovery-group="dg-group1" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
> {noformat}
> Following exception is thrown on client
> {noformat}
> Exception in thread "main" java.lang.RuntimeException: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at client.ProducerJms11.sendMessages(ProducerJms11.java:67)
> at client.Producer.run(Producer.java:34)
> at client.Producer.sendAllSync(Producer.java:25)
> at client.ProducerJms11.main(ProducerJms11.java:14)
> Caused by: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:261)
> at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
> at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
> at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
> at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at client.ProducerJms11.sendMessages(ProducerJms11.java:43)
> ... 3 more
> Caused by: java.io.EOFException: Read past end of file
> at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
> at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUnsignedByte(BlockUnmarshaller.java:258)
> at org.jboss.marshalling.river.BlockUnmarshaller.readInt(BlockUnmarshaller.java:296)
> at org.jboss.marshalling.river.BlockUnmarshaller.readUTF(BlockUnmarshaller.java:326)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.readExternal(ActiveMQConnectionFactory.java:186)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1414)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
> ... 15 more
> Caused by: an exception which occurred:
> in object of type org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
> {noformat}
> It fails on attempt to look up RemoteCF
> {noformat}
> ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(ClientDefaults.CONNECTION_FACTORY);
> {noformat}
> Same scenario with connector works well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list