PK75279: IF A REMOTE HOST ADDRESS IS PASSED TO THE IPC CONNECTOR, THE LATTER MAY IGNORE IT AND STILL CONNECT TO LOCALHOST

Fixes are available

APAR status

Closed as program error.

Error description

On zOS, whenever condition is right, the IPC connector will use
the localcomm channel instead of the TCP channel. And when
localcomm is used, the target host address is ignored. So if a
remote host is passed in (which is invalid and should trigger an
 exception if in "normal" situation with TCP), IPC will ignore
it and still connect to the localhost. This causes confusion.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: Correct several admin problems.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The APAR corrects the following problems:
1 - The localcomm channel always assumes localhost as the
target host and ignores the hostname passed in. If you
unwittingly point the IPC connector to a remote host, the
localcomm channel will connect to localhost anyway as long as
the port matches. This will be confusing.

2 -The product name "EXPRESS" is relatively recent, and the
code was still checking for the old name "embeddedExpress". Not
finding any match, the code proceeds to return the stack
product (SCA) level.

3 - During server startup in the servant region, a
NullPointerException is thrown in ffdc. This not only clutters
the servant log but also introduces certain performance lag.

Problem conclusion

1 - The solution is, when the target host passed in is not
localhost, disable localcomm channel, thus leaving only the
normal TCP channel in place which will fail the connection if
any of the hostname or port specs mismatch.

2 - The solution is to update the matching string in the
code from the old "embeddedExpress" to the new name "EXPRESS".

3 - The code contains a defect which makes a call that is not
valid in the servant region. The solution is to add additional
check in the code so that the call does not apply to the
servant region.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.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
PK75279
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-11-07
Closed date
2009-02-23
Last modified date
2009-02-23

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

PK75279: IF A REMOTE HOST ADDRESS IS PASSED TO THE IPC CONNECTOR, THE LATTER MAY IGNORE IT AND STILL CONNECT TO LOCALHOST

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?