[
https://issues.apache.org/jira/browse/QPID-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063882#comment-13063882
]
Robbie Gemmell commented on QPID-2794:
--------------------------------------
Hi Danushka,
The broker startup refactoring I mentioned above has now been committed (mainly
QPID-2815). This provides a cleaner way to configure and start Broker instances
within the same JVM as other components, giving ability for the calling
applications to control exception handling and isolating the presence of
System.exit() calls in the Main class, outwith the actual startup/shutdown code
path. As a result of this I am going to close QPID-3323 and QPID-2794.
You can see example of how to use and configure one of the new Broker instances
by looking at the now significantly reduced Main class. Please let us know if
you have any problems using the refactored system to achieve your goal and we
can look how best to resolve the issue.
Regards,
Robbie
> Broker shutdown logic needs changing to run inside another process
> ------------------------------------------------------------------
>
> Key: QPID-2794
> URL: https://issues.apache.org/jira/browse/QPID-2794
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Danushka Menikkumbura
> Assignee: Robbie Gemmell
> Attachments: QPID-2794.patch
>
>
> At the moment the broker shutdown terminates the JVM which is a problem when
> the broker runs inside another process.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
