thx - looks like we aren't sending the configuration properties across
at all - will re-open AMQ-1542 and fix as soon as svn is back
cheers,
Rob
On 30 Apr 2008, at 18:44, sgm wrote:
Well, I found the real problem. I went back and looked at the 5.0.0
issue someone reported about duplex conne
Well, I found the real problem. I went back and looked at the 5.0.0
issue someone reported about duplex connections and networkTTL here
http://issues.apache.org/activemq/browse/AMQ-1542 and realized it's
the same problem.
It turns out the dynamicOnly property isn't being passed over the
duplex con
ah - ok - thx for investigating it further!
On 30 Apr 2008, at 17:29, sgm wrote:
Hi Rob - I did more testing and it seems that a duplex connection
creates an additional subscriber on the spoke's queue when messages
are routed there. So even though my subscriber is no longer active,
this spuriou
Hi Rob - I did more testing and it seems that a duplex connection
creates an additional subscriber on the spoke's queue when messages
are routed there. So even though my subscriber is no longer active,
this spurious subscriber causes messages to continue to be sent to the
broker.
I'll create a Jir
On 29 Apr 2008, at 23:23, sgm wrote:
I'm seeing a problem with dead subscribers not being
detected/propagated using duplex networkConnections.
Specifically, I've set up a hub/spoke arrangement with a central
broker (hub) and several remote brokers (spokes). On one spoke I
publish messages to a
