--Environment - Red Hat Enterprise Linux Server release 6.3 (Santiago) - java version "1.7.0_79" - GlassFish 4.1

Event: java.io.IOException occurred while processing a large amount of data with GlassFish

[2020/05/21 17:41:07.805][656b5aef53f][][FATAL] - java.io.IOException: java.lang.InterruptedException
org.glassfish.grizzly.nio.transport.TCPNIOTransportFilter.handleRead(TCPNIOTransportFilter.java:92)
org.glassfish.grizzly.filterchain.TransportFilter.handleRead(TransportFilter.java:173)
org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:284)
org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:201)
org.glassfish.grizzly.filterchain.DefaultFilterChain.read(DefaultFilterChain.java:351)
org.glassfish.grizzly.filterchain.FilterChainContext.read(FilterChainContext.java:695)
org.glassfish.grizzly.http.io.InputBuffer.blockingRead(InputBuffer.java:1119)
org.glassfish.grizzly.http.server.io.ServerInputBuffer.blockingRead(ServerInputBuffer.java:95)
org.glassfish.grizzly.http.io.InputBuffer.fill(InputBuffer.java:1143)
org.glassfish.grizzly.http.io.InputBuffer.read(InputBuffer.java:353)
org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:267)
org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:270)
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
java.io.InputStreamReader.read(InputStreamReader.java:184)
java.io.BufferedReader.fill(BufferedReader.java:154)
java.io.BufferedReader.readLine(BufferedReader.java:317)
java.io.BufferedReader.readLine(BufferedReader.java:382)
...abridgement...

Cause: The application execution time has timed out

The problem was that I didn't specify the setting configs.config.network-config.protocols.protocol.http.request-timeout-seconds to set the execution time of the application.

The default timeout for Glassfish is 15 minutes. This can happen in a variety of situations. For example, if the request fires a long-running action that does not respond within the timeout period, the request to the server is made over HTTPS and only HTTP (or vice versa) is supported in the HTTP connection pool. For example, if there are no more connections available. java - GRIZZLY0023 Glassfish warning - Stack Overflow

Action: Set http.request-timeout-seconds in domain.xml

This time, the timeout was 15 minutes because it was not set, so I set it to unlimited "-1".

`domain.xml`


  <configs>
    <config name="server-config">
      <network-config>
        <protocols>
          <protocol name="http-listener-1">
            <http max-post-size-bytes="20971520" default-virtual-server="server" max-connections="250" request-timeout-seconds="-1">

When setting on the GlassFish management screen (http: // localhost: 4848), server-config> Network Config> Network Listeners> {Target Listener}> [HTTP] tab>Request Timeout:

It seems that "-1" cannot be set from Glassfish 3.1.2, but when I set it, java.io.IOException no longer occurs ... But when I look at the management screen, the initial value is 900 seconds (15 minutes). ···Strange