Broken pipe from web service in AS6

[meetoblivion]

A few times now in a production instance I have, we've run into this problem where a socket exception occurred when generating data from a web service.  The only odd thing about the application is that it's both JMS and WebServices running (as well as REST).  There is no front end - the webservices feed a remote front end.  Any idea on what cause this?

Caused by: javax.xml.bind.MarshalException

- with linked exception:

[ClientAbortException:  java.net.SocketException: Broken pipe]

        at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:320)

        at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:244)

        at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:74)

        at org.apache.cxf.jaxb.JAXBEncoderDecoder.writeObject(JAXBEncoderDecoder.java:536)

        at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.java:227)

        ... 39 more

Caused by: ClientAbortException:  java.net.SocketException: Broken pipe

        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:401)

        at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

        at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

        at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:424)

        at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:413)

        at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:89)

        at org.apache.cxf.io.AbstractWrappedOutputStream.write(AbstractWrappedOutputStream.java:46)

        at com.sun.xml.bind.v2.runtime.output.UTF8XmlOutput.write(UTF8XmlOutput.java:406)

        at com.sun.xml.bind.v2.runtime.output.Encoded.write(Encoded.java:163)

        at com.sun.xml.bind.v2.runtime.output.UTF8XmlOutput.writeName(UTF8XmlOutput.java:235)

        at com.sun.xml.bind.v2.runtime.output.UTF8XmlOutput.beginStartTag(UTF8XmlOutput.java:163)

        at com.sun.xml.bind.v2.runtime.output.NamespaceContextImpl$Element.startElement(NamespaceContextImpl.java:491)

        at com.sun.xml.bind.v2.runtime.XMLSerializer.endNamespaceDecls(XMLSerializer.java:287)

        at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:683)

        at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.serializeBody(SingleElementNodeProperty.java:152)

        at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:340)

        at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:696)

        at com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:65)

        at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:168)

        at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:155)

        at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:340)

        at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:696)

        at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:152)

        at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:189)

        at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(ElementBeanInfoImpl.java:316)

        at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:323)

        at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:72)

        at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:494)

        at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:315)

        ... 43 more

Caused by: java.net.SocketException: Broken pipe

        at java.net.SocketOutputStream.socketWrite0(Native Method)

        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

        at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:726)

        at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:449)

        at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349)

        at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:750)

        at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:126)

        at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:559)

        at org.apache.coyote.Response.doWrite(Response.java:567)

        at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:396)

        ... 71 more

[genman]

I would say this is completely normal, completely healthy. If the remote host closes the connection without reading the response, this could happen.

You can verify what's going on using "tcpdump" and/or Wireshark.

[meetoblivion]

It seems like it's mostly caused by the web service consumer (front end) making incomplete requests.  I have our network folks taking a look.