Issue Details (XML | Word | Printable)

Key: GLASSFISH-16073
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Joe Fialli
Reporter: Joe Fialli
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

GMS1077 gms total message size is too big (default max is 4MB) is repeated in server log

Created: 22/Feb/11 02:21 PM   Updated: 14/Mar/12 06:04 PM   Resolved: 20/Apr/11 09:38 AM
Component/s: group_management_service
Affects Version/s: 3.1_b43
Fix Version/s: 3.1.1_b01, 4.0_b37

Time Tracking:
Not Specified

Tags: 3-1_exclude 3_1-next
Participants: Bobby Bissett and Joe Fialli

 Description  « Hide

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
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.

Joe Fialli added a comment - 22/Feb/11 02:23 PM

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

Bobby Bissett added a comment - 20/Apr/11 09:38 AM

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