APAR status
Closed as program error.
Error description
In ND environment could not set-up Runtime
"Diagnostic Trace Service" for following servers (JVMs)with
different trace file names.
.
dmgr,nodeagnet and server1
.
All 3 servers are updated at same time.
For example if we specify following value
${SERVER_LOG_ROOT}/server1_trace.log for server1
( Runtime Diagnostic Trace Service) all other servers
(nodeagnet and dmgr) are reflecting same value.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Network Deployment *
* users using Administration Console to get *
* run time trace files for different servers *
* such as dmgr, nodeagent and server1. *
****************************************************************
* PROBLEM DESCRIPTION: In ND environment could not set up *
* run time "Diagnostic Trace Service" *
* for the following servers with *
* different trace file names. *
* *
* dmgr,nodeagnet and server1 *
* *
* All 3 servers are updated at the same *
* time. For example if we specify the *
* following value ${SERVER_LOG_ROOT}/ *
* server1_trace.log for server1, all *
* other servers (nodeagent and dmgr) *
* are reflecting same value. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
WebSphere uses the preferences.xml to save the run time trace
file name for different user. In the preferences.xml,
there is only one entry for the run time trace which is
shared by all servers.
Problem conclusion
To separate the run time trace for different servers, added
server name as part of the run time trace file path when
saving it to the preferences.xml. Now there are separate
sections corresponding to difference servers and the trace
file name is part of the separated section.
Temporary fix
PQ74390_Test.jar
Comments
APAR information |
APAR number |
PQ74390 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-05-21 |
Closed date |
2004-02-10 |
Last modified date |
2004-02-10 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|