PK82138: WSADMIN USING WRONG DEFAULT PORT IN CELL PROFILE.

Fixes are available

APAR status

Closed as program error.

Error description

When creating a cell profile, running ./wsadmin.sh from the
AppSrv profile bin directory attempts to connect to 8880 by
default instead of 8879. When run from the Dmgr profile bin
directory, it connects correctly to 8879.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: 1. wsadmin using wrong default port in  *
*                      Cell profile                            *
*                      2. PMT augmentation of SCA is           *
*                      permitted and fails                     *
*                      3. -unaugmentAll exception if           *
*                      profiles never created.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1. When running wsadmin.sh from a cell's application server
profile's bin directory, an attempt is incorrectly made to
port 8880 by default rather than port 8879. However, when run
from the Dmgr profile's bin directory it connects correctly to
port 8879.
2. After augmenting a profile via Profile Management Tool (PMT)
and selecting "yes" to augment another profile, a panel is
presented where you are only permitted to re-augment the same
profile with the same augment.
3. When invoking the manageprofiles command with a mode of
-unaugmentAll, an exception is thrown if a profile has not
been previously created.

Problem conclusion

1. Cell default profile template's updatePorts.ant config action
was fixed to reference the correct portdef.props file where the
correct default port is defined.
2. The checkbox indicating that another profile is to be
augmented has been removed.
3. The profiles framework was enhanced to recognize that the
non-existence of a profile registry is a valid scenario and is
semantically equivalent to an empty profile registry.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5  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
PK82138
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
2009-03-09
Closed date
2009-05-01
Last modified date
2009-05-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:
24 October 2021

Tips

PK82138: WSADMIN USING WRONG DEFAULT PORT IN CELL PROFILE.

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?