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
Article Number
Applies To
RSA Product/Service Type: ALL
RSA Version/Condition: 7.0.2
Issue
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
Resolution
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
Related Articles
Getting a Request could not be handled error when trying to change the certificate store on RSA Via Lifecycle & Governance… Number of Views 'The request could not be handled' error occurs upon clicking and loading change requests from Requests > Requests in RSA … Number of Views An extra group that's non-existed in the role added while trying to add new user to the role in RSA Governance & Lifecycle Number of Views Passcode format error when trying to set a PIN thru a Cisco ASA Number of Views RSA Identity Governance and Lifecycle Review Details link ($reviewDetailURL) in Reviewer Email gets "The request could not… Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
