[Stratos-dev] Major issue of multiple users accessing the admin console on stratos
ruwan at wso2.com
Mon Nov 8 20:33:57 PST 2010
On 11/9/10 9:56 AM, Sumedha Rubasinghe wrote:
> On Tue, Nov 9, 2010 at 8:52 AM, Ruwan Linton <ruwan at wso2.com
> <mailto:ruwan at wso2.com>> wrote:
> I would like to draw the $subject to your attention.
> Basically non of our admin services are designed to work with
> multiuser access.
> We do support multi user access. But the problem is, all of us use the
> admin account.
> Could you explain a scenario where this effects the functionality of
> the console? well... I am talking more on the standalone case..
Even if you log into the same standalone server with the same admin
account by 2 users, this problem is there. This is not a problem of
stratos, this has been there from the start of the admin services but
now with stratos the probability of this happening is very high, since
we have a single instance.
Registry might not have this issue, since registry ultimately works with
a DB and is transactional.
> On stratos this might be a major hit since we promote it as a
> multiuser platform.
> Just to make it clear this is not an issue of multitenancy, but if
> 2 users of a single tenant logs into the same stratos service
> simultaneously and tries to do some activities on the management
> console they will most of the time get dead pages or if the code
> is written properly an error page.
> Synchronizing the all the admin service methods blindly will not
> solve this issue, since the elements that we access from different
> places might cause the issue, for example one user could re-load
> the synapse configuration, while the other user tries to add a
> proxy, and if the re-loading action got started first, the adding
> proxy action will get an error.
> One sub optimal solution to this issue is to queue admin requests
> for a given tenant configuration and let the admin requests
> execute sequentially, because if we are to do the optimal solution
> implementation we need to find all the clashing actions and
> synchronize them with a single lock, which is out of the scope of
> this release I guess.
> Thoughts please??
> Ruwan Linton
> Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
> phone: +1 408 754 7388 ext 51789
> email: ruwan at wso2.com <mailto:ruwan at wso2.com>; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> tweet: http://twitter.com/ruwanlinton
> Stratos-dev mailing list
> Stratos-dev at wso2.org <mailto:Stratos-dev at wso2.org>
Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ruwan at wso2.com; cell: +94 77 341 3097
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Stratos-dev