PQ55060: XMLCONFIG TRANSPORT PORT

 A fix is available

PQ55060, 4.0.1: XMLConfig does not create Application Server transport ports



APAR status
Closed as unreproducible.

Error description
When an Application Server is created using XMLConfig in WAS 401
the Transport Port number generated is 9080, which is the same
one used by the Default Server. Is there a way that the port be
autogenerated to a number. Testing of early WAS 4.02 drivers
does auto generate the value. Need e-fix for WAS 4.01
.
Verified that a unique transport port is generated with WAS 4.01
when using the Create Application Server Wizard, or when
creating a new application server from the topology tree.
.
Please see PMR for details.
.
Also see 
PQ52555 as it is somewhat related.
Local fix
I suggest ensuring that <transport-port></transport-port> tags
are provided in all imported XML files to work around the
problem. If you can verify that this problem is indeed fixed in
WAS 4.02, then request that an e-fix be created for WAS 4.01.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 release 4.01                                 *
****************************************************************
* PROBLEM DESCRIPTION: When applicatication server is created  *
*                      using XMLConfig and the input  xml file *
*                      does not contain webcontainer port      *
*                      information, XMLConfig fails to assign  *
*                      a unique port number to the newly       *
*                      created application server, the port    *
*                      assigned is always 9080.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When application server is created using XMLConfig and the
input  xml file  does not contain  webcontainer port
information,  XMLConfig fails to assign unique port number to
the newly created application server, the port assigned is
always 9080.
Problem conclusion Temporary fix
The solution to this problem is part of upcoming 402.
Meanwhile the users of WebSphere Application Server 4.01 can
use e-fix PQ55060_eFix_AEServer to solve the problem.
Comments
APAR information
APAR number PQ55060
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED UR5
PE NoPE
HIPER NoHIPER
Submitted date 2001-11-20
Closed date 2001-11-29
Last modified date 2001-11-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

SRLS

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ55060
IBM Group: Software Group
Modified date: Nov 29, 2001