-
1. Re: Usage of auto-deploy-exploded="true" in Prod environment
jaikiran Jun 16, 2015 7:31 AM (in response to sridharthiyagarajan)1 of 1 people found this helpfulEarlier versions of JBoss AS (prior to version 7) had a problem wherein if you deployed an exploded application (i.e. as a folder) then the deployment scanner would sometimes pick up the deployment even before the application was fully copied over. This would cause deployment failures.
To prevent issues like these, JBoss AS7 and later versions now expect to find a marker file to trigger the deployment. The marker file should be placed (by the person who's copying over the deployment) in the deployments folder when the deployment is completely copied over and ready for deployment.
-
2. Re: Usage of auto-deploy-exploded="true" in Prod environment
sridharthiyagarajan Jun 17, 2015 12:13 AM (in response to sridharthiyagarajan)Many thanks for the response... Jaikiran. Here in Wildfly 8.2.0 AS, I am deploying an exploded EAR application in standalone/deployments folder and when starting the server, it generates test.ear.isdeploying marker file and after successful deployment, it generates test.ear.deployed marker file. So, this means there should not be any problem when deploying an exploded application in Wildfly 8.2.0 AS as marker files are getting generated by the server every time when starting the server.
-
3. Re: Usage of auto-deploy-exploded="true" in Prod environment
jaikiran Jun 17, 2015 1:30 AM (in response to sridharthiyagarajan)1 of 1 people found this helpfulI was actually talking about the .dodeploy marker, the presence of which triggers the application deployment for exploded deployments, when auto-deploy-exploded (is by default) false.
-
4. Re: Usage of auto-deploy-exploded="true" in Prod environment
sridharthiyagarajan Jun 17, 2015 4:56 AM (in response to jaikiran)Many thanks for the response.. Jaikiran. Marker files are generated by the server start up. So, should .dodeploy marker file be generated and copied manually in case of exploded deployment (with auto-deploy-exploded="false" which is default) ?
-
5. Re: Usage of auto-deploy-exploded="true" in Prod environment
sridharthiyagarajan Jun 18, 2015 4:48 AM (in response to sridharthiyagarajan)1 of 1 people found this helpful.dodeploy marker files gets generated for exploded application deployment (with auto-deploy-exploded="true") during server start and while deploying, it is .isdeploying and after successful deployment, it is .deployed in case if it is a failure, then it is .failed. I think the below WARN message can be ignored.
WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 5) JBAS015005: Reliable deployment behaviour is not possible when auto-deployment of exploded content is enabled (i.e. deployment without use of ".dodeploy"' marker files). Configuration of auto-deployment of exploded content is not recommended in any situation where reliability is desired. Configuring the deployment scanner's auto-deploy-exploded setting to "false" is recommended.
Many thanks .. Jaikiran.
-
6. Re: Usage of auto-deploy-exploded="true" in Prod environment
jameslivingston Jun 18, 2015 11:53 PM (in response to sridharthiyagarajan)1 of 1 people found this helpfulIf you are going to use the marker files, turn off auto-deploy-exploded="true" - that is for only when you want to do it without marker files (which is dangerous, as the message says).
-
7. Re: Usage of auto-deploy-exploded="true" in Prod environment
sridharthiyagarajan Jun 19, 2015 6:51 AM (in response to jameslivingston)Many thanks for the response.. James.