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 lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <13587446.post@talk.nabble.com>
Date: Mon, 5 Nov 2007 06:07:25 -0800 (PST)
From: Johan E <johan.eke@gmail.com>
To: users@activemq.apache.org
Subject: Hang during startup of internal activemq in appserver cluster using
 persistance.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Environment:

WebSphere Applicationserver 6.1 ND
Oracle 10g
ActiveMQ 4.1.1
Using activemq_ra resource adapter.


ActiveMQ configuration:
Persistans using Oracle database


Two questions.

#1. When starting up the cluster of application servers only one application
server
    starts up correctly. The rest of thes servers hang. Doing a thread dump
on the jvm
    for the hanging applicationservers shows the startup thread hanging on
the 

    class DefaultDatabaseLocker
    ...
    .....
    boolean answer = statement.execute();   <--- Hangs here
    .....
    ...

    Should this really be executing in the startupthread in the resource
adapter
    and not spawned of into a separate process ? Since this code allways
will hang in 
    a wait since the first server has done "select for update" ?


#2. Would the code above not result in a hanging thread in all JVM:s except
the one
    owning the lock? What happens when we want to stop the application in
the JEE container
    would it not result in the shutdown also hanging waiting for this thread
?
-- 
View this message in context: http://www.nabble.com/Hang-during-startup-of-internal-activemq-in-appserver-cluster-using-persistance.-tf4751821s2354.html#a13587446
Sent from the ActiveMQ - User mailing list archive at Nabble.com.