Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

An error occurred while parsing parameters. {0} java.io.IOException-WAS7

 
selva raja
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

Im getting the below mentioned error in SystemOut.log frequently, after this error the application stops responding. What could be the root cause. please find the log info....

[3/7/11 17:00:20:741 IST] 00000224 srt E com.ibm.ws.webcontainer.srt.SRTServletRequest parseParameters SRVE0133E: An error occurred while parsing parameters. {0}
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:200)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
at com.ibm.ws.tcp.channel.impl.NioSocketIOChannel.read(NioSocketIOChannel.java:241)
at com.ibm.ws.tcp.channel.impl.NioSocketIOChannel.attemptReadFromSocketUsingNIO(NioSocketIOChannel.java:140)
at com.ibm.ws.tcp.channel.impl.SocketIOChannel.attemptReadFromSocket(SocketIOChannel.java:631)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:596)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.processWork(WorkQueueManager.java:341)
at com.ibm.ws.tcp.channel.impl.NioTCPReadRequestContextImpl.processAsyncReadRequest(NioTCPReadRequestContextImpl.java:139)
at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.readInternal(TCPReadRequestContextImpl.java:169)
at com.ibm.ws.tcp.channel.impl.NioTCPReadRequestContextImpl.processSyncReadRequest(NioTCPReadRequestContextImpl.java:68)
at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPReadRequestContextImpl.java:111)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer(HttpServiceContextImpl.java:4139)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readSingleBlock(HttpServiceContextImpl.java:3371)
at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.readBodyBuffer(HttpServiceContextImpl.java:3477)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundServiceContextImpl.getRequestBodyBuffer(HttpInboundServiceContextImpl


Thanks,
selva
 
pallavi mamilla
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Selva,

Are you able to find the solution for this problem? This issue is hammering our JVMs and causing outages.
 
Kurtcebe Eroglu
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
IMHO this may be a network problem. If this is the case, following may help.

If your server is becoming unresponsive after seeing this error frequently, try setting ConnectionIOTimeout of your HTTP transport to a lower value (for example 1 sec instead of default 5 seconds). You will still see these exceptions for bad requests but server shall stay more responsive, as your webcontainer threads will be blocked for a shorter duration before timing out on a bad request. If you don't have responsiveness issues but just irritated by this exception every once in a while, you may increase this value to give more slack to cover for network problems.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic