Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6F481200CBB for ; Tue, 4 Jul 2017 10:47:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6DE54160BEF; Tue, 4 Jul 2017 08:47:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B3E10160BE1 for ; Tue, 4 Jul 2017 10:47:13 +0200 (CEST) Received: (qmail 18584 invoked by uid 500); 4 Jul 2017 08:47:12 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 18565 invoked by uid 99); 4 Jul 2017 08:47:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jul 2017 08:47:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 66668C24A5 for ; Tue, 4 Jul 2017 08:47:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id MDREFQbOpZ8j for ; Tue, 4 Jul 2017 08:47:08 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id ECA6560D72 for ; Tue, 4 Jul 2017 08:47:07 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B2E07E0DF9 for ; Tue, 4 Jul 2017 08:47:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5B7362461C for ; Tue, 4 Jul 2017 08:47:01 +0000 (UTC) Date: Tue, 4 Jul 2017 08:47:01 +0000 (UTC) From: "Mark Thomas (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DAEMON-364) Latest RHEL kernel update crashes jsvc MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 04 Jul 2017 08:47:14 -0000 [ https://issues.apache.org/jira/browse/DAEMON-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Thomas resolved DAEMON-364. -------------------------------- Resolution: Duplicate > Latest RHEL kernel update crashes jsvc > -------------------------------------- > > Key: DAEMON-364 > URL: https://issues.apache.org/jira/browse/DAEMON-364 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc > Affects Versions: 1.0.15 > Reporter: Peter Walsh > > After applying the latest RHEL kernel updates (CVE-2017-1000364), all jsvc instance crash on start up with the following: > {quote}# > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGBUS (0x7) at pc=0x00007f0fcea07bdc, pid=28581, tid=0x00007f0fdfc0c700 > # > # JRE version: (8.0_121-b13) (build ) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # j java.lang.Object.()V+0 > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # //hs_err_pid28581.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp{quote} > Manually starting the service does not exhibit the problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)