Skip to main content

JAXRPC 2.0 socket time outs?

5 replies [Last post]
hr_stoyanov
Offline
Joined: 2004-04-01
Points: 0

Doug and all-,
We are trying run some performance tests, which involve JBoss 4.0.2 (uses Tomcat 5 internally) and JAXRPC 2.0. We are getting the below client-side and server-side exceptions.

1) I wonder if there is some socket timeout parameters to be set for JAXRPC 2.0.

2) As s separate question, shall we expect some performance improvements in the next JAX-WS 2.0 for processing ML payloads?

Hristo

---------------------------------------
16:46:13,248 INFO [STDOUT] Jun 21, 2005 4:46:13 PM com.sun.xml.rpc.server.http.
JAXRPCServletDelegate doPost
SEVERE: caught throwable
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer
.java:747)
at org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.d
oRead(InternalInputBuffer.java:777)
at org.apache.coyote.http11.filters.IdentityInputFilter.doRead(IdentityI
nputFilter.java:115)
at org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuff
er.java:712)
at org.apache.coyote.Request.doRead(Request.java:427)
at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.j
ava:283)
at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:379)
at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:298)
at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStrea
m.java:149)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.readFully(JAXRPCSer
vletDelegate.java:697)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.getSOAPMessageFromR
equest(JAXRPCServletDelegate.java:780)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServle
tDelegate.java:365)
at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:8

and these client caught exceptions:
-----------------------------------

JavaCallMethod(Native: 1002 - Java Exception, Native Error 0: javax.xml.rpc.JAXRPCException: HTTP transport error: java.net.SocketException: Connection reset)
JavaCallMethod(Native: 1002 - Java Exception, Native Error 0: java.rmi.RemoteException: JAXRPCSERVLET28: Missing port information; nested exception is: javax.xml.rpc.soap.SOAPFaultException: JAXRPCSERVLET28: Missing port information)
JavaCallMethod(Native: 1002 - Java Exception, Native Error 0: javax.xml.rpc.JAXRPCException: HTTP transport error: java.net.SocketException: Unexpected end of file from server)
JavaCallMethod(Native: 1002 - Java Exception, Native Error 0: javax.xml.rpc.JAXRPCException: HTTP transport error: java.net.ConnectException: Connection timed out: connect)

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
wijetnga
Offline
Joined: 2005-07-16
Points: 0

Hristo,
I am having the same issue. Could you tell me what the performance Eng. did to fix this issue.

Thanks,
Sulo.

hr_stoyanov
Offline
Joined: 2004-04-01
Points: 0

Sulo-,
I remember it to be some conf. entry in the JBoss server.

jitu
Offline
Joined: 2003-06-14
Points: 0

We use standard Servlet framework on the server side, and HttpUrlConnection on the java side. So everything should be fine. Do you see the timeouts when the load is high ?

hr_stoyanov
Offline
Joined: 2004-04-01
Points: 0

Jitu-,
Yes. We do heavy load testing and JAX-RPC 2.0 is part of it. Since we are using JBoss/Tomcat we are aware of a few parameters there than need to be adjusted. My question was if there is something to look into JAX-RPC as well related to timeouts.

Yesterday our performance engineers managed to adjust the server and got rid of the time out exceptions, so it is not an issue anymore, it seems...

Thanks
Hristo

kohlert
Offline
Joined: 2003-06-16
Points: 0

Hristo,

We will look into the socket timeout issue.

As for performance we will be looking into that in a general sense. What exactly do you mean by ML payloads, are you refering to dispatch/provider and message level or something else?

Thanks