I had quite a number of this dead lock issues before, have to modify the code, trial and error, just to make it works, looks like the main problem is this jdbc 3.x, so far so good.
Davor Hrg wrote: > > nice to know :) , thnx > I still use 3.x :) > > On Wed, Jul 9, 2008 at 9:10 AM, Angelo Chen <[EMAIL PROTECTED]> > wrote: > >> >> just discovered that my mysql jdbc driver is stil 3.x, updated to 5.1.6 >> in >> pom.xml, problem goes away up to now. >> >> >> Angelo Chen wrote: >> > >> > Hi, >> > >> > I encounter this warning quite often, it usually happens when I updated >> a >> > row using mysql command line, then quit, after that I either update or >> > append some rows using T5-hibernate, any idea why ? Thanks. >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/T5%3A-dead-lock-in-Tapestry---Hibernate-tp18353145p18355745.html >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/T5%3A-dead-lock-in-Tapestry---Hibernate-tp18353145p18356498.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
