Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-4363

JMS transport uses the "clientReceiveTimeout" on server side

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.6.1
    • Fix Version/s: 2.4.9, 2.5.5, 2.6.2
    • Component/s: Transports
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description


      The JMS transport always uses the "clientReceiveTimeout" to configure the timeout of the DefaultMessageListenerContainer which doesn't make sense on the server side. Worse, if that value is set very high, the server may hang in the endpoint.stop() call when trying to stop the service as it has to wait for the receive to timeout. The values should be separated so clients and servers can use separate values.

        Attachments

          Activity

            People

            • Assignee:
              dkulp Daniel Kulp
              Reporter:
              dkulp Daniel Kulp
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: