Known issues in TeamForge connector 2.3

The following is a known issue in TeamForge connector 2.3. It has a workaround.

When the connector integrated application is removed and added again to the same project in TeamForge, connector fails with the following exception:

org.hibernate.exception.ConstraintViolationException: could not insert: [com.collabnet.ccf.ccfmaster.server.domain.ExternalApp]; nested exception is javax.persistence.PersistenceException:

org.hibernate.exception.ConstraintViolationException: could not insert: [com.collabnet.ccf.ccfmaster.server.domain.ExternalApp]

• Workaround: Delete the old external application entry created for the project from the CCF "EXTERNAL_APP" table. Connect to the CCF database and run the following query to delete the old external application entry. The old external application entry can be identified thorough the "prplid" of the integrated application enabled for the project.

  DELETE FROM “EXTERNAL_APP" WHERE (LINK_ID = 'prpl1000');