Top Navigation
i

2 instances of G-reg share with one dattabase

I am running two instances of G-reg on two machines. Both instances are pointing to a central Oracle DB, and I am having issues with the external roles. I created a new external role through one instance called "developer role" but I didn't see it on the second instances, even after a refresh. However, the external source configuration did show up..and synch up between both instances.

Also, I am getting permission denied to browse the registry even though I logged in as an admin? Question, can we run two G-reg instances against one DB? if so, do we need to do extra config?

Thanks in advance.
Tony

Re: 2 instances of G-reg share with one dattabase

Hi Tony,

Yes you can run two instances against the same database. Have you also made sure that the database instances which are pointed to from the user management (found in conf/user-mgt.xml) are the same as well?

More information can be found at [1].

[1] http://wso2.org/project/registry/3.0.2/docs/installation_guide/db_oracle.html#Setup-Conf

Thanks,
Senaka.

I found out the problem.

I found out the problem. Both of my instances are pointing to the same oracle DB (I updated the registry.xml and user-mgt.xml) but no luck. Then, I started out another brand new installation (unzip the zip file to a new directory on both machines). Then, I modified the registry.xml and user-mgt.xml before STARTING the registry. it worked now. Somehow, if I started the registry using H2 first, it caused the unexpected problem even though I used the wso2server -cleanCache.

Anyways, the second problem is still here, the Admin does not have the permission to browse the resource / on both instances? See exception below.

[2009-12-31 09:43:32,157] INFO - 'admin' logged out at [2009-12-31 09:43:32,01
57]
[2009-12-31 09:43:37,438] INFO - 'admin' logged in at [2009-12-31 09:43:37,043
8] from IP address 10.1.3.28
[2009-12-31 09:43:39,782] ERROR - User admin is not authorized to read the resources /.

Once I shutdown one instance and restart the second one, admin user can browse the resource /.

Re: I found out the problem.

Hi Tony, I believe that the second problem, is due to the in-memory permission model not-syncing with the changes at the persistence layer, in a duly manner. There was some discussion related to fixing this issue, using some synchronisation mechanism. We are looking forward to fix this for a future release. Thanks, Senaka.

Senaka, Thanks for the

Senaka, Thanks for the reply, I have tried some more and found out that when i pointed my registry to Oracle, I was getting more permission issue such as "unable to browse registry" and could not get into the "add a service" panel. Even though on single instance. Then, I switched back to H2, and everything worked fine. Thanks.

Re: Senaka, Thanks for the

Great. You are welcome. Thanks, Senaka.
cloud bb