Hi people.
I have a exception that it makes my life sad. But i have a feeling that the error comes from application. I wanna to know if I can do anything in the server. 

The exception java.net.SocketTimeoutException repeats a LOT (almost all entries are this exception) in the systemOut. The app connects to AS400 for operations. I have WASND 6.1 installed over Windows Server 2003 64bits. 

[2/29/12 13:57:31:252 VET] 00004b53 E UOW=null source=com.ibm.ws.webcontainer.srt.SRTServlet
Request org=IBM prod=WebSphere component=
Application Server thread=[WebContainer : 15775]

SRVE0133E: An error occurred while parsing parameters. java.net.SocketTimeoutException: Socket operation timed out before it could be completed
at com.ibm.ws.tcp.channel.impl.SocketRWChannelSelector.
checkForTimeouts(SocketRWChannelSelector.java:462)
at com.ibm.ws.tcp.channel.impl.ChannelSelector.run
(ChannelSelector.java:237)
at java.lang.Thread.run(Thread.java:811)

What do you suggests?

;)

 

Hi Yasmin,

 If you're seeing this error in the log of the WAS in the application has to be failing something. As message indicate that it is doing something (reading parameters) and because timeout it fails.

 How is the application connecting to AS400? using HoD, HATS, invoking are WebService?

 You need to determine who is launching the timeout (there are a lot of timeouts) depending the timeout you can ajust the timeout.

 If you increase the timeout maybe the application can finish doing whatever it need to do

  Look at this technote

Common Timeouts effecting Web Services, HTTP and SOAP clients

www-01.ibm.com/support/docview.wss?uid=s...

  tell us if you need more help.

regards,

For a socket timeout I would recommend you first look at the JVM Web Container settings and determine if the timeout there is acceptable.  Acceptable is a debatable term here...  You need to discuss with the service your waiting for on the other end to see what kind of SLA you should expect from them.

You could also look into a network trace with your Networking group.  They sould be able to verify that the server on the other end of your request is getting the request.

Assuming that the request gets to the other side, it sounds like it's the performance of the target system (the SLA mentioned above.)  You should be able to press that group for more information about the performance. 

If they can't improve the performance there, consider:
1.  Increase the timeout on the web container (WebSphere)
2.  Discuss with the developers how they can reduce the load on the target system

Erik  

Hi Erik ,Gabriel

I'm also facing same isssue , i have checked the channel frame work(TCP,SSL,HTTP,Wecontainer channel , webcontianer settings.) read , and write , presit timeout  ...etc   value are default.

And  my applicatin connecting to webservices .. 

while enable  the trace on webspher and plugin level this issue was not replicated in the log files ( tarce,systemout.log ,plugin logs ).


IBM WebSphere Application Server - ND -Version 7.0.0.23
OS -Linux 5.


Could you please advise me on this issue .


ERROR:

E com.ibm.ws.webcontainer.srt.SRTServletRequest parseParameters SRVE0133E: An error occurred while parsing parameters. {0}
java.net.SocketTimeoutException: Socket operation timed out before it could be completed
at com.ibm.ws.tcp.channel.impl.SocketRWChannelSelector.checkForTimeouts(SocketRWChannelSelector.java:462)
at com.ibm.ws.tcp.channel.impl.ChannelSelector.run(ChannelSelector.java:241)
at java.lang.Thread.run(Thread.java:736)

Thanks in advance !

Regards,
Sathish  

 

Hi

Whats the timeout settings?
do you know, if you are writing large data?

your timeout issus could be because of the amount of data or time it is taking to write the data.

Are you able to reproduce the problem or is it just happening randomly ?

Hi Joseph ,

please find time out detais below .

Transport Channels TCP inbound channel

Inactivity timeout 60 seconds

HTTP inbound channe

Read timeout 60 seconds
Write timeout 60 seconds
Persistent timeout 30 seconds

Web container inbound channel
Write buffer size = 32768
Application , appserve(JVM) and webservices level Session time out vlue is 30 mis
Session time out=30 mins

 Thanks in advance

Rergards
Satheesh  

Hi Joseph,

do you know, if you are writing large data?

No idea, can you please tell me how to check wrting the large data or not

Are you able to reproduce the problem or is it just happening randomly ?

Ican't reproduce the issue while enable the trace but i can see every 3to4 mins this error message in the systemout log file

 
Thanks in advance

Regards
Sathish  

Hi Satheesh,

  If you are accesing to WAS through Apache or IHS you can check your access.log if I'm not wrong (i need to review) in each line the last data is amount of bytes.
 
  If you enable com.ibm.ws.tcp.channel.impl.*=finest you don't see nothing in traces? and in ffdc files? if you can see every 3 to 4 mins is rare...
 
  Have you review the next web services timeouts?
 
  HTTP transport custom properties for Web services applications
  pic.dhe.ibm.com/infocenter/wasinfo/v7r0/...
 
  Hope this helps.  Tell us if you need more support.
 
Regards

[quote author=208146361 post=537052305]

Hi Joseph,

do you know, if you are writing large data?

No idea, can you please tell me how to check wrting the large data or not

Are you able to reproduce the problem or is it just happening randomly ?

Ican't reproduce the issue while enable the trace but i can see every 3to4 mins this error message in the systemout log file

 
Thanks in advance

Regards
Sathish  [/quote]

check with developers to findout what is the typical post data size they expect.

Strange that you are not able to reproduce but can see it every 3-4mins. it also suggests that data write/read could be slow and when the packets gets accumulated you might be getting a timeout.

• Do a continous 'ping' from source machine to destination machine. This will tell, if network has any role in the issue.


• Check the log on target machine, if you can find any access information related to timeout


• increase read and write timeout by 10-15sec and see if the issue persists.

Hi Gabriel, 

 I have check the timeout values on JVM custom properties(java virtual machine --> custom properties )  for Web services applications.  we didn't configurered any off the follwing properties ..

com.ibm.websphere.webservices.http.connectionIdleTimeout
com.ibm.websphere.webservices.http.connectionKeepAlive
com.ibm.websphere.webservices.http.connectionPoolCleanUpTime
com.ibm.websphere.webservices.http.connectionTimeout
com.ibm.websphere.webservices.http.maxConnection
com.ibm.websphere.webservices.http.responseContentEncoding
com.ibm.websphere.webservices.http.requestContentEncoding
com.ibm.websphere.webservices.http.requestResendEnabled
com.ibm.websphere.webservices.http.SocketTimeout

And before that i had enable the trace using follwing string "*=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:TCPChannel=all:GenericBNF=all" but the issue was not replacate in the logi file ...



 
Please suggest me ..

Thanks
Sathish 

 

Hi Joseph,

Wish You Happy New Year ..

while  'ping' from source machine to destination machine. we didn't see any related to timeout.
 
Also am chceking with developer( typical post data size they expect. ) with the same .....  i will get back to you soon with our findings


Thanks
Sathish
 

Happy new year!

Sure .. also keep an eye on the trends like under what condictions or at what times this issue is occuring.

cheers
Joseph

satheesh

  Your problem is:

  E com.ibm.ws.webcontainer.srt.SRTServletRequest parseParameters SRVE0133E: An error occurred while parsing parameters. {0}
java.net.SocketTimeoutException: Socket operation timed out before it could be completed
at com.ibm.ws.tcp.channel.impl.SocketRWChannelSelector.checkForTimeouts(SocketRWChannelSelector.java:462)
at com.ibm.ws.tcp.channel.impl.ChannelSelector.run(ChannelSelector.java:241)
at java.lang.Thread.run(Thread.java:736)

  please enable next traces:
 
    *=info: com.ibm.ws.tcp.*=finest

  Have you test Joseph's suggestion?
 
    increase read and write timeout by 10-15sec and see if the issue persists.
    
Regards

Hi Gabriel/Joseph,


I need to incerese read and write timeout on all resourses or only webcontainer resusores  ...

HttpQueueInboundDefault 
HttpQueueInboundDefaultSecure 
WCInboundAdmin 
WCInboundAdminSecure 

WCInboundDefault
WCInboundDefaultSecure
 
please corect me if iam wrong ..
 

Thanks
Satheesh  

Satheesh,

  review your application request port and increase read and write timeout in corresponding channel port.
 
  probably
 
  HttpQueueInboundDefault
  HttpQueueInboundDefaultSecure
 
  WCInboundDefault
  WCInboundDefaultSecure
 
  Tuning transport channel services
  pic.dhe.ibm.com/infocenter/wasinfo/v7r0/...
 
  have you enabled traces?
 
  hope this help.
 
regards

We are facing same issue. Was there a solution to this problem?
Error log printing in app server:

[4/26/14 0:08:33:499 EDT] 00000028 srt           E com.ibm.ws.webcontainer.srt.SRTServletRequest parseParameters SRVE0133E: An error occurred while parsing parameters. {0}

                                 java.net.SocketTimeoutException: Socket operation timed out before it could be completed

at (SocketRWChannelSelector.java:462)

                at com.ibm.ws.tcp.channel.impl.ChannelSelector.run(ChannelSelector.java:241)

 

Thanks for taking the time to discuss this, I feel strongly about it and love learning more on this topic. If possible, as you gain expertise, would you mind updating your topic with more information? It is extremely helpful for me.

apparel printing
banners