Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Topic-icon Question Delay Between Invocations [INTEGRATION Rdbms to Wsdl]

More
17 May 2018 03:52 #1 by craigacgomez
Delay Between Invocations [INTEGRATION Rdbms to Wsdl] was created by craigacgomez
Few quick questions regarding the "Delay Between Invocation" parameter in the "INTEGRATION Rdbms to Wsdl" template. I did not find any documentation about the parameter
1. Can I use this to rate-limit HTTP requests to a web service.
2. Assuming this is a time parameter and what is the unit of time? Milliseconds, seconds, minutes?
More
24 May 2018 16:26 #2 by Thomas BLETON
Replied by Thomas BLETON on topic Delay Between Invocations [INTEGRATION Rdbms to Wsdl]
Hello,
In the template "INTEGRATION Rdbms to Wsdl", the "Delay Between Invocation" is the delay (in milliseconds) applied before each webservice call.
By default it is 0 => no delay.

Does this answer your questions?
More
27 May 2018 04:17 #3 by craigacgomez
Replied by craigacgomez on topic Delay Between Invocations [INTEGRATION Rdbms to Wsdl]
Thank you! This works, though the time in milliseconds in doubled. A value of 500 results in a 1 second delay, but it's good enough for my requirements.

Cheers,
Craig
More
29 May 2018 10:46 #4 by Thomas BLETON
Replied by Thomas BLETON on topic Delay Between Invocations [INTEGRATION Rdbms to Wsdl]
It is weird: in my tests the delay is not doubled. Maybe the delay you observe is the delay + the webservice execution time ?

Thomas.
More
30 May 2018 16:01 #5 by Thomas BLETON
Replied by Thomas BLETON on topic Delay Between Invocations [INTEGRATION Rdbms to Wsdl]
Hi, I was just told that the delay *is* actually doubled as you observed (my test case was not showing this up for some reason).
This will be fixed (bug#3446)

Thomas.