[IGNITE-17145] Fix handle BinaryObjectException at the thin JDBC

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.13
• Fix Version/s: 2.14
• Component/s: jdbc
• Release Note: Fixed handling of BinaryObjectException on response to deserialization at the thin JDBC client
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Taras Ledkov
• Reporter: Taras Ledkov
• Created: 09/Jun/22 11:28
• Updated: 09/Sep/22 16:46
• Resolved: 14/Jun/22 09:02

Description

I am trying to get enum field using sqlline, but failed with error Statement is closed.

0: jdbc:ignite:thin://127.0.0.1> select status from nebulaclusterinfo;
Error: Statement is closed. (state=,code=0)
java.sql.SQLException: Statement is closed.
	at org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.ensureNotClosed(JdbcThinStatement.java:950)
	at org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.getWarnings(JdbcThinStatement.java:546)
	at sqlline.Commands.execute(Commands.java:849)
	at sqlline.Commands.sql(Commands.java:733)
	at sqlline.SqlLine.dispatch(SqlLine.java:795)
	at sqlline.SqlLine.begin(SqlLine.java:668)
	at sqlline.SqlLine.start(SqlLine.java:373)
	at sqlline.SqlLine.main(SqlLine.java:265)

0: jdbc:ignite:thin://127.0.0.1> select count(status) from nebulaclusterinfo;
+--------------------------------+
|         COUNT(STATUS)          |
+--------------------------------+
| 310                            |
+--------------------------------+
1 row selected (0.108 seconds)

Issue Links

• is duplicated by: IGNITE-17154 Fix handle BinaryObjectException at the thin JDBC
• links to: GitHub Pull Request #10084
• links to: TCBot