[
https://issues.jboss.org/browse/AS7-3163?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-3163:
----------------------------------
Summary: Handling of cancellation of ModelController operations is broken
(was: FS deployment scanner fails completely after single timeout failure)
Priority: Blocker (was: Major)
Assignee: Brian Stansberry (was: Jason Greene)
Git Pull Request:
https://github.com/jbossas/jboss-as/pull/1156 (was:
https://github.com/jbossas/jboss-as/pull/1156)
Component/s: Domain Management
(was: Server)
Forum Reference:
http://community.jboss.org/thread/176829 (was:
http://community.jboss.org/thread/176829)
Changing JIRA title to match the core issue.
Handling of cancellation of ModelController operations is broken
----------------------------------------------------------------
Key: AS7-3163
URL:
https://issues.jboss.org/browse/AS7-3163
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1
Reporter: Brent Douglas
Assignee: Brian Stansberry
Priority: Blocker
Attachments: mbeans.txt, stacktrace.txt
When deploying via the the FS deployment scanner a timeout causes all subsequent
deployments to fail with further timeout failures.
The problem appears to be that FileSystemDeploymentService submits the DeployTask for
timed execution it acquires a lock it's copy of ContainerStateMonitor (via
OperationContextImpl.acquireContainerMonitor()). When a timeout exception is throw by the
first failure this lock is never cleaned up which results in all further deployment jobs
to hang on ContainerStateMonitor.await (line 161).
Restarting the server clears the monitor and allows the scanner to be reused as normal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira