[jboss-jira] [JBoss JIRA] (WFLY-3198) Reenabling an application prevents it from deployement after a restart
Brian Stansberry (JIRA)
issues at jboss.org
Wed Apr 2 09:07:13 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958470#comment-12958470 ]
Brian Stansberry commented on WFLY-3198:
----------------------------------------
A thought for future improvement (not required to resolve this issue):
We should look into using the management API notification stuff Jeff Mesnil has done/is doing. The scanner subsystem can register listeners and the deployment ops can emit events. This can be used to keep the scanner aware of changes to the deployments part of the management model independent of the periodic scans.
This would close a gap that exists where the scan could be configured to run infrequently (say 10 mins), the .undeployed app gets deployed via console, and then before the scanner runs again and cleans out the .undeployed, the server is reloaded/restarted.
> Reenabling an application prevents it from deployement after a restart
> ----------------------------------------------------------------------
>
> Key: WFLY-3198
> URL: https://issues.jboss.org/browse/WFLY-3198
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ConfigAdmin
> Affects Versions: 8.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
>
> After disabling and then re-enabling the application, I don't see Application.war.deployed; I still see Application.war.undeployed.
> That explains why it doesn't get deployed after restart.
--
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
More information about the jboss-jira
mailing list