activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Geer <ch...@cxtsoftware.com>
Subject Re: EOF Exception
Date Mon, 27 Jan 2014 17:08:08 GMT
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 <chris@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&amp;waitForStart=10000" />
> >     </bean>
> >
> > Netstat came back with nothing.
> >
> >
> > On Tue, Jan 21, 2014 at 4:01 PM, Rodrigo Ramos <crackduoro@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 <art@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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message