[jboss-jira] [JBoss JIRA] (WFLY-2469) Upgrade to HornetQ 2.4.0.CR1
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Wed Nov 13 05:38:06 EST 2013
[ https://issues.jboss.org/browse/WFLY-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923098#comment-12923098 ]
RH Bugzilla Integration commented on WFLY-2469:
-----------------------------------------------
Jeff Mesnil <jmesnil at redhat.com> made a comment on [bug 1029836|https://bugzilla.redhat.com/show_bug.cgi?id=1029836]
Description of problem:
If an error occurs and the JMS bridge tries to reconnect to the JMS provider to look up the JMS resources from its FailureHandler, it fails with the exception:
10:37:02,546 INFO [org.hornetq.jms.server] (pool-3-thread-3) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 1,000 ms
10:37:03,547 WARN [org.hornetq.jms.server] (pool-3-thread-3) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.apache.qpid.jndi.PropertiesFileInitialContextFactory from classloader ModuleClassLoader for Module "org.hornetq:main" from local module loader @ac44b88 (finder: local module finder @5d3ad33d (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base))
at org.jboss.as.naming.InitialContextFactoryBuilder.createInitialContextFactory(InitialContextFactoryBuilder.java:64)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:681) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.init(InitialContext.java:240) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.<init>(InitialContext.java:214) [rt.jar:1.6.0_24]
at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1222) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1460) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2000(JMSBridgeImpl.java:83) [hornetq-jms-server.jar:]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2049) [hornetq-jms-server.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
How reproducible:
Always
Steps to Reproduce:
1. run a jms-bridge with a JMS provider loaded from a module
2. disconnect the network to make the jms-bridge fails
3. reconnect the network. The jms-bridge will handle the failure and reconnects to the JMS provider
Actual results:
The jms-bridge FailureHandler is not able to load the JMS provider classes.
Expected results:
The jms-bridge FailureHandler must be able to load the JMS provider classes from the module specified when the jms-bridge is added.
> Upgrade to HornetQ 2.4.0.CR1
> ----------------------------
>
> Key: WFLY-2469
> URL: https://issues.jboss.org/browse/WFLY-2469
> Project: WildFly
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 8.0.0.CR1
>
>
> HornetQ 2.4.0.CR1 depends on Netty 4.0.x versions that broke compatibility with Netty 3.x
--
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
More information about the jboss-jira
mailing list