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 "Randy Watler (JIRA)" <je...@portals.apache.org> on 2009/06/15 20:45:07 UTC
[jira] Resolved: (JS2-1033) Deadlock during PAM initialization
between java prefs and database row locks
[ https://issues.apache.org/jira/browse/JS2-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randy Watler resolved JS2-1033.
-------------------------------
Resolution: Fixed
Issue resolved by initializing empty registry with root preferences for portlet applications and entities.
Also modified initialization of preferences provider to ensure preloading was done within transaction scope. API modification was made to distinguish between init() and preload() functionality and transaction requirements.
SVN commit: 784908
> Deadlock during PAM initialization between java prefs and database row locks
> ----------------------------------------------------------------------------
>
> Key: JS2-1033
> URL: https://issues.apache.org/jira/browse/JS2-1033
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Portlet Registry
> Affects Versions: 2.1.3
> Environment: Multiple Core Linux x86-64
> Jetspeed 2.1.3
> Initial Deployment
> Reporter: Randy Watler
> Assignee: Randy Watler
> Fix For: 2.1.4
>
>
> Deadlock occurs between java prefs and database row locks when root PAM preferences entries are included in multiple write transactions in initial system startup when multiple PAs are registering concurrently.
--
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