349639 – In jetty-7.1.6.v20100715 sometimes occure many brokePipe IOexception

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349639 - In jetty-7.1.6.v20100715 sometimes occure many brokePipe IOexception

Summary: In jetty-7.1.6.v20100715 sometimes occure many brokePipe IOexception

Status:	RESOLVED INVALID

Alias:	None

Product:	Jetty
Classification:	RT
Component:	server (show other bugs)
Version:	unspecified
Hardware:	Power PC Linux

Importance:	P3 major (vote)
Target Milestone:	7.2.x
Assignee:	Greg Wilkins
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-06-16 21:33 EDT by 高二荣
Modified:	2011-06-17 08:53 EDT (History)
CC List:	2 users (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 高二荣

2011-06-16 21:33:57 EDT

2011-06-17 08:42:02,755 ERROR [framework.pipe.ResultExporterPipe:49] - export result error:
org.eclipse.jetty.io.RuntimeIOException: java.io.IOException: Broken pipe
        at org.eclipse.jetty.io.UncheckedPrintWriter.setError(UncheckedPrintWriter.java:107)
        at org.eclipse.jetty.io.UncheckedPrintWriter.write(UncheckedPrintWriter.java:280)
        at org.eclipse.jetty.io.UncheckedPrintWriter.write(UncheckedPrintWriter.java:295)
        at com.taobao.top.impl.core.export.ProtocolXmlV2.export(ProtocolXmlV2.java:147)
        at com.taobao.top.impl.core.export.ProtocolXmlV2.export(ProtocolXmlV2.java:125)
        at com.taobao.top.core.DefaultApiExporter.exportStrategy(DefaultApiExporter.java:200)
        at com.taobao.top.core.DefaultApiExporter.export(DefaultApiExporter.java:87)
        at com.taobao.top.core.framework.pipe.ResultExporterPipe.doPipe(ResultExporterPipe.java:47)
        at com.taobao.top.core.framework.pipe.ResultExporterPipe.doPipe(ResultExporterPipe.java:21)
        at com.taobao.top.xbox.framework.http.AbstractHttpPipeManager.doPipes(AbstractHttpPipeManager.java:456)
        at com.taobao.top.xbox.framework.http.AbstractHttpPipeManager.doPipes(AbstractHttpPipeManager.java:348)
        at com.taobao.top.xbox.framework.http.HttpPipeTask.run(HttpPipeTask.java:87)
        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:662)
Caused by: java.io.IOException: Broken pipe
        at sun.nio.ch.EPollArrayWrapper.interrupt(Native Method)
        at sun.nio.ch.EPollArrayWrapper.interrupt(EPollArrayWrapper.java:256)
        at sun.nio.ch.EPollSelectorImpl.wakeup(EPollSelectorImpl.java:175)
        at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.wakeup(SelectorManager.java:819)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.updateKey(SelectChannelEndPoint.java:417)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.blockWritable(SelectChannelEndPoint.java:349)
        at org.eclipse.jetty.http.AbstractGenerator.blockForOutput(AbstractGenerator.java:493)
        at org.eclipse.jetty.http.AbstractGenerator.flush(AbstractGenerator.java:430)
        at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:78)
        at org.eclipse.jetty.server.HttpConnection$Output.flush(HttpConnection.java:1133)
        at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:159)
        at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:86)
        at java.io.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:109)
        at org.eclipse.jetty.server.HttpWriter.write(HttpWriter.java:258)
        at org.eclipse.jetty.server.HttpWriter.write(HttpWriter.java:107)
        at org.eclipse.jetty.server.HttpWriter.write(HttpWriter.java:96)
        at org.eclipse.jetty.io.UncheckedPrintWriter.write(UncheckedPrintWriter.java:271)
        ... 13 more

Comment 1 Jesse McConnell

2011-06-17 08:53:47 EDT

I would recommend trying a more recent version of jetty, we are up to 7.4.2.v20110526

if you still see this error then please reopen this issue with some additional information regarding frequency, what the client (browser or java) and network conditions, its possible this was just issues with the client or network, not really enough to go on in terms of isolating or legitimizing an actual issue.

cheers