You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Smith, Burton" <Bu...@Williams.com> on 2014/08/25 22:14:42 UTC
[users@httpd] AJP Errors?
Can someone tell me about this error set? They show up in the Apache(mod_jk) log. They may or may not indicate that one node is down. I would like to know how to differentiate between a recoverable and a non-recoverable issue so that 24x7 support can monitor the issue. My Apache version is 2.2.15 if that helps.
[error] ajp_connect_to_endpoint::jk_ajp_common.c (1026): (103t1) cping/cpong after connecting to the backend server failed (errno=110)
[error] ajp_send_request::jk_ajp_common.c (1630): (103t1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=110)
[info] ajp_service::jk_ajp_common.c (2623): (103t1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[error] ajp_connect_to_endpoint::jk_ajp_common.c (1026): (103t1) cping/cpong after connecting to the backend server failed (errno=110)
[error] ajp_send_request::jk_ajp_common.c (1630): (103t1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=110)
[info] ajp_service::jk_ajp_common.c (2623): (103t1) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
---
Thanks,
Burton L. Smith
AW: [users@httpd] accept.lock.nn [wd-vc]
Posted by "Bremser, Kurt (AMOS Austria GmbH)" <Ku...@allianz.at>.
These are basically semaphore files for the MPM.
Delete them all once you have stopped apache for any reason.
Kurt
Newton was wrong. There is no gravity. The Earth sucks.
________________________________
Von: Gil Dawson [gildawson@gmail.com] im Auftrag von Gil Dawson [Gil@GilDawson.com]
Gesendet: Dienstag, 26. August 2014 15:14
An: users@httpd.apache.org
Betreff: [users@httpd] accept.lock.nn [wd-vc]
A number of similar files appear in the same directory as my log files, i.e., .../var/log/apache2/
accept.lock.29
accept.lock.31
accept.lock.32
accept.lock.34
accept.lock.42
accept.lock.45
accept.lock.88
accept.lock.111
accept.lock.113
They are of varying ages; the youngest is a couple of months ago, the oldest, years.
What are they, and can I safely delete them?
--Gil
AMOS Austria GmbH
1130 Wien, Hietzinger Kai 101-105
FN 365014k, Handelsgericht Wien
UID: ATU 66614737
http://www.allianz.at
********************************************************
Dieses E-Mail und allfaellig daran angeschlossene Anhaenge
enthalten Informationen, die vertraulich und
ausschliesslich fuer den (die) bezeichneten Adressaten
bestimmt sind.
Wenn Sie nicht der genannte Adressat sind, darf dieses
E-Mail samt allfaelliger Anhaenge von Ihnen weder anderen
Personen zugaenglich gemacht noch in anderer Weise
verwertet werden.
Wenn Sie nicht der beabsichtigte Empfaenger sind, bitten
wir Sie, dieses E-Mail und saemtliche angeschlossene
Anhaenge zu loeschen.
Please note: This email and any files transmitted with it is
intended only for the named recipients and may contain
confidential and/or privileged information. If you are not the
intended recipient, please do not read, copy, use or disclose
the contents of this communication to others and notify the
sender immediately. Then please delete the email and any
copies of it. Thank you.
********************************************************
[users@httpd] accept.lock.nn
Posted by Gil Dawson <Gi...@GilDawson.com>.
A number of similar files appear in the same directory as my log files, i.e., .../var/log/apache2/
accept.lock.29
accept.lock.31
accept.lock.32
accept.lock.34
accept.lock.42
accept.lock.45
accept.lock.88
accept.lock.111
accept.lock.113
They are of varying ages; the youngest is a couple of months ago, the oldest, years.
What are they, and can I safely delete them?
--Gil
Re: [users@httpd] Interpreting a GET
Posted by Sergei <se...@gmail.com>.
It is an attempt at SQL injection.
Sergei.
On 26/08/14 08:52, Gil Dawson wrote:
> This critter appears in my log sometimes:
>
> 113.161.88.70 - - [24/Aug/2014:00:29:49 -0700] "GET
> /?C=D;O=A'+union+select+char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33)+--+
> HTTP/1.1" 200 5630
>
>
> Apache apparently understands it (and returns 200 5630). I didn't
> find "char(" in RFC2616 nor a Google Search of the Apache
> documentation <http://httpd.apache.org/docs/2.2/>.
>
> Any idea what it is?
>
> --Gil
[users@httpd] Interpreting a GET
Posted by Gil Dawson <Gi...@GilDawson.com>.
This critter appears in my log sometimes:
113.161.88.70 - - [24/Aug/2014:00:29:49 -0700] "GET /?C=D;O=A'+union+select+char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33),char(38,126,33)+--+ HTTP/1.1" 200 5630
Apache apparently understands it (and returns 200 5630). I didn't find "char(" in RFC2616 nor a Google Search of the Apache documentation.
Any idea what it is?
--Gil
Re: [users@httpd] AJP Errors?
Posted by Rainer Jung <ra...@kippdata.de>.
Am 03.09.2014 um 23:23 schrieb Smith, Burton:
>> -----Original Message-----
>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>> Sent: Saturday, August 30, 2014 3:12 AM
>
>> Am 28.08.2014 um 22:39 schrieb Smith, Burton:
>>> -----Original Message-----
>>>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>>>> Sent: Tuesday, August 26, 2014 2:37 AM
>> It is possible that your linux distribution doesn't provide current mod_jk packages. But building mod_jk is very
>> simple.
>>
>> - You need to have gcc installed
>> - You need to have httpd and the httpd headers (httpd-dev?) installed
>>
>> - Then you download the source release from http://tomcat.apache.org/download-connectors.cgi. Current version
>> is 1.2.40.
>>
>> - You extract the tarball and change into sub directory "native".
>>
>> - You run "./configure --with-apxs=/path/to/my/apxs" where you replace /ath/to/my/apxs with the full path to your
>> httpd apxs (or apxs2) command
>>
>
> I'm hung up on apxs. I can't find one. Where should I look next?
Whoever provided you httpd should also provide you with the apxs script.
Most Linux distros put it into an additional httpd-devel or
apache2-devel or similar package. The script is sometimes names apxs2
instead of apxs. Often it is installed in /usr/sbin if Apche is
installed into the OS platform, or in the Apache bin directory if Apache
has a completely separate installation directory.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] AW: **SPAM?** RE: [users@httpd] AJP Errors? [wd-vc]
Posted by Daniel <df...@gmail.com>.
Wherever you have httpd installed apxs should be there too in the same
binaries directory
El 04/09/2014 07:05, "Bremser, Kurt (AMOS Austria GmbH)" <
Kurt.Bremser@allianz.at> escribió:
> apxs resides in the "bin" directory of the apache install tree (eg
> /usr/local/apache/bin)
>
> Kurt Bremser
> AMOS Austria
>
> Newton was wrong. There is no gravity. The Earth sucks.
> ________________________________________
> Von: Smith, Burton [Burton.Smith@Williams.com]
> Gesendet: Mittwoch, 3. September 2014 23:23
> An: users@httpd.apache.org
> Betreff: **SPAM?** RE: [users@httpd] AJP Errors? [wd-vc]
>
> Rainer,
>
> I got after it again.
>
> >-----Original Message-----
> >From: Rainer Jung [mailto:rainer.jung@kippdata.de]
> >Sent: Saturday, August 30, 2014 3:12 AM
>
> >Am 28.08.2014 um 22:39 schrieb Smith, Burton:
> >> -----Original Message-----
> >>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
> >>> Sent: Tuesday, August 26, 2014 2:37 AM
>
> >>> First: Since your Apache version 2.2.15 is pretty old and mod_jk had
> >>> many improvements in the last years, I suggest that you check your
> mod_jk version and consider upgrading to
> > latest.
> >
> >> I thought I would start with the upgrades. Yum pulled
> httpd-tools.x86_64 0:2.2.15-31.el6_5 without mod_ssl and
> >mod_jk. I figured out the SSL part. Can you recommend how to correct
> the JK?
> >
> >It is possible that your linux distribution doesn't provide current
> mod_jk packages. But building mod_jk is very
> >simple.
> >
> >- You need to have gcc installed
> >- You need to have httpd and the httpd headers (httpd-dev?) installed
> >
> >- Then you download the source release from
> http://tomcat.apache.org/download-connectors.cgi. Current version
> > is 1.2.40.
> >
> >- You extract the tarball and change into sub directory "native".
> >
> >- You run "./configure --with-apxs=/path/to/my/apxs" where you replace
> /ath/to/my/apxs with the full path to your
> > httpd apxs (or apxs2) command
> >
>
> I'm hung up on apxs. I can't find one. Where should I look next?
>
> ---
> Thanks,
> Burton L. Smith
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> AMOS Austria GmbH
> 1130 Wien, Hietzinger Kai 101-105
> FN 365014k, Handelsgericht Wien
> UID: ATU 66614737
>
> http://www.allianz.at
>
> ********************************************************
> Dieses E-Mail und allfaellig daran angeschlossene Anhaenge
> enthalten Informationen, die vertraulich und
> ausschliesslich fuer den (die) bezeichneten Adressaten
> bestimmt sind.
> Wenn Sie nicht der genannte Adressat sind, darf dieses
> E-Mail samt allfaelliger Anhaenge von Ihnen weder anderen
> Personen zugaenglich gemacht noch in anderer Weise
> verwertet werden.
> Wenn Sie nicht der beabsichtigte Empfaenger sind, bitten
> wir Sie, dieses E-Mail und saemtliche angeschlossene
> Anhaenge zu loeschen.
>
> Please note: This email and any files transmitted with it is
> intended only for the named recipients and may contain
> confidential and/or privileged information. If you are not the
> intended recipient, please do not read, copy, use or disclose
> the contents of this communication to others and notify the
> sender immediately. Then please delete the email and any
> copies of it. Thank you.
> ********************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
[users@httpd] AW: **SPAM?** RE: [users@httpd] AJP Errors? [wd-vc]
Posted by "Bremser, Kurt (AMOS Austria GmbH)" <Ku...@allianz.at>.
apxs resides in the "bin" directory of the apache install tree (eg /usr/local/apache/bin)
Kurt Bremser
AMOS Austria
Newton was wrong. There is no gravity. The Earth sucks.
________________________________________
Von: Smith, Burton [Burton.Smith@Williams.com]
Gesendet: Mittwoch, 3. September 2014 23:23
An: users@httpd.apache.org
Betreff: **SPAM?** RE: [users@httpd] AJP Errors? [wd-vc]
Rainer,
I got after it again.
>-----Original Message-----
>From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>Sent: Saturday, August 30, 2014 3:12 AM
>Am 28.08.2014 um 22:39 schrieb Smith, Burton:
>> -----Original Message-----
>>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>>> Sent: Tuesday, August 26, 2014 2:37 AM
>>> First: Since your Apache version 2.2.15 is pretty old and mod_jk had
>>> many improvements in the last years, I suggest that you check your mod_jk version and consider upgrading to
> latest.
>
>> I thought I would start with the upgrades. Yum pulled httpd-tools.x86_64 0:2.2.15-31.el6_5 without mod_ssl and
>mod_jk. I figured out the SSL part. Can you recommend how to correct the JK?
>
>It is possible that your linux distribution doesn't provide current mod_jk packages. But building mod_jk is very
>simple.
>
>- You need to have gcc installed
>- You need to have httpd and the httpd headers (httpd-dev?) installed
>
>- Then you download the source release from http://tomcat.apache.org/download-connectors.cgi. Current version
> is 1.2.40.
>
>- You extract the tarball and change into sub directory "native".
>
>- You run "./configure --with-apxs=/path/to/my/apxs" where you replace /ath/to/my/apxs with the full path to your
> httpd apxs (or apxs2) command
>
I'm hung up on apxs. I can't find one. Where should I look next?
---
Thanks,
Burton L. Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
AMOS Austria GmbH
1130 Wien, Hietzinger Kai 101-105
FN 365014k, Handelsgericht Wien
UID: ATU 66614737
http://www.allianz.at
********************************************************
Dieses E-Mail und allfaellig daran angeschlossene Anhaenge
enthalten Informationen, die vertraulich und
ausschliesslich fuer den (die) bezeichneten Adressaten
bestimmt sind.
Wenn Sie nicht der genannte Adressat sind, darf dieses
E-Mail samt allfaelliger Anhaenge von Ihnen weder anderen
Personen zugaenglich gemacht noch in anderer Weise
verwertet werden.
Wenn Sie nicht der beabsichtigte Empfaenger sind, bitten
wir Sie, dieses E-Mail und saemtliche angeschlossene
Anhaenge zu loeschen.
Please note: This email and any files transmitted with it is
intended only for the named recipients and may contain
confidential and/or privileged information. If you are not the
intended recipient, please do not read, copy, use or disclose
the contents of this communication to others and notify the
sender immediately. Then please delete the email and any
copies of it. Thank you.
********************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] AJP Errors?
Posted by "Smith, Burton" <Bu...@Williams.com>.
Rainer,
I got after it again.
>-----Original Message-----
>From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>Sent: Saturday, August 30, 2014 3:12 AM
>Am 28.08.2014 um 22:39 schrieb Smith, Burton:
>> -----Original Message-----
>>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>>> Sent: Tuesday, August 26, 2014 2:37 AM
>>> First: Since your Apache version 2.2.15 is pretty old and mod_jk had
>>> many improvements in the last years, I suggest that you check your mod_jk version and consider upgrading to
> latest.
>
>> I thought I would start with the upgrades. Yum pulled httpd-tools.x86_64 0:2.2.15-31.el6_5 without mod_ssl and
>mod_jk. I figured out the SSL part. Can you recommend how to correct the JK?
>
>It is possible that your linux distribution doesn't provide current mod_jk packages. But building mod_jk is very
>simple.
>
>- You need to have gcc installed
>- You need to have httpd and the httpd headers (httpd-dev?) installed
>
>- Then you download the source release from http://tomcat.apache.org/download-connectors.cgi. Current version
> is 1.2.40.
>
>- You extract the tarball and change into sub directory "native".
>
>- You run "./configure --with-apxs=/path/to/my/apxs" where you replace /ath/to/my/apxs with the full path to your
> httpd apxs (or apxs2) command
>
I'm hung up on apxs. I can't find one. Where should I look next?
---
Thanks,
Burton L. Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] AJP Errors?
Posted by Rainer Jung <ra...@kippdata.de>.
Am 28.08.2014 um 22:39 schrieb Smith, Burton:
> -----Original Message-----
>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>> Sent: Tuesday, August 26, 2014 2:37 AM
>> To: users@httpd.apache.org
>> Subject: Re: [users@httpd] AJP Errors?
>> First: Since your Apache version 2.2.15 is pretty old and mod_jk had many improvements in the last years, I
>> suggest that you check your mod_jk version and consider upgrading to latest.
>
> I thought I would start with the upgrades. Yum pulled httpd-tools.x86_64 0:2.2.15-31.el6_5 without mod_ssl and mod_jk. I figured out the SSL part. Can you recommend how to correct the JK?
It is possible that your linux distribution doesn't provide current
mod_jk packages. But building mod_jk is very simple.
- You need to have gcc installed
- You need to have httpd and the httpd headers (httpd-dev?) installed
- Then you download the source release from
http://tomcat.apache.org/download-connectors.cgi. Current version is 1.2.40.
- You extract the tarball and change into sub directory "native".
- You run "./configure --with-apxs=/path/to/my/apxs" where you replace
/ath/to/my/apxs with the full path to your httpd apxs (or apxs2) command
- You run "make"
- You copy the new module file apache-2.0/mod_jk.so to wherever you want
the module to be installed, e.g. in your httpd modules directory or
elsewhere. Reference that chosen place in your "LoadModule" httpd
directive for mod_jk.
- You add the example config files "conf/httpd-jk.conf" and
"conf/workers.properties" from the extracted tarball to your httpd and
customize it.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] AJP Errors?
Posted by "Smith, Burton" <Bu...@Williams.com>.
OK Rainer,
-----Original Message-----
>From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>Sent: Tuesday, August 26, 2014 2:37 AM
>To: users@httpd.apache.org
>Subject: Re: [users@httpd] AJP Errors?
>
>Hi Burton,
>
>Am 25.08.2014 um 22:14 schrieb Smith, Burton:
>> Can someone tell me about this error set? They show up in the
>> Apache(mod_jk) log. They may or may not indicate that one node is
>> down. I would like to know how to differentiate between a recoverable
>> and a non-recoverable issue so that 24x7 support can monitor the issue.
>> My Apache version is 2.2.15 if that helps.
>>
>> [error] ajp_send_request::jk_ajp_common.c (1630): (103t1) connecting
>> to backend failed. Tomcat is probably not started or is listening on
>> the wrong port (errno=110)
>>
>> [info] ajp_service::jk_ajp_common.c (2623): (103t1) sending request to
>> tomcat failed (recoverable), because of error during request sending
>> (attempt=1)
>>
>> [error] ajp_connect_to_endpoint::jk_ajp_common.c (1026): (103t1)
>> cping/cpong after connecting to the backend server failed (errno=110)
>>
>> [error] ajp_send_request::jk_ajp_common.c (1630): (103t1) connecting
>> to backend failed. Tomcat is probably not started or is listening on
>> the wrong port (errno=110)
>>
>> [info] ajp_service::jk_ajp_common.c (2623): (103t1) sending request to
>> tomcat failed (recoverable), because of error during request sending
>> (attempt=1)
>
>First: Since your Apache version 2.2.15 is pretty old and mod_jk had many improvements in the last years, I
> suggest that you check your mod_jk version and consider upgrading to latest.
I thought I would start with the upgrades. Yum pulled httpd-tools.x86_64 0:2.2.15-31.el6_5 without mod_ssl and mod_jk. I figured out the SSL part. Can you recommend how to correct the JK?
---
Thanks,
Burton L. Smith
Re: [users@httpd] AJP Errors?
Posted by Rainer Jung <ra...@kippdata.de>.
Hi Burton,
Am 25.08.2014 um 22:14 schrieb Smith, Burton:
> Can someone tell me about this error set? They show up in the
> Apache(mod_jk) log. They may or may not indicate that one node is
> down. I would like to know how to differentiate between a recoverable
> and a non-recoverable issue so that 24x7 support can monitor the issue.
> My Apache version is 2.2.15 if that helps.
>
> [error] ajp_connect_to_endpoint::jk_ajp_common.c (1026): (103t1)
> cping/cpong after connecting to the backend server failed (errno=110)
>
> [error] ajp_send_request::jk_ajp_common.c (1630): (103t1) connecting to
> backend failed. Tomcat is probably not started or is listening on the
> wrong port (errno=110)
>
> [info] ajp_service::jk_ajp_common.c (2623): (103t1) sending request to
> tomcat failed (recoverable), because of error during request sending
> (attempt=1)
>
> [error] ajp_connect_to_endpoint::jk_ajp_common.c (1026): (103t1)
> cping/cpong after connecting to the backend server failed (errno=110)
>
> [error] ajp_send_request::jk_ajp_common.c (1630): (103t1) connecting to
> backend failed. Tomcat is probably not started or is listening on the
> wrong port (errno=110)
>
> [info] ajp_service::jk_ajp_common.c (2623): (103t1) sending request to
> tomcat failed (recoverable), because of error during request sending
> (attempt=1)
First: Since your Apache version 2.2.15 is pretty old and mod_jk had
many improvements in the last years, I suggest that you check your
mod_jk version and consider upgrading to latest.
"recoverable" means mod_jk will send the same request again. If mod_jk
has already send part of the request to Tomcat and doesn't get back a
response or something breaks while sending the request, it decides on
the type of request and config, whether it is allowed to send the same
request again.
Consider a final request in some flow ordering stuff from a shop. mod_jk
might have send the request and an error happens when trying to read the
response. Should it then send the request again or not?
You can influence behavior using the ajp13 worker config property
recovery_options, which is a bit mask. Look for "recovery_options" in
the docs:
http://tomcat.apache.org/connectors-doc/reference/workers.html
Often value "31" (all available bits set) is appropriate, but it depends
on the application.
Using cping/cpong is nice, because it checks the connection before
mod_jk tries to send the request. So if cping/cpong fails it is clear,
that mod_jk can always retry, because Tomcat hasn't received any part of
the request yet.
The number of retries mod_jk will use for a worker is also configurable,
by default "2", property "retries" on an ajp13 worker, see the same docs
page.
If all retries fail, then it will try a fail over (for a recoverable
request), but often a failover will work on the http level, but not on
the application level, because e.g. a web session on one Tomcat doesn't
exist on the failover Tomcat (without adding session replication).
Log messages:
- a load balancer worker will log after an unrecoverable failure:
"unrecoverable error XXX, request failed. Tomcat failed in the middle
of request, we can't recover to another instance.", where XX is a number.
The message will be marked with [error]
- an AJP13 worker can log several message containing "recoverable" or
"unrecoverable". I'll list them here based on the current version. RRR
will either be the strings "recoverable" or "unrecoverable", SSS a
socket number, EEE an error number:
[info]: "(WORKERNAME) failed sending request (RRR) "
"(errno=EEE)",
[error]: "(WORKERNAME) failed sending request on a fresh connection
(RRR), socket SSS (errno=EEE)",
[error]: "(WORKERNAME) failed sending request body of size LLL (RRR), "
"socket SSS (errno=EEE)",
[error]: "(WORKERNAME) failed sending request body of size LLL (lb mode)
(RRR), socket SSS (errno=EEE)",
[error]: "(WORKERNAME) unexpected condition err=EEE recoverable=%d",
[error]: "(WORKERNAME) sending request to tomcat failed (unrecoverable),
%s (attempt=%d)",
[info]: "(WORKERNAME) sending request to tomcat failed (RRR), %s
(attempt=%d)",
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org