geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <>
Subject [jira] Commented: (GERONIMO-5444) Add slight delay during async startup of ActiveMQ
Date Fri, 09 Jul 2010 21:23:51 GMT


Kevan Miller commented on GERONIMO-5444:

I totally agree, in general. However, this is not normal processing.

ActiveMQ broker start up is a synchronous operation. The start() call will block until the
broker is fully started. So, in a default configuration, the broker will be completely started
(and there is never any delay processing).

To support Master-Slave/shared file system broker configurations, we have an asynchronous
start mode. For a "slave" broker, the start() call may block forever (i.e. the broker may
be a "slave" forever). So, we need an asynchronous method of starting the Broker service,
without blocking the Geronimo server startup. So, we start a thread to perform broker start
asynchronously. This code adds a "delay" to give the broker service enough time to start,
but won't block forever. 

In Master-Slave configurations, you need to configure "clients" to use multiple brokers (i.e.
they may not be connecting to a broker on the same Geronimo server). They should be configured
to use multicast protocols or failover protocols (configured with multiple broker uri's or
use new AMQ support for dynamic failover uri's).

If they delay time expires, this almost certainly means our broker is a "slave" broker. JMS
clients will then be connecting to the "master" running in a different geronimo server.

> Add slight delay during async startup of ActiveMQ
> -------------------------------------------------
>                 Key: GERONIMO-5444
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.2.1
>            Reporter: Kevan Miller
>             Fix For: 2.2.1, 3.0
> If ActiveMQ is being started asynchronously (e.g. for a master-slave shared file system
configuration), JMS clients may be started prior to the actual start of the server. We should
allow the doStart of the ActiveMQ service to have a delay, giving time for the service to
start, if this server ends up being the Master. 

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

View raw message