[jboss-jira] [JBoss JIRA] (AS7-6549) Remote JNDI is not working with a HornetQ-only JMS bridge

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767502#comment-12767502 ] 

RH Bugzilla Integration commented on AS7-6549:
----------------------------------------------

Nikoleta Ziakova <nziakova at redhat.com> made a comment on [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653]

It seems that JMS bridge can be now started:

12:38:05,216 INFO  [org.jboss.messaging] (ServerService Thread Pool -- 67) JBAS011610: Started JMS Bridge myBridge

However when trying to send messages to source queue producer gets exception:

12:38:30,956 ERROR [org.jboss.qa.hornetq.apps.clients.ProducerClientAck:114] Producer got exception and ended:
org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.NotSerializableException: org.hornetq.core.client.impl.ClientSessionFactoryImpl]
	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:79)
	at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:79)
	at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:83)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at org.jboss.qa.hornetq.apps.clients.ProducerClientAck.run(ProducerClientAck.java:79)
Caused by: java.io.NotSerializableException: org.hornetq.core.client.impl.ClientSessionFactoryImpl
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:891)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:585)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
	at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
	at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
	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$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: an exception which occurred:
	in field factories
	in field serverLocator
	in object org.hornetq.jms.client.HornetQXAConnectionFactory at 7920f96a

It is possible to send messages to the same queue while JMS Bridge is not connected. The exception occurs only when JMS Bridge is started.

See configurations and logs in attachment.
                
> Remote JNDI is not working with a HornetQ-only JMS bridge
> ---------------------------------------------------------
>
>                 Key: AS7-6549
>                 URL: https://issues.jboss.org/browse/AS7-6549
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 8.0.0.Alpha1
>
>
> The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes.
> However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira