|
From: Toli K. <to...@ma...> - 2007-04-30 15:58:07
|
Robert, I believe i know what the problem may be. in QFJ 1.1.0 we fixed a bug where an error connecting to the Jdbc store caused teh JdbcLog to go into an infinite recursion and print out the log below: > java.sql.SQLException: We are already in the process of making 1 connections and the number of simultaneous builds has been throttled to 0 essentially, it catch an exception making the first db entry, then would try to log the exception, and never stop. you get the idea. > I'm still baffled though why my FileStoreFactory code (no JDBC logging) will not work with the 1.1.0 libraries though... in that case, you are not dealing with JdbcLog so everything worked fine - your system worked correctly and the above situation didn't happen. If you look at the output of QFJ 1.1, you should see somewhere a line saying something about encountering a "write to Jdbc" failure and quitting the JdbcLog. Still not sure why your app will quit completely in case of a JdbcLog failure - it should just not log, but the app itself should keep working. So see if your database is setup correctly, make sure you can log on to it with the credentials supplied in the SessionSettings, etc. Also, if you can, try to run it in the debugger and trap all Errors/Exceptions, maybe for some reason JdbcLog throws some error that kills your entire app? |