Any details on that? Sorry this is so hard to debug, but if you're using Spring and Groovy on top of iBATIS, you'll have a heck of a stack trace to debug through....
iBATIS is a fairly simple little library, but when you pile all of that stuff on top it becomes pretty hard to find problems. Is there any way you can build a simpler implementation of one of your features that sidesteps all of the app layers you have, just to see if it's truly iBATIS or if it's something else? Also, I'm confused why the version in the trunk wouldn't work... Clinton -----Original Message----- From: Stéphane Hanser [mailto:[EMAIL PROTECTED] Sent: January-14-08 9:25 AM To: [email protected] Subject: Re: Ibatis throttle - possible deadlock (ibatis 2.2, 2.3) We also tried to use the last ibatis version from svn but it doesn't work with our application (it seems that tere are compatibility issues with groovy or something) Le 14 janv. 08 à 12:47, Nikolas Kyriazopoulos Panagiotopoulos a écrit : >> Could you possibly have an old iBATIS jar somewhere - maybe at the >> common >> or server level in Tomcat? > Not anymore. > >> >> What db and what version? If it's mysql, which type? > MySql 5.0.45 (client) 5.0.32-Debian_7etch3-log(server), InnoDb > >> What does the jdbc URL look like? Are you passing any special >> arguments >> via the JDBC URL? > jdbc:mysql://<an ip address here>/<database name here> > no arguments to my knowledge (apart from normal username and > password) > >> Are you using straight SQL in the SqlMaps or are you using stored >> procedures? > Straight SQL only > >> Are you seeing any locks in the db itself? > No. > >> You could set the java.sql logging category to DEBUG and then you'd >> be able >> to trace which statements are blocking. This will generate a lot >> of logfile >> data, so be ready for it. > > Ok, we are configuring it at the moment. Stay tuned ;) >
