Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
In an environment where access to many ports is blocked by RACF, cell profile creation might fail with: INSTCONFFAILED: The profile could not be created. <WASHOME>/logs/manageprofiles/default/createDefaultServer.log will show this error message: WASX7015E: Exception running command: "$AdminTask createApplicationServer aaaaa {-name bbbbb -specificShortName BBBBB -generic com.ibm.websphere.management.exception.ConfigServiceException: Resolved port number 65536 is out of range.
Local fix
Use genUniquePorts to cause the port scanner code to not run. Here are the steps to use this: 1) In the <WAS_HOME>/profileTemplates directory, locate this file and make a backup copy: cell\dmgr\actions\createDefaultServer.ant 2) Open the original in an editor and towards the bottom, you will find a line: command="$AdminTask createApplicationServer ... -bitmode ${bits}}" 3) change the end of it from }}" (bracket, bracket, quote) to } -genUniquePorts false}" (bracket, space, -genUniquePorts, space, false, bracket, quote) 4) Save the file and run profile creation.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5. * **************************************************************** * PROBLEM DESCRIPTION: Cell profile creation fails with a * * port number out of range message, even * * though all ports are explicitly * * supplied by the user. * **************************************************************** * RECOMMENDATION: * **************************************************************** Cell profile creation scans for available ports for the default application server. This behavior is consistent with distributed platforms, but on Z/OS it can occur even when all ports have been explicitly specified by the Z-PMT tool. In a restricted environment, the unnecessary port availability checking could cause profile creation to fail.
Problem conclusion
The port availability scan for the default application server included in the cell profile on Z/OS is no longer performed, as the port information is already supplied to or otherwise determined by the Z-PMT tool. APAR PI21144 is currently targeted for inclusion in Fix Pack 8.5.5.4 of WebSphere Application Server V8.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
In the WAS_HOME/profileTemplates directory, within cell/dmgr/actions/createDefaultServer.ant, change: ${z.appserver.cluster.transition.name} to: ${z.appserver.cluster.transition.name} -genUniquePorts false
Comments
APAR Information
APAR number
PI21144
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-07-01
Closed date
2014-08-04
Last modified date
2014-08-04
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022