[CXF-8895] Deadlock instead of timeout with new HttpClientHTTPConduit using large payloads

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6.0, 3.6.1
• Fix Version/s: 3.6.2, 4.0.3
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Manuel
• Created: 28/Jun/23 09:30
• Updated: 18/Sep/23 18:48
• Resolved: 06/Sep/23 20:20

Description

Hello,

 

we discovered an issue that causes a deadlock with large payloads which exceed the chunk-length (that is used as buffer size for an PipedInputStream) when sending a message to a currently offline/not-available server.

Even when setting the ConnectionTimeout for the HTTPConduit to e.g., 1000ms, the timeout does not occur. (the ReceiveTimeout works as expected though)

The feature that introduced the new HttpClientHTTPConduit was CXF-8840 with commit 1e7169.

 

What was expected:

Any type of timeout-related exception.

 

What actually happened:

The thread runs into a deadlock.

 

How to reproduce:

Run org.apache.cxf.systest.dispatch.DispatchClientServerTest.testTimeout()  and increase the payload of resources/GreetMeDocLiteralReq.xml (or use the attachment provided). The test will not terminate after the given timeout, the test will run indefinitely.

The PipedInputStream's read method was never called (server offline), hence the PipedOutputStream's write method can't continue to write the data -> Deadlock.

 

Regards,

Manuel