You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2009/04/10 00:44:15 UTC
[jira] Assigned: (JS2-893) cluster synchronization feature
[ https://issues.apache.org/jira/browse/JS2-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Sean Taylor reassigned JS2-893:
-------------------------------------
Assignee: Randy Watler (was: David Sean Taylor)
> cluster synchronization feature
> -------------------------------
>
> Key: JS2-893
> URL: https://issues.apache.org/jira/browse/JS2-893
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: Other
> Affects Versions: 2.1.2, 2.1.3, 2.2.0
> Reporter: Joachim Müller
> Assignee: Randy Watler
> Fix For: 2.2.0
>
> Attachments: JS2-893_patch.zip
>
>
> We developed a cluster synchronization feature that is able to synchronize the execution of an objects method cluster-wide. The approach is similar to the spring transaction proxy, so we are able to AOP-inject the cluster synchronization via spring configuration. The component is highly customizable. A new database table is used for synchonization, but any other data container (i.e. broadcast-distributed-hashmap) could be used.
> One main application for this functionality is the start of many jetspeed cluster nodes and synchronize the deployment of the PAs to the database. (Even with the VersionedApplicationManager we experienced DB constraints failures on startup with fresh database, preventing the some PAs from registration.)
> Patch follows (exists only for the 2.1.2-POSTRELEASE branch yet).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org