[forge-issues] [JBoss JIRA] (FORGE-2146) FurnaceImpl sets the status to STOPPED before clearing state

George Gastaldi (JIRA) issues at jboss.org
Thu Nov 13 17:16:29 EST 2014


    [ https://issues.jboss.org/browse/FORGE-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019912#comment-13019912 ] 

George Gastaldi commented on FORGE-2146:
----------------------------------------

[~lincolnthree], should we allow Furnace containers to be reused (eg: start() allowed to be called after stop() is called)? If so then I agree with Jess, since we should not unset configuration state (eg: repositories) for that to happen.

> FurnaceImpl sets the status to STOPPED before clearing state
> ------------------------------------------------------------
>
>                 Key: FORGE-2146
>                 URL: https://issues.jboss.org/browse/FORGE-2146
>             Project: Forge
>          Issue Type: Bug
>            Reporter: Jess Sightler
>
> See also:
> https://github.com/forge/furnace/blob/master/container/src/main/java/org/jboss/forge/furnace/impl/FurnaceImpl.java#L253
> This should not set STOPPED before the call to cleanup(). Also, perhaps there should be some reconsideration to automatically calling cleanup() in this state?
> I am surprised as an API user to see that all repos are automatically removed from an instance after the container is closed.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the forge-issues mailing list