For what it's worth, I have found mod_jk to be a little flakey at times.
If you don't need to rely on it for load balancing, then simply using mod_rewrite/mod_proxy might save you some hassles.
As for Jboss 4.x/jdk1.5, if I were planning a new deployment I might consider starting out with that target, but have a 1.4.2 JVM or two as backup.
Also, we've found that building Jboss from source against your target VM(s) can often help catch problems early.
In case you're curious, in production we currently use Apache 1.3.31/Jboss-3.2.3/Jetty-4.2.20.
IBM 1.3.1 SR7P on AIX 4.3, 5.x (32-bit and 64-bit).
IBM 1.4.1 SR2 on Redhat ES 2.1.
For Apache with JBoss/Tomcat, stay with mod_jk1.2.x. So go with mod_jk1.2.6.
There are some new connectors coming over the next few months. But the supported connector currently for Apache is mod_jk1.2.x
Sounds good, I'll probably go ahead and give the Jboss 4.x/ jdk1.5 a try. As for the security side of things, are there any security concerns with having Jboss on the web server with Apache/Tomcat?
Thanks for the info!
One more question in addition to the security one from above. Is there any documentation that talks about the actual hardware system requirements/recommendations? Is there any benefit to having multi-processor machines or just having multiple single proc machines in the clustered environment? Also RAM recommendations in a production environment? Thanks for any insight!