PQ50243: IMPROPER HOST NAME, WHEN STARTED HTTP SERVER RECEIVED GETHOSTBYNAME ERROR MSG IN NETSCAPE LOG FILE, UNABLE TO SERVE ANY WAS REQ.


APAR

APAR status
Closed as program error.

Error description
The customer was configuring OSE Remote in a multi-node cloned
environment.  Per the OSE Remote configuration instructions they
manually edited the queues.properties file on the HTTP server
machine and added the required entries, including the ose.srvgrp
ibmoselink.clonex.host entries. They mistyped one of these host
entries so that it was unable to be resolved throught DNS.  When
they attempted to start their http server they received gethostb
error messages in the netscape log file, and they were unable to
server any WebSphere requests, even to the clones whos
host names were resolvable.
The customer was able to find the mistyped host name and correct
it, and was able to get their configuration up and running.  How
they feel that the WebSphere plug-in should have been able to ig
the incorrect entry, and route requests to the properly configur
The problem is recreatable with IBM HTTP Server, rather than the
Netscape server the customer is using.  In this case, the HTTP S
failed to completely start.  As with Netscape, correcting the in
hostname in the queues.properties file resolved the problem.
Please create a defect for servicability since the product did n
ot provide enough information for the customer to figure out on
their own what was causing the problem. WASWLMK, WASPERFK
SVC
Local fix
Work around was to correct improper hostname so WebSphere would
serve requests again.
Problem summary
The plugin is working as designed.  In order for requests to
be serviced properly the information in the properties files
has to be correct.  Valid hostnames are critical to
the overall functioning of the plugin in an OSE remote
configuration.  If we cannot reach the defined machine, we
cannot
service requests.  So, an invalid hostname is a considered a
critical
error.  While the plugin does attempt to validate the info
in the
properties files  (like resolving the host names defined in
the
queues.properties file), it is ultimately up to the user to
make sure
that the information contained in these files are correct.
Problem conclusion
Added new error message to give users more information when
invalid hostname is supplied.
Temporary fix
Comments
APAR information
APAR numberPQ50243
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-07-02
Closed date2001-08-23
Last modified date2001-09-20

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:

PQ52629

Modules/Macros
PLUGIN
APAR is sysrouted TO one or more of the following:PQ52629Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ50243
IBM Group: Software Group
Modified date: 2001-09-20