latest kernel-default 3.0.101-104.2 update and tomcat

SUSE Product Topics SLES Updates
1

Just updated my SLES 11 SP4 to kernel-default 3.0.101-104.2 and now tomcat 7.0.78 core dumps immediately on startup.

I reverted back to the previous kernel-default 3.0.101.100.1 and the same tomcat runs normally.

[CODE]#

A fatal error has been detected by the Java Runtime Environment:

SIGBUS (0x7) at pc=0x00007f1995d04ec3, pid=82488, tid=0x00007f19a79a2700

JRE version: (8.0_131-b11) (build )

Java VM: Java HotSpot™ 64-Bit Server VM (25.131-b11 mixed mode linux-amd64 compressed oops)

Problematic frame:

j java.lang.Object.()V+0

Core dump written. Default location: //core or core.82488

An error report file with more information is saved as:

/data/hs_err/hs_err-vw-tomcat-324937.log[/CODE]

I have attached hs_err-vw-tomcat-324937.log

I am not sure what else to include here that would assist the kernel or tomcat developers

2

I am guessing this is related to fixes in the kernel for the Stack Clash
issues that came out recently; the fix is known to cause issues with
Java-based applications, like Apache Tomcat.

Some links to the Stack Clash issue and fix follow:
https://www.suse.com/support/kb/doc/?id=7020973

Also see:
CVE-2017-1000364
CVE-2017-1000366

I do not know of a fix for the new Java-related issue, but I’m looking and
sending this thread on to SUSE so the impact can be better-measured. They
are already aware of the issue and may have a fix already, in which case
I’ll post back once I find it.

–
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

3

I have been informed by SUSE that this is a known issue with that kernel. A fix should be available shortly.