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
- 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
- Error 80070005 accessing SSIS/DTS on SQL 2008 and Server 2008
- Scripting the root password on Ubuntu 9.10 (karmic)
- Installing Chef 0.8 alpha on Ubuntu Karmic
- HP SMH On Ubuntu Karmic
Archives
What I'm Doing...
- Big weekend for @alleycat_acres, @opscode released Chef 0.8.2, and march is @SeattleRedCross month. Volunteering convergence! 1 week ago
- @caseorganic Exciting! Let me know if you could use any logistical help too. in reply to caseorganic 1 week ago
- @jtimberman because FOX is jumpy? Methinks Firefly got popular after it was cancelled. http://en.wikipedia.org/wiki/Done_the_Impossible in reply to jtimberman 1 week ago
- More updates...
Posting tweet...
Powered by Twitter Tools.
0 Responses to “jboss ha weirdness”
Leave a Reply