PQ85467: MODIFYING HTTPTRANSPORT CONFIGURATION USING WSADMIN.SH. WSADMIN ALTER THE PORT ALREADY IN USE BY ANOTHER SERVER ON THE SAME HOST | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When modifying HTTPTransport configuration using wsadmin.sh. The current behavior using wsadmin is when attempting to alter the port on a server to a value already in use by another server on the same host, an adjustPort() method is called to pick the next available port and configure to this value instead: .. WASX7209I: Connected to process "dmgr" on node PLEX1Manager using SOAP connector ; The type of process is: DeploymentManager WASX7029I: For help, enter: "$Help help" wsadmin>set http [lindex [$AdminConfig list HTTPTransport] 3] (cells/PLEX1Network/nodes/SY1/servers/clusterServer1: server.xml#HTTPTransport_2) wsadmin>$AdminConfig showall $http {address {{host *} {port 0}}} {external false} {properties {}} {sslConfig SY1/DefaultHTTPS} {sslEnabled true} wsadmin>set address [list [list address [list [list host *] [list port 9086]]]] {address {{host *} {port 9086}}} wsadmin>$AdminConfig modify $http $address .. wsadmin>$AdminConfig save .. wsadmin>$AdminConfig showall $http {address {{host *} {port 9087}}} {external false} {properties {}} {sslConfig SY1/DefaultHTTPS} {sslEnabled true} wsadmin> .. You can get around the problem by using the admin console. You are able to specify the port to the value they choose which is the desired results for your case. .. From investigation we find that wsadmin.sh is working as designed as we are trying to avoid port conflicts on the host system and that the admin console is in error as it is supposed to use the adjustPort() method also. .. However, if you are configured to use VIPA, you need to be able to specify the same port value on different servers on (what seems to be, via host name and ip address) the same host. .. The customer was attempting to script all of our resoures, cluster and Server creation. The transports can be created OK but the wsadmin forces the ports to be unique and does not honor the ports the customer we specified. .. The customer have a need to have servers in the same cluster with the same host/port assignments since we are using DVIPAs for our HTTP connectivity. These servers are in different nodes so there should be no problems. ..Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: By default, the WSADMIN scripting * * client will ensure all ports on a z/OS * * system are unique. This can be a * * problem for customers implementing the * * VIPA technology in their environment. * * In the case of VIPA, a server may need * * to share the same port number as * * another server on the same system. * **************************************************************** * RECOMMENDATION: * **************************************************************** Creation/modification of servers via wsadmin scripting forces port definitions between servers to be unique which conflicts with VIPA technology. Currently, scripting will automatically choose the next available port if the choosen port for the configuration update is already in use. Example: Modifying HTTPTransport configuration from using port 0 to use port 9086, but 9086 is already in use by a server on the system. WASX7209I: Connected to process "dmgr" on node PLEX1Manager using SOAP connector; The type of process is: DeploymentManager WASX7029I: For help, enter: "$Help help" wsadmin>set http lindex $AdminConfig list HTTPTransport 3 (cells/PLEX1Network/nodes/SY1/servers/clusterServer1:server. xml#HTTPTransport_2) wsadmin>$AdminConfig showall $http {address {{host *} {port 0}}} {external false} {properties {}} {sslConfig SY1/DefaultHTTPS} {sslEnabled true} wsadmin>set address list list address list list host * list port 9086 {address {{host *} {port 9086}}} wsadmin>$AdminConfig modify $http $address wsadmin>$AdminConfig save wsadmin>$AdminConfig showall $http {address {{host *} {port 9087}}} {external false} {properties {}} {sslConfig SY1/DefaultHTTPS} {sslEnabled true} wsadmin>Problem conclusion The fix to this apar introduces a new attribute, adjustPort, that allows a customer to specify if WebSphere should adjust server ports so they are unique. When adjustPort is true, port adjustment will take place. When false, port adjustment will not take place. If adjustPort is not specified, by default ports will be adjusted. Example1: (creating a new server) set node $AdminConfig getid /Node:SY1/ $AdminConfig create Server $node {{name serv}{adjustPort false}} $AdminConfig save Example2: (modifying HttpTransport configuration) set http lindex $AdminConfig list HTTPTransport 3 set address list list address list list host * list port 9082 list adjustPort false $AdminConfig modify $http $address $AdminConfig save $AdminConfig showall $http This APAR requires a change to the InfoCenter. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ The change is to InfoCenter article "Example: Migrating - Creating an application server (rxml_mcreateserv), which now reads: When using the wsadmin tool, server ports are uniquely generated by default. You can disable this behaviour using the adjustPort parameter. For example: $AdminConfig create Server $node {{name myserv} {adjustPort false}} $AdminConfig save The value of the adjustPort parameter is set to true by default. If you set the value of the adjustPort parameter to false, ports will not be made unique by the wsadmin scripting tool. The change is to InfoCenter article "Example: Migrating - Modifying the virtual host (rxml_mvhost), which now reads: When using wsadmin, server ports are uniquely generated by default. To disable the unique generation of ports via wsadmin use the following example: set def_host $AdminConfig getid /VirtualHost:default_host/ $AdminConfig modify $def_host {{aliases {{{port 80} {hostname *}} {{port 9080} {hostname *}} {{port 9081} {hostname *}}}} {adjustPort false}} $AdminConfig save The value of the adjustPort parameter is set to true by default. If you set the value of the adjustPort parameter to false, unique ports will not be generated. APAR PQ85467 is associated with SERVICE LEVEL W502015 of WebSphere Application Server V5.1.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ89466 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ85467.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ85467
IBM Group: Software Group
Modified date: Oct 5, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.