[
https://issues.apache.org/jira/browse/HBASE-15127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-15127:
-----------------------------------
Fix Version/s: (was: 1.4.2)
(was: 1.3.2)
(was: 2.0.0)
Not looked at since 2016, unscheduling. Probably should close as CR
> NPE in RpcServer$Call.wrapWithSasl()
> ------------------------------------
>
> Key: HBASE-15127
> URL: https://issues.apache.org/jira/browse/HBASE-15127
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Priority: Major
>
> I saw this in a log file, not sure whether it is important to fix or not:
> {code}
> 2016-01-09 01:30:58,905 WARN [FifoRpcScheduler.handler1-thread-25]
> ipc.RpcServer: FifoRpcScheduler.handler1-thread-25: caught:
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Call.wrapWithSasl(RpcServer.java:412)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Call.setResponse(RpcServer.java:395)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:128)
> at
> org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:74)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is 0.98 based code base corresponding to:
> {code}
> synchronized (connection.saslServer) {
> token = connection.saslServer.wrap(responseBytes, 0,
> responseBytes.length);
> }
> {code}
> I believe the saslserver was set to null earlier by {{disposeSasl()}} because
> Connection is closing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
