Exception thrown invoking listener [com.pyxis.greenhopper.jira.listeners.CacheEvictionListener]

[Geoffrey Laparra]

Hello,

I'm facing an important log spamming whenever a creation edition or deletion is made on an issue.
3 voluminous errors  are throne (693 lines) :

2015-07-07 18:19:59,346 http-bio-8443-exec-8302 ERROR admin 1099x427834x1 c6f1vk 10.120.17.39,10.2.5.212 /secure/QuickCreateIssue.jspa [jira.event.issue.IssueEventListenerHandler] Exception thrown invoking listener [com.pyxis.greenhopper.jira.listeners.CacheEvictionListener] : It appears that a call has been made to BridgeServiceLocator when it is not initialised. This may indicate a plugin reloadability problem??
java.lang.IllegalStateException: It appears that a call has been made to BridgeServiceLocator when it is not initialised. This may indicate a plugin reloadability problem??
at com.atlassian.greenhopper.service.BridgeServiceLocator.getInstance(BridgeServiceLocator.java:183)
at com.pyxis.greenhopper.jira.listeners.CacheEvictionListener.evict(CacheEvictionListener.java:89)
(...)
2015-07-07 18:19:59,353 http-bio-8443-exec-8302 ERROR admin 1099x427834x1 c6f1vk 10.120.17.39,10.2.5.212 /secure/QuickCreateIssue.jspa [jira.event.issue.IssueEventListenerHandler] Exception thrown invoking listener [com.pyxis.greenhopper.jira.customfields.GreenHopperCTFIndexer] : It appears that a call has been made to BridgeServiceLocator when it is not initialised. This may indicate a plugin reloadability problem??
java.lang.IllegalStateException: It appears that a call has been made to BridgeServiceLocator when it is not initialised. This may indicate a plugin reloadability problem??
at com.atlassian.greenhopper.service.BridgeServiceLocator.getInstance(BridgeServiceLocator.java:183)
at com.pyxis.greenhopper.jira.listeners.GHSyncherListener.isLicenseValid(GHSyncherListener.java:42)
(...)
2015-07-07 18:19:59,419 http-bio-8443-exec-8302 ERROR admin 1099x427834x1 c6f1vk 10.120.17.39,10.2.5.212 /secure/QuickCreateIssue.jspa [jira.event.issue.IssueEventListenerHandler] Exception thrown invoking listener [com.pyxis.greenhopper.jira.listeners.LabelSyncher] : It appears that a call has been made to BridgeServiceLocator when it is not initialised. This may indicate a plugin reloadability problem??
java.lang.IllegalStateException: It appears that a call has been made to BridgeServiceLocator when it is not initialised. This may indicate a plugin reloadability problem??
at com.atlassian.greenhopper.service.BridgeServiceLocator.getInstance(BridgeServiceLocator.java:183)
at com.pyxis.greenhopper.jira.listeners.GHSyncherListener.isLicenseValid(GHSyncherListener.java:42)
(...)

Do you understand what my instance might be facing ?

[crf · Accepted solution]

JIRA Agile has a cross-version compatibility layer so that it can "bridge" a common internal abstraction of several services to the correct linkage in different versions, conditionally take advantage of services as they appear, and so on.  The BridgeServiceLocator is the class that helps it figure out which version of a service to use, find it, and use it.  It should be initialized automatically as part of JIRA Agile starting up, and when JIRA Agile goes away or gets upgraded, the old one is explicitly cleared out.

The error message you are seeing means one of two things has happened.  Either:

1. JIRA Agile did not come up properly and the BridgeServiceLocator for some reason was never initialized; or,
2. More likely, you have upgraded JIRA Agile, but for some reason bits and pieces of the old version of the plugin did not successfully unregister themselves even though the old BridgeServiceLocator successfully shut itself down, and those leftover bits are still trying to respond to issue events.  In the course of doing so they are trying to talk to the bridge service, and since it's gone you get the error message you reported.

Neither situation is a good one.  I would recommend restarting to see if it clears the situation up, and you might consider reporting this in a support case along with your log files to see if the reason for the failure can be identified in them.

[Geoffrey Laparra]

Thank you Chris,

I'm gonna raise this issue at Agile plugin staff.

Edit : Actually it got fixed by it-self by rebooting the server. Thanks again.