Transport time out exception on Remote Agent Console

This question is in reference to Atlassian Documentation: Get help and support

I am using Bamboo Cloud. I configured a Windows Remote Agent. Agent successfully builds jobs. But I am seeing following exception continuously:

2016-04-20 11:19:49,660 WARN [ActiveMQ InactivityMonitor Worker] [FailoverTransport] Transport (https://xxx.atlassian.net:443/builds/jmsServlet) failed, attempting to automatically reconnect
org.apache.activemq.transport.InactivityIOException: Channel was inactive (no connection attempt made) for too (>30000) long: https://xxx.atlassian.net:443/builds/jmsServlet
at org.apache.activemq.transport.AbstractInactivityMonitor$1$1.run(AbstractInactivityMonitor.java:91)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 

Why is it happening? How do I fix it?

1 answer

0 votes

We have identified the root cause behind this problem and we will start rolling out a fix soon.

Is this fix in?

Not yet. You can ask for a workaround if you contact support.atlassian.com

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira Service Desk

What's new in Jira Service Desk Server: Introducing 4.0 & more - Feb 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...

45 views 0 0
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