Fix (APAR):  JR27308

Status:  Fix

Release:  6.0.1.6,6.0.1.5,6.0.1.4

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR27308

Byte size of APAR:  66114

Date: 2007-09-13

Abstract:  If a project is built using servicedeploy and then deployed to the server, line numbers are not shown in the stack trace

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

ERROR DESCRIPTION:                                              
Customer code being compiled by serviceDeploy does not include  
basic Java debug info, whereas code exported in an EAR manually 
from WID includes debug (by default, it is configurable in WID).
                                                                
When Java code has no debug info, stack traces in WAS logs do   
not include source file & line number info. This creates a      
serviceability problem where customer cannot easily locate the  
specific code corresponding to stack traces.                    

LOCAL FIX:                                                      
No local fix                                                    

PROBLEM SUMMARY

USERS AFFECTED:
Users of WebSphere Process Server 6.0.1.4
or later;
Users of WebSphere Process Server 6.0.2.0
or later;

PROBLEM DESCRIPTION:
If a project is built using
servicedeploy and then deployed to
the server, line numbers are not
shown in the stack trace

RECOMMENDATION:
None

Problem can be fixed by adding a new parameter "-javaDebug" to
servicedeploy to enable line number to be shown with compile
project

PROBLEM CONCLUSION:                                             
Apply iFix to resolve the stated problem.                       


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also 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

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. 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

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: