Yes, I was correct, when I logged in as ST, I could see these local
registry resources!

On Mon, May 28, 2012 at 10:15 PM, Afkham Azeez <[email protected]> wrote:

> Looks like another funadamental error! In my tenant's registry space, I
> cannot see this resource. Looks like the new statistics persistence code
> has been written without tenant awareness & is storing stuff in the ST
> registry space for all tenants! This will result in clashes & mix ups!
>
>
>
> On Mon, May 28, 2012 at 10:04 PM, Afkham Azeez <[email protected]> wrote:
>
>> [2012-05-28 22:03:56,398] @azeez.org [1] [Application Server]ERROR
>> {org.wso2.carbon.registry.core.jdbc.Repository} -  Failed to add new
>> Collection
>> /_system/local/repository/components/org.wso2.carbon.system.statistics/services/ProductionSchedulingServiceThere
>> already exist non collection resource.
>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to add
>> new Collection
>> /_system/local/repository/components/org.wso2.carbon.system.statistics/services/ProductionSchedulingServiceThere
>> already exist non collection resource.
>>  at
>> org.wso2.carbon.registry.core.jdbc.Repository.addEmptyCollection(Repository.java:1146)
>> at org.wso2.carbon.registry.core.jdbc.Repository.add(Repository.java:1010)
>>  at
>> org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:328)
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:709)
>>  at
>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.put(CacheBackedRegistry.java:415)
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:649)
>>  at
>> org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.persistOperationStatistics(StatisticsPersistenceScheduler.java:208)
>> at
>> org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.invoke(StatisticsPersistenceScheduler.java:37)
>>  at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.invokeCarbonDeploymentSchedulerExtenders(CarbonDeploymentSchedulerTask.java:101)
>>  at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:71)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>  at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:680)
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>**
email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to