2 Replies Latest reply on Oct 26, 2011 8:36 PM by daveryan

    Application gets re deployed

    Chinmoy Chakraborty Newbie

      Hello,

       

      I am using using JBoss AS 7.0.2 and we are using 'auto-deploy-exploded ' to deploy our application. Following is the configuration for 'standalone' mode.

      ...

      <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0">

                  <deployment-scanner name="default" path="deployments" scan-enabled="true" scan-interval="5000" relative-to="jboss.server.base.dir" auto-deploy-zipped="false" auto-deploy-exploded="true" deployment-timeout="60"/>

              </subsystem>...

       

      What we see is that the app gets restared in every scan-interval and the session gets invalid and its almost impossible to work. What are the possible ways when an app can get re-deployed? Does it re deploy with modification of any file (e.g xml, log, class, txt etc)? We need to debug our system and find out what is going wrong. Please help.

       

       

      Chinmoy

        • 2. Re: Application gets re deployed
          daveryan Newbie

          The Deployment Scanner's readme file seems to suggest that any changes will trigger the redploy, per the text quoted below. This is why you can use the unix touch command to update the file's access and modification timestamps and trigger redeployment.

           

          The filesystem deployment scanner in AS 7 and later works differently from

          previous JBoss AS releases. The scanner can operate in one of two different

          modes, depending on whether it will directly monitor the deployment content

          in order to decide to deploy (or redeploy) it.

           

           

          1) Auto-deploy mode: The scanner will directly monitor the deployment content,

          automatically deploying new content and redeploying content whose timestamp

          has changed. This is similiar to the behavior of previous AS releases, although

          there are differences:

           

           

          a) A change in any file in an exploded deployment triggers redeploy. Because

          EE 6 applications do not require deployment descriptors, there is no attempt

          to monitor deployment descriptors and only redeploy when a deployment

          descriptor changes.

          b) The scanner will place marker files in this directory as an indication of

          the status of its attempts to deploy or undeploy content.

           

           

          Are you using autodeployment for any specific reason? A development project? It might save you some trouble to use manual deployment and redeploy your applications with the .dodeploy marker file. Otherwise the Management Console or Management CLI is the preferred method of application management.