Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.4.3
-
Component/s: None
-
Labels:None
Description
Here's the stack trace (and I don't need to unmarshal Subjects, but cannot seem to disable that converter)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at javax.security.auth.Subject.<clinit>(Subject.java:165)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.thoughtworks.xstream.converters.extended.SubjectConverter.class$(SubjectConverter.java:42)
at com.thoughtworks.xstream.converters.extended.SubjectConverter.canConvert(SubjectConverter.java:42)
at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:60)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60)
at com.conceptwave.yaml.XmlConverter.unmarshal(XmlConverter.java:417)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60)
at com.conceptwave.yaml.XmlConverter.unmarshal(XmlConverter.java:354)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60)
at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:137)
at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33)
at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:923)
[... snipped ...]
Caused by: java.lang.SecurityException: unable to instantiate Subject-based policy
at javax.security.auth.Policy.getPolicyNoCheck(Unknown Source)
at javax.security.auth.Policy.getPolicy(Unknown Source)
at javax.security.auth.SubjectDomainCombiner$5.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.SubjectDomainCombiner.compatPolicy(Unknown Source)
at javax.security.auth.SubjectDomainCombiner.<clinit>(Unknown Source)
... 41 more
Issue Links
- relates to
-
XSTR-566
AppEngine Compatibility.
-
Activity
XStream 1.3.3 never existed, so I think this report was for XStream 1.3.1. However, that was the first version that actually had a check for the availability of the Subject class in the XStream initialization. Unfortunately this check did only load the class, but without initializing it. Therefore the converter was registered nevertheless and the runtime initialized the class later at first access which caused the exception. XStream will now initialize the class directly at loading time and ignore any occurring LinkageError resulting in a normal failed attempt to locate it.
Jörg Schaible
added a comment - XStream 1.3.3 never existed, so I think this report was for XStream 1.3.1. However, that was the first version that actually had a check for the availability of the Subject class in the XStream initialization. Unfortunately this check did only load the class, but without initializing it. Therefore the converter was registered nevertheless and the runtime initialized the class later at first access which caused the exception. XStream will now initialize the class directly at loading time and ignore any occurring LinkageError resulting in a normal failed attempt to locate it. 
After removing all references to SubjectConverter from source code and rebuilding, works fine.
Here's relevant version information (I missed it when submitting a report):
Windows XP
java version "1.6.0_12"
XStream 1.3.3 release
Eclipse Project SDK Version: 3.5.0.v20090423-7Q7bA7DPQ1SM6OYQ7wKYJhI-z-xZJCmLTBRhtZ0o61b1z Build id: I20090611-1540