Fixing XStream ObjectAccessException in LiveCycle ES2 on WebLogic 10.x.x

Problem:

If you encounter an exception of the form “com.thoughtworks.xstream.converters.reflection.ObjectAccessException” on Weblogic 10.x.x during LC ES2 operations; it’s due to JVM vendor name changes by Oracle in later releases (Oracle JRockit build R28.0.0) of JRockit.
Oracle changed JVM vendor name in this release to “Oracle” which now causes to fail the vendor check in XStream (which expects it to be “BEA”).

The solution which we confirmed and Oracle supports is to use the earlier Jrockit which still says vendor name as “BEA”. XStream keys off this.

Typical exception you would see is of the nature (Class name it reports could be different depending on the nature of the LC operation):
e.g. –
——-
Caused by: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Cannot find class com.adobe.idp.dsc.jdbc.bean.XmlDocumentInfoBean
——-

Solution/Workaround:
Workaround for now is to run an older release of JRockit(not a R28 release). Oracle JRockit Real Time 3.1.2-1.6.0.14

Later versions of LC will include a new version of XStream that will have this problem fixed.

Reference:

http://jira.codehaus.org/browse/XSTR-618?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

About Santosh Tatke

Santosh Tatke is a Sr. Support Architect at Adobe Systems. He specializes in ADEP (formerly LiveCycle) technology stack and works closely with customers, solution consultants and partners to troubleshoot, analyze and resolve technical challenges during POC, implementation, deployment or upgrade. He is a Certified LiveCycle ES2.5 Process Management Expert.
This entry was posted in Adobe LiveCycle ES2 (9.0.x) and tagged . Bookmark the permalink.

Comments are closed.