z/OS Adjunct region terminated with SEC3 in WAS 6

Technote (troubleshooting)


Problem(Abstract)

z/OS Adjunct region terminated with SEC3 in WAS 6 after ITCAM 6.0 DC was installed

Cause

The root cause of abend SEC3 in the Adjunct region is java.lang.ClassNotFoundException:

com.ibm.ws.naming.util.CyaneaInitCtxFactory.

The Adjunct server is another kind of servant in WAS 6 and uses many of the properties provided on the Servant process definition but not all of them. The servant classpath includes the <DC_HOME>/etc directory which is used to set a JNDI initial context factory for monitoring JNDI requests. However the Adjunct server does not share the classpath with the servant, so it fails with ClassNotFoundException.


Resolving the problem

The adjunct region is started because SIB is enabled in the WAS 6 server. If the customer does not need to run SIB, then they can disable SIB to stop the adjunct region being started with

the application server.

If SIB needs to run, then specify property 'ws.ext.dirs' with <DC_HOME>/lib in the custom properties of the Adjunct's JVM as follows:

1. Select Application servers>your_server>Process
Definitions>Adjunct>Java Virtual Machine>Custom Properties from the WAS administration console.

2. Append the value of <DC_HOME>/lib to the property 'ws.ext.dirs' if it exists; otherwise create property 'ws.ext.dirs' with the value of <DC_HOME>/lib.

3. Save the configuration

4. Re-start the WAS server

Note that <DC_HOME> is the home path of the running DC directory.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Composite Application Manager for WebSphere
ITCAM for WebSphere (z/OS)

Software version:

6.0

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

1254982

Modified date:

2009-10-27

Translate my page

Machine Translation

Content navigation