[jboss-jira] [JBoss JIRA] (AS7-6800) Clean unreferenced deployments from the content repository
[
https://issues.jboss.org/browse/AS7-6800?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-6800:
---------------------------------------
A possible simple solution to this is to pass the value of the "persistent"
attribute from the deployment resource into the repo and use it to track non-persistent
deployments and remove them when the content repo service stops. This is a bit dodgy
though. It doesn't cover cases where the service isn't stopped during shutdown;
e.g. a hard kill or where -Xrs is passed to the JVM thus disabling shutdown hook
execution. The latter seems to be used in init.d scripts. (The MSC service container is
stopped via a shutdown hook; it is that which causes services to stop.). A background
process that periodically cleans unreferenced content may work better.
Clean unreferenced deployments from the content repository
----------------------------------------------------------
Key: AS7-6800
URL: https://issues.jboss.org/browse/AS7-6800
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Brian Stansberry
Fix For: 8.0.0.Alpha1
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira