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 B991E172D1 for ; Sun, 5 Apr 2015 21:34:34 +0000 (UTC) Received: (qmail 42944 invoked by uid 500); 5 Apr 2015 21:34:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 42903 invoked by uid 500); 5 Apr 2015 21:34:34 -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 42892 invoked by uid 99); 5 Apr 2015 21:34:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2015 21:34:34 +0000 Date: Sun, 5 Apr 2015 21:34:34 +0000 (UTC) From: "Will Zhang (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-9122) CassandraDaemon.java:167 NullPointerException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Will Zhang created CASSANDRA-9122: ------------------------------------- Summary: CassandraDaemon.java:167 NullPointerException Key: CASSANDRA-9122 URL: https://issues.apache.org/jira/browse/CASSANDRA-9122 Project: Cassandra Issue Type: Bug Environment: Windows 7 Reporter: Will Zhang Fix For: 2.1.3 Repeated occurrance of null pointer exception in system.log after upgrading from 2.1.2 to 2.1.3. System.log section below. ERROR [CompactionExecutor:40] 2015-04-05 18:34:36,413 CassandraDaemon.java:167 - Exception in thread Thread[CompactionExecutor:40,1,main] java.lang.NullPointerException: null at org.apache.cassandra.service.CacheService$KeyCacheSerializer.serialize(CacheService.java:475) ~[apache-cassandra-2.1.3.jar:2.1.3] at org.apache.cassandra.service.CacheService$KeyCacheSerializer.serialize(CacheService.java:463) ~[apache-cassandra-2.1.3.jar:2.1.3] at org.apache.cassandra.cache.AutoSavingCache$Writer.saveCache(AutoSavingCache.java:274) ~[apache-cassandra-2.1.3.jar:2.1.3] at org.apache.cassandra.db.compaction.CompactionManager$11.run(CompactionManager.java:1152) ~[apache-cassandra-2.1.3.jar:2.1.3] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_11] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_11] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_11] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_11] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11] INFO [ScheduledTasks:1] 2015-04-05 18:34:38,392 ColumnFamilyStore.java:877 - Enqueuing flush of sstable_activity: 35890 (0%) on-heap, 0 (0%) off-heap INFO [MemtableFlushWriter:30] 2015-04-05 18:34:38,401 Memtable.java:339 - Writing Memtable-sstable_activity@388081044(3726 serialized bytes, 1656 ops, 0%/0% of on/off-heap limit) -- This message was sent by Atlassian JIRA (v6.3.4#6332)