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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-327:
----------------------------------------------

Yong Hao Gao <hgao at redhat.com> made a comment on [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653]

There are some non-serializable fields that caused the problem. When a JMS bridge is deployed and started and if it uses a local Connection Factory to create connections, the Connection Factory will have such fields stored. When a remote client looks up the same connection factory via JNDI, the factory won't get serialized because of those fields.

To workaround the client can use a different Connection Factory. I'll submit the fix soon.

Howard
                
> Remote JNDI is not working with a HornetQ-only JMS bridge
> ---------------------------------------------------------
>
>                 Key: WFLY-327
>                 URL: https://issues.jboss.org/browse/WFLY-327
>             Project: WildFly
>          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