on 11-13-2009 11:16 AM
Hello Everybody,
I am currently developing a Java Webservice for Netweaver 7.11. The web service should trigger the execution of a jar file which is locally available at the server on which the web service is deployed.
The process which is locally executed needs about 60s to be finished.
But when trying to start this process via a web service I get the following message:
Invalid transport binding settings.Read timed out
But this message still appears if I set the timeout settings to a value of 900s, which is definately long enough.
I would be really thankful if somebody has an idea, where the problem is located and how to solve it.
Kind Regards,
Carl Heckmann
Hi,
Did you expose it as service and configure endpoint properly? this error happen most of them time because of incorrect binding.
please check and respond.
Regards,
Gourav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gouray,
Thanks for your reply. I assume, that I configured it correctly, since I exposed 2 web services with this EJB, and the other one is running just fine.
The code of the EJB can be found below. The Service startDataCollectionProcess does not work, due to the timeout problem. The other service, isSystemOnlineCheck works without any problems.:
package com.sap.nwdemo.sidct.services;
@WebService(name = "SIDCTServicesBean", portName = "SIDCTServicesBeanPort", serviceName = "SIDCTServicesBeanService", targetNamespace = "http://sap.com/nwdemo/sidct/services/")
@Stateless
public class SIDCTServicesBean {
/**
* Starts the data collection process COuld be also started using the
* console
*/
@WebMethod
public Long startDataCollectionProcess() {
SIDCT sidct = new SIDCT();
Long duration = sidct.gatherData();
return duration;
}
@WebMethod
@WebResult(name = "isOnline")
public boolean isSystemOnlineCheck(@WebParam(name = "SID")
String sid, @WebParam(name = "InstanceNumber")
String systemNumber, @WebParam(name = "NetworkID")
int nwguid) {
[....]
}
}
I hope this is enough information for you to tell me if the service is configured properly or not.
Kind Regards,
Carl
I measured the time, the service needs and took this time*10 as timeout value, but still atimeout occured.
The problem is most likely connected to the actual code.
Within the gatherData() method a lot of filesystem operations are executed and also somme HttP-connections are used. Does anybody know if this might cause problems when wrapping this functionality into web services´apart from problems concerning concurrency.
Best Regards,
Carl
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.