Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <6556288.57061287068981090.JavaMail.jira@thor>
Date: Thu, 14 Oct 2010 11:09:41 -0400 (EDT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2962) Hanging at startup
In-Reply-To: <4290403.46991286366620375.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62584#action_62584 ] 

Gary Tully commented on AMQ-2962:
---------------------------------

so it looks like it is hanging in the same way as before. can you generate another thread dump of the hung broker with the sun jdk?

The connection errors, it looks like the vm transport is being used and each connection is trying to create another broker. 
Try using the tcp transport in the brokerURL in the ra.xml or jboss ra config or use waitForStart=20000 on the vm url. check out the vm transport reference for more detail

> Hanging at startup
> ------------------
>
>                 Key: AMQ-2962
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2962
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.4.1
>         Environment: Fedora Core 12
>            Reporter: Roelof Naude
>            Priority: Minor
>         Attachments: debug_traces_hanging.log, debug_traces_startup.log, thread_dump_during_hang.txt
>
>
> Noticed today the activemq was hanging during startup. Investigation revealed that it is tied to expiration of messages at startup. The only way to recover from this was to kill -9 the VM and delete the kahadb message store.
> Further testing was done whereby message expiry time was set to longer period. AMQ started up just fine. Another test was performed whereby:
> 1. subscribe for messages
> 2. send a few messages
> 3. disconnect consumer
> 4. send more messages (1 or 2 will do)
> 5. shutdown AMQ
> 6. wait for a time period exceeded the expiration time of the messages
> 7. start AMQ. at this time it should be hanging
> Logs and thread dumps attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.