Is JIRA 7.5 compatible with Crucible 4.5

I am trying to add Issue trigger "Create review" but I have a message that I use too old version of Crucible.

I have the latest version of JIRA and Crucible installed.

Does anyone know about incompatibilities between JIRA 7.5 and Crucible 4.5?

2 answers

This widget could not be displayed.

Hi Michal,

Can you enable debug logging in Crucible and retry the link and provide the error message from the logs:

Starting Crucible with the command line options --debug --debug-perf will print a lot of information to Crucible's logs.

Once you turn on debug logging and restart Crucible, replicate the trigger issue and paste the log snippet from the time the issue occurred so we can see exactly what Crucible is saying.

Cheers,

Branden

I am not sure if I caught correct log snippets, but those log entries appeared  when I tried to add "Create review" trigger.

I am also attaching screenshot of the error message.

2017-09-21 11:07:14,482 DEBUG [IncrPing3 ] fisheye RepositoryHandle-acquire - acquire engine on BBBL, count=1, waited 0 ms to acquire.
2017-09-21 11:07:14,482 DEBUG [IncrPing3 ] fisheye RepositoryHandle-release - release engine on BBBL, count=0 waited 0 ms to release
2017-09-21 11:07:27,029 DEBUG [notificationManager1 ] fisheye DefaultNotificationSender-lambda$sendNotifications$0 - Processing notifications
2017-09-21 11:03:35,264 DEBUG [qtp2003463579-185 ] fisheye ProfilingServletFilter-logRequest - end request in 465ms GET /crucible/rest/applinks/3.0/status/27275dc7-8319-3584-989b-c7a0645b0098/oauth nosession 200 mem=65,370MB
2017-09-21 11:03:35,280 DEBUG [qtp2003463579-184 ] fisheye ProfilingServletFilter-logRequest - start request GET /crucible/rest/applinks/latest/applicationlink/27275dc7-8319-3584-989b-c7a0645b0098/authentication/provider nosession
2017-09-21 11:03:35,300 DEBUG [qtp2003463579-184 ] fisheye ProfilingServletFilter-logRequest - end request in 21ms GET /crucible/rest/applinks/latest/applicationlink/27275dc7-8319-3584-989b-c7a0645b0098/authentication/provider nosession 401 mem=0,791MB
2017-09-21 11:03:35,317 DEBUG [qtp2003463579-185 ] fisheye ProfilingServletFilter-logRequest - start request GET /crucible/rest/applinks/latest/manifest nosession
2017-09-21 11:03:35,330 DEBUG [qtp2003463579-185 ] fisheye ProfilingServletFilter-logRequest - end request in 13ms GET /crucible/rest/applinks/latest/manifest nosession 200 mem=0,575MB
2017-09-21 11:03:35,460 DEBUG [Resource Monitor ] fisheye SystemResourceMonitor$MonitoringTask-run - tc=126, ofd=563, mfd=4096, fm=113581960, tm=574095360
2017-09-21 11:03:41,973 DEBUG [notificationManager1 ] fisheye DefaultNotificationSender-lambda$sendNotifications$0 - Processing notifications
2017-09-21 11:03:56,977 DEBUG [notificationManager1 ] fisheye DefaultNotificationSender-lambda$sendNotifications$0 - Processing notifications
2017-09-21 11:04:10,466 DEBUG [Resource Monitor ] fisheye SystemResourceMonitor$MonitoringTask-run - tc=126, ofd=562, mfd=4096, fm=112911120, tm=574095360
2017-09-21 11:04:11,981 DEBUG [notificationManager1 ] fisheye DefaultNotificationSender-lambda$sendNotifications$0 - Processing notifications
2017-09-21 11:04:12,966 DEBUG [Resource Monitor ] fisheye SystemResourceMonitor$MonitoringTask-run - tc=125, ofd=562, mfd=4096, fm=112839664, tm=574095360
2017-09-21 11:04:14,422 DEBUG [PingerTimer ] fisheye RepositoryHandle-acquire - acquire engine on BBBL, count=1, waited 0 ms to acquire.
2017-09-21 11:04:14,422 DEBUG [PingerTimer ] fisheye RepositoryHandle-release - release engine on BBBL, count=0 waited 0 ms to release
2017-09-21 11:04:14,423 DEBUG [IncrPing3 BBBL ] fisheye RepositoryHandle-acquire - acquire engine on BBBL, count=1, waited 0 ms to acquire.
2017-09-21 11:04:14,423 DEBUG [IncrPing3 BBBL ] fisheye RepositoryStatus-setMessage - Status change [BBBL]: Contacting repository.
2017-09-21 11:04:14,423 INFO  [IncrPing3 BBBL ] fisheye BaseRepositoryScanner-ping - processing repository BBBL (BBBL)
2017-09-21 11:04:14,423 INFO  [IncrPing3 BBBL ] fisheye Svn2Scanner-doSlurpTransaction - Starting slurp of BBBL (BBBL)
2017-09-21 11:04:14,424 DEBUG [SvnExecution1 BBBL ] fisheye SvnTask$1-run - Executing (IncrPing3 BBBL) svn info -r HEAD #here was our svn server address#
2017-09-21 11:04:14,482 DEBUG [IncrPing3 BBBL ] fisheye RepositoryStatus-setMessage - Status change [BBBL]: Obtaining changeset list
2017-09-21 11:04:14,482 DEBUG [IncrPing3 BBBL ] fisheye Svn2WrapUpProcessor-process - Started wrapup processing: startRevision=4384, lastScannedCsid=4383
2017-09-21 11:04:14,482 DEBUG [IncrPing3 BBBL ] fisheye Svn2WrapUpProcessor-process - Completed wrapup processing: lastCsProcessed=-1
2017-09-21 11:04:14,482 INFO  [IncrPing3 BBBL ] fisheye BaseRepositoryScanner-ping - done slurp for repository BBBL (BBBL) time = 59 ms
2017-09-21 11:04:14,482 DEBUG [IncrPing3 BBBL ] fisheye RepositoryHandle-release - release engine on BBBL, count=0 waited 0 ms to release
2017-09-21 11:04:14,483 DEBUG [IncrPing3 ] fisheye RepositoryHandle-acquire - acquire engine on BBBL, count=1, waited 0 ms to acquire.
2017-09-21 11:04:14,483 DEBUG [IncrPing3 ] fisheye RepositoryHandle-release - release engine on BBBL, count=0 waited 0 ms to release

 JIRA-Crucible-error.png

This widget could not be displayed.

Hi Michal,

In regards to the logs we're looking for an exception such as the following:


com.atlassian.fisheye.jira.RemoteJiraException:
        at com.atlassian.fecru.plugins.jirarest.restinvoker.JiraRestInvokerImpl.invoke(JiraRestInvokerImpl.java:65)
        at com.atlassian.fecru.plugins.jirarest.restinvoker.JiraRestInvokerImpl.invokeAuthenticated(JiraRestInvokerImpl.java:28)
        at com.atlassian.fecru.plugins.jirarest.JiraIssueImpl.load(JiraIssueImpl.java:102)
        at com.atlassian.fecru.plugins.jirarest.JiraServerImpl.getIssue(JiraServerImpl.java:181)
        at com.atlassian.fisheye.jira.issue.JiraIssueServiceImpl.retrieveJiraIssue(JiraIssueServiceImpl.java:168)
        at com.atlassian.fisheye.jira.issue.JiraIssueServiceImpl.getJiraIssue(JiraIssueServiceImpl.java:96)
        at com.atlassian.fisheye.jira.issue.JiraIssueServiceImpl.getJiraIssue(JiraIssueServiceImpl.java:71)

If you don't see any exceptions on the FECRU side take a look at the atlassian-jira.log from the time you attempted to add the issue trigger to see if that provides any further clues in our investigation.

Cheers,

Branden

I'm afraid there's no RemoteJiraException int JIRA log files. :(

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...

1,492 views 10 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you