[
https://issues.jboss.org/browse/JBAS-9051?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-9051:
----------------------------------------
So for this issue, the "real issue" is what's in the issue title -- the
behavior of the scanner -- and not the fact that the server isn't responding.
There's another issue (e.g. JBAS-9010) for the server behavior.
I think the fix is to add a timeout (configurable, in seconds, default pretty long, say 60
secs) for how long the scanner should wait for a response.
Then wrap the call to the server to execute the composite op in a Callable, and hand it
off executor.submit(). Get back a Future and block on get(timeout).
Handle a TimeoutException by logging an error, cancelling the future, and going through
all the update tasks and invoking handleFailed with an appropriate error message.
FilesystemDeploymentService hangs during deploy and doesn't pick
any subsequent deployments
-------------------------------------------------------------------------------------------
Key: JBAS-9051
URL:
https://issues.jboss.org/browse/JBAS-9051
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: JBoss AS7 master
Reporter: jaikiran pai
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.Beta2
Attachments: boot.log, server.log, standalone-deployment-file-listing.txt,
td.log
FilesystemDeploymentService hangs while deploying certain file system based deployments.
The deployment being processed stays in .deploying marker state and any new deployments
added (along with a .dodeploy) to the deployment folder do not get processed. Attached is
a thread dump.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira