activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: ActiveMQ exceptions
Date Mon, 01 May 2006 08:52:44 GMT
3.0 is pretty old (over a year ago) - can you reproduce these problems
with 4.0-RC3?

On 4/29/06, ActiveMQ_User1 <web_address1@yahoo.com> wrote:
>
> Hi,
>
> We are using ActiveMQ 3.0 in conjuction with Mule and Spring in our app. We
> have setup ActiveMQ to run as a background windows service. Basically, the
> app polls a given directory for a file and then processes it accordingly,
> sending MQ messages and performing JDBC updates.
>
> We have been getting some exceptions logged in our mule and activemq log
> files recently, and I'd like to know if anyone here has any suggestions on
> what may be causing them and any work-arounds, if possible.
>
> Below are some of the exceptions:
>
> 2006-04-26 09:28:20,364 [TcpTransportChannel:
> Socket[addr=localhost/127.0.0.1,port=61616,localport=1085]] 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)
>
> Followed by:
>
> 2006-04-26 09:28:21,254 [Thread-0] ERROR JmsConnector stopConnector:309 -
> Failed to disconnect: Initialisation Failure: syncSendTimedOut: connection
> no longer OK
> org.mule.providers.ConnectException: Initialisation Failure:
> syncSendTimedOut: connection no longer OK
>         at org.mule.providers.jms.JmsConnector.doDisconnect(JmsConnector.java:236)
>         at
> org.mule.providers.AbstractConnector.disconnect(AbstractConnector.java:816)
>         at
> org.mule.providers.AbstractConnector.stopConnector(AbstractConnector.java:307)
>         at org.mule.MuleManager.stopConnectors(MuleManager.java:822)
>         at org.mule.MuleManager.stop(MuleManager.java:794)
>         at org.mule.MuleManager.dispose(MuleManager.java:352)
>         at org.mule.MuleManager$ShutdownThread.run(MuleManager.java:1340)
> Caused by: javax.jms.JMSException: syncSendTimedOut: connection no longer OK
>         at
> org.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:998)
>         at
> org.activemq.ActiveMQConnection.sendConnectionInfoToBroker(ActiveMQConnection.java:1210)
>         at org.activemq.ActiveMQConnection.close(ActiveMQConnection.java:614)
>         at org.mule.providers.jms.JmsConnector.doDisconnect(JmsConnector.java:233)
>         ... 6 more
>
>
> Any ideas as to what could be causing this?
>
> Also, in our activemq.log file we have been noticing that it says the JMS
> provider is stopping (for no apparent reason) and then it restarts after a
> few minutes or sometimes hours.
>
> Eg:
>
> 2006-04-21 14:27:07,612 [main           ] INFO  BrokerConnectorImpl
> - ActiveMQ connector started: TcpTransportServerChannel@tcp://hostname:61616
> 2006-04-21 14:27:07,612 [main           ] INFO  BrokerContainerImpl
> - ActiveMQ JMS Message Broker (ID:hostname-1911-1145600822003-0:0) has
> started
> 2006-04-21 14:27:17,315 [ocalport=61616]] INFO  BrokerContainerImpl
> - Adding new client: ID:hostname-1914-1145600835909-1:0 on transport:
> TcpTransportChannel: Socket[addr=/127.0.0.1,port=1916,localport=61616]
> 2006-04-23 13:01:39,734 [MQ ShutdownHook] INFO  BrokerContainerImpl
> - ActiveMQ Message Broker (ID:hostname-1911-1145600822003-0:0) is shutting
> down
> 2006-04-23 13:01:40,765 [MQ ShutdownHook] INFO  BrokerContainerImpl
> - Removing client: ID:hostname-1914-1145600835909-1:0 on transport:
> TcpTransportChannel: Socket[addr=/127.0.0.1,port=1916,localport=61616]
> 2006-04-23 13:01:42,093 [MQ ShutdownHook] INFO  BrokerConnectorImpl
> - ActiveMQ connector stopped: TcpTransportServerChannel@tcp://hostname:61616
> 2006-04-23 13:01:42,218 [MQ ShutdownHook] INFO  BrokerContainerImpl
> - ActiveMQ JMS Message Broker (ID:hostname-1911-1145600822003-0:0) stopped
> 2006-04-23 13:06:07,584 [main           ] INFO  BrokerContainerImpl
> - ActiveMQ 3.0 JMS Message Broker (ID:hostname-1059-1145768746922-0:0) is
> starting
>
>
> Does anyone know why this may be happening and if it is normal?
>
> I have since tried adding 'reliable' to the brokerURL - but am not sure if
> this will make a difference.
>
> Any ideas/suggestions would be much appreciated - thanks so much!
> --
> View this message in context: http://www.nabble.com/ActiveMQ-exceptions-t1529594.html#a4155128
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


--

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message