You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
My remote agent suddenly become offline on the 7th of November, after working flawlessly for a while. Those are the debug steps I've taken so far. Nothing worked. I'll be grateful for some help, because now I'm a bit lost.
The error with secure connection was:
ERROR [ActiveMQ BrokerService[bamboo] Task-20] [TransportConnector] Could not accept connection from tcp://AGENT-IP:7756 : javax.net.ssl.SSLException
ERROR [ActiveMQ BrokerService[bamboo] Task-33] [TransportConnector] Could not accept connection from tcp://AGENT-IP:37703 : javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
Now without secure connection:
WARN [ActiveMQ Transport: tcp:///22.214.171.124:30445@54663] [Transport] Transport Connection to: tcp://AGENT-IP:30445 failed: java.io.EOFException
EDIT : the remote agent is now working with TCP. The workaround flag for SSL needs to be removed from the Broker client URI. Still don't know why the secure version is not working.
EDIT 2 : just tried the secure connection without the workaround flag, didn't work
EDIT 3 : it almost looks like with or without the workaround flag in secure mode (ssl://), the result is the same. Now that I've tested without the flag, it seems to me that the workaround is not effective anymore, because the error messages look the same. But I have no idea why it would stop working suddenly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.