[ https://jira.jboss.org/jira/browse/JBREM-1215?page=com.atlassian.jira.plu... ] David Lloyd updated JBREM-1215: ------------------------------- Workaround Description: Make sure your connection option map includes Options.MAX_INBOUND_MESSAGE_SIZE with a value of 4096. This will prevent the problem. (was: Make sure your connection option map includes Options.MAX_INBOUND_MESSAGE_SIZE with a value of 2048. This will prevent the problem.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBREM-1215?page=com.atlassian.jira.plu... ] David Lloyd commented on JBREM-1215: ------------------------------------ Proper behavior: - Server sends min & max allowed message sizes - Client sends preferred size - If the client preferred size is < min, min is used (both ways) - If the client preferred size is > max, max is used (both ways) - Otherwise, client size is used (both ways) - If the server sizes are not acceptable to the client, the connection is terminated - The greeting message packet must be <= 1400 or so (to accomodate common path MTUs - the client might have a good reason to request a small message size) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira