Re: [Sequoiadb-discuss] Request blocked forever in Sequoia

[Emmanuel C. <ma...@fr...>]

Hi Richard,

Sorry for forgetting about this. The fastest quick fix would be to 
change org.continuent.sequoia.controller.backend.DriverCompliance line 586
replace:
    return supportGetGeneratedKeys;
with
   return true;

That should fix it for now.

To really know what happens, using directly your MySQL driver to connect 
to your MySQL database, try a code like:
Connection c = DriverManager.connect(...);
Statement s = c.createStatement();
s.execute("select 1");
s.getGeneratedKeys();

This last call should trigger an SQLException. Please post that 
exception so that I can diagnose the problem.

Thanks for your feedback,
Emmanuel

> Hi Emmanuel,
>
> Is there any info I could send you in order to pinpoint the problem.
> I am running out of time and a decision will soon be made to go with 
> MySQL Cluster ($$$) and I don't want that.
>
> Thanks for your help,
>
> Richard 
>
>
> On May 14, 2009, at 6:48 PM, Richard Vigeant wrote:
>
>> Hi Emmanuel,
>>
>> I'm using MySQL 5.1.31 community with mysql-connector-java-5.1.7.
>>
>> Thanks,
>>
>> Richard
>>
>> -----Original Message-----
>> From: Emmanuel Cecchet [mailto:ma...@fr...]
>> Sent: Thu 5/14/2009 6:02 PM
>> To: Richard Vigeant
>> Cc: seq...@li... 
>> <mailto:seq...@li...>
>> Subject: Re: [Sequoiadb-discuss] Request blocked forever in Sequoia
>>
>> Hi Richard,
>>
>> > I'm sending you the debug log of the problem.
>> > I noticed that an error that repeatedly occurs about table
>> > 'alfresco.sequoiaSABase' does not exists. In fact I don't know where
>> > this comes from because there is no reference to such a table anywhere
>> > in our modules.
>> This was a prototype implementation of stored procedure semantic in the
>> database that has been deprecated. The message was not removed but it
>> can be safely ignored.
>>
>> The problem comes from there:
>> 2009-05-14 16:26:55,338 WARN  backend.DatabaseBackend.mysql1 Task
>> execution failed (java.sql.SQLException: Backend mysql1 does not support
>> auto generated keys.)
>>
>> What is strange is that the error does not get propagated back to the
>> client and get stuck.
>>
>> It might well be that your version of MySQL does not support generated
>> keys or that the JDBC driver is not compliant to the spec and when we
>> test Statement.getGeneratedKeys() it throws an exception rather than
>> returning a null ResultSet.
>>
>> Which version of MySQL are you using, with which driver?
>>
>> Thanks for the feedback,
>> Emmanuel
>>
>> --
>> Emmanuel Cecchet
>> FTO @ Frog Thinker
>> Open Source Development & Consulting
>> --
>> Web: http://www.frogthinker.org
>> email: ma...@fr... <mailto:ma...@fr...>
>> Skype: emmanuel_cecchet
>>
>>
>


-- 
Emmanuel Cecchet
FTO @ Frog Thinker 
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: ma...@fr...
Skype: emmanuel_cecchet