Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-31032

When restarting Tomcat, hot deployment overwrites the config data of new portlets in database

    Details

      Description

      I have 2 portal instances per one Liferay installation, using shared database.
      I hot deploy my new portlet. The portlet will be available (active) for all instances by the default. Now I go to "Control Panel" --> "Plugins Configuration" of the 2nd portal instance and find & set inactive my portlet. Then I restart Tomcat and check again the status of my portlet at the 2nd portal instance. The result is active (yes) for my portlet. In summary, the status of my portlet is changed from active (at deployment) to inactive (set by Plugins Configuration GUI) to active (Tomcat restarted).

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                6 years, 36 weeks, 1 day ago

                Packages

                Version Package
                6.2.0 CE M4