Legacy Knowledge Base
Published Sep. 10, 2025

Restart required after every Jar Deployment

Written By

Ankit Gupta

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

When the jar is deployed, it is not reflected until and unless the server is restarted

Environment

  • Liferay DXP 7.0

Resolution

Sometimes, the jar is deployed and is not reflecting on the portal until and unless the server is restarted. This might cause the issue as the production environment can't be restarted after each and every deployment. In order to check what is causing the issue, please check if the below property is added in portal-ext.properties or not.

direct.servlet.context.reload=false

By default, the above-mentioned property is enabled i.e. set to "true". It is responsible to refresh the servlet associated with a JSP; when the JSP has been modified. 

Therefore, by removing the property direct.servlet.context.reload=false or setting direct.servlet.context.reload=true in portal-ext.properties will resolve the issue, i.e. after each deployment of jar server restart is not required.

Please Note: Once you remove or set the above property to true in portal-ext.properties. You need to restart the server in order to bring the changes.

 

Did this article resolve your issue ?

Legacy Knowledge Base