Re: Error in apache mod-jk logs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Loai, On 11/3/18 13:19, Loai Abdallatif wrote: > Dear Colleagues > > We installed apache with mod_jk that connected to tomcat workers on > the different machine, during monitoring the received requests we > notice the below error on mod_jk log, and after checking the worker > log we find the request received and logged in the access-log of > the worker but the main problem is Tomcat Instance is working and > running while the apache shows the below error. > > also I requested static object from Tomcat worker , and the below > error didn't appear in modjk logs > > > [Sat Nov 03 13:06:20 2018][54448:140562048997120] [warn] > ajp_get_endpoint::jk_ajp_common.c (3372): Unable to get the free > endpoint for worker worker_app1 from 1 slots [Sat Nov 03 13:06:20 > 2018][54448:140562048997120] [info] service::jk_lb_worker.c (1343): > could not get free endpoint for worker worker_app1 (0 retries) [Sat > Nov 03 13:06:20 2018][54448:140562048997120] [info] > service::jk_lb_worker.c (1650): All tomcat instances failed, no > more workers left for recovery (attempt=1, retry=1) [Sat Nov 03 > 13:06:20 2018][54448:140562048997120] [info] > service::jk_lb_worker.c (1670): All tomcat instances are busy or in > error state [Sat Nov 03 13:06:20 2018][54448:140562048997120] > [error] service::jk_lb_worker.c (1675): All tomcat instances > failed, no more workers left Are you *sure* the requests are getting through? Usually those errors mean that the request never made it to a back-end Tomcat. What kind of Apache MPM are you running (prefork, event, etc.)? What configuration do you have for MaxWorkers/MaxRequests/MaxThreads/etc. that are relevant for your MPM? What does your Tomcat configuration look like for AJP? How many back-end Tomcat servers do you have? - -chris -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlvd4dsACgkQHPApP6U8 pFgRQQ//R9MTu10PT2yiqVzFsa74ylviQOH3RTiZpudcxEfFKGdHNwcT9x49GcoN iOobXt/DD5vC8GagabIA4twtVBYT9BI8kMU2GEHByUXWM7B9JdHJVNOXWSJU5Vyr VrQg909FiisQJXwQI+wMm5iRar00abJ+b8SRZ3k5AgC2bM8ybBoDA+M3ypBNSQFx qY9LheTpt37zktYVRNf1YtJpdAKJEIGiTxvT6rFvKlPco50DeKqBZRKT3XrE/6rd Uu9VXnkzQ+1DMeI2BLd9DZzlltT28EpbpC1XHMlPTd9nHkK6ORqDQPwLLkqgjHAq hXodLQtlpfbpEtk6FgPY/OZqTQTJL1mxEX8uGOpQDXD8yyEx7ro5h6i00xAH8GfI 1+Lk70zuBBrVmeDhTHcBD+du0l9nXPLWBAs5KlXcFmxjKcGY0y6N6V7zk1fuqRJp N/b2FfdzYo3jF8uh0zjswg0MvmbLunt0KQ1BP3VZFbKFWJsvHTzkElPtQe0jYwJ6 W43KtCWMbE4Ppo1Y++0cJz1e08KQ0+6uGCgKkOb6zrUe/b8wd7qGGhtqDg0Fde4R biJYqIsobNJzs8r/aLuY1tq6CPplb+rNIUAoSmhIoL6uhqxjZwNitX5YIBWfYrW8 DApAWGXaUDhOgFteASZ9xf1203ihqFcNwtm/JVu6lS/06SNgqU4= =DMcF -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Error in apache mod-jk logs
Dear Colleagues We installed apache with mod_jk that connected to tomcat workers on the different machine, during monitoring the received requests we notice the below error on mod_jk log, and after checking the worker log we find the request received and logged in the access-log of the worker but the main problem is Tomcat Instance is working and running while the apache shows the below error. also I requested static object from Tomcat worker , and the below error didn't appear in modjk logs [Sat Nov 03 13:06:20 2018][54448:140562048997120] [warn] ajp_get_endpoint::jk_ajp_common.c (3372): Unable to get the free endpoint for worker worker_app1 from 1 slots [Sat Nov 03 13:06:20 2018][54448:140562048997120] [info] service::jk_lb_worker.c (1343): could not get free endpoint for worker worker_app1 (0 retries) [Sat Nov 03 13:06:20 2018][54448:140562048997120] [info] service::jk_lb_worker.c (1650): All tomcat instances failed, no more workers left for recovery (attempt=1, retry=1) [Sat Nov 03 13:06:20 2018][54448:140562048997120] [info] service::jk_lb_worker.c (1670): All tomcat instances are busy or in error state [Sat Nov 03 13:06:20 2018][54448:140562048997120] [error] service::jk_lb_worker.c (1675): All tomcat instances failed, no more workers left
Re: [EXTERNAL] Re: Request header too large..
On 03/11/2018 01:35, Amit Pande wrote: > Thanks Chris. Yes, I will soon send out the patch for review. Logically, I can see some hurdles for such a patch that are going to be difficult to overcome. Tomcat will process all of the received data up to the limit. It is on the subsequent read to get more data that the exception is thrown. The issue is how to determine which header is actually the problem as it may not be the one currently being read. Consider the following: ReqLine - 1024 bytes Headers - 5 * 128 bytes Header - 1 * 6*1024 bytes Headers - 5 * 128 bytes Is the problem the 6k header? The 1k request line? Has the client duplicated the block of 5 128 byte headers? Or is the request valid and Tomcat's limit too low? There is no way for Tomcat to determine where the root cause lies. The only reliable way to figure out what went wrong is for a knowledgeable system admin to look at the complete set of headers. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Request for a technical review
On 02/11/2018 16:34, Mallory Mooney wrote: > Hi everyone! > > Just wanted to check-in to see if anyone has had the chance to take a look > at the draft and leave feedback. I'll be locking things down for this one > by Thursday of next week (Nov. 8), so there's some time left if you are > still working through it. Note I suspect a number of folks aren't even looking at it because it is behind an authentication-wall (regardless of how willingly / speedily access is granted on request). Mark > > Have a great weekend! > > > On Fri, Oct 19, 2018 at 7:52 AM Mallory Mooney > wrote: > >> Hi all! >> >> Just wanted to give you an update. I am working to get things for this >> series wrapped up by the first week of November. Hopefully, that still >> gives everyone enough time to review and leave any feedback. >> >> Mallory >> >> On Fri, Oct 12, 2018 at 3:37 PM Mallory Mooney < >> mallory.moo...@datadoghq.com> wrote: >> >>> Igal, it will be available publicly once published! I don't have an >>> official publish date yet but can share that when it becomes more concrete. >>> >>> And no PRs yet, Chris! It's still in the less cool GDoc stage of the >>> review process. :) >>> >>> On Fri, Oct 12, 2018 at 1:36 PM Igal Sapir wrote: >>> On 10/12/2018 11:23 AM, Christopher Schultz wrote: > Mallory, > > On 10/12/18 13:23, Mallory Mooney wrote: >>> I definitely appreciate everyone's willingness to help out! >>> >>> Here is the link to the GDoc: >>> > https://docs.google.com/document/d/1fudlXj055nnPd-1lUoAXIS2ge8qNI56_jgUhHgKczFE/edit?usp=sharing >>> Requesting access will still be needed, but I can grant that ASAP. >>> I want to make sure I can attribute comments/suggestions to >>> specific people, so I know who to thank, and who to follow up with >>> if I need more clarification on a specific comment. Plus, it makes >>> the IT department happy. > What, no GitHub PRs? ;) > > +1 > > Is that going to be publicly available or is it a > proprietary/private/commercial guide? > > > Igal > > -chris > >>> On Thu, Oct 11, 2018 at 9:53 AM Christopher Schultz < >>> ch...@christopherschultz.net> wrote: >>> >>> Mark, >>> >>> On 10/10/18 6:00 PM, Mark Thomas wrote: >> On 10/10/18 17:44, Mallory Mooney wrote: >>> Hi all, >>> >>> I work for Datadog and am writing a guide about monitoring >>> Tomcat (with or without Datadog). I'd love to get some >>> feedback on the technical content. The project maintainers >>> we reached out to recommended we post a request here. >>> >>> Would anyone be up for that? I can send the post link to >>> someone directly. >>> >>> Appreciate your help and time! >> Why not post the link here so the community can review the >> document? >>> +1 >>> >>> There are many active community members who have an interest in >>> monitoring. I'm sure you'll get lots of feedback. >>> >>> -chris - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> -- >>> Mallory Mooney >>> Technical Content Writer >>> >> >> >> -- >> Mallory Mooney >> Technical Content Writer >> > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
