on 08-28-2018 5:32 PM
Dear all,
I am currently developing an iflow which is accessing some SOAP methods and some OData services. The SOAP methods are all part of the same service and therefore share the same wsdl. The methods are called in different parts of the iflow and therefore there are multiple receivers. Everything worked fine until today. Suddenly I noticed the following error at all the soap channels:
"multiple receiver channels should not use the same wsdl port name"
I can not believe that I still have to "duplicate" the wsdls as suggested in this two years old archived post:
https://archive.sap.com/discussions/thread/3862699
Does anyone know a solution for this?
Many thanks in advance
Tim
Hello Tim,
As per my understanding 2 year old post holds true,you need to follow the steps mebtioned in that post.
Regards,
Sriprasad Shivaram Bhat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sriprasad,
not really! As stated in my previous post the error only shows up when you manually change the default timeout of the channel. In case you stick with the default setting it works fine (at least in my case with three receivers / channels). So in my opinion its a bug in the SOAP adapter.
kind regards
Tim
Ok I found out that this error pops up when setting the timeout of the channel to something different than the default 60000ms. In my case due to a socket timeout I wanted to increase the timeout to 120000ms for all three channels and after that the mentioned error showed up. From my point of view this is appears to be a bug in the SOAP adapter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.