Query fails in JDBC but executes OK in CUBRID Manager

1. CM version is also 8.3.1?
2. The thing is CM works through JDBC, so the issue is interesting. But I will relay this issue to the Lab.

What an interesting issue it is!
Please check your JDBC version which CM is using, and if both JDBC version is same.
We are guessing that CAS was terminated during query processing, so that error message is “cannot communicate with a broker” and it causes CAS killed.

When executing the query in CSQL with server 8.3.1,
the result is
csql> SELECT MAX(SYS_CONNECT_BY_PATH(text, ''))AS myQuery FROM ( SELECT ROWNUM AS r, 'INSERT INTO _values (SELECT CAST(' + a.attr_name + ' as VARCHAR(255)) from ' + c.class_name + '); ' AS text FROM _db_class c JOIN _db_attribute a ON c = a.class_of JOIN _db_data_type t ON a.data_type = t.type_id WHERE c.is_system_class = 0 AND t.type_name in ('VARCHAR', 'CHAR', 'STRING', 'INT', 'SMALLINT', 'BIGINT', 'NUMERIC', 'FLOAT', 'DOUBLE', 'DATE', 'TIME', 'DATETIME', 'TIMESTAMP') ) AS res START WITH r = 1 CONNECT BY PRIOR r = r - 1;
csql> ;x

=== <Result of SELECT Command in Line 1> ===

myQuery
======================
NULL

however 8.4.0 results in:
csql> SELECT MAX(SYS_CONNECT_BY_PATH(text, ''))AS myQuery FROM ( SELECT ROWNUM AS r, 'INSERT INTO _values (SELECT CAST(' + a.attr_name + ' as VARCHAR(255)) from ' + c.class_name + '); ' AS text FROM _db_class c JOIN _db_attribute a ON c = a.class_of JOIN _db_data_type t ON a.data_type = t.type_id WHERE c.is_system_class = 0 AND t.type_name in ('VARCHAR', 'CHAR', 'STRING', 'INT', 'SMALLINT', 'BIGINT', 'NUMERIC', 'FLOAT', 'DOUBLE', 'DATE', 'TIME', 'DATETIME', 'TIMESTAMP') ) AS res START WITH r = 1 CONNECT BY PRIOR r = r - 1;

=== <Result of SELECT Command in Line 1> ===

myQuery
======================
'INSERT INTO _values (SELECT CAST(c5 as VARCHAR(255)) from t); INSERT INTO _values (SELECT CAST(c as VARCHAR(255)) from tab); INSERT INT
O _values (SELECT CAST(text as VARCHAR(255)) from tab2); '

1 rows selected.

Therefore we can also guess it should be engine's problem, not JDBC issue. However engine's different operation causes CAS killed.
Tell us more details about JDBC version, and server version+build number with "cubrid_rel"

The thing is that initially I was running CM 4.0 (so different JDBC file).
Today I run the same SQL in CM 8.3.1 (using 8.3.1 JDBC) so it was OK, too.
Conclusion: working on both CM 8.4.0 and CM 8.3.1 but not in Java (using JDBC 8.3.1)

The output of cubrid_rel is:
"CUBRID 2008 R3.1 (8.3.1.1002) (Feb 21 2011 18:52:22)"

Engine dev lab took the issue and moved to their BTS

Mr Kang dong wan is a new assignee.