Tomcat Connector issue

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Tomcat Connector issue

George Stanchev-2
We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with error=87 (0x00000057) on a 302 redirect proxied by TC connector 1.2.46. I can see the 302 response come over from TC and it looks legit. Trace logs below. Anyone else running into a similar error or perhaps some clue as to why this can be happening?



[Thu Jun 18 09:37:28.185 2020] [6060:2544] [trace] jk_tcp_socket_sendfull::jk_connect.c (1042): enter
[Thu Jun 18 09:37:28.186 2020] [6060:2544] [trace] jk_tcp_socket_sendfull::jk_connect.c (1072): exit
[Thu Jun 18 09:37:28.187 2020] [6060:2544] [trace] ajp_connection_tcp_send_message::jk_ajp_common.c (1292): exit
[Thu Jun 18 09:37:28.188 2020] [6060:2544] [debug] ajp_send_request::jk_ajp_common.c (1768): (worker-local) Statistics about invalid connections: connect check (0), cping (0), send (0)
[Thu Jun 18 09:37:28.188 2020] [6060:2544] [debug] ajp_send_request::jk_ajp_common.c (1779): (worker-local) request body to send 0 - request body to resend 0
[Thu Jun 18 09:37:28.189 2020] [6060:2544] [trace] ajp_send_request::jk_ajp_common.c (1904): exit
[Thu Jun 18 09:37:28.190 2020] [6060:2544] [trace] ajp_get_reply::jk_ajp_common.c (2201): enter
[Thu Jun 18 09:37:28.191 2020] [6060:2544] [trace] ajp_connection_tcp_get_message::jk_ajp_common.c (1325): enter
[Thu Jun 18 09:37:28.193 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1093): enter
[Thu Jun 18 09:37:28.199 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1122): exit
[Thu Jun 18 09:37:28.200 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1093): enter
[Thu Jun 18 09:37:28.202 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1122): exit
[Thu Jun 18 09:37:28.203 2020] [6060:2544] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1459): received from ajp13 pos=0 len=307 max=16384
...<response snip>...
[Thu Jun 18 09:37:28.223 2020] [6060:2544] [trace] ajp_connection_tcp_get_message::jk_ajp_common.c (1463): exit
[Thu Jun 18 09:37:28.224 2020] [6060:2544] [trace] ajp_process_callback::jk_ajp_common.c (1919): enter
[Thu Jun 18 09:37:28.225 2020] [6060:2544] [trace] ajp_unmarshal_response::jk_ajp_common.c (718): enter
[Thu Jun 18 09:37:28.226 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (736): (worker-local) status = 302
[Thu Jun 18 09:37:28.228 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (743): Number of headers is = 5
[Thu Jun 18 09:37:28.229 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[0] [Expires] = [19-Mar-1971 08:23:00 GMT]
[Thu Jun 18 09:37:28.229 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[1] [Cache-Control] = [no-store, no-cache, private, must-revalidate]
[Thu Jun 18 09:37:28.230 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[2] [Pragma] = [no-cache]
[Thu Jun 18 09:37:28.231 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[3] [Location] = [<a href="https://host/idp/login?fsid=2baf82dbd9e74657988568e2ae98ceef&continue=https%3A%2F%host%2Fworkcenter%2Ftmtrack.dll%3Fshell%3Dswc">https://host/idp/login?fsid=2baf82dbd9e74657988568e2ae98ceef&continue=https%3A%2F%host%2Fworkcenter%2Ftmtrack.dll%3Fshell%3Dswc]
[Thu Jun 18 09:37:28.232 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[4] [Content-Length] = [0]
[Thu Jun 18 09:37:28.233 2020] [6060:2544] [trace] ajp_unmarshal_response::jk_ajp_common.c (806): exit
[Thu Jun 18 09:37:28.234 2020] [6060:2544] [trace] start_response::jk_isapi_plugin.c (889): enter
[Thu Jun 18 09:37:28.235 2020] [6060:2544] [debug] start_response::jk_isapi_plugin.c (939): Starting response for URI '/idp/login' (protocol HTTP/1.1)
[Thu Jun 18 09:37:28.236 2020] [6060:2544] [debug] start_response::jk_isapi_plugin.c (1048): Not using Keep-Alive
[Thu Jun 18 09:37:28.237 2020] [6060:2544] [error] start_response::jk_isapi_plugin.c (1082): HSE_REQ_SEND_RESPONSE_HEADER failed with error=87 (0x00000057)
[Thu Jun 18 09:37:28.238 2020] [6060:2544] [trace] start_response::jk_isapi_plugin.c (1092): exit
[Thu Jun 18 09:37:28.239 2020] [6060:2544] [trace] ajp_connection_tcp_get_message::jk_ajp_common.c (1325): enter
[Thu Jun 18 09:37:28.240 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1093): enter
[Thu Jun 18 09:37:28.241 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1122): exit
[Thu Jun 18 09:37:28.242 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1093): enter
[Thu Jun 18 09:37:28.243 2020] [6060:2544] [trace] jk_tcp_socket_recvfull::jk_connect.c (1122): exit
[Thu Jun 18 09:37:28.244 2020] [6060:2544] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1459): received from ajp13 pos=0 len=2 max=16384
Reply | Threaded
Open this post in threaded view
|

Re: Tomcat Connector issue

Christopher Schultz-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

George,

On 6/22/20 17:13, George Stanchev wrote:
> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with error=87
> (0x00000057) on a 302 redirect proxied by TC connector 1.2.46.
Windows error 0x00000057 is ... "Cannot connect to printer"??? I
assume you are on Windows because you mentioned
HSE_REQ_SEND_RESPONSE_HEADER which is IIS, right?

> I can see the 302 response come over from TC and it looks legit.
> Trace logs below. Anyone else running into a similar error or
> perhaps some clue as to why this can be happening?
Did anything change recently in your environment?

> [Thu Jun 18 09:37:28.185 2020] [6060:2544] [trace]
> jk_tcp_socket_sendfull::jk_connect.c (1042): enter [Thu Jun 18
> 09:37:28.186 2020] [6060:2544] [trace]
> jk_tcp_socket_sendfull::jk_connect.c (1072): exit [Thu Jun 18
> 09:37:28.187 2020] [6060:2544] [trace]
> ajp_connection_tcp_send_message::jk_ajp_common.c (1292): exit [Thu
> Jun 18 09:37:28.188 2020] [6060:2544] [debug]
> ajp_send_request::jk_ajp_common.c (1768): (worker-local) Statistics
> about invalid connections: connect check (0), cping (0), send (0)
> [Thu Jun 18 09:37:28.188 2020] [6060:2544] [debug]
> ajp_send_request::jk_ajp_common.c (1779): (worker-local) request
> body to send 0 - request body to resend 0 [Thu Jun 18 09:37:28.189
> 2020] [6060:2544] [trace] ajp_send_request::jk_ajp_common.c (1904):
> exit [Thu Jun 18 09:37:28.190 2020] [6060:2544] [trace]
> ajp_get_reply::jk_ajp_common.c (2201): enter [Thu Jun 18
> 09:37:28.191 2020] [6060:2544] [trace]
> ajp_connection_tcp_get_message::jk_ajp_common.c (1325): enter [Thu
> Jun 18 09:37:28.193 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1093): enter [Thu Jun 18
> 09:37:28.199 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1122): exit [Thu Jun 18
> 09:37:28.200 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1093): enter [Thu Jun 18
> 09:37:28.202 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1122): exit [Thu Jun 18
> 09:37:28.203 2020] [6060:2544] [debug]
> ajp_connection_tcp_get_message::jk_ajp_common.c (1459): received
> from ajp13 pos=0 len=307 max=16384 ...<response snip>... [Thu Jun
> 18 09:37:28.223 2020] [6060:2544] [trace]
> ajp_connection_tcp_get_message::jk_ajp_common.c (1463): exit [Thu
> Jun 18 09:37:28.224 2020] [6060:2544] [trace]
> ajp_process_callback::jk_ajp_common.c (1919): enter [Thu Jun 18
> 09:37:28.225 2020] [6060:2544] [trace]
> ajp_unmarshal_response::jk_ajp_common.c (718): enter [Thu Jun 18
> 09:37:28.226 2020] [6060:2544] [debug]
> ajp_unmarshal_response::jk_ajp_common.c (736): (worker-local)
> status = 302 [Thu Jun 18 09:37:28.228 2020] [6060:2544] [debug]
> ajp_unmarshal_response::jk_ajp_common.c (743): Number of headers is
> = 5 [Thu Jun 18 09:37:28.229 2020] [6060:2544] [debug]
> ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local)
> Header[0] [Expires] = [19-Mar-1971 08:23:00 GMT] [Thu Jun 18
> 09:37:28.229 2020] [6060:2544] [debug]
> ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local)
> Header[1] [Cache-Control] = [no-store, no-cache, private,
> must-revalidate] [Thu Jun 18 09:37:28.230 2020] [6060:2544] [debug]
> ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local)
> Header[2] [Pragma] = [no-cache] [Thu Jun 18 09:37:28.231 2020]
> [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799):
> (worker-local) Header[3] [Location] =
> [https://host/idp/login?fsid=2baf82dbd9e74657988568e2ae98ceef&continue
=https%3A%2F%host%2Fworkcenter%2Ftmtrack.dll%3Fshell%3Dswc]
>
>
[Thu Jun 18 09:37:28.232 2020] [6060:2544] [debug]
ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[4]
[Content-Length] = [0]
> [Thu Jun 18 09:37:28.233 2020] [6060:2544] [trace]
> ajp_unmarshal_response::jk_ajp_common.c (806): exit [Thu Jun 18
> 09:37:28.234 2020] [6060:2544] [trace]
> start_response::jk_isapi_plugin.c (889): enter [Thu Jun 18
> 09:37:28.235 2020] [6060:2544] [debug]
> start_response::jk_isapi_plugin.c (939): Starting response for URI
> '/idp/login' (protocol HTTP/1.1) [Thu Jun 18 09:37:28.236 2020]
> [6060:2544] [debug] start_response::jk_isapi_plugin.c (1048): Not
> using Keep-Alive

Any idea why it's "Not using Keep-Alive"?

> [Thu Jun 18 09:37:28.237 2020] [6060:2544] [error]
> start_response::jk_isapi_plugin.c (1082):
> HSE_REQ_SEND_RESPONSE_HEADER failed with error=87 (0x00000057) [Thu
> Jun 18 09:37:28.238 2020] [6060:2544] [trace]
> start_response::jk_isapi_plugin.c (1092): exit [Thu Jun 18
> 09:37:28.239 2020] [6060:2544] [trace]
> ajp_connection_tcp_get_message::jk_ajp_common.c (1325): enter [Thu
> Jun 18 09:37:28.240 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1093): enter [Thu Jun 18
> 09:37:28.241 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1122): exit [Thu Jun 18
> 09:37:28.242 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1093): enter [Thu Jun 18
> 09:37:28.243 2020] [6060:2544] [trace]
> jk_tcp_socket_recvfull::jk_connect.c (1122): exit [Thu Jun 18
> 09:37:28.244 2020] [6060:2544] [debug]
> ajp_connection_tcp_get_message::jk_ajp_common.c (1459): received
> from ajp13 pos=0 len=2 max=16384

Is this reproducible?

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7yHaIACgkQHPApP6U8
pFh+9xAAgd0RvxDipkXNqDBuEo5aa5HmlEwLSOnQW0P8RpjCb8q3OwK6qeyLUMXu
iSe0fJggOhdO+P6jzLr6EutZdGXl+fvHz2aODFJypBPQGwHNqBZS4J2x1FYOCe6x
KrzxIpMPakqz87ES1LjGZLjkUk+JhHEZa3iIUR+D58su+D+DTv4RhELOcoAL1bU6
a315bthTm+R+gA2UTMJ/EQAB6Vf6ASFnxv+ArfcAnWieuhfmYN8l7daZU941bTIK
MQjaOBjh2mDL9QqgmwNzlbOLAeUItblc01zcNPbruzXE8enjPoxwAojipMghGHwy
EWenXRVtuae2s2/qmJEdpk23zpfccry0O1CNxgdDSpGuE/MIpxybuY829Lwux071
1hPMH6nM623vqox0nw1u9iRa5T6IvzZcioi9b0XGgdKP0hkS8Q2sHuJDe6WeGmuy
+uR2D2sWqpSePzVaeVJlDn06G/u8S7Cz79W7M5ZSnVSZHsuKDXoDpQV3ykj6FtBd
2vmEqEYxMUzOc3d2X8p+r2Ecr6s9AiBP27V/eWSwWhRA72vxBCAY23RdpbZlyWIf
WbRsmVTf/zuTiynZe1EvJcxCHfRfXfXY9D+XHD0Gj/igQDFw78FhnLWWBMDJ32Be
+xCHlWNs1jVAxLI3XeTAlHlnhTZFvE6bf6zDTPy4tQatx4PL/CQ=
=LlJS
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Tomcat Connector issue

markt
On 23/06/2020 16:20, Christopher Schultz wrote:
> George,
>
> On 6/22/20 17:13, George Stanchev wrote:
>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with error=87
>> (0x00000057) on a 302 redirect proxied by TC connector 1.2.46.
> Windows error 0x00000057 is ... "Cannot connect to printer"???

Not sure where you found that. 0x57 is "Invalid Parameter"

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Tomcat Connector issue

Christopher Schultz-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 6/23/20 11:32, Mark Thomas wrote:

> On 23/06/2020 16:20, Christopher Schultz wrote:
>> George,
>>
>> On 6/22/20 17:13, George Stanchev wrote:
>>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with
>>> error=87 (0x00000057) on a 302 redirect proxied by TC connector
>>> 1.2.46.
>> Windows error 0x00000057 is ... "Cannot connect to printer"???
>
> Not sure where you found that. 0x57 is "Invalid Parameter"

Yeah, it sounded weird. Searching Google for "windows 0x00000057" (at
least here in the US) gives a million pages about errors connecting to
printers, like this one which is the top-hit for me with expanded
explanation:

https://appuals.com/fix-printer-error-0x00000057/

"
Error 0x00000057 is a printer related error on Windows which does not
allow the user to add the printer. This error is usually due to
corrupt drivers previously installed and the permission issues. ...
The 1st one would delete the driver and the second method would be to
copy the driver from a working computer.
"

I don't have a "perror" program for Windows handy right now, so I just
tried Google :/

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7yIVkACgkQHPApP6U8
pFgKoBAAiPIynvL8XRjvd2UdkuCxVAdVY45zanKYd+shrMU7y+5hn8kEz3fWi0aH
Yg16uC23bGX+M9f+97voQlHdLiCPZ9S+FzXU4bBsNkEggrWSkJeAcVxY2+FJPiyF
fvpg4Zd2KJLiecm6mwAtltnOOAubfK7+unXPMsa5PPLtZJ2WJtM8/IWgr7BElVj7
BJsKjx20R9O2n9c84DsyR49XV/hkFNgERwd8DVIWNjyEjMbOA+59M/8+knr+yCNc
t37AeQ+8QAl6Zb/WfZbzp2c47TQNQzLRYmNS9+1jlNiBvGL4BCIxR9nfoNsh8lso
eZUYvHLjOl3SuwJq7uzPhQyxeR0O3fdZHj1tPnIXXPqJLg+MkN3tk/1uhiIRiFTd
p1D8CM+NqW1/fKslBgi/2J015g+a30euHA8r/g7710QrI9k0PENZHC7ZYSztV1Gf
FEqzLt+XX0rKveT2IMPGCY/H9xuRN5i+/h0JgMC+uBAALxH22/Nwl5x3cSpUMron
mQAd85JyL023VrO0qb1VbvZMs6T6MDAJdJwdbhC/N8LJp88aPI7/ymtlZGI+Qho2
LKS3y4EC5IccVIHhDiUejH401hzD3s61ZBMOUvW1tOFFyv+QrWPb5XKRsBUoO5GT
Xf5uZJNBkv/Zwz2ZcI0Qt2elNbD5FWrWhM2VLcdraQjJY2u1NnM=
=ysFf
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Tomcat Connector issue

markt
On 23/06/2020 16:35, Christopher Schultz wrote:

>
>
> On 6/23/20 11:32, Mark Thomas wrote:
>> On 23/06/2020 16:20, Christopher Schultz wrote:
>>> George,
>>>
>>> On 6/22/20 17:13, George Stanchev wrote:
>>>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with
>>>> error=87 (0x00000057) on a 302 redirect proxied by TC connector
>>>> 1.2.46.
>>> Windows error 0x00000057 is ... "Cannot connect to printer"???
>
>> Not sure where you found that. 0x57 is "Invalid Parameter"
>
> Yeah, it sounded weird. Searching Google for "windows 0x00000057" (at
> least here in the US) gives a million pages about errors connecting to
> printers, like this one which is the top-hit for me with expanded
> explanation:
>
> https://appuals.com/fix-printer-error-0x00000057/
>
> "
> Error 0x00000057 is a printer related error on Windows which does not
> allow the user to add the printer. This error is usually due to
> corrupt drivers previously installed and the permission issues. ...
> The 1st one would delete the driver and the second method would be to
> copy the driver from a working computer.
> "
>
> I don't have a "perror" program for Windows handy right now, so I just
> tried Google :/

For the archives:
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Tomcat Connector issue

George Stanchev-2
Thanks all for the responses. It is on AWS VM machine that I don't have access to. I've googed the crap of x57 but besides some Bugzilla report from Adobe that seemed unrelated nothing good comes out of Google. x57 as Mark said is bad parameter and it is a generic error meaning either the p->lpEcb->ConnID is invalid or something is wrong with the headers or their sizes. Also chunking is off so keep-alive is JK_FALSE. I can try to enable the chunking to see if I can fork the execution into the HSE_REQ_SEND_RESPONSE_HEADER_EX call on jk_isapi_plugin.c#1066 and if it would make a difference. The headers from TC on the 302 response are pretty vanilla and I cannot imagine headers+sizes are wrong which leaves p->lpEcb->ConnID. I have omitted the actual binary dump of the AJP message because it is from a customer and didn't want to disclose their hostname but I can obfuscate it and post it if we think it is related to the issue.

For now forking into the _EX call is the only idea I have to explore...

Asked to procur another VM image in case something is wrong with IIS but it is a problem for them...

Any ideas on how to even approach this are much appreciated...

George

-----Original Message-----
From: Mark Thomas <[hidden email]>
Sent: Tuesday, June 23, 2020 9:42 AM
To: [hidden email]
Subject: Re: Tomcat Connector issue

On 23/06/2020 16:35, Christopher Schultz wrote:

>
>
> On 6/23/20 11:32, Mark Thomas wrote:
>> On 23/06/2020 16:20, Christopher Schultz wrote:
>>> George,
>>>
>>> On 6/22/20 17:13, George Stanchev wrote:
>>>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with
>>>> error=87 (0x00000057) on a 302 redirect proxied by TC connector
>>>> 1.2.46.
>>> Windows error 0x00000057 is ... "Cannot connect to printer"???
>
>> Not sure where you found that. 0x57 is "Invalid Parameter"
>
> Yeah, it sounded weird. Searching Google for "windows 0x00000057" (at
> least here in the US) gives a million pages about errors connecting to
> printers, like this one which is the top-hit for me with expanded
> explanation:
>
> https://appuals.com/fix-printer-error-0x00000057/
>
> "
> Error 0x00000057 is a printer related error on Windows which does not
> allow the user to add the printer. This error is usually due to
> corrupt drivers previously installed and the permission issues. ...
> The 1st one would delete the driver and the second method would be to
> copy the driver from a working computer.
> "
>
> I don't have a "perror" program for Windows handy right now, so I just
> tried Google :/

For the archives:
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Tomcat Connector issue

George Stanchev-2
In reply to this post by markt
Is it possible something is wrong with the header values

[Thu Jun 18 09:37:28.229 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[0] [Expires] = [19-Mar-1971 08:23:00 GMT]
[Thu Jun 18 09:37:28.229 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[1] [Cache-Control] = [no-store, no-cache, private, must-revalidate]
[Thu Jun 18 09:37:28.230 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[2] [Pragma] = [no-cache]
[Thu Jun 18 09:37:28.231 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[3] [Location] = [https://host/idp/login?fsid=2baf82dbd9e74657988568e2ae98ceef&continue=https%3A%2F%2Fhost%2Fworkcenter%2Ftmtrack.dll%3Fshell%3Dswc]
[Thu Jun 18 09:37:28.232 2020] [6060:2544] [debug] ajp_unmarshal_response::jk_ajp_common.c (799): (worker-local) Header[4] [Content-Length] = [0]


This is pretty standard, I can't see anything wrong...

-----Original Message-----
From: George Stanchev
Sent: Tuesday, June 23, 2020 10:33 AM
To: [hidden email]
Subject: RE: Tomcat Connector issue

Thanks all for the responses. It is on AWS VM machine that I don't have access to. I've googed the crap of x57 but besides some Bugzilla report from Adobe that seemed unrelated nothing good comes out of Google. x57 as Mark said is bad parameter and it is a generic error meaning either the p->lpEcb->ConnID is invalid or something is wrong with the headers or their sizes. Also chunking is off so keep-alive is JK_FALSE. I can try to enable the chunking to see if I can fork the execution into the HSE_REQ_SEND_RESPONSE_HEADER_EX call on jk_isapi_plugin.c#1066 and if it would make a difference. The headers from TC on the 302 response are pretty vanilla and I cannot imagine headers+sizes are wrong which leaves p->lpEcb->ConnID. I have omitted the actual binary dump of the AJP message because it is from a customer and didn't want to disclose their hostname but I can obfuscate it and post it if we think it is related to the issue.

For now forking into the _EX call is the only idea I have to explore...

Asked to procur another VM image in case something is wrong with IIS but it is a problem for them...

Any ideas on how to even approach this are much appreciated...

George

-----Original Message-----
From: Mark Thomas <[hidden email]>
Sent: Tuesday, June 23, 2020 9:42 AM
To: [hidden email]
Subject: Re: Tomcat Connector issue

On 23/06/2020 16:35, Christopher Schultz wrote:

>
>
> On 6/23/20 11:32, Mark Thomas wrote:
>> On 23/06/2020 16:20, Christopher Schultz wrote:
>>> George,
>>>
>>> On 6/22/20 17:13, George Stanchev wrote:
>>>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with
>>>> error=87 (0x00000057) on a 302 redirect proxied by TC connector
>>>> 1.2.46.
>>> Windows error 0x00000057 is ... "Cannot connect to printer"???
>
>> Not sure where you found that. 0x57 is "Invalid Parameter"
>
> Yeah, it sounded weird. Searching Google for "windows 0x00000057" (at
> least here in the US) gives a million pages about errors connecting to
> printers, like this one which is the top-hit for me with expanded
> explanation:
>
> https://appuals.com/fix-printer-error-0x00000057/
>
> "
> Error 0x00000057 is a printer related error on Windows which does not
> allow the user to add the printer. This error is usually due to
> corrupt drivers previously installed and the permission issues. ...
> The 1st one would delete the driver and the second method would be to
> copy the driver from a working computer.
> "
>
> I don't have a "perror" program for Windows handy right now, so I just
> tried Google :/

For the archives:
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Tomcat Connector issue

George Stanchev-2
In reply to this post by George Stanchev-2
I am sorry, but any ideas how to approach this? I have eliminated the possibility that the client is dropping the connection so it must be something within IIS/Win. Switching to keep_alive=true and HSE_REQ_SEND_RESPONSE_HEADER_EX did not make a difference.

In the logs, occasionally I  see a variation:

start_response::jk_isapi_plugin.c (1082): HSE_REQ_SEND_RESPONSE_HEADER_EX failed with error=1229 (0x000004cd)

one time there was

iis_write::jk_isapi_plugin.c (1283): Vector write of chunk encoded response failed with 1229 (0x000004cd)

which means the send response headers succeeded before writing the chunk. The responses are generated in relatively good time so timeouts are ruled out...

All things point to connID being dropped/invalid but I can put a finger on anything. The only thing I that pops on Google is an old post about having to adjust responseBufferLimit=0 in IIS that might cause those errors. I think I have ruled out external firewall/intermediary dropping the connection on the client side. I know they have FIPS enabled on the Windows side but I cannot imagine that would make a difference. Calls to other virtual directories under that site do not exhibit this behavior. Interestingly the same is observed under othe OSes (Windows Server 2012) procured with their scrips...

Any help/ideas is much appreciated....

George

-----Original Message-----
From: George Stanchev <[hidden email]>
Sent: Tuesday, June 23, 2020 10:31 AM
To: Tomcat Users List <[hidden email]>
Subject: RE: Tomcat Connector issue

Thanks all for the responses. It is on AWS VM machine that I don't have access to. I've googed the crap of x57 but besides some Bugzilla report from Adobe that seemed unrelated nothing good comes out of Google. x57 as Mark said is bad parameter and it is a generic error meaning either the p->lpEcb->ConnID is invalid or something is wrong with the headers or their sizes. Also chunking is off so keep-alive is JK_FALSE. I can try to enable the chunking to see if I can fork the execution into the HSE_REQ_SEND_RESPONSE_HEADER_EX call on jk_isapi_plugin.c#1066 and if it would make a difference. The headers from TC on the 302 response are pretty vanilla and I cannot imagine headers+sizes are wrong which leaves p->lpEcb->ConnID. I have omitted the actual binary dump of the AJP message because it is from a customer and didn't want to disclose their hostname but I can obfuscate it and post it if we think it is related to the issue.

For now forking into the _EX call is the only idea I have to explore...

Asked to procur another VM image in case something is wrong with IIS but it is a problem for them...

Any ideas on how to even approach this are much appreciated...

George

-----Original Message-----
From: Mark Thomas <[hidden email]>
Sent: Tuesday, June 23, 2020 9:42 AM
To: [hidden email]
Subject: Re: Tomcat Connector issue

On 23/06/2020 16:35, Christopher Schultz wrote:

>
>
> On 6/23/20 11:32, Mark Thomas wrote:
>> On 23/06/2020 16:20, Christopher Schultz wrote:
>>> George,
>>>
>>> On 6/22/20 17:13, George Stanchev wrote:
>>>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with
>>>> error=87 (0x00000057) on a 302 redirect proxied by TC connector
>>>> 1.2.46.
>>> Windows error 0x00000057 is ... "Cannot connect to printer"???
>
>> Not sure where you found that. 0x57 is "Invalid Parameter"
>
> Yeah, it sounded weird. Searching Google for "windows 0x00000057" (at
> least here in the US) gives a million pages about errors connecting to
> printers, like this one which is the top-hit for me with expanded
> explanation:
>
> https://appuals.com/fix-printer-error-0x00000057/
>
> "
> Error 0x00000057 is a printer related error on Windows which does not
> allow the user to add the printer. This error is usually due to
> corrupt drivers previously installed and the permission issues. ...
> The 1st one would delete the driver and the second method would be to
> copy the driver from a working computer.
> "
>
> I don't have a "perror" program for Windows handy right now, so I just
> tried Google :/

For the archives:
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Tomcat Connector issue

George Stanchev-2
To give some closure to the issue, it turned out to be networking related. Still not clear how cleanup of the hosts file on the client machines fixed it but that's what happened.

Thanks to all that chimed in earlier.

George

-----Original Message-----
From: George Stanchev <[hidden email]>
Sent: Monday, June 29, 2020 9:13 AM
To: Tomcat Users List <[hidden email]>
Subject: RE: Tomcat Connector issue

I am sorry, but any ideas how to approach this? I have eliminated the possibility that the client is dropping the connection so it must be something within IIS/Win. Switching to keep_alive=true and HSE_REQ_SEND_RESPONSE_HEADER_EX did not make a difference.

In the logs, occasionally I  see a variation:

start_response::jk_isapi_plugin.c (1082): HSE_REQ_SEND_RESPONSE_HEADER_EX failed with error=1229 (0x000004cd)

one time there was

iis_write::jk_isapi_plugin.c (1283): Vector write of chunk encoded response failed with 1229 (0x000004cd)

which means the send response headers succeeded before writing the chunk. The responses are generated in relatively good time so timeouts are ruled out...

All things point to connID being dropped/invalid but I can put a finger on anything. The only thing I that pops on Google is an old post about having to adjust responseBufferLimit=0 in IIS that might cause those errors. I think I have ruled out external firewall/intermediary dropping the connection on the client side. I know they have FIPS enabled on the Windows side but I cannot imagine that would make a difference. Calls to other virtual directories under that site do not exhibit this behavior. Interestingly the same is observed under othe OSes (Windows Server 2012) procured with their scrips...

Any help/ideas is much appreciated....

George

-----Original Message-----
From: George Stanchev <[hidden email]>
Sent: Tuesday, June 23, 2020 10:31 AM
To: Tomcat Users List <[hidden email]>
Subject: RE: Tomcat Connector issue

Thanks all for the responses. It is on AWS VM machine that I don't have access to. I've googed the crap of x57 but besides some Bugzilla report from Adobe that seemed unrelated nothing good comes out of Google. x57 as Mark said is bad parameter and it is a generic error meaning either the p->lpEcb->ConnID is invalid or something is wrong with the headers or their sizes. Also chunking is off so keep-alive is JK_FALSE. I can try to enable the chunking to see if I can fork the execution into the HSE_REQ_SEND_RESPONSE_HEADER_EX call on jk_isapi_plugin.c#1066 and if it would make a difference. The headers from TC on the 302 response are pretty vanilla and I cannot imagine headers+sizes are wrong which leaves p->lpEcb->ConnID. I have omitted the actual binary dump of the AJP message because it is from a customer and didn't want to disclose their hostname but I can obfuscate it and post it if we think it is related to the issue.

For now forking into the _EX call is the only idea I have to explore...

Asked to procur another VM image in case something is wrong with IIS but it is a problem for them...

Any ideas on how to even approach this are much appreciated...

George

-----Original Message-----
From: Mark Thomas <[hidden email]>
Sent: Tuesday, June 23, 2020 9:42 AM
To: [hidden email]
Subject: Re: Tomcat Connector issue

On 23/06/2020 16:35, Christopher Schultz wrote:

>
>
> On 6/23/20 11:32, Mark Thomas wrote:
>> On 23/06/2020 16:20, Christopher Schultz wrote:
>>> George,
>>>
>>> On 6/22/20 17:13, George Stanchev wrote:
>>>> We are getting HSE_REQ_SEND_RESPONSE_HEADER failed with
>>>> error=87 (0x00000057) on a 302 redirect proxied by TC connector
>>>> 1.2.46.
>>> Windows error 0x00000057 is ... "Cannot connect to printer"???
>
>> Not sure where you found that. 0x57 is "Invalid Parameter"
>
> Yeah, it sounded weird. Searching Google for "windows 0x00000057" (at
> least here in the US) gives a million pages about errors connecting to
> printers, like this one which is the top-hit for me with expanded
> explanation:
>
> https://appuals.com/fix-printer-error-0x00000057/
>
> "
> Error 0x00000057 is a printer related error on Windows which does not
> allow the user to add the printer. This error is usually due to
> corrupt drivers previously installed and the permission issues. ...
> The 1st one would delete the driver and the second method would be to
> copy the driver from a working computer.
> "
>
> I don't have a "perror" program for Windows handy right now, so I just
> tried Google :/

For the archives:
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]