A fix is available
APAR status
Closed as program error.
Error description
BLUESCREEN or CRASH running application using CS/WIN LUA api. bugcheck_str: 0x50 faulting_ip: appnapi+17856 2nd BS or CRASH reported by this apar: KMODE_EXCEPTION_NOT_HANDLED (1E) ARG1: C0000005 The exception code that was not handled ARG2: bca54ec0, The address of exception at FAULTING_IP: appn+11dec0 bca54ec0 0fb68008010000 movzx eax,byte ptr (eax+0x108)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All running LUA applications. * **************************************************************** * PROBLEM DESCRIPTION: System CRASH when LUA application * * terminates unexpectedly while * * processing RUI_TERM verb. * **************************************************************** * RECOMMENDATION: * **************************************************************** The LUA application issues the RUI_TERM and terminated without waiting for the RUI_TERM to complete. Other RUI_VERB(s) were outstanding with SNAPS requiring to be cancelled. Since the application is gone, the RUI stub clean up process is called to cleanup all sessions. When the cleanup session process kicks off it issues RUI_TERM to all the session, including the session with the outstanding RUI_TERM. When we process the outsanding RUI_TERM response, a CRASH occurs.
Problem conclusion
The RUI_STUB received the RUI_TERM response for the 2nd RUI_TERM from the SNAPs with the lua_prim_rc == LUA_UNSUCCESSFUL and lua_sec_rc == LUA_COMMAND_COUNT_ERROR. In the cleanup function, we cleanup all the outstanding verbs and cancel the IRP's irrespective of the PRC & SRC. When stub cancels the IRP the VCB related memory gets freed. However, we won't free the SESSION related data structure. Instead of just freeing the verb, the stub code also has to free the session and it's related data.
Temporary fix
Comments
APAR Information
APAR number
JR26010
Reported component name
COMM SERV NT 6.
Reported component ID
5639F2503
Reported release
612
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-02-21
Closed date
2007-02-26
Last modified date
2007-02-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
APPNAPI
Fix information
Fixed component name
COMM SERV NT 6.
Fixed component ID
5639F2503
Applicable component levels
R612 PSY
UP
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSHQNF","label":"Communications Server for Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"612"}]
Document Information
Modified date:
06 October 2021