Cannot Edit Perforce Job Integration Settings After Migrating a JIRA Instance From One Server to Another
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Upon modifying the Perforce Job Integration (via Administration > Plugins > Enable Perforce Job Integration), a
java.lang.RuntimeExceptionis thrown.When JIRA starts up and attempts to load the Perforce properties, a
java.lang.RuntimeExceptionis thrown.
In Linux you should see:
1
2
3
4
5
6
7
8
9
10
11
12
Cause:
java.lang.RuntimeException: invalid perforce executable detected:[c:\Perforce\p4.exe]
Stack Trace:
java.lang.RuntimeException: invalid perforce executable detected:[/tools/dev/bin/p4]
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.ensurePathIsValid(ValidEnv.java:49)
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.getExecutable(ValidEnv.java:56)
at com.perforce.api.P4Process.pure_exec(P4Process.java:290)
at com.perforce.api.P4Process.exec(P4Process.java:266)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.resolveServerAddress(PerforceConfigImpl.java:199)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.createEnvironment(PerforceConfigImpl.java:129)In Windows you should see:
1
2
3
4
5
6
7
8
9
10
11
12
Cause:
java.lang.RuntimeException: invalid perforce executable detected:[/tools/dev/bin/p4]
Stack Trace:
java.lang.RuntimeException: invalid perforce executable detected:[/tools/dev/bin/p4]
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.ensurePathIsValid(ValidEnv.java:49)
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.getExecutable(ValidEnv.java:56)
at com.perforce.api.P4Process.pure_exec(P4Process.java:290)
at com.perforce.api.P4Process.exec(P4Process.java:266)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.resolveServerAddress(PerforceConfigImpl.java:199)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.createEnvironment(PerforceConfigImpl.java:129)Cause
The incorrect path is being used for the operating system. This bug is being tracked at FISH-431.
Workaround
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Shutdown the JIRA instance.
Run the following queries to remove any traces of perforce Job Integration on the database level:
1 2 3DELETE FROM propertytext WHERE id in (SELECT id FROM propertyentry WHERE PROPERTY_KEY LIKE 'fisheye.p4%'); DELETE FROM propertystring WHERE id in (SELECT id FROM propertyentry WHERE PROPERTY_KEY LIKE 'fisheye.p4%'); DELETE FROM propertyentry WHERE PROPERTY_KEY LIKE 'fisheye.p4%';ℹ️ The above SQL may need to be changed depending on the DBMS used.
Start JIRA again.
Re-configure the Perforce Job Integration and verify it is correct.
Was this helpful?