PK71761: MIGRATION OF DEPLOYMENT MANAGER FAILS TO STOP ACTIVE DMGR

Fixes are available

APAR status

Closed as program error.

Error description

In secure migrations to v7, a signer exchange prompt may appear
in the logs or trace during the migration when the
WASPostUpgrade process attempts to stop the running dmgr
process.  This prompt cannot be responded to and so the stop
action fails to stop the old dmgr process.

Local fix

Stop the active dmgr process prior to attempting WASPostUpgrade,
or perform the dmgr migration specifying the option
"-keepDmgrEnabled true", to keep the previous release deployment
 manager enabled.

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server Migration      *
*                  Tools users using Network Deployment        *
****************************************************************
* PROBLEM DESCRIPTION: Migration cannot find the correct       *
*                      SSL keys when trying to stop a          *
*                      running deployment manager that is      *
*                      being migrated.                         *
****************************************************************
* RECOMMENDATION:  Apply this fix, or stop the old deployment  *
*                  manager process, or run the migration       *
*                  specifying the -keepDmgrEnabled true option *
****************************************************************
The runtime tools cache the v7 autogenerated default keystores
early in WASPostUpgrade processing.  This cache is not updated
during the migration, so the incorrect keys are located when
the WASPostUpgrade tool attempts to stop the running
deployment manager process.  This will only occur if the
original configuration uses the default keystores, and those
keystores match the names used by the v7 autogenerated default
keystores.  This case occurs for customers using default *.p12
keystores in v6.1 migrating to v7.

Problem conclusion

The migration has been updated to flush the keystore cache
prior to connecting to the deployment manager process so the
migrated keystores will be used.

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
PK71761
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-09
Closed date
2008-09-17
Last modified date
2008-09-17

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022

Tips

PK71761: MIGRATION OF DEPLOYMENT MANAGER FAILS TO STOP ACTIVE DMGR

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?