Fix (APAR):  JR31976

Status:  Fix

Release:  6.1.2.2,6.1.0.3,6.1.0.2,6.1.0.1

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR31976

Byte size of APAR:  20638

Date: 2009-05-01

Abstract:  Artifact Loader on WPS v6.1.0.x and v6.1.2.x prints many detailed messages intended for problem determination in SystemOut.log as informational messages. These messages might not p

Description/symptom of problem:  
JR31976 resolves the following problem:

ERROR DESCRIPTION:                                              
WPS 6.1.2.2 on WAS 6.1.0.19 prints out a lot of the following   
messages to the SystemOut.log during startup:                   
[2/5/09 7:35:10:709 EET] 00000049 ArtifactLoade I   request the 
fileURI:                                                        
jar%3Afile%3A/ibm/WebSphere/ProcServer612/profiles/wps01/install
edApps/i                                                        
ntpwpscell/HAVALEv16App.ear/HAVALEv16.jar%21/xsd-includes/http.H
AVALEv6.                                                        
xsd                                                             

LOCAL FIX:                                                      
As workaround can be set the trace level of the server to       
ArtifactLoader=warning                                          

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.1.0.x and
v6.1.2.x users.

PROBLEM DESCRIPTION:
Artifact Loader on WPS v6.1.0.x and
v6.1.2.x prints many detailed messages
intended for problem determination in
SystemOut.log as informational
messages. These messages might not
provide values to customers and makes
other messages harder to find.

RECOMMENDATION:
None

Certain messages in Artifact Loader runtime are using INFO
logging level, which causes the logs to be printed to
SystemOut.log by default. These messages should be changed to
at least FINE logging level, because their original purpose is
for problem determination.

PROBLEM CONCLUSION:                                             
Artifact Loader now prints messages intended for problem        
determination with at least FINE logging level, so these        
messages do not appear in SystemOut.log. These messages will    
be printed to trace.log only if tracing is enabled for          
Artifact Loader. Applying this interim fix will resolve         
this issue.                                                     


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: