Perforce Job Integration Stopped Working
Problem
The integration stopped working. Only some of the JIRA issues are copied to Perforce as "perforce jobs".
The following appears in the atlassian-jira.log
2016-09-06 20:02:35,639 http-bio-8080-exec-272 ERROR admin 1234x3633456x2 z9kz76 12.3.456.78,910.111.22.33 /secure/QuickEditIssue.jspa [jira.event.issue.IssueEventListenerHandler] Exception thrown invoking listener [com.atlassian.jirafisheyeplugin.perforce.listener.JobUpdateListener] : Cannot cast com.atlassian.jirafisheyeplugin.perforce.PerforceManagerImpl to com.atlassian.jirafisheyeplugin.perforce.PerforceManager
java.lang.ClassCastException: Cannot cast com.atlassian.jirafisheyeplugin.perforce.PerforceManagerImpl to com.atlassian.jirafisheyeplugin.perforce.PerforceManager
at java.lang.Class.cast(Class.java:3369)
at com.atlassian.jira.plugin.OsgiServiceTrackerCacheImpl.getOsgiComponentOfType(OsgiServiceTrackerCacheImpl.java:73)
at com.atlassian.jira.ComponentManager.getOSGiComponentInstanceOfType(ComponentManager.java:713)
Diagnosis
- The configuration of the Perforce with Jira was performed as described in the Atlassian KB Create a Perforce Job when creating a JIRA issue;
There is no duplicate Fisheye plugin (jira-fisheye-plugin-xxx.jar) in the $JIRA_HOME\plugins\installed-plugins folder.
On Unix, you can check this by running the command:
ls -la $JIRA_HOME\plugins\installed-plugins
Cause
We have identified two possible causes that can cause this error:
- Corrupted plugin cache; or
- Expired password for the service account that runs the p4web process
Resolution
Cause 1:
To clear the plugin cache, it is required to restart your Jira instance.
Cause 2:
Change the password expired password for the service account that runs the p4web process. Please, refer to the Perforce documentation for further details: Passwords and P4Web and Passwords and Authorization.