3 Replies Latest reply on Jul 17, 2002 6:14 AM by Adrian Brock

    Native exception occurs when using scheduler mbean during sh

    Robert Finneran Newbie

      Hi,

      I'm running JBoss-3.0.1RC1 on Win2K using Sun j2sdk1.4.0 Java Hotspot client VM (1.4.0-b92 mixed mode.)

      I have a class that implements org.jboss.varia.scheduler.Schedulable and is configured as follows:


      true
      com.digitalskyscrapers.crsguides.utils.SchedulableHeartBeat
      Schedulabe Test,0
      java.lang.String,int
      1
      60000
      -1


      It appears that the scheduler did not unhook the system level timer event and that the JVM is not smart enough to do it for the application anyway before it (the JVM) shuts down. Is there some way to fix the scheduler service to listen to JMX shutdown events and then to cancel the timer events before JVM shutdown?

      Note that the exception only occurs on about 40% of my shutdowns.

      Thanks in Advance!!!!

      BTW: My apps seem to run a lot faster under 3.0.1 as compared to 2.4.4. Great job JBoss Team!

        • 1. Re: Native exception occurs when using scheduler mbean durin
          Adrian Brock Master

          What exception are you getting?

          From a quick glance, the scheduler should be stopping the timer.

          Regards,
          Adrian

          • 2. Re: Native exception occurs when using scheduler mbean durin
            Robert Finneran Newbie

            Here's the exception report, but it is not much help. (Please note that I could not find the hs_err_pid1008.log file that was supposedly generated by the JVM)

            18:38:29,143 INFO [Server] Shutdown complete
            Shutdown complete
            Halting VM

            An unexpected exception has been detected in native code outside the VM.
            Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77F82D8F
            Function=RtlInitUnicodeString+0x1B
            Library=C:\WINNT\System32\ntdll.dll

            Current Java thread:
            at java.lang.Shutdown.halt(Native Method)
            at java.lang.Runtime.halt(Runtime.java:254)
            at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:6
            88)

            Dynamic libraries:
            0x00400000 - 0x00406000 C:\j2sdk1.4.0\bin\java.exe
            0x77F80000 - 0x77FFB000 C:\WINNT\System32\ntdll.dll
            0x77DB0000 - 0x77E0C000 C:\WINNT\system32\ADVAPI32.dll
            0x77E80000 - 0x77F35000 C:\WINNT\system32\KERNEL32.DLL
            0x77D40000 - 0x77DAD000 C:\WINNT\system32\RPCRT4.DLL
            0x78000000 - 0x78046000 C:\WINNT\system32\MSVCRT.dll
            0x6D330000 - 0x6D442000 C:\j2sdk1.4.0\jre\bin\client\jvm.dll
            0x77E10000 - 0x77E74000 C:\WINNT\system32\USER32.dll
            0x77F40000 - 0x77F7C000 C:\WINNT\system32\GDI32.DLL
            0x77570000 - 0x775A0000 C:\WINNT\System32\WINMM.dll
            0x6D1D0000 - 0x6D1D7000 C:\j2sdk1.4.0\jre\bin\hpi.dll
            0x6D300000 - 0x6D30D000 C:\j2sdk1.4.0\jre\bin\verify.dll
            0x6D210000 - 0x6D228000 C:\j2sdk1.4.0\jre\bin\java.dll
            0x6D320000 - 0x6D32D000 C:\j2sdk1.4.0\jre\bin\zip.dll
            0x6D2D0000 - 0x6D2DD000 C:\j2sdk1.4.0\jre\bin\net.dll
            0x75050000 - 0x75058000 C:\WINNT\System32\WSOCK32.dll
            0x75030000 - 0x75043000 C:\WINNT\System32\WS2_32.DLL
            0x75020000 - 0x75028000 C:\WINNT\System32\WS2HELP.DLL
            0x785C0000 - 0x785CC000 C:\WINNT\System32\rnr20.dll
            0x77980000 - 0x779A4000 C:\WINNT\System32\DNSAPI.DLL
            0x77340000 - 0x77353000 C:\WINNT\System32\iphlpapi.dll
            0x77520000 - 0x77525000 C:\WINNT\System32\ICMP.DLL
            0x77320000 - 0x77337000 C:\WINNT\System32\MPRAPI.DLL
            0x75150000 - 0x75160000 C:\WINNT\System32\SAMLIB.DLL
            0x75170000 - 0x751BF000 C:\WINNT\System32\NETAPI32.DLL
            0x77BE0000 - 0x77BEF000 C:\WINNT\System32\SECUR32.DLL
            0x751C0000 - 0x751C6000 C:\WINNT\System32\NETRAP.DLL
            0x77950000 - 0x7797A000 C:\WINNT\system32\WLDAP32.DLL
            0x77A50000 - 0x77B3A000 C:\WINNT\system32\OLE32.DLL
            0x779B0000 - 0x77A4B000 C:\WINNT\system32\OLEAUT32.DLL
            0x773B0000 - 0x773DE000 C:\WINNT\System32\ACTIVEDS.DLL
            0x77380000 - 0x773A2000 C:\WINNT\System32\ADSLDPC.DLL
            0x77830000 - 0x7783E000 C:\WINNT\System32\RTUTILS.DLL
            0x77880000 - 0x7790D000 C:\WINNT\System32\SETUPAPI.DLL
            0x77C10000 - 0x77C6E000 C:\WINNT\System32\USERENV.DLL
            0x774E0000 - 0x77512000 C:\WINNT\System32\RASAPI32.DLL
            0x774C0000 - 0x774D1000 C:\WINNT\System32\rasman.dll
            0x77530000 - 0x77552000 C:\WINNT\System32\TAPI32.dll
            0x71780000 - 0x7180A000 C:\WINNT\system32\COMCTL32.DLL
            0x70BD0000 - 0x70C34000 C:\WINNT\system32\SHLWAPI.DLL
            0x77360000 - 0x77379000 C:\WINNT\System32\DHCPCSVC.DLL
            0x775A0000 - 0x77625000 C:\WINNT\System32\CLBCATQ.DLL
            0x777E0000 - 0x777E8000 C:\WINNT\System32\winrnr.dll
            0x777F0000 - 0x777F5000 C:\WINNT\System32\rasadhlp.dll
            0x74FD0000 - 0x74FEF000 C:\WINNT\system32\msafd.dll
            0x75010000 - 0x75017000 C:\WINNT\System32\wshtcpip.dll
            0x6D2F0000 - 0x6D2F5000 C:\j2sdk1.4.0\jre\bin\rmi.dll
            0x77920000 - 0x77943000 C:\WINNT\system32\imagehlp.dll
            0x72A00000 - 0x72A2D000 C:\WINNT\system32\DBGHELP.dll
            0x690A0000 - 0x690AB000 C:\WINNT\System32\PSAPI.DLL

            Local Time = Tue Jul 16 18:38:31 2002
            Elapsed Time = 1344
            #
            # The exception above was detected in native code outside the VM
            #
            # Java VM: Java HotSpot(TM) Client VM (1.4.0-b92 mixed mode)
            #
            # An error report file has been saved as hs_err_pid1008.log.
            # Please refer to the file for further information.
            #

            • 3. Re: Native exception occurs when using scheduler mbean durin
              Adrian Brock Master

              Hi,

              This is a VM error.
              The log file is probably in jboss\bin, but it will
              just look like the information you posted.

              Regards,
              Adrian