You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by lurker <lu...@gmail.com> on 2008/02/11 03:40:38 UTC
Inactivity monitor exception is closing connection.
I'm programming some kind of messaging program that sends messages in sparse
frequency using activeMQ.
I got exceptions like following and connection between client and activeMQ
server is closed.
----------
11:20:24,202 DEBUG [InactivityMonitor] Message sent since last write check,
resetting flag
11:20:39,202 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
11:20:39,202 DEBUG [InactivityMonitor] Message received since last read
check, resetting flag:
11:20:54,202 DEBUG [InactivityMonitor] Message sent since last write check,
resetting flag
11:21:09,202 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
11:21:09,202 DEBUG [InactivityMonitor] Message received since last read
check, resetting flag:
11:21:24,202 DEBUG [InactivityMonitor] Message sent since last write check,
resetting flag
11:21:39,202 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
11:21:39,202 DEBUG [InactivityMonitor] Message received since last read
check, resetting flag:
11:21:54,202 DEBUG [InactivityMonitor] Message sent since last write check,
resetting flag
11:22:09,202 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
11:22:09,202 DEBUG [InactivityMonitor] Message received since last read
check, resetting flag:
11:22:24,202 DEBUG [InactivityMonitor] Message sent since last write check,
resetting flag
11:22:39,202 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
11:22:39,202 DEBUG [InactivityMonitor] Message received since last read
check, resetting flag:
11:22:54,202 DEBUG [InactivityMonitor] Message sent since last write check,
resetting flag
11:23:09,202 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
11:23:09,202 DEBUG [InactivityMonitor] No message received since last read
check for tcp://aaa.aaa.aaa/111.111.111.111:61616! Throwing
InactivityIOException.
11:23:09,218 WARN [ActiveMQConnection] Async exception with no exception
listener: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too long: some.domain.com/som.ip.he.re:61616
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too long: some.domain.com/som.ip.he.re:61616
at
org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:108)
11:23:09,218 DEBUG [TcpTransport] Stopping transport
tcp://some.domain.com/som.ip.he.re:61616
11:23:09,218 WARN [ActiveMQConnection] Async exception with no exception
listener: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
at java.io.DataInputStream.readInt(Unknown Source)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
at java.lang.Thread.run(Unknown Source)
------------
I don't know what is the problem.
Please help me.
Thanks in advance.
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15404620.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by bill richard <bi...@126.com>.
I also met this situation,and I set a exception listener,when the
exception listener listened this kind of exception.it will redo the sub.
And i also tried setting the maxIn..=0.but it has a bug,i reported it
long time ago.
lurker wrote:
>
> I'm programming some kind of messaging program that sends messages in
> sparse frequency using activeMQ.
> I got exceptions like following and connection between client and activeMQ
> server is closed.
> ----------
> 11:20:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:20:39,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:20:39,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:20:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:21:09,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:21:09,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:21:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:21:39,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:21:39,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:21:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:22:09,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:22:09,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:22:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:22:39,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:22:39,202 DEBUG [InactivityMonitor] Message received since last read
> check, resetting flag:
> 11:22:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check, resetting flag
> 11:23:09,202 DEBUG [InactivityMonitor] No message sent since last write
> check, sending a KeepAliveInfo
> 11:23:09,202 DEBUG [InactivityMonitor] No message received since last read
> check for tcp://aaa.aaa.aaa/111.111.111.111:61616! Throwing
> InactivityIOException.
> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no exception
> listener: org.apache.activemq.transport.InactivityIOException: Channel was
> inactive for too long: some.domain.com/som.ip.he.re:61616
> org.apache.activemq.transport.InactivityIOException: Channel was inactive
> for too long: some.domain.com/som.ip.he.re:61616
> at
> org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:108)
> 11:23:09,218 DEBUG [TcpTransport] Stopping transport
> tcp://some.domain.com/som.ip.he.re:61616
> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no exception
> listener: java.net.SocketException: socket closed
> java.net.SocketException: socket closed
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
> at
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
> at java.io.DataInputStream.readInt(Unknown Source)
> at
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:192)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:184)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:172)
> at java.lang.Thread.run(Unknown Source)
> ------------
>
> I don't know what is the problem.
> Please help me.
> Thanks in advance.
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p16116806.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by vineetk <vk...@bellsouth.net>.
I am using activemq-all-5.1-SNAPSHOT.jar and still get this error:
2008-02-19 11:44:25,768 (ActiveMQConnection.java:1453) WARN
org.apache.activemq.ActiveMQConnection - Async exception with no exception
listener: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too long.
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too long.
at
org.apache.activemq.transport.InactivityMonitor.readCheck(InactivityMonitor.java:101)
at
org.apache.activemq.transport.InactivityMonitor.access$000(InactivityMonitor.java:35)
at
org.apache.activemq.transport.InactivityMonitor$1.run(InactivityMonitor.java:51)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:431)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198)
at
edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:189)
at
edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:213)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
rajdavies wrote:
>
> Could you try a snaphot of ActiveMQ 5.1 ?
>
> thanks,
>
> Rob
>
> On Feb 11, 2008, at 2:40 AM, lurker wrote:
>
>>
>> I'm programming some kind of messaging program that sends messages
>> in sparse
>> frequency using activeMQ.
>> I got exceptions like following and connection between client and
>> activeMQ
>> server is closed.
>> ----------
>> 11:20:24,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:20:39,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:20:39,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:20:54,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:21:09,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:21:09,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:21:24,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:21:39,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:21:39,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:21:54,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:22:09,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:22:09,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:22:24,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:22:39,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:22:39,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:22:54,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:23:09,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:23:09,202 DEBUG [InactivityMonitor] No message received since
>> last read
>> check for tcp://aaa.aaa.aaa/111.111.111.111:61616! Throwing
>> InactivityIOException.
>> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no
>> exception
>> listener: org.apache.activemq.transport.InactivityIOException:
>> Channel was
>> inactive for too long: some.domain.com/som.ip.he.re:61616
>> org.apache.activemq.transport.InactivityIOException: Channel was
>> inactive
>> for too long: some.domain.com/som.ip.he.re:61616
>> at
>> org.apache.activemq.transport.InactivityMonitor
>> $4.run(InactivityMonitor.java:108)
>> 11:23:09,218 DEBUG [TcpTransport] Stopping transport
>> tcp://some.domain.com/som.ip.he.re:61616
>> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no
>> exception
>> listener: java.net.SocketException: socket closed
>> java.net.SocketException: socket closed
>> at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(Unknown Source)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
>> at java.io.DataInputStream.readInt(Unknown Source)
>> at
>> org
>> .apache
>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>> at
>> org
>> .apache
>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
>> 192)
>> at
>> org
>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
>> 184)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>> 172)
>> at java.lang.Thread.run(Unknown Source)
>> ------------
>>
>> I don't know what is the problem.
>> Please help me.
>> Thanks in advance.
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15404620.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15561547.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by jpitts <ju...@gmail.com>.
Is this still planned? Does anyone have an idea when it may happen?
rajdavies wrote:
>
>
> [....] We should be coming out with a 5.0.1
> real soon that will include the fix
>
>
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p16093098.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by jpitts <ju...@gmail.com>.
Is this still planned? Does anyone have an idea when it may happen?
rajdavies wrote:
>
>
> [....] We should be coming out with a 5.0.1
> real soon that will include the fix
>
>
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p16093098.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by Rob Davies <ra...@gmail.com>.
On 28 Feb 2008, at 09:42, cedricb wrote:
>
> Hi Rob,
>
> We've got the same issue with a Spring 2.5.1/ActiveMQ 5.0.0
> application.
>
> I've just tested the apache-activemq-5.1-20080227.125551-32 version
> and it
> look like the problem is fixed... :-)
>
> When do you think, 5.1 will be release? I don't really want to go to
> production with a snapshot version. If it's a simple fix, do you
> think it's
> possible to backport it to the 5.0 branch?
>
>
> Regards,
> Cedric.
>
> ---
> Could you try a snaphot of ActiveMQ 5.1 ?
>
> thanks,
> Rob
> --
> View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15732876.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Good to know its fixed for you! We should be coming out with a 5.0.1
real soon that will include the fix
Re: Inactivity monitor exception is closing connection.
Posted by cedricb <ce...@hotmail.com>.
Hi Rob,
We've got the same issue with a Spring 2.5.1/ActiveMQ 5.0.0 application.
I've just tested the apache-activemq-5.1-20080227.125551-32 version and it
look like the problem is fixed... :-)
When do you think, 5.1 will be release? I don't really want to go to
production with a snapshot version. If it's a simple fix, do you think it's
possible to backport it to the 5.0 branch?
Regards,
Cedric.
---
Could you try a snaphot of ActiveMQ 5.1 ?
thanks,
Rob
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15732876.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by lurker <lu...@gmail.com>.
Thanks for your fast reply, Rob.
I tried activeMQ 5.1.
The connection alive time is longer than 5.0 version that I used before.
But it still closes the connection after some while.
I attach the exception logs below.
Is there any configuration value for idle timeout?
-----
18:34:04,249 DEBUG [InactivityMonitor] No message sent since last write
check, sending a KeepAliveInfo
18:34:14,249 DEBUG [InactivityMonitor] 30000 ms elapsed since last read
check.
18:34:14,249 DEBUG [InactivityMonitor] No message received since last read
check for tcp://some.domain.com/127.0.0.1:61616! Throwing
InactivityIOException.
18:34:14,249 WARN [ActiveMQConnection] Async exception with no exception
listener: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too long: some.domain.com/127.0.0.1:61616
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too long: some.domain.com/127.0.0.1:61616
at
org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:142)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
18:34:14,249 DEBUG [TcpTransport] Stopping transport
tcp://some.domain.com/127.0.0.1:61616
18:34:14,265 WARN [ActiveMQConnection] Async exception with no exception
listener: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
at java.io.DataInputStream.readInt(Unknown Source)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:203)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:195)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
at java.lang.Thread.run(Unknown Source)
rajdavies wrote:
>
> Could you try a snaphot of ActiveMQ 5.1 ?
>
> thanks,
>
> Rob
>
> On Feb 11, 2008, at 2:40 AM, lurker wrote:
>
>>
>> I'm programming some kind of messaging program that sends messages
>> in sparse
>> frequency using activeMQ.
>> I got exceptions like following and connection between client and
>> activeMQ
>> server is closed.
>> ----------
>> 11:20:24,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:20:39,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:20:39,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:20:54,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:21:09,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:21:09,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:21:24,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:21:39,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:21:39,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:21:54,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:22:09,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:22:09,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:22:24,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:22:39,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:22:39,202 DEBUG [InactivityMonitor] Message received since last
>> read
>> check, resetting flag:
>> 11:22:54,202 DEBUG [InactivityMonitor] Message sent since last write
>> check,
>> resetting flag
>> 11:23:09,202 DEBUG [InactivityMonitor] No message sent since last
>> write
>> check, sending a KeepAliveInfo
>> 11:23:09,202 DEBUG [InactivityMonitor] No message received since
>> last read
>> check for tcp://aaa.aaa.aaa/111.111.111.111:61616! Throwing
>> InactivityIOException.
>> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no
>> exception
>> listener: org.apache.activemq.transport.InactivityIOException:
>> Channel was
>> inactive for too long: some.domain.com/som.ip.he.re:61616
>> org.apache.activemq.transport.InactivityIOException: Channel was
>> inactive
>> for too long: some.domain.com/som.ip.he.re:61616
>> at
>> org.apache.activemq.transport.InactivityMonitor
>> $4.run(InactivityMonitor.java:108)
>> 11:23:09,218 DEBUG [TcpTransport] Stopping transport
>> tcp://some.domain.com/som.ip.he.re:61616
>> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no
>> exception
>> listener: java.net.SocketException: socket closed
>> java.net.SocketException: socket closed
>> at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(Unknown Source)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
>> at java.io.DataInputStream.readInt(Unknown Source)
>> at
>> org
>> .apache
>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
>> at
>> org
>> .apache
>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
>> 192)
>> at
>> org
>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
>> 184)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>> 172)
>> at java.lang.Thread.run(Unknown Source)
>> ------------
>>
>> I don't know what is the problem.
>> Please help me.
>> Thanks in advance.
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15404620.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15409835.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by Rob Davies <ra...@gmail.com>.
Could you try a snaphot of ActiveMQ 5.1 ?
thanks,
Rob
On Feb 11, 2008, at 2:40 AM, lurker wrote:
>
> I'm programming some kind of messaging program that sends messages
> in sparse
> frequency using activeMQ.
> I got exceptions like following and connection between client and
> activeMQ
> server is closed.
> ----------
> 11:20:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check,
> resetting flag
> 11:20:39,202 DEBUG [InactivityMonitor] No message sent since last
> write
> check, sending a KeepAliveInfo
> 11:20:39,202 DEBUG [InactivityMonitor] Message received since last
> read
> check, resetting flag:
> 11:20:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check,
> resetting flag
> 11:21:09,202 DEBUG [InactivityMonitor] No message sent since last
> write
> check, sending a KeepAliveInfo
> 11:21:09,202 DEBUG [InactivityMonitor] Message received since last
> read
> check, resetting flag:
> 11:21:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check,
> resetting flag
> 11:21:39,202 DEBUG [InactivityMonitor] No message sent since last
> write
> check, sending a KeepAliveInfo
> 11:21:39,202 DEBUG [InactivityMonitor] Message received since last
> read
> check, resetting flag:
> 11:21:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check,
> resetting flag
> 11:22:09,202 DEBUG [InactivityMonitor] No message sent since last
> write
> check, sending a KeepAliveInfo
> 11:22:09,202 DEBUG [InactivityMonitor] Message received since last
> read
> check, resetting flag:
> 11:22:24,202 DEBUG [InactivityMonitor] Message sent since last write
> check,
> resetting flag
> 11:22:39,202 DEBUG [InactivityMonitor] No message sent since last
> write
> check, sending a KeepAliveInfo
> 11:22:39,202 DEBUG [InactivityMonitor] Message received since last
> read
> check, resetting flag:
> 11:22:54,202 DEBUG [InactivityMonitor] Message sent since last write
> check,
> resetting flag
> 11:23:09,202 DEBUG [InactivityMonitor] No message sent since last
> write
> check, sending a KeepAliveInfo
> 11:23:09,202 DEBUG [InactivityMonitor] No message received since
> last read
> check for tcp://aaa.aaa.aaa/111.111.111.111:61616! Throwing
> InactivityIOException.
> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no
> exception
> listener: org.apache.activemq.transport.InactivityIOException:
> Channel was
> inactive for too long: some.domain.com/som.ip.he.re:61616
> org.apache.activemq.transport.InactivityIOException: Channel was
> inactive
> for too long: some.domain.com/som.ip.he.re:61616
> at
> org.apache.activemq.transport.InactivityMonitor
> $4.run(InactivityMonitor.java:108)
> 11:23:09,218 DEBUG [TcpTransport] Stopping transport
> tcp://some.domain.com/som.ip.he.re:61616
> 11:23:09,218 WARN [ActiveMQConnection] Async exception with no
> exception
> listener: java.net.SocketException: socket closed
> java.net.SocketException: socket closed
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at
> org
> .apache
> .activemq
> .transport
> .tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
> at
> org
> .apache
> .activemq
> .transport
> .tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
> at java.io.DataInputStream.readInt(Unknown Source)
> at
> org
> .apache
> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268)
> at
> org
> .apache
> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:
> 192)
> at
> org
> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:
> 184)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
> 172)
> at java.lang.Thread.run(Unknown Source)
> ------------
>
> I don't know what is the problem.
> Please help me.
> Thanks in advance.
>
> --
> View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15404620.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Inactivity monitor exception is closing connection.
Posted by sparky2708 <da...@columbia.edu>.
Reading the forums, doesn't this error mean that there is some problem
with the heartbeat. The client was still alive when it happened as seen in
the previous posts (it did throw the exception when the InactivityMonitor
killed the connection).
I assume you are referring to the maxinactivity property. What should
that be set to? (I thought it is set pretty high at 3000ms by default?).
Still not clear if this is a known bug and when would it be resolved? Seems
like a lot of people are seeing this...
Zao Liu wrote:
>
> I guess it is a warning for disconnect the clients which has been inactive
> for a long time. You can set the time for inactive connection by set
> activitymonitor.
>
>
> On Thu, Feb 21, 2008 at 2:52 PM, sparky2708 <da...@columbia.edu> wrote:
>
>>
>> This started happening since we upgraded from 4.1.0. 4.1.0 doesn't seem
>> to
>> have this problem.
>>
>>
>> sparky2708 wrote:
>> >
>> > I am getting the same error with SNAPSHOT-5.1:
>> >
>> > 21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
>> > tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
>> > com.company_name.messaging.MessageManager::onException
>> > javax.jms.JMSException: Channel was inactive for too long:
>> > puccell/10.0.55.197:61616
>> > at
>> > org.apache.activemq.util.JMSExceptionSupport.create(
>> JMSExceptionSupport.java:49)
>> > at
>> > org.apache.activemq.ActiveMQConnection.onAsyncException(
>> ActiveMQConnection.java:1649)
>> > at
>> > org.apache.activemq.ActiveMQConnection.onException(
>> ActiveMQConnection.java:1666)
>> > at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> > at
>> > org.apache.activemq.transport.ResponseCorrelator.onException(
>> ResponseCorrelator.java:116)
>> > at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> > at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> > at
>> > org.apache.activemq.transport.WireFormatNegotiator.onException(
>> WireFormatNegotiator.java:143)
>> > at
>> > org.apache.activemq.transport.InactivityMonitor.onException(
>> InactivityMonitor.java:204)
>> > at
>> > org.apache.activemq.transport.InactivityMonitor$4.run(
>> InactivityMonitor.java:142)
>> > at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>> ThreadPoolExecutor.java:650)
>> > at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:675)
>> > at java.lang.Thread.run(Thread.java:595)
>> > Caused by: org.apache.activemq.transport.InactivityIOException: Channel
>> > was inactive for too long: puccell/10.0.55.197:61616
>> > ... 4 more
>> > 21/02/2008 08:03:35,098 ERROR [ActiveMQ Connection Worker:
>> > tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
>> > com.company_name.messaging.MessageManager::onException
>> > javax.jms.JMSException: Channel was inactive for too long:
>> > puccell/10.0.55.197:61616
>> > at
>> > org.apache.activemq.util.JMSExceptionSupport.create(
>> JMSExceptionSupport.java:49)
>> > at
>> > org.apache.activemq.ActiveMQConnection.onAsyncException(
>> ActiveMQConnection.java:1649)
>> > at
>> > org.apache.activemq.ActiveMQConnection.onException(
>> ActiveMQConnection.java:1666)
>> > at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> > at
>> > org.apache.activemq.transport.ResponseCorrelator.onException(
>> ResponseCorrelator.java:116)
>> > at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> > at
>> > org.apache.activemq.transport.TransportFilter.onException(
>> TransportFilter.java:99)
>> > at
>> > org.apache.activemq.transport.WireFormatNegotiator.onException(
>> WireFormatNegotiator.java:143)
>> > at
>> > org.apache.activemq.transport.InactivityMonitor.onException(
>> InactivityMonitor.java:204)
>> > at
>> > org.apache.activemq.transport.InactivityMonitor$4.run(
>> InactivityMonitor.java:142)
>> > at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>> ThreadPoolExecutor.java:650)
>> > at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:675)
>> > at java.lang.Thread.run(Thread.java:595)
>> > Caused by: org.apache.activemq.transport.InactivityIOException: Channel
>> > was inactive for too long: puccell/10.0.55.197:61616
>> > ... 4 more
>> >
>> > Anybody have a workaround? I am having problems using this version
>> because
>> > it just kicks off all of my services after awhile!
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15628176.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by Zao Liu <za...@cs.indiana.edu>.
I guess it is a warning for disconnect the clients which has been inactive
for a long time. You can set the time for inactive connection by set
activitymonitor.
On Thu, Feb 21, 2008 at 2:52 PM, sparky2708 <da...@columbia.edu> wrote:
>
> This started happening since we upgraded from 4.1.0. 4.1.0 doesn't seem to
> have this problem.
>
>
> sparky2708 wrote:
> >
> > I am getting the same error with SNAPSHOT-5.1:
> >
> > 21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
> > tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
> > com.company_name.messaging.MessageManager::onException
> > javax.jms.JMSException: Channel was inactive for too long:
> > puccell/10.0.55.197:61616
> > at
> > org.apache.activemq.util.JMSExceptionSupport.create(
> JMSExceptionSupport.java:49)
> > at
> > org.apache.activemq.ActiveMQConnection.onAsyncException(
> ActiveMQConnection.java:1649)
> > at
> > org.apache.activemq.ActiveMQConnection.onException(
> ActiveMQConnection.java:1666)
> > at
> > org.apache.activemq.transport.TransportFilter.onException(
> TransportFilter.java:99)
> > at
> > org.apache.activemq.transport.ResponseCorrelator.onException(
> ResponseCorrelator.java:116)
> > at
> > org.apache.activemq.transport.TransportFilter.onException(
> TransportFilter.java:99)
> > at
> > org.apache.activemq.transport.TransportFilter.onException(
> TransportFilter.java:99)
> > at
> > org.apache.activemq.transport.WireFormatNegotiator.onException(
> WireFormatNegotiator.java:143)
> > at
> > org.apache.activemq.transport.InactivityMonitor.onException(
> InactivityMonitor.java:204)
> > at
> > org.apache.activemq.transport.InactivityMonitor$4.run(
> InactivityMonitor.java:142)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> ThreadPoolExecutor.java:650)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:675)
> > at java.lang.Thread.run(Thread.java:595)
> > Caused by: org.apache.activemq.transport.InactivityIOException: Channel
> > was inactive for too long: puccell/10.0.55.197:61616
> > ... 4 more
> > 21/02/2008 08:03:35,098 ERROR [ActiveMQ Connection Worker:
> > tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
> > com.company_name.messaging.MessageManager::onException
> > javax.jms.JMSException: Channel was inactive for too long:
> > puccell/10.0.55.197:61616
> > at
> > org.apache.activemq.util.JMSExceptionSupport.create(
> JMSExceptionSupport.java:49)
> > at
> > org.apache.activemq.ActiveMQConnection.onAsyncException(
> ActiveMQConnection.java:1649)
> > at
> > org.apache.activemq.ActiveMQConnection.onException(
> ActiveMQConnection.java:1666)
> > at
> > org.apache.activemq.transport.TransportFilter.onException(
> TransportFilter.java:99)
> > at
> > org.apache.activemq.transport.ResponseCorrelator.onException(
> ResponseCorrelator.java:116)
> > at
> > org.apache.activemq.transport.TransportFilter.onException(
> TransportFilter.java:99)
> > at
> > org.apache.activemq.transport.TransportFilter.onException(
> TransportFilter.java:99)
> > at
> > org.apache.activemq.transport.WireFormatNegotiator.onException(
> WireFormatNegotiator.java:143)
> > at
> > org.apache.activemq.transport.InactivityMonitor.onException(
> InactivityMonitor.java:204)
> > at
> > org.apache.activemq.transport.InactivityMonitor$4.run(
> InactivityMonitor.java:142)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> ThreadPoolExecutor.java:650)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:675)
> > at java.lang.Thread.run(Thread.java:595)
> > Caused by: org.apache.activemq.transport.InactivityIOException: Channel
> > was inactive for too long: puccell/10.0.55.197:61616
> > ... 4 more
> >
> > Anybody have a workaround? I am having problems using this version
> because
> > it just kicks off all of my services after awhile!
> >
>
> --
> View this message in context:
> http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
Re: Inactivity monitor exception is closing connection.
Posted by sparky2708 <da...@columbia.edu>.
Would love to know how to do that. Can you give me an example of a test case
or where I would find out how to write a test case?
rajdavies wrote:
>
> Could you please provide a test case ?
>
> cheers,
>
> Rob
> On 21 Feb 2008, at 22:52, sparky2708 wrote:
>
>>
>> This started happening since we upgraded from 4.1.0. 4.1.0 doesn't
>> seem to
>> have this problem.
>>
>>
>> sparky2708 wrote:
>>>
>>> I am getting the same error with SNAPSHOT-5.1:
>>>
>>> 21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
>>> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
>>> com.company_name.messaging.MessageManager::onException
>>> javax.jms.JMSException: Channel was inactive for too long:
>>> puccell/10.0.55.197:61616
>>> at
>>> org
>>> .apache
>>> .activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:
>>> 49)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
>>> at
>>> org
>>> .apache
>>> .activemq.ActiveMQConnection.onException(ActiveMQConnection.java:
>>> 1666)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.ResponseCorrelator.onException(ResponseCorrelator.java:
>>> 116)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport
>>> .WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.InactivityMonitor.onException(InactivityMonitor.java:204)
>>> at
>>> org.apache.activemq.transport.InactivityMonitor
>>> $4.run(InactivityMonitor.java:142)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor
>>> $Worker.runTask(ThreadPoolExecutor.java:650)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor
>>> $Worker.run(ThreadPoolExecutor.java:675)
>>> at java.lang.Thread.run(Thread.java:595)
>>> Caused by: org.apache.activemq.transport.InactivityIOException:
>>> Channel
>>> was inactive for too long: puccell/10.0.55.197:61616
>>> ... 4 more
>>> 21/02/2008 08:03:35,098 ERROR [ActiveMQ Connection Worker:
>>> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
>>> com.company_name.messaging.MessageManager::onException
>>> javax.jms.JMSException: Channel was inactive for too long:
>>> puccell/10.0.55.197:61616
>>> at
>>> org
>>> .apache
>>> .activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:
>>> 49)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
>>> at
>>> org
>>> .apache
>>> .activemq.ActiveMQConnection.onException(ActiveMQConnection.java:
>>> 1666)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.ResponseCorrelator.onException(ResponseCorrelator.java:
>>> 116)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport
>>> .WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.InactivityMonitor.onException(InactivityMonitor.java:204)
>>> at
>>> org.apache.activemq.transport.InactivityMonitor
>>> $4.run(InactivityMonitor.java:142)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor
>>> $Worker.runTask(ThreadPoolExecutor.java:650)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor
>>> $Worker.run(ThreadPoolExecutor.java:675)
>>> at java.lang.Thread.run(Thread.java:595)
>>> Caused by: org.apache.activemq.transport.InactivityIOException:
>>> Channel
>>> was inactive for too long: puccell/10.0.55.197:61616
>>> ... 4 more
>>>
>>> Anybody have a workaround? I am having problems using this version
>>> because
>>> it just kicks off all of my services after awhile!
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15634456.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by Rob Davies <ra...@gmail.com>.
Could you please provide a test case ?
cheers,
Rob
On 21 Feb 2008, at 22:52, sparky2708 wrote:
>
> This started happening since we upgraded from 4.1.0. 4.1.0 doesn't
> seem to
> have this problem.
>
>
> sparky2708 wrote:
>>
>> I am getting the same error with SNAPSHOT-5.1:
>>
>> 21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
>> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
>> com.company_name.messaging.MessageManager::onException
>> javax.jms.JMSException: Channel was inactive for too long:
>> puccell/10.0.55.197:61616
>> at
>> org
>> .apache
>> .activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:
>> 49)
>> at
>> org
>> .apache
>> .activemq
>> .ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
>> at
>> org
>> .apache
>> .activemq.ActiveMQConnection.onException(ActiveMQConnection.java:
>> 1666)
>> at
>> org
>> .apache
>> .activemq
>> .transport.TransportFilter.onException(TransportFilter.java:99)
>> at
>> org
>> .apache
>> .activemq
>> .transport.ResponseCorrelator.onException(ResponseCorrelator.java:
>> 116)
>> at
>> org
>> .apache
>> .activemq
>> .transport.TransportFilter.onException(TransportFilter.java:99)
>> at
>> org
>> .apache
>> .activemq
>> .transport.TransportFilter.onException(TransportFilter.java:99)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
>> at
>> org
>> .apache
>> .activemq
>> .transport.InactivityMonitor.onException(InactivityMonitor.java:204)
>> at
>> org.apache.activemq.transport.InactivityMonitor
>> $4.run(InactivityMonitor.java:142)
>> at
>> java.util.concurrent.ThreadPoolExecutor
>> $Worker.runTask(ThreadPoolExecutor.java:650)
>> at
>> java.util.concurrent.ThreadPoolExecutor
>> $Worker.run(ThreadPoolExecutor.java:675)
>> at java.lang.Thread.run(Thread.java:595)
>> Caused by: org.apache.activemq.transport.InactivityIOException:
>> Channel
>> was inactive for too long: puccell/10.0.55.197:61616
>> ... 4 more
>> 21/02/2008 08:03:35,098 ERROR [ActiveMQ Connection Worker:
>> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
>> com.company_name.messaging.MessageManager::onException
>> javax.jms.JMSException: Channel was inactive for too long:
>> puccell/10.0.55.197:61616
>> at
>> org
>> .apache
>> .activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:
>> 49)
>> at
>> org
>> .apache
>> .activemq
>> .ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
>> at
>> org
>> .apache
>> .activemq.ActiveMQConnection.onException(ActiveMQConnection.java:
>> 1666)
>> at
>> org
>> .apache
>> .activemq
>> .transport.TransportFilter.onException(TransportFilter.java:99)
>> at
>> org
>> .apache
>> .activemq
>> .transport.ResponseCorrelator.onException(ResponseCorrelator.java:
>> 116)
>> at
>> org
>> .apache
>> .activemq
>> .transport.TransportFilter.onException(TransportFilter.java:99)
>> at
>> org
>> .apache
>> .activemq
>> .transport.TransportFilter.onException(TransportFilter.java:99)
>> at
>> org
>> .apache
>> .activemq
>> .transport
>> .WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
>> at
>> org
>> .apache
>> .activemq
>> .transport.InactivityMonitor.onException(InactivityMonitor.java:204)
>> at
>> org.apache.activemq.transport.InactivityMonitor
>> $4.run(InactivityMonitor.java:142)
>> at
>> java.util.concurrent.ThreadPoolExecutor
>> $Worker.runTask(ThreadPoolExecutor.java:650)
>> at
>> java.util.concurrent.ThreadPoolExecutor
>> $Worker.run(ThreadPoolExecutor.java:675)
>> at java.lang.Thread.run(Thread.java:595)
>> Caused by: org.apache.activemq.transport.InactivityIOException:
>> Channel
>> was inactive for too long: puccell/10.0.55.197:61616
>> ... 4 more
>>
>> Anybody have a workaround? I am having problems using this version
>> because
>> it just kicks off all of my services after awhile!
>>
>
> --
> View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Inactivity monitor exception is closing connection.
Posted by sparky2708 <da...@columbia.edu>.
This started happening since we upgraded from 4.1.0. 4.1.0 doesn't seem to
have this problem.
sparky2708 wrote:
>
> I am getting the same error with SNAPSHOT-5.1:
>
> 21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
> com.company_name.messaging.MessageManager::onException
> javax.jms.JMSException: Channel was inactive for too long:
> puccell/10.0.55.197:61616
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
> at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1666)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
> at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
> at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
> at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:204)
> at
> org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.activemq.transport.InactivityIOException: Channel
> was inactive for too long: puccell/10.0.55.197:61616
> ... 4 more
> 21/02/2008 08:03:35,098 ERROR [ActiveMQ Connection Worker:
> tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
> com.company_name.messaging.MessageManager::onException
> javax.jms.JMSException: Channel was inactive for too long:
> puccell/10.0.55.197:61616
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
> at
> org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
> at
> org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1666)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
> at
> org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
> at
> org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
> at
> org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
> at
> org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:204)
> at
> org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.activemq.transport.InactivityIOException: Channel
> was inactive for too long: puccell/10.0.55.197:61616
> ... 4 more
>
> Anybody have a workaround? I am having problems using this version because
> it just kicks off all of my services after awhile!
>
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15622035.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Inactivity monitor exception is closing connection.
Posted by sparky2708 <da...@columbia.edu>.
I am getting the same error with SNAPSHOT-5.1:
21/02/2008 08:03:34,335 ERROR [ActiveMQ Connection Worker:
tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
com.company_name.messaging.MessageManager::onException
javax.jms.JMSException: Channel was inactive for too long:
puccell/10.0.55.197:61616
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at
org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
at
org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1666)
at
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
at
org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
at
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
at
org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
at
org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:204)
at
org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too long: puccell/10.0.55.197:61616
... 4 more
21/02/2008 08:03:35,098 ERROR [ActiveMQ Connection Worker:
tcp://puccell/10.0.55.197:61616] (MessageManager.java:439) -
com.company_name.messaging.MessageManager::onException
javax.jms.JMSException: Channel was inactive for too long:
puccell/10.0.55.197:61616
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
at
org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1649)
at
org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1666)
at
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
at
org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:116)
at
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
at
org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
at
org.apache.activemq.transport.WireFormatNegotiator.onException(WireFormatNegotiator.java:143)
at
org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:204)
at
org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.activemq.transport.InactivityIOException: Channel was
inactive for too long: puccell/10.0.55.197:61616
... 4 more
Anybody have a workaround? I am having problems using this version because
it just kicks off all of my services after awhile!
--
View this message in context: http://www.nabble.com/Inactivity-monitor-exception-is-closing-connection.-tp15404620s2354p15611505.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.