I don’t know enough about jboss to make an intelligent keyword filled post about this, but I wanted to note that while troubleshooting jboss ha-jndi jms crap, make sure that telneting to port 1099 produces an fqdn. on a couple servers /etc/hosts had a different hostname portion of the fqdn than the hostname alias, and this silently broke JMS. Telneting to 1099 revealed this, or at least, indicated it was dns related as working boxes were giving an fqdn while non working boxes weren’t. I think jgroups isn’t friendly with dns over all.
Recent Posts
- Joining Opscode
- Dependant Paradigms
- Amazon ELB requires CRLF for HTTP Requests
- an evening with Munin graph aggregation
- Setting a permanent Windows Hostname on EC2
- Configuration Management vs Meatcloud: 5 reasons CM wins
- Moar unofficial chef 0.7.16.2
- Got recursion not available and Cisco SSL VPN
- Chef 0.7.16wt1 fork and more 0.8 alpha notes
- knife, or, my tool is actually a library
Archives
What I'm Doing...
- I'm at Black Rock City (Open Playa, Black Rock Desert, Gerlach). http://4sq.com/aMlp4y 1 week ago
- The Suburban is whole again with a new ignition coil, control module, and plug wires. Now, napping in Bend. 1 week ago
- Road trip challenge one: roadside timing chain replacement. Go! 1 week ago
- More updates...
Posting tweet...
Powered by Twitter Tools.
0 Responses to “jboss ha weirdness”