cancel
Showing results for 
Search instead for 
Did you mean: 

WebService not returning results in some circumstances

Former Member
0 Kudos

Hello,

we observe a strange behaviour of WebServices on Netweaver 7.10 SP4. Results of the call are not returned in the variables in some special circumstances.

When the WebService works:

Servlet -> JNDI Lookup to Bean -> Bean -> Injection of WebService -> WebService

When the WebService sometimes fails (3 of 5 parallel calls fail)

Servlet -> Plain Java Class -> JNDI Lookup to Bean -> Bean -> Injection of WebService -> WebService

What we can see in the response from ABAP system that hosts the service is, that in returns a result all the time. We can see the result in the HTTP response. Here is the code we use to call the webservice:


public 	void Login(String username, String password, byte[] deviceId, byte[] physicalId, Holder<String> description, 
			              Holder<String> errorCode, Holder<byte[]> sessionId, 
			              Holder<String> validationStatus){
	WEBSERVICE webservice = service.get_SERVICE_Port();

	BindingProvider bp = (BindingProvider)webservice;
	bp.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, username);
	bp.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, password);

        webservice.Login(deviceId, physicalId, description, errorCode, sessionId, validationStatus);

	if (TRACE.beInfo()) {
		String result = "Username: " + username + " Thread: " + Thread.currentThread();
		result += ", DeviceId: " + new String(deviceId) + ", PhysicalId: " + new String(physicalId);
		result += ", Description: " + description.value + ", ErrorCode: " + errorCode.value;
		result += ", SessionId: " + sessionId.value + ", ValidationStatus: " + validationStatus.value;
		LogRegistry.LOGGING.log(Severity.INFO, TRACE, MSGCollection.WS_RESULT(), new Object[] {"Login", result});
	}
}

You can see that we log the results to the Netweaver logging. We don't get any exception in the calls. Resulting logs look like:

successfull call:

WS Login Result: Username: USER315 Thread: HTTP Worker [5], DeviceId: , PhysicalId: , Description: , ErrorCode: , SessionId: [B@3618e213, ValidationStatus:

failed call:

WS h2oLogin Result: Username: USER313 Thread: HTTP Worker [4], DeviceId: , PhysicalId: , Description: null, ErrorCode: null, SessionId: null, ValidationStatus: null

As you cann see in the second case all variables are null. Anny idea what may cause that behaviour??

Thanks,

Frank

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Problem was solved by updating to SP 5 and applying Note 1152973.