PM99024: JAVA.LANG.RUNTIMEEXCEPTION NOT BEING CAUGHT BY HPEL ON Z/OS APPLICATION SERVER

Fixes are available

APAR status

Closed as program error.

Error description

In this case, there was not space on the file system to write
out messages and the HPEL code
com.ibm.ws.logging.hpel.impl.LogRepositoryManagerImpl.getControl
lingProc
essDirectory(LogRepositoryManagerImpl.java:598) took a
java.lang.RuntimeException.  This exception was not caught, and
cased the control region to terminate.  The HPEL could should
catch this exception and handle it.

The control region joblog had these messages
Trace: 2013/07/31 10:59:26.979 02 t=8B7250 c=UNK key=S2 tag=
(13007004)
  SourceId: com.ibm.ws.hamanager.impl.HAGroupImpl
  ExtendedMessage: HMGR0132I: The local member of group
GN_PS=CEL_Intranet_zOS_B\MAN_apwastib2\APP_apwastib2_U,IBM_hc=CL
S_U,SFS_UUID
=CA9910C5D59F5A2500000300000000A300000000,SVR_SHORT=WTIB2SU,type
=WAS_TRANSACTIONS failed to respond properly to a health check.
The exception is java.lang.RuntimeException: Failed to create
instance log repository. See SystemOut.log for details.
 at
com.ibm.ws.logging.hpel.impl.LogRepositoryManagerImpl.getControl
lingProcessDirectory(LogRepositoryManagerImpl.java:598)
 at
com.ibm.ws.logging.hpel.impl.LogRepositoryManagerImpl.calculateL
ogFile(LogRepositoryManagerImpl.java:540)
 at
com.ibm.ws.logging.hpel.impl.LogRepositoryManagerImpl.startNewFi
le(LogRepositoryManagerImpl.java:550)
 at
com.ibm.ws.logging.hpel.impl.LogRepositoryWriterImpl.logRecord(L
ogRepositoryWriterImpl.java:160)
 at
com.ibm.ws.logging.hpel.handlers.LogRecordHandler.processEvent(L
ogRecordHandler.java:111)
 at
com.ibm.ws.logging.hpel.handlers.LogRecordHandler.publish(LogRec
ordHandler.java:245)
 at java.util.logging.Logger.log(Logger.java:1281)
 at com.ibm.ejs.ras.Tr.logToJSR47Logger(Tr.java:1712)
 at com.ibm.ejs.ras.Tr.fireEvent(Tr.java:1667)
 at com.ibm.ejs.ras.Tr.fireTraceEvent(Tr.java:1586)
 at com.ibm.ejs.ras.Tr.entry(Tr.java:838)
 at
com.ibm.ws.recoverylog.spi.RLSHAGroupCallback.isAlive(RLSHAGroup
Callback.java:439)
 at
com.ibm.ws.hamanager.impl.HAGroupImpl.doIsAlive(HAGroupImpl.java
:864)
 at
com.ibm.ws.hamanager.impl.HAGroupImpl$HAGroupUserCallback.doCall
back(HAGroupImpl.java:1388)
 at com.ibm.ws.hamanager.impl.Worker.run(Worker.java:64)
 at
com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1691)
. The JVM will be terminated.
Trace: 2013/07/31 10:59:40.965 02 t=8B7250 c=UNK key=S2 tag=
(8700D41C)
  Description: Log Boss/390 Error
  from filename: ./bbglsys.cpp
  at line: 1052
  error message: BBOO0157E JVM EXIT API DRIVEN. JVM EXITING
WITH CODE=31
Trace: 2013/07/31 10:59:41.034 02 t=8E5840 c=UNK key=S2 tag=
(84005969)
  Description: Log Boss/390 Error
  from filename: ./bbgoboai.cpp
  at line: 2409
  error message: BBOO0006E WEBSPHERE FOR Z/OS PROCESS WTIB2SU
ENDED ABNORMALLY, REASON=C9C21236.

Local fix

ensure there is enough space in the file system for logging

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0 and V8.5                        *
****************************************************************
* PROBLEM DESCRIPTION: Unable to create instance directory     *
*                      for logging , if lock file get          *
*                      removed.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If lock file present in Log Directory got removed , then
RuntimeException is thrown from HPEL component , which can
cause JVM termination.

Problem conclusion

Now, if somehow lock file is removed which is required to
create instance directory under HPEL , then instead of
throwing RuntimeException , logDirectory with Label
"XXXXXXX" will be created.

APAR PM99024 is currently targeted for inclusion in Fix
Packs 8.0.0.9 and 8.5.5.2 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PM99024
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-10-14
Closed date
2013-12-17
Last modified date
2014-05-21

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
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022

Tips

PM99024: JAVA.LANG.RUNTIMEEXCEPTION NOT BEING CAUGHT BY HPEL ON Z/OS APPLICATION SERVER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?