[Building Sakai] Gradebook2 and Sakai 2.6.x

Wed Jan 13 13:52:17 PST 2010

Hi Kevin,
Sorry about that... it's a known bug in the 1.1.x versions, in the JIRA as
GRBK-387 [1]. We're currently QAing a fix for 1.2.0 -- basically what's
happening is that the client is sending multiple (most likely identical)
configuration change requests, for example when the instructor changing the
width of a column... it's basically a transaction problem, so when the
second or third request arrives the query to determine if we want an insert
or an update in the db has already come back "insert", so the service tries
to insert twice with the same record. We have it in production without
hearing any negative feedback from the users, and from what I can see in the
code I believe it's in the category of unpleasant but non-destructive
exceptions.

Let me know if it's actually causing problems for you and I can try to
backport the fix to 1.1.x -- this would involve cutting a 1.1.6 tag.

Thanks,
James

[1] http://jira.sakaiproject.org/browse/GRBK-387

On Tue, Jan 12, 2010 at 5:36 PM, Kevin Chan <kevin at media.berkeley.edu>wrote:

>  Hi James,
>
> So it looks like while Gradebook2 is building against our Sakai 2.6.x
> deployment, we are now seeing DB constraint errors whenever we try to access
> the gradebook tool via GB1 or GB2:
>
> caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint
> (SAKAI_DEV. GB_GRADE_RECORD_T) violated
>
> I am going to try this again with some DB expert help next week, but was
> wondering if you or anyone else encounter this error.
>
> Also, I noticed in the SVN commits made against the 1.1.x-test (which was
> the basis for 1.1.5), there is a note " NOJIRA : rSmart is still at v2.6.1
> and not v2.6.2". I am guessing this was just a matter of pom updates.
>
> Finally, is anyone besides rSmart running Gradebook2 on 2.6.x?
>
>   Kevin Chan
>
>   Operations Team
>   Educational Technology Services
>   University of California, Berkeley
>
>
> On 11/23/09 1:45 PM, Kevin Chan wrote:
>
> Thanks James, those additional SQL statements did the trick (as far as
> loading of both the old and new Gradebooks go).
>
>   Kevin Chan
>
>   Operations Team
>   Educational Technology Services
>   University of California, Berkeley
>
>
> On 11/20/09 1:24 PM, James Renfro wrote:
>
> Apologies, it looks like I managed to check in a slightly newer patch under
> the 1.1.x branches, so the gradebook module's data model objects are now
> up-to-date with trunk, rather than the 1.1.x sql scripts.
>
> This is not an issue at all, since those fields will just be left null, but
> you'll need to apply the following in your db:
>
>
> https://source.sakaiproject.org/contrib/gradebook2/trunk/sakai/2-6-x/sql/oracle/GRBK-367.sql
>
> and possibly also
>
>
> https://source.sakaiproject.org/contrib/gradebook2/trunk/sakai/2-6-x/sql/oracle/GRBK-234.sql
>
> I'll update the 1.1.x-dev and 1.1.x-test branches to fix this, and I'm
> planning to bring gradebook2.sql up-to-date so that's the only script new
> installers need to run.
>
>
>
> On Thu, Nov 19, 2009 at 4:24 PM, Kevin Chan <kevin at media.berkeley.edu>wrote:
>
>> Hi James,
>>
>> Thanks for the notes. With the exception of using the 1.1.x-dev branch
>> instead of 1.1.x-test, I had followed the instructions very closely (there
>> was a part of a patch to Assignments.java that failed (easily merged) and
>> some "alter table" SQL that were unnecessary as the added columns are
>> already in our 2.6.x DB) and had gotten errors as I described previously.
>>
>> I rebuilt GB2 today with a clean copy of data from our production DB and
>> got the same results.
>>
>> If I try to view GB2, I get:
>>
>> org.sakaiproject.portal.api.PortalHandlerException:
>> org.sakaiproject.tool.api.ToolException: Request processing failed; nested
>> exception is
>> org.springframework.dao.InvalidDataAccessResourceUsageException: could not
>> execute query; nested exception is
>> org.hibernate.exception.SQLGrammarException: could not execute query
>>     at
>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:769)
>> ...
>> caused by: java.sql.SQLException: ORA-00904:
>> "GRADEBOOK0_"."DO_SHOW_ITEM_STATS": invalid identifier
>> --end of snippet
>>
>> I am not familiar with any table called "GRADEBOOK0", all Gradebook tables
>> begin with "GB_".
>>
>> If I try to view Gradebook, I get:
>>
>> org.sakaiproject.portal.api.PortalHandlerException:
>> org.sakaiproject.tool.api.ToolException: Cannot get value for expression
>> '#{bean.pageName ne 'gradebookSetup' && bean.userAbleToEditAssessments}'
>>     at
>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:769)
>>
>> caused by: org.sakaiproject.tool.api.ToolException: Cannot get value for
>> expression '#{bean.pageName ne 'gradebookSetup' &&
>> bean.userAbleToEditAssessments}'
>> --end of snippet
>>
>> Let me know if I should open a Jira ticket or if it is something that I
>> overlooked. Also, do you know if rSmart built GB2/2.6.x with the default
>> Sakai modules (like portal, we have a slightly customized version of portal
>> so maybe that is the problem) or if there were heavy changes/other modules
>> needed to make it work?
>>
>>
>> Thanks,
>>
>>   Kevin Chan
>>
>>   Operations Team
>>   Educational Technology Services
>>   University of California, Berkeley
>>
>>
>>  On 11/18/09 7:58 PM, James Renfro wrote:
>>
>> Hi Kevin,
>> It is definitely possible to get Gradebook2 working with a Sakai 2.6.x
>> deployment. RSmart has it running, and I'm working with it locally on my
>> desktop. Most of the other institutions that are using Gradebook2 are
>> running 2.5.x afaik.
>>
>> Not sure which tag you're installing. We're currently running 1.1.3 in
>> production at UCDavis, and this is our current "recommended" build for all
>> institutions, but ootb that tag is organized to build against 2.5.x right
>> now.
>>
>> Versions 1.1.3, 1.1.4, and 1.1.5 are all the same as far as actual code,
>> and represent incremental improvements to the build process.
>>
>> For 2.6.x compatibility I would recommend 1.1.5, which has not yet been
>> cut, but which will soon be our latest fully QA'd version that has been put
>> together explicitly to build against 2.6.x -- it will still require patches
>> to be applied to both the original gradebook module and sam module, which is
>> unfortunately going to be the case for gb2 in general at least until 2.7.x,
>> but it should no longer require any patching to the gradebook2 code itself
>> to run against 2.6.x -- you can run this code currently from our test
>> branch.
>>
>> https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test
>>
>> We should be cutting 1.1.5 itself in the next week, depending how long the
>> QA process takes, at which point the code will be at:
>>
>> https://source.sakaiproject.org/contrib/gradebook2/tags/1.1.5
>>
>>
>> If you're running with auto.ddl off, you will also need to run one or more
>> of the scripts included in:
>>
>>
>> https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/client/src/sql/oracle/
>>
>> For other instructions you may want to consult the 2.6.x install
>> directions, if you haven't dug them out already (they have been updated in
>> the last few days to match the current code).
>>
>>
>> https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/sakai/2-6-x/INSTALL.txt
>>
>> Finally, you may want to tweak the version of 2.6.x for the build... you
>> can do this by running this script:
>>
>>
>> https://source.sakaiproject.org/contrib/gradebook2/branches/1.1.x-test/setSakaiVersion.sh
>>
>>
>> Please let me know if you run into any problems,
>> James
>>
>>
>>
>> On Wed, Nov 18, 2009 at 5:06 PM, Kevin Chan <kevin at media.berkeley.edu>wrote:
>>
>>> Hi,
>>>
>>> I am looking to do a test build of Gradebook2 as a part of UC Berkeley's
>>> Sakai 2.6.x deployment. It looks like rSmart has already completed this
>>> implementation and the effort to document/implement this is happening in:
>>>
>>> http://jira.sakaiproject.org/browse/GRBK-330
>>> http://jira.sakaiproject.org/browse/GRBK-422
>>>
>>> Although I managed to compile GB2 with our code, there were some DB
>>> errors when I attempted to view both GB2 and the 2.6.x gradebook. This
>>> issue may very well be self generated (I am not working with a clean
>>> DB), but I just wanted to see if anyone can confirm that this is
>>> possible and any instruction (perhaps something not currently in any
>>> INSTALL.txt files) would be great.
>>>
>>> I am working with the GB2 1.1.x-dev branch as that appears to be the one
>>> that is being used for 2.6.x integration.
>>>
>>> Thanks,
>>>
>>> --
>>>   Kevin Chan
>>>
>>>   Operations Team
>>>   Educational Technology Services
>>>   University of California, Berkeley
>>>
>>> _______________________________________________
>>> 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"
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100113/4567f158/attachment.html 