Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of rajdavies@gmail.com
 designates 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=Vski5NBkuFwhHZSWH+LjvbOTP0rbEvyS8b0KoY7uIgrNQE/GoJrZcObCm14zgDhzZq
         c/Fz0VQHUUw1Lz1cxKrciXlyTfKqaz5GFCTKDz9rCX3HZe6/Etwp16sZMd30F8sXOGB3
         33qruN4EPryqUqaiYphIt+RyPz1XE0HGE5CkY=
Message-Id: <3FB9E4D1-8CA0-4503-9714-EC2A5D4B330C@gmail.com>
From: Rob Davies <rajdavies@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <17775480.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: ActiveMQ Message Broker shut down without Exception
Date: Wed, 11 Jun 2008 12:49:03 +0100
References: <17771296.post@talk.nabble.com>
 <C4FD3CBD-77F3-40E1-BFB4-8DC3B277B503@gmail.com>
 <17775480.post@talk.nabble.com>

That looks like you're using ActiveMQ 4.1 - want to try 5.1 instead ?

On 11 Jun 2008, at 12:35, dolphin_cheng wrote:

>
>  Yes, there is nothing in the logs from Activemq to indicate why it =20=

> failed.
> In the logs from our project there is only exception "Could not =20
> connect to
> broker URL: tcp://159.226.2.169:61616?wireFormat.
> maxInactivityDuration=3D0. Reason: java.net.ConnectException: =
Connection
> refused".
>   I paste the content of start.out of AMQ:
> ACTIVEMQ_HOME: /home/agrid/activemq
> Loading message broker from: xbean:activemq.xml
> INFO  BrokerService                  - ActiveMQ 4.1.0-incubator JMS =20=

> Message
> Broker (localhost) is starting
> INFO  BrokerService                  - For help or more information =20=

> please
> see: http://incubator.apache.org/activemq/
> INFO  ManagementContext              - JMX consoles can connect to
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO  JDBCPersistenceAdapter         - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> INFO  DefaultDatabaseLocker          - Attempting to acquire the =20
> exclusive
> lock to become the Master broker
> INFO  DefaultDatabaseLocker          - Becoming the master on =20
> dataSource:
> org.apache.derby.jdbc.EmbeddedDataSource@19a8416
> INFO  JournalPersistenceAdapter      - Journal Recovery Started =20
> from: Active
> Journal: using 5 x 20.0 Megs at: /home/agrid/activemq/activemq-data/=20=

> journal
> INFO  JournalPersistenceAdapter      - Journal Recovered: 19 =20
> message(s) in
> transactions recovered.
> INFO  TransportServerThreadSupport   - Listening for connections at:
> tcp://condor.sdg.ac.cn:61616?wireFormat.maxInactivityDuration=3D0
> INFO  TransportConnector             - Connector openwire Started
> INFO  TransportServerThreadSupport   - Listening for connections at:
> ssl://condor.sdg.ac.cn:61617
> INFO  TransportConnector             - Connector ssl Started
> INFO  TransportServerThreadSupport   - Listening for connections at:
> stomp://condor.sdg.ac.cn:61613
> INFO  TransportConnector             - Connector stomp Started
> INFO  NetworkConnector               - Network Connector default-nc =20=

> Started
> INFO  BrokerService                  - ActiveMQ JMS Message Broker
> (localhost, ID:condor.sdg.ac.cn-38555-1213168854805-1:0) started
> INFO  BrokerService                  - ActiveMQ Message Broker =20
> (localhost,
> ID:condor.sdg.ac.cn-38555-1213168854805-1:0) is shutting down
> INFO  NetworkConnector               - Network Connector default-nc =20=

> Stopped
> INFO  TransportConnector             - Connector openwire Stopped
> INFO  TransportConnector             - Connector ssl Stopped
> INFO  TransportConnector             - Connector stomp Stopped
> INFO  BrokerService                  - ActiveMQ JMS Message Broker
> (localhost, ID:condor.sdg.ac.cn-38555-1213168854805-1:0) stopped
>
>
> rajdavies wrote:
>>
>> There's nothing in the logs from ActiveMQ to indicate why it failed ?
>>
>> On 11 Jun 2008, at 08:02, dolphin_cheng wrote:
>>
>>>
>>>  We use activemq 5.1.0 and deploy it in a linux system. Several
>>> days ago, I
>>> asked a question that EOFException can lead to broker shut down. But
>>> I found
>>> that even there is no EOFException the broker can shut down too. We
>>> are
>>> waiting for the solution vexedly, please help us ^_^
>>>  Thanks very much=EF=BC=81=EF=BC=81
>>> --=20
>>> View this message in context:
>>> =
http://www.nabble.com/ActiveMQ-Message-Broker-shut-down-without-Exception-=
tp17771296p17771296.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>
>>
>>
>
> --=20
> View this message in context: =
http://www.nabble.com/ActiveMQ-Message-Broker-shut-down-without-Exception-=
tp17771296p17775480.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>