sachindeshpande
asked on
Application crashes (disappears) intermittently without leaving any trace/dump.
We have an application , which is primarily written in Java and C++. We sell 2 versions of our product one in Windows 2000 and the other in Windows 2003. We use JNI to talk to C++. We also use SQL Server 2000.
Recently for our latest release we added a C# component and communicate with it within Java. We are using the .NET 1.1 framework.
Since we added the component we are seeing intermittent crashes of the product and there is no stack trace or dump left in most cases. The crashes even occur when the applicaiton is idle and in some cases when the application is started for the first time after reboot. Also in some cases the crashes occur in a few hours and in some cases in takes a week. (We have seen that it takes longer to crash on Windows 2000 than Windows 2003)
The some cases we see an error in the windows application log as follows :
"Faulting application java.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x00003847.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp"
And the worst thing about this is we rarely see this error in our testing machines here. Last week we were able to replicate it in some cases but we cannot find a well defined replication scenario. And this always occurs at all our customer sites.
This has become a very urgent issue for us as it is happening at the customer site. I would really appreciate if you could look inot this soon.
Best Regards,
Sachin.
Recently for our latest release we added a C# component and communicate with it within Java. We are using the .NET 1.1 framework.
Since we added the component we are seeing intermittent crashes of the product and there is no stack trace or dump left in most cases. The crashes even occur when the applicaiton is idle and in some cases when the application is started for the first time after reboot. Also in some cases the crashes occur in a few hours and in some cases in takes a week. (We have seen that it takes longer to crash on Windows 2000 than Windows 2003)
The some cases we see an error in the windows application log as follows :
"Faulting application java.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x00003847.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp"
And the worst thing about this is we rarely see this error in our testing machines here. Last week we were able to replicate it in some cases but we cannot find a well defined replication scenario. And this always occurs at all our customer sites.
This has become a very urgent issue for us as it is happening at the customer site. I would really appreciate if you could look inot this soon.
Best Regards,
Sachin.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have uploaded the log and dump files on our ftp site
Site address : http://www.timbrecom.com/Customer
username : guest01
password : timbre01
Thanks,
Sachin.
The java process encounter access violation (ie c0000005) at module mscorwks and the Java error handling encounter another abend STATUS_WAKE_SYSTEM_DEBUGGE R (ie 80000007). In order to avoid recursive program loop within the recovery routine. Java process crashes immediately.
EXCEPTION_RECORD: 1a41f750 -- (.exr 1a41f750)
ExceptionAddress: 79248a40 (mscorwks!Thread::ReturnTo Context+0x 0000002d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 000001ec
Attempt to read from address 000001ec
BUGCHECK_STR: 80000007
DEFAULT_BUCKET_ID: APPLICATION_FAULT
PROCESS_NAME: java.exe
ERROR_CODE: (NTSTATUS) 0x80000007 - {STATUS_WAKE_SYSTEM_DEBUGG ER
FAULTING_THREAD: 000008f4
CONTEXT: 1a41f76c -- (.cxr 1a41f76c)
eax=00000000 ebx=1a41fa68 ecx=1a41fa68 edx=00000004 esi=00166c50 edi=000bab38
eip=79248a40 esp=1a41fa38 ebp=1a41fa4c iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010293
mscorwks!Thread::ReturnToC ontext+0x2 d:
79248a40 8b80ec010000 mov eax,[eax+0x1ec] ds:0023:000001ec=????????
Resetting default scope
EXCEPTION_RECORD: 1a41f750 -- (.exr 1a41f750)
ExceptionAddress: 79248a40 (mscorwks!Thread::ReturnTo
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 000001ec
Attempt to read from address 000001ec
BUGCHECK_STR: 80000007
DEFAULT_BUCKET_ID: APPLICATION_FAULT
PROCESS_NAME: java.exe
ERROR_CODE: (NTSTATUS) 0x80000007 - {STATUS_WAKE_SYSTEM_DEBUGG
FAULTING_THREAD: 000008f4
CONTEXT: 1a41f76c -- (.cxr 1a41f76c)
eax=00000000 ebx=1a41fa68 ecx=1a41fa68 edx=00000004 esi=00166c50 edi=000bab38
eip=79248a40 esp=1a41fa38 ebp=1a41fa4c iopl=0 nv up ei ng nz ac pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010293
mscorwks!Thread::ReturnToC
79248a40 8b80ec010000 mov eax,[eax+0x1ec] ds:0023:000001ec=????????
Resetting default scope
ASKER
Thanks for the analysis.
What do you think is causing the error ? Also do you think there is a possible resolution ?
Thanks,
Sachin.
What do you think is causing the error ? Also do you think there is a possible resolution ?
Thanks,
Sachin.
http://support.microsoft.com/default.aspx?scid=kb;en-us;837088
The hotfix solved the issue for me, at least it hasn't happened again since.
GL