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)
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)
- duplicates
-
JDK-6302804 Hotspot VM dies ungraceful death when C heap is exhausted in various places.
- Closed
- relates to
-
JDK-6362318 (thread) uncaught exception handler can be silenced by OutOfMemoryError
- Open
-
JDK-6694099 Hotspot vm_exit_out_of_memory should dump core
- Closed
-
JDK-4343963 hotspot dumps core on minor vm exits (e.g. mistyped library name)
- Closed