activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Yaussy (JIRA)" <>
Subject [jira] Commented: (AMQ-643) maxInactivityDuration does not seem to work properly
Date Thu, 23 Mar 2006 16:18:26 GMT
    [ ] 

Kevin Yaussy commented on AMQ-643:

I'm very happy with the eviction policy features.  We will make *extensive* use of that (btw,
we may want to implement an eviction  policy at some point - any way to do that ?).  However,
I can raise a feature request for the subscription dropping.

One thing I forgot to mention in my comment above is that the broker networkConnector url
config changed again.  You now have to explicitly put on failover if you want broker-to-broker
connections to use failover.  That dropped off at one point (I was trying to find where you
and I conversed about that - it was some other JIRA entry), where you would get double failover
transport decorators, thus causing problems with shutdown.  You said that static would do
the same thing.

Anyway, not a big deal, but I believe you had updated some documentation regarding this. 
So, you might want to revisit that again.

> maxInactivityDuration does not seem to work properly
> ----------------------------------------------------
>          Key: AMQ-643
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: Connector
>     Versions: 4.0 RC1
>  Environment: AMQ 4 03/17/2006 SNAPSHOT
> Solaris 8, 10
>     Reporter: Kevin Yaussy
>     Assignee: Hiram Chirino
>      Fix For: 4.0 RC 2
>  Attachments: amq1.xml, amq2.xml
> AMQ 4 03/17/2006 SNAPSHOT
> Using maxInactivityDuration causes a connection to automatically break after the inactivity
duration, even though nothing is wrong with either side of the connection.
> Tracing it through, it looks like the KeepAliveInfo command does not require a response.
 This means that the KeepAlive sent never results in receive activity.  So, if both processes
are perfectly fine, just not sending any data, the connection breaks due to InactivityMonitor.readCheck.
> I've changed to return true for isResponseRequired.  This seems to
fix the problem, from a client perspective, anyway.
> However, if this is used for broker-to-broker connections, and you force a problem with
one of the brokers (like doing pstop on Solaris), major problems will happen:
> 1)  The broker that is left alone seems to break the connection.  But, it continues to
attempt to send messages to the failed broker.  It was mentioned in the forum at one point
you were going to have the broker unregister subscriptions so it would not attempt to send
messages to the failed broker.  Doesn't seem like this is in place.
> 2) If you reawaken the pstopped broker, the two brokers never really recover properly.
 Connections continue to get broken, over and over again.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message