[
https://issues.apache.org/activemq/browse/AMQ-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59085#action_59085
]
Marko commented on AMQ-2517:
----------------------------
Hi,
I am also experiencing same problem.
I am using ActiveMQ broker (v 5.3.1) and NMS ActiveMQ clients.
Consumer is subscribed to topic and uses asynchronous message receiving.
However problem appears when consumer is idle for about 30 minutes, that is
consumer stops receiving messages after it has been idle for approximately 30
minutes.
This problem does not appear when both clients and broker are running on same
machine. Everything works fine when consumer application is restarted.
I have set maxInactivityDuration to 0.
I have also set handlers for ConnectionInterruptedListener,
ConnectionResumedListener and ExceptionListener but no events are fired.
After I close consumer application ACTIVEMQ console does report one consumer
less.
Here is transport connector configuration element in activemq.xml:
<transportConnector name="openwire"
uri="tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=0&keepAlive=true"
discoveryUri="multicast://default"/>
and client connects by using following uri:
"failover:(tcp://somehost:61616?wireFormat.maxInactivityDuration=0)"
Any idea why is this happening?
> Client stops receiving messages from topic after about 30 minutes of
> inactivity
> -------------------------------------------------------------------------------
>
> Key: AMQ-2517
> URL: https://issues.apache.org/activemq/browse/AMQ-2517
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.2.0, 5.3.0
> Environment: Ubuntu Karmic Koala
> java version "1.5.0_11"
> Reporter: Petr Kozelka
> Priority: Critical
>
> Hello,
> I have very simple ActiveMQ JMS client that listens on a topic. It works
> fine, but after about 30 minutes when there is no traffic, it "does not hear"
> anything.
> Also, AMQ console indicates that there is one less consumer on that topic.
> It seems to me somewhat similar to issue #AMQ-1251.
> This behavior is the same on 5.2.0 and 5.3.0 version - always deployed both
> on provider and client side.
> Is there a setting that might influence/workarround it ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
