Subject Re[2]: [Firebird-Java] problems on linux...
Author Marczisovszky Daniel
DJ> I ran into this a long time ago and never found a solution except not to
DJ> use isql. I have no idea what is causing this.  As you say, sticking
DJ> entirely to the java drivers seems to work ok.  I think closing isql may
DJ> also make the changes visible??

no. it does not help at all. this is not a problem of isql. I've also
tried with FIBPlus, IBX and ZeosLIB for Delphi and I could not update
the database with any of them.

Well, while I was playing with it, I found a more serious issue:

I've added close statements to my code, which is absolutely correct
according to the API.

The original code was this

Statement st = conn.createStatement();
ResultSet rs = st.executeQuery("select username from test");
rs.next();
System.out.println(rs.getString(1));
try {
Thread.sleep(2000);
}
catch (Exception ee) {}

and replaced with this:

Statement st = conn.createStatement();
ResultSet rs = st.executeQuery("select username from test");
rs.next();
System.out.println(rs.getString(1));
rs.close();
st.close();
try {
Thread.sleep(2000);
}
catch (Exception ee) {}

So when I run this new test and I connect to the test.gdb (I only
connect, I do not issue any sql command) then the java test hangs up.
It stops, but I don't know where. I've attached the log file, the jave
test ran three iterations, so it read the first record three times.

David, don't you know personally someone from FB developers who has
linux and may run this test? This is a joke, we can not have releases
of a database system with such issues. This means one can not manage
his database remotely, only with java. If it is the bug of Firebird,
then this is a quite serious issue and should be fixed as soon as it
is possible.

It hangs up at a op_response according to the log, but I can not
interpret it.

Roman, I you tell me what would be required on a linux box for
debugging, probably I could give an account. (although that linux box is
not mine, but I will try everything to solve this)

If it is the bug of the driver, I'm sure we can find it out, we're
good :)

Best wishes,
Daniel