[AMBARI-2526] NPE in the ambari log4j when the threads are shutting down

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2.4
• Fix Version/s: 1.2.4
• Component/s: ambari-server
• Assignee: Sumit Mohanty
• Reporter: Sumit Mohanty
• Created: 01/Jul/13 17:12
• Updated: 01/Jul/13 17:39
• Resolved: 01/Jul/13 17:39

Description

NPE in the ambari log4j when the threads are shutting down.

Here is the stack trace:

[6/30/13 11:47:22 PM] 
Logging initialized using configuration in jar:file:/grid/3/hadoop/mapred/taskTracker/distcache/1047829140697497604_-722583028_403336841/host1/apps/webhcat/hive.tar.gz/hive/lib/hive-common-0.11.0.1.3.0.0-107.jar!/hive-log4j.properties
Exception in thread "Thread-1" java.lang.NullPointerException
    at org.apache.ambari.log4j.common.store.DatabaseStore.close(DatabaseStore.java:99)
    at org.apache.ambari.log4j.common.LoggingThreadRunnable.run(LoggingThreadRunnable.java:72)
    at java.lang.Thread.run(Thread.java:662)
FAILED: Error in metadata: org.apache.thrift.transport.TTransportException: java.net.SocketTimeoutException: Read timed out
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask
templeton: job failed with exit code 1