Connections 3.0.1 Fix Pack 1 installation issue

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
 [exec]   [wsadmin]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [exec]   [wsadmin]      at sun.reflect.NativeMethodAccessorImpl.invoke(
 [exec]   [wsadmin]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 [exec]   [wsadmin]      at java.lang.reflect.Method.invoke(
 [exec]   [wsadmin]      at
 [exec]   [wsadmin]      at
 [exec]   [wsadmin]      at
 [exec]   [wsadmin]      at
 [exec]   [wsadmin]      at
 [exec]   [wsadmin] EJBDeploy level: @build@
 [exec]   [wsadmin] ADMA5008E: The EJBDeploy program failed on file /tmp/app7307803356142343542.ear. Exception: Error executing EJBDeploy
 [exec]   [wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: 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: 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.

2 Responses to Connections 3.0.1 Fix Pack 1 installation issue

  1. Jaakko says:

    I’ve had this happen several times now in different environments when installing Connections 3.0.1 Fix Pack 1 and/or one of the Cumulative Refreshes that have been released after fp1. It may not just be News, any other app can fail updating too.

    For what it’s worth, rolling back the (partially failed) 3.0.1 fix pack 1 install with IBM Installation Manager, deleting the ejbdeploy configuration directory and reinstalling the update has always worked for me. No need to revert to backups or a snapshot unless you want to. And if this problem occurs with interim fixes that are installed with Connections Update Installer, you can of course just try again with the ejbdeploy configuration wiped.

    • Hi Jaakko,
      Thanks for the info, I was guessing/hoping that uninstalling using Installation Manager would do the trick but it’s great to know that is the case, thankfully I’ve not see the issue again (yet!).
      Thanks again.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

%d bloggers like this: