PK72319: ADMINAGENT REGISTERED BASE SERVER USES OLD FILETRANSFER PORT

Fixes are available

APAR status

Closed as program error.

Error description

When a base server is registered to an admin agent, you can
still connect to the base server directly via wsadmin using the
base server port.  When using the file transfer mechanism such
as for the AdminConfig extract command, file transfer used to be
listening on port 9043 for the base server, but is now
listening on port 9044 through the AdminAgent. However, the
base server thinks that port 9043 is the port for file
transfers, when it  should be port 9044 instead. This might
result in the error:
java.net.ConnectException: Connection refused

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server       *
*                  version 7.0 that have admin agent profiles  *
****************************************************************
* PROBLEM DESCRIPTION: There are two problems resolved by      *
*                      this APAR. A description of both        *
*                      follows:                                *
*                      a) A node registered to an AdminAgent   *
*                      uses the old filetransfer port.         *
*                      b) When a node is deregistered from     *
*                      the AdminAgent, some threads continue   *
*                      to run and some memory is not           *
*                      released.                               *
*                      If nodes are repeatedly registered      *
*                      and then deregistered an out of         *
*                      memory condition can occur.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
For both problems being resolved:
a) An un-registered base application server uses port X for
filetransfer client.  When that base application server is
registered to an AdminAgent, the AdminAgent
now has the filetransfer port Y.   Filetransfer client should
use port Y even if an admin client(e.g. wsadmin) connects
directly to the base application server.   In this error case,
filetransfer client is getting the wrong port from the
Repository and connecting to port X incorrectly.  This results
in an exception during filetransfer client execution:
java.net.ConnectException: Connection refused: connect
b) When a node is deregistered from the AdminAgent, some
threads continue to run and some memory is not released.  If
nodes are repeatedly registered and then deregistered an out
of memory condition can occur.

Problem conclusion

For each problem:
a) Repository code has been updated to return the AdminAgent's
filetransfer client port for a registered node.
b) Code was updated to stop a repository thread and release
admin security objects in an admin agent when a node is
deregistered.

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
PK72319
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-17
Closed date
2008-11-03
Last modified date
2008-11-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
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

PK72319: ADMINAGENT REGISTERED BASE SERVER USES OLD FILETRANSFER PORT

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?