Exception: ServiceLocatorImpl has been shut down

In some cases customers have reported strange exceptions related to a ServiceLocatorImpl. In case you are affected as well, the following exception might occur in your logs:

CODE

java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_6,7,1663346084) has been shut down
at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:106) [backbone-issue-sync-3.8.0.jar:?]
at org.jvnet.hk2.internal.FactoryCreator.dispose(FactoryCreator.java:173) [backbone-issue-sync-3.8.0.jar:?]
at org.jvnet.hk2.internal.SystemDescriptor.dispose(SystemDescriptor.java:542) [backbone-issue-sync-3.8.0.jar:?]
at org.glassfish.jersey.process.internal.RequestScope$Instance.remove(RequestScope.java:532) [backbone-issue-sync-3.8.0.jar:?]
at org.glassfish.jersey.process.internal.RequestScope$Instance.release(RequestScope.java:549) [backbone-issue-sync-3.8.0.jar:?]
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:446) [backbone-issue-sync-3.8.0.jar:?]
at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:681) [backbone-issue-sync-3.8.0.jar:?]
at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:411) [backbone-issue-sync-3.8.0.jar:?]
at com.k15t.backbone.sync.appclient.DefaultRestJiraClient.executeRequest(DefaultRestJiraClient.java:281) [backbone-issue-sync-3.8.0.jar:?]
at com.k15t.backbone.commons.appclient.AbstractClient.executeRequest(AbstractClient.java:320) [backbone-issue-sync-3.8.0.jar:?]
at com.k15t.backbone.commons.appclient.AbstractClient.executeRequest(AbstractClient.java:311) [backbone-issue-sync-3.8.0.jar:?]
at com.k15t.backbone.commons.appclient.AbstractClient.executeRequest(AbstractClient.java:248) [backbone-issue-sync-3.8.0.jar:?]
at com.k15t.backbone.commons.appclient.AbstractClient.get(AbstractClient.java:156) [backbone-issue-sync-3.8.0.jar:?]
...

The actual log message might look a bit different, but should be related to the ServiceLocatorImpl.

Reason

It can have multiple reasons why this is occurring. The problem is that we can't reliably say when this error happens and also customers who have reported this issue did not observe this on a regular basis. Hence we assume this is only a temporary problem.

Troubleshooting

In order to fix this problem, we suggest to disable/enable Backbone Issue Sync from the add-ons/app administration page. If this does not help, try to uninstall and re-install Backbone Issue Sync. If this also does not help, a restart of your Jira server might help. If you are still experiencing problems after following all steps, please contact support@k15t.com.