[jboss-jira] [JBoss JIRA] (AS7-3163) FS deployment scanner fails completely after single timeout failure
Brian Stansberry (Commented) (JIRA)
jira-events at lists.jboss.org
Fri Jan 6 18:06:10 EST 2012
[ https://issues.jboss.org/browse/AS7-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654444#comment-12654444 ]
Brian Stansberry commented on AS7-3163:
---------------------------------------
Can you post the entire stack trace when this happens? Even better, if you can start
1)Run jconsole
2) attach to the server process
3) Go to the jboss.msc:type=container,name=jboss.as mbean
4) Run the "dumpServicesAsString" operation
5) Copy and paste the operation return value from the dialog box to a file
6) Attach that file here
If possible, please attach the deployment or mail it to me (briandotstansberryatredhatdotcom).
The timeout reported by the FS scanner is a symptom. The real issue is whatever is causing ContainerStateMonitor to not progress.
> FS deployment scanner fails completely after single timeout failure
> -------------------------------------------------------------------
>
> Key: AS7-3163
> URL: https://issues.jboss.org/browse/AS7-3163
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.1.0.CR1
> Reporter: Brent Douglas
> Assignee: Jason Greene
>
> 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
More information about the jboss-jira
mailing list