000034482 - 'Unable to save Connector' error when saving a JAVA Code Based AFX connector in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jan 5, 2017Last modified by RSA Customer Support on Oct 24, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000034482
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1, 7.x
 
IssueWhen creating a JAVA Code Based AFX connector (in the user interface to go AFX > Connectors > Create Connector > Connector Template: JavaCodeBased) and importing a third party .jar file, the following error occurs while saving the changes:
 
Unable to save Connector
 


 


User-added image


The aveksaServer.log has an oracle constraint error:
 
ORA-00001: unique constraint (AVUSER.U_AFX_FILE_NAME_VERSION) violated

 

10/24/2019 15:12:59.870 WARN  (default task-20) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 1, SQLState: 23000
10/24/2019 15:12:59.871 ERROR (default task-20) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-00001: unique constraint (AVUSER.U_AFX_FILE_NAME_VERSION) violated


10/24/2019 15:12:59.901 INFO  (default task-20) [org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl] HHH000010: On release of batch it still contained JDBC statements
10/24/2019 15:12:59.902 ERROR (default task-20) [org.hibernate.internal.SessionImpl] HHH000346: Error during managed flush [could not execute statement]
10/24/2019 15:12:59.907 ERROR (default task-20) [com.aveksa.afx.server.service.AFXConnectorServiceProvider] Unable to save entity - Connector: Id[13]; Name[JDBC-connector10]; DisplayName[JDBC connector10]; Description[]; Caused by: ORA-00001: unique constraint (AVUSER.U_AFX_FILE_NAME_VERSION) violated


com.aveksa.server.db.PersistenceException: n/a
        at com.aveksa.server.db.persistence.PersistenceServiceProvider.commitTransaction(PersistenceServiceProvider.java:2742)
        at com.aveksa.server.db.persistence.PersistenceServiceProvider.commitTransaction(PersistenceServiceProvider.java:2700)
        at com.aveksa.server.db.PersistenceManager.commitTransaction(PersistenceManager.java:420)
        at com.aveksa.afx.server.service.AFXConnectorServiceProvider.saveWithFileSpec(AFXConnectorServiceProvider.java:1480)
        at com.aveksa.afx.ui.pages.connector.edit.BaseEditConnectorWizard.handleSubmit(BaseEditConnectorWizard.java:219)
        at com.aveksa.gui.pages.base.data.wizard.TabbedWizardDialogData.handleRequest(TabbedWizardDialogData.java:66)
        at com.aveksa.afx.ui.pages.connector.edit.BaseEditConnectorWizard.handleRequest(BaseEditConnectorWizard.java:125)
...
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (AVUSER.U_AFX_FILE_NAME_VERSION) violated

        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
        at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:226)
        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:59)
        at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:910)
        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1119)
        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3780)
        at oracle.jdbc.driver.T4CPreparedStatement.executeInternal(T4CPreparedStatement.java:1343)
        at oracle.jdbc.driver.OraclePreparedStatement.executeLargeUpdate(OraclePreparedStatement.java:3865)
        at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3845)
        at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1061)
        at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:537)
        at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:204)
        ... 84 more
Caused by: Error : 1, Position : 0, Sql = insert into T_AV_AFX_FILE (CHECKSUM, DESCRIPTION, DISPLAY_NAME, NAME, IS_SUPPLIED, VERSION, ID, CONTENT) values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 ), OriginalSql = insert into T_AV_AFX_FILE (CHECKSUM, DESCRIPTION, DISPLAY_NAME, NAME, IS_SUPPLIED, VERSION, ID, CONTENT) values (?, ?, ?, ?, ?, ?, ?, ?), Error Msg = ORA-00001: unique constraint (AVUSER.U_AFX_FILE_NAME_VERSION) violated

 


Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log for your specific deployment.

 
CauseThis error occurs when a third party .jar that is being uploaded is already present in the RSA Identity Governance and Lifecycle product classpath. This causes a constraint violation in the database.

In the above example, a third party .jar called mysql-connector-java-5.1.36-bin.jar is already present in the classpath.
 
ResolutionThis error may be avoided by renaming the third party .jar to avoid a file name conflict.

For example, in the above case, rename the file to some other name like mysql-connector-java-5.1.36-bin_test.jar, upload it again and save the connector to move forward.

Fore more information on this error please see the RSA Identity Governance & Lifecycle - JAVA Code Based Connector Datasheet.
 

Attachments

    Outcomes