IC91900: TCP WAIT TIMEOUT ISSUE

3.4.1.8-SterlingSecureProxy-Windows-if0009
3.4.1.8-SterlingSecureProxy-SolarisSPARC-if0009
3.4.1.8-SterlingSecureProxy-Linux-if0009
3.4.1.8-SterlingSecureProxy-Linux_S390-if0009
3.4.1.8-SterlingSecureProxy-HP-if0009
3.4.1.8-SterlingSecureProxy-HP-IA-if0009
3.4.1.8-SterlingSecureProxy-AIX-if0009

APAR status

• Closed as program error.

Error description

• SSP receiving timeout issues with Connect:Direct, even when
  using the same server, hardware, and network routing (installed
  Connect:Direct on the SSP server for tests).
  

Local fix

• None.  Transfers fail with connection timeouts at different
  points in the transfer.  Trasnfers directly to Connect:Direct
  run smoothly.
  

Problem summary

• Customer sending large GB+ files over their VPN network via C:D
  without Secure Plus (non-secure). At seemingly random times
  during the transfer the transfer times out with
     CSP057E 16 Exception or other serious error occurred:
  exception in processing Did not get buffer in 90000 ms
     CSP900E Logged Exception : java.io.InterruptedIOException:
  Did not get buffer in 90000 ms
  The timeout was happening on the non-sending side of the
  channel, and was self-healing if it detected any activity in
  the session within the last second.  In some cases, the one
  second activity check failed and the transfer timed out.
  

Problem conclusion

• Increased the activity check value during the timeout operation
  from 1 second to 10 seconds to ensure active transfers will not
  time out.
  

Temporary fix

• Increased an internal keep-alive value from 1 second to 10
  seconds to allow a long-running transmission to keep running
  when there is no activity in the reverse direction.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR SECURE PROX

• Fixed component ID

  5725D0300

Applicable component levels

• R341 PSY

     UP