6 Replies Latest reply on Apr 18, 2020 12:37 PM by PaulC

    https connection reset on import

    PaulC

      Hi

       

      Oracle APEX : 19.2

      ORDS:19.2

      Application Server : Apache Tomcat 9

      Oracle DB : 12.1.2 & 12.2

       

      Tomcat set up to use https:-

      <Connector SSLEnabled="true" acceptCount="100" clientAuth="false"

          disableUploadTimeout="true" enableLookups="false" maxThreads="25"

          port="8443" keystoreFile="conf/xxxxxxxx.jks" keystorePass="xxxxxxxxxxx"

          protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https"

          secure="true" sslProtocol="TLS" />

       

      Tomcat webserver front ended with F5 network load balancer (with ssl certs) which redirect to webserver.

       

      It is possible to login to Apex development environment with no problems (using  https://"f5server"/ords/"database").  But an import of any object (workspace, application, shared components workspace files, etc) fails with the error (the error arise almost instantly):-

      https://"f5server"/ords/"database"/wwv_flow.accept

       

      The connection was reset.

       

      Try:

      ERR_CONNECTION_RESET

       

       

      Looking at APEX views, nothing appears to be loaded, so don't think any payload started on APEX.

       

      The tomcat log file show:-

       

      08-Apr-2020 09:18:15.618 INFO [https-jsse-nio-8443-exec-1] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header

      Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

      java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

      at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:416)

      at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260)

      at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)

      at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)

      at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639)

      at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)

      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

      at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

                      at java.base/java.lang.Thread.run(Thread.java:834)

       

      So I'm guessing this is a http header issue and there is some configuration missing?

       

      Any help much appreciated

       

      Thanks

       

      Paul