Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Message-ID: <1028369664.1240985490624.JavaMail.jira@brutus>
Date: Tue, 28 Apr 2009 23:11:30 -0700 (PDT)
From: "Randy Watler (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@portals.apache.org
Subject: [jira] Resolved: (JS2-893) cluster synchronization feature
In-Reply-To: <991114190.1215462511810.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JS2-893?page=3Dcom.atlassian.j=
ira.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 retryi=
ng portlet application registrations in both the 2.2 trunk and 2.1.3-POST b=
ranch, (to be 2.1.4).

Fixes included adding retry loop in startPortletApplication APIs and cleani=
ng up prefs cache in the 2.1.3-POST branch. The 2.2 trunk has a new prefs/r=
egistry implementation that did not require any improvements based on the n=
eed 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/o=
r 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=C3=BCller
>            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 synchroniz=
e 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 s=
ynchronization via spring configuration. The component is highly customizab=
le. A new database table is used for synchonization, but any other data con=
tainer (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 fai=
lures on startup with fresh database, preventing the some PAs from registra=
tion.)
> Patch follows (exists only for the 2.1.2-POSTRELEASE branch yet).

--=20
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