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
- Stubbing class constants with rspec and Ruby
- Downloading All The Github Repositories
- Generating entropy in the cloud
- Disabling Firefox shortcuts on OS X
- Recreating the Opscode Chef validation key
- require-rubygems.overrides and gem2deb 0.2.2
- locale errors on debian
- Creating a Debian sid emi for Eucalyptus
- LVM errors with sbuild
- munin-cgi-graph with fcgid on ubuntu lucid
Archives
What I'm Doing...
- @ScottMuc as in, the meatcloud. http://t.co/pyk67swq in reply to ScottMuc 8 hrs ago
- OH: I'm a devop and @adamhjk still hugged me. #culture 8 hrs ago
- @mr_chip Although, spread across all the regions. in reply to mr_chip 9 hrs ago
- More updates...
Posting tweet...
Powered by Twitter Tools
0 Responses to “jboss ha weirdness”