You are not providing us with consistent answers to the questions we are
asking. This makes it a LOT harder to help you.
When I asked you:
"Does this happen with every request or just some. Is there a pattern
(size of file, type, etc)."
You replied:
"Yes it does happen all the time."
Below you state that only larger resources are affected. You also
mention compression.
So, which is it?
Are only larger requests affected? If so, can you determine the
threshold and what is it?
Is compression a factor? Are only compressed resources affected or not?
You can help by doing / providing the following:
1. Perform a (binary) search and determine which version the problem
first appears in. At the moment we know 9.0.89 worked and 9.0.100
exhibits the issue.
2. Provide a mininal web application (WAR with source) that demonstrates
the issue.
Meanwhile, I am going to set up a test environment as I don't have any
with IIS express and see if I can reproduce the issue.
Mark
On 04/09/2025 16:35, Boddapu, Ramdev wrote:
We are currently encountering a compatibility issue between IIS and Tomcat when
using the AJP protocol. Our setup works as expected with Tomcat version 9.0.89,
including the successful delivery of large static .min.js files (e.g., >1.5
MB). However, after upgrading to Tomcat version 9.0.108, we are experiencing
failures for the same URLs. Specifically, the browser reports a
net::ERR_CONTENT_DECODING_FAILED error, and no response is received.
Interestingly, static resources smaller than approximately 6 KB are served
correctly in both Tomcat versions. This suggests that Tomcat 9.0.108 handles
smaller responses properly but may be encountering issues with larger
compressed responses.
We suspect that changes in Tomcat 9.0.108 related to compression or response
buffering may be contributing to this behavior. To help resolve this, we would
appreciate your guidance on:
1. Any known changes in Tomcat 9.0.108 that could affect AJP response
handling or compression.
2. Recommended configuration adjustments in server.xml (e.g., packetSize,
compression, MIME types).
3. IIS-level settings that may need to be updated to ensure compatibility
with Tomcat 9.0.108, particularly for large static resources.
Please let us know if further logs or diagnostics are required. We are happy to
provide additional details to assist with troubleshooting.
________________________________
From: Thomas Sörensen <[email protected]>
Sent: Thursday, September 4, 2025 4:08 PM
To: [email protected] <[email protected]>
Subject: Re: Tomcat Upgrade from 9.0.89 to 9.0.108 is failing
Hi
We had a similar issue and it was resolve by updating the isapi_redirect.dll
from 1.2.48 to 1.2.50
https://dlcdn.apache.org/tomcat/tomcat-connectors/jk/binaries/windows/<https://urldefense.com/v3/__https://dlcdn.apache.org/tomcat/tomcat-connectors/jk/binaries/windows/__;!!AI5hVGByxkJIiw!gImppIR0VVKTxfTHmKQ4iv7Dm4b3SY-5k_5b-IpSES4Oa52bE0uinqTCLHQakecfy1kvL_Ls6K_1-Z_82NwRRYowQPsu-baVlYHLYg$>
It's worth a shot.
[1467204888818_logo-sm.png]
Excosoft • Thomas Sörensen
Cell +46 (0)76-199 3184
Email [email protected]<mailto:[email protected]>
www.excosoft.se<https://urldefense.com/v3/__http://www.excosoft.se/__;!!AI5hVGByxkJIiw!gImppIR0VVKTxfTHmKQ4iv7Dm4b3SY-5k_5b-IpSES4Oa52bE0uinqTCLHQakecfy1kvL_Ls6K_1-Z_82NwRRYowQPsu-bb4XYpjUg$>
________________________________
From: Boddapu, Ramdev <[email protected]>
Sent: 03 September 2025 17:08
To: [email protected] <[email protected]>
Subject: Re: Tomcat Upgrade from 9.0.89 to 9.0.108 is failing
Thanks Mark for your responce , below is the required details .
we havent checked all version's but when we check on 9.0.100 it failed , it
worked on 9.0.89
Let me know if you have any findings , i will also try to find from which
version it started failing .
IIS - 10 express
Windows OS version - Windows server
IIS version - 10
ISAPI redirector version - 1.2.48
ISAPI redirector config?
````
extension_uri=/myproject/isapi_redirect.dll
log_file=C:/iis/isapi/isapi_redirect.log
log_level=info
worker_file=C:/iis/isapi/workers.properties
worker_mount_file=C:/iis/isapi/uriworkermap.properties
````
````
worker.list=ag_loadbalancer,status
worker.ag-host1-node1.type = ajp13
worker.ag-host1-node1.host = tomcat-host
worker.ag-host1-node1.port = 8109
worker.ag-host1-node1.retries = 3
worker.ag-host1-node1.recovery_options = 16
worker.ag-host1-node1.secret=secretTest1
# Define worker list for ag load balancer
worker.ag_loadbalancer.type = lb
worker.ag_loadbalancer.balance_workers =ag-host1-node1
worker.ag_loadbalancer.sticky_session = false
worker.ag_loadbalancer.retries = 3
# Define the status
worker.status.type = status
````
AJP connector config?
<Connector protocol="AJP/1.3"
address="0.0.0.0"
port="8109"
redirectPort="8443"
secretRequired="true"
secret="secretTest1"
allowedRequestAttributesPattern=".*" />
Thanks,
Ramdev.
________________________________
From: Mark Thomas <[email protected]>
Sent: Wednesday, September 3, 2025 8:19 PM
To: [email protected] <[email protected]>
Subject: Re: Tomcat Upgrade from 9.0.89 to 9.0.108 is failing
Windows OS version?
IIS version?
ISAPI redirector version?
ISAPI redirector config?
AJP connector config?
Does this happen on all connections or just some connections?
Which version of Tomcat does this start with? You will need to perform a
(I suggest binary) search from 9.0.89 to 9.0.108 to find out the last
version this worked / the first version this failed.
Mark
On 03/09/2025 15:44, Boddapu, Ramdev wrote:
We have setup with IIS -> tomcat(9.0.89) with AJP , this works perfectly . But
when we upgraded tomcat to 9.0.108 it is failing with below error .
03-Sep-2025 15:03:14.392 FINE [ajp-nio-0.0.0.0-8109-exec-4]
org.apache.coyote.AbstractProcessor.setErrorState Error state
[CLOSE_CONNECTION_NOW] reported while processing request
java.io.EOFException
at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1385)
at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1336)
at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1243)
at org.apache.coyote.ajp.AjpProcessor.read(AjpProcessor.java:1194)
at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:560)
at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:349)
at
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:935)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1826)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1189)
at
org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:658)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
at java.base/java.lang.Thread.run(Thread.java:834)
Thanks , any help is apricated .
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
