[
https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on WFLY-122:
---------------------------------------
Yes, the solution will be something like that, although I don't want it as blocking
part of boot (we highly value boot time) but rather a side task kicked off during boot.
Emmanuel Hugonnet is working on this; he's working on a related Bugzilla and I just
saw now he wasn't assigned to this JIRA.
I just updated the title and description a bit to highlight the fact that this isn't
just about deployments.
Clean unreferenced items from the content repository
----------------------------------------------------
Key: WFLY-122
URL:
https://issues.jboss.org/browse/WFLY-122
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Emmanuel Hugonnet
Fix For: 9.0.0.CR1
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.1#6329)