[ https://issues.apache.org/activemq/browse/AMQ-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-2245.
--------------------------------

    Resolution: Fixed

Fixed in SVN revision 773569. 

Broker's context is not entirely cleaned on stop. I tried to find most of those places and cover them with a test case. If you experience a problem in behavior of the restarted broker, please reopen this issue with your configuration (and use case) 

> 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
>
>
> 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.