[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
|Fix Version/s:||3.1.1_b01, 4.0_b37|
|Reporter:||Joe Fialli||Assignee:||Joe Fialli|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
An attempt to send a message larger than GMS max message size results in repeated reporting of the WARNING
Here is sample message:
[#|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.
% 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
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).