1. If max-connection is set to 800 on server-side.
When the server reaches the max-connection, it rejects any new client
connections. That means any client trying to connect to the server may be
unable to do so...If you expect more than 800 client connection at any
time, you can increase this by ch
In my opinion, 1MB is too big. I believe it will cause congestion on the
network. Keep to a moderate size on the order of less than 100K.
--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: +1-631-835-4771
On Mon, Feb 6, 2017 at 9:20 PM, Goutam Tadi wrote:
> Hi,
>
> I have a coupl
Thank you for the info.
On Mon, Feb 6, 2017 at 2:05 PM Barry Oglesby wrote:
> The max-connections property configures the maximum number of client
> connections that can be created on a server.
>
> If a set of clients is attempting to create >800 connections to the same
> server either during an
The max-connections property configures the maximum number of client
connections that can be created on a server.
If a set of clients is attempting to create >800 connections to the same
server either during an operation or while prefilling its pool of
connections, a warning like this is logged on
Hi,
I have a couple of questions regarding max-connections attribute in
cache.xml.
1. If max-connections is set to 800 by default, does that mean if I have
800+ region.put() methods from multiple clients in parallel, Will this
cause issue to some of the inserts or requests from server ?
2. If I
