PQ58881: THIN ADMIN CONSOLE DOES NOT DISPLAY TRACELOGGER CORRECTLY

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
These problems are related to thin admin client not logging:
1. Web Console Trace Service won't accept characters
   '/', '\', and '$' for tracing strings even if these are part
   of the trace logger's name.
.
2. Web Console only shows the last Group a Trace Logger
   was added to, not all the groups it is present in.
.
3. Web Console generates the wrong Trace String after
   selecting a Named Trace Logger and enabling it.
.
4. Trace logger should have an option to include the
   Trace Name in the trace output since all trace output is
   directed to one trace file, and multiple deployments
   (under different JNDI names) of the same class result in
   not being able to tell which deployment generated which
   message when output comes from the same class.
.
I have talked to developer and also sent him an email with
further details.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0 AEs users   *
*                 customizing trace strings in the Thin Admin. *
****************************************************************
* PROBLEM DESCRIPTION: The Thin Admin trace service does not   *
*                      handle custom trace strings properly    *
*                      in certain cases, causing the trace     *
*                      string to be constructed improperly     *
*                      or reject characters that should be     *
*                      valid.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Thin Admin does not accept certain characters
('$', '\', '/') as valid in a trace string.  Thus causing
an "The trace string is improperly formed" error when
the trace settings are attempted to be saved.
Also, If a user added a new trace component (through a
custom service) that began with a component that already
existed in the component list then the construction of
the trace string would not be correct.
Example:
com.ibm.ws.pmi.server.PmiRegistry is an existing trace
string. A user adds pmi.test.first to the trace tree
using a custom service. When the user selects
pmi.test.first and sets the level of tracing, the
contructed trace string comes out to be
com.ibm.ws.pmi.test.*=all=enabled.
Problem conclusion
The issue with certain characters being invalid has been
resolved. '/', '\', and '$' are now acceptable characters
in the trace settings. The issue with the custom trace
component being constructed improperly has also been resolve
to show the proper trace string when that trace component
is enabled for tracing. There were two other issues that
were originally reported when this APAR was openend that did
not get resolved due to design integrity and request for
a new feature.  They are the web console only shows
the last group a trace logger was added to, and the option
to includethe trace name in the trace output, respectively.
Temporary fix
This eFix fixes the trace service to allow a user to add a new
trace component to the existing trace service components and
have the trace string contructed properly.  Before the trace
string would be wrong if the custom trace component that was
added began with a component that already existed in the trace
component list.
Also, there were certain characters that the Thin Admin was not
accepting as valid when it should be.  (e.g.: '$', '/', '\').
Comments
APAR information
APAR number PQ58881
Reported component name WEBSPHERE AES N
Reported component ID 5630A2301
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-08
Closed date 2002-08-28
Last modified date 2002-09-19

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
THINADMI          

SRLS

Fix information
Fixed component name WEBSPHERE AES N
Fixed component ID 5630A2301

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58881
IBM Group: Software Group
Modified date: Sep 19, 2002