Hi there! >Wow, that is a wacky one..it seems most likely that it is a driver issue (i >can promise that there is no >"if>(sql.length() == 1983) blowChunks();" code in SQL Maps.
:-) >Can you try it with the latest Oracle drivers? >From all reports, the 10g drivers resolved a ton of bugs that were popping up. 10g drivers ? Not sure what you mean ? We are running 9.2, found det ojdbc14.jar driver and tested it and general speaking the driver worked with our code at least. BUT when I tried to reproduce the error from yesterday with old driver, I was not able to do it !!!!!! :-( What a luck. This error has been present for 1 week now. But it was yesterday I found out the 1983 case. Since yesterday, haven't done anything that should have caused any bug "fix's" with this problem, even brought back some CVS version of part of the code involved, no luck either to reproduce it now. The only difference I can think of is the load of the system at the moment from yesterday when I found the "bug". Will try tomorrow again with the old driver to see if I can reproduce it, and then only switch to the new driver if it pop up again. >It might not hurt to update to a more recent iBATIS build, too. Thougth of that too, but at the moment too much testing of rest of the application, to be on the safe side before an upgrade :-) But we should do it soone yes. -- Anyway thanks for the driver tip, think we has been using the classes12.jar by an old habit :-) Cheers, Erlend
