[Building Sakai] Elluminate (Collaborate) - Unique Constraint

Thu May 17 04:23:29 PDT 2012

 Error
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=20cf303b40637a5d7e04c032ce2d

--20cf303b40637a5d7e04c032ce2d
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello.

A couple of thoughts next time someone works on the Elluninate LMS
add-on:

010 allow the school to set institutional defaults: pre-session access
(inc. any time), recording options, # of concurrent speakers, etc.

020 allow institutions to set default views, like monthly instead of
daily on the session recordings page would save a lot of end-user
frustration trying to find a session archive.

030 schools should be able to alter their default Elluminate email
template

040 fix bug where if the session is defined as public, only one
moderator can be listed (??)

I think anything of value that would make the tool more flexible,
efficient and easier to use should be considered on this and on any LMS
add-on.

Good to hear Blackboard is finally releasing new Elluninate mobile apps
this Summer.

Greetings from Chicago,

--- Ed Garay
Assistant Director for Academic Computing

Director, UIC Instructional Technology Lab

University of Illinois at Chicago

www.accc.uic.edu/itl
www.twitter.com/garay

***** Ubiquitously social...
***** Retiring (leaving UIC) on July 1st, 2012

Sent from my Nokia Lumia 900 Windows Phone

From: John Bush
Sent: 5/16/2012 10:12 PM
To: Geng, Kelly
Cc: sakai-dev
Subject: Re: [Building Sakai] Elluminate (Collaborate) - Unique
Constraint Error
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 fixe=
d 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 Dag=
nall
>> Sent: Wednesday, May 16, 2012 1:43 PM
>> To: Sam Ottenhoff
>> Cc: sakai-dev
>> Subject: Re: [Building Sakai] Elluminate (Collaborate) - Unique Constrai=
nt
>> 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 Hiberna=
te
>> sequence generator called "increment" despite it being non-cluster-safe:
>>
>>
>>
>> =C2=A0=C2=A0 http://docs.jboss.org/hibernate/orm/3.3/reference/en/html/m=
apping.html
>>
>>
>>
>> Look in the Hibernate definition files (end in .hbm.xml) and look for:
>>
>>
>>
>> =C2=A0=C2=A0<generator class=3D"increment"/>
>>
>>
>>
>> That is bad and won't work for anyone that runs more than one Sakai serv=
er
>> (everyone).
>>
>>
>>
>> Use "native" instead and your database will generate sequences correctly=
:
>>
>>
>>
>> =C2=A0=C2=A0<generator class=3D"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 sam=
e
>> 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 w=
ork
>> fine. It just seems to be inserts from Sakai1 only that cause the confli=
ct.
>>
>> 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 la=
ter
>> 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 miss=
ing
>> something? Could there be a sequence missing? Have you ever heard of a
>> sequencing conflict like this occurring with multiple app servers connec=
ted
>> 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

--=20
John Bush
602-490-0470

--20cf303b40637a5d7e04c032ce2d
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
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"
--20cf303b40637a5d7e04c032ce2d--