4 Replies Latest reply on Jul 30, 2012 3:12 AM by Max Rydahl Andersen

    JBoss EAP 6 requires two stop commands to really stop

    henk de boer Master

      Using Eclipse 3.7.2, JBoss Tools 3.3 final, JBoss EAP 6.0.0 and Java SE 6 on OS X 10.6, I need to give the stop command twice before JBoss EAP 6 actually stops.

       

      The first time it says stopping and "Connecting to JBoss EAP 6.0 Runtime Server via JMX" for several seconds. Then the message goes away from the progress view, but seemingly nothing has happened. In debug view I see all the server threads are still there. The server runtime then moves back from the "stopping" status to "debugging". If I give the stop command again (via the Servers view), JBoss EAP stops nearly instantly.

       

      I've tried with a completely bare EAP, without any apps deployed to it, as well as with an app.

        • 1. Re: JBoss EAP 6 requires two stop commands to really stop
          Rob Stryker Master

          Hi Henk:

           

          This indicates that there is some error when stopping. Do you think you could open a jira and target it to me regarding this so I don't lose track of it?

           

          The two-stop situation was a fallback we added in for just these situations, so it's a good thing it's there, but obviously it's not ideal and is still pretty confusing for users.

           

          After the first stop, could you check your console view? Usually there are multiple consoles there. One should be for the running server, but another might be for the recently launched shutdown command. This might indicate what went wrong during the shutdown.

           

          Thanks again.

           

          - Rob

          • 2. Re: JBoss EAP 6 requires two stop commands to really stop
            henk de boer Master

            Hi,

            After the first stop, could you check your console view? Usually there are multiple consoles there. One should be for the running server, but another might be for the recently launched shutdown command. This might indicate what went wrong during the shutdown.

             

            Unfortunately there doesn't seem to be another console. The only console is the one that shows output from the running server, and the icon for switching consoles is grayed-out.

             

            There do are some entries in the error log though:

             

            !ENTRY org.eclipse.wst.server.core 4 0 2012-06-27 23:12:30.744
            !MESSAGE Server JBoss EAP 6.0 Runtime Server failed to stop
            

             

            and

             

            !ENTRY org.jboss.ide.eclipse.as.core 4 16973826 2012-06-27 23:12:00.722
            !MESSAGE The server was shutdown forcefully. All processes were terminated.
            

             

             

            Now there are some exceptions from a GlassFish plugin as well. Those are rather maddening ones that are triggered everytime I interact with the JBoss server runtime. With the JBoss AS 7.x server runtime they also happen, but don't seem to effect anything, e.g an excerpt:

             

            !ENTRY org.eclipse.jface 4 2 2012-06-27 23:12:06.370
            !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
            !STACK 0
            java.lang.NullPointerException
                      at com.sun.enterprise.jst.server.sunappsrv.actions.PreludeUpdateCenterAction.accept(PreludeUpdateCenterAction.java:171)
                      at com.sun.enterprise.jst.server.sunappsrv.actions.AppServerContextAction.selectionChanged(AppServerContextAction.java:238)
                      at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:143)
                      at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164)
                      at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
                      at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
                      at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
                      at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162)
                      at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188)
                      at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211)
                      at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:478)
                      at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241)
                      at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239)
                      at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233)
                      at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403)
                      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
            
            

             

            Before I'll create the Jira issue let me first investigate what happens on a fresh Eclipse 3.7.2.

             

            Thanks for your time!

            • 3. Re: JBoss EAP 6 requires two stop commands to really stop
              henk de boer Master

              henk de boer wrote:

               

              Before I'll create the Jira issue let me first investigate what happens on a fresh Eclipse 3.7.2.

               

              Using a fresh Eclipse 3.7.2 with only JBoss Tools installed (a small selection from JBoss Tools actually), JBoss 6 EAP starts and stops nearly instantly.

               

              In the Eclipse environment where it fails, there are some extra plug-ins and servers installed: the OpenShift, GlassFish and WebLogic (OEPE) server runtimes, the eGit and Mercurial plug-ins and finally the GAE plug-in.

              • 4. Re: JBoss EAP 6 requires two stop commands to really stop
                Max Rydahl Andersen Master

                hi Henk,

                 

                Could you open https://jira.jboss.org/jira/browse/JBIDE describing the setup ?

                 

                I can tell you that OpenShift, eGit and GAE should not affect any of this since those we use/test with already.

                 

                Could you try adding each of Glassfish, weblogic and mercurial plugins and retry the start/stop of EAP 6 and let us know when it stops working for you ?

                 

                (A more likely explanation is though that you have an older JBoss Tools version installed which is not compatible with EAP 6/JBoss 7.1.2 shutdown which we did have to fix in the JBoss Tools 3.3.x beta's)