Problem

I have a WebSphere Application Server Network Deployment version 8.5.5.12 application server. Five Enterprise Applications are running on this application server. I have two enterprise applications which are frequently being updated by deploying *.jsp and *.class files.

For deployments of *.class I was using the rollout feature of WebSphere Application Server. But to deploy the *.jsp files I was using the update option to update the EAR and it was working smoothly, the name of this EAR was payEAR.ear. I deployed the *.jsp files many times during working hours and the sessions of the users never become expired.

A few days ago I deployed the newly created payEAR.ear application and after that, I faced the issue that when I was updating this payEAR.ear it restarted itself automatically. Due to restarting of the payEAR.ear session of all logged-in users on this application becomes expired.

I was facing the issue of restarting only for payEAR.ear, other applications were not restarting while updating *.jsp files.

Reason

After enabling the trace logs and diagnosing the logs it was found that the application.xml file was not included in the newly created payEAR.ear. Due to this WebSphere Application Server created a new file named application_merged.xml.

Solution

I have created the payEAR.ear again including the application.xml file. Uninstalled the running payEAR.ear and installed the newly created payEAR.ear through dmgr console. It resolved the problem of restarting the application and session expiry of the logged-in users.

Note: WebSphere Application Server Network Deployment version 8.5.5.12 running on HP-UX 11.31.

Last Updated: September 15, 2018