Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,419,227
Community Members
 
Community Events
171
Community Groups

Unable to Configure Application Links (java.net.SocketException: Connection reset)

Running Bitbucket, Confluence, Jira with a reverse proxy configuration (IIS10) without any problems.

Now I added FishEye and Crucible in the same manner. Fisheye Service is reachable and working via https.

But now I'm unable to Configure Application Links (java.net.SocketException: Connection reset) to bitbucket or jira. It seemed that fisheye cannot resolve https addresses.

What do I need to configure to get it work?

2 answers

1 accepted

0 votes
Answer accepted

After deleting and reinstalling Fisheye/Crucible it's now working. The only thing I changed wass providing a valid crucible lic while setup ...

This SocketException occurs on the server side when the client closed the socket connection before the response could be returned over the socket. For example, by quitting the browser before the repsonse was retrieved. Connection reset simply means that a TCP RST was received. This happens when your peer receives data that it can't process, and there can be various reasons for that. The simplest is when you close the socket, and then write more data on the output stream. By closing the socket, you told your peer that you are done talking, and it can forget about your connection. When you send more data on that stream anyway, the peer rejects it with an RST to let you know it isn't listening.

@line hammer - Would this mean that there is a pending setup on my end? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS

Atlassian Community Events