Yes, save some frustration and use mod_jk.
See my FAQ:
And check this thread for a full story line ;).
I don't have any problem using ajp13 (mod_jk). The only bad thing is that you have to specify a hard mapping between context and physical path of the application in mod_jk.conf file. As long as embeded tomcat is not reading server.xml the only way to deploy an war (ear) is to use the autodeploy feature of jboss. The problem comes when you have to make a change, because you have to redeploy the entire thing which will end up in a different directory than the original one. In this case I have edit mod_jk.conf file and restart Apache which is annoying.
Is there a workaround to force jboss to redeploy an application in the same directory?
Is there any way to deploy an application in a different directory and manage it manualy (without autodeploy feature)?
What do mean "specify a hard mapping between context and physical path of the application" as being an issue?
You have to specify the Tomcat host and deployed context name with either connector. If using mod_jk.conf is a problem just put that info in httpd.conf per the docs. you will still need your worker.properties file though and you can have more than one worker (Tomcat instance) per Apache server.
I know of no work around yet yet.
Sorry JT, I made a mistake confusing Alias with JkMount. Thanks for your help.