Getting 'Request Error : The request could not be handled' error when trying to access requests in RSA Identity Governance and Lifecycle
Originally Published: 2019-02-04
Last Modified: 2023-10-06
Article Number
000044675
Applies To
RSA Product Set: Identity Governance and Lifecycle
RSA Product/Service Type: ALL
RSA Version/Condition: 7.0.2
 
Issue
An operator requested addition and removal of access for multiple users. Some of the change requests are throwing request could not be handled error upon clicking and loading UI > Requests > Requests. The other access requests are loading okay.

The following error is observed in aveksaServer.log:
  
01/07/2019 15:30:19.560 ERROR (default task-90) [com.aveksa.gui.core.MainManager] 
com.thoughtworks.xstream.io.StreamException: : only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0... @1:1) 
at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:124) 
at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148) 
at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141) 
at com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118) 
at com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103) 
at com.thoughtworks.xstream.io.xml.XppReader.<init>(XppReader.java:63) 
at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54) 
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:913) 
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:904) 
at com.aveksa.server.core.cr.ChangeRequest.getRequestFormData(ChangeRequest.java:1915) 
at com.aveksa.gui.objects.changeRequest.GuiChangeRequest.getRequestFormData(GuiChangeRequest.java:881) 
at com.aveksa.gui.pages.changeRequest.detail.ChangeRequestDetailHelper.printAdditionalInformationSection(ChangeRequestDetailHelper.java:681) 
at com.aveksa.gui.pages.changeRequest.detail.ChangeRequestDetailHelper.printContent(ChangeRequestDetailHelper.java:167) 
at com.aveksa.gui.pages.other.detailpopup.DetailHelper.printContent(DetailHelper.java:66) 
at com.aveksa.gui.pages.changeRequest.detail.main.ChangeRequestMainPageView.printContent(ChangeRequestMainPageView.java:23) 
... 
Caused by: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0... @1:1) 
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1519) 
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395) 
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) 
at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109) 
... 67 more


As per customer, no changes has been made to the system prior to occurrence of this issue.
Cause
The issue is due to a bug with Oracle JDBC Driver which is fixed in Oracle patch 19158500. If a Clob is accessed with the JDBC driver that is exactly 8000 characters long it returns an incorrect value
 
Resolution
1. Download Oracle JDBC driver(ojdbc7.jar) from this article's attachment. This Oracle JDBC driver includes Oracle patch 19158500
2. Replace /home/oracle/wildfly-8.2.0.Final/modules/com/oracle/main/ojdbc7.jar with the Oracle JDBC driver obtained from RSA Customer Support
3. Restart WildFly application server i.e. acm restart
 
Notes
The official Oracle patch 19158500 to fix the Oracle JDBC driver error will be included in all future RSA Identity Governance and Lifecycle releases.

Related Articles

Trending Articles

Don't see what you're looking for?