Hi Senaka, On Mon, May 28, 2012 at 1:17 PM, Senaka Fernando <[email protected]> wrote:
> Hi Charitha, > > With regards to the docs on how to use the JMX API, extract the docs > distribution that was built with the binary distribution that you have, and > click on the "Administration API" link in the Java Docs section of the left > menu. In the API documentation, you'll notice that there is a package with > a jmx part in its name. Go through those and you'll be able to understand > what parameters to use. We have not yet started documenting these (on the > wiki-based docs I mean), and once that's done, these will become more > readable. But, you'll need not be blocked till that's done. > I'm not blocked on these JMX docs and I have already reported some bugs related to JMX functionality. I raised a blocker for docs issue because not having documentation is like feature is not ready from end-user point of view. > > Thanks, > Senaka. > > > On Mon, May 28, 2012 at 11:45 AM, Senaka Fernando <[email protected]> wrote: > >> Hi all, >> >> Please note that the configuration examples have now been added to the >> registry.xml file. This should be available with builds after r128457. >> >> Thanks, >> Senaka. >> >> >> On Mon, May 28, 2012 at 11:39 AM, Charitha Kankanamge >> <[email protected]>wrote: >> >>> Thanks a lot Senaka. >>> >>> On Mon, May 28, 2012 at 10:50 AM, Senaka Fernando <[email protected]>wrote: >>> >>>> Hi Charitha, >>>> >>>> You need to add the following line to the registry.xml. >>>> >>>> <enableJMX>true</enableJMX> >>>> >>>> Please note that we are in the process of improving the configuration >>>> (functionality will stay the same but the configuration will be improved so >>>> that you can turn on/off various MBeans related to registry - compared to >>>> the current which is all or nothing), and you'll have the corresponding >>>> settings in the registry.xml in future packs. As of now, please use the >>>> above configuration. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Mon, May 28, 2012 at 10:32 AM, Charitha Kankanamge < >>>> [email protected]> wrote: >>>> >>>>> I cannot find registry JMX Mbean in this pack hence unable to test JMX >>>>> API. >>>>> >>>>> /Charitha >>>>> >>>>> >>>>> On Fri, May 25, 2012 at 12:26 PM, Aparna Karunarathna <[email protected] >>>>> > wrote: >>>>> >>>>>> Hi Dimuthu, >>>>>> >>>>>> As per an offline discussion with Senaka most of the new features are >>>>>> available on this build. Therefore we are continuing testing on this >>>>>> build. >>>>>> >>>>>> Regards, >>>>>> Aparna >>>>>> >>>>>> On Fri, May 25, 2012 at 11:20 AM, Dimuthu Leelarathne < >>>>>> [email protected]> wrote: >>>>>> > Hi Aparna, >>>>>> > >>>>>> > We - the AppFactory team also experienced that. According to Supun >>>>>> this is >>>>>> > fixed in revision r128159. >>>>>> > >>>>>> > So you can use a pack built before 24th May or wait for the next >>>>>> build >>>>>> > coming after a platform build. >>>>>> > >>>>>> > thanks, >>>>>> > dimuthu >>>>>> > >>>>>> > >>>>>> > On Fri, May 25, 2012 at 11:13 AM, Aparna Karunarathna < >>>>>> [email protected]> >>>>>> > wrote: >>>>>> >> >>>>>> >> Hi, >>>>>> >> >>>>>> >> Following exception was thrown continuously when start the GReg >>>>>> and we >>>>>> >> are able to login to the management console. Currently we are >>>>>> doing a >>>>>> >> smoke test and will report the other issues. >>>>>> >> >>>>>> >> >>>>>> >> org.wso2.carbon.registry.core.exceptions.RegistryException: The >>>>>> path >>>>>> >> >>>>>> >> >>>>>> '/_system/local/repository/components/org.wso2.carbon.system.statistics/services/WorkListService/{ >>>>>> http://wso2.org/worklist/}addTask' >>>>>> >> contains one or more illegal characters (~!@#;%^*()+={}|\<>"',) >>>>>> >> at >>>>>> >> >>>>>> org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:287) >>>>>> >> 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:662) >>>>>> >> >>>>>> >> Regards, >>>>>> >> Aparna >>>>>> >> >>>>>> >> On Fri, May 25, 2012 at 10:54 AM, Evanthika Amarasiri >>>>>> >> <[email protected]> wrote: >>>>>> >> > Noticed the following minor issue while extracting the G-Reg >>>>>> pack. >>>>>> >> > >>>>>> >> > inflating: >>>>>> >> > >>>>>> >> > >>>>>> wso2greg-4.0.0-SNAPSHOT/samples/asset-models/ApplicationModel/handler-def/handlers.xml >>>>>> >> > inflating: >>>>>> >> > >>>>>> >> > >>>>>> wso2greg-4.0.0-SNAPSHOT/samples/asset-models/ApplicationModel/registry-extensions/application.rxt >>>>>> >> > replace >>>>>> >> > wso2greg-4.0.0-SNAPSHOT/samples/asset-models/Populator/build.xml? >>>>>> >> > [y]es, [n]o, [A]ll, [N]one, [r]ename: y >>>>>> >> > inflating: >>>>>> >> > wso2greg-4.0.0-SNAPSHOT/samples/asset-models/Populator/build.xml >>>>>> >> > >>>>>> >> > Regards, >>>>>> >> > Evanthika >>>>>> >> > >>>>>> >> > >>>>>> >> > On Fri, May 25, 2012 at 9:45 AM, Dimuthu Leelarathne < >>>>>> [email protected]> >>>>>> >> > wrote: >>>>>> >> >> >>>>>> >> >> Hi, >>>>>> >> >> >>>>>> >> >> Please find the Greg pack at >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>>> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-141/artifact/JOB1/GREG >>>>>> >> >> >>>>>> >> >> thanks, >>>>>> >> >> dimuthu >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> On Fri, May 25, 2012 at 9:33 AM, Charitha Kankanamge >>>>>> >> >> <[email protected]> >>>>>> >> >> wrote: >>>>>> >> >>> >>>>>> >> >>> Hi Dimuthu, >>>>>> >> >>> Please give us a G-reg pack, we will look into other packs >>>>>> only after >>>>>> >> >>> completing a functional test round of G-Reg. >>>>>> >> >>> >>>>>> >> >>> >>>>>> >> >>> On Friday, May 25, 2012, Dimuthu Leelarathne wrote: >>>>>> >> >>>> >>>>>> >> >>>> Hi Charitha, >>>>>> >> >>>> >>>>>> >> >>>> Next packs are going to be merged. Greg merging is done. We >>>>>> can give >>>>>> >> >>>> you >>>>>> >> >>>> a pack from Bamboo only for Greg if it is blocking. >>>>>> >> >>>> >>>>>> >> >>>> Others are not ready yet. >>>>>> >> >>>> >>>>>> >> >>>> thanks, >>>>>> >> >>>> dimuthu >>>>>> >> >>>> >>>>>> >> >>>> On Thu, May 24, 2012 at 5:44 PM, Charitha Kankanamge >>>>>> >> >>>> <[email protected]> >>>>>> >> >>>> wrote: >>>>>> >> >>>>> >>>>>> >> >>>>> Hi Senaka/Dimuthu, >>>>>> >> >>>>> Will it be possible for us to get a C4 based testable G-reg >>>>>> pack for >>>>>> >> >>>>> testing by tomorrow? We are supposed to start executing the >>>>>> test >>>>>> >> >>>>> scenarios >>>>>> >> >>>>> which we drafted in G-reg QA plan [1] >>>>>> >> >>>>> >>>>>> >> >>>>> >>>>>> >> >>>>> >>>>>> >> >>>>> [1] >>>>>> https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AvhVRxNoCg0KdHRVMm1pM2xLUDREajdHRVlQekJRcUE&pli=1#gid=0 >>>>>> >> >>>>> >>>>>> >> >>>>> Thanks! >>>>>> >> >>>>> Charitha >>>>>> >> >>>>> >>>>>> >> >>>> >>>>>> >> >>>> >>>>>> >> >>>> >>>>>> >> >>>> -- >>>>>> >> >>>> Dimuthu Leelarathne >>>>>> >> >>>> Technical Lead >>>>>> >> >>>> >>>>>> >> >>>> WSO2, Inc. (http://wso2.com) >>>>>> >> >>>> email: [email protected] >>>>>> >> >>>> >>>>>> >> >>>> Lean . Enterprise . Middleware >>>>>> >> >>>> >>>>>> >> >>> >>>>>> >> >>> >>>>>> >> >>> -- >>>>>> >> >>> Charitha Kankanamge >>>>>> >> >>> cell: +94 718 359 265 >>>>>> >> >>> blog: http://charithaka.blogspot.com >>>>>> >> >>> >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> -- >>>>>> >> >> Dimuthu Leelarathne >>>>>> >> >> Technical Lead >>>>>> >> >> >>>>>> >> >> WSO2, Inc. (http://wso2.com) >>>>>> >> >> email: [email protected] >>>>>> >> >> >>>>>> >> >> Lean . Enterprise . Middleware >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> _______________________________________________ >>>>>> >> >> Dev mailing list >>>>>> >> >> [email protected] >>>>>> >> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >> >> >>>>>> >> > >>>>>> >> > >>>>>> >> > _______________________________________________ >>>>>> >> > Dev mailing list >>>>>> >> > [email protected] >>>>>> >> > http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >> > >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> >> -- >>>>>> >> Regards, >>>>>> >> Aparna Karunarathna. >>>>>> >> WSO2 Inc. >>>>>> >> Mobile:0714002533 >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Dimuthu Leelarathne >>>>>> > Technical Lead >>>>>> > >>>>>> > WSO2, Inc. (http://wso2.com) >>>>>> > email: [email protected] >>>>>> > >>>>>> > Lean . Enterprise . Middleware >>>>>> > >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Aparna Karunarathna. >>>>>> WSO2 Inc. >>>>>> Mobile:0714002533 >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Product Manager - WSO2 Governance Registry; >>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> * >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
