You can probably do what you want via the security API's  but it is a bit
messy and more complicated. One alternative is to use server groups which a
client then must also configure to direct traffic/connections to specific
servers but also doesn't limit the number of connections a client can make
to any given server. A third external option is probably to use something
like iptables to  prevent the connections in the first place but this can
be a pain to configure and inflexible for a cluster setup.

*Vince Ford*
GemFire Sustenance Engineering
Beaverton, OR USA
503-533-3726 (office)
http://www.pivotal.io
Open Source Project Geode https://geode.incubator.apache.org/
<https://network.pivotal.io/products/project-geode>

On Thu, Oct 1, 2015 at 2:34 PM, Vinay Upadhya <[email protected]> wrote:

> Thanks Darrel. My question is more about trying to limit it from the
> server side in an attempt to stop rogue clients outside the jurisdiction of
> the Gemfire server owners.
>
> *Vinay Upadhya *| Sr. Field Engineer
>
> 917-514-1842 | [email protected] | Pivotal Software Inc.
> <http://www.pivotal.io/>
>
> On Oct 1, 2015, at 5:29 PM, Darrel Schneider <[email protected]>
> wrote:
>
> You can do this on the client side. It is part of the client pool
> configuration.
> We have a number of ways to configure this pool. You can do it with
> cache.xml or apis. You can probably do it with Spring.
>
> If you are using the ClientCacheFactory API then you would do it
> with 
> com.gemstone.gemfire.cache.client.ClientCacheFactory.setPoolMaxConnections(int)
>
> Hope this answers your question.
>
>
> On Thu, Oct 1, 2015 at 2:10 PM, Vinay Upadhya <[email protected]> wrote:
>
>> Hello,
>>
>> We have the max-connections property on the cache-server tag on a geode
>> server which limits the incoming connections to that number. Is there a way
>> however to assign a certain number of maximum connections per client
>> connecting to a node?
>>
>> *Vinay Upadhya *| Sr. Field Engineer
>>
>> 917-514-1842 | [email protected] | Pivotal Software Inc.
>> <http://www.pivotal.io/>
>>
>>
>
>

Reply via email to