[
https://issues.apache.org/activemq/browse/AMQ-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42343#action_42343
]
Kevin Yaussy commented on AMQ-1582:
-----------------------------------
Please see AMQ-1671, as it may be related.
> If InactivityMonitor is inactive, exception notification are not reported
> -------------------------------------------------------------------------
>
> Key: AMQ-1582
> URL: https://issues.apache.org/activemq/browse/AMQ-1582
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 4.1.1
> Environment: windows 2000, jdk 1.5.0, apache-gernonimo-2.0.2
> Reporter: Antonio Muñoz
>
> Since it is mantory to use a provider URL like this:
> tcp://localhost:61616?wireFormat.maxInactivityDuration=0
> In order to avoid the problem described on these issues AMQ-1146 and AMQ-1482
> we are starting all our jvm with that maxInactivityDuration value.
> But the problem that appears using this configuration is that when the
> InactivityMonitor is inactive every exception on the connection is not
> reported to the jms exception listener. So, it is not posible detecting the
> lost of the conection. Event if our ActiveMQ broker is dead, our clients are
> not notified.
> We have compile the activemq source code using the pom you provide but using
> the branch activemq-4.1 (from the branches folder). As your development
> people has solve this problem in this branch patching the class
> InactivyMonitor, the version we generated is working properly. Even if we are
> using the maxInactivityDuraction with the zero value, the exception are
> reported in the proper way.
> The actual issue is tha since Activemq 5.x is not supported by the last
> version of Geronimo AS 2.0.2 it should be needed an ActiveMQ 4.1 manteniance
> realese including at least the patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
