File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

getParameter() gives error SRVE0133E

 
Steve McCain
Ranch Hand
Posts: 45
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Using WAS 5.1 on Solaris.

In about 0.5% of POST requests to a servlet I get a SVRE0133E error on the first call to getParameter().
Advice on why these occasional errors occur & what to do about them would be much appreciated.

Full details of the error as follows:-
[10/07/04 02:16:12:603 BST] 1c5ee67 SRTServletReq E SRVE0133E: An error occurred while parsing parameters. java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.ibm.ws.io.Stream.read(Stream.java:17)
at com.ibm.ws.io.ReadStream.read(ReadStream.java:177)
at com.ibm.ws.http.ContentLengthInputStream.read
ContentLengthInputStream.java:32)
at com.ibm.ws.io.ReadStream.read(ReadStream.java:177)
at com.ibm.ws.webcontainer.http.HttpConnection.read(HttpConnection.java:
340)
at com.ibm.ws.webcontainer.srp.SRPConnection.read(SRPConnection.java:200
)
at com.ibm.ws.webcontainer.srt.SRTInputStream.read(SRTInputStream.java:8
0)
at com.ibm.ws.webcontainer.srt.http.HttpInputStream.read(HttpInputStream
.java:309)
at com.ibm.ws.webcontainer.servlet.RequestUtils.parsePostData(RequestUti
ls.java:517)
at com.ibm.ws.webcontainer.srt.SRTServletRequest.parseParameters(SRTServ
letRequest.java:789)
at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServlet
Request.java:412)
at enquiriescontrol.EnquiryControl.performTask(EnquiryControl.java:60)
at enquiriescontrol.EnquiryControl.doPost(EnquiryControl.java:36)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(Stric
tServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(Stric
tLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecy
cleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(Strict
LifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstan
ce.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(V
alidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(Ser
vletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDi
spatch(WebAppRequestDispatcher.java:974)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAp
pRequestDispatcher.java:555)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebApp
 
Steve McCain
Ranch Hand
Posts: 45
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Occasionally I find a similar error:

[20/07/04 09:51:45:293 BST] d74b31 SRTServletReq E SRVE0133E: An error occurred while parsing parameters. java.io.IOException: post body contains less bytes than specified by content-length
at com.ibm.ws.webcontainer.servlet.RequestUtils.parsePostData(RequestUtils.java:521)
at com.ibm.ws.webcontainer.srt.SRTServletRequest.parseParameters(SRTServletRequest.java:789)
at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServletRequest.java:412)
at enquiriescontrol.EnquiryControl.performTask(EnquiryControl.java:90)
at enquiriescontrol.EnquiryControl.doPost(EnquiryControl.java:40)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
etc

Any help would be appreciated.
 
john randolf
Greenhorn
Posts: 1
  • 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i had the exact same problem...It was KILLING our production system. it was happening to anyone with a modem....heres the fix :


Increase the value of the ConnectionIOTimeOut parameter to avoid receiving an exception when hosting Web services on WebSphere Application Server

When hosting Web services on WebSphere Application Server, you can receive the following exception: java.long.SocketTimeOutException: Read Timed Out.

A slow network connection between the client and the Web service causes this problem. In such cases, the HTTP socket might time out before the Web service engine completely reads the SOAP request. Sudden increases in overall network activity cause this problem inmost cases. The problem can also occur when the client is accessing the Web service from a slow network connection and in situations where the amount of data in the SOAP request is large.

To solve the problem, increase the ConnectionIOTimeOut parameter for your Web container HTTP transport. The default value is 5 seconds. You can increase the value 30 seconds or greater. Set the value using the administrative console. Click Servers > Application Servers > server_name > Web Container > HTTP Transports > port_number > Custom Properties > New. Type the following property name and value:

* Name: ConnectionIOTimeOut
* Value: 30

If the Web service is hosted in a clustered environment, set the property on each application server in the cluster. If your application server is listening on more than one port number, set the property on all ports.


http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?tab=search&searchWord=SRVE0133E+SocketTimeoutException%3A+Read+timed+out+x=8&maxHits=54
 
Steve McCain
Ranch Hand
Posts: 45
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Many thanks for the advice John. I made the change about four days ago &
have not seen any more SocketTimeOut problems since, so it looks like its fixed!!



cheers

Steve
 
David Ulicny
Ranch Hand
Posts: 724
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are running WAS 5.0 on iSeries.

We have the same problem, the error SRVE0133E. The application is running,
but the http plugin and http server (Apache for iSeries 2.0.47) look like dead. They do not any logs. The administration console is unavailable too. Do you know why is the Admin console unavailable?
Is the problem in Http Transport?

Any help would be appreciated.
 
rohit chavan
Ranch Hand
Posts: 132
Hibernate Java Oracle
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
john randolf wrote:i had the exact same problem...It was KILLING our production system. it was happening to anyone with a modem....heres the fix :


Increase the value of the ConnectionIOTimeOut parameter to avoid receiving an exception when hosting Web services on WebSphere Application Server

When hosting Web services on WebSphere Application Server, you can receive the following exception: java.long.SocketTimeOutException: Read Timed Out.

A slow network connection between the client and the Web service causes this problem. In such cases, the HTTP socket might time out before the Web service engine completely reads the SOAP request. Sudden increases in overall network activity cause this problem inmost cases. The problem can also occur when the client is accessing the Web service from a slow network connection and in situations where the amount of data in the SOAP request is large.

To solve the problem, increase the ConnectionIOTimeOut parameter for your Web container HTTP transport. The default value is 5 seconds. You can increase the value 30 seconds or greater. Set the value using the administrative console. Click Servers > Application Servers > server_name > Web Container > HTTP Transports > port_number > Custom Properties > New. Type the following property name and value:

* Name: ConnectionIOTimeOut
* Value: 30

If the Web service is hosted in a clustered environment, set the property on each application server in the cluster. If your application server is listening on more than one port number, set the property on all ports.


http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?tab=search&searchWord=SRVE0133E+SocketTimeoutException%3A+Read+timed+out+x=8&maxHits=54
It is still usefull after 9 years , the navigation path has changed a bit on the console that's it. Thank you John!
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic