The same configuration should work to front GlassFish 3.1.2 with Apache.
Are mappings working? Any errors in the mod_jk or server logs?
Amy
On 4/12/12 11:18 AM, Glenn Holmer wrote:
> I'm unable to get 3.1.2 fronted by Apache with the same technique we
> used for 3.1.1:
>
> asadmin create-http-listener --listenerport 8009 --listeneraddress 0.0.0.0 --defaultvs server jk-listener
> asadmin set server-config.network-config.network-listeners.network-listener.jk-listener.jk-enabled=true
>
> After doing this, we edit server-config and create a new thread pool
> called jk-thread-pool with minimum size of 5 and maximum size of 150,
> then assign this pool to the jk-listener just created.
>
> I've also tried the instructions in Amy Roh's blog:
>
> http://weblogs.java.net/blog/amyroh/archive/2012/02/15/running-glassfish-312-apache-http-server
>
> Basically, it just doesn't look like anything's happening. There's
> certainly some traffic (see attached wireshark screenshot), but clicking
> on a link to the app goes nowhere (no page view, no error message,
> nothing). The app does respond normally on port 8080.
>
> I'm getting this in the mod_jk log (machine's hostname is "shadow"):
>
> [Thu Apr 12 12:34:58 2012] ajp13 shadow 0.038683
> [Thu Apr 12 12:35:10 2012] ajp13 shadow 0.027556
> [Thu Apr 12 12:35:19 2012] ajp13 shadow 0.026036
> [Thu Apr 12 12:35:23 2012] ajp13 shadow 0.019418
> [Thu Apr 12 12:35:47 2012] ajp13 localhost 0.024984
> [Thu Apr 12 12:35:53 2012] ajp13 localhost 0.017817
> [Thu Apr 12 12:36:07 2012] ajp13 shadow 0.022193
> [Thu Apr 12 12:38:31 2012] [32129:3055422320] [info]
> ajp_send_request::jk_ajp_common.c (1496): (ajp13) all endpoints are
> disconnected, detected by connect check (1), cping (0), send (0)
> [Thu Apr 12 12:38:31 2012] ajp13 shadow 0.021329
> [Thu Apr 12 12:41:54 2012] ajp13 shadow 0.019667
>
> which looks fairly normal to me. Is there anything different about 3.1.2
> as regards fronting it with Apache?
>