APAR status |
Closed as program error.
| Error description
WAS3.5x and WAS302.x. Basically if client can resolve an nslook
up then remote adminclient should connect w/o issuing a naming
resolve error message. If client's etc/host's server hostname
entry does not match the server's etc/host's server hostname
entry then throw a valid error message like hostname not found
or hostname does not match server hostname so that cust can
resolve these issues w/o calling support and running socket leve
l traces to determine that was the problem. Local fix
Make sure hosts files on both the client and server match
the dns hostname for the machine. Also connecting to the client
using the adminclient.bat or .sh script w/the correct spelling
of the hostname (case correct). This is only a problem on
unix o/s. Problem summary
During the initial context lookup - in the RepositoryClient
constructor, if the name lookup fails, there feedback to the
user is limited to system trace.
.
The request is to output some more descriptive messages to
system.err to inform the user that a potential problem exists
with the admin server hostname which was supplied on the
command line. Problem conclusion
An audit message will be added to the RepositoryClient.java
code detailing NamingException potential from a hostname
misspelling or mismatched case.
.
In researching this defect - it is apparent from a WindowsNT
admin client - without enabling product tracing and/or verbose
output (-v command line option), NO OUTPUT is directed to
stdout or stderr. This is because the adminclient.bat file
in version 3.5.x, invokes the javaw executable. This jvm
is special for Windows environments and does not include
a command shell environment. This precludes the output
of text to stdout/stderr.
.
Code changed in: com/ibm/ejs/sm/client/RepositoryClient.java Temporary fixComments
APAR information | APAR number | PQ47453 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-03-30 | Closed date | 2001-05-23 | Last modified date | 2001-05-23 |
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:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|