PM44368: INVALID CASES OF MULTIPLE PROCESS DEFINITIONS IN SERVER.XML ARE NOT DETECTED BY "$ADMINCONFIG VALIDATE" OR VIA ADMIN CONSOLE

Fixes are available

APAR status

Closed as program error.

Error description

Validation of configuration files, as performed by "$AdminConfig
validate", or as triggered by the Administrative Console does
not detect non-valid cases where multiple process definitions
are present in the server configuration file. (server.xml).
Except when configuring for a target platform of native Z/OS,
having multiple process definitions is not valid.  Outside of
native Z/OS, having multiple process definitions configured can
cause process launch failures, generally leading to a sever
loss of function.

Local fix

Manually correct process definition statement in server.xml
file.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 and V8.0 modifying the server   *
*                  configuration.                              *
****************************************************************
* PROBLEM DESCRIPTION: Configuration Validation does not       *
*                      check for multiple Process Definitions  *
*                      in server.xml.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Multiple Process Definitions are only allowed for WebSphere
Application Server installations on z/OS. These process
definitions exist in server.xml. For example:
</processDefinitions>
<processDefinitions xmi:type="processexec:JavaProcessDef"
xmi:id="JavaProcessDef_1183122130082"
workingDirectory="${USER_INSTALL_ROOT}"
executableTargetKind="JAVA_CLASS"
executableTarget="com.ibm.ws.runtime.WsServer">
<execution xmi:id="ProcessExecution_1183122130078"
processPriority="20" runAsUser="" runAsGroup=""/>
<ioRedirect xmi:id="OutputRedirect_1183122130078"
stdoutFilename="${SERVER_LOG_ROOT}/native_stdout.log"
stderrFilename="${SERVER_LOG_ROOT}/native_stderr.log"/>
<monitoringPolicy xmi:id="MonitoringPolicy_1183122130078"
maximumStartupAttempts="3" pingInterval="60" pingTimeout="300"
autoRestart="true" nodeRestartState="STOPPED"/>
<jvmEntries xmi:id="JavaVirtualMachine_1183122130078"
verboseModeClass="false" verboseModeGarbageCollection="false"
verboseModeJNI="false" runHProf="false" hprofArguments=""
debugMode="false"
debugArgs="-
agentlib:jdwp=transport=dt_socket,server=y,suspend=n
,address=7777" genericJvmArguments="">
<systemProperties xmi:id="Property_1"
name="com.ibm.security.jgss.debug" value="off"
required="false"/>
<systemProperties xmi:id="Property_2"
name="com.ibm.security.krb5.Krb5Debug" value="off"
required="false"/>
</jvmEntries>
</processDefinitions>
The existence of more than one Process Definition may lead to
start-up failures on other operating system. Configuration
Validation, which can be run by '$AdminConfig validate' or the
Administrative Console, does not check for this condition and
flag it as an error.

Problem conclusion

The Configuration Validation component has been updated to
check for multiple Process Definitions. If the operating system
is not z/OS, an error message will be generated. For example:

WASX7195I: Severity 1; line 0; target
"Websphere:_Websphere_Config_Data_Display_Name=server1,_Webspher
e_Config_Data_Type=Server,_Websphere_Config_Data_Id=cells/JasonB
-w520Node11Cell/nodes/JasonB-w520Node11/servers/server1|server.x
ml#Server_1183122130078,_WEBSPHERE_CONFIG_SESSION=Script133480ce
836"; CHKW2260E: The server.xml file for server server1 has
too many process definitions

A work-around is to remove the extra Process Definition by
using the scripting console's $AdminConfig function.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.23 and 8.0.0.3.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM44368
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-25
Closed date
2012-01-03
Last modified date
2012-01-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 APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP

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

Document Information

Modified date:
27 October 2021

Tips

PM44368: INVALID CASES OF MULTIPLE PROCESS DEFINITIONS IN SERVER.XML ARE NOT DETECTED BY "$ADMINCONFIG VALIDATE" OR VIA ADMIN CONSOLE

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

R800 PSY

Document Information

Share your feedback

Need support?