You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@activemq.apache.org by Rodrigo Ramos <cr...@gmail.com> on 2014/01/04 01:55:45 UTC

Transport Connection WARN

Hello everybody


Im having a lot of WARNs as follows:

014-01-03 18:48:01,288 | INFO  | Network connection between
vm://vass-broker-3#20 and tcp:///10.142.176.107:45959@61616(vass-broker-4)
has been established. |
org.apache.activemq.network.DemandForwardingBridgeSupport |
triggerStartAsyncNetworkBridgeCreation:
remoteBroker=tcp:///10.142.176.107:45959@61616, localBroker=
vm://vass-broker-3#20
2014-01-03 18:49:41,001 | WARN  | Transport Connection to: tcp://
10.142.176.106:43466 failed: java.io.EOFException |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///10.142.176.106:43466@61616
2014-01-03 18:49:41,002 | WARN  | Transport Connection to: tcp://
10.142.176.106:44756 failed: java.io.EOFException |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///10.142.176.106:44756@61616


is this a normal error?

Regards

Re: Transport Connection WARN

Posted by Rodrigo Ramos <cr...@gmail.com>.

Thanks my friend.


2014/1/4 artnaseef <ar...@artnaseef.com>

> Then you have nothing to worry about - the warning is actually a good
> thing,
> telling you the broker saw the end of the connection and should cleanup
> properly.
>
> Cheers.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Transport-Connection-WARN-tp4676004p4676018.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Transport Connection WARN

Posted by artnaseef <ar...@artnaseef.com>.

Then you have nothing to worry about - the warning is actually a good thing,
telling you the broker saw the end of the connection and should cleanup
properly.

Cheers.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Transport-Connection-WARN-tp4676004p4676018.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Transport Connection WARN

Posted by Rodrigo Ramos <cr...@gmail.com>.

Thanks for your answer.


In my case could be cause my team has used kill command.

Regards


2014/1/4 artnaseef <ar...@artnaseef.com>

> It's normal if the other end of the connection was closed without first
> shutting down the JMS connection.  This can easily happen under the
> following conditions:
>
> - JVM terminates abnormally
> - Server power failure
> - Network connection broken (e.g. disconnected ethernet wire)
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Transport-Connection-WARN-tp4676004p4676013.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Transport Connection WARN

Posted by artnaseef <ar...@artnaseef.com>.

It's normal if the other end of the connection was closed without first
shutting down the JMS connection.  This can easily happen under the
following conditions:

- JVM terminates abnormally
- Server power failure
- Network connection broken (e.g. disconnected ethernet wire)




--
View this message in context: http://activemq.2283324.n4.nabble.com/Transport-Connection-WARN-tp4676004p4676013.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.