portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joachim Müller (JIRA) <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-893) cluster synchronization feature
Date Tue, 26 Aug 2008 09:41:45 GMT

    [ https://issues.apache.org/jira/browse/JS2-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625680#action_12625680
] 

Joachim Müller commented on JS2-893:
------------------------------------

The patch should be modified in deployment.xml to use the VersionedApplicationManager instead
of the PortletApplicationManager (or at least set descriptorChangeMonitorInterval to 0). We
experienced in some setups that the DescriptorChangeMonitor fires a startPA() before startPortletApplication
was executed as it was blocked by the cluster synchronization.

Unfortunately startPA() cannot be proxied because it is protected. What about making the method
public so the cluster sync can hook in?

> 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
>            Reporter: Joachim Müller
>            Assignee: David Sean Taylor
>             Fix For: 2.1.2, 2.1.3, 2.2
>
>         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


Mime
View raw message