Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Fri, 13 Jun 2014 01:55:00 -0700 (PDT)
From: sdkrum <sorenk@uninett.no>
To: users@activemq.apache.org
Message-ID: <1402649700005-4682119.post@n4.nabble.com>
Subject: activemq dies without warning or hint
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi!

I am using acitevemq (version 5.9) in a standard installation (apart from
the java memory, which we raised to 2 gb ) for a while now, but lately it
behaves strange. Under some load (mostly over one or topic) the activemq
process dies without further notice. I do not find anything in the log file
( data/activemq.log ).

Here is a small hint i found (but i have no idea if it has anything to do
with the process dying:=20

2014-06-12 16:16:48,188 | INFO  | Initializing Spring FrameworkServlet
'dispatcher' | /admin | main
2014-06-12 16:30:19,476 | WARN  | Transport Connection to:
tcp://127.0.0.1:48661 failed: java.net.SocketException: Connection reset |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///127.0.0.1:48661@61616
2014-06-13 07:46:31,432 | INFO  | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@5135e781: startup date [Fri
Jun 13 07:46:31 CEST 2014]; root of context hierarchy |
org.apache.activemq.xbean.XBeanBrokerFactory$1 | main

ActiveMq was started at 16:16 and I know that the server was alive until
about 21:00 and so i started it again next morning, as you see in the log.

Any kind of help is appreciated. I looked a bit around in the documentation=
,
but did not find a hint where to start searching.

Kind regards

S=C3=B8ren Krum
So i have some questions: I found in config some log configuration files
(log4j.properties/logging.properties), but i do not really know how to
change them so that i find a possible reason for the server crashing. The
clients using the jms are all mule instances, but i am not sure if their lo=
g
output helps in finding the issue.


--
View this message in context: http://activemq.2283324.n4.nabble.com/activem=
q-dies-without-warning-or-hint-tp4682119.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.