[gradebook2-dev] Gradebook2 v1.4.1 UI isssue

Mon Dec 19 15:46:04 PST 2011

We ran into the same problem. The issue is that Java is UTF-16 and
Oracle is UTF-8. So if the user enters multibyte characters, it can
happen that we end up with more than 756 bytes. What we did in the
short term is to double the field size to 1512. In the long run, we
need to validate user input and use byte string length operations
rather than string based ones.

Please see https://jira.sakaiproject.org/browse/GRBK-945 for more details.
-- Thomas

On Mon, Dec 19, 2011 at 2:25 PM, Geng, Kelly <gengx at muohio.edu> wrote:
> Thomas,
>
> Following up with this column length issue, I have changed the column size from 255 to 756 a few months back, and it seems to fix the problem until today I see another bug report pasted below. It seems like gb2 is trying to insert that column with a 757-length content. Do you have any idea what caused this? We are running 1.4.1 gb2 + Sakai 2.7.x + Oracle.
>
> Thanks,
> Kelly
>
> ========================================================
> stack trace:
>
> org.sakaiproject.portal.api.PortalHandlerException: org.sakaiproject.tool.api.ToolException: Request processing failed; nested exception is org.springframework.jdbc.UncategorizedSQLException: Hibernate flushing: could not insert collection: [org.sakaiproject.gradebook.gwt.sakai.model.ActionRecord.propertyMap#1278770]; uncategorized SQLException for SQL [insert into GB_ACTION_RECORD_PROPERTY_T (ACTION_RECORD_ID, PROPERTY_NAME, PROPERTY_VALUE) values (?, ?, ?)]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
> ; nested exception is java.sql.BatchUpdateException: ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
>
>    at org.sakaiproject.portal.charon.handlers.ToolHandler.doPost(ToolHandler.java:73)
> caused by: org.sakaiproject.tool.api.ToolException: Request processing failed; nested exception is org.springframework.jdbc.UncategorizedSQLException: Hibernate flushing: could not insert collection: [org.sakaiproject.gradebook.gwt.sakai.model.ActionRecord.propertyMap#1278770]; uncategorized SQLException for SQL [insert into GB_ACTION_RECORD_PROPERTY_T (ACTION_RECORD_ID, PROPERTY_NAME, PROPERTY_VALUE) values (?, ?, ?)]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
> ; nested exception is java.sql.BatchUpdateException: ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
>
>    at org.sakaiproject.portal.charon.SkinnableCharonPortal.forwardTool(SkinnableCharonPortal.java:1303)
> caused by: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.springframework.jdbc.UncategorizedSQLException: Hibernate flushing: could not insert collection: [org.sakaiproject.gradebook.gwt.sakai.model.ActionRecord.propertyMap#1278770]; uncategorized SQLException for SQL [insert into GB_ACTION_RECORD_PROPERTY_T (ACTION_RECORD_ID, PROPERTY_NAME, PROPERTY_VALUE) values (?, ?, ?)]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
> ; nested exception is java.sql.BatchUpdateException: ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
>
>    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
> caused by: org.springframework.jdbc.UncategorizedSQLException: Hibernate flushing: could not insert collection: [org.sakaiproject.gradebook.gwt.sakai.model.ActionRecord.propertyMap#1278770]; uncategorized SQLException for SQL [insert into GB_ACTION_RECORD_PROPERTY_T (ACTION_RECORD_ID, PROPERTY_NAME, PROPERTY_VALUE) values (?, ?, ?)]; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
> ; nested exception is java.sql.BatchUpdateException: ORA-12899: value too large for column "SAKAI_2"."GB_ACTION_RECORD_PROPERTY_T"."PROPERTY_VALUE" (actual: 757, maximum: 756)
>
>
> -----Original Message-----
> From: gradebook2-dev-bounces at collab.sakaiproject.org [mailto:gradebook2-dev-bounces at collab.sakaiproject.org] On Behalf Of Geng, Kelly
> Sent: Friday, October 14, 2011 2:01 PM
> To: Thomas Amsler
> Cc: gradebook2-dev at collab.sakaiproject.org
> Subject: Re: [gradebook2-dev] Gradebook2 v1.6.1 UI isssue
>
> Great! Thanks!
>
> -----Original Message-----
> From: Thomas Amsler [mailto:tpamsler at ucdavis.edu]
> Sent: Friday, October 14, 2011 2:00 PM
> To: Geng, Kelly
> Cc: gradebook2-dev at collab.sakaiproject.org
> Subject: Re: Gradebook2 v1.6.1 UI isssue
>
> Yes, once you change the length from 255 to 756, you won't have the
> GRBK-945 issue.
> -- Thomas
>
> On Fri, Oct 14, 2011 at 10:43 AM, Geng, Kelly <gengx at muohio.edu> wrote:
>> So the column length is the only cause of the issue? I already applied the workaround, and just want to make sure it will fix the issue.
>>
>> -kelly
>>
>>
>>
>> -----Original Message-----
>> From: Thomas Amsler [mailto:tpamsler at ucdavis.edu]
>> Sent: Friday, October 14, 2011 1:36 PM
>> To: Geng, Kelly
>> Cc: gradebook2-dev at collab.sakaiproject.org
>> Subject: Re: Gradebook2 v1.6.1 UI isssue
>>
>> We need to adjust the HBM files so that auto.ddl process works properly.
>> -- Thomas
>>
>> On Fri, Oct 14, 2011 at 10:34 AM, Geng, Kelly <gengx at muohio.edu> wrote:
>>> So is the fix of GRBK-945 just to change the audo ddl, or is it not confirmed that it will completely fix the issue?
>>>
>>> Thanks!
>>>
>>> -kelly
>>>
>>> -----Original Message-----
>>> From: Thomas Amsler [mailto:tpamsler at ucdavis.edu]
>>> Sent: Friday, October 14, 2011 1:31 PM
>>> To: Geng, Kelly
>>> Cc: gradebook2-dev at collab.sakaiproject.org
>>> Subject: Re: Gradebook2 v1.6.1 UI isssue
>>>
>>> On Fri, Oct 14, 2011 at 6:00 AM, Geng, Kelly <gengx at muohio.edu> wrote:
>>>> Ok, will do. Does v1.5.1 have this issue?
>>>
>>> Yes.
>>>
>>>>
>>>> Also, is the root cause of "Failed Request" logged in https://jira.sakaiproject.org/browse/GRBK-945 get figured out and fixed? We got complaints about this occasionally and really want it to be fixed.
>>>
>>> It's not fixed yet, but GRBK-945 has a documented workaround.
>>>
>>> -- Thomas
>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Thomas Amsler [mailto:tpamsler at ucdavis.edu]
>>>> Sent: Friday, October 14, 2011 1:15 AM
>>>> To: Geng, Kelly
>>>> Cc: gradebook2-dev at collab.sakaiproject.org
>>>> Subject: Re: Gradebook2 v1.6.1 UI isssue
>>>>
>>>> Please create a GRBK JIRA:
>>>> https://jira.sakaiproject.org/browse/GRBK
>>>>
>>>> and provide as much detail as possible on how to reproduce this. There is one known issues w.r.t. the "Updating..." message:
>>>> https://jira.sakaiproject.org/browse/GRBK-1121
>>>>
>>>> ..., which will be fixed in 1.7.0.
>>>>
>>>> Best,
>>>> -- Thomas
>>>>
>>>>
>>>> On Thu, Oct 13, 2011 at 9:20 PM, Geng, Kelly <gengx at muohio.edu> wrote:
>>>>> Hi GB2 Developers,
>>>>>
>>>>> We are planning to upgrade gb2 1.4.1 to 1.6.1. Playing it on our dev server, I found that in the instructor view, every time I tried to save the editing in the Gradebook Settings panel, on top of the screen it shows "Updating..." but never went away until I close the panel ( see the attached screenshot). This may confuse the users and have them waiting. Is this something which can be fixed?
>>>>>
>>>>> Thanks,
>>>>> Kelly Geng
>>>>> Miami University
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
> _______________________________________________
> gradebook2-dev mailing list
> gradebook2-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/gradebook2-dev