[Building Sakai] Elluminate (Collaborate) - Unique Constraint Error

[John Bush]

Ok here's the email I sent to them, and the patch.  If you are running
on 2.8 the only thing you need is to swap out the kernel-util version.

----------------

The changes to the hbm's are for the cluster issue.  I think that
should be pretty straightforward to a dev.  The one thing is you need
to manually update the database, because hibernate/mysql won't adjust
the columns to AUTO_INCREMENT.  I don't know how this affects Oracle,
I haven't tested that.

Here's the sql for MySql.  According to our MySQL expert, mysql will
automatically set the auto increment value to one more than the
highest value in the table, so there's shouldn't be any duplication
problems for those upgrading.

alter table ell_configuration modify ID bigint(20) NOT NULL AUTO_INCREMENT;
alter table ELL_SESSION_DATA modify ID bigint(20) NOT NULL AUTO_INCREMENT;

Let me know if you have questions, happy to go over any of the changes
with development.  Its really just a bunch of pom (ie build) changes,
to support 2.7, nothing in the code needed to change.



On Wed, May 16, 2012 at 8:04 PM, John Bush <john.bush at rsmart.com> wrote:
> Guys I sent them a patch to resolve this last year, it was a hibernate
> id uniqueness issue, I had access to their svn I think, let me see if
> I can dig up the patch.
>
> On Wed, May 16, 2012 at 2:23 PM, Geng, Kelly <gengx at muohio.edu> wrote:
>> Paul,
>>
>>
>>
>> We had the same issue last fall and contacted the vendor. They have fixed it
>> in a later version. We downloaded it and it has been working fine since
>> then.
>>
>>
>>
>> Kelly
>>
>>
>>
>>
>>
>> From: sakai-dev-bounces at collab.sakaiproject.org
>> [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Paul Dagnall
>> Sent: Wednesday, May 16, 2012 1:43 PM
>> To: Sam Ottenhoff
>> Cc: sakai-dev
>> Subject: Re: [Building Sakai] Elluminate (Collaborate) - Unique Constraint
>> Error
>>
>>
>>
>> Sam
>> Thanks a million! I believe you are right.
>>
>> I don't think there is much active development on this integration tool.
>> Here's the code:
>> https://source.sakaiproject.org/contrib/unicon/elluminate/
>>
>> Again, thank you!
>>
>> Paul Dagnall
>> Application Developer & Administrator
>> University of Dayton
>>
>> On Wed, May 16, 2012 at 11:45 AM, Sam Ottenhoff <ottenhoff at longsight.com>
>> wrote:
>>
>> My guess is that the developers of this tool incorrectly use the Hibernate
>> sequence generator called "increment" despite it being non-cluster-safe:
>>
>>
>>
>>    http://docs.jboss.org/hibernate/orm/3.3/reference/en/html/mapping.html
>>
>>
>>
>> Look in the Hibernate definition files (end in .hbm.xml) and look for:
>>
>>
>>
>>   <generator class="increment"/>
>>
>>
>>
>> That is bad and won't work for anyone that runs more than one Sakai server
>> (everyone).
>>
>>
>>
>> Use "native" instead and your database will generate sequences correctly:
>>
>>
>>
>>   <generator class="native"/>
>>
>>
>>
>> Do the developers of this integration maintain the integration as open
>> source?
>>
>>
>>
>> --Sam
>>
>> On Wed, May 16, 2012 at 11:36 AM, Paul Dagnall <pdagnall1 at udayton.edu>
>> wrote:
>>
>> Hi
>> We're getting a bizarre error using the Elluminate (now Blackboard
>> Collaborate) synchronous integration. The problem is, all works fine on app
>> server Sakai2 but I get "ORA-00001: unique constraint" when I do the same
>> thing on Sakai1. This error tells me that it's trying to insert a record
>> with a duplicate primary key. The code is identical on both servers.
>>
>> Using Sakai2 (the one that works) I can create records and I see the ID
>> column in ELL_SESSION_DATA table increment by 1 appropriately. Updates work
>> fine. It just seems to be inserts from Sakai1 only that cause the conflict.
>>
>> It gets stranger. On a whim I decided to redeploy the tool and bounce
>> tomcat. Afterward everything was fine on both servers for a time, but later
>> the problem resurfaced but it switched servers. The problem is only
>> happening on the other one now. Grrrr!
>>
>> We're new to using multiple app servers. Other tools are fine. Am I missing
>> something? Could there be a sequence missing? Have you ever heard of a
>> sequencing conflict like this occurring with multiple app servers connected
>> to the same database?
>>
>> Thanks!
>>
>> Paul Dagnall
>> Application Developer & Administrator
>> University of Dayton
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>
>
>
> --
> John Bush
> 602-490-0470



-- 
John Bush
602-490-0470
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.7.patch
Type: application/octet-stream
Size: 10746 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120516/4b55fafe/attachment.obj