Dynamic status port configuration for WebSphere Application Server startup
 Technote (troubleshooting)
 
Problem(Abstract)
How to assign a specified port for was.status.socket, which by default is dynamically allocated by the launcher.
 
Resolving the problem
To find out what port was dynamically assigned, use the following command:

ps -ef|grep >
-Dwas.status.socket=XXXXX


IBM® WebSphere® Application Sever uses the was.status.socket property to tell the "launcher" about the start-up status. The Application Server launcher could also be the NodeAgent.

Before an application server is launched, the launcher acquires a free port from the operating system and then sets the was.status.socket property and gives it to Application Server during the launch process.

WebSphere Application Server sends the status about the start up to this port and the launcher grabs the information and proceeds. This property is dynamically set by the launching application and passed on to Application Server.

The status port can be set while launching the node, manager, or server from the command line using the -statusPort parameter option with startNode, startManager, or startServer commands.

The status port can also be configured by setting the Java™ system property: was.status.socket. IBM recommends allowing the Application Server to pick up the status port dynamically so that there will not be any port conflicts.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): z/OS
Software version: 5.1.1.8
Software edition:
Reference #: 1231480
IBM Group: Software Group
Modified date: Aug 31, 2007