PK85069: WEBSPHERE SERVER ABENDS WHEN SMF ENABLED AT STARTUP WITH BBOO0158E, BBOO0006E, C9C2120C.

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere Application Server when SMF enabled may abend during
startup. We noticed the servant process abends with a tdump
and the joblog has the the below messages.

Trace: 2009/04/02 16:16:40.004 01 t=AD1E88 c=UNK key=P8
(0000000A)
  Description: Log Boss/390 Error
  from filename: ./bbglsys.cpp
  at line: 928
  error message: BBOO0158E JVM ABORT API DRIVEN. JVM ABORTING.
Trace: 2009/04/02 16:16:40.011 01 t=AD1E88 c=UNK key=P8
(0000000A)
  Description: Log Boss/390 Error
  from filename: ./bbgoboai.cpp
  at line: 5833
  error message: BBOO0006E WEBSPHERE FOR Z/OS PROCESS WTES711
ENDED ABNORMALLY, REASON=C9C2120C.
Trace: 2009/04/02 16:16:40.028 01 t=AD4B50 c=UNK key=P8
(04030001)
  Description: enter RestartThreadRtn
  thread type: 6
  ORB request pointer: 0

The callstack of the abending tcb from the TDUMP, which can also
be found in the joblog.

Trace: 2009/04/02 16:15:01.808 01 t=AD1E88 c=UNK key=P8 (0407201
  Description: Java exception created
  from filename: ./bbgocjex.cpp
  Method Name: createExceptionForJava(JNIEnv *, char *, unsigned
int, CORBA::CompletionStatus, CORBA::Exception *, char *,
CORBA::Boolean, CORBA::Boolean) java.lang.NoClassDefFoundError:
UNKNOWN
 at com.ibm.ws390.sm.smf.SmfJActivity.saveSmfRequestTracker
 Values(Native Method)
 at com.ibm.ws390.sm.smf.SmfDispatchEventRecorder.
 endDispatch(SmfDispatchEventRecorder.java:236)
 at com.ibm.ejs.container.DispatchEventListenerManager.
 callDispatchEventListeners(DispatchEventListenerManager.java:1
 at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.
 at xx.yyy.ejb.soa.EJSLocalStatelessSOAInitializer_5718e302.ini
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcc
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingM
 at java.lang.reflect.Method.invoke(Method.java:599)
 at xx.yyy.zz.ejb.EJBInvocationHandler.invoke(EJBInvocationHand
 at &#65423;Proxy22.init(Unknown Source)
 at xx.yyy.zz.servlets.CLInitializationServlet.initSOA(CLInitia
 at xx.yyy.zz.servlets.CLInitializationServlet.init(CLInitializ
 at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(Servlet
 at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(Ser
 at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(S
 at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.
 at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappi
 at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationF
 at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebApp
 at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplicati
 at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(V
 at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebConta
 at com.ibm.ws.webcontainer.WSWebContainer.run(WSWebContainer.j
 at java.lang.Thread.run(Thread.java:735)
Caused by: java.lang.ClassNotFoundException: UNKNOWN
 at java.lang.Throwable.<init>(Throwable.java:80)
 at java.lang.ClassNotFoundException.<init>(ClassNotFoundExcept
 at org.eclipse.osgi.framework.internal.core.BundleLoader.findC
 at org.eclipse.osgi.framework.internal.core.BundleLoader.findC
 at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.lo
 at java.lang.ClassLoader.loadClass(ClassLoader.java:609)
 ... 25 more


Note: The problem symptom is highly intermittent.

Local fix

```
Disable SMF.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
*                      fails to start when SMF 120 subtype 9   *
*                      records and the CPU usage subsection    *
*                      are enabled.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Certain types of threads lack a request-specific object that
is used in generating the SMF 120 subtype 9 CPU usage
subsection.  When WebSphere Application Server for z/OS
attempts to write out the SMF 120 subtype 9 CPU usage
subsection, it encounters a null pointer, which causes the
server to terminate.

Problem conclusion

The SMF 120 subtype 9 CPU usage subsection will now only be
written from threads that contain the necessary
request-specific object.

APAR PK85069 is currently targeted for inclusion in
Service Level (Fix Pack) 7.0.0.5 of WebSphere
Application Server  for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK85069
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-21
Closed date
2009-05-05
Last modified date
2009-08-03

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

R700 PSY UK48200
UP09/07/27 P F907

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK85069: WEBSPHERE SERVER ABENDS WHEN SMF ENABLED AT STARTUP WITH BBOO0158E, BBOO0006E, C9C2120C.

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

R700 PSY UK48200

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?