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 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 connection. If I create simplex connections between two
brokers, one with dynamicOnly="true", the other unspecified
(="false"), I get the same behavior as with my duplex
dynamicOnly="true" connection.
The 1542 issue above is the problem, but the posted fix is only
partial. I believe it should be reopened, and the fix should be to
copy all relevant networkConnection properties.
On 4/30/08, Rob Davies <[EMAIL PROTECTED]> wrote:
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 spurious subscriber causes messages to continue to be sent to
the
broker.
I'll create a Jira.
On 4/30/08, Rob Davies <[EMAIL PROTECTED]> wrote:
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 queue, and subscribe on another spoke. I
have
dynamicOnly="true" so when I kill the subscriber and bring it up
on
another spoke, the messages are delivered to the proper broker.
But with duplex="true" (and no other configuration change), the
death
of the subscriber doesn't seem to get recognized or propagated and
messages are still delivered to the dead subscriber's broker.
This is with the 5.1.0 snapshot posted on the Download page. I
haven't
tried with 5.0 as that has another issue with duplex and
networkTTL.
I checked Jira and didn't find anything similar, but I'm using an
intermediate release so maybe it's a known issue. Can anyone
confirm?
Thanks.
Looks like a new issue (well, one we didn't know about) to me -
can you
raise a jira?
cheers,
Rob
http://open.iona.com/ -Enterprise Open Integration
http://rajdavies.blogspot.com/
