You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Chris Geer <ch...@cxtsoftware.com> on 2014/01/19 16:07:54 UTC
EOF Exception
We've recently been getting a series of log messages that I can't quite
explain and was hoping someone can shed some light on the situation. We
consistently get these log messages every few minutes. The only thing
talking with ActiveMQ is our Camel routes using the ActiveMQ component. We
are on Camel 2.10.7 and ActiveMQ 5.6 inside Karaf 2.2.10. There doesn't
seem to be any issues with the functionality but I'm not sure why this
keeps happening. I'm assuming this that one of my camel routes is just
closing the connection improperly but I don't know how to fix it.
WARN | /127.0.0.1:61616 | FailoverTransport | 142 -
org.apache.activemq.activemq-core - 5.6.0 | Transport (tcp://127.0.0.1:61616)
failed, reason: java.io.EOFException, attempting to automatically reconnect
INFO | tiveMQ Task-7464 | FailoverTransport | 142 -
org.apache.activemq.activemq-core - 5.6.0 | Successfully reconnected to
tcp://localhost:61616
INFO | tiveMQ Task-7464 | FailoverTransport | 142 -
org.apache.activemq.activemq-core - 5.6.0 | Successfully connected to
tcp://localhost:61616
The more worrisome logs messages are the ones that follow. To my knowledge
I don't have anything running on port 47400 and can't track down what might
be trying to connect to it.
WARN | /127.0.0.1:47400 | Transport | 142 -
org.apache.activemq.activemq-core - 5.6.0 | Transport Connection to: tcp://
127.0.0.1:47400 failed: java.io.EOFException
WARN | xception Handler | Transport | 142 -
org.apache.activemq.activemq-core - 5.6.0 | Transport Connection to: tcp://
127.0.0.1:47400 failed:
org.apache.activemq.transport.InactivityIOException: Cannot send, channel
has already failed: tcp://127.0.0.1:47400
I've tried to look at the debug logs but still couldn't track down which
calls are triggering these messages. Could be log overload masking
something. Is there something specific to look for?
Chris
Re: EOF Exception
Posted by Christian Posta <ch...@gmail.com>.
well... correction, and just for completion... the default url is actually
failover:(tcp://localhost:61616)
On Mon, Jan 27, 2014 at 10:42 AM, Christian Posta
<ch...@gmail.com> wrote:
> That's correct. The default url in the ActiveMQConnectionFactory is
> tcp://localhost:61616
>
> https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQConnectionFactory.java#L91
>
> On Mon, Jan 27, 2014 at 10:08 AM, Chris Geer <ch...@cxtsoftware.com> wrote:
>> I think you are correct that there is something rogue out there not using
>> the connection pool and making it's own connection. It occurred to me that
>> if you use the Camel ActiveMQ component that by default it connects to
>> localhost over Openwire. So it probably means that someone screwed up their
>> camel route and didn't use the connection pool and it's working due to
>> defaults, not due to correct setup.
>>
>>
>> On Mon, Jan 27, 2014 at 10:04 AM, Christian Posta <christian.posta@gmail.com
>>> wrote:
>>
>>> You probably had something on your local machine open a connection to
>>> the broker on 61616. The logging indicates that the client used port
>>> 47400. Guess you have to figure out what rouge client is making
>>> connections if you expect everything to happen over the VM transport.
>>> Maybe shut off the openwire connector?
>>>
>>> On Tue, Jan 21, 2014 at 4:42 PM, Chris Geer <ch...@cxtsoftware.com> wrote:
>>> > Clients and broker are all running in the same karaf instance...in fact
>>> all
>>> > my "clients" are connecting using this connection setting:
>>> >
>>> > <bean id="activemqConnectionFactory"
>>> > class="org.apache.activemq.ActiveMQConnectionFactory">
>>> > <property name="brokerURL"
>>> > value="vm://default?create=false&waitForStart=10000" />
>>> > </bean>
>>> >
>>> > Netstat came back with nothing.
>>> >
>>> >
>>> > On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos <cr...@gmail.com>
>>> wrote:
>>> >
>>> >> Hello Chris,
>>> >>
>>> >> You can use netstat for identify what process is listening in 47400
>>> port,
>>> >> as root type:
>>> >>
>>> >> # netstat -punlt | grep 47400
>>> >>
>>> >>
>>> >> I hope will be helpfully
>>> >>
>>> >> Regards
>>> >>
>>> >>
>>> >> 2014/1/21 artnaseef <ar...@artnaseef.com>
>>> >>
>>> >> > Can you use a network packet sniffer, like tcpdump or wireshark?
>>> >> >
>>> >> > Those errors mean the other end of the TCP/IP connection was dropped
>>> >> > without
>>> >> > a higher-level cleanup of the connection. Could be the broker
>>> dropping
>>> >> and
>>> >> > coming back, network issues (timeouts, disconnects), or aborted
>>> >> connection
>>> >> > in the broker.
>>> >> >
>>> >> > The log lines posted are from the clients, right? Is there anything
>>> >> > corresponding on the broker side?
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > View this message in context:
>>> >> >
>>> >>
>>> http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
>>> >> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>> >> >
>>> >>
>>>
>>>
>>>
>>> --
>>> Christian Posta
>>> http://www.christianposta.com/blog
>>> twitter: @christianposta
>>>
>
>
>
> --
> Christian Posta
> http://www.christianposta.com/blog
> twitter: @christianposta
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: EOF Exception
Posted by Christian Posta <ch...@gmail.com>.
That's correct. The default url in the ActiveMQConnectionFactory is
tcp://localhost:61616
https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQConnectionFactory.java#L91
On Mon, Jan 27, 2014 at 10:08 AM, Chris Geer <ch...@cxtsoftware.com> wrote:
> I think you are correct that there is something rogue out there not using
> the connection pool and making it's own connection. It occurred to me that
> if you use the Camel ActiveMQ component that by default it connects to
> localhost over Openwire. So it probably means that someone screwed up their
> camel route and didn't use the connection pool and it's working due to
> defaults, not due to correct setup.
>
>
> On Mon, Jan 27, 2014 at 10:04 AM, Christian Posta <christian.posta@gmail.com
>> wrote:
>
>> You probably had something on your local machine open a connection to
>> the broker on 61616. The logging indicates that the client used port
>> 47400. Guess you have to figure out what rouge client is making
>> connections if you expect everything to happen over the VM transport.
>> Maybe shut off the openwire connector?
>>
>> On Tue, Jan 21, 2014 at 4:42 PM, Chris Geer <ch...@cxtsoftware.com> wrote:
>> > Clients and broker are all running in the same karaf instance...in fact
>> all
>> > my "clients" are connecting using this connection setting:
>> >
>> > <bean id="activemqConnectionFactory"
>> > class="org.apache.activemq.ActiveMQConnectionFactory">
>> > <property name="brokerURL"
>> > value="vm://default?create=false&waitForStart=10000" />
>> > </bean>
>> >
>> > Netstat came back with nothing.
>> >
>> >
>> > On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos <cr...@gmail.com>
>> wrote:
>> >
>> >> Hello Chris,
>> >>
>> >> You can use netstat for identify what process is listening in 47400
>> port,
>> >> as root type:
>> >>
>> >> # netstat -punlt | grep 47400
>> >>
>> >>
>> >> I hope will be helpfully
>> >>
>> >> Regards
>> >>
>> >>
>> >> 2014/1/21 artnaseef <ar...@artnaseef.com>
>> >>
>> >> > Can you use a network packet sniffer, like tcpdump or wireshark?
>> >> >
>> >> > Those errors mean the other end of the TCP/IP connection was dropped
>> >> > without
>> >> > a higher-level cleanup of the connection. Could be the broker
>> dropping
>> >> and
>> >> > coming back, network issues (timeouts, disconnects), or aborted
>> >> connection
>> >> > in the broker.
>> >> >
>> >> > The log lines posted are from the clients, right? Is there anything
>> >> > corresponding on the broker side?
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > View this message in context:
>> >> >
>> >>
>> http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
>> >> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >> >
>> >>
>>
>>
>>
>> --
>> Christian Posta
>> http://www.christianposta.com/blog
>> twitter: @christianposta
>>
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: EOF Exception
Posted by Chris Geer <ch...@cxtsoftware.com>.
I think you are correct that there is something rogue out there not using
the connection pool and making it's own connection. It occurred to me that
if you use the Camel ActiveMQ component that by default it connects to
localhost over Openwire. So it probably means that someone screwed up their
camel route and didn't use the connection pool and it's working due to
defaults, not due to correct setup.
On Mon, Jan 27, 2014 at 10:04 AM, Christian Posta <christian.posta@gmail.com
> wrote:
> You probably had something on your local machine open a connection to
> the broker on 61616. The logging indicates that the client used port
> 47400. Guess you have to figure out what rouge client is making
> connections if you expect everything to happen over the VM transport.
> Maybe shut off the openwire connector?
>
> On Tue, Jan 21, 2014 at 4:42 PM, Chris Geer <ch...@cxtsoftware.com> wrote:
> > Clients and broker are all running in the same karaf instance...in fact
> all
> > my "clients" are connecting using this connection setting:
> >
> > <bean id="activemqConnectionFactory"
> > class="org.apache.activemq.ActiveMQConnectionFactory">
> > <property name="brokerURL"
> > value="vm://default?create=false&waitForStart=10000" />
> > </bean>
> >
> > Netstat came back with nothing.
> >
> >
> > On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos <cr...@gmail.com>
> wrote:
> >
> >> Hello Chris,
> >>
> >> You can use netstat for identify what process is listening in 47400
> port,
> >> as root type:
> >>
> >> # netstat -punlt | grep 47400
> >>
> >>
> >> I hope will be helpfully
> >>
> >> Regards
> >>
> >>
> >> 2014/1/21 artnaseef <ar...@artnaseef.com>
> >>
> >> > Can you use a network packet sniffer, like tcpdump or wireshark?
> >> >
> >> > Those errors mean the other end of the TCP/IP connection was dropped
> >> > without
> >> > a higher-level cleanup of the connection. Could be the broker
> dropping
> >> and
> >> > coming back, network issues (timeouts, disconnects), or aborted
> >> connection
> >> > in the broker.
> >> >
> >> > The log lines posted are from the clients, right? Is there anything
> >> > corresponding on the broker side?
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >> >
> >>
> http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
> >> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >> >
> >>
>
>
>
> --
> Christian Posta
> http://www.christianposta.com/blog
> twitter: @christianposta
>
Re: EOF Exception
Posted by Christian Posta <ch...@gmail.com>.
You probably had something on your local machine open a connection to
the broker on 61616. The logging indicates that the client used port
47400. Guess you have to figure out what rouge client is making
connections if you expect everything to happen over the VM transport.
Maybe shut off the openwire connector?
On Tue, Jan 21, 2014 at 4:42 PM, Chris Geer <ch...@cxtsoftware.com> wrote:
> Clients and broker are all running in the same karaf instance...in fact all
> my "clients" are connecting using this connection setting:
>
> <bean id="activemqConnectionFactory"
> class="org.apache.activemq.ActiveMQConnectionFactory">
> <property name="brokerURL"
> value="vm://default?create=false&waitForStart=10000" />
> </bean>
>
> Netstat came back with nothing.
>
>
> On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos <cr...@gmail.com> wrote:
>
>> Hello Chris,
>>
>> You can use netstat for identify what process is listening in 47400 port,
>> as root type:
>>
>> # netstat -punlt | grep 47400
>>
>>
>> I hope will be helpfully
>>
>> Regards
>>
>>
>> 2014/1/21 artnaseef <ar...@artnaseef.com>
>>
>> > Can you use a network packet sniffer, like tcpdump or wireshark?
>> >
>> > Those errors mean the other end of the TCP/IP connection was dropped
>> > without
>> > a higher-level cleanup of the connection. Could be the broker dropping
>> and
>> > coming back, network issues (timeouts, disconnects), or aborted
>> connection
>> > in the broker.
>> >
>> > The log lines posted are from the clients, right? Is there anything
>> > corresponding on the broker side?
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> >
>> http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >
>>
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: EOF Exception
Posted by Chris Geer <ch...@cxtsoftware.com>.
Clients and broker are all running in the same karaf instance...in fact all
my "clients" are connecting using this connection setting:
<bean id="activemqConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL"
value="vm://default?create=false&waitForStart=10000" />
</bean>
Netstat came back with nothing.
On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos <cr...@gmail.com> wrote:
> Hello Chris,
>
> You can use netstat for identify what process is listening in 47400 port,
> as root type:
>
> # netstat -punlt | grep 47400
>
>
> I hope will be helpfully
>
> Regards
>
>
> 2014/1/21 artnaseef <ar...@artnaseef.com>
>
> > Can you use a network packet sniffer, like tcpdump or wireshark?
> >
> > Those errors mean the other end of the TCP/IP connection was dropped
> > without
> > a higher-level cleanup of the connection. Could be the broker dropping
> and
> > coming back, network issues (timeouts, disconnects), or aborted
> connection
> > in the broker.
> >
> > The log lines posted are from the clients, right? Is there anything
> > corresponding on the broker side?
> >
> >
> >
> > --
> > View this message in context:
> >
> http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
>
Re: EOF Exception
Posted by Rodrigo Ramos <cr...@gmail.com>.
Hello Chris,
You can use netstat for identify what process is listening in 47400 port,
as root type:
# netstat -punlt | grep 47400
I hope will be helpfully
Regards
2014/1/21 artnaseef <ar...@artnaseef.com>
> Can you use a network packet sniffer, like tcpdump or wireshark?
>
> Those errors mean the other end of the TCP/IP connection was dropped
> without
> a higher-level cleanup of the connection. Could be the broker dropping and
> coming back, network issues (timeouts, disconnects), or aborted connection
> in the broker.
>
> The log lines posted are from the clients, right? Is there anything
> corresponding on the broker side?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: EOF Exception
Posted by artnaseef <ar...@artnaseef.com>.
Can you use a network packet sniffer, like tcpdump or wireshark?
Those errors mean the other end of the TCP/IP connection was dropped without
a higher-level cleanup of the connection. Could be the broker dropping and
coming back, network issues (timeouts, disconnects), or aborted connection
in the broker.
The log lines posted are from the clients, right? Is there anything
corresponding on the broker side?
--
View this message in context: http://activemq.2283324.n4.nabble.com/EOF-Exception-tp4676514p4676607.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.