JVM dies with little/misleading problem information during excessive creation of ORB threads

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P2
    • 5.0u14
    • Affects Version/s: 5.0u13
    • Component/s: hotspot
    • None
    • sparc
    • solaris_10

      If thousands of threads are created for ORB connections (using the unrecommended com.sun.jndi.cosnaming.CNCtx initial context) the JVM frequently dies with no, little or misleading information about the cause.
      With Java 5 there is no hint about ressource consumption. Java 6 throws an OutOfMemoryError although Java heap is not exhausted and virtual process size is less than 1 GB. The JVM in most cases crashes with SIGBUS or SIGSEGV but without either a core or a hs_err_* file. (The problem is even more hidden if the JVM is embedded into S1AS 8.2)

            Assignee:
            Coleen Phillimore
            Reporter:
            Andreas Mueller (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: