PK72660: APPLICATION UPDATE HANGS. INCORRECT MESSAGE DURING CLUSTER MEMBER CREATION WHEN IT FAILS.

Fixes are available

APAR status

Closed as program error.

Error description

Application update using incorrect Enterprise Archive (ear)
file causes a hang.
The createClusterMember command reports an incorrect message
when it fails due to an incompatible feature pack installed in
the node.
Application Server for z/OS version 7 server does not start in
a mixed cell environment when there are nodes of a lower
version within the same LPAR.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: The APAR has fixed the following        *
*                      problems:                               *
*                      1. Application update hangs when        *
*                      incorrect ear file is specified to      *
*                      perform full update.                    *
*                      2. createClusterMember command          *
*                      reports incorrect message due to        *
*                      new member is not compatible with the   *
*                      existing cluster members.               *
*                      3. zOS version 7 server does not        *
*                      start in mixed cell when there are      *
*                      lower version of V6.1 nodes within the  *
*                      same LPAR.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following 3 problems are reported in this APAR:

1. When an application update is performed using properties
file based configuration with an ear file that does not exist,
the thread hangs.

An example properties file that can be used to reproduce the
problem:
app.template (property file)
#
# Create parameters
# Replace the line `SKIP=true` with 'SKIP=false' under each
section that is needed
# Set necessary parameters under each command or step sections
# Invoke applyConfigProperties command using this properties
file.
# Use this section to update an application with a complete
ear file.
# Update ResourceId field with appname (
ResourceId=Deployment=appName )
#

#
ResourceType=Application
ImplementingResourceType=Application
ResourceId=Deployment=DefaultApplication
SKIP=false
CreateDeleteCommandProperties=true
#

#
#Properties
#
Name=DefaultApplication #required
useDefaultBindings=true #required
operationType=update #required
contentFile=c:/apps/app1/newApp1.ear #required (actual file to
updatewith)
Update=true #required
contentType=app #required

Command to use from wsadmin:

wsadmin> $AdminTask applyConfigProperties {-propertiesFileName
app.template }

2. When a new cluster member is created on a cluster that
already has some existing cluster members and the application
targeted on the cluster requires some feature packs being
installed on the node and the node selected for the new member
does not have the required feature pack, the create cluster
member command fails as expected. But the error reported is
not meaningful.

For example: Trying to add a V6.1 Feature Pack for Web Services
server to a Feature Pack for EJB 3.0 cluster on the WebSphere
Application Server v7 deployment manager with a Feature Pack
for EJB 3.0 application already installed using the
AdminClusterManagement.createClusterMember wsadmin procedure
returns:

Exception: com.ibm.ws.scripting.ScriptingException
com.ibm.ws.scripting.ScriptingException:
com.ibm.websphere.management.cmdframework.CommandValidationExcep
tion:
ADMG9249E: Exception caught validating the memberConfig step
of the createClusterMember task command:
com.ibm.websphere.management.cmdframework.CommandValidationExcep
tion:
ADMA0111E:  The following J2EE and deployment options 14 are
selected, but are not supported
while installing an application on nodes svt219Node01 of
version 6;

3. Application Server V7.0 server fails to start in mixed-cell
with one Application Server V6.1 node and one Application
Server V7.0 node within same LPAR.

Problem conclusion

1. Application update hangs with property file configuration:
Fixed the code to check for a non-existing file and report the
error.

2. createClusterMemeber reports incorrect message:
Fixed the code to return a more meaningful error message.

3. V7 server fails to start in mixed cell:
Changed the code to always start the server daemon at the
highest level.


The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK72660
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-23
Closed date
2008-10-01
Last modified date
2008-10-01

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
23 October 2021

Tips

PK72660: APPLICATION UPDATE HANGS. INCORRECT MESSAGE DURING CLUSTER MEMBER CREATION WHEN IT FAILS.

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

Document Information

Share your feedback

Need support?