PQ66255: COM.IBM.EJS.SM.UTIL.PROCESS.EXCEPTION.PROCESSOPEXCEPTION ERROR CREATING NEW PROCESS MSG UNDER LARGE NUMBER OF EJBS

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as documentation error.

Error description
WebSphere ManagedServer startup failed with following msg
Failed to start the server: "SVR_NAME"
com.ibm.ejs.sm.util.process.exception.ProcessOpException: Error
creating new process.
at com.ibm.ejs.sm.util.process.Win32ProcessGlue.create
at com.ibm.ejs.sm.util.process.Win32Process.create
at com.ibm.ejs.sm.util.process.ProcessFactory.create
at com.ibm.ejs.sm.active.ActiveServerProcess.startAction
at com.ibm.ejs.sm.active.ActiveEJBServerProcess.startAction
at com.ibm.ejs.sm.active.ActiveObject.startObject
at com.ibm.ejs.sm.active.ActiveObject.start
at java.lang.reflect.Method.invoke
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject
at com.ibm.ejs.sm.agent._AdminAgent_Stub.invokeActiveObject
at com.ibm.ejs.sm.beans.LiveRepositoryObjectImpl$StartTask.execu
at com.ibm.ejs.sm.util.task.AsyncTaskEngine$WorkerThread.run
.
With the very long -epmSpec options in given command line
arguments with above message.
Local fix
Use epm=XXX or any others with ManagedServer's EPN spec field
cf:
epm=none
epm=high
cf:epm=noneepm=high
Problem summary
****************************************************************
* USERS AFFECTED: The users of WebSphere Application Server    *
*                 Version 3.5.7.                               *
****************************************************************
* PROBLEM DESCRIPTION: There are situations where a long EPM   *
*                      specification string causes a failure   *
*                      to start the WebSphere Application      *
*                      Server.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
There are situations where a long EPM specification string
causes failure to start the WebSphere Application Server. It
happens when there are a large number of EPM module objects
that have different EPM levels from their parents.

To work around this problem, choose one of the following
methods:

. In Resource Analyzer, set the EPM level at the root or the
top level EPM module objects

. In the administrative console, set epm=high as the EPM
specification string and restart the WebSphere Application
Server. This enables all the EPM counters.
methods:. In Resource Analyzer, set the EPM level at the root or thetop level EPM module objects. In the administrative console, set epm=high as the EPMspecification string and restart the WebSphere ApplicationServer. This enables all the EPM counters.
Problem conclusion
Close this APAR as a documentation change.
(Version 3.5.7 Release Notes)
Temporary fix
Comments
APAR information
APAR numberPQ66255
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED DOC
PENoPE
HIPERNoHIPER
Submitted date2002-09-17
Closed date2002-10-29
Last modified date2002-10-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros

Fix information
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ66255
IBM Group: Software Group
Modified date: 2002-10-29