[
http://jira.jboss.com/jira/browse/JBAS-5101?page=all ]
Brian Stansberry closed JBAS-5101.
----------------------------------
Resolution: Done
For, AS 5, bundling was re-enabled for the non "-sync" stacks in
multiplexer-stacks.xml. Left off for the "-sync" stacks as these should be used
for lower volume applications, and adding a possible 60ms roundtrip latency to requests is
not the default behavior I want. Users should feel free to enable bundling in those
stacks if their load tests show the load they are driving over the channel justifies it.
For AS 4.2.3, bundling was enabled in the tomcat clustering cache config and in the EJB3
SFSB clustering cache config. Not enabled in the EJB3 entity clustering config, as that
uses REPL_SYNC. Not enabled in cluster-service.xml as 1) that is a low volume channel
that may make synchronous requests and 2) I'm not willing to port JBAS-4997 to
Branch_4_2.
Re-enable JGroups message bundling
----------------------------------
Key: JBAS-5101
URL:
http://jira.jboss.com/jira/browse/JBAS-5101
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-5.0.0.Beta4, JBossAS-4.2.3.GA
For 4.2.0 JGroups message bundling was disabled pending investigation of JGRP-497. That
is fixed in JGroups 2.4.1.SP4. Message bundling improves performance, so we should
re-enable it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira