From: Richard V. <ric...@va...> - 2009-05-14 19:54:25
|
Hi, Actually I meant that the query as seen in MySQL had a value of (0, null, 'M') while in Sequoia it shows (0, -5, 'M'). I will make a debug trace and and send it to you. Thanks, Richard On May 14, 2009, at 3:36 PM, Emmanuel Cecchet wrote: > Richard, > >> 2- The query that blocks in Sequoia's write request queue is >> slightly different in Sequoia than in direct MySQL: >> In mysql: insert into alf_attributes (version, acl_id, >> type) values (0, null, 'M') >> In Sequoia: insert into alf_attributes (version, acl_id, >> type) values (?, ?, 'M') | <!%L|0|!%><!%N|-5|!%> > Actually it's the same query. The %N tag is to encode null so that > the code called is PreparedStatement.setNull(param, sqlType) with > sqlType being equal to -5 (which corresponds to BIGINT in > java.sql.Types). In both cases, you are exactly executing the same > query. > > Otherwise your configuration seems fine so we probably have to look > somewhere else. > Set the scheduler, loadbalancer and DatabaseBackend loggers to DEBUG > in log4j.properties and send the trace so that we can see what is > going on. > > Thanks for your feedback, > Emmanuel > > -- > Emmanuel Cecchet > FTO @ Frog Thinker Open Source Development & Consulting > -- > Web: http://www.frogthinker.org > email: ma...@fr... > Skype: emmanuel_cecchet > |