Subject | tomcat+fbsql-1.0.0 (yet). Cannot getAutocommit on one machine, doesnt on anoth |
---|---|
Author | fedd_kraft |
Post date | 2005-07-15T21:27:48Z |
Hello again!
Copied a tomcat webapp from one machine to another.
It began to complain
java.sql.SQLException: You cannot getAutomcommit on an unassociated
closed connection.
at org.firebirdsql.jdbc.FBConnection.getAutoCommit
(FBConnection.java:448)
at org.firebirdsql.jdbc.FBConnection.willEndTransaction
(FBConnection.java:1019)
at org.firebirdsql.jdbc.FBConnection.checkEndTransaction
(FBConnection.java:1024)
at org.firebirdsql.jdbc.FBPreparedStatement.executeQuery
(FBPreparedStatement.java:116)
but worked okay on previous location.
Happens when try to execute a precise prepared query (not first in
the program, but the same all the time).
Doesnt happen when the web app needs not to execute that precise
query, but goes other branch of algorythm. The query is valid, and
not callable statement (its just 'select count("id") from "permread"
where "id"=? and "userid"=?')
Impossible that the connection has been closed before - the program
would crash on both machines then.
Any ideas? (My silly thought is that threading in new tomcat is
organized different way, and the exception is an effect of 1.0 thread-
unsafety?... But this is not likely, because only one servlet works,
it takes connection from the pool at the beginning then puts it back
at the end of responding; there's no way for tomcat to execute that
straightforward servlet's response routine in several threads)
Copied a tomcat webapp from one machine to another.
It began to complain
java.sql.SQLException: You cannot getAutomcommit on an unassociated
closed connection.
at org.firebirdsql.jdbc.FBConnection.getAutoCommit
(FBConnection.java:448)
at org.firebirdsql.jdbc.FBConnection.willEndTransaction
(FBConnection.java:1019)
at org.firebirdsql.jdbc.FBConnection.checkEndTransaction
(FBConnection.java:1024)
at org.firebirdsql.jdbc.FBPreparedStatement.executeQuery
(FBPreparedStatement.java:116)
but worked okay on previous location.
Happens when try to execute a precise prepared query (not first in
the program, but the same all the time).
Doesnt happen when the web app needs not to execute that precise
query, but goes other branch of algorythm. The query is valid, and
not callable statement (its just 'select count("id") from "permread"
where "id"=? and "userid"=?')
Impossible that the connection has been closed before - the program
would crash on both machines then.
Any ideas? (My silly thought is that threading in new tomcat is
organized different way, and the exception is an effect of 1.0 thread-
unsafety?... But this is not likely, because only one servlet works,
it takes connection from the pool at the beginning then puts it back
at the end of responding; there's no way for tomcat to execute that
straightforward servlet's response routine in several threads)