I am having an issue with getting a remote bamboo agent to connect to the main server due to a dns resolving issue.
The wrapper has the following config:
But looking at the log file it fails because:
INFO | jvm 1 | 2012/01/24 00:49:07 | 2012-01-24 00:49:07,539 ERROR [ActiveMQ Task] [FailoverTransport] Failed to connect to transport after: 10 attempt(s)
INFO | jvm 1 | 2012/01/24 00:49:07 | 2012-01-24 00:49:07,539 WARN [Thread-1] [BambooJmsProxyFactoryBean] Exception when running afterPropertiesSet
INFO | jvm 1 | 2012/01/24 00:49:07 | javax.jms.JMSException: THRALL.metech.com.au
The problem here is that THRALL.metech.com.au does not resolve, only THRALL or THRALL.development.metech.com.au.
I am not sure where it is getting the first resolution from.
I have tried setting some properties in bamboo-agent.cfg.xml to force the name
but the log still shows it using tcp://THRALL.metech.com.au for some reason:
INFO | jvm 1 | 2012/01/24 00:44:52 | 2012-01-24 00:44:51,990 INFO [Thread-1] [BambooActiveMQConnectionFactory] Setting broker URL to 'failover:(tcp://THRALL.metech.com.au:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10'
INFO | jvm 1 | 2012/01/24 00:44:52 | 2012-01-24 00:44:52,178 INFO [Thread-1] [BambooActiveMQConnectionFactory] Setting broker URL to 'failover:(tcp://THRALL.metech.com.au:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10'
I've set the DNS resolution options in the windows TCP/IP settings, and looked at this page which outlines the problem:
Following it's suggestion (both links goto the same page) i updated the general page config to use the fully qualified domain but it still doesn't work.
(Sorry about the formatting, it seems to have removed all the new line characters)
Wow, Thanks. I had no idea that setting was on the main server. I wonder why it would have automatically set it to that? During the install?
No matter, with 'bamboo.jms.broker.client.uri' and 'bamboo.jms.broker.uri' set correctly it works fine.
(I did not set bamboo.jms.broker.client.uri, does that matter?)
As a bonus comment - I had a similar issue on our Bamboo server where we used the hostname in the server's bamboo.cfg.xml file but the server could not resolve it, so didn't bind to any IP. Adding an entry to the hosts file so it resolved fixed the problem (I'm sure DNS would have worked too).
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot