Hi,
Arrgh! Accidentally hit the send button before I included this info..
Sorry. I've got an simple pub/sub app that I'll forward along if I can
reliably recreate the issue.
JDK: 1.5.0_14
ActiveMQ 4.1.1
OS: RHEL 5.
<transportConnectors>
<transportConnector name="openwire"
uri="tcp://zend01.dev.manhunt.net:61616" discoveryUri="multicast://def
ault"/>
</transportConnectors>
<networkConnectors>
<!-- by default just auto discover the other brokers -->
<networkConnector name="default-nc" uri="multicast://default"/>
</networkConnectors>
Thanks again,
S.
------ Forwarded Message
From: Scott Frazier <[EMAIL PROTECTED]>
Date: Tue, 04 Mar 2008 21:10:26 -0500
To: "users@activemq.apache.org" <users@activemq.apache.org>
Conversation: NPE in DemandForwardingBridge
Subject: NPE in DemandForwardingBridge
Hi,
I'm a recent adopter of ActiveMQ 4.1.1 in a simple, two instance
"network of brokers" configuration. I'm being burned by the
DemandForwardingBridge throwing an internal NPE and dying. I believe this is
the same issue as outlined in AMQ-1455.
Has anyone else been burned by this and if so, any advice or
workarounds? I can probably switch to a master/slave config in development,
but I'm definitely going to need interest-based routing at some point as we
add additional physical facilities.
Thanks in advance,
S.
------ End of Forwarded Message
