- Restarting the the Application server is PAIN. You need to do this every time you deploy. It adds at least 30 minutes to a software iteration.
- Hot deployment of Enterprise ARchive*s simply *doesn’t work. Save your sanity and don’t even test it.
- Multiple instances of JBoss in the same machine is INSANELY difficult (allocate 13 ports for each application server x 6)
- How awful are those XML configuration files? My ports-bindings.xml is 1000s of lines long
- The logs suck. From their init.d, there isn’t a date stamp. You’ll have to check the actual logs JBoss generates if you get JBoss running.
- If you have Swing applications that use JNDI. Good luck with the firewall administration.
- Community communication happens on a PHP forum. Professional? Please.
- The Web console. Shockingly bad.
- You’re crazy to run it at as a HTTP server. You’ll be requiring mod_jk.
- Read the JBoss blogs to witness crack abuse. Quote: I love XML
- It’s a pig. JSP recompiles on a restart and all sorts of mysterious slowness for whatever stupid reason.