activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1069) Setting maxInactivityDuration on broker to broker connections to value greater than 30 seconds doesn't work
Date Tue, 23 Oct 2007 13:54:23 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hiram Chirino resolved AMQ-1069.
--------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 5.2.0)

Please re-open issue if you do get around to attaching the configuration file that you were
using.

> Setting maxInactivityDuration on broker to broker connections to value greater than 30
seconds doesn't work
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1069
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1069
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>         Environment: Linux RHEL 4 with Java 1.5
>            Reporter: Eric Wood
>            Assignee: Hiram Chirino
>            Priority: Minor
>
> We are running AMQ in a configuration with embedded brokers on both the producer and
consumer (broker to broker network communication).  We have an extremely high latency network,
which results in a large number of inactivity timeouts.  Once we discovered how to set the
timeout, we tried to set it to a value of 100 seconds which we believe will work better with
our configuration and network.  However, we observed that timeouts were still occuring after
30 seconds of inactivity.  We tried setting the inactivity timeout value on both brokers and
got the same result.  We tried setting it to a value less than 30 (i.e. 10)  and we saw timeouts
occuring on that interval.  Because of this, we believe that there must be a limit on the
inactivity timeout value.  If there is such a limit, could it be increased.? The 30 second
value causes a large number of timeouts, which we believe causes a lower effective throughput
than is truly possible with JMS/AMQ.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message