Topic
  • 8 replies
  • Latest Post - ‏2010-10-25T15:54:44Z by Youdlikewouldntyou
SystemAdmin
SystemAdmin
37421 Posts

Pinned topic SRVE0133E: An error occurred while parsing parameters. java.io.IOException:

‏2008-04-13T00:49:29Z |
Hi,

I am getting below error in production box. Cna somebody give me some pointer on where to really look for ?
4/12/08 16:54:35:895 GMT+05:30 00002a97 SRTServletReq E SRVE0133E: An error occurred while parsing parameters. java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
at com.ibm.io.async.AbstractAsyncChannel.multiIO(AbstractAsyncChannel.java:474)
at com.ibm.io.async.AsyncSocketChannelHelper.read(AsyncSocketChannelHelper.java:194)
at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.readAIOSync(AioSocketIOChannel.java:205)
at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:150)
at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPReadRequestContextImpl.java:109)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer(HttpServiceContextImpl.java:4139)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSingleBlock(HttpServiceContextImpl.java:3383)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readBodyBuffer(HttpServiceContextImpl.java:3488)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1606)
at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.bufferIsGood(WCCByteBufferInputStream.java:109)
at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.read(WCCByteBufferInputStream.java:79)
at com.ibm.ws.webcontainer.srt.http.HttpInputStream.read(HttpInputStream.java:294)
at com.ibm.ws.webcontainer.servlet.RequestUtils.parsePostData(RequestUtils.java:297)
at com.ibm.ws.webcontainer.srt.SRTServletRequest.parseParameters(SRTServletRequest.java:1476)
at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameterNames(SRTServletRequest.java:1111)
at org.apache.struts.util.RequestUtils.populate(RequestUtils.java:1225)
at org.apache.struts.action.RequestProcessor.processPopulate(RequestProcessor.java:821)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:254)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.idea.icare2.filter.AuthorizationFilter.doFilter(AuthorizationFilter.java:185)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:761)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)

4/12/08 16:54:52:367 GMT+05:30 00002a4d SRTServletReq E SRVE0133E: An error occurred while parsing parameters. java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
at com.ibm.io.async.AbstractAsyncChannel.multiIO(AbstractAsyncChannel.java:474)
at com.ibm.io.async.AsyncSocketChannelHelper.read(AsyncSocketChannelHelper.java:194)
at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.readAIOSync(AioSocketIOChannel.java:205)
at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:150)
at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPReadRequestContextImpl.java:109)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer(HttpServiceContextImpl.java:4139)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSingleBlock(HttpServiceContextImpl.java:3383)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readBodyBuffer(HttpServiceContextImpl.java:3488)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.getRequestBody
Updated on 2010-10-25T15:54:44Z at 2010-10-25T15:54:44Z by Youdlikewouldntyou
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2008-05-01T14:13:00Z  
    Did you ever figure out anything with this? My app server hung this morning and I saw that same error in my logs.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2008-05-01T16:02:21Z  
    Did you ever figure out anything with this? My app server hung this morning and I saw that same error in my logs.
    Hi,

    I am yet to resolve this problem. Production server is showing this exception in the SystemOut.log always and as of now server is not hung or stopped. But I am afraid that due to this my log files are getting filled very quickly.

    I have seen one article in javaranch and please have a look. I am not able to do below changes in production as websphere admiistrator is not comfortable with making this change :-). If you have any success from the below article, please let me know.

    http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic& f=46&t=005730
  • JohnPP
    JohnPP
    52 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2008-06-04T05:14:28Z  
    We had this exact error
    SRTServletReq E SRVE0133E: An error occurred while parsing parameters. java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.

    For us the problem was a HTML input submit button that had onClick=self.close()
    Onclick the form submits and then the page closes which caused the error.

    Locally the server reported a different error: reason: RC: 10054 An existing connection was forcibly closed by the remote host.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2008-10-03T20:29:25Z  
    • JohnPP
    • ‏2008-06-04T05:14:28Z
    We had this exact error
    SRTServletReq E SRVE0133E: An error occurred while parsing parameters. java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.

    For us the problem was a HTML input submit button that had onClick=self.close()
    Onclick the form submits and then the page closes which caused the error.

    Locally the server reported a different error: reason: RC: 10054 An existing connection was forcibly closed by the remote host.
    I am having the same issue, Do anybody know what could cause this issue and/or how to fix it?! Best Regards
  • Haf
    Haf
    2 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOException:

    ‏2009-11-03T14:29:42Z  
    Hi,

    sorry for pushing
    unfortunately I have the same problem.
    I get

    java.io.IOException: SRVE0080E Invalid content length

    and

    java.io.IOException: Async IO operation failed, reason: RC: 10054 An existing connection was forcibly closed by the remote host.

    What are the reasons for this exceptions and how to fix that?

    Tanks for any advice!

    Regards

    Haf

    Tech-Data:
    WebSphere Application Server 6.1.0.19
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2009-11-04T06:42:53Z  
    Hi,

    I am yet to resolve this problem. Production server is showing this exception in the SystemOut.log always and as of now server is not hung or stopped. But I am afraid that due to this my log files are getting filled very quickly.

    I have seen one article in javaranch and please have a look. I am not able to do below changes in production as websphere admiistrator is not comfortable with making this change :-). If you have any success from the below article, please let me know.

    http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic& f=46&t=005730
    Hi,

    Are you trying to refer to this url ?? If not , please have a look at this one as well.

    http://www.coderanch.com/t/75394/Websphere/getParameter-gives-error-SRVE-E

    Thanks
    Akash
  • Haf
    Haf
    2 Posts

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2009-11-11T11:11:50Z  
    Hi,

    Are you trying to refer to this url ?? If not , please have a look at this one as well.

    http://www.coderanch.com/t/75394/Websphere/getParameter-gives-error-SRVE-E

    Thanks
    Akash
    Hi,

    thanks for your response.
    Yes I know this post, however I did not tried it, cause I do not see any
    java.net.SocketTimeOutException: Read Timed Out
    Exceptions in my log files.
    maybe I will try this configuration...

    Thanks

    Haf
  • Youdlikewouldntyou
    Youdlikewouldntyou
    1 Post

    Re: SRVE0133E: An error occurred while parsing parameters. java.io.IOExcept

    ‏2010-10-25T15:54:44Z  
    • Haf
    • ‏2009-11-11T11:11:50Z
    Hi,

    thanks for your response.
    Yes I know this post, however I did not tried it, cause I do not see any
    java.net.SocketTimeOutException: Read Timed Out
    Exceptions in my log files.
    maybe I will try this configuration...

    Thanks

    Haf
    You need to run a *.flush() function every so often, otherwise, your going to run out of memory and get a disconnect from trying to write too much data to the client buffer.