[
http://jira.amdatu.org/jira/browse/AMDATU-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11286#comment-11286
]
Marcel Offermans commented on AMDATU-314:
-----------------------------------------
Regarding 2: I have debugged quite a few cases where indeed the callbacks that
the DM triggers cause deep stack traces that show deadlocks in code that uses
DM. I have taken great care inside DM not to hold on to any locks when calling
code that is outside my control. Typical scenarios I see are related to holding
locks while:
a) invoking other services, which is never save since you have no clue what
happens there;
b) invoking the DM, specifically DM.add(Component) that might register a
service and invoke callbacks on dependencies that were waiting for it.
> 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, 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
