Topic
  • 2 replies
  • Latest Post - ‏2018-09-20T05:25:59Z by khushbukashyap443@gmail.com
SystemAdmin
SystemAdmin
2735 Posts

Pinned topic Javacore ntdll.dll on Websphere 7

‏2013-03-15T09:23:56Z |
Hello, everyone.
We have various machines with Websphere Application Server 7 at Windows 2003 SP2 Server, in different machines, with different applications.
Constantly 2 or more times a day, in different moments of the day, we have the Application Server down because of a JavaCore.
At the Javacore files we have the module of the crash is the ntdll.dlll library and the current thread normally is a internal process of IBM.
Someone saw something similar and knows a solution?
Below I pass an example of the Javacore entry.
Thanks a lot
Fabrizio Dutra

NULL
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TISIGINFO Dump Event "gpf" (00002000) received
1TIDATETIME Date: 2013/03/13 at 11:17:37
1TIFILENAME Javacore filename: D:\WebSphere7\AppServer\profiles\AppSrv01\javacore.20130313.111724.5472.0002.txt
1TIREQFLAGS Request Flags: 0x81 (exclusive+preempt)
1TIPREPSTATE Prep State: 0x0
1TIPREPINFO Exclusive VM access not taken: data may not be consistent across javacore sections
NULL
0SECTION GPINFO subcomponent dump routine
NULL ================================
2XHOSLEVEL OS Level : Windows Server 2003 5.2 build 3790 Service Pack 2
2XHCPUS Processors -
3XHCPUARCH Architecture : x86
3XHNUMCPUS How Many : 4
3XHNUMASUP NUMA is either not supported or has been disabled by user
NULL
1XHEXCPCODE J9Generic_Signal_Number: 00000040
1XHEXCPCODE ExceptionCode: C0000008
1XHEXCPCODE ExceptionAddress: 7C84CF3A
1XHEXCPCODE ContextFlags: 00010007
1XHEXCPCODE Handler1: 7FEFA0C0
1XHEXCPCODE Handler2: 7FECC000
NULL
1XHEXCPMODULE Module: C:\WINDOWS\system32\ntdll.dll
1XHEXCPMODULE Module_base_address: 7C800000
1XHEXCPMODULE Offset_in_DLL: 0004CF3A
NULL
1XHREGISTERS Registers:
2XHREGISTER EDI: 00000000
2XHREGISTER ESI: 601061D4
2XHREGISTER EAX: C0000008
2XHREGISTER EBX: 00000000
2XHREGISTER ECX: 60CFFC84
2XHREGISTER EDX: 7C82860C
2XHREGISTER EIP: 7C84CF3A
2XHREGISTER ESP: 60CFFC98
2XHREGISTER EBP: 60CFFCC0
2XHREGISTER EFLAGS: 00000282
2XHREGISTER GS: 0000
2XHREGISTER FS: 003B
2XHREGISTER ES: 0023
2XHREGISTER DS: 0023
NULL
1XHFLAGS VM flags:00000000
NULL
NULL
0SECTION ENVINFO subcomponent dump routine
NULL =================================
1CIJAVAVERSION JRE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 build jvmwi3260sr9-20101209_70480
1CIVMVERSION VM build 20101209_070480
1CIJITVERSION JIT disabled, AOT disabled
1CIGCVERSION GC - 20101027_AA
1CIRUNNINGAS Running as a standalone JVM

.........

1XMCURTHDINFO Current thread
NULL
3XMTHREADINFO "Non-Deferred Alarm Manager" J9VMThread:0x5FE7F400, j9thread_t:0x601074A4, java/lang/Thread:0x0066FCC8, state:R, prio=5
3XMTHREADINFO1 (native thread ID:0x11E8, native priority:0x5, native policy:UNKNOWN)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/lang/Object.wait(Native Method)
4XESTACKTRACE at java/lang/Object.wait(Bytecode PC:3)
4XESTACKTRACE at com/ibm/ejs/util/am/AlarmManagerThreadCSLM.run(Bytecode PC:286)
4XESTACKTRACE at java/lang/Thread.run(Bytecode PC:13)
3XMTHREADINFO3 Native callstack:
4XENATIVESTACK RtlIpv4StringToAddressExW+0xb584 (0x7C84CF3A ntdll+0x4cf3a)
4XENATIVESTACK RtlLockHeap+0x25c (0x7C83D2B1 ntdll+0x3d2b1)
4XENATIVESTACK monitor_wait_original+0x23c (j9thread.c:3754, 0x7FFA384C J9THR24+0x384c)
4XENATIVESTACK monitor_wait+0x31 (j9thread.c:3597, 0x7FFA4311 J9THR24+0x4311)
4XENATIVESTACK j9thread_monitor_wait+0x14 (j9thread.c:3467, 0x7FFA44A4 J9THR24+0x44a4)
4XENATIVESTACK internalAcquireVMAccessNoMutexWithMask+0x1a (vmaccess.c:238, 0x7FF28CBA j9vm24+0x38cba)
4XENATIVESTACK internalAcquireVMAccessNoMutex+0xf (vmaccess.c:253, 0x7FF28CFF j9vm24+0x38cff)
4XENATIVESTACK internalAcquireVMAccessClearStatus+0x1f (vmaccess.c:227, 0x7FF29B2F j9vm24+0x39b2f)
4XENATIVESTACK jclCallMonitorWaitInterruptable+0x17a (threadhelp.c:126, 0x7FC88FEA jclscar_24+0x38fea)
4XENATIVESTACK java_lang_Object_wait+0x7e (jlobj_cl.asm:358, 0x7FC6580E jclscar_24+0x1580e)
4XENATIVESTACK javaProtectedThreadProc+0x7d (vmthread.c:1669, 0x7FF2CB9D j9vm24+0x3cb9d)
4XENATIVESTACK j9sig_protect+0x41 (j9signal.c:144, 0x7FECC161 J9PRT24+0xc161)
4XENATIVESTACK javaThreadProc+0x35 (vmthread.c:261, 0x7FF2D3C5 j9vm24+0x3d3c5)
4XENATIVESTACK thread_wrapper+0xbf (j9thread.c:971, 0x7FFA3F4F J9THR24+0x3f4f)
4XENATIVESTACK _endthread+0xaa (0x7C34940F msvcr71+0x940f)
4XENATIVESTACK GetModuleHandleA+0xdf (0x77E6482F kernel32+0x2482f)
Updated on 2013-03-18T08:22:57Z at 2013-03-18T08:22:57Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    2735 Posts

    Re: Javacore ntdll.dll on Websphere 7

    ‏2013-03-18T08:22:57Z  
    javacore dump was generated due to an invalid condition observed within the module "C:\WINDOWS\system32\ntdll.dll". As per the failing thread's native function call stack, the top most native frame "RtlIpv4StringToAddressExW" referenced to invalid memory address which resulted into "GPF/Segmentation Fault" condition.

    I suspect erroneous condition within the Windows module for the failure. Since you have more than one system configured in your environment, I recommend you to compare the Windows configurations(like fix pack & other parameters) between the passing & failing system.
  • khushbukashyap443@gmail.com
    1 Post

    Re: Javacore ntdll.dll on Websphere 7

    ‏2018-09-20T05:25:59Z  

    If you are not able to access the dll file then you need to learn how to fix ntdll.dll file and then after that you can use this file easily.