Java threads produce OutOfMemoryError with 4.4.0-22 kernel

[Mike O'Rourke]

Hi all.

I am running Ubuntu 16.04 (through regular updates and upgrades) on an HP DL380 with dual hex-core Xeon 3.47GHz cpus and 96GB RAM.

I upgraded this system a week ago, and started getting Java OutOfMemoryErrors (unable to create new native thread) from Wowza Streaming Engine. I tried older versions of Java (7 and 6 oracle versions) and they improved it, but did not fix it.

When I stopped the Wowza service from the command line, the service command would hang until I killed the java process.

I booted my system into the 3.16.0-41 kernel that was still there, and everything works as it should (no more OutOfMemoryErrors). I have not tried the 3.16 kernel with Java 8 OpenJDK; it is still running on Java 7.

Did something change drastically with the thread modules between the 3.16.0 kernel and the 4.4.0 kernel?

Wowza starts Java with the -Xmx10000M option.

One of the log entries for this error is:

WARN server comment 2016-05-20 23:55:21 - - - --5405.152 - - - - - - - - Unexpected exception.: 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 org.apache.mina.util.NewThreadExecutor.execute(NewThreadExecutor.java:34)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(SocketIoProcessor.java:104)|at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(SocketIoProcessor.java:83)|

Thanks.
Mike.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 21 16:44 seq
 crw-rw---- 1 root audio 116, 33 May 21 16:44 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/media--vg-swap_1
InstallationDate: Installed on 2015-04-08 (411 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2)
MachineType: HP ProLiant DL380 G7
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/hostname--vg-root ro
ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-41-generic N/A
 linux-backports-modules-3.16.0-41-generic N/A
 linux-firmware 1.157
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 3.16.0-41-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-05-14 (9 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 07/02/2013
dmi.bios.vendor: HP
dmi.bios.version: P67
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP67:bd07/02/2013:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL380 G7
dmi.sys.vendor: HP

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1584471/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1584471

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

apport information

[Mike O'Rourke (morourke)]

Would it be more helpful to run apport-collect with the 4.4.0-22 kernel running after the OutOfMemoryError has occurred?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety

[Mike O'Rourke (morourke)]

kernel-bug-exists-upstream

[Mike O'Rourke (morourke)]

I have an apport-collect file saved that was run against the 4.6 kernel. I can upload it if you like; apport would not do anything with it since it was not a mainstream kernel.

[Mike O'Rourke (morourke)]

tags: added: kernel-bug-exists-upstream