Troubleshooting FishEye for JIRA

Troubleshooting

As of Version 2.0 the FishEye plugin depends on atlassian-p4package - have a quick look at the install guide before upgrading.

On this page:

Plugin Tab is Not Visible

If the plugin tab is not visible on the 'View Issue' or 'Browse Project' page in JIRA, check that:

1. JIRA reports the plugin as installed correctly on the Administration->Plugins page.
2. JIRA users have the 'View Version Control' permission.

Enabling Debug Logging

To enable debug logging for the plugin, update the CLASS-SPECIFIC LOGGING LEVELS section of your WEB-INF/classes/log4j.properties file by inserting the following:

log4j.category.com.atlassian.jira.ext.fisheye = DEBUG, console, filelog
log4j.additivity.com.atlassian.jira.ext.fisheye = false

..and restart JIRA.

Perforce Job Integration

See the Job Integration documentation.

Performance

Q: The FishEye issue or project tab panel takes a long time to load.

A: There are several settings on the FishEye Configuration page that can be tweaked to improve performance:

Updating a Changeset Message (SVN only)

If you've updated a the log message attached to a Subversion changeset and the result isn't showing up in FishEye or the JIRA FishEye plugin.

First you will need to rescan the revision properties in FishEye
Then you need to access the cache/statistics screen via the JIRA FishEye Configuration page in the Administration section...
...and click Flush Cache

Other FAQ

Q: How is the Crucible review tab panel populated?

A: It depends on the version of the plugin you are using:

• Prior to Version 2.3 of the plugin a review is displayed on the Crucible tab panel if (and only if) it contains a revision that is displayed on the FishEye tab panel. Having the issue key in the description will not automatically link it to the issue.
• In Version 2.3+ you can configure the Crucible tab panel to use the method described above and/or search for issue keys in the title/description of reviews.

Q: I see the following error in JIRA / my log file:

org.apache.commons.httpclient.ConnectTimeoutException

or

org.apache.commons.httpclient.SocketTimeoutException

A: To confirm that it really is FishEye / Crucible taking a long time to respond, go to the FishEye Configuration screen and update the API Connection Timeout and API Socket Timeout fields.

Then take a look at making some performance improvements.

Q: I have the following error in my log:

Could not remove old Perforce Job Update listener: ...

A: This means that JIRA could not automatically the old Perforce plugin Job Update listener from your configuration. Follow the Listeners documentation to remove it. The old listener class name is com.atlassian.jira.plugin.ext.perforce.listener.JobUpdateListener

Q: I have the following error in my log:

Exception encountered whilst trying to remove service 'Perforce Changes Indexing Service'

or

Error resolving service with name Perforce Changes Indexing Service

A: This means that JIRA could not automatically the old Perforce plugin Changes Indexing Service from your configuration. Follow the Services documentation to remove it. The service's class name is com.atlassian.jira.plugin.ext.perforce.changelists.ChangesIndexService

Q: I have the following error in my log:

Failed to update namespace of CustomField id=...

A: This means JIRA failed to upgrade your Perforce plugin data. A workaround is to delete and recreate the effected custom field (note the id in the log message) but this will cause you to lose whatever data was stored there. To properly resolve the issue, please contact Atlassian Support.

Q: I have the following error in my log:

Detected reference to Create Job Post-Function in filesystem-configured workflow 'blahblah' 
for transition 'rhubarb'. Please manually upgrade the configuration for this workflow by 
updating the post-function <arg name="class.name" /> elements containing 
'com.atlassian.jira.plugin.ext.perforce.workflow.CreateJobFunction' to the new namespace: 
'com.atlassian.jira.ext.fisheye.perforce.workflow.CreateJobFunction'.

A: The upgrade task for upgrading Perforce plugin workflows to FishEye plugin 2.0 workflows can not automatically upgrade workflows loaded from file system xml descriptors at runtime. To be upgrade them manually, locate your JIRA workflow xml files in your JIRA webapp and update the following elements:

   ...
          <post-functions>
            ...
            <function type="class">
              <arg name="class.name">com.atlassian.jira.plugin.ext.perforce.workflow.CreateJobFunction</arg>
            </function>
            ...
          </post-functions>

to:

   ...
          <post-functions>
            ...
            <function type="class">
              <arg name="class.name">com.atlassian.jira.ext.fisheye.perforce.workflow.CreateJobFunction</arg>
            </function>
            ...
          </post-functions>

Q: I have the following error in my log:

More than one old Create Job post-function was defined for workflow transition 'rhubarb' 
- they will be merged into ONE post-function under the new namespace.

A: This means that, pre-upgrade, you had more than one Create Job post-function configured for a particular workflow transition. This is typically redundant, so the upgrade process automatically merges them into one (which is placed in the position of the first Create Job post-function encountered). If you really wanted two instances of the Create Job post-function (ie. you have custom code that relies on it - two instances will not generally create two jobs) you can still manually add it after the initial upgrade. The upgrade process will not attempt to merge instances of the new version of the post-function.

Q: I have the following error in my log:

Exception encountered when attempting to storing updated workflow blahblah ...

A: There was a problem upgrading your Perforce Job-related workflow. You may restart JIRA to attempt the upgrade again. If this problem persists, contact Atlassian Support.

Q: When trying to connect to my Perforce Server, I get the following exception:

com.perforce.api.CommitException java.io.IOException: 
Perforce client error: Connect to server failed; check $P4PORT. 
TCP connect to 192.168.0.79:2128 failed. connect: 192.168.0.79:2128: WSAETIMEDOUT

A: Your Perforce server is slow to respond and has timed out. Check that you can access it remotely from the command-line using p4. Ensure that the port that your Perforce server is running on is not blocked by your firewall or anti-virus software.

Search the Perforce troubleshooting documentation for the error code WSAETIMEDOUT for more possible solutions.

Contacting the Author

If you are still stuck or think you've encountered a bug, please raise an issue in the JIRA FishEye Plugin project.

Bugs, Feature Requests & Improvements? If you've found a bug in the JIRA FishEye plugin or would like to request a new feature or improvement - please raise an issue in the JIRA FishEye Plugin project.