geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jules Gosnell (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1818) ActiveMQ broker is shutting down before the rest of the server
Date Wed, 10 May 2006 10:21:05 GMT
    [ ] 

Jules Gosnell commented on GERONIMO-1818:

It looks like support for this property/fn-ality disappeared between 3.2.2 and 4.0-M4 - it
is also not in trunk at the time of this comment.

Geronimo seems to be on AMQ 4.0-SNAPSHOT - so I would expect this issue to be present. :

[jules@smilodon geronimo-trunk]$ find . -name pom.xml | xargs grep activeMqVersion
./pom.xml:    <activeMqVersion>4.0-SNAPSHOT</activeMqVersion>

WADI is being bitten by the same problem:

I have posted activemq-user asking for help. As soon as WADi has a fix, I will report back.


> ActiveMQ broker is shutting down before the rest of the server
> --------------------------------------------------------------
>          Key: GERONIMO-1818
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: kernel
>     Versions: 1.1
>     Reporter: Kevan Miller
>      Fix For: 1.1

> The ActiveMQ broker is shutting down before the rest of the Geronimo server. This can
result in several errors (deadlock and infinite recursion) as well as annoying info messages
> Server shutdown begun              
> 13:49:11,666 INFO  [ActiveMQAsfEndpointWorker] Endpoint connection to JMS broker failed:
Initialization of TcpTransportChannel failed. URI was: tcp://localhost:61616 Reason:
Connection refused
> 13:49:11,666 INFO  [ActiveMQAsfEndpointWorker] Endpoint will try to reconnect to the
JMS broker in 30 seconds
> Server shutdown completed
> In the past, these problems have been avoided by the following in the activemq-broker
config plan:
>     <gbean name="SystemProperties" class="">
>         <attribute name="systemProperties">
>         </attribute>
>     </gbean>
> However, it doesn't seem to be working. Seem to be 3 possible explanations:
> 1) The SystemProperties GBean is not working.
> 2) The order of GBean shutdown has been changed and the broker is being stopped before
clients are stopped.
> 3) ActiveMQ 3.2.4 disable-clean-shutdown processing is broken.
> Most likely explanation is 1) or 2)...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message