Blocker Description
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.