Lists of properties not read correctly from binary entites
Description
Activity
Megan May October 3, 2008 at 11:15 AM
These fixes have been included in an official foundation release so I am marking them as closed and unassigning them from the Sakai QA account
Peter Knoop May 20, 2008 at 10:52 AM
Based on comments, this appears to be resolved in 2.5.x as well, so adding to the list of Fix Versions.
David Horwitz May 19, 2008 at 12:43 AM
Yes version mismatch between content and entity
Ian Boston May 17, 2008 at 4:30 PM
I believe this was due to an incomplete build in 2.5.x ?
David Horwitz May 16, 2008 at 12:19 AM
This seems to cause test failures on 2-5-x:
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.733 sec <<< FAILURE!
testParse(org.sakaiproject.content.impl.serialize.impl.test.ProfileSerializerTest) Time elapsed: 4.663 sec <<< ERROR!
org.sakaiproject.entity.api.serialize.EntityParseException: Failed to parse entity
at org.sakaiproject.util.serialize.Type1BaseResourcePropertiesSerializer.parse(Type1BaseResourcePropertiesSerializer.java:131)
at org.sakaiproject.content.impl.serialize.impl.Type1BaseContentCollectionSerializer.doParse(Type1BaseContentCollectionSerializer.java:368)
at org.sakaiproject.content.impl.serialize.impl.Type1BaseContentCollectionSerializer.parse(Type1BaseContentCollectionSerializer.java:178)
at org.sakaiproject.content.impl.serialize.impl.test.ProfileSerializerTest.testParse(ProfileSerializerTest.java:104)
Caused by: java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:178)
at java.io.DataInputStream.readUTF(DataInputStream.java:565)
at java.io.DataInputStream.readUTF(DataInputStream.java:522)
at org.sakaiproject.util.serialize.Type1BaseResourcePropertiesSerializer.parse(Type1BaseResourcePropertiesSerializer.java:100)
... 29 more
Results :
Tests in error:
testParse(org.sakaiproject.content.impl.serialize.impl.test.ProfileSerializerTest)
Tests run: 7, Failures: 0, Errors: 3, Skipped: 0
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.sakaiproject.content.impl.serialize.impl.test.GMTDateformatterTest
16-May-2008 09:11:36 org.sakaiproject.content.impl.serialize.impl.test.GMTDateformatterTest testParse
INFO: Took 285 ms 0.01425 per parse
16-May-2008 09:11:36 org.sakaiproject.content.impl.serialize.impl.test.GMTDateformatterTest testParse
INFO: Took 135 ms 0.00675 per format
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.025 sec
testPad(org.sakaiproject.content.impl.serialize.impl.test.GMTDateformatterTest) Time elapsed: 0.007 sec
testParse(org.sakaiproject.content.impl.serialize.impl.test.GMTDateformatterTest) Time elapsed: 0.969 sec
Results :
Tests in error:
Tests run: 9, Failures: 0, Errors: 3, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
In some http level testing, I have been exercising some code that is not used (AFAIK), but could effect the reading back of lists of properties being stored in binary entites. A grep of the code base shows that this never happens in the core of sakai.
The symptoms are 2 fold. a) a set of properties stored as a List, is written to the database, but are missing when read back from the database.
or b) the EOFException is thrown on reading a binary entity containing a List of properties.
In the operation itself there is no dataloss, but the UI and user might get confused.
I have marked this as a blocker against 2.5.0 targetted for 2.5.x and 2.5.1 as I think there is potential data loss if the tool trying to do this to a ContentResource or a ContentCollection could generate the impression of data loss even though the data is in the DB.
I will update the Unit tests in this area to target the problem and commit a fix. This should be applied to 2.5.x and 2.5.1