-
Bug
-
Resolution: Won't Fix
-
P2
-
None
-
7u80
One of our customers started to see start-up failures of their application server caused by out of memory errors on native (non-Java) level. In the server logs they see many messages like this one:
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949)
...
The error started to appear after they upgraded from Java 7u79 32 bit to Java 7u80 32 bit. The platform is Windows Server 2012 R2.
During the investigation it was discovered that the error is caused by zlib 1.2.3 => 1.2.8 library update. Replacing zip.dll in 7u80 with its version from 7u79 fixes the problem. So technically this issue is a regression of the following change:
https://bugs.openjdk.java.net/browse/JDK-8044725
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:949)
...
The error started to appear after they upgraded from Java 7u79 32 bit to Java 7u80 32 bit. The platform is Windows Server 2012 R2.
During the investigation it was discovered that the error is caused by zlib 1.2.3 => 1.2.8 library update. Replacing zip.dll in 7u80 with its version from 7u79 fixes the problem. So technically this issue is a regression of the following change:
https://bugs.openjdk.java.net/browse/JDK-8044725
- duplicates
-
JDK-8151848 Higher native memory usage caused by upgrade to zlib 1.2.8
-
- Closed
-
- relates to
-
JDK-8151848 Higher native memory usage caused by upgrade to zlib 1.2.8
-
- Closed
-
-
JDK-8044725 Bug in zlib 1.2.5 prevents inflation of some gzipped files (zlib 1.2.8 port)
-
- Closed
-