java.lang.IllegalStateException - ApplicationLink with id '12345a67-bcd8-9012-efg3-4hij5k6lmn7o' not found
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
This error is thrown when, for example, you try to delete an Application Link in Fisheye:
1
2
3
4
5
2011-11-21 01:39:17,201 INFO [btpool0-475 ] fisheye.app TotalityFilter-logExceptionDetails - Exception "ApplicationLink with id '12345a67-bcd8-9012-efg3-4hij5k6lmn7o' not found!" (java.lang.IllegalStateException) while processing "/WEB-INF/jsp/crucible/review/monolithic/review.jsp" (Referer:"null")
java.lang.IllegalStateException: ApplicationLink with id '12345a67-bcd8-9012-efg3-4hij5k6lmn7o' not found!
at com.atlassian.applinks.core.DefaultEntityLinkService.getStoredEntityLinks(DefaultEntityLinkService.java:407)
at com.atlassian.applinks.core.DefaultEntityLinkService.getEntityLinksForKey(DefaultEntityLinkService.java:518)
at com.atlassian.applinks.core.DefaultEntityLinkService.getEntityLinks(DefaultEntityLinkService.java:533)
Cause:
The Application Link configuration inside $FISHEYE_INST/config.xml got messed up in someway.
Resolution:
Shutdown the Fisheye instance;
Create a backup of the file $FISHEYE_INST/config.xml, for safety;
Open the original $FISHEYE_INST/config.xml with a text editor;
Delete all <trustedApplication> elements and their inner elements. More than one may exist. They're listed after the element </currentApplication> and before the element <check-for-updates/>. It should look like:
</currentApplication><check-for-updates/>If running Fisheye/Crucible 3.0.x or older:
Delete all the <property> elements (except the one related to the UPM plugin as it's not related to Application Links) found inside the <properties> element, so it looks like:
<properties><property name="com.atlassian.upm.log.PluginSettingsAuditLogService:log:upm_audit_log" value="<the_property_value>"/></properties>Save and close the file
If running Fisheye/Crucible 3.1.x or newer:
Application Links properties are now stored in the database (see FE-4754).
Connect to your database and run the following query:
1DELETE from cru_repository_property WHERE cru_property_name LIKE '%applink%' OR cru_property_name LIKE '%oauth%';Commit changes and disconnect from your database.
Start the Fisheye instance again.
Make sure that no Application Link to Fisheye exist in the other application you're trying to integrate with Fisheye (e.g., JIRA).
Re-create the Application Link from scratch in both sides, following this document (if JIRA is the other application in question).
Was this helpful?