[Building Sakai] Problems with jdk 1.7.0_71 and assignments

[Matthew Jones]

What method are you seeing this in (for the debug statements)? Can you
attach the patch where you put in this debugging to a jira? I haven't
upgraded to _71 yet but not sure how this could happen either.

On Tue, Oct 28, 2014 at 2:03 PM, John Hall <hall at udel.edu> wrote:

> We're running Oracle 11g on Solaris x86, and our Tomcats are 7.0.54.
>
> I just tried a fresh 1.7.0_72 on our dev server and that had the issue as
> well.  Going back to 65 again fixed it.
>
> -John
>
> On Tue, Oct 28, 2014 at 1:32 PM, Kirschner, Beth <bkirschn at umich.edu>
> wrote:
>
>> That's disturbing - we're about to upgrade to Java 1.7.0_71, so I'm
>> curious if anyone else has seen this too. Even though it looks like it's
>> not database related, I am curious what database you are using?
>>
>> - Beth
>>
>> On Oct 28, 2014, at 11:32 AM, John Hall <hall at udel.edu> wrote:
>>
>> > We've recently upgraded Java to 1.7.0_71 on out Sakai 2.9.3 instance
>> and since then have experienced a strange problem with the assignment tool.
>> >
>> > For a very small number of submissions the assignment id is being
>> corrupted at some point -- not apparently in the database since I've
>> checked the problem submissions and assignments, including decoding the
>> BASE64 XML and all assignment IDs look OK there.  In all the cases I've
>> examined, just the first character of the UUID is changing at some point to
>> a non-hexadecimal character (I've seen 'r','s',etc).
>> >
>> > For instance I added some logging, and can see that the assignment ID
>> is correct at some point, but then gets changed:
>> >
>> > 2014-10-28 10:34:43,267 DEBUG ajp-bio-8019-exec-8
>> org.sakaiproject.assignment.impl.BaseAssignmentService - Got
>> assignmentId=17a46ae0-6ccc-45ce-b68f-00b39db78a52 from ref
>> >
>> > 2014-10-28 10:34:43,273 DEBUG ajp-bio-8019-exec-8
>> org.sakaiproject.assignment.impl.BaseAssignmentService - calling
>> submissionReference with assignmentId=s7a46ae0-6ccc-45ce-b68f-00b39db78a52
>> >
>> > The URLs for grading in the assignment list for grading have the
>> incorrect assignmentId and cause an NPE at the point it tries to get a
>> grade, since the assignment doesn't exist under that ID.   No further
>> assignments are listed so Instructors are stuck not being able to grade
>> further submissions.  I suspect something's going wrong in Velocity.
>> >
>> > I reproduced the problem on a dev server by copying the database over,
>> and when I changed it back to Java 1.7.0_65 the problem went away.  All the
>> assignmentids and grading links were correct in the GUI and no NPE.
>> >
>> > Has anyone else experienced this?  I'm trying to figure out if it's a
>> general sakai problem, in which case I'll  put a Jira in, or something
>> specific to our local deployment.
>> >
>> > Thanks,
>> > John Hall
>> > --
>> >
>> > John F. Hall
>> > Project Leader I, IT-Web Development
>> > University of Delaware
>> > _______________________________________________
>> > 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 F. Hall
> Project Leader I, IT-Web Development
> University of Delaware
>
> _______________________________________________
> 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/20141028/ca44a88c/attachment.html