Windows server - Windows Server 2016 (64bit). Yes it does happen all the time.
It works perfectly with tomcat 9.0.89 , it started failing when we migrated to tomcat 9.0.108 . I would appreciate your help , if you have any leads/pointer which we should focus . Thanks, Ramdev. ________________________________ From: Mark Thomas <ma...@apache.org> Sent: Thursday, September 4, 2025 12:58 PM To: users@tomcat.apache.org <users@tomcat.apache.org> Subject: Re: Tomcat Upgrade from 9.0.89 to 9.0.108 is failing On 03/09/2025 16:08, Boddapu, Ramdev wrote: > Thanks Mark for your responce , below is the required details . Thanks that is a good start. Still need a fee more details. Which specific version of Windows server? Does this happen with every request or just some. Is there a pattern (size of file, type, etc). I suspect we are going to need a sample web application (simplest possible WAR - with source) that demonstrates the issue. Mark > > 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 <ma...@apache.org> > Sent: Wednesday, September 3, 2025 8:19 PM > To: users@tomcat.apache.org <users@tomcat.apache.org> > 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: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > 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: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org 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.
