You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Dirk Koehler <dk...@yahoo-inc.com> on 2007/06/15 12:04:12 UTC
Unable to get the free endpoint for worker xyz from, 1 slots
Hi,
recently I'm facing an issue with the mod_jk connector (1.2.21) together
with apache 1.3.x where requests to apache are answered with 500
INTERNAL SERVER ERROR. Enabling mod_jk debug logging shows that at
exactly that time mod_jk warnings show up saying something like (after
having tomcat/apache up for some time):
[Thu Jun 14 19:49:51 2007] [19351:0000] [warn]
ajp_get_endpoint::jk_ajp_common.c (2336): Unable to get the free
endpoint for worker myworker from 1 slots
[Thu Jun 14 19:49:51 2007] [19351:0000] [info]
ajp_get_endpoint::jk_ajp_common.c (2350): can't find free endpoint
Did anybody has an any hints or a answer for me what could have caused
that issue. I was looking in the web for any hints but unfortunately was
not successful yet!
All help is pretty much appreciated
thx,
dirk
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Unable to get the free endpoint for worker xyz from, 1 slots
Posted by Tim Funk <fu...@joedog.org>.
Check the manager app and see how many ajp connections are in use. If
your "lucky" maybe tomcat is not seeing the dropped apache connections.
In which case - I forget how to fix this. (With our looking through the
docs and google first) Since you are on localhost - that is probably not
the case.
-Tim
Dirk Koehler wrote:
> Well, my server xml defines maxProcessors to be 512, apache is
> configured with MaxClients 128...
>
> <Connector port="22001" address="127.0.0.1" maxProcessors="512"
> enableLookups="false" redirectPort="8443"
> protocol="AJP/1.3" />
>
> Also mbean (Catalina:type=ThreadPool,name=jk-127.0.0.1-22001) reports
> that there are up to 512 processors...
>
> any more ideas?
>
> thx, dirk
>
> Tim Funk wrote:
>> You probably have more apache children running than connections which
>> can be accepted by tomcat. See the Connector config docs on how o up
>> them.
>>
>> -Tim
>>
>> Dirk Koehler wrote:
>>> Hi,
>>>
>>> recently I'm facing an issue with the mod_jk connector (1.2.21) together
>>> with apache 1.3.x where requests to apache are answered with 500
>>> INTERNAL SERVER ERROR. Enabling mod_jk debug logging shows that at
>>> exactly that time mod_jk warnings show up saying something like (after
>>> having tomcat/apache up for some time):
>>>
>>> [Thu Jun 14 19:49:51 2007] [19351:0000] [warn]
>>> ajp_get_endpoint::jk_ajp_common.c (2336): Unable to get the free
>>> endpoint for worker myworker from 1 slots
>>> [Thu Jun 14 19:49:51 2007] [19351:0000] [info]
>>> ajp_get_endpoint::jk_ajp_common.c (2350): can't find free endpoint
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Unable to get the free endpoint for worker xyz from, 1 slots
Posted by Dirk Koehler <dk...@yahoo-inc.com>.
Well, my server xml defines maxProcessors to be 512, apache is
configured with MaxClients 128...
<Connector port="22001" address="127.0.0.1" maxProcessors="512"
enableLookups="false" redirectPort="8443"
protocol="AJP/1.3" />
Also mbean (Catalina:type=ThreadPool,name=jk-127.0.0.1-22001) reports
that there are up to 512 processors...
any more ideas?
thx, dirk
Tim Funk wrote:
> You probably have more apache children running than connections which
> can be accepted by tomcat. See the Connector config docs on how o up
> them.
>
> -Tim
>
> Dirk Koehler wrote:
>> Hi,
>>
>> recently I'm facing an issue with the mod_jk connector (1.2.21) together
>> with apache 1.3.x where requests to apache are answered with 500
>> INTERNAL SERVER ERROR. Enabling mod_jk debug logging shows that at
>> exactly that time mod_jk warnings show up saying something like (after
>> having tomcat/apache up for some time):
>>
>> [Thu Jun 14 19:49:51 2007] [19351:0000] [warn]
>> ajp_get_endpoint::jk_ajp_common.c (2336): Unable to get the free
>> endpoint for worker myworker from 1 slots
>> [Thu Jun 14 19:49:51 2007] [19351:0000] [info]
>> ajp_get_endpoint::jk_ajp_common.c (2350): can't find free endpoint
>>
>> Did anybody has an any hints or a answer for me what could have caused
>> that issue. I was looking in the web for any hints but unfortunately was
>> not successful yet!
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Unable to get the free endpoint for worker xyz from, 1 slots
Posted by Tim Funk <fu...@joedog.org>.
You probably have more apache children running than connections which
can be accepted by tomcat. See the Connector config docs on how o up them.
-Tim
Dirk Koehler wrote:
> Hi,
>
> recently I'm facing an issue with the mod_jk connector (1.2.21) together
> with apache 1.3.x where requests to apache are answered with 500
> INTERNAL SERVER ERROR. Enabling mod_jk debug logging shows that at
> exactly that time mod_jk warnings show up saying something like (after
> having tomcat/apache up for some time):
>
> [Thu Jun 14 19:49:51 2007] [19351:0000] [warn]
> ajp_get_endpoint::jk_ajp_common.c (2336): Unable to get the free
> endpoint for worker myworker from 1 slots
> [Thu Jun 14 19:49:51 2007] [19351:0000] [info]
> ajp_get_endpoint::jk_ajp_common.c (2350): can't find free endpoint
>
> Did anybody has an any hints or a answer for me what could have caused
> that issue. I was looking in the web for any hints but unfortunately was
> not successful yet!
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Unable to get the free endpoint for worker xyz from, 1 slots
Posted by Rainer Jung <ra...@kippdata.de>.
Could you please post your configuration and maybe some more snippets
from the debug log? What is your platform?
Under *nix systems Apache 1.3 is single threaded and uses a single
backend connection tied to a process, so this situation should never happen.
How easy can you reproduce this?
Regards,
Rainer
Dirk Koehler wrote:
> Hi,
>
> recently I'm facing an issue with the mod_jk connector (1.2.21) together
> with apache 1.3.x where requests to apache are answered with 500
> INTERNAL SERVER ERROR. Enabling mod_jk debug logging shows that at
> exactly that time mod_jk warnings show up saying something like (after
> having tomcat/apache up for some time):
>
> [Thu Jun 14 19:49:51 2007] [19351:0000] [warn]
> ajp_get_endpoint::jk_ajp_common.c (2336): Unable to get the free
> endpoint for worker myworker from 1 slots
> [Thu Jun 14 19:49:51 2007] [19351:0000] [info]
> ajp_get_endpoint::jk_ajp_common.c (2350): can't find free endpoint
>
> Did anybody has an any hints or a answer for me what could have caused
> that issue. I was looking in the web for any hints but unfortunately was
> not successful yet!
>
> All help is pretty much appreciated
>
> thx,
>
> dirk
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org