June 7, 2012 2 Comments
During the installation of fix pack 1 for IBM Connections 3.0.1 I had an issue with the upgrade of the News application.
One of the (many) good things about Connections is that it writes a separate insallation/upgrade log for each application which really helps narrow down the search for the cause of installation/upgrade issues, so in this instance I opened the newsUpdate.log (located in /opt/IBM/LotusConnections/logs) and found the following:
[exec] [wsadmin] An unexpected exception was thrown. Halting execution. [exec] [wsadmin] Shutting down workbench. [exec] [wsadmin] Error executing deployment: java.lang.IllegalStateException. Error is Platform not running. [exec] [wsadmin] java.lang.IllegalStateException: Platform not running [exec] [wsadmin] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374) [exec] [wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [exec] [wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) [exec] [wsadmin] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) [exec] [wsadmin] at java.lang.reflect.Method.invoke(Method.java:611) [exec] [wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:494) [exec] [wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:114) [exec] [wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:107) [exec] [wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:348) [exec] [wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:310) [exec] [wsadmin] EJBDeploy level: @build@ [exec] [wsadmin] ADMA5008E: The EJBDeploy program failed on file /tmp/app7307803356142343542.ear. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy [exec] [wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy [exec] [wsadmin] ADMA5011I: The cleanup of the temp directory for application News is complete. [exec] [wsadmin] ADMA5069E: The installation of application News failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session. [exec] [wsadmin] WASX7017E: Exception received while running file "/opt/IBM/LotusConnections/ConfigEngine/config/work/was/EarUpdate.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for News failed: see previous messages for details.
After some investigation I eventually found a technote ( EJB Deploy Error: java.lang.IllegalStateException: Unable to acquire application service ), which whilst not directly relating to Connections, looked as though it could help resolve the issue.
The technote says “The problem may occur when Enterprise JavaBeans Deploy is updated as part of a Fix Pack install and there are files in the EJB Deploy configuration directory from the previous EJB Deploy install.” and the recommended fix is to delete the contents of the EJB Deploy Configuration directory.
As I was fortunate enough to be doing the install on virtual machines I reverted to the snapshots taken just prior to starting the upgrade, then removed the contents of the EJB Deploy Confiuration directory (/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/ejbdeploy/configuration) and re-ran the installation of fix pack 1, which this time completed successfully.