users@glassfish.java.net

Re: Issue with modjk configuration in Glassfish V3

From: Amy Roh <amy.roh_at_oracle.com>
Date: Thu, 23 Feb 2012 13:29:31 -0800

Which version of Apache and mod_jk are you using?

Can you try either removing "worker.worker1.connection_pool_size=10"
from the worker.properties or increasing the size?

On 2/23/12 12:35 PM, forums_at_java.net wrote:
> Hi All,
>
> We are using Glassfish 2.1.1 for a long time and is the server in
> front-faced with Apache Httpserver. So we have done the modjk
> configurations
> as mentioned and everything worked fine. Now we are in the process of
> upgrading to Glassfish v3. We have done modjk configuration by running
> following command: create-network-listener --protocol http-listener-1
> --listenerport 8009 --jkenabled true jk-connector The worker.properties
> has remain unchanged and we are using the same as used with Glassfish v2:
> worker.list=worker1 worker.worker1.port=8009
> worker.worker1.host=localhost
> worker.worker1.type=ajp13 worker.worker1.connection_pool_size=10 But
> now
> we are intermittently getting the status 500 error. We are seeing
> following
> exception in mod_jk. [Thu Feb 16 15:13:25 2012][16070:10] [warn]
> jk_ajp_common.c (3185): Unable to get the free endpoint for worker
> worker1
> from 10 slots [Thu Feb 16 15:13:25 2012][16070:10] [error] mod_jk.c
> (2612): Could not get endpoint for worker=worker1 My question is the
> same setting works perfectly for Glassfish 2.1.1 in production
> environment
> where the request load is considerably high where as in V3 we get this
> error
> in stage environment while 2 users are using the app. What has changed
> in V3
> related to mod_jk configuration? Is anything specific required to be
> tuned in
> v3? Please help Regards Arnab
>
> --
>
> [Message sent by forum member 'arnosgh']
>
> View Post: http://forums.java.net/node/883740
>
>