Changing a Web or EJB project results in an application to be restarted with option Never publish automatically

When the publishing option Never publish automatically is enabled with the publishing setting for WebSphere Application Server Run server with resources within the workspace enabled, the WAR can still be restarted even without a publishing taking place. This problem is caused by automatic class reloading in WebSphere Application Server.

For example, if a new method is added to the servlet, the WAR will be restarted automatically even though the server is in a Republish state.

To workaround this known limitation:

  1. Restart the server in debug mode. While in debug mode, the changes will take place, but the WAR will not be restarted since the changes are picked up as part of the hot code replace.
  2. Disable WebSphere Application Server class reloading by specifying a WebSphere Extension Deployment Descriptor.
    • Select web project > Java EE > Generate WebSphere Extensions Deployment Descriptor.
    • The generated ibm-web-ext.xml file will be in the web project's WEB-INF.
    • Open ibm-web-ext.xml and go to the Design tab.
    • Uncheck Enable Reloading.
    • Republish your application
  3. Open the server editor and select Run server with resources on Server form the Publishing settings for WebSphere Application Server section.
Icon that indicates the type of topic Reference topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: rchangeprojectneverpublishautomatically.html