Fixes are available
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
The server unique port generation algorithm is based on the machine host IP. If the port has been used in the dmgr host machine, it will keep increasing by 1 until an unique port is found. However, if appserver node and dmgr have different host aliases or host IPs within the same machine they will be treated as different host machines and duplicate ports can be assigned.
Local fix
Use same host alias/host ip on dmgr and node within same host machine.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Duplicate server ports are assigned * * during server creation when a * * deployment * * manager and node are on the same * * machine * * and using host aliases. * **************************************************************** * RECOMMENDATION: * **************************************************************** The server unique port generation algorithm uses the host IP address as a key to é ádetermine whether the node and deployment manager are in the same host é ámachine. é áIf the node host IP address is same as the deployment manager's address then unique ports will be generated for new servers on the node. é áHowever, if the server node and deployment manager use different host aliases within the é ásame machine, the node would be treated as a different ho machine and é áduplicate server ports could be assigned during server é ácreation. It could cause the following port conflict error é ámessage when starting the server. [1/30/18 13:34:38:520 EST] 00000001 TCPPort é á é á é á E é á é áTCPC0003E: TCP Channel é áTCPInboundChannel_jm.Default_JM_SSL_Port_Connector_Na é á é á é á é á initialization failed. é áThe socket bind failed for host é á é áachflisbatch-cc1-qa2-wsdm.fras.frb.org and port 9421. é áThe é áport may already be in use. é á é á é á
Problem conclusion
It is a bug in the unique server port generation algorithm where é áthe node should not be necessarily treated as a differe host machine even though it has a different host name and IP fro that of the deployment manager. é áIt should also check if mult network interfaces are configured in the é ámachine. é áIf mult network interfaces contain both node and deployment manager host IP addresses, it means both the node and the deployment manager are in the same machine. é á The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.14/9.0.0.8. é áPlease refer to the é áRecommended Up page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI92079
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-04
Closed date
2018-02-05
Last modified date
2018-04-13
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
R850 PSY
UP
Document Information
Modified date:
04 May 2022