Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running TwoMinuteExample: Socket Exception at: [Broken pipe (Write failed)] #1187

frankgerhardt opened this issue Feb 18, 2019 · 2 comments


None yet
2 participants
Copy link

commented Feb 18, 2019

Debian 8, OpenJDK 8, fitnesse-standalone.jar, fitnesse-git-plugin-1.2.0-all.jar.

Firefox ESR


Fresh install.

When running the TwoMinuteExample test, I get this Exception about every third time. The test results are displayed ok.

WARNING: Socket Exception at: 1550448365328 [Broken pipe (Write failed)] Broken pipe (Write failed)
	at java.base/ Method)
	at java.base/
	at java.base/
	at fitnesse.FitNesseExpediter.send(
	at fitnesse.http.ChunkedResponse.closeTrailer(
	at fitnesse.http.ChunkedResponse.close(
	at fitnesse.responders.ChunkingResponder.startSending(
	at fitnesse.http.ChunkedResponse.sendTo(
	at fitnesse.FitNesseExpediter.sendResponse(
	at java.base/java.util.concurrent.Executors$
	at java.base/
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.base/java.util.concurrent.ThreadPoolExecutor$
	at java.base/

I'd prefer not to get these Exceptions even if they are only "warnings".

tcnh added a commit to tcnh/fitnesse that referenced this issue Feb 18, 2019


This comment has been minimized.

Copy link

commented Feb 18, 2019

Did a bit of digging on this one. Couldn't reproduce it on a windows rig, but a debian VM with the mentioned Java version gave the described behaviour.

What I >think< happens is that SuiteResponder calls closeTrailer() and then close() on the respnse object.
close() then also calls closeTrailer(), resulting in CR/LF being sent twice in a row. My guess is that the first call causes the socket connection to be dropped, sometimes in time for the second call to actually fail (as if the test was stopped manually).

I removed the -what seems to be- obsolete call from SuiteResponder in my 1187 branch. After that, I can no longer reproduce the issues (and see no new trouble appearing on both windows and debian jessie when running the two-minute Example and the full SuiteAcceptanceTests)


This comment has been minimized.

Copy link

commented Feb 18, 2019

I had this only in Firefox, not in Chrome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.