• Type: Suggestion
• Resolution: Fixed
• Fix Version/s: 2.2 M5
• Component/s: None
• Labels:

  None

1. ec2-67-202-41-102.compute-1.amazonaws.com-bamboo-elastic-agent.out

   28/Jan/2009 12:44 AM

   28 kB

   MarkC

[BAM-3301] Implement proper retry mechanism for tunnel establishment

Collapse comment: Adrian Hempel [Atlassian] added a comment - 05/Feb/2009 11:58 PM

Adrian Hempel [Atlassian] added a comment - 05/Feb/2009 11:58 PM

I've fixed the bug - The agent wasn't stopping and waiting for both the HTTP and JMS tunnels to be established - it was only waiting for one.

Expand comment: Adrian Hempel [Atlassian] added a comment - 05/Feb/2009 11:58 PM

Adrian Hempel [Atlassian] added a comment - 05/Feb/2009 11:58 PM I've fixed the bug - The agent wasn't stopping and waiting for both the HTTP and JMS tunnels to be established - it was only waiting for one.

Collapse comment: Adrian Hempel [Atlassian] added a comment - 02/Feb/2009 12:39 AM

Adrian Hempel [Atlassian] added a comment - 02/Feb/2009 12:39 AM

I haven't been able to reproduce the problem on tardigrade.

I can see the DoubleSSLSocketFactory in the stack traces, and it was at the same time that we were making all kinds of changes there, so it might have been related to that, rather than atlassian-tunnel:0.2-SNAPSHOT.

I'll put it back in after tomorrow's demo, and monitor it.

Expand comment: Adrian Hempel [Atlassian] added a comment - 02/Feb/2009 12:39 AM

Adrian Hempel [Atlassian] added a comment - 02/Feb/2009 12:39 AM I haven't been able to reproduce the problem on tardigrade. I can see the DoubleSSLSocketFactory in the stack traces, and it was at the same time that we were making all kinds of changes there, so it might have been related to that, rather than atlassian-tunnel:0.2-SNAPSHOT. I'll put it back in after tomorrow's demo, and monitor it.

Collapse comment: MarkC added a comment - 28/Jan/2009 12:44 AM, Edited by MarkC - 28/Jan/2009 12:45 AM

MarkC added a comment - 28/Jan/2009 12:44 AM - edited

Upgrading to atlassian-tunnel-0.2-SNAPSHOT (specicailly atlassian-tunnel-0.2-20090127.060311-1.jar) causes a whole bunch of java.net.ConnectException: Connection refused exceptions.

Unsure of root cause but rolling back to 0.1 works again.

See ec2-67-202-41-102.compute-1.amazonaws.com-bamboo-elastic-agent.out for full details

Expand comment: MarkC added a comment - 28/Jan/2009 12:44 AM, Edited by MarkC - 28/Jan/2009 12:45 AM

MarkC added a comment - 28/Jan/2009 12:44 AM - edited Upgrading to atlassian-tunnel-0.2-SNAPSHOT (specicailly atlassian-tunnel-0.2-20090127.060311-1.jar) causes a whole bunch of java.net.ConnectException: Connection refused exceptions. Unsure of root cause but rolling back to 0.1 works again. See ec2-67-202-41-102.compute-1.amazonaws.com-bamboo-elastic-agent.out for full details