From: Melissa C. <mel...@qx...> - 2005-01-09 21:48:51
|
Neither the V2 stardard or MT driver made a difference. However some further testing of mine may get closer to the problem. As I said earlier, removing the files from the application frame/thread fixed the problem. However this appears to only be true within the application, ie if i modify the same record on Thread A, then B then go back to A it is fine. However if I modify the record in application A then B then go back to A it is NOT ok, I get the same deadlock error. Vladimir Tsvigun wrote: > Hi, Melissa! > > >>I cant connect with anything but servername:alias becuase it is a linux >>server and we dont want the database openly available. > > > Very well! We already have many details :-) > > >>Since removing the files from the application frame this strange >>behaviour is fixed. > > > Ok! > However it is necessary to execute one more check > Please, > 1)download OdbcJdbc v2.0 and uninstall v1.2,v1.3 and install v2.0 > 2)You will see 2 installations at creation DSN from ODBC Administrator > > Firebird/InterBase(r) driver --> 1 connect -- 1 thread > Firebird/InterBase(r) driver MT --> 1 connect -- many thread > > 3)Create two different DSN and check up again you test > 4)Inform result > > >>(remembering the Gemini one did so it doesnt behave too badly). > > > Thanks :-) > > -- > Best regards, > Vladimir Tsvigun > Last snapshot OdbcJdbc here www.praktik.km.ua > |