[ http://issues.apache.org/jira/browse/GERONIMO-1818?page=all ]
Kevan Miller resolved GERONIMO-1818:
------------------------------------
Regression: [Regression]
Resolution: Fixed
The problem was the SystemProperties gbean was being started after Active MQ
was started. So, ActiveMQ was setting their shutdown handler. This causes the
active mq broker to stop prior to any other geronimo modules.
I made the ActiveMQContainerGBean dependent on the SystemProperties GBean. So,
the system property 'activemq.broker.disable-clean-shutdown' is now set to true
before ActiveMQ is started.
> ActiveMQ broker is shutting down before the rest of the server
> --------------------------------------------------------------
>
> Key: GERONIMO-1818
> URL: http://issues.apache.org/jira/browse/GERONIMO-1818
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: kernel
> Versions: 1.1
> Reporter: Kevan Miller
> Assignee: 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 like:
> 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: java.net.ConnectException: 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="org.apache.geronimo.system.properties.SystemProperties">
> <attribute name="systemProperties">
> activemq.broker.disable-clean-shutdown=true
> </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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
