jax-ws
  1. jax-ws
  2. JAX_WS-1142

It is not possible to distinguish between a read/write SocketTimeoutException when a web service call fails with a WebServiceException

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: runtime
    • Labels:
      None
    • Environment:

      Any

      Description

      When a web service call fails due to a timeout, a WebServiceException is thrown with SocketTimeoutException cause.

      It is not possible to distinguish between a read timeout and a write timeout, which is important to be able to distinguish between "call not made" and "response not received".

        Activity

        Hide
        liam.williams.geo added a comment -

        Suggested fix: wrap the SocketTimeoutException in a custom read/write exception that can be determined by catching the SocketTimeoutException on either connect() or read().

        Show
        liam.williams.geo added a comment - Suggested fix: wrap the SocketTimeoutException in a custom read/write exception that can be determined by catching the SocketTimeoutException on either connect() or read().

          People

          • Assignee:
            Unassigned
            Reporter:
            liam.williams.geo
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 2 days
              2d
              Remaining:
              Remaining Estimate - 2 days
              2d
              Logged:
              Time Spent - Not Specified
              Not Specified