On 24/08/17 11:43, Petr Nemecek wrote: > Hi, > > this error occurs even if I bypass IIS i.e. go directly to Tomcat. > > My request are SOAP requests, I get thet bad gateway error on the client > side, then when the processing of the request finishes I could see following > error in Tomcat/stderr. > > com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet caught throwable > javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: > java.io.IOException: An existing connection was forcibly closed by the remote > host
Looks like you need to increase the client timeout. > What is weird, that when I don't run the Tomcat as service, but just from > command line, I don't get this error. Indeed. That should have no effect. Mark > > My startup Options for Tomcat are: > > -Dcatalina.home=c:\tomcat\apache-tomcat-8.5.15-dev > -Dcatalina.base=c:\tomcat\apache-tomcat-8.5.15-dev > -Djava.io.tmpdir=c:\tomcat\apache-tomcat-8.5.15-dev\temp > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=c:\tomcat\apache-tomcat-8.5.15-dev\conf\logging.properties > -Dfile.encoding=utf-8 > -Dorg.apache.cxf.stax.allowInsecureParser=true > -Djava.rmi.server.hostname=w.x.y.z > -Dcom.sun.management.jmxremote=true > -Dcom.sun.management.jmxremote.port=8101 > -Dcom.sun.management.jmxremote.local.only=false > -Dcom.sun.management.jmxremote.authenticate=false > -Dcom.sun.management.jmxremote.ssl=false > > Regards, > Petr > > -----Original Message----- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Thursday, August 24, 2017 10:04 AM > To: Tomcat Users List <users@tomcat.apache.org> > Subject: Re: Tomcat 8.5.15/502: Bad Gateway > > On 24/08/17 08:39, Petr Nemecek wrote: >> Hello, >> >> I have a Tomcat behind IIS, and I get the 502: Bad Gateway error for long >> running requests. >> >> After some experiments I've found out, that if I use connector 8082 (see >> below), I have this problem, but when I switch to 8084 (see below), the >> problem disappears. The only difference is that proxyName, proxyPort and >> scheme are set in the first connector. >> >> Obviously I need both, to have those set and to serve the log running >> requests without error... Any idea? > > Those attributes won't make the slightest difference. > > Tomcat has no control over how long IIS gives a request to complete before > deciding to return a 502. You should look at your IIS / ISAPI configuration. > > Mark > >> >> Many thanks, >> Petr Nemecek >> >> <Connector port="8082" protocol="HTTP/1.1" >> connectionTimeout="20000" >> redirectPort="8444" >> URIEncoding="UTF-8" >> proxyName="www.xyz.eu" >> proxyPort="80" >> scheme="http" /> >> >> <Connector port="8084" protocol="HTTP/1.1" >> connectionTimeout="20000" >> redirectPort="8444" >> URIEncoding="UTF-8" /> >> >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
