Uploaded image for project: 'Magnolia License'
  1. Magnolia License
  2. MGNLLIC-47

CLONE - Memory-Leak/Classloader errors because BouncyCastleProvider is registrated for all WARs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 1.3.3, 1.4.1
    • None
    • None
    • None
    • all os
    • Yes
    • 5.1.1

      The registration of BouncyCastleProvider in info.magnolia.license.KeyGenerator and info.magnolia.license.LicenseProcessor with "Security.addProvider(new BouncyCastleProvider());" is changing JVM-settings and therefore all WARs in an Appserver are seeing this registration and classes of BouncyCastle.
      If another WAR wants to use another version of BouncyCastle this can lead to Classloader issues. The Provider is also not removed on WAR-undeploy -> Memory-Leak.

      In a WAR "Security.addProvider()" should be never used, because of all side-effects for other WARs ->

        Acceptance criteria

              mdivilek Milan Divilek
              mgri Markus Grieder
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD