[ 
https://issues.apache.org/jira/browse/OFBIZ-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111780#comment-14111780
 ] 

Wai commented on OFBIZ-5729:
----------------------------

Pierre,

This is a bug.  It is not a misunderstanding on how to configure a multitenant 
system.

Perhaps my usage of ...

$ ant load-tenant-data-readers -Ddata-readers=seed -DtenantId=DEMO1

gave you the wrong impression that the necessary databases were not already 
configured (eg. ofbiztenant and ofbiz_DEMO1 and ofbizolap_DEMO1).  The 
appropriate data in ofbiztenant (eg. tables TENANT and TENANT_DATA_SOURCE) has 
already been filled.

You can create a fresh tenant using ...

$ ant create-tenant

and ofbiz will hang.

This is clearly a bug.

Wai

> ofbiz hangs on installing tenant database 
> ------------------------------------------
>
>                 Key: OFBIZ-5729
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5729
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Wai
>            Assignee: Adrian Crum
>         Attachments: ofbiz console output-with bug.log, ofbiz console 
> output-with fix.log, ofbiz-5729.patch, ofbiz-5729.patch
>
>
> When installing data into a tenant database, ofbiz hangs.
> Using the following command line.
> $ ant load-tenant-data-readers -Ddata-readers=seed -DtenantId=DEMO1
> The problem is that ofbiz uses DelegatorFactory.getDelegator() to find/create 
> the tenant delegator, asynchronously, for the target tenant database using a 
> single daemon thread.  As part of the tenant delegator creation, it needs to 
> find/create a base delegator.  When the base delegator is intially absent, 
> ofbiz will block trying to create one by using the same daemon thread--which 
> is already being used.  Hence, ofbiz is deadlocked.
> The solution is to make sure that a base delegator is always created first 
> before a find/create tenant delegator is attempted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to