1 2 Previous Next 17 Replies Latest reply on Dec 4, 2008 10:59 AM by Peter Johnson

    JBoss as Windows service - stopping the service powers down

    jonathanztaub Newbie

      Browsing the internet, I found the following describing on how to setup JBoss as a Windows service - http://wiki.jboss.org/wiki/JBossNativeWindows

      I was able to successfully install it as a service.
      The weird and ANNOYING issue is that when I stop the service from within the Services administrative tool, it causes the machine to power down.
      Am I missing something here? This is MOST annoying.

        • 1. Re: JBoss as Windows service - stopping the service powers d
          jaikiran pai Master

           

          when I stop the service from within the Services administrative tool, it causes the machine to power down.


          I haven't heard of that before. Which version of JBoss Native and which version of JBoss and Java? Also which Windows operating system? Are you sure you downloaded the correct JBossNative for your OS?

          • 2. Re: JBoss as Windows service - stopping the service powers d
            jaikiran pai Master

            And when you shutdown the service, there's a shutdown.log created in %JBOSS_HOME%\bin folder. Can you post its contents?

            • 3. Re: JBoss as Windows service - stopping the service powers d
              Peter Johnson Master

              I have JBossAS running as a service on a Windows 2003 server and I shut it down every night for the backup and the server has never shut down.

              Also post the results of this command (replace service-name with the service name in service.bat):

              sc sq service-name

              • 4. Re: JBoss as Windows service - stopping the service powers d
                jonathanztaub Newbie

                 

                "PeterJ" wrote:
                I have JBossAS running as a service on a Windows 2003 server and I shut it down every night for the backup and the server has never shut down.

                Also post the results of this command (replace service-name with the service name in service.bat):

                sc sq service-name


                I'm not home right now but I do remember I downloaded the latest version - 2.0.4 for windows (about 1.0 MB).
                Mayhap I downloaded the wrong thing?

                Also, I'm administering this remote Windows 2003 server which I'm new too. I have a hard time getting what exactly is installed and what hardware it is. I believe it is 32 bit as the JVM 1.6_07 for windows 32 works fine on it and there lots of x86 in the hardware profile, which I believe means it is a 32 bit machine. Correct me if I'm wrong.

                • 5. Re: JBoss as Windows service - stopping the service powers d
                  jonathanztaub Newbie

                  Forgot..... I'm running JBoss 4.2.3.
                  The service.bat had JBoss 5 for various description messages.
                  Perhaps it is incompatiable with 4.2.3?

                  • 6. Re: JBoss as Windows service - stopping the service powers d
                    Peter Johnson Master

                    JBoss Native 2.0.4 is the latest version, and yes it names the service JBAS50SVC in anticipation of the JBossAS 5.0 release, but I have used 2.0.4 with both AS 4.2.2 and 5.0.0.CR1 without any problems (it should work with 4.2.3 with no problems).

                    One way to tell if you are running the 64-bit Windows is if you have both a Program Files and a Program Files(x86) directory. There are other ways also (and if I was at home where I am running 640bit Vista, I could tell you), most likely by looking the My Computer | Properties or at System Information.

                    My guess would be that if you see a lot of x86 stuff, then you have a 64-bit system and the stuff you are looking at is compiled for 32-bit - the 64-bit Windows will run 32-bit software. Therefore, you can run a 32-bit JVM on 64-bit Windows, so that is not a clear indication of the OS type.

                    Regardless of all that, you should ensure that the JBoss Native you are using matches the OS type - that is, if the OS is 64-bit, you need the 64-bit variation of JBoss Native.

                    • 7. Re: JBoss as Windows service - stopping the service powers d
                      jonathanztaub Newbie

                      When JBoss starts, I see:
                      OS-System: Windows 2003 5.2,x86

                      There aren't any x86 related directories.
                      I also installed MySQL for Windows and I didn't download the 64bit installation. Whatever the underlying hardware is, at the end all that matters is what the OS is running as, I believe. Please correct me if I'm wrong.

                      • 8. Re: JBoss as Windows service - stopping the service powers d
                        jonathanztaub Newbie

                        I have verified that this is a 32bit machine.
                        I downloaded the JBoss Native 2.0.4 Win32, unzipped it and put it under:

                        C:\Program Files\jboss-4.2.3.GA\jboss-native-2.0.4-windows-x86-ssl

                        I'm using JRE 1.6_07 (doubt if it matters).

                        I also observed this behavior on my desktop machine at work, which is a Windows XP. I'm out of ideas.

                        • 9. Re: JBoss as Windows service - stopping the service powers d
                          jaikiran pai Master

                          Okay, lets start looking at the shutdown.log and also the output of the following:

                          "PeterJ" wrote:

                          Also post the results of this command (replace service-name with the service name in service.bat):

                          sc sq service-name



                          Do the "Event Logs" of Windows show anything as to why the system shutdown?

                          • 10. Re: JBoss as Windows service - stopping the service powers d
                            Peter Johnson Master

                            I just now verified correct operation on XP SP2 using Native 2.0.4, AS 4.2.3, JDK 6u7.

                            Is the shutdown orderly, or does the system just suddenly power off?

                            Post the settings for the System and Recovery properties, in the System Failure area.

                            Also, get the listdlls utility from sysinternals. With jbossas running, open a command prompt and enter:

                            listdlls java

                            Post the results that pertain to jbossas. As do:

                            listdlls jbosssvc

                            and post those results. The listdlls output will let us know if there is an unusual DLL that got loaded into the JVMs address space.

                            • 11. Re: JBoss as Windows service - stopping the service powers d
                              jonathanztaub Newbie

                              Sorry for the late response, as I was super busy with lots of stuff.
                              Here is more information:

                              run.log:

                              19:56:24,343 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@1847a42(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@1e61582 destination=queue/ServiceRequest isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
                              org.jboss.mq.SpyJMSException: Asynchronous close from server.; - nested throwable: (java.io.IOException: Close request from the server or transport layer.)
                              


                              shutdown.log:
                              Shutting down JBoss Application Server 4.2.3 [2008-08-12 22:26:04]
                              A system shutdown is in progress.(1115)
                              Shutdown JBoss Application Server 4.2.3 service [2008-08-12 22:26:04]
                              


                              sc qc jboss:
                              SERVICE_NAME: jboss
                               TYPE : 110 WIN32_OWN_PROCESS (interactive)
                               START_TYPE : 2 AUTO_START
                               ERROR_CONTROL : 1 NORMAL
                               BINARY_PATH_NAME : "C:\Program Files\jboss-4.2.3.GA\jboss-native-2.0.4-windows-x86-ssl\bin\jbosssvc.exe" -r JBOSS
                               LOAD_ORDER_GROUP :
                               TAG : 0
                               DISPLAY_NAME : JBoss Application Server 4.2.3
                               DEPENDENCIES : Tcpip
                               : Afd
                               SERVICE_START_NAME : LocalSystem
                              


                              For the time being, I'm stopping JBoss using the shutdown.bat, in order to avoid machine shutdown. I observed this behavior on a dev box I have at work as well.

                              • 12. Re: JBoss as Windows service - stopping the service powers d
                                Peter Johnson Master

                                The service description looks OK, but I cringe at seeing JBossAS installed in Program Files - having spaces in a path can cause some Java libraries fits. I keep mine at d:\opt\jboss\jboss-4.2.3.GA. If you move it out of Program Files and the problem goes away, I will add this problem to my growing list of things that can go wrong when running Java apps in a path with spaces in it.

                                I was hoping that "sc qc" would also list the services that the jboss service depends on, but it doesn't. Could you look that up in the services manager window? It is the Dependencies tab on the Properties dialog box for the service.

                                Also, please provide the information I asked for in my prior post.

                                • 13. Re: JBoss as Windows service - stopping the service powers d
                                  jonathanztaub Newbie

                                   

                                  "PeterJ" wrote:
                                  The service description looks OK, but I cringe at seeing JBossAS installed in Program Files - having spaces in a path can cause some Java libraries fits. I keep mine at d:\opt\jboss\jboss-4.2.3.GA. If you move it out of Program Files and the problem goes away, I will add this problem to my growing list of things that can go wrong when running Java apps in a path with spaces in it.

                                  I was hoping that "sc qc" would also list the services that the jboss service depends on, but it doesn't. Could you look that up in the services manager window? It is the Dependencies tab on the Properties dialog box for the service.

                                  Also, please provide the information I asked for in my prior post.


                                  Sorry it took me so long. This wasn't an urgent (though annoying) task and had lots of other stuff to do.

                                  Listdlls java yielded the following:
                                  
                                  ListDLLs v2.25 - DLL lister for Win9x/NT
                                  Copyright (C) 1997-2004 Mark Russinovich
                                  Sysinternals - www.sysinternals.com
                                  
                                  ------------------------------------------------------------------------------
                                  java.exe pid: 960
                                  Command line: "C:\Program Files\Java\jre1.6.0_07\bin\java" -Xrs -Dprogram.name=run.bat -XX:-HeapDumpOnOutOfMemoryError -Xms256m -Xmx1024m -Duser.timezone=GMT -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs="C:\Program Files\jboss-4.2.3.GA\lib\endorsed" -classpath "C:\Program Files\jboss-4.2.3.GA\bin\run.jar" org.jboss.Main -b 0.0.0.0
                                  
                                   Base Size Version Path
                                   0x00400000 0x23000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\java.exe
                                   0x7c800000 0xc0000 5.02.3790.3959 C:\WINDOWS\system32\ntdll.dll
                                   0x77e40000 0x102000 5.02.3790.4062 C:\WINDOWS\system32\kernel32.dll
                                   0x77f50000 0x9b000 5.02.3790.3959 C:\WINDOWS\system32\ADVAPI32.dll
                                   0x77c50000 0x9f000 5.02.3790.4115 C:\WINDOWS\system32\RPCRT4.dll
                                   0x76f50000 0x13000 5.02.3790.3959 C:\WINDOWS\system32\Secur32.dll
                                   0x7c340000 0x56000 7.10.3052.0004 C:\Program Files\Java\jre1.6.0_07\bin\msvcr71.dll
                                   0x6d7c0000 0x250000 10.00.0000.0023 C:\Program Files\Java\jre1.6.0_07\bin\client\jvm.dll
                                   0x77380000 0x91000 5.02.3790.4033 C:\WINDOWS\system32\USER32.dll
                                   0x77c00000 0x48000 5.02.3790.4237 C:\WINDOWS\system32\GDI32.dll
                                   0x76aa0000 0x2d000 5.02.3790.3959 C:\WINDOWS\system32\WINMM.dll
                                   0x76290000 0x1d000 5.02.3790.3959 C:\WINDOWS\system32\IMM32.DLL
                                   0x6d270000 0x8000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\hpi.dll
                                   0x76b70000 0xb000 5.02.3790.3959 C:\WINDOWS\system32\PSAPI.DLL
                                   0x6d770000 0xc000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\verify.dll
                                   0x6d310000 0x1f000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\java.dll
                                   0x6d7b0000 0xf000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\zip.dll
                                   0x6d570000 0x13000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\net.dll
                                   0x71c00000 0x17000 5.02.3790.3959 C:\WINDOWS\system32\WS2_32.dll
                                   0x77ba0000 0x5a000 7.00.3790.3959 C:\WINDOWS\system32\msvcrt.dll
                                   0x71bf0000 0x8000 5.02.3790.3959 C:\WINDOWS\system32\WS2HELP.dll
                                   0x71b20000 0x41000 5.02.3790.4318 C:\WINDOWS\System32\mswsock.dll
                                   0x76ed0000 0x2a000 5.02.3790.4318 C:\WINDOWS\system32\DNSAPI.dll
                                   0x76f70000 0x7000 5.02.3790.3959 C:\WINDOWS\System32\winrnr.dll
                                   0x76f10000 0x2e000 5.02.3790.3959 C:\WINDOWS\system32\WLDAP32.dll
                                   0x76f80000 0x5000 5.02.3790.3959 C:\WINDOWS\system32\rasadhlp.dll
                                   0x6d4c0000 0x9000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\management.dll
                                   0x5f270000 0x5a000 5.02.3790.3959 C:\WINDOWS\system32\hnetcfg.dll
                                   0x71ae0000 0x8000 5.02.3790.3959 C:\WINDOWS\System32\wshtcpip.dll
                                   0x68000000 0x35000 5.02.3790.3959 C:\WINDOWS\system32\rsaenh.dll
                                   0x7c8d0000 0x7ff000 6.00.3790.4184 C:\WINDOWS\system32\SHELL32.dll
                                   0x77da0000 0x52000 6.00.3790.3959 C:\WINDOWS\system32\SHLWAPI.dll
                                   0x77420000 0x103000 6.00.3790.3959 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.3959_x-ww_D8713E55\comctl32.dll
                                   0x6d750000 0x8000 6.00.0070.0006 C:\Program Files\Java\jre1.6.0_07\bin\sunmscapi.dll
                                   0x761b0000 0x93000 5.131.3790.3959 C:\WINDOWS\system32\CRYPT32.dll
                                   0x76190000 0x12000 5.02.3790.3959 C:\WINDOWS\system32\MSASN1.dll
                                  


                                  As for dependencies, in the services console, JBoss has the following:
                                  * AFD
                                  * TCP/IP Protocol Driver --> IPSec driver

                                  • 14. Re: JBoss as Windows service - stopping the service powers d
                                    Peter Johnson Master

                                    I do not see anything unusual in the DLLs being used by the JVM. That and your earlier statement that using shutdown to stop the app server does not halt the machine leads me to believe that the issue must be related to the service code or configuration, and not to JBossAS.

                                    Is there nothing in the system logs that would indicate why the system shut down?

                                    The only other thing I can think of is that there some system-wide option is set, and that is causing the shutdown when the jboss service is stopped. Something like "shut down when the last process run by user xxx is stopped". Or perhaps some other service was inadvertently set to depend on the jboss service. Or there is a scheduled task that periodically runs and checks on the system status and when the jboss service is stopped, that task shuts down the system.

                                    1 2 Previous Next