[
https://issues.apache.org/jira/browse/OFBIZ-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022712#comment-13022712
]
Lon F. Binder commented on OFBIZ-4242:
--------------------------------------
We did some preliminaries, but the changes were co-mingled with a number of
others, so I don't have clean profile data.
One thing I can say is that the system startup is substantially faster.
Another benefit is that when the cluster is out of sync, which we've seen
numerous times after a crash due to extremely high load, the re-synchronization
is much faster because instead of waiting 60+ seconds for each component, it is
only 60+ for the selected components (in our case 4 vs. ~30).
> CatalinaContainer Doesn't Respect <distributable/> Node for web.xml files.
> --------------------------------------------------------------------------
>
> Key: OFBIZ-4242
> URL: https://issues.apache.org/jira/browse/OFBIZ-4242
> Project: OFBiz
> Issue Type: Bug
> Components: ALL APPLICATIONS
> Affects Versions: Release 09.04
> Reporter: Lon F. Binder
> Assignee: Jacques Le Roux
> Labels: cluster, clustering, tomcat
> Attachments: ofbiz-4242-patch.txt
>
>
> Per the servlet specification, the {{web.xml}} file should allow an optional
> {{<distributable/>}} node to indicate that the application is clusterable.
> Currently, OFBiz does not respect this setting and assumes all applications
> should be distributed if any cluster configuration is provided in the
> {{ofbiz-containers.xml}} file. As a result, if, for example, the
> {{DeltaManager}} is enable, all applications attempt to cluster and
> communicate via {{DeltaManager}}.
> The expected and proper functionality is to check the individual
> application's web.xml file for the {{<distributable/>}} node and only use the
> {{DeltaManager}} if found; otherwise the {{StandardManager}} should be used
> for sessions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
