[
https://issues.jboss.org/browse/WFLY-327?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on WFLY-327:
----------------------------------------------
Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug
912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653]
Issue in the previous comment seems to be related to the way how connection factory is
deployed and looked up from JNDI.
Client and JMS bridge are using the same connection factory. When JMS bridge uses this
connection factory first then JMS client gets this NotSerializableException.
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