Bug 63075 - loss of connection with mod_jk
Summary: loss of connection with mod_jk
Status: RESOLVED INVALID
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: mod_jk (show other bugs)
Version: 1.2.46
Hardware: PC All
: P1 blocker (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-11 10:54 UTC by rajendra rathore
Modified: 2019-02-06 11:54 UTC (History)
0 users



Attachments
logs (645.41 KB, application/x-zip-compressed)
2019-01-11 10:54 UTC, rajendra rathore
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rajendra rathore 2019-01-11 10:54:16 UTC
Created attachment 36374 [details]
logs

Hi Team,

we are using Apache Http server with basic authentication, when we try to send some request to apache for authentication it will fail with 401 error and when we check the JK Status, we found that status was not proper means instead of 'OK' state it was 'Awaiting..'. We are facing this issue with tomcat connector 1.2.46, it worked with 1.2.43. I attached our log files for your reference, please let me know if you need anything else.
Comment 1 Rainer Jung 2019-02-06 11:54:33 UTC
First: I will close this ticket after my response, because your logs do not show any obvious indication for a bug. If you want to discuss this further, please first present your case to the users list:

  http://tomcat.apache.org/lists.html#tomcat-users

The requests with status 401 in your logs seem normal. If you eg. use basic auth, then the first request does not contain credentials and responds with 401. This triggers a popup in the browser asking for credentials and the retries the same request, in your case with the user name wcadmin. These requests sometimes for (status 200) and sometimes do not work (status 503). You mod_jk logs indicate, that when they do not work, Apache can not connect to your tomcat, maybe because it is down.

Note that you are also getting mod_jk errors during startup because of not having a correct JkShmFile. You should fix these before investigating your other problems further.

Regards,

Rainer