Fix (APAR): PK54781 Status: Fix Release: 6.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: PK54781 Byte size of APAR: 18250 Date: 2007-11-20 Abstract: A CommontNotFoundException would be thrown if the cancel button on the Middleware Application Scripts panel for unmanaged web applications was clicked. The button did not work as Description/symptom of problem: PK54781 resolves the following problem: ERROR DESCRIPTION: WebSPhere Extended Deployment Middleware agent throws the following exception com.ibm.websphere.management.cmdframework. CommandNotFoundException: Command or command group null is not found When executing the following steps: From the AdminConsole-> ALl Applications->Middleware aAplication Unmanaged panel, complete the following steps: 1. Select "Application Scripts" 2. Do not select any properties 3. Cancel the operation LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: This problem affects users of WebSphere Extended Deployment 6.1.0.0 who utilize the unmanaged web applications support in the product. PROBLEM DESCRIPTION: A CommontNotFoundException would be thrown if the cancel button on the Middleware Application Scripts panel for unmanaged web applications was clicked. The button did not work as expected. RECOMMENDATION: None The cancel button on the Middleware Application Scripts panel di d not work as expected and the Exception below would be thrown. com.ibm.websphere.management.cmdframework.CommandNotFoundExcepti on: Command or command group null is not found at com.ibm.ws.management.cmdframework.impl.CommandMetadataMgr.ge tCommandProvider(CommandMetadataMgr.java:1122) at com.ibm.ws.management.cmdframework.impl.CommandMgrImpl.create Command(CommandMgrImpl.java:91) at com.ibm.ws.console.middlewareapps.action.MiddlewareAppScripts Action.execute(MiddlewareAppScriptsAction.java:129) at org.apache.struts.action.RequestProcessor.processActionPerfor m(RequestProcessor.java:484) at org.apache.struts.action.RequestProcessor.process(RequestProc essor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet. java:1486) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.j ava:528) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servle tWrapper.java:995) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servle tWrapper.java:930) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(Web AppFilterChain.java:145) at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssi stence(WSCUrlFilter.java:792) at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringT askState(WSCUrlFilter.java:363) at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlF ilter.java:229) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter (FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(Web AppFilterChain.java:130) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(We bAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(W ebAppFilterManager.java:761) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(W ebAppFilterManager.java:673) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest( ServletWrapper.java:498) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleReques t(ServletWrapper.java:464) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.ja va:3276) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGrou p.java:267) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContain er.java:811) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebConta iner.java:1455) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannel Link.java:113) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDi scrimination(HttpInboundLink.java:454) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNe wInformation(HttpInboundLink.java:383) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.comp lete(HttpICLReadCallback.java:102) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadComp letedCallback.complete(SSLReadServiceContext.java:1815) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete( WorkQueueManager.java:556) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQu eueManager.java:606) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQu eueManager.java:979) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQ ueueManager..java:1064) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469) PROBLEM CONCLUSION: Middleware application scripts do not apply to unmanaged web applications so they are not supported. The fix removes the association between the Middleware Application Scripts panel and unmanaged web applications as well as addresses the issue with the cancel button. Directions to apply fix: Install Fix to: __ Application Server Nodes X_ Deployment Manager Nodes __ Both NOTE: The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files. Customers must be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. 1) Copy 6.1.0.0-WS-WXDOP-IFPK54781.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) On Unix or Linux system, ensure that the number of open file descriptors permitted is greater than 1024. (For example, set it to 8192 via ulimit -n 8192.) Otherwise, installation could fail. 4) Launch Update Installer 5) Enter the installation location of the WebSphere product you want to update. 6) Select the "Install maintenance package" operation. 7) Enter the file name of the maintenance package to install (6.1.0.0-WS-WXDOP-IFPK54781.pak file which was copied in the maintenance directory). The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory. 8) Install the maintenance package. 9) Restart WebSphere Directions to remove fix: NOTE: The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. NOTE: FIXES MUST BE REMOVED IN THE ORDER 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, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.1.0.0-WS-WXDOP-IFPK54781.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Additional Information: On Unix or Linux system, ensure that the number of open file descriptors permitted is greater than 1024. Otherwise, installation of the fix could fail.