Fix (APAR): JR28885 Status: Fix Release: 6.1.0.1,6.1,6.0.2.4 Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 26739 Date: 2008-07-18 Abstract: The problem occurs in the panel for Business processes where we select the maximum rows in the preferences field to 1 and to go to next page we need to click on next button. And Wh Description/symptom of problem: JR28885 resolves the following problem: ERROR DESCRIPTION: In the panel for starting and stopping business processes the second page could not be displayed when the list of entries is larger than the maximum rows in the preferences. The following exception is seen: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: Invalid path /ProcessComponentCollection was requested at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError (WebAppD ispatcherContext.java:603) at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServ letRespo nse.java:868) at org.apache.struts.action.RequestProcessor.processMapping(Request Processo r.java:684) at org.apache.struts.action.RequestProcessor.process(RequestProcess or.java: 242) at org.apache.struts.action.ActionServlet.process(ActionServlet.jav a:1486) LOCAL FIX: Do not use the maximum row feature or choose a larger number than number of entries. PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2 and 6.1.0 users. PROBLEM DESCRIPTION: The problem occurs in the panel for Business processes where we select the maximum rows in the preferences field to 1 and to go to next page we need to click on next button. And When we click on next button we get a message which states that page cannot be displayed. RECOMMENDATION: None Summary of the problem is customer was not able to go to next page after clicking the next button and after setting the maximum preferences field to 1 for business processes. PROBLEM CONCLUSION: Admin console cosmetics issue, when trying to go to next page for the Business processes.Admin console cosmetics issue, when trying to go to next page on clicking the next button we see a page not found exception for the Business processes. The end user impact is not high since there is a workaround available. workaround is instead of selecting maximum rows to be 1 select 20 rows at a time. 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) open a command prompt and change to directory WPS_HOME/profiles/wpsprofile/bin and run iscdeploy.bat -restore 5) 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: