Hi Myrna,
Thanks. Thinking about it, this test cannot run in this combination
(jdk13 server) because it uses a stored procedure which internally
sets the holdability. Since the network server is running with jdk13,
these statements in the stored procedure will not work:
Statement st1 = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE ,
ResultSet.CONCUR_READ_ONLY,
ResultSet.HOLD_CURSORS_OVER_COMMIT);
....
Statement st2 = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE ,
ResultSet.CONCUR_READ_ONLY,
ResultSet.CLOSE_CURSORS_AT_COMMIT);
You should see an exception in derby.log for this.
To make the test work in this combo, I think reflection can be used
for holdability calls in the stored procedure call. Other parts of
test should work, except for:
if(HAVE_DRIVER_MANAGER_CLASS){
testHoldability(conn,ResultSet.HOLD_CURSORS_OVER_COMMIT);
testHoldability(conn,ResultSet.CLOSE_CURSORS_AT_COMMIT);
}
)
Is this test you are doing a one-time test? If you plan to run it on a
regular basis, I think we should change the test. I guess the first
step is to see if remaining parts of test work in this server/client
jvm combination. Hope this helps.
Thanks,
Deepa
