[jboss-jira] [JBoss JIRA] (WFCORE-213) Clean unreferenced items from the content repository

RH Bugzilla Integration (JIRA) issues at jboss.org
Wed Nov 26 09:33:40 EST 2014


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

RH Bugzilla Integration commented on WFCORE-213:
------------------------------------------------

Petr Kremensky <pkremens at redhat.com> changed the Status of [bug 1018026|https://bugzilla.redhat.com/show_bug.cgi?id=1018026] from ASSIGNED to VERIFIED

> Clean unreferenced items from the content repository
> ----------------------------------------------------
>
>                 Key: WFCORE-213
>                 URL: https://issues.jboss.org/browse/WFCORE-213
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Emmanuel Hugonnet
>             Fix For: 1.0.0.Alpha14
>
>
> The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example:
> 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed.
> 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed.
> Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases.



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


More information about the jboss-jira mailing list