WebSphere application server Traditional not starting - websphere

I am trying to start my websphere traditional application server from rational application developer. At the first time server started properly but after stopping it and starting it again next day it is giving admin exception: null pointer exception in the console
[12/7/22 14:47:15:934 IST] 00000001 SystemErr R com.ibm.websphere.management.exception.AdminException: java.lang.NullPointerException
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.management.MBeanFactoryImpl.deactivateMBean(MBeanFactoryImpl.java:1168)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.batch.endpointsensor.BatchSensorComponent.destroy(BatchSensorComponent.java:100)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.runtime.component.ContainerHelper.destroyComponent(ContainerHelper.java:341)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.runtime.component.ContainerHelper.destroyComponents(ContainerHelper.java:325)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.runtime.component.ContainerImpl.destroyComponents(ContainerImpl.java:607)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.runtime.component.ContainerImpl.destroy(ContainerImpl.java:598)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.runtime.component.ServerImpl.destroy(ServerImpl.java:501)
[12/7/22 14:47:15:935 IST] 00000001 SystemErr R at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:334)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:238)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:711)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at java.lang.reflect.Method.invoke(Method.java:508)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:101)
[12/7/22 14:47:15:936 IST] 00000001 SystemErr R at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:82)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at java.lang.reflect.Method.invoke(Method.java:508)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
[12/7/22 14:47:15:937 IST] 00000001 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[12/7/22 14:47:15:938 IST] 00000001 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
[12/7/22 14:47:15:938 IST] 00000001 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
[12/7/22 14:47:15:938 IST] 00000001 SystemErr R at java.lang.reflect.Method.invoke(Method.java:508)
[12/7/22 14:47:15:938 IST] 00000001 SystemErr R at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
[12/7/22 14:47:15:939 IST] 00000001 SystemErr R at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
[12/7/22 14:47:15:939 IST] 00000001 SystemErr R at org.eclipse.core.launcher.Main.run(Main.java:981)
[12/7/22 14:47:15:939 IST] 00000001 SystemErr R at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:423)
[12/7/22 14:47:15:939 IST] 00000001 SystemErr R at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:180)
[12/7/22 14:47:15:939 IST] 00000001 SystemErr R Caused by: java.lang.NullPointerException
[12/7/22 14:47:15:939 IST] 00000001 SystemErr R at com.ibm.ws.management.MBeanFactoryImpl.deactivateMBean(MBeanFactoryImpl.java:1141)
[12/7/22 14:47:15:940 IST] 00000001 SystemErr R ... 36 more
i am totally new to this can anyone explain me what can be issue as it worked before perfectly.

Related

Identify Cause of NULL_CLASS_PTR_READ_c0000005 on combase!CStdMarshal::UnmarshalIPID in PowerBuilder 10 App

What are some alternate steps that could be used to identify the root cause of this access violation read crash. I don't have access to source code or the customer env so need to specify steps to collect required information.
The issue only occurs when 3rd party firewall software is running, of which it's driver can be seen in stack traces of the process when using ProcMon stack summary feature. However I need to work out more explicitly how the issue is caused to enable a fix from 3rd party firewall vendor.
I have tried to walk customer through capturing API Monitor traces and Time Travel Debugging Trace however they are triggering the application to crash before issue can be reproduced.
The application seems to be built with PowerBuilder 10.2.1.0.
Crash dump output shows the following:
0:000> !analyze -v
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
eax=00000010 ebx=009c653c ecx=06da3ce4 edx=0019ccf8 esi=00000000 edi=00a63f88
eip=756afcbf esp=0019cb7c ebp=0019cbc0 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210206
combase!CStdMarshal::UnmarshalIPID+0xb8:
756afcbf 8b5804 mov ebx,dword ptr [eax+4] ds:002b:00000014=????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 756afcbf (combase!CStdMarshal::UnmarshalIPID+0x000000b8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000014
Attempt to read from address 00000014
PROCESS_NAME: appname.exe
READ_ADDRESS: 00000014
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000014
STACK_TEXT:
0019cbc0 756c62a5 0019ccf8 0019cd08 009c5aa0 combase!CStdMarshal::UnmarshalIPID+0xb8
0019cc48 756d61b0 0019ccf0 0019cf1c 00000000 combase!CStdMarshal::UnmarshalObjRef+0x155
0019ce54 5b309fe8 009ef828 5b2f5fa4 0019cf1c combase!CoUnmarshalInterface+0xdc0
0019ceec 5b312666 5b2f5fa4 0019cf1c 0000003d oleacc!SharedBuffer_Free+0x2b8
0019cf7c 5b3097fb 00002728 0000003d 00000001 oleacc!SharedBuffer_Allocate+0x8e36
0019cfa0 1123c095 11437d18 ffffffff 03d977cc oleacc!EXTERNAL_LresultFromObject+0x4b
WARNING: Stack unwind information not available. Following frames may be wrong.
0019cfd4 112363b7 0007079e ffffffff fffffffc pbvm100!FN_EvtTimerWnd+0xa75
0019d068 75db44bb 0007079e 0000003d ffffffff pbvm100!FN_DataWindowWnd+0x4a7
0019d094 75d94ffc 11235f10 0007079e 0000003d user32!_InternalCallWinProc+0x2b
0019d178 75d94b9a 11235f10 00000000 0000003d user32!UserCallWinProcCheckWow+0x3ac
0019d1dc 75d9e1df 01098290 00000000 0000003d user32!DispatchClientMessage+0xea
0019d218 7758428d 0019d234 00000020 0019d408 user32!__fnDWORD+0x3f
0019d250 759a2c0c 75db2d92 0007079e 0000003d ntdll!KiUserCallbackDispatcher+0x4d
0019d254 75db2d92 0007079e 0000003d ffffffff win32u!NtUserMessageCall+0xc
0019d298 75db2cf2 ffffffff fffffffc 00000002 user32!SendMessageTimeoutWorker+0x9b
0019d2bc 5b309695 0007079e 0000003d ffffffff user32!SendMessageTimeoutW+0x22
0019d2f8 5b30954b 0007079e fffffffc 5b2f5cc4 oleacc!NativeIAccessibleFromWindow+0x70
0019d328 5b32f49e 5b2f5cc4 0019d348 fffffffc oleacc!AccessibleObjectFromWindow+0x27
0019d360 5b32fa57 00000000 0019d3f8 0019d3c0 oleacc!AccessibleObjectFromEvent+0x5e
0019d374 76080c8b 0007079e fffffffc 00000000 oleacc!EXTERNAL_AccessibleObjectFromEvent+0x27
0019d39c 76080bae 00000000 0019d3f8 0019d3c0 msctf!AccessibleObjectFromEvent+0x38
0019d418 7606a0c5 0007079e fffffffc 00000000 msctf!CThreadInputMgr::OnAccFocusEvent+0x9f
0019d468 76069320 00008005 0007079e fffffffc msctf!CThreadInputMgr::OnCiceroEvent+0xa5
0019d4c4 75d9f019 001f02b7 00008005 0007079e msctf!WinEventProc+0xf0
0019d508 7758428d 0019d524 00000020 0019d928 user32!__ClientCallWinEventProc+0x39
0019d540 11297886 0007079e 0007079e 0704d628 ntdll!KiUserCallbackDispatcher+0x4d
0019d558 11234dd9 000b0736 00000000 00000000 pbvm100!FN_WndProc+0x766
0019d828 75db44bb 000b0736 00000007 00360360 pbvm100!FN_WindowWnd+0x14e9
0019d854 75d94ffc 112338f0 000b0736 00000007 user32!_InternalCallWinProc+0x2b
0019d938 75d9454f 112338f0 00000000 00000007 user32!UserCallWinProcCheckWow+0x3ac
0019d970 10b8f24d 112338f0 000b0736 00000007 user32!CallWindowProcW+0x7f
0019d998 75db44bb 000b0736 00000007 00360360 pbshr100!PBC_MainProc3D+0x16d
0019d9c4 75d94ffc 10b8f0e0 000b0736 00000007 user32!_InternalCallWinProc+0x2b
0019daa8 75d94b9a 10b8f0e0 00000000 00000007 user32!UserCallWinProcCheckWow+0x3ac
0019db0c 75d9e1df 010832e0 00000000 00000007 user32!DispatchClientMessage+0xea
0019db48 7758428d 0019db64 00000020 0019dce4 user32!__fnDWORD+0x3f
0019db80 759a30ac 75da6b6e 000b0736 00000007 ntdll!KiUserCallbackDispatcher+0x4d
0019db84 75da6b6e 000b0736 00000007 00000000 win32u!NtUserSetFocus+0xc
0019dbc4 75dee1b9 0102ab40 00000000 00000007 user32!MDIClientWndProcWorker+0x14e
0019dbe4 75db44bb 00360360 00000007 00360360 user32!MDIClientWndProcW+0x29
0019dc10 75d94ffc 75dee190 00360360 00000007 user32!_InternalCallWinProc+0x2b
0019dcf4 75d9454f 75dee190 00000000 00000007 user32!UserCallWinProcCheckWow+0x3ac
0019dd2c 10b8cdd2 75dee190 00360360 00000007 user32!CallWindowProcW+0x7f
0019dd54 75d952a1 00000000 77554470 112338f0 pbshr100!PBC_NormalProc3D+0x72
0019dd90 75d94ffc 10b8cd60 00360360 00000007 user32!UserCallWinProcCheckWow+0x651
0019de74 75d9454f 10b8cd60 00000000 00000007 user32!UserCallWinProcCheckWow+0x3ac
0019deac 112380fd 10b8cd60 00360360 00000007 user32!CallWindowProcW+0x7f
0019deec 75db44bb 00360360 00000007 00360360 pbvm100!FN_MDIClientWnd+0x2dd
0019df18 75d94ffc 11237e20 00360360 00000007 user32!_InternalCallWinProc+0x2b
0019dffc 75d947ad 11237e20 00000000 00000007 user32!UserCallWinProcCheckWow+0x3ac
0019e060 75d94473 0102ab40 00000000 00000000 user32!SendMessageWorker+0x1fd
0019e094 75da669a 00360360 00000007 00360360 user32!SendMessageW+0x123
0019e0d0 75da62a7 0102ab40 00000000 010832e0 user32!xxxMDIActivate+0x201
0019e114 75deea18 00000000 00000000 00000000 user32!DefMDIChildProcWorker+0x1f7
0019e128 112971f8 000b0736 00000022 00000000 user32!DefMDIChildProcW+0x18
0019e150 112dcf2a 000b0736 00000022 00000000 pbvm100!FN_WndProc+0xd8
0019e168 112dcba9 11297120 000b0736 00000022 pbvm100!fn_txnservice_create_instance+0x912a
0019e18c 11235260 11297120 000b0736 00000022 pbvm100!fn_txnservice_create_instance+0x8da9
0019e470 75db44bb 000b0736 00000022 00000000 pbvm100!FN_WindowWnd+0x1970
0019e49c 75d94ffc 112338f0 000b0736 00000022 user32!_InternalCallWinProc+0x2b
0019e580 75d9454f 112338f0 00000000 00000022 user32!UserCallWinProcCheckWow+0x3ac
0019e5b8 10b8f24d 112338f0 000b0736 00000022 user32!CallWindowProcW+0x7f
0019e5e0 75db44bb 000b0736 00000022 00000000 pbshr100!PBC_MainProc3D+0x16d
0019e60c 75d94ffc 10b8f0e0 000b0736 00000022 user32!_InternalCallWinProc+0x2b
0019e6f0 75d94b9a 10b8f0e0 00000000 00000022 user32!UserCallWinProcCheckWow+0x3ac
0019e754 75d9e1df 010832e0 00000000 00000022 user32!DispatchClientMessage+0xea
0019e790 7758428d 0019e7ac 00000020 0019ea6c user32!__fnDWORD+0x3f
0019e7c8 759a2ddc 75dcaa02 000b0736 00000000 ntdll!KiUserCallbackDispatcher+0x4d
0019e7cc 75dcaa02 000b0736 00000000 00000000 win32u!NtUserSetWindowPos+0xc
0019e820 75d8fa58 00000001 00000000 0019ee94 user32!MDICompleteChildCreation+0x1b895
0019e8d8 75da6be3 03d994c4 16cf0000 80000000 user32!CreateWindowInternal+0x2ec
0019e94c 75dee1b9 0102ab40 00000000 00000220 user32!MDIClientWndProcWorker+0x1c3
0019e96c 75db44bb 00360360 00000220 00000000 user32!MDIClientWndProcW+0x29
0019e998 75d94ffc 75dee190 00360360 00000220 user32!_InternalCallWinProc+0x2b
0019ea7c 75d9454f 75dee190 00000000 00000220 user32!UserCallWinProcCheckWow+0x3ac
0019eab4 10b8cdd2 75dee190 00360360 00000220 user32!CallWindowProcW+0x7f
0019eaec 75db44bb 00360360 00000220 00000000 pbshr100!PBC_NormalProc3D+0x72
00000000 00000000 00000000 00000000 00000000 user32!_InternalCallWinProc+0x2b
SYMBOL_NAME: oleacc!SharedBuffer_Free+2b8
MODULE_NAME: oleacc
IMAGE_NAME: oleacc.dll
STACK_COMMAND: ~0s ; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_oleacc.dll!SharedBuffer_Free
OS_VERSION: 10.0.18362.239
BUILDLAB_STR: 19h1_release_svc_prod1
OSPLATFORM_TYPE: x86
OSNAME: Windows 10
IMAGE_VERSION: 7.2.18362.1
FAILURE_ID_HASH: {2506b308-0659-fc20-d871-5cc908d8929d}
Followup: MachineOwner
The parameters passed to the COM APIs are:
0c 0019cbc0 756c62a5 combase!CStdMarshal::UnmarshalIPID(struct _GUID * riid = 0x0019ccf8 {618736E0-3C3D-11CF-810C-00AA00389B71}, struct tagSTDOBJREF * pStd = 0x0019cd08, class OXIDEntry * pOXIDEntry = 0x009c5aa0, void ** ppv = 0x0019cf1c)+0xb8 [onecore\com\combase\dcomrem\marshal.cxx # 2406]
0d 0019cc48 756d61b0 combase!CStdMarshal::UnmarshalObjRef(struct tagOBJREF * objref = 0x0019ccf0, void ** ppv = 0x0019cf1c)+0x155 [onecore\com\combase\dcomrem\marshal.cxx # 2194]
0e (Inline) -------- combase!UnmarshalSwitch(void)+0xe7 [onecore\com\combase\dcomrem\marshal.cxx # 1825]
0f (Inline) -------- combase!UnmarshalObjRef(void)+0x1f8 [onecore\com\combase\dcomrem\marshal.cxx # 1963]
10 0019ce54 5b309fe8 combase!CoUnmarshalInterface(struct IStream * pStm = 0x009ef828, struct _GUID * riid = 0x5b2f5fa4 {00000000-0000-0000-C000-000000000046}, void ** ppv = 0x0019cf1c)+0xdc0 [onecore\com\combase\dcomrem\coapi.cxx # 1993]
This seems to reference IAccessible interface which has the following registry info:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
#="IAccessible"
[HKEY_CLASSES_ROOT\interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\ProxyStubClsid32]
#="{00020424-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\interface\{618736E0-3C3D-11CF-810C-00AA00389B71}\TypeLib]
#="{1EA4DBF0-3C3B-11CF-810C-00AA00389B71}"
"Version"="1.1"
This then seems to refer to PSOAInterface:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\clsid\{00020424-0000-0000-C000-000000000046}]
#="PSOAInterface"
[HKEY_CLASSES_ROOT\clsid\{00020424-0000-0000-C000-000000000046}\InprocServer32]
#="C:\\Windows\\System32\\oleaut32.dll"
"ThreadingModel"="Both"
Reversing the crashing function to psuedocode this code is within the PowerBuilder runtime i.e. pbvm100.dll:
0:000> lmvm pbvm100
Browse full module list
start end module name
111e0000 11528000 pbvm100 (export symbols) pbvm100.dll
Loaded symbol image file: pbvm100.dll
Image path: C:\Program Files\AppName\pbvm100.dll
Image name: pbvm100.dll
Browse all global symbols functions data
Timestamp: Wed Aug 15 13:28:53 2007 (46C272F5)
CheckSum: 004132DA
ImageSize: 00348000
File version: 10.2.1.9948
Product version: 10.2.1.0
File flags: 2 (Mask 3) Pre-release
File OS: 10001 DOS Win16
File type: 1.65 App
File date: 00000000.00000000
Translations: 0409.04e4
Information from resource tables:
CompanyName: Sybase Inc.
ProductName: PowerBuilder/InfoMaker
InternalName: PB 10.0
FileVersion: 10.2.1.9948
FileDescription: Sybase Inc. Product File
LegalCopyright: Copyright Sybase Inc. 2004
LRESULT __stdcall FN_DataWindowWnd(HWND hWnd, UINT Msg, WPARAM wParam, LPARAM lParam)
{
etc..
if ( Msg <= 0x106 )
{
if ( Msg == 262 )
return CallWindowProcW(*((WNDPROC *)v12 + 3), hWnd, 0x106u, wParam, lParam);
switch ( Msg )
{
case 0x3Du:
if ( lParam != -4 )
goto LABEL_72;
result = CrashingFunction(hWnd, wParam, -4, 0);
break;
etc...
}
}
}
int __cdecl CrashingFunction(HWND hWnd, int a2, int a3, int a4)
{
int result; // eax
int v5; // [esp+Ch] [ebp-14h]
int v6; // [esp+14h] [ebp-Ch]
int v7; // [esp+18h] [ebp-8h] BYREF
int v8; // [esp+1Ch] [ebp-4h]
v8 = 0;
v7 = 0;
v6 = GetWindowProperties(hWnd);
if ( !v6 )
return 0;
if ( *(_DWORD *)(v6 + 628) || (v8 = PB_CreateAccessibleService(v6 + 628)) == 0 && *(_DWORD *)(v6 + 628) )
{
v5 = GetWinProp(hWnd);
if ( v5 )
{
if ( *(_DWORD *)v5 == 16509 )
{
v8 = (*(int (__stdcall **)(_DWORD, HWND, int))(**(_DWORD **)(v6 + 628) + 16))(
*(_DWORD *)(v6 + 628),
hWnd,
v5 + 256);
if ( !v8 && *(_DWORD *)(v5 + 256) )
{
if ( a4 )
{
(*(void (__stdcall **)(_DWORD, int, int *))(**(_DWORD **)(v5 + 256) + 116))(*(_DWORD *)(v5 + 256), a4, &v7);
if ( v7 )
result = PB_LresultFromObject(&unk_11437D18, a2, v7);
else
result = 0;
}
else
{
result = PB_LresultFromObject(&unk_11437D18, a2, *(_DWORD *)(v5 + 256));
}
}
else
{
switch ( v8 )
{
case -2147467261:
DisplayErrorMsg(0x4B0u, 0x4B4u);
break;
case -2147024890:
DisplayErrorMsg(0x4B0u, 0x4B2u);
break;
case -2147024882:
DisplayErrorMsg(0x4B0u, 0x4B6u);
break;
}
result = 0;
}
}
else
{
result = 0;
}
}
else
{
result = 0;
}
}
else
{
if ( v8 == -2147024882 )
DisplayErrorMsg(0x4B0u, 0x4B6u);
else
DisplayErrorMsg(0x4B0u, 0x4B1u);
result = 0;
}
return result;
}

ExceptionHandler stacktrace on Windows

So, I see this line in one of the callstacks of a dump (x86/Windows 7) I am looking at. I have heavily snipped it as my question is pertaining only to this call.
Args to Child
01111111 04444444 05555555 ntdll!KiUserExceptionDispatcher+0xf
and going by: http://www.nynaeve.net/Code/KiUserExceptionDispatcher.c
It looks like the first two arguments on the stack must be the context record and the exception record. However with some experimentation I noted that 01111111 is not the first argument. It actually starts from 04444444. So, in this case .cxr 04444444 and .exr 05555555 display sane output.
Now, I understand the debugger might just show whatever is on the stack at that point and I shouldn't probably rely on that alone but if everything below that line is marked with "stack unwind information not available. Following frames may be wrong", how am I to know that I should ignore 01111111?
UPDATE
Lets try a different approach. Here are 2 relevant pieces of information:
Args to Child
0ccccccc 77895ac4 00000000 kernel32!UnhandledExceptionFilter+0x9e
[... various other calls here, leading up to ...]
0eeeeeee 0aaaaaaa 0bbbbbbb ntdll!KiUserExceptionDispatcher+0xf
So, check this out. The lone parameter to UnhandledExceptionFilter is an EXCEPTION_POINTERS* structure, right?
0:010> dd 0ccccccc l2
0ddddddd 0bbbbbbb 0aaaaaaa
In the EXCEPTION_POINTERS struct, the first field is the EXCEPTION_RECORD (0bbbbbbb) while the second is the CONTEXT_RECORD (0aaaaaaa). However in the call to KiUserEceptionDispatcher, these arguments appear in the opposite way. Not to mention the fact 0eeeeeee is NOT the first parameter to KiUserExceptionDispatcher but 0ccccccc IS the first parameter to UnhandledExceptionFilter.
I am SO confused!

windows 7 x86 32 bit machine
winkey + r -> windbg calc
bp ntdll!KiUserExceptionDispatcher
f5
divide 0/0 in calculator to raise an exception
(ac8.c8c): C++ EH exception - code e06d7363 (first chance)
Breakpoint 0 hit
eax=0023e1ec ebx=02b12fd0 ecx=00000003 edx=00000000 esi=02b13178 edi=00000001
eip=76e77048 esp=0023dee0 ebp=0023e23c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!KiUserExceptionDispatcher:
76e77048 fc cld
your post shows the return address to be + 0xf so lets see whats upto that point
0:000> u . .+f
ntdll!KiUserExceptionDispatcher:
76e77048 fc cld
76e77049 8b4c2404 mov ecx,dword ptr [esp+4]
76e7704d 8b1c24 mov ebx,dword ptr [esp]
76e77050 51 push ecx
76e77051 53 push ebx
76e77052 e85d88fdff call ntdll!RtlDispatchException (76e4f8b4)
76e77057 0ac0 or al,al
so it appears you have broken after entering RtlDispatchException from your call stack
breaking to enter the call
0:000> tc
eax=0023e1ec ebx=0023dee8 ecx=0023df08 edx=00000000 esi=02b13178 edi=00000001
eip=76e77052 esp=0023ded8 ebp=0023e23c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!KiUserExceptionDispatcher+0xa:
76e77052 e85d88fdff call ntdll!RtlDispatchException (76e4f8b4)
0:000> t
eax=0023e1ec ebx=0023dee8 ecx=0023df08 edx=00000000 esi=02b13178 edi=00000001
eip=76e4f8b4 esp=0023ded4 ebp=0023e23c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!RtlDispatchException:
76e4f8b4 8bff mov edi,edi
looking at stack if you ask windbg to be verbose it will even decipher the context for you
0:000> kb 3
# ChildEBP RetAddr Args to Child
00 0023ded0 76e77057 0023dee8 0023df08 0023dee8 ntdll!RtlDispatchException
01 0023ded0 7521b760 0023dee8 0023df08 0023dee8 ntdll!KiUserExceptionDispatcher+0xf
02 0023e23c 7579359c e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x58
0:000> kv 3
# ChildEBP RetAddr Args to Child
00 0023ded0 76e77057 0023dee8 0023df08 0023dee8 ntdll!RtlDispatchException (FPO: [Non-Fpo])
01 0023ded0 7521b760 0023dee8 0023df08 0023dee8 ntdll!KiUserExceptionDispatcher+0xf (FPO: [2,0,0]) (CONTEXT # 0023df08)
02 0023e23c 7579359c e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x58 (FPO: [Non-Fpo])
exr output
0:000> .exr poi(#esp+4)
ExceptionAddress: 7521b760 (KERNELBASE!RaiseException+0x00000058)
ExceptionCode: e06d7363 (C++ EH exception)
ExceptionFlags: 00000001
NumberParameters: 3
Parameter[0]: 19930520
Parameter[1]: 0023e294
Parameter[2]: 007c15b4
unable to find C-Runtime symbols, even with unqualified search
context record output
0:000> dt ntdll!_CONTEXT poi(#esp+8)
+0x000 ContextFlags : 0x1003f
+0x004 Dr0 : 0
+0x008 Dr1 : 0
+0x00c Dr2 : 0
+0x010 Dr3 : 0
+0x014 Dr6 : 0
+0x018 Dr7 : 0
+0x01c FloatSave : _FLOATING_SAVE_AREA
+0x08c SegGs : 0
+0x090 SegFs : 0x3b
+0x094 SegEs : 0x23
+0x098 SegDs : 0x23
+0x09c Edi : 1
+0x0a0 Esi : 0x2b13178
+0x0a4 Ebx : 0x2b12fd0
+0x0a8 Edx : 0
+0x0ac Ecx : 3
+0x0b0 Eax : 0x23e1ec
+0x0b4 Ebp : 0x23e23c
+0x0b8 Eip : 0x7521b760
+0x0bc SegCs : 0x1b
+0x0c0 EFlags : 0x202
+0x0c4 Esp : 0x23e1ec
+0x0c8 SegSs : 0x23
+0x0cc ExtendedRegisters : [512] "???"
you can even get both by use .extptr (note you may need to reset context to default scope using .cxr after using this command)
0:000> .exptr (#esp+4)
----- Exception record at 0023dee8:
ExceptionAddress: 7521b760 (KERNELBASE!RaiseException+0x00000058)
ExceptionCode: e06d7363 (C++ EH exception)
ExceptionFlags: 00000001
NumberParameters: 3
Parameter[0]: 19930520
Parameter[1]: 0023e294
Parameter[2]: 007c15b4
unable to find C-Runtime symbols, even with unqualified search
----- Context record at 0023df08:
eax=0023e1ec ebx=02b12fd0 ecx=00000003 edx=00000000 esi=02b13178 edi=00000001
eip=7521b760 esp=0023e1ec ebp=0023e23c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
KERNELBASE!RaiseException+0x58:
7521b760 c9 leave
0:000> kb 3
# ChildEBP RetAddr Args to Child
00 0023e23c 7579359c e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x58
01 0023e274 0079eee0 0023e294 007c15b4 02b13178 msvcrt!_CxxThrowException+0x48
02 0023e288 0079146e 02b13178 80000002 c87a3f02 calc!divrat+0x69
0:000> .cxr
Resetting default scope
0:000> kb 3
# ChildEBP RetAddr Args to Child
00 0023ded0 76e77057 0023dee8 0023df08 0023dee8 ntdll!RtlDispatchException
01 0023ded0 7521b760 0023dee8 0023df08 0023dee8 ntdll!KiUserExceptionDispatcher+0xf
02 0023e23c 7579359c e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x58
hope this suffices to research on your own for your specific situation for which you cant divulge the actual windbg stack trace

Spring Integration SFTP Issue : 2 Too many authentication failures for webadm

I am trying to transfer file from one server to another server using SI SFTP adapater. It worked for 1st time. after that I am started getting below error. Can anyone through some light how to resolve it.
[7/18/14 18:05:26:273 EDT] 00000034 SystemErr R at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
[7/18/14 18:05:26:273 EDT] 00000034 SystemErr R at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
[7/18/14 18:05:26:273 EDT] 00000034 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)
[7/18/14 18:05:26:273 EDT] 00000034 SystemErr R Caused by: java.lang.IllegalStateException: failed to create SFTP Session
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R at org.springframework.integration.sftp.session.DefaultSftpSessionFactory.getSession(DefaultSftpSessionFactory.java:321)
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R at org.springframework.integration.file.remote.session.CachingSessionFactory$1.createForPool(CachingSessionFactory.java:74)
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R at org.springframework.integration.file.remote.session.CachingSessionFactory$1.createForPool(CachingSessionFactory.java:71)
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R at org.springframework.integration.util.SimplePool.doGetItem(SimplePool.java:187)
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R at org.springframework.integration.util.SimplePool.getItem(SimplePool.java:167)
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R ... 198 more
[7/18/14 18:05:26:274 EDT] 00000034 SystemErr R Caused by: java.lang.IllegalStateException: failed to connect
[7/18/14 18:05:26:275 EDT] 00000034 SystemErr R at org.springframework.integration.sftp.session.SftpSession.connect(SftpSession.java:250)
[7/18/14 18:05:26:275 EDT] 00000034 SystemErr R at org.springframework.integration.sftp.session.DefaultSftpSessionFactory.getSession(DefaultSftpSessionFactory.java:316)
[7/18/14 18:05:26:275 EDT] 00000034 SystemErr R ... 202 more
[7/18/14 18:05:26:275 EDT] 00000034 SystemErr R Caused by: com.jcraft.jsch.JSchException: SSH_MSG_DISCONNECT: 2 Too many authentication failures for webadm
[7/18/14 18:05:26:276 EDT] 00000034 SystemErr R at com.jcraft.jsch.Session.read(Session.java:987)
[7/18/14 18:05:26:276 EDT] 00000034 SystemErr R at com.jcraft.jsch.UserAuthPublicKey.start(UserAuthPublicKey.java:83)
[7/18/14 18:05:26:276 EDT] 00000034 SystemErr R at com.jcraft.jsch.Session.connect(Session.java:463)
[7/18/14 18:05:26:276 EDT] 00000034 SystemErr R at com.jcraft.jsch.Session.connect(Session.java:183)
[7/18/14 18:05:26:276 EDT] 00000034 SystemErr R at org.springframework.integration.sftp.session.SftpSession.connect(SftpSession.java:241)
[7/18/14 18:05:26:276 EDT] 00000034 SystemErr R ... 203 more

how to declare __stdcall calling convention function pointer that is GCC compatible

This works with MSVC (compile and link).
extern void (_TMDLLENTRY * _TMDLLENTRY tpsetunsol _((void (_TMDLLENTRY *)(char _TM_FAR *, long, long)))) _((char _TM_FAR *, long, long));
But with GCC compiling is ok but linking phase fails with undefined reference pointing to this. Is this declaration already GCC compatible or is there possibly some other problem?
#define _TMDLLENTRY __stdcall
#define _TM_FAR
nm output from MSVC created object file:
00000000 N .debug$S
00000000 N .debug$S
00000000 N .debug$S
00000000 N .debug$S
00000000 N .debug$T
00000000 i .drectve
00000000 r .rdata
00000000 r .rdata
00000000 r .rdata
00000000 t .text
00000000 t .text
00000000 t .text
U #__security_check_cookie#4
00aa766f a #comp.id
00000001 a #feat.00
U ___security_cookie
U __imp__CloseClipboard#0
U __imp__EmptyClipboard#0
U __imp__GlobalAlloc#8
U __imp__GlobalLock#4
U __imp__GlobalUnlock#4
U __imp__MessageBoxA#16
U __imp__OpenClipboard#4
U __imp__SetClipboardData#8
00000000 T _CheckBroadcast#0
00000000 T _Inittpsetunsol#0
U _memcpy
U _memset
U _sprintf
U _tpchkunsol#0
U _tpsetunsol#4
00000000 T _vCSLMsgHandler#12
nm output from MinGW compiler:
nm Release/broadc.o
00000000 b .bss
00000000 d .data
00000000 N .debug_abbrev
00000000 N .debug_aranges
00000000 N .debug_info
00000000 N .debug_line
00000000 N .debug_loc
00000000 r .eh_frame
00000000 r .rdata
00000000 t .text
00000104 T _CheckBroadcast#0
U _CloseClipboard#0
U _EmptyClipboard#0
U _GlobalAlloc#8
U _GlobalLock#4
U _GlobalUnlock#4
0000010c T _Inittpsetunsol#0
U _MessageBoxA#16
U _OpenClipboard#4
U _SetClipboardData#8
U _sprintf
U _tpchkunsol#0
U _tpsetunsol
00000000 T _vCSLMsgHandler#12
Edit: Looking at _tpsetunsol symbol it is quite evident that MSVC and GCC produce different symbols.
GCC produces: U _tpsetunsol and MSVC: U _tpsetunsol#4
Is there a way to have GCC produce same symbol than MSVC?
Edit2: output from nm wtuxws32.lib (that is where tpsetunsol is defined)
WTUXWS32.dll:
00000000 i .idata$4
00000000 i .idata$5
00000000 t .text
00000000 I __imp__tpsetunsol#4
U __IMPORT_DESCRIPTOR_WTUXWS32
00000000 T _tpsetunsol#4
Is this impossible to get to work with GCC? Thanks.

Application on websphere throws ClassCastException on application restart

I have an application of Websphere application server 7.0 (Parent Last)
Please read through the description to understand the problem.
I created a new websphere profile. Configured my application on it and started the application and now when I test the application. It works Good.
Now, I went to websphere console and re-start my application. This time when I test my application. I get error.
The log says a classCastException :
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R java.lang.ClassCastException: com.csc.fs.ra.SimpleConnectionSpecImpl incompatible with com.csc.fs.ra.SimpleConnectionSpecImpl
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.ra.ip.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:69)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.InteractionHandlerBase.getConnection(InteractionHandlerBase.java:165)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.InteractionHandlerBase.execute(InteractionHandlerBase.java:95)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.InteractionHandlerBase.process(InteractionHandlerBase.java:230)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.SystemAccessBase.invokeInteraction(SystemAccessBase.java:374)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.SystemAccessBase.internalInvoke(SystemAccessBase.java:242)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.SystemAccessBase.invoke(SystemAccessBase.java:55)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.sa.SystemAccessBase.login(SystemAccessBase.java:106)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.session.AuthenticatorBase.logonSystemSession(AuthenticatorBase.java:153)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.session.AuthenticatorBase.addSystemSessions(AuthenticatorBase.java:132)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.session.standalone.AuthenticatorBase.logon(AuthenticatorBase.java:224)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.session.AuthenticatorBase.logon(AuthenticatorBase.java:93)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.service.ServiceControllerAbstract.logon(ServiceControllerAbstract.java:387)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.delegate.DirectServiceController.logon(DirectServiceController.java:132)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.delegate.ServiceDelegateDirect.logon(ServiceDelegateDirect.java:133)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.ui.BaseServiceAction.logon(BaseServiceAction.java:124)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.ui.action.desktop.Logon.perform(Logon.java:47)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.ui.ServiceDelegator.execute(ServiceDelegator.java:506)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.ui.ServiceDelegator.processEvent(ServiceDelegator.java:240)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.ui.BeanBase.executeEvent(BeanBase.java:779)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at pagecode.authorization.Logon.submit(Logon.java:66)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at java.lang.reflect.Method.invoke(Method.java:600)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at org.apache.el.parser.AstValue.invoke(AstValue.java:131)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at org.apache.jasper.el.JspMethodExpression.invoke(JspMethodExpression.java:67)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at javax.faces.component.UICommand.broadcast(UICommand.java:315)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:775)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1267)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1661)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.csc.fs.accel.ui.filters.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:82)
[3/21/13 6:06:18:616 EDT] 0000001d SystemErr R at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
The reason behind this ClassCastException is multiple version of the class SimpleConnectionSpecImpl .
This class is being supplied by Resource adapters that I have configured externally through websphere admin console.
But now when I stop the server and restart the server, I can again use the application with no error.
So my closest guess websphere is caching class files because of which I am seeing the exception.
Any thoughts? Ideas?
Please let me know if you require any more details

You see the exception because there are different class loaders that have loaded that class, which technically makes them different classes.
We've solved this problem before by have the class be apart of the server classpath and only have the server load it. This way there is only one class loader for the class and all applications running on the server can use it from there.
The only other options I can see here is don't restart your app unless you plan to restart the server as well. I would only see this as a pain in a development environment but once you hit production I doubt you're frequently restarting apps.

Resources