PK95714: CONFIGURATION SETTINGS IN DIAGNOSTIC TRACE SERVICE PANEL LOST AFTER SWITCHING FROM RUNTIME TAB TO CONFIGURATION TAB

Fixes are available

APAR status

Closed as program error.

Error description

Configuration settings made and then saved on the Runtime tab
in the Diagnostic Trace Service panel are lost once you select
the Configuration Tab.




1. In the Diagnostic Trace Service panel, configure it so that
   you are tracing to memory, and enable the log.

2. Save these settings.

3. Now click on the Runtime tab and click back to the
   Configuration tab.  You will find that the 'Enable log'
   setting has been lost.  It gets reset when you click another
   server and come back to this one.  So once the settings are
   set via the configuration tab, if I select the Runtime tab,
   and then the configuration tab again, the 'Enable Log'
   setting is no longer checked, but tracing to memory is still
   selected.

4. Click back to the Runtime tab, select the Memory Buffer
   option, enter a max size and a dump file name, click OK.
   After selecting the 'Runtime tab', the values are lost.

5. Finally, in the Diagnostic Trace Service panel for a
   different server, click its Runtime tab and look at the
   values for its Memory Buffer, you will see that the
   settings are the ones you just entered for the previous
   server.

Local fix

```
No local fix or workaround available.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0 Administrative Console *
****************************************************************
* PROBLEM DESCRIPTION: The displayed values on the runtime     *
*                      tab are incorrect. One of the fields    *
*                      is not fetched correctly & other is     *
*                      set to different value                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The value from the MBean was not fetched correctly. A different
field was fetched causing the incorrect value. Also another
field was not set properly to be rendered by the JavaServer
Page (JSP).

Problem conclusion

The code was changed to fetch the values correctly from the
MBean. The code was also changed to set the value in the form
which is expected by the JSP.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.31 and 7.0.0.9.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK95714
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-09
Closed date
2009-10-22
Last modified date
2009-11-20

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

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK95714: CONFIGURATION SETTINGS IN DIAGNOSTIC TRACE SERVICE PANEL LOST AFTER SWITCHING FROM RUNTIME TAB TO CONFIGURATION TAB

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?