Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6E26104DC for ; Tue, 9 Jul 2013 16:47:53 +0000 (UTC) Received: (qmail 50273 invoked by uid 500); 9 Jul 2013 16:47:53 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 50034 invoked by uid 500); 9 Jul 2013 16:47:52 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 49921 invoked by uid 99); 9 Jul 2013 16:47:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 16:47:51 +0000 Date: Tue, 9 Jul 2013 16:47:51 +0000 (UTC) From: "Paulo Pires (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-5739) Class unloading triggers container crash MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Paulo Pires created CASSANDRA-5739: -------------------------------------- Summary: Class unloading triggers container crash Key: CASSANDRA-5739 URL: https://issues.apache.org/jira/browse/CASSANDRA-5739 Project: Cassandra Issue Type: Bug Components: Drivers Affects Versions: 1.2.4 Reporter: Paulo Pires While undeploying a Java webapp on a Glassfish cluster, I get a exception and consequently Glassfish crashes. The log can be seen at http://pastebin.com/CG6LKPEv After some research, WebappClassLoader tries to clear references on each loaded class, triggering the call to static StorageService.getPartitioner() which then tries to load the cassandra.yaml file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira