Problem in SOAP-RPC call

[FONT=Helv][SIZE=2]This is regarding a problem I am facing in calling service through SOAP-RPC protocol via HTTP transport.
The whole scenarion is as followes:
[FONT=Helv][SIZE=2]–> Our client team gave us two xsd files
[FONT=Helv][SIZE=2]–> I created two Documents/Schema with the help of these xsd files.
–> Taking these documents as input & outputs I created a flow service processFlow :
[FONT=Helv][SIZE=2]–> & then created a wsdl file from this flow service with
Protocol : SOAP-RPC ;
[FONT=Helv][SIZE=2]Using this wsdl file client application is calling processFlow service hosted on the host given in wsdl file & sending a SOAP message
[FONT=Helv][SIZE=2][FONT=Helv][SIZE=2]but here it is throwing exception like this :

Exception in thread “main” javax.xml.rpc.JAXRPCException: Exception while performing call. Read timed outorg.systinet.wasp.client.XMLInvocationException: Exception while processing incoming message message. Read timed out at com.systinet.wasp.client.XMLInvocationHelperImpl._receive(XMLInvocationHelperImpl.java:699) at com.systinet.wasp.client.XMLInvocationHelperImpl._receive(XMLInvocationHelperImpl.java:617) at com.systinet.wasp.client.XMLInvocationHelperImpl._call(XMLInvocationHelperImpl.java:145) at com.systinet.wasp.client.XMLInvocationHelperImpl.call(XMLInvocationHelperImpl.java:77) at org.systinet.wasp.client.XMLInvocationHelper.call(XMLInvocationHelper.java:18) at com.systinet.wasp.rpc.WaspCallImpl.invoke(WaspCallImpl.java:492) at com.systinet.wasp.rpc.WaspCallImpl.invoke(WaspCallImpl.java:450) at com.systinet.wasp.client.ClientProxy._invoke(ClientProxy.java:456) at com.systinet.wasp.client.ClientProxy.invoke(ClientProxy.java:109) at $Proxy61.processFlow(Unknown Source) at com.gehc.WorkOutWSDL.EPDMPOC_ItemInfo_Pub_serviceServiceClient.main(EPDMPOC_ItemInfo_Pub_serviceServiceClient.java:81)Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at com.idoox.transport.util.ReadLine.read(ReadLine.java:46) at com.idoox.transport.http.client.HttpResponse.processResponse(HttpResponse.java:293) at com.idoox.transport.http.client.HttpResponse.letsGo(HttpResponse.java:239) at com.idoox.transport.http.client.HttpResponse.getStatusCode(HttpResponse.java:54) at org.idoox.transport.InputMessageWrapper.getStatusCode(InputMessageWrapper.java:57) at org.idoox.transport.InputMessageWrapper.getStatusCode(InputMessageWrapper.java:57) at org.idoox.transport.InputMessageWrapper.getStatusCode(InputMessageWrapper.java:57) at com.systinet.wasp.lb_cookies_interceptor.InputMessageWrapper.getStatusCode(InputMessageWrapper.java:27) at com.systinet.wasp.client.XMLInvocationHelperImpl._receive(XMLInvocationHelperImpl.java:641)

while previously he was getting this exception

Exception in thread “main” javax.xml.rpc.soap.SOAPFaultException: [ISS.0088.9134] Exception occurred while processing the body of the message at com.systinet.wasp.rpc.FaultDeserializationHelper.deserializeFault(FaultDeserializationHelper.java:106) at com.systinet.wasp.rpc.WaspCallImpl.deserializeFault(WaspCallImpl.java:2208) at com.systinet.wasp.rpc.WaspCallImpl.deserializeResponse(WaspCallImpl.java:1101) at com.systinet.wasp.rpc.WaspCallImpl.invoke(WaspCallImpl.java:508) at com.systinet.wasp.rpc.WaspCallImpl.invoke(WaspCallImpl.java:450) at com.systinet.wasp.client.ClientProxy._invoke(ClientProxy.java:456) at com.systinet.wasp.client.ClientProxy.invoke(ClientProxy.java:109) at $Proxy61.processFlow(Unknown Source) at com.gehc.WorkOutWSDL.EPDMPOC_ItemInfo_Pub_serviceServiceClient.main(EPDMPOC_ItemInfo_Pub_serviceServiceClient.java:79)

Can anybody guess what is the root cause of this problem.
[/size][/font][/SIZE][/FONT][/SIZE][/FONT][/SIZE][/FONT][/SIZE][/FONT][/SIZE][/FONT][/SIZE][/FONT]

No guesses from me without looking at the WSDL and XSD files. Can you consume the service you exposed using an IS web services connector?

BTW, did I mention yet that soap-rpc is baaaaaadddddd.

Mark