[
https://issues.apache.org/activemq/browse/AMQ-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59594#action_59594
]
Scott Clasen commented on AMQ-2245:
-----------------------------------
I see the same stack trace today in 5.3.1 after trying to force start a
BrokerService that was stopped. Is there a way to replace the ErrorBroker?
> Allow restart of embedded broker
> --------------------------------
>
> Key: AMQ-2245
> URL: https://issues.apache.org/activemq/browse/AMQ-2245
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.3.0
>
> Attachments: ActiveMQThreadBrokerFactory.java
>
>
> Currently we don't allow restarting the stopped broker and instead developers
> need to create another instance of the broker and start it. Usually this is a
> desired behavior and should remain a default one. But we should provide an
> option to people wanting to start stopped brokers. The proposed enhancement
> will introduce
> {code}
> public void start(boolean force);
> {code}
> method, which will force the broker to start.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
