Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360051 - SocketConnectionTest.testServerClosedConnection is excluded
Summary: SocketConnectionTest.testServerClosedConnection is excluded
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.5.1   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 7.5.x   Edit
Assignee: Simone Bordet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 18:08 EDT by Greg Wilkins CLA
Modified: 2011-10-06 10:16 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Wilkins CLA 2011-10-05 18:08:17 EDT 
The SocketConnectionTest.testServerClosedConnection is currently excluded from the build because it fails with 100% CPU.

If the test is slowed down with sleeps/debug, it completes successfully.

When it fails, it appears that the first request is completed OK and the second request send call completes, but the call to serverSocket.accept() never gets a new connection and something consumes 100% CPU.
Comment 1 Simone Bordet CLA 2011-10-06 10:16:29 EDT 
Fixed.
The problem was that the parser was reading -1 but the connection never closed, and this lead to CPU spinning.
Test had to be modified since it cannot work like it does for the SelectConnector.