[GLASSFISH-16073] GMS1077 gms total message size is too big (default max is 4MB) is repeated in server log Created: 22/Feb/11  Updated: 14/Mar/12  Resolved: 20/Apr/11

Status: Resolved
Project: glassfish
Component/s: group_management_service
Affects Version/s: 3.1_b43
Fix Version/s: 3.1.1_b01, 4.0_b37

Type: Bug Priority: Minor
Reporter: Joe Fialli Assignee: Joe Fialli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3-1_exclude, 3_1-next


An attempt to send a message larger than GMS max message size results in repeated reporting of the WARNING
in server.log.

Here is sample message:
[#|2011-02-22T17:06:00.412-0500|WARNING|glassfish3.1|ShoalLogger|_ThreadID=24;_ThreadName=Thread-1;|GMS1077: total message size is too big: size = 12,584,300, max size = 4,196,352|#]

[#|2011-02-22T17:06:00.548-0500|WARNING|glassfish3.1|ShoalLogger|_ThreadID=32;_ThreadName=Thread-1;|GMS1077: total message size is too big: size = 12,584,366, max size = 4,196,352|#]



A workaround exists if the default max gms message size is too small.
To create a cluster with a larger max message size, use the following command:

% asadmin create-cluster --properties "GMS_MAX_MESSAGE_LENGTH=8200000" theClusterName


To increase the max message size for an already created cluster, use the following command with cluster running.

$ asadmin set clusters.cluster.myCluster.property.GMS_MAX_MESSAGE_LENGTH=8200000
Command set executed successfully.

After setting the value, stop the cluster and DAS domain, then restart the DAS and the cluster with the new settings.

Comment by Joe Fialli [ 22/Feb/11 ]

Fix is already known for this issue and is checked into shoal gms trunk.

Comment by Bobby Bissett [ 20/Apr/11 ]

This was integrated into GF in rev 45770 (before 3.1.1 branch was created).

Generated at Wed Oct 07 17:55:40 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.