Beeline may throw the misleading exception

Sometimes we can see 'out of sequence response' message in beeline, for example:

Error: org.apache.thrift.TApplicationException: CloseOperation failed: out of sequence response (state=08S01,code=0)
java.sql.SQLException: org.apache.thrift.TApplicationException: CloseOperation failed: out of sequence response
at org.apache.hive.jdbc.HiveStatement.closeClientOperation(HiveStatement.java:198)
at org.apache.hive.jdbc.HiveStatement.close(HiveStatement.java:217)
at org.apache.hive.beeline.Commands.execute(Commands.java:891)
at org.apache.hive.beeline.Commands.sql(Commands.java:713)
at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:976)
at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:816)
at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:774)
at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:487)
at org.apache.hive.beeline.BeeLine.main(BeeLine.java:470)

and there is no other usage message to figured it out, even with --verbose, this makes problem puzzled as beeline does not have concurrency problem on underlying thrift transport.