Brian Stansberry [
http://community.jboss.org/people/brian.stansberry] created the
discussion
"Re: Thoughts on filesystem action driven hot deployment"
To view the discussion, visit:
http://community.jboss.org/message/598635#598635
--------------------------------------------------------------
David Lloyd argued against the .failed files essentially because of the problem you raise.
The true representation of the state of the server is in the standalone.xml file, not in
these marker files.
The FS scanner is a client to the core server in pretty much the same way that a user
using the CLI is and the someone using web console will be. It detects changes on the
filesystem, makes requests to the core server management layer and the writes up .failed,
.deployed etc based on what it response it gets. Those files represent the client view of
the system though; if the server doesn't respond, the FS scanner eventually gives up
and marks a failure. But because the server didn't respond the FS scanner doesn't
really know the true state on the server side.
The server isn't responding probably due to JBAS-9010, which is being worked. The
"Failed to execute deployment operation in allowed timeout [60]" message needs
to be beefed up to make it clear that this is an anomalous situation, the scanner
doesn't know what happened, and the user needs to investigate and clean up.
https://issues.jboss.org/browse/JBAS-9020 https://issues.jboss.org/browse/JBAS-9020 will
help with the cleanup issue. Currently we don't track where deployment content comes
from, and we treat all content the same, whether it was scanned in from deployments/ or
installed into the system via CLI or web console. As a result, following reboot we lose
track of whether stuff that was installed by the scanner is no longer present and needs to
be undeployed.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/598635#598635]
Start a new discussion in JBoss AS7 Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]