Details

      Description

      Currently, the app server provides generic upgrade logging for the upgrade process. However, if the upgrade fails, it does not provide detail as to what in the process failed. It would be very convenient if more logging could be provided. For example, if the upgrade hangs in a specific process for for an extended period of time or receives a message such as:

      "The database contains changes from a previous upgrade attempt that failed."

      It would be very helpful if there was some type of logging that could pin point what exactly are those changes or the reasoning for it.

        Attachments

          Activity

            People

            • Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              ira.chui Ira Chui
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package