You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/11/21 05:12:42 UTC
[jira] Created: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Mixing Attribute value types results in write failures
------------------------------------------------------
Key: DIRSERVER-1104
URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
Project: Directory ApacheDS
Issue Type: Bug
Components: core
Affects Versions: 1.5.1, bigbang
Reporter: Alex Karasulu
Assignee: Alex Karasulu
Priority: Blocker
Fix For: bigbang
This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
Here's an example entry which would cause such a failure:
dn: cn=person1,ou=system
objectClass: organizationalPerson
cn: person1
sn: sn_person1
seealso: cn=Good One,ou=people,o=sevenSeas
seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (DIRSERVER-1104) Mixing Attribute value types results in write failures
Posted by Alex Karasulu <ak...@apache.org>.
Superb fix!!! You rock!
On Nov 21, 2007 6:18 PM, Emmanuel Lecharny (JIRA) <ji...@apache.org> wrote:
> Emmanuel Lecharny resolved DIRSERVER-1104.
> ------------------------------------------
>
> Resolution: Fixed
>
> In our case, we were trying to substitute a byte[] with the correct String value, after comparing the stored byte[] with the string.getBytes( "UTF-8" ). There were _no_ chance it could happen, leading the byte[] to stay into an attribute supposed to contain only Strings.
Thanks for it.
Alex
[jira] Commented: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544538 ]
Alex Karasulu commented on DIRSERVER-1104:
------------------------------------------
The integration tests fail on windows. This is where the bug clearly shows itself but *NIX can be made to show it as well.
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-1104.
------------------------------------
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.4, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 1.5.4
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1104:
-------------------------------------
Attachment: error.log
This is a log of the error showing the bug clearly in SchemaServiceITest
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1104.
------------------------------------------
Resolution: Fixed
There was a very stincky error in the way value removal where handled in AttributeImpl :
if one byte[] value was to be removed from an attribute's Value, then a pointer comparison was done instead of a Arrays.equals(). Obviously, the existing value was not removed, as the pointer was different.
In our case, we were trying to substitute a byte[] with the correct String value, after comparing the stored byte[] with the string.getBytes( "UTF-8" ). There were _no_ chance it could happen, leading the byte[] to stay into an attribute supposed to contain only Strings.
Fixed in bigbang :
http://svn.apache.org/viewvc?rev=597245&view=rev
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1104:
-------------------------------------
Attachment: offending.ldif
This is the example LDIF that causes a failure if loaded and the server is sync'd. It's taken directly from here where thanks to this kind of data we were able to find this bug:
http://tinyurl.com/yw6bjx
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-1104:
----------------------------------------
Assignee: Emmanuel Lecharny (was: Alex Karasulu)
I need your help with this. You have much of the background knowledge on the matter.
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544535 ]
Emmanuel Lecharny commented on DIRSERVER-1104:
----------------------------------------------
Does the trunk build ok? Of so, yes, I agree, we will have to get this issue fixed before merging bigbang into runk. Makes sense.
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544512 ]
Alex Karasulu commented on DIRSERVER-1104:
------------------------------------------
You say,
"I would not do that right now as we will have a new sub-project (server-entry) where we will have all those classes."
OK if that's the case I don't think we want to move this branch over into the trunk until this issue is completely fixed. If there is some workaround to remove it then we should think of applying it. The ServerEntry effort is dragging it's feet so I don't know how much exposure we'll have with this problem.
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544164 ]
Alex Karasulu commented on DIRSERVER-1104:
------------------------------------------
I went in to fix this thinking it would be simple and ran into all these problems:
(1) Why was the serialization structure of the partition changed? We are now storing an extra byte at the beginning of a value to indicate that it is a byte[] or a String.
The presumption that all values of an attribute are either a byte[] or a String is incorrect so doing this is a problem unless we can convert the value to the proper format correctly by considering the syntax of the value. This however is not a simple matter. There may be no way this far into the persistence code to determine the syntax associated with a value being persisted. This alteration was a bad move IMHO and screws us a bit.
(2) Why has all this code been moved to ldap-shared when it deals specifically with the serialization mechanism used by the JDBM partition implementation?
Too many things are being put into the ldap-shared module. It's a jumbled up mess in there and it's only getting bigger. Only put things into shared if it really can be reused. This very specific serialization mechanism may not be.
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1104) Mixing Attribute value types
results in write failures
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544402 ]
Emmanuel Lecharny commented on DIRSERVER-1104:
----------------------------------------------
I have added this byte in front of each value because I needed to know which kind of value it was : String or byte[]. It's mandatory unless you accept to have classCast exceptions.
Now, from the server POV, values are supposed to be H/R or not. If they are H/R (and the schema nows about it), values are stored as Strings. If not, they are stored as byte[]. If a value is not H/R and you pass a String, we convert the String to a byte[] before storing it.
If you try to import a LDIF into the server, as it goes through the chain, it should be the same.
In your sample, the seealso field contains a base64 encoded DN :
cn=Bad Eékà ,ou=people,o=sevenSeas
This is another problem which should be handled differently (seems to me that the DN syntax checker is not strict enough ...)
No need to change all the server logic to fix such a problem. It will be changed anyway when we will use Value instead of byte[] or Strings.
We can move back the serializers to another place, close to JDBM, sure. It has been moved close to the place where those attributes where defined.
I would not do that right now as we will have a new sub-project (server-entry) where we will have all those classes.
> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
> Key: DIRSERVER-1104
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: bigbang, 1.5.1
> Reporter: Alex Karasulu
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: bigbang
>
> Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.
> First a characterization of the bug. An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values. Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable. However this is not the case. The fact that an attributeType is human readable has no bearing on how the user supplies the value. Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
> dn: cn=person1,ou=system
> objectClass: organizationalPerson
> cn: person1
> sn: sn_person1
> seealso: cn=Good One,ou=people,o=sevenSeas
> seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException. Note the log of the error can be found attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.