Its fixed in this version - http://activemq.apache.org/activemq-412-release.html
cheers,
Rob
On 17 Jun 2008, at 06:42, Suchitha Koneru (sukoneru) wrote:
After having read through nabble active mq forums , It is a known
issue
with active mq 4.1.1 that when max inactivity duration is set to -1 ,
the client is not notified of any connection exceptions.
This issues is mentioned in
https://issues.apache.org/activemq/browse/AMQ-1582
Is there a patch available for this ? In which of the latter
versions of
active MQ is this issue fixed ?
Please let us know, we are very close to our production date.
Thanks a lot,
Suchitha.
-----Original Message-----
From: Suchitha Koneru (sukoneru)
Sent: Monday, June 16, 2008 1:00 PM
To: [EMAIL PROTECTED]; users@activemq.apache.org
Subject: subscriber issues.
Hello All ,
We use the active mq broker for exchanging the messages
between two JVM's. One JVM is a tomcat server and the other other is
stand alone java process. The active MQ broker is started by one of
the
threads in the stand alone have process.
We use durable subscribers and non persistent delivery of messages.
There is one durable subscriber and topic publisher per JVM. After
running for 2-3 days the subscriber in the Tomcat server stops
receiving
messages , Iam not sure if the subscriber died or if it is blocked ,
or
if the TCP socket got closed. I do not see any exceptions in the
logs.
Any insights into debugging this issue ? Is there a way I can look at
all the threads and ports being used by active MQ ? Can I print the
ports at which the subscriber and publisher are running in the logs.
The broker url is as follows
failover/:tcp/://ipAddress/:portNumber
The maxInactivity duration is set as -1
Version of Tomcat : 5.5.9
Active Mq Version : 4.1.1
Java 1.6
The durable subscriber in Tomcat server is configured as per the
example
http://activemq.apache.org/setting-up-activemq-with-tomcat-559.html.
thank you,
suchitha.
