activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan E <>
Subject Hang during startup of internal activemq in appserver cluster using persistance.
Date Mon, 05 Nov 2007 14:07:25 GMT


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
    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

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

    Should this really be executing in the startupthread in the resource
    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:
Sent from the ActiveMQ - User mailing list archive at

View raw message