Hi Oliver,
Sorry for the late reply.
The best answer I could give you is, when you consider concurrent access
limitation it requires for the same throttle mediator 'id' to be called
on the response flow as well so that it could deduct those messages from
the available limit. If the ids won't match the deduction would not be
done and the messages would be allowed to pass through. As Indika stated
you can get a better idea from the
http://synapse.apache.org/Synapse_Configuration_Language.html.
<http://synapse.apache.org/Synapse_Configuration_Language.html>
I hope this will help you to solve you problem to some extent.
Thanks,
Evanthika.
Olivier Ziller wrote:
thanks Evanthika, i will do that
could you tell me why we have do add this on the out sequence?
regards
Evanthika Amarasiri a écrit :
Hi Oliver,
I see a small issue with your configuration. I think you should put
the following in your <out> mediator.
*<throttle id="id"/>
*(Note that this will not have any affect on the error that you get
as I can see. Just pointing it out..)
For example in your configuration, you should have the throttle id
tag in the out mediator for it to work properly.
<syn:sequence statistics="enable" name="seq_esb-test-opi"
trace="enable">
<syn:in>
....
<syn:throttle id="TG_OPI">
<syn:policy>
<wsp:Policy
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
....
</syn:throttle>
</syn:in>
<syn:out>
*<throttle id="TG_OPI"/>*
<syn:send/>
</syn:out>
</syn:sequence>
Thanks,
Evanthika
Asankha C. Perera wrote:
Hi Olivier
i still have this problem...
what i have forgot is that each of my synapse servers are behind an
apache reverse proxy.
and i'm wondering if this proxy could not cause the problem?
Yes, this seems like the culprit! I cant imagine that Apache
mod_proxy does not understand http 1.1 chunked encoding.. maybe its
just a configuration setting you need to enable
asankha
