PH01698: WHEN TUNNELING SSL REQUESTS THROUGH CACHING PROXY, IT'S POSSIBLETHE CONNECTION CAN HANG IF DATA GREATER THAN 1024 BYTES IS SENT

9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When tunneling SSL requests through Edge Caching Proxy, it is
  possible for the connection to hang if data greater than 1024
  bytes is sent
  
  Problem reported on version 8.5.5.13 on Linux Red Hat
  Enterprise 7.5
  

Local fix

• Use Non-SSL connections
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM Caching Proxy                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Tunneling SSL requests through IBM      *
  *                      Caching Proxy might hang if more than   *
  *                      1024 bytes of data is sent.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When tunneling SSL requests through IBM Caching Proxy, it is
  possible for the connection to hang if more than 1024 bytes of
  data is sent due to the improper flushing of a buffer.
  

Problem conclusion

• IBM Caching Proxy was updated to properly flush the buffer.
  
  The fix for this is targeted for the following IBM Caching
  Proxy fixpacks:
  - 9.0.0.10
  - 8.5.5.15
  

Temporary fix

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

  WEBS CACH PROXY

• Fixed component ID

  5724H8810

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP