You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ruiluis <ru...@eyesee.pt> on 2012/12/18 12:55:01 UTC
Connection reset
Good day. I have several types of clients that connect to a topic using
stomp. Sometimes after some use ( just some 7/8 messages) the users get
disconnected and this error appears in the activemq log file after i try to
send a message from the producer to the clients..
its quite strange because the clients do not detect the connection
failure...
2012-12-18 11:27:21,401 | DEBUG | Transport Connection to:
tcp://127.0.0.1:1031 failed: java.net.SocketException: Connection reset |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///127.0.0.1:1031@61613
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:189)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
at
org.apache.activemq.transport.tcp.TcpTransport$2.fill(TcpTransport.java:612)
at
org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
at
org.apache.activemq.transport.tcp.TcpTransport$2.read(TcpTransport.java:597)
at java.io.DataInputStream.readByte(DataInputStream.java:265)
at
org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(StompWireFormat.java:155)
at
org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:148)
at
org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:170)
at
org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:98)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:229)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:221)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:204)
at java.lang.Thread.run(Thread.java:722)
2012-12-18 11:27:21,405 | DEBUG | Unregistering MBean
org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=stomp,Connection=ID_demoserver-50466-1355829271859-2_1
| org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ Transport:
tcp:///127.0.0.1:1031@61613
--
View this message in context: http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Connection reset
Posted by Raul Kripalani <ra...@evosent.com>.
Did you try enabling TCP keepalives on the Connection Factory (client) and
the Transport Connector (broker)? Perhaps that hints the intermediate
router that the connection is still alive on both ends.
See the keepAlive option in [1].
[1] http://activemq.apache.org/tcp-transport-reference.html
Regards,
*Raúl Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk>
On Thu, Dec 20, 2012 at 4:26 PM, ruiluis <ru...@eyesee.pt> wrote:
> you all were right.. the problem was originated by a router that for a
> reason
> that i am unaware of, simply decides to drop my tcps connections.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660952.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Connection reset
Posted by ruiluis <ru...@eyesee.pt>.
you all were right.. the problem was originated by a router that for a reason
that i am unaware of, simply decides to drop my tcps connections.
--
View this message in context: http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660952.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Connection reset
Posted by Christian Posta <ch...@gmail.com>.
every two minutes is quite a long time. the default inactivity monitor on
the tcp transport will timeout after 30s (although i think you'd see
something in the logs if that was the reason the socket was closed). the
default inactivity monitor also sends heart beat messages so that the
connection doesn't get shutdown due to user inactivity. there must be
something else going on in your situation
On Wed, Dec 19, 2012 at 10:51 AM, ruiluis <ru...@eyesee.pt> wrote:
> its driving me crazy because it cannot be due to inactivity because i
> ensure
> that it sends something almost every two minutes.. some third process
> removing the connections that is very strange because the server is a clean
> server running almost nothing..
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660921.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Re: Connection reset
Posted by ruiluis <ru...@eyesee.pt>.
its driving me crazy because it cannot be due to inactivity because i ensure
that it sends something almost every two minutes.. some third process
removing the connections that is very strange because the server is a clean
server running almost nothing..
--
View this message in context: http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660921.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Connection reset
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Dec 18, 2012 at 8:03 PM, Christian Posta
<ch...@gmail.com> wrote:
> Maybe some third party monitors killing the connection?
>
Or maybe a firewall if a connection has been inactive for X period.
>
> On Tue, Dec 18, 2012 at 4:55 AM, ruiluis <ru...@eyesee.pt> wrote:
>
>> Good day. I have several types of clients that connect to a topic using
>> stomp. Sometimes after some use ( just some 7/8 messages) the users get
>> disconnected and this error appears in the activemq log file after i try to
>> send a message from the producer to the clients..
>> its quite strange because the clients do not detect the connection
>> failure...
>>
>> 2012-12-18 11:27:21,401 | DEBUG | Transport Connection to:
>> tcp://127.0.0.1:1031 failed: java.net.SocketException: Connection reset |
>> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
>> Transport: tcp:///127.0.0.1:1031@61613
>> java.net.SocketException: Connection reset
>> at java.net.SocketInputStream.read(SocketInputStream.java:189)
>> at java.net.SocketInputStream.read(SocketInputStream.java:121)
>> at
>>
>> org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
>> at
>>
>> org.apache.activemq.transport.tcp.TcpTransport$2.fill(TcpTransport.java:612)
>> at
>>
>> org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
>> at
>>
>> org.apache.activemq.transport.tcp.TcpTransport$2.read(TcpTransport.java:597)
>> at java.io.DataInputStream.readByte(DataInputStream.java:265)
>> at
>>
>> org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(StompWireFormat.java:155)
>> at
>>
>> org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:148)
>> at
>>
>> org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:170)
>> at
>>
>> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:98)
>> at
>>
>> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:229)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:221)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:204)
>> at java.lang.Thread.run(Thread.java:722)
>> 2012-12-18 11:27:21,405 | DEBUG | Unregistering MBean
>>
>> org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=stomp,Connection=ID_demoserver-50466-1355829271859-2_1
>> | org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ Transport:
>> tcp:///127.0.0.1:1031@61613
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> *Christian Posta*
> http://www.christianposta.com/blog
> twitter: @christianposta
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Connection reset
Posted by Christian Posta <ch...@gmail.com>.
Maybe some third party monitors killing the connection?
On Tue, Dec 18, 2012 at 4:55 AM, ruiluis <ru...@eyesee.pt> wrote:
> Good day. I have several types of clients that connect to a topic using
> stomp. Sometimes after some use ( just some 7/8 messages) the users get
> disconnected and this error appears in the activemq log file after i try to
> send a message from the producer to the clients..
> its quite strange because the clients do not detect the connection
> failure...
>
> 2012-12-18 11:27:21,401 | DEBUG | Transport Connection to:
> tcp://127.0.0.1:1031 failed: java.net.SocketException: Connection reset |
> org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
> Transport: tcp:///127.0.0.1:1031@61613
> java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:189)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at
>
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50)
> at
>
> org.apache.activemq.transport.tcp.TcpTransport$2.fill(TcpTransport.java:612)
> at
>
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58)
> at
>
> org.apache.activemq.transport.tcp.TcpTransport$2.read(TcpTransport.java:597)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at
>
> org.apache.activemq.transport.stomp.StompWireFormat.readHeaderLine(StompWireFormat.java:155)
> at
>
> org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:148)
> at
>
> org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:170)
> at
>
> org.apache.activemq.transport.stomp.StompWireFormat.unmarshal(StompWireFormat.java:98)
> at
>
> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:229)
> at
> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:221)
> at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:204)
> at java.lang.Thread.run(Thread.java:722)
> 2012-12-18 11:27:21,405 | DEBUG | Unregistering MBean
>
> org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=stomp,Connection=ID_demoserver-50466-1355829271859-2_1
> | org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ Transport:
> tcp:///127.0.0.1:1031@61613
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta