NativeSPClustering- shared shibd

[Cantor, Scott]

On 9/13/16, 12:33 PM, "users on behalf of Vedran Bartonicek" <users-bounces at shibboleth.net on behalf of vbartoni at gmail.com> wrote:

>    Thanks for the clarification. In case I manage to find a root cause,will publish to
> this thread.

I looked at the code to refresh my memory, and indeed what it does is use a connection from the pool and if the send() call fails, it does a single retry by fetching another from the pool.

I suppose it's true that if there were that many bad connections in the pool, it would be visible, and I think in practice there just usually aren't because the pool count tends to be very small.

I think there are more here because you're doing what should not be done, using a remote service. The system is incapable of performing at any scale that way, so there are all sorts of reasons it's not workable, and this is just one more.

But I don't generally hard code values like retry counts. If you file a request, it can eventually get exposed as a configuration setting.

-- Scott