We upgraded Jira to version 5.2.9 and Fisheye from version 2.7.x to 2.10.4. However when we went to use jira for user management, we get a the error below. This despite the fact that we went to the Jira user server in Jira and added the application name and created a password, both of which we use when we try to set up Jira user management on the Fisheye side.
"Problem communicating with JIRA: java.net.ConnectException: Connection refused"
Also notice that sometimes we get the following error:
Can't put the entire error as the comment field here does not allow more than 2000 charachters.
Its possible but I was able to create full trust application links between the two applications. In fact, when I go to the "Fisheye Configuration" screen in Jira, I see that there is communication between the two as both the Crucible Project list cache and the Repository List cache were refreshed as of a few hours ago.
Also, These applications are on the same box. Although traffic for each goes comes in from the outside via two different ip addresses (and nics) they do reside on the same machine.
In the JIRA User Server, what IP address have you added? localhost and the IPv4 AND IPv6 representation of localhost? Check if you have IPv6 enabled on the server and if this is an issue. By default I've seen JIRA miss this when establishing the user management / application link.
On the Jira User Server I have tried adding the ip address of the nic we've assigned to fisheye and to whom the proper dns record points to. (Although we've put Jira and Fisheye on the same server, traffic for each comes in via separate ip's.) I've also tried with 127.0.0.1 though not the IPv6 version of localhost. We have IPv6 disabled via /etc/sysconfig/network (CentOS). The strange thing is that we are also using stash, also on the same box and had no problem using Jira as the user server there.
I'm having the exact same issue. This is a first-time install of Fisheye/Crucible, and we're trying to use our existing Jira user database. Putting in the correct details gives the exact error above - but the authentication details are then saved. Users aren't collected though, so there's nothing in the 'users' screen.
Also, clicking 're-sync' gives an alert "Error synchronising users: Problem communicating with Crowd", and clicking 'edit' shows: "Your request was unable to be processed java.lang.ArrayIndexOutOfBoundsException - -1"
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot