Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-1297

MemoryUtil should not fail on Google App Engine with NoClassDefFoundError

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 7.0.0.Beta2
    • 6.4.0.Final, 6.5.0.CR1, 7.0.0.Beta1
    • core engine
    • None
    • NEW
    • NEW

    Description

      MemoryUtil throws this exception on Google App Engine:

      java.lang.NoClassDefFoundError: Could not initialize class
com.google.apphosting.runtime.security.shared.stub.java.lang.management.ManagementFactory
at org.drools.core.util.MemoryUtil.<clinit>(MemoryUtil.java:33)

      because the PermGen check goes the wrong way on GAE.

      In the MemoryUtil code on line 33, we need something like:

      if (... || isGAE()) {
...
}

public boolean isGAE() {
   String p = System.getProperty("com.google.appengine.runtime.environment");
   return p != null && !p.equals("");
}

      On GAE, p is "Development". => act same like isAndroid()
      On GCE (= plain old OpenJDK), p is null. => act normally
      On plain Fedora with OpenJDK 8, p is null. => act normally

      Attachments

        Issue Links

          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RHBRMS-2599 MemoryUtil should not fail on Google App Engine with NoClassDefFoundError

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHBRMS-2600 MemoryUtil should not fail on Google App Engine with NoClassDefFoundError

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mfusco@redhat.com Mario Fusco
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: