Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <4172304.post@talk.nabble.com>
Date: Mon, 1 May 2006 18:17:51 -0700 (PDT)
From: ActiveMQ_User1 <web_address1@yahoo.com>
To: activemq-users@geronimo.apache.org
Subject: ActiveMQ shuts down..
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi,

We're using ActiveMQ 3.0 in our app (we are running it as a background
windows service). We've noticed that after running for a few hours, it stops
for no apparent reason. Here's what we get in our activemq log file, just
prior to it stopping.

2006-04-28 17:29:42,335 [MQ ShutdownHook] INFO  BrokerContainerImpl           
- ActiveMQ Message Broker (ID:myhost-4347-1146195103879-0:0) is shutting
down
2006-04-28 17:29:42,366 [MQ ShutdownHook] INFO  BrokerContainerImpl           
- Removing client: ID:myhost-4353-1146195118113-1:0 on transport:
TcpTransportChannel: Socket[addr=/127.0.0.1,port=4356,localport=61616]
2006-04-28 17:29:42,366 [MQ ShutdownHook] WARN  BrokerContainerImpl           
- No clientID available for client: brokerConnector-client:(3916193) :
TcpTransportChannel: Socket[addr=/192.168.39.247,port=51472,localport=61616]
2006-04-28 17:29:42,382 [MQ ShutdownHook] INFO  BrokerConnectorImpl           
- ActiveMQ connector stopped: TcpTransportServerChannel@tcp://myhost:61616


We're also using Mule - this is what we get in our mule log file:

2006-04-28 17:29:42,366 [TcpTransportChannel:
Socket[addr=localhost/127.0.0.1,port=61616,localport=4356]] WARN 
TcpTransportChannel doClose:496 - Peer closed connection 
java.io.EOFException
	at java.io.DataInputStream.readByte(Unknown Source)
	at
org.activemq.io.impl.AbstractDefaultWireFormat.readPacket(AbstractDefaultWireFormat.java:169)
	at
org.activemq.transport.tcp.TcpTransportChannel.run(TcpTransportChannel.java:308)
	at java.lang.Thread.run(Unknown Source)


Is this a problem that has been fixed in new versions of ActiveMQ? I am
considering upgrading to 3.2.2 - would this resolve the issue?

Thanks!
--
View this message in context: http://www.nabble.com/ActiveMQ-shuts-down..-t1535666.html#a4172304
Sent from the ActiveMQ - User forum at Nabble.com.