PM39125: Cumulative fixes for RAS and HPEL components

Fixes are available

APAR status

Closed as program error.

Error description

Multiple unexpected behaviors in the RAS and HPEL components.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using the logging and trace          *
*                  functionalities.                            *
****************************************************************
* PROBLEM DESCRIPTION: This is a cumulative APAR that          *
*                      addresses a few issues.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem description of each issue is as follows:
(702469) A RasException that occurs as a result of an invalid
action by the user in the administrative console appears in
the SystemOut.log but does not appear to the user from the
administrative console.
For example:
go to the "Logging and tracing > server1 > Diagnostic trace
service > "Runtime" tab, select File and set the FileName to a
file in a directory that does not have write permissions, and
press ok.  This results in no error being displayed.  Returning
to this panel, the changes have been reverted back to the
original values without an explanation on why the specified
values did not go into effect.
The following exception appears in SystemOut.log:
[4/10/11 15:18:21:186 UTC] 00000017
ManagerAdmin  E   TRAS0008E: Failed to open trace log file
/was_logs/trace.log com.ibm.ejs.ras.RasException: Ras
does not have necessary permission to write file trace.log to
directory /was_logs/trace.log
at
com.ibm.ejs.ras.RasHelper.validateFileName(RasHelper.java:993)
at
com.ibm.ejs.ras.RasHelper.generateOutputFileName(RasHelper.java:
933)
at
com.ibm.ejs.ras.ManagerAdmin.addServerTraceFileListener(ManagerA
dmin.java:1293
)
at
com.ibm.ejs.ras.ManagerAdmin.setTraceOutputToFile(ManagerAdmin.j
ava:967)
at
com.ibm.ws.runtime.mbean.TraceServiceMBean.setTraceOutputToFile(
TraceServiceMBean.java:352)
(702533) HPEL binary files may be deleted as part of the
retention policy, but its parent directorie(s) that is empty
as a result still exist.
(703214) From the runtime tab (for either Basic or HPEL mode)
of the change log details level panel, enabling sensitive log
filtering will cause all the internal trace guards to be
visible in the trace spec.
For example:
Go to Troubleshooting -> Logs and trace -> (server) -> Change
log detail levels, where the default tracespec is *=INFO (or
any other value). Select the checkbox for "Disable logging and
tracing of potentially sensitive data.".  Returning to this
panel will show the tracespec string as modified with a very
long string because the traceguard string has been added.
(708117) HPEL Internal trace does not function on the iSeries
platform.  When the JVM custom property
com.ibm.ws.logging.hpel.debug=true, the tracespec is
configured to "*=info: com.ibm.hpel.debug=all", and in HPEL
mode, internal HPEL logging is expected to create logs in the
default temp directory. HPEL Internal trace files have the
name of hpelDebugLogger.<PID>.<instance>.log
(709181) hpel reader and writer classes and packages are
missing in the javadoc available in the infocenter.
(710848) From the administrative console, it is possible in an
IBM-based JVM environment to generate heapdumps and system
cores.  When attempting to generate heap dumps or system cores
for a non-IBM JVM environment where this functionality is not
available, the resulting error message is misleading.  The
resulting error message is
"Server <server_name> is stopped or not responding.  Heap dump
cannot be performed on a stopped server."
(711124) In HPEL mode, when the LogViewer (Troubleshooting->
Logs and Trace -> <server> -> view HPEL logs and trace) in the
administrative console is first loaded, the currently selected
log is not highlighted.
(713512) Attempting to view an FFDC incident file from the
HPEL LogViewer (Troubleshooting-> Logs and Trace -> <server>
-> view HPEL logs and trace) of the administrative console
results in a FileNotFoundException exception occurs.
For example, clicking on an entry such as:
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
Inicdent emitted on
C:\WebSphere\profiles\AppSrv01\logs\ffd
c\server1_1ce7502_11.10.14_11.11.20.133
2070065135304803507.txt 123 456
will result in "An error occurred during fetch of message
detail. Please ensure that you are connected to the network
and you can access the server.  Review server logs for further
analysis."
The following can be seen in the output logs:
E
com.ibm.ws.webcontainer.servlet.ServletWrapper service
SRVE0014E: Uncaught service() exception root cause FFDC File
View Servlet: java.io.FileNotFoundException:
C:WebSphereprofilesAppSrv01logsffdcserver1_1ce7502_11.10.14_11.1
1.20.1332070065135304803507.txt (The filename, directory name,
or volume label syntax is incorrect.)
at
java.io.FileInputStream.open(Native Method)
at
java.io.FileInputStream.<init>(FileInputStream.java:123)
at
java.io.FileInputStream.<init>(FileInputStream.java:83)
at
java.io.FileReader.<init>(FileReader.java:52)
at
com.ibm.ws.console.probdetermination.hpellogview.FFDCIncidentFil
eServlet.verifyFile(FFDCIncidentFileServlet.java:255)
at
com.ibm.ws.console.probdetermination.hpellogview.FFDCIncidentFil
eServlet.readFFDCFile(FFDCIncidentFileServlet.java:231)
at
com.ibm.ws.console.probdetermination.hpellogview.FFDCIncidentFil
eServlet.service(FFDCIncidentFileServlet.java:204)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

Problem conclusion

(702469) This has been fixed so that if an invalid action that
results in a RasException will be surface to the user in the
admin console.

(702533) When HPEL binary files are deleted under the
retention policy, its parent directorie(s) will be removed
with it.

(703214) This has been corrected so that once the sensitive
log filtering has been enabled, the user will continue to see
the user-specified tracespec from the administrative console.

(708117) The fix to this will now allow HPEL Internal trace,
when enabled, to be written to the temp directory.

(709181) The hpel reader and writer classes/packages such as
com.ibm.websphere.logging.hpel.reader and
com.ibm.websphere.logging.hpel.writer now appear in the javadoc

(710848) This has been addressed such that if a user tried to
invoke an unsupported systemcore or heap dump request, the
resulting error reported reflects the root problem.  Eg:
a heap dump request on a non-IBM JVM would result in something
similar to:

systemdump.fail.reason= The heap dump request to the server
<servername> failed because of the following reason:
<com.ibm.websphere.management.exception.HeapDumpNotSupportedExce
ption>

(711124) The currently selected log is now highlighted when
the HPEL LogViewer is first loaded in the administrative
console.

(713512) Clicking on the link to the FFDC incident file from
the administrative console will now result in a display of the
file contents


The fix for this APAR is currently targeted for inclusion in
fix pack 8.0.0.2.  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
PM39125
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-12
Closed date
2011-10-19
Last modified date
2011-10-19

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R800 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM39125: Cumulative fixes for RAS and HPEL components

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

R800 PSY

Document Information

Share your feedback

Need support?