[
https://issues.apache.org/jira/browse/IOTDB-502?page=com.atlassian.jira.plugin.system.issuetabp!nels:comment-tabpanel&focusedCommentId=17039130#comment-17039130
]
Xiangdong Huang commented on IOTDB-502:
---------------------------------------
The patch is ok.
But I think it is time to put "how to detect whether a client is compatible"
on the agenda.
> Fix possible NPE in `org.apache.iotdb.db.service.TSServiceImpl`
> ---------------------------------------------------------------
>
> Key: IOTDB-502
> URL: https://issues.apache.org/jira/browse/IOTDB-502
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Engine
> Reporter: Xin Wang
> Assignee: Xin Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ZoneId}} in {{org.apache.iotdb.db.service.TSServiceImpl#getTimeZone}} may
> be {{null}}
>
> One of the scenes may trigger the bug:
> {quote}The IoTDB server throws the following error when accessing 0.1p
> server(master) by 0.9 shell client (latest release).
> {quote}
>
> Exception trace:
> {quote}java.lang.NullPointerException: null at
> org.apache.iotdb.db.service.TSServiceImpl.getTimeZone(TSServiceImpl.java:1120)
> at
> org.apache.iotdb.service.rpc.thrift.TSIService$Processor$getTimeZone.getResult(TSIService.java:1853)
> at
> org.apache.iotdb.service.rpc.thrift.TSIService$Processor$getTimeZone.getResult(TSIService.java:1833)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at
> org.apache.thrift.TBaseProcessor.pro#ess(TBaseProcessor.java:38) at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:313)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
