on 03-20-2014 10:18 AM
Hi All,
I have developed a Synchronous ABAP proxy to SOAP web service scenario.
ECC sends an ABAP proxy request to PI, PI forwards the request to the target system as SOAP message.
I have checked the interface via SOAP UI and it works fine but when we run the end-to-end flow it always ends with a Synchronous timeout error.
The Target system confirms that the response is sent from there side but in PI we are not receiving any response and the system throws a timeout error.
As both PI and the Target system are in same Landscape there is no firewall in between.
Please suggest what can be the possible reasons and the approach to resolve the same?
Thanks in advance,
Shashank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
when you test the scenario from SOAPUI what is the response time?
Regards,
Muni.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If you have gone through the document I sent, you'll find that your issue is in section 2.2.7 Messaging System Times out
Potential cause for the error:
The parameter: 'xiadapter.inbound.timeout.default' is an Adapter Engine messaging
system parameter. The value specifies how long the messaging system waits for a response during
synchronous communication. If this time elapses, a "MessageExpired" exception is triggered.
This parameter will apply to all synchronous messages going through the Adapter Engine messaging
system.
Proposed Solution:
Set property of Service "XPI Adapter: XI" within SAP NetWeaver Administrator
xiadapter.inbound.timeout.default
Default: 180000 [ms]
Note
If this parameter value is not increased to > 3 minutes then the messages will
continue to timeout with the message expired exception.
In NWA, Go to->Operation Management->Systems-> Start & Stop -> Java Services -> (Under Related
Tasks) Java System Properties.
Hope this helps,
Mark
Hi Shashank,
I recently came up with similar error. in my case it was issue with firewall. port was not opened.
go to check the receiver communication channel log. i am sure it would give error like 'unable to create socket".
FYI you have shared the error which happened in the RWB testing.
quick check will be log into your pi os level and telnet the target server with corresponding port.
Regards,
Muni.
Also as target is in same landscape as PI we are not using any credential to hit the Web URL.
But we have some asynchronous scenario in which when the same target system hits the PI URL they need credentials, so will it be required even for a synchronous scenario where PI posts the data and waits for response in the same session?
Hi,
I have attached the receiver communication channel snapshot, there is no firewall between the systems as both are in same landscape, also no username-pass is required to send the request.
We tried at the OS level from PI server cmd window to trigger the request and we received successful response, which confirms that PI server is able to get the response but still I get time out when i trigger the data.
Please correct me if i am wrong but the last thing now i can think of is as the SOAP channel is on Java Stack and to access that target system needed credentials for one inbound interface so even for this sync scenario the target system should maintain it some where when the response is sent back to PI.
Regards,
Shashank
Hi,
The response is received with in a second be it via SOAP UI or PI server cmd. By default the timeout is set to 3 minutes in PI. I am not understanding the purpose of increasing the time out here.
Please let me know if my below understanding is correct or not
"The target system needed credentials for one inbound interface, so for this synchronous scenario(PI<->Target) should the target system maintain credentials some where when the response is sent back to PI as the SOAP channel is on Java Stack?"
Hi,
"The target system needed credentials for one inbound interface, so for this synchronous scenario(PI<->Target) should the target system maintain credentials some where when the response is sent back to PI as the SOAP channel is on Java Stack?"
Generally for receiver channel we get the user name and password from target system ie web service.
How did you test in SOAPUI? did you test it with providing username and password or not?
even if web service requires user/pwd then it will throw 401 unauthorized error.
check this
can you go to RWB-->component monitoring-->adapter Engine-->communication channel monitoring-->your channel
check if the channel has any errors/exceptions logs.
Regards,
Muni.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.