PQ75322: UNKOWNHOSTEXCEPTION NOT SURFACED DURING APPLICATION CONTROLLER REGION STARTUP WHEN NODE HOST NAME IS INCORRECTLY SET UP

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When customizing for the base app server and starting the
application controller region for the first time, it may
fail if the host name is not set up correctly in TCP/IP.
During app server controller region startup, a getByName is
done in com.ibm.ws.http.HttpTransport.initialize for the
Node host name.  When this fails, it is not reported as a
UnkownHostException.  Instead the exception percolates and
surfaces externally as message:
BBOO0221W ADMC0015W: SOAP connector failed to start with
      exception: mvs02.myhost.com
where the "exception" shows as the host name, in this
example the host name is mvs02.myhost.com.  If there is a
different exception listed (i.e. not the host name), it is a
different issue that needs to be diagnosed separately.
.
If you have tracing set to *=all=enabled in the server.xml
file, you will see the following traces preceding the
BBOO0221W/ADMC0015W messages:
Trace: 2003/06/11 14:08:40.713 01 t=9EA920 c=UNK key=S2
  FunctionName: com.ibm.ws.http.HttpTransport
  SourceId: com.ibm.ws.http.HttpTransport
  Category: ENTRY
  ExtendedMessage: initialize
Trace: 2003/06/11 14:09:20.718 01 t=9EA920 c=UNK key=S2
  FunctionName: com.ibm.ws.management.connector.soap.SOAPServer
  SourceId: com.ibm.ws.management.connector.soap.SOAPServer
  Category: EXIT
  ExtendedMessage: initialize - failed
.
This is an ENTRY trace for com.ibm.ws.http.HttpTransport
initialize method but no EXIT trace for that method along with
EXIT trace from com.ibm.ws.management.connector.soap.SOAPServer
indicating this method's initialize failed.
.
If the UnknownHostException was inidicated externally, it may
give customers a clearer indication that the TCP/IP setup is
not correct.
Local fix
Change TCP/IP setup so that the 'Node host name' is known to
TCP/IP via a getByName java call, such as reconfiguring using
the primary home address.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: UnkownHostException not surfaced        *
*                      during application controller           *
*                      region startup when node host name      *
*                      is incorrectly set up                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When customizing for the base app server and starting the
application controller region for the first time, it may
fail if the host name is not set up correctly in TCP/IP.
During app server controller region startup, a getByName is
done in com.ibm.ws.http.HttpTransport.initialize for the
Node host name.  When this fails, it is not reported as a
UnkownHostException.  Instead the exception percolates and
surfaces externally as message:
BBOO0221W ADMC0015W: SOAP connector failed to start with
exception: mvs02.myhost.com
where the "exception" shows as the host name, in this
example the host name is mvs02.myhost.com.  If there is a
different exception listed (i.e. not the host name), it is a
different issue that needs to be diagnosed separately.
Problem conclusion
An UnknownHostException is now reported upon failure in
in addition to the "SOAP connector failed to start with
exception: " error message.

APAR PQ75322 is associated with SERVICE LEVEL W501002 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
ž**** PE03/11/04 PTF IN ERROR. SEE APAR 
PQ80432  FOR DESCRIPTION
ž**** PE03/11/20 PTF IN ERROR. SEE APAR 
PQ81185  FOR DESCRIPTION
APAR information
APAR number PQ75322
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-06-16
Closed date 2003-10-22
Last modified date 2003-12-07

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ81380    UP03/10/28 P F310

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ75322.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 #: PQ75322
IBM Group: Software Group
Modified date: Dec 7, 2003