[
http://jira.amdatu.org/jira/browse/AMDATU-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11344#comment-11344
]
Ivo Ladage - van Doorn commented on AMDATU-314:
-----------------------------------------------
Attached a patch that resolves the issue. Changes are primarily in removing
excessive read/write locks, which were there for concurrency reasons but still
did not prevent all concurrency issues. Note that concurrency will hardly be an
issue, since tenants are managed by ConfigurationAdmin.
- Removed write locks from create, update and delete methods. Now the tenant is
first created/updated/deleted from the TenantManagementService, then the cache
is updated (instead of completely cleared and reloaded).
- getTenantById now first tries to load tenant from the cache and return it, if
not contained by the cache it invokes TenantManagementService
> Deadlock when creating many tenants from ConfigAdmin
> ----------------------------------------------------
>
> Key: AMDATU-314
> URL: http://jira.amdatu.org/jira/browse/AMDATU-314
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Core
> Affects Versions: 0.1.1
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.3.0-M0
>
> Attachments: tenant.txt, threaddump.txt, threads.txt
>
>
> If you create many tenants (i.e. 100) at once by adding the tenant
> configuration to the org.amdatu.core.tenant.cfg file in the /deploy
> directory, it ends up quite soon in some kind of deadlock situation. The
> dashboard is not accessible anymore and it doesn't create more then just a
> few tenants.s
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
