port.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.
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-moni
le.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
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-except
; at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(TransportFilter.java:99)
>>> at
>>> org
>>> .apache
>>> .activemq
>>> .transport.TransportFilter.onException(
ccell/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
> org.apache.activemq.transport.InactivityMonitor$4.run(
>> InactivityMonitor.java:142)
>> > at
>> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>> ThreadPoolExecutor.java:650)
>> > at
>> > java.util.concurrent.ThreadPoolExecu
ivityMonitor$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)
> >
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.
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.
.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(TcpTr
> .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
&
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-
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.
14 matches
Mail list logo