Exception during aggregation. Reason: java.lang.RuntimeException: sailpoint.connector.ConnectorException: org/jaxen/VariableContext after upgrade to 8.4P2

Hi Team,

After upgrade from 8.3P3 to 8.4P2, JDBC connector for Oracle DB, is failling with error:

Exception during aggregation. Reason: java.lang.RuntimeException: sailpoint.connector.ConnectorException: org/jaxen/VariableContext

I can see in release doc that jaxen lib is upgraded in 8.4 Release:

CONSEALINK3274
Jaxen library upgraded to a compatible version for supporting JDK 11```

has anyone faced this issue? if yes any advice?

Hi @dheerajk27,

Is org.jaxen being referenced from a build map rule?

Hi @paul_hilchey ,

Thanks for the reply.

There is no buildMap rule we are using, though we are using creation/Customisation and mergeMap rule but we have not user org.jaxen in any of the rules explicitly.

Hi @dheerajk27,

Have you added the ojdbc10 under WEB-INF/lib ?

Hi @sarvanmarri ,

I see ojdbc11 jar in WEB-INF/lib:

-rw-r–r–. 1 tomcat tomcat 5173200 Apr 30 09:42 ojdbc11.jar

image

Dear @dheerajk27

Please check if you have multi version file at lib folder.
WEB-INF/lib
try to download new ojdbc(ojdbc8.jar and ojdbc11.jar) driver check whether that makes any difference

  • Copy the downloaded jar file into this WEB-INF/lib directory.
  • Restart your IdentityIQ application server.

Jaxen is an XPath processor.
I’m not seeing how it is coming in to play with the JDBC connector.

1 Like

Hi All,

I created a sailpoint support case and being advised to add below entry to application.xml, based on KB Article: Support Articles - [IdentityIQ] Error when rule sends an email: "Velocity is not initialized correctly" - Customer Support , which fixed the issue.

<entry key="load-by-sysclassloader">
  <value>
    <List>
      <String>org.jaxen</String>
    </List>
  </value>
</entry>

Hi Team,

The issue was that i was using Dom4J liberary to create an xmlPayLoad in my customiation rule, which internally uses Jaxen library to create xPath. In 8.4 Jaxen liberary is removed as it is no longer being used by IdentityIQ core code as per Support team, causing the error.

I fixed it by replacing Dom4j with standared java library such as javax.xml.parsers.DocumentBuilder, org.w3c.dom.Document, and javax.xml.transform.