Announcement Announcement Module
Collapse
No announcement yet.
Errors in WebSphere Application Server 6.1 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Errors in WebSphere Application Server 6.1

    Hello guys, nice to be here. I am posting this on behalf of a developer. We have a WebSphere Application Server that sits in our internal network. There are two Apache Web Servers in the DMZ front ended by a load-balancing device. When we run load against the system, we get Spring errors. The errors are below. If someone has seen this before then great, but at the very least I'd like some ideas on some things I should check because I am clean out of them.

    TRACING ON APPLICATION SERVER

    [8/29/12 0:07:14:054 EDT] 00000269 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: cat-client-ws. Exception thrown : org.springframework.web.util.NestedServletExceptio n: Request process
    ing failed; nested exception is org.springframework.ws.soap.axiom.AxiomSoapMessage CreationException: Could not parse request: Async IO operation failed, reason: RC: 107 Transport endpoint is not connected; nested exception is com.ctc.wst
    x.exc.WstxIOException: Async IO operation failed, reason: RC: 107 Transport endpoint is not connected
    at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:583)
    at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:511)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.cache.servlet.ServletWrapper.servicePro xied(ServletWrapper.java:282)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)
    ...................

    Caused by: org.springframework.ws.soap.axiom.AxiomSoapMessage CreationException: Could not parse request: Async IO operation failed, reason: RC: 107 Transport endpoint is not connected; nested exception is com.ctc.wstx.exc.WstxIOException
    : Async IO operation failed, reason: RC: 107 Transport endpoint is not connected

    Or:

    [7/19/12 17:30:14:179 EDT] 0000003c ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: cat-client-ws. Exception thrown : org.springframework.web.util.NestedServletExceptio n: Request processing failed; nested exception is org.springframework.ws.soap.axiom.AxiomSoapMessage Exception: Could not write message to OutputStream: OutputStream encountered error during write; nested exception is com.ctc.wstx.exc.WstxIOException: OutputStream encountered error during write
    at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:583)

    ......................

    Caused by: com.ibm.wsspi.webcontainer.ClosedConnectionExcepti on: OutputStream encountered error during write
    at com.ibm.ws.webcontainer.channel.WCCByteBufferOutpu tStream.write(WCCByteBufferOutputStream.java:114)
    at com.ibm.ws.webcontainer.srt.SRTOutputStream.write( SRTOutputStream.java:96)
    at com.ibm.wsspi.webcontainer.util.BufferedServletOut putStream.writeOut(BufferedServletOutputStream.jav a:467)
    at com.ibm.wsspi.webcontainer.util.BufferedServletOut putStream.flushBytes(BufferedServletOutputStream.j ava:351)
    at com.ibm.wsspi.webcontainer.util.BufferedServletOut putStream.write(BufferedServletOutputStream.java:3 14)
    at org.springframework.ws.transport.TransportOutputSt ream.write(TransportOutputStream.java:60)
    at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:9 6)
    at com.ctc.wstx.sw.BufferingXmlWriter.flush(Buffering XmlWriter.java:214)
    at com.ctc.wstx.sw.BufferingXmlWriter.close(Buffering XmlWriter.java:194)
    at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(Ba seStreamWriter.java:1690)
    ... 32 more
    Caused by: java.io.IOException: Async IO operation failed, reason: RC: 32 Broken pipe

    TRACING ON PLUGIN COMPONENT ON APACHE WEB SERVER

    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - TRACE: mod_was_ap22_http: cb_write_body: In the write body callback writing 32768
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - TRACE: lib_htresponse: htresponseGetChunk: Getting the next chunk
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - TRACE: lib_htresponse: htresponseGetChunk: Chunk length hex: 8000 -> 32768
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - TRACE: ws_esi: readResponseBody, len_p=32768
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - TRACE: mod_was_ap22_http: cb_write_body: In the write body callback writing 32768
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - WARNING: mod_was_ap22_http: cb_write_body: write failed , 32768 attempted, -1 actual.
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - WARNING: mod_was_ap22_http: cb_write_body: response flush failed.
    [Thu Jul 19 17:30:14 2012] 0000545c 069deba0 - WARNING: ESI: esiResponsePassThru: failed to write body client closed connection

    Kind regards,

    'D'
Working...
X