[
https://issues.apache.org/jira/browse/IOTDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
刘大伟 closed IOTDB-300.
---------------------
> When the server restart, the client cannot find the connection error
> --------------------------------------------------------------------
>
> Key: IOTDB-300
> URL: https://issues.apache.org/jira/browse/IOTDB-300
> Project: Apache IoTDB
> Issue Type: Bug
> Reporter: 刘大伟
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 1. Start the IOTDB-Client and connect to the server successfully
> 2. Restart the server side
> 3. And then if you execute any command on the client, you will receive an
> error message: 'MSG: cannot get ID for statement'
>
> This problem occurs after the [iotdb-291] merge, because a *requeststmtid()*
> method is added before executing the SQL statement, but this method is not
> the same as the previous *executeQuery()* method: when an error is returned,
> re-establish a connection and try again.
>
> I will refer to the *executeQuery()* method of reconnection for repair. Of
> course, I think the best way is to have the client constantly check the
> connection. What do you think, friends?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
