4 Replies Latest reply on Dec 29, 2010 5:54 PM by piotrekde

    Automatic re-deployment: stopped but not starting

    piotrekde Newbie

      Hi,

       

      I have some strange issue with JBoss-5.0.0 (with hornetq). When I made some change in my application and redeploy it (just by deleting .ear  in deploy directory and then copying the newly created one), my beans are properly stopped, but nothing more happens.

       

      Here is some part of logs:

       

      00:28:02,796 INFO  [SessionSpecContainer] Stopping jboss.j2ee:ear=sis.ear,jar=sis.jar,name=BasicRequestSenderBean,service=EJB3
      00:28:02,871 INFO  [EJBContainer] STOPPED EJB: eu.smoothit.sis.communication.intersis.request.BasicRequestSenderBean ejbName: BasicRequestSenderBean

      00:28:02,796 INFO  [SessionSpecContainer] Stopping jboss.j2ee:ear=app.ear,jar=app.jar,name=DefaultRequestBean,service=EJB3

      00:28:02,871 INFO  [EJBContainer] STOPPED EJB: pl.edu.uj.DefaultRequestBean ejbName: DefaultRequestBean

       

      I use IDE without built-in j2ee support, so ANT is my build/deploy tool. Also it's a project I've joined recently so I don't know if it's behavior configured intentionally (is it possible to do so?). Where to look for answer?  (I've never met with anything like that before.)

       

      Thanks,

      Piotr

        • 1. Re: Automatic re-deployment: stopped but not starting
          Wolf-Dieter Fink Master

          I'm not sure if it helps but

          do not remove your .ear,

          copy the new .ear into the same filesystem (not to the deploy directory)

          use 'move' instead of copy to replace the .ear

           

          copy is not always an atomar operation.

          • 2. Re: Automatic re-deployment: stopped but not starting
            piotrekde Newbie

            Thanks for answer!

            I've done as you suggested but it didn't help - it is the same issue as previously - EAR is stopped but not started.

            The same when I do it from system command-line level. Also, I've experimented with file permissions (my OS is Linux), but even after 777 permission there is still the same problem.

             

            This is my hdscanner-jboss-beans.xml (I think it's standard for this version of JBoss)

             

            <?xml version="1.0" encoding="UTF-8"?>
            <!--
                Hot deployment scanning
               
                $Id: profileservice-jboss-beans.xml 79345 2008-10-10 13:46:55Z emuckenhuber $
            -->
            <deployment xmlns="urn:jboss:bean-deployer:2.0">
                <!-- Hotdeployment of applications -->
                <bean name="HDScanner"
                    class="org.jboss.system.server.profileservice.hotdeploy.HDScanner">
                    <property name="mainDeployer"><inject bean="MainDeployer"/></property>
                    <property name="controller"><inject bean="jboss.kernel:service=KernelController"/></property>
                    <property name="profileService"><inject bean="ProfileService"/></property>
                    <property name="scanPeriod">5000</property>
                    <property name="scanThreadName">HDScanner</property>
                </bean>
            </deployment>

            <?xml version="1.0" encoding="UTF-8"?>

             

            <!--

                Hot deployment scanning

             

                $Id: profileservice-jboss-beans.xml 79345 2008-10-10 13:46:55Z emuckenhuber $

            -->

            <deployment xmlns="urn:jboss:bean-deployer:2.0">

             

                <!-- Hotdeployment of applications -->

                <bean name="HDScanner"

                    class="org.jboss.system.server.profileservice.hotdeploy.HDScanner">

                    <property name="mainDeployer"><inject bean="MainDeployer"/></property>

                    <property name="controller"><inject bean="jboss.kernel:service=KernelController"/></property>

                    <property name="profileService"><inject bean="ProfileService"/></property>

                    <property name="scanPeriod">5000</property>

                    <property name="scanThreadName">HDScanner</property>

                </bean>

            </deployment>

             

            • 3. Re: Automatic re-deployment: stopped but not starting
              Wolf-Dieter Fink Master

              Could you attach a server.log with startup and direct redeploy attempt?

              • 4. Re: Automatic re-deployment: stopped but not starting
                piotrekde Newbie

                I found a solution.

                Because redeployment has been failing, I wasn't waiting for JBoss to shutdown - just killing it (kill -9). Server hadn't change to stop correctly so that I haven't seen in syslog that in fact it stucked on undeploying one bean. Everything looked correctly as everything finished without errors, but actually undeployment process stucked. My fault, and solution : just be patient and do not kill JBoss

                 

                Thanks!