[ 
https://issues.apache.org/jira/browse/JS2-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Randy Watler resolved JS2-893.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.4

PAM implementations are now capable of successfully rolling back and retrying 
portlet application registrations in both the 2.2 trunk and 2.1.3-POST branch, 
(to be 2.1.4).

Fixes included adding retry loop in startPortletApplication APIs and cleaning 
up prefs cache in the 2.1.3-POST branch. The 2.2 trunk has a new prefs/registry 
implementation that did not require any improvements based on the need to 
recover successfully from failed registrations.

2.1.3 svn commit: 769669
2.2 svn commit: 769670

The new service proposed as a fix for these problems was not encorporated. A 
new JIRA issue should be created to donate the service into the 2.2 and/or 
2.1.4 if that is still desired.

> 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.1.4, 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-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org

Reply via email to