Details
-
Bug
-
Resolution: Fixed
-
Low
-
2.4.4
-
None
Description
When I do an upgrade from JIRA 4.2.x (non-ual) to 4.x (ual) for fisheye config that uses anonymous access, I get the following style of exceptions:
2011-02-03 14:39:24,806 main ERROR [com.atlassian.jirafisheyeplugin.FishEyeManagerImpl] Error retrieving repositories for 'http://localhost:8060/' java.io.IOException: The application link with id 'null' was not found for instance 'FishEyeInstanceImpl[id=0,name=0,isCru=true,isCruStandalone=false,url=http://localhost:8060/,apiUrl=http://localhost:8060/,charset=<null>,username=<null>,basicHttpAuthUsername=<null>,basicHttpAuthPassword=<null>,socketTimeout=-1,connectionTimeout=-1,applicationId=<null>,hasBeenInitialised=true]' at com.atlassian.jirafisheyeplugin.rest.fisheye.FishEyeRestApiManagerImpl.callFisheye(FishEyeRestApiManagerImpl.java:128) at com.atlassian.jirafisheyeplugin.rest.fisheye.FishEyeRestApiManagerImpl.callFisheye(FishEyeRestApiManagerImpl.java:118) at com.atlassian.jirafisheyeplugin.FishEyeManagerImpl.getRepositories(FishEyeManagerImpl.java:126) at com.atlassian.jirafisheyeplugin.FishEyeManagerImpl.updateInstanceRepositories(FishEyeManagerImpl.java:268) at com.atlassian.jirafisheyeplugin.FishEyeManagerImpl.refresh(FishEyeManagerImpl.java:287) at com.atlassian.jirafisheyeplugin.config.RefreshManager.refreshAll(RefreshManager.java:86) at com.atlassian.jirafisheyeplugin.config.RefreshManager.onStart(RefreshManager.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:60) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1.execute(AsynchronousAbleEventDispatcher.java:28) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:56) at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:151) at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:70) at com.atlassian.multitenant.event.DefaultPeeringEventPublisherManager.publish(DefaultPeeringEventPublisherManager.java:17) at com.atlassian.multitenant.event.PeeringEventPublisher.publish(PeeringEventPublisher.java:23) at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:84) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:305) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:237) at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:61) at com.atlassian.jira.upgrade.ConsistencyLauncher.start(ConsistencyLauncher.java:39) at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:36) at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:50) at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:45) at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.get(MultiTenantComponentMapImpl.java:121) at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.onTenantStart(MultiTenantComponentMapImpl.java:165) at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:134) at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:131) at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForEachListener(DefaultMultiTenantManager.java:256) at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startTenant(DefaultMultiTenantManager.java:130)
It does not appear to cause any user visible problems (all the applinks are created and the changesets/reviews are there) its just some huge exceptions in the logs.