[CXF-4363] JMS transport uses the "clientReceiveTimeout" on server side

• 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
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Daniel Kulp
• Created: 06/Jun/12 14:29
• Updated: 28/Aug/12 17:44
• Resolved: 11/Jul/12 14:40

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.