Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311609 - Intermittent WebSocketLoadTest failure
Summary: Intermittent WebSocketLoadTest failure
Status: RESOLVED WORKSFORME
Alias: None
Product: Jetty
Classification: RT
Component: build (show other bugs)
Version: 7.1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 7.0.2.RC0   Edit
Assignee: Jesse McConnell CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 15:28 EDT by Michael Gorovoy CLA
Modified: 2011-06-29 10:24 EDT (History)
2 users (show)

See Also:

Attachments
Test output (2.79 KB, text/plain)
2010-05-04 15:28 EDT, Michael Gorovoy CLA 		no flags Details
View All 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 Michael Gorovoy CLA 2010-05-04 15:28:49 EDT 
Created attachment 167031 [details]
Test output

Running org.eclipse.jetty.websocket.WebSocketLoadTest
2010-05-04 15:25:50.333:INFO::Logging to StdErrLog::DEBUG=false via org.eclipse.jetty.util.log.StdErrLog
2010-05-04 15:25:50.347:INFO::jetty-7.1.0.RC1-SNAPSHOT
2010-05-04 15:25:50.392:INFO::Started SelectChannelConnector@0.0.0.0:51939
Exception in thread "pool-1-thread-289" java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:188)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
	at java.io.InputStreamReader.read(InputStreamReader.java:167)
	at java.io.BufferedReader.fill(BufferedReader.java:136)
	at java.io.BufferedReader.read(BufferedReader.java:157)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.readString(WebSocketLoadTest.java:203)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:181)
	... 3 more
Exception in thread "pool-1-thread-288" java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:188)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
	at java.io.InputStreamReader.read(InputStreamReader.java:167)
	at java.io.BufferedReader.fill(BufferedReader.java:136)
	at java.io.BufferedReader.read(BufferedReader.java:157)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.readString(WebSocketLoadTest.java:203)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:181)
	... 3 more
Exception in thread "pool-1-thread-290" java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:188)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
	at java.io.InputStreamReader.read(InputStreamReader.java:167)
	at java.io.BufferedReader.fill(BufferedReader.java:136)
	at java.io.BufferedReader.read(BufferedReader.java:157)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.readString(WebSocketLoadTest.java:203)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:181)
	... 3 more
Exception in thread "pool-1-thread-483" java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:188)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
	at java.io.InputStreamReader.read(InputStreamReader.java:167)
	at java.io.BufferedReader.fill(BufferedReader.java:136)
	at java.io.BufferedReader.read(BufferedReader.java:157)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.readString(WebSocketLoadTest.java:203)
	at org.eclipse.jetty.websocket.WebSocketLoadTest$WebSocketClient.run(WebSocketLoadTest.java:181)
Comment 1 Michael Gorovoy CLA 2011-06-29 10:24:10 EDT 
It appears that this module has undergone several rounds of refactoring caused by updates in websocket spec, and this apparently is no longer an issue.