Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-26378

Fix hot-reload issues due to JAR files not being closed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.3
    • Component/s: Runtime

      Description

      We have various hot-reload issues whose root cause is JAR files not being closed during hot-reload.

      If there is an InputStream from a JAR file resource that is not closed correctly (leaked), the JAR file stays open, and in turn the sun.net.www.protocol.jar JarFileFactory caches used by sun.net.www.protocol.jar.JarURLConnection are not being released. This causes subsequent references to a new version of the JAR file at the same location to not be read, because the old one is still in cache.

      The solution is to properly close the ClassLoader from which these JAR file resources are read.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day
                  1d

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.