Fixes are available
APAR status
Closed as program error.
Error description
Worklight Server v7.0 and v7.1 may experience a memory leak, resulting in a out of memory event. The reason for the memory leak is one of the "Default Executor-thread-xxxx" threads being deadlocked, waitng for " com/worklight/core/auth/impl/AuthenticationContext", as can be seen in a javacore dump: 1LKDEADLOCK Deadlock detected !!! NULL --------------------- NULL 2LKDEADLOCKTHR Thread "Default Executor-thread-4858" (0x00000000F02BBD00) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00007F85BA192538 infl_mon_t: 0x00007F85BA1925B0: 4LKDEADLOCKOBJ com/worklight/core/auth/impl/AuthenticationContext@0x00000000183 4C650 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "Default Executor-thread-4846" (0x00000000F08DEB00) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00007F85BA10C158 infl_mon_t: 0x00007F85BA10C1D0: 4LKDEADLOCKOBJ com/ibm/ws/session/store/memory/MemorySession@0x00000000196C9170 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "Default Executor-thread-4858" (0x00000000F02BBD00) NULL NULL ---------------------------------------------------------------- -------- As a result of this deadlock, Worklight Server won't clean up old sessions, resulting in the number of sessions (com.ibm.ws.session.store.memory.MemorySession class in a heap dump) continuosly growing. Eventually, Worklight Server may run out of memory. Additional Keywords: Worklight Versions Affected: 7.0. 7.1 Initial Impact: High
Local fix
Restart Worklight Server
Problem summary
**************************************************************** * USERS AFFECTED: * * Administrators of a Worklight server who use V7.0 * **************************************************************** * PROBLEM DESCRIPTION: * * Worklight Server v7.0 and v7.1 may experience a memory leak, * * resulting in an out of memory event. * * The reason for the memory leak is a number of threads enter * * a deadlock * * As a result of this deadlocks, Worklight Server won't clean * * up old sessions, resulting in the number of sessions * * continuously growing. * * Eventually, Worklight Server may run out of memory. * **************************************************************** * RECOMMENDATION: * * - * ****************************************************************
Problem conclusion
code was changed to prevent threads from entering a deadlock
Temporary fix
Restart Worklight Server
Comments
APAR Information
APAR number
PI50660
Reported component name
MFPF/WORKLIGHT
Reported component ID
5725I4301
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-10-15
Closed date
2015-10-29
Last modified date
2015-10-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MFPF/WORKLIGHT
Fixed component ID
5725I4301
Applicable component levels
R700 PSY
UP
R710 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZH4A","label":"IBM Worklight"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
17 October 2021