Re: [Dev] [MB4] Removing Hazelcast dependency from common coordination tasks
+1 On Mon, Aug 21, 2017 at 12:58 PM, Asanka Abeyweera <asank...@wso2.com> wrote: > Hi all, > > We are still using Hazelcast for some common tasks even though we > alternatively have the RDBMS based coordination implementation. I am > planning to refactor code to remove those Hazelcast tasks in MB4. > > I could see that we are using Hazelcast for following tasks, > >- Hazelcast node addresses are maintained in Node details for >consumption by an MBean service. Since we are planning to use REST services >as an alternative to admin service, we can get rid of this. Additionally, >in a non-Hazelcast environment, it does not make sense to maintain the >Hazelcast node addresses. >- To check if the node IDs are duplicated, a Hazelcase map is >maintained. We can remove this when we use the RDBMS based coordination. >- A unique ID generated using a Hazelcast ID generator is used as a >parameter in generating cluster-wide unique IDs. Since we are focusing >mainly on the 2 node HA deployment we do not need a cluster-wide unique >message ID. If we need a cluster-wide unique ID we can later implement an >algorithm on top of the RDBMS based coordination. > > > WDYT? > > -- > Asanka Abeyweera > Senior Software Engineer > WSO2 Inc. > > Phone: +94 712228648 <071%20222%208648> > Blog: a5anka.github.io > > <https://wso2.com/signature> > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while building the product-is
ples . SKIPPED >> [INFO] scim-provisioning .. SKIPPED >> [INFO] Identity Server : OAuth 1.0a samples with Identity Server SKIPPED >> [INFO] WSO2 Carbon - OAuth10a Resource Owner Equivalent ... SKIPPED >> [INFO] Identity Server : OAuth2.0 Samples with Identity Server 5.2.0 >> SKIPPED >> [INFO] OAuth 2.0 Playground App with WSO2 Identity Server 5.2.0 SKIPPED >> [INFO] OAuth 2.0 Custom Grant . SKIPPED >> [INFO] Identity Server : SSO Samples .. SKIPPED >> [INFO] Travelocity.COM ServiceProvider / RelyingParty Webapp SKIPPED >> [INFO] Identity Server : XACML Samples SKIPPED >> [INFO] WSO2 Entitlement Sample Online Trading . SKIPPED >> [INFO] Identity Server : STS Samples .. SKIPPED >> [INFO] STS Client . SKIPPED >> [INFO] Identity Server : Passive STS Samples .. SKIPPED >> [INFO] PassiveSTSSample ... SKIPPED >> [INFO] org.wso2.identity.passivests.filter SKIPPED >> [INFO] PassiveSTSSampleApp SKIPPED >> [INFO] Identity Server : InfoRecoverySample Maven Webapp .. SKIPPED >> [INFO] InfoRecoverySample Maven Webapp SKIPPED >> [INFO] Identity Server : Workflow Samples . SKIPPED >> [INFO] sample-handler . SKIPPED >> [INFO] Identity Server Integration Tests .. SKIPPED >> [INFO] WSO2 IS - Integration Test Admin Clients Module SKIPPED >> [INFO] WSO2 IS - Integration UI Pages Module .. SKIPPED >> [INFO] WSO2 IS - Integration Test Utils Module SKIPPED >> [INFO] Custom Attribute Finder SKIPPED >> [INFO] WSO2 Identity Integration Test Common .. SKIPPED >> [INFO] Identity Test Back-end Module .. SKIPPED >> [INFO] org.wso2.identity.integration.test . SKIPPED >> [INFO] ---- >> >> [INFO] BUILD FAILURE >> [INFO] >> >> [INFO] Total time: 04:26 min >> [INFO] Finished at: 2017-07-20T13:57:21+05:30 >> [INFO] Final Memory: 94M/783M >> [INFO] >> >> Please kindly help. >> >> Thanks, >> Piraveena >> *Piraveena Paralogarajah* >> Intern- Software Engineering | WSO2 >> *Email *: pirave...@wso2.com >> *Mobile* : +94776099594 <+94%2077%20609%209594> >> <http://wso2.com/signature> >> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while building the product-is
could this be a problem with tycho version? similar problem seems to have resolved in : "[Builder] Build failed in Jenkins: carbon-kernel__openjdk8 » WSO2 Carbon Kernel - Distribution #190" On Tue, Aug 1, 2017 at 5:54 PM, Darshana Gunawardana <darsh...@wso2.com> wrote: > Hi Ramith, > > As mentioned above, we were not able to narrow down the exact signed jar > which caused this issue. That's why we sought the help of the dev list. > > Without pin point the which cert that missed in the java8 cacert, I would > say copying the java7 cacert is a workaround. > > Thanks, > > On Tue, Aug 1, 2017 at 5:44 PM, Ramith Jayasinghe <ram...@wso2.com> wrote: >> >> is this a workaround ? or a the correct fix? >> I came up with the same problem when trying to build project-ei in a >> another environment? >> >> On Thu, Jul 20, 2017 at 4:49 PM, Piraveena Paralogarajah >> <pirave...@wso2.com> wrote: >>> >>> [+Darshana, Maduranga] >>> >>> We found a workaround solution for this issue. >>> >>> We used -X flag to get more debug logs. >>> org.eclipse.osgi_3.8.0.v20110726-1606.jar was the final jar installed >>> during the execution. So we assumed the issue was in this file. Even though >>> we imported the certificates of the jar file to the cacert store, It didn't >>> work. >>> >>> When we tested with java7, it worked fine. So we copied the contents of >>> cacert store of java 7 and pasted in the cacert store of java 8. Now it >>> works fine. >>> >>> Thanks Maduranga and Darshana >>> >>> Regards, >>> Piraveena >>> >>> >>> Piraveena Paralogarajah >>> Intern- Software Engineering | WSO2 >>> Email : pirave...@wso2.com >>> Mobile : +94776099594 >>> >>> >>> On Thu, Jul 20, 2017 at 3:42 PM, Piraveena Paralogarajah >>> <pirave...@wso2.com> wrote: >>>> >>>> Hi, >>>> >>>> I tried to build the product-is. When building product-is using java >>>> 1.8, the build was failed due to error - one or more certificates rejected. >>>> >>>> Error log: >>>> >>>> [INFO] Command line: >>>> /bin/sh -c cd >>>> /home/piraveena/Documents/wso2/product_is/product-is/modules/p2-profile-gen >>>> && /usr/lib/jvm/java-8-oracle/jre/bin/java -jar >>>> /home/piraveena/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar >>>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository >>>> file:/home/piraveena/Documents/wso2/product_is/product-is/modules/p2-profile-gen/target/p2-repo >>>> -artifactRepository >>>> file:/home/piraveena/Documents/wso2/product_is/product-is/modules/p2-profile-gen/target/p2-repo >>>> -installIU carbon.product.id -profileProperties >>>> org.eclipse.update.install.features=true -profile is -bundlepool >>>> file:/home/piraveena/Documents/wso2/product_is/product-is/modules/p2-profile-gen/target/wso2carbon-core-4.4.16/repository/components >>>> -shared >>>> file:/home/piraveena/Documents/wso2/product_is/product-is/modules/p2-profile-gen/target/wso2carbon-core-4.4.16/repository/components/p2 >>>> -destination >>>> file:/home/piraveena/Documents/wso2/product_is/product-is/modules/p2-profile-gen/target/wso2carbon-core-4.4.16/repository/components/is >>>> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming >>>> Installing carbon.product.id 5.4.0.SNAPSHOT. >>>> Installation failed. >>>> One or more certificates rejected. Cannot proceed with installation. >>>> Application failed, log file location: >>>> /home/piraveena/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1500539238509.log >>>> >>>> [INFO] >>>> >>>> [INFO] Reactor Summary: >>>> [INFO] >>>> [INFO] WSO2 Identity Server ... SUCCESS [ >>>> 1.448 s] >>>> [INFO] org.wso2.carbon.is.migrate.client .. SUCCESS [ >>>> 31.276 s] >>>> [INFO] WSO2 Identity Server Styles Parent . SUCCESS [ >>>> 0.069 s] >>>> [INFO] Identity Server: UI styles . SUCCESS [ >>>> 1.592 s] >>>> [INFO] WSO2 IS - Features Aggregator Module ... SUCCESS [ >
Re: [Dev] For reference - data changes between MB 3.1.0 and MB 3.2.0 (internal feature)
whats the possibility of writing a tool which can migrate the data? On Sun, Apr 2, 2017 at 7:53 PM, Hasitha Hiranya <hasit...@wso2.com> wrote: > Hi, > > Please see attached. > > 1. Queue names should be fixed in about 5 tables (make all simple) > 2. Queue data string is updated in the model > 3. Subscriber data string is updated in the model > 4. Subscriber has a UUID as subscriber ID now. > 5. Subscriber connection is base64 encoded. Code will decode and work. In > 3.1.0 there was nothing like that. > 6. Inactive durable topic subscribers are derived from the queues now. No > entries in subscriber table. > > > Since there is a lot of changes in schema and code, IMO migrating from > 3.1.0 to 3.2.0 is error prone. Mainly this is because the model of working > is different now. > > Can we migrate a production MB customer to EI using below approach? > > 1. Create an EI cluster. MB cluster is in production. > 2. Switch publishers to EI cluster. Let subscribers be done with MB cluster > 3. Switch subscribers also to EI cluster. > > For durable topic/queue subscribers above should work. > > WDYT? > > > -- > *Hasitha Abeykoon* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improving MB Slot Coordinator to Work in a NATed/Containerized Environment
Thank you Isuru for this. we like to have the changes suggested by Imesh. On Fri, Aug 26, 2016 at 8:15 PM, Imesh Gunaratne <im...@wso2.com> wrote: > [+ Ramith] > > Great work Isuru!! Well written!! > I think it might be useful for explaining why this feature was needed in > the PR description. > > Thanks! > > On Fri, Aug 26, 2016 at 5:37 PM, Isuru Haththotuwa <isu...@wso2.com> > wrote: > >> Hi MB team, >> >> Please review the P/R for $subject [1], for the jira ticket reported at >> [2]. I'm yet to write a test for this, will send a separate P/R once done. >> >> [1]. https://github.com/wso2/andes/pull/685 >> >> [2]. https://wso2.org/jira/browse/MB-1736 >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048 >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [MB][3.2.0][Performance] Make wait strategy configurable
what do you think about subject? I briefly experimented with BlockingWaitStrategy (we use this right now), SleepingWaitStrategy, YieldingWaitStrategy it seems, BlockingWaitStrategy - takes high CPU in one thread always ( in the thread pool) YieldingWaitStrategy - CPU seems to be distributed across the pool. BUT when the server is idle Disruptor eats lot of CPU doing thread.yield(). therefore not good. SleepingWaitStrategy - CPU consumption is less. we need to check latency introduced by thread.sleep ( over blocking wait) regards, -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [MB][3.2.0][Analytics] Remove metrics view from product distribution
since MB v 3.0.0, it included carbon-matrices lib and there are graphs to show useful statistics. (Management Console -> Monitor -> Messaging Metrics). However, given that we are going to ship a analytics-mb distribution. Do we need to have this GUI/page in management console? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB][C5] How to write unit tests to mock the user core?
please disregard above noise! On Mon, Aug 15, 2016 at 3:36 PM, Ramith Jayasinghe <ram...@wso2.com> wrote: > this needs to be a public email isn't it? > > On Mon, Aug 15, 2016 at 2:10 PM, Sajini De Silva <saj...@wso2.com> wrote: > >> Hi, >> >> I have finished the first stage of MB authorization model for C5. Now I >> need to test the model by writing some test cases. Now user core is outside >> of MB how do we mock the user core in test cases. Is there any samples for >> this? >> >> Thanks, >> >> -- >> Sajini De SIlva >> Senior Software Engineer; WSO2 Inc.; http://wso2.com , >> Email: saj...@wso2.com >> Blog: http://sajinid.blogspot.com/ >> Git hub profile: https://github.com/sajinidesilva >> >> Phone: +94 712797729 >> >> > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: ram...@wso2.com > P: +94 772534930 > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB][C5] How to write unit tests to mock the user core?
this needs to be a public email isn't it? On Mon, Aug 15, 2016 at 2:10 PM, Sajini De Silva <saj...@wso2.com> wrote: > Hi, > > I have finished the first stage of MB authorization model for C5. Now I > need to test the model by writing some test cases. Now user core is outside > of MB how do we mock the user core in test cases. Is there any samples for > this? > > Thanks, > > -- > Sajini De SIlva > Senior Software Engineer; WSO2 Inc.; http://wso2.com , > Email: saj...@wso2.com > Blog: http://sajinid.blogspot.com/ > Git hub profile: https://github.com/sajinidesilva > > Phone: +94 712797729 > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Natasha Wijesekara
Congrats !!! On Wed, Jun 29, 2016 at 11:20 AM, Chiranga Alwis <chira...@wso2.com> wrote: > Congratulations Natasha! > > On Wed, Jun 29, 2016 at 11:06 AM, Dileesha Rajapakse <dilee...@wso2.com> > wrote: > >> Congratulations Natasha! >> >> On Wed, Jun 29, 2016 at 10:59 AM, Sajith Perera <saji...@wso2.com> wrote: >> >>> Congratulations Natasha..!!! :) >>> >>> On Wed, Jun 29, 2016 at 10:49 AM, Natasha Wijesekara <nata...@wso2.com> >>> wrote: >>> >>>> Thank you all !!! >>>> >>>> On Wed, Jun 29, 2016 at 10:45 AM, Natasha Wijesekara <nata...@wso2.com> >>>> wrote: >>>> >>>>> Thank you akki ! :) >>>>> >>>>> On Wed, Jun 29, 2016 at 10:32 AM, Himasha Guruge <himas...@wso2.com> >>>>> wrote: >>>>> >>>>>> Congrats Natasha! :) >>>>>> >>>>>> On Wed, Jun 29, 2016 at 10:23 AM, Nandika Jayawardana < >>>>>> nand...@wso2.com> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> It's my pleasure to announce Natasha Wijesekara as a WSO2 Committer. >>>>>>> Natasha has been a great contributor to BPS and PC products and in >>>>>>> recognition of her contributions, she's been voted as a WSO2 Committer. >>>>>>> >>>>>>> Congratulations Natasha and keep up the good work! >>>>>>> >>>>>>> Regards >>>>>>> Nandika >>>>>>> >>>>>>> -- >>>>>>> Nandika Jayawardana >>>>>>> WSO2 Inc ; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Himasha Guruge >>>>>> *Software Engineer* >>>>>> WS*O2* *Inc.* >>>>>> Mobile: +94 777459299 >>>>>> himas...@wso2.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Natasha Wijesekare* >>>>> >>>>> *Software Engineering Intern, WSO2 Inc: http://wso2.com >>>>> <http://wso2.com/>* >>>>> *email : nata...@wso2.com <nata...@wso2.com>* >>>>> *mobile: +94 771358651 <%2B94%20771358651>* >>>>> >>>> >>>> >>>> >>>> -- >>>> *Natasha Wijesekare* >>>> >>>> *Software Engineering Intern, WSO2 Inc: http://wso2.com >>>> <http://wso2.com/>* >>>> *email : nata...@wso2.com <nata...@wso2.com>* >>>> *mobile: +94 771358651 <%2B94%20771358651>* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Sajith Dimal >>> Software Engineer >>> Mobile : +94783101496 >>> WSO2 Inc. | http://wso2.com >>> lean.enterprise.middleware >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Dileesha Rajapakse >> *Intern - Engineering* >> Mobile : +94 (0) 772 555 933 >> Tel : +94 112 741 505 >> dilee...@wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Chiranga Alwis, > Software Engineering Intern, > +94 77 5930497 > +94 77 6368208 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Option to ship MQTT client lib with ESB
+1. that's a good idea. BTW, how are we going to handle version upgrades (for client lib) ? On Wed, Jun 8, 2016 at 7:19 AM, Pamod Sylvester <pa...@wso2.com> wrote: > Hi All, > > Could we consider the $Subject, (since the library is interoperable with > all standard MQTT brokers). > > Currently it requires client lib to be separately downloaded when > integrating with a broker [1] > > [1] > https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample > > Thanks, > Pamod > > -- > *Pamod Sylvester * > > *WSO2 Inc.; http://wso2.com <http://wso2.com>* > cell: +94 77 7779495 > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [UUF] Pet store sample not working without last forwards slash
I think in both cases the app should load in the browser? On Thu, May 26, 2016 at 5:31 PM, Hemika Kodikara <hem...@wso2.com> wrote: > Hi All, > > The pets-store can be accessed with "http://127.0.0.1:8080/pets-store/; > > But cannot be accessed with "http://127.0.0.1:8080/pets-store; (with the > missing forward slash at the end). I get a "Cannot find an app for context > 'null'." message on the browser. > > Also a small suggestion - Can we show the URLs of the apps deployed on the > console when the server startsup. IMO, it will help out the users in user > experience wise. > > Regards, > Hemika > > Hemika Kodikara > Software Engineer > WSO2 Inc. > lean . enterprise . middleware > http://wso2.com > > Mobile : +9477762 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] OOM Issues and HazelCast behaviour
HI Azeez/Sameera, Having encountered some OOM issues (relating to HZ) I looked at what Hazelcast does in face of GC errors [1]. It will drop all connections, threads, and shuts it self down. Now, Think about one of our server's ( say MB) face a OOM and embedded HZ instance shuts it self down. I propose when this happens entire server should stop its processing intelligently ( if not shutting down). Rational is one of the sub-system in the server shutdown while other parts of the server don't care, which is wrong. As for MB, it tries to stop processing in a meaningful manner and I argue this should be something any server should do if they use HZ clustering. thoughts? [1] https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/instance/DefaultOutOfMemoryHandler.java -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 772534930 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Adding H2 Driver as a Dependency only for the Destribution
and shall we upgrade H2 version to latest? On Fri, Feb 12, 2016 at 2:24 PM, Ramith Jayasinghe <ram...@wso2.com> wrote: > So whats the verdict? > @sameera: can we have some thing similar to 'carbon-persistence' or > something which contains H2? > > On Fri, Feb 12, 2016 at 11:48 AM, Niranjan Karunanandham > <niran...@wso2.com> wrote: >> Hi Akalanka, >> >> On Fri, Feb 12, 2016 at 11:37 AM, Akalanka Pagoda Arachchi >> <darsha...@wso2.com> wrote: >>> >>> Hi Niranjan, >>> >>> Yes, we could have avoided adding h2-database-engine as a dependency in >>> 4.4.x Andes. >>> >>> If we add the h2 driver to the datasource feature, it would mean whenever >>> datasource feature is used h2 driver will be copied. Will that be OK? My >>> opinion is if the H2 driver is not a dependency for the feature, it should >>> not be contained in the feature. When we create a distribution from that >>> feature, if H2 DB is used as the default DB configuration, we should provide >>> the H2 driver with the distribution. >> >> Sorry about it. I was under the impression that the datasource core for C5 >> supports by default is for H2 DB like in C4. This is why I suggested that we >> define it at the datasource core feature. >> >>> >>> WDYT? >>> >>> Thanks, >>> Akalanka. >>> >>> On Fri, Feb 12, 2016 at 11:05 AM, Niranjan Karunanandham >>> <niran...@wso2.com> wrote: >>>> >>>> Hi Akalanka / all >>>> >>>> On Fri, Feb 12, 2016 at 10:46 AM, Akalanka Pagoda Arachchi >>>> <darsha...@wso2.com> wrote: >>>>> >>>>> Hi All, >>>>> >>>>> In the previous distributions, we had H2 database driver as a dependency >>>>> for our features so that it will be copied to the plugins folder when the >>>>> pack is created.However, in this scenario, H2 database driver is not >>>>> exactly >>>>> a dependency of the Andes Core feature since it is not using the H2 >>>>> driver. >>>> >>>> Are you referring to the h2-database-engine jar? This was there in the >>>> plugins folder of kernel core zip in 4.4.x. If so, then why is andes core >>>> feature also packing this? >>>> >>>>> >>>>> Therefore, my suggestion is to avoid adding H2 database driver as a >>>>> dependency for the Andes Core feature, but rather add it as a dependency >>>>> for >>>>> product distribution module so that when the distribution pack is created, >>>>> the H2 driver, which is required for default database configurations is >>>>> copied to the plugins folder. >>>>> >>>>> This will be useful in reducing the Andes Core feature bundle size as >>>>> well. >>>>> >>>>> If any product is to install Andes Core feature, they will have to copy >>>>> the relevant jar file to the dropins folder if they don't already have it. >>>>> >>>>> WDYT? >>>>> >>>>> If we're to go ahead with this approach we need a way to install osgi >>>>> bundles to the distribution that are not available in the features or >>>>> create >>>>> a new feature containing H2 database driver. >>>> >>>> If we require a default DB, then I would suggest to have it with database >>>> core feature. WDYT? >>>> >>>>> >>>>> >>>>> Please provide your thoughts. >>>>> >>>>> Thanks, >>>>> Akalanka. >>>>> >>>>> -- >>>>> Darshana Akalanka Pagoda Arachchi, >>>>> Software Engineer >>>>> 078-4721791 >>>> >>>> >>>> Regards, >>>> Nira >>>> >>>> -- >>>> >>>> Niranjan Karunanandham >>>> Senior Software Engineer - WSO2 Inc. >>>> WSO2 Inc.: http://www.wso2.com >>> >>> >>> >>> >>> -- >>> Darshana Akalanka Pagoda Arachchi, >>> Software Engineer >>> 078-4721791 >> >> >> Regards, >> Nira >> >> -- >> >> Niranjan Karunanandham >> Senior Software Engineer - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com > > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: ram...@wso2.com > P: +94 777542851 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Adding H2 Driver as a Dependency only for the Destribution
So whats the verdict? @sameera: can we have some thing similar to 'carbon-persistence' or something which contains H2? On Fri, Feb 12, 2016 at 11:48 AM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi Akalanka, > > On Fri, Feb 12, 2016 at 11:37 AM, Akalanka Pagoda Arachchi > <darsha...@wso2.com> wrote: >> >> Hi Niranjan, >> >> Yes, we could have avoided adding h2-database-engine as a dependency in >> 4.4.x Andes. >> >> If we add the h2 driver to the datasource feature, it would mean whenever >> datasource feature is used h2 driver will be copied. Will that be OK? My >> opinion is if the H2 driver is not a dependency for the feature, it should >> not be contained in the feature. When we create a distribution from that >> feature, if H2 DB is used as the default DB configuration, we should provide >> the H2 driver with the distribution. > > Sorry about it. I was under the impression that the datasource core for C5 > supports by default is for H2 DB like in C4. This is why I suggested that we > define it at the datasource core feature. > >> >> WDYT? >> >> Thanks, >> Akalanka. >> >> On Fri, Feb 12, 2016 at 11:05 AM, Niranjan Karunanandham >> <niran...@wso2.com> wrote: >>> >>> Hi Akalanka / all >>> >>> On Fri, Feb 12, 2016 at 10:46 AM, Akalanka Pagoda Arachchi >>> <darsha...@wso2.com> wrote: >>>> >>>> Hi All, >>>> >>>> In the previous distributions, we had H2 database driver as a dependency >>>> for our features so that it will be copied to the plugins folder when the >>>> pack is created.However, in this scenario, H2 database driver is not >>>> exactly >>>> a dependency of the Andes Core feature since it is not using the H2 driver. >>> >>> Are you referring to the h2-database-engine jar? This was there in the >>> plugins folder of kernel core zip in 4.4.x. If so, then why is andes core >>> feature also packing this? >>> >>>> >>>> Therefore, my suggestion is to avoid adding H2 database driver as a >>>> dependency for the Andes Core feature, but rather add it as a dependency >>>> for >>>> product distribution module so that when the distribution pack is created, >>>> the H2 driver, which is required for default database configurations is >>>> copied to the plugins folder. >>>> >>>> This will be useful in reducing the Andes Core feature bundle size as >>>> well. >>>> >>>> If any product is to install Andes Core feature, they will have to copy >>>> the relevant jar file to the dropins folder if they don't already have it. >>>> >>>> WDYT? >>>> >>>> If we're to go ahead with this approach we need a way to install osgi >>>> bundles to the distribution that are not available in the features or >>>> create >>>> a new feature containing H2 database driver. >>> >>> If we require a default DB, then I would suggest to have it with database >>> core feature. WDYT? >>> >>>> >>>> >>>> Please provide your thoughts. >>>> >>>> Thanks, >>>> Akalanka. >>>> >>>> -- >>>> Darshana Akalanka Pagoda Arachchi, >>>> Software Engineer >>>> 078-4721791 >>> >>> >>> Regards, >>> Nira >>> >>> -- >>> >>> Niranjan Karunanandham >>> Senior Software Engineer - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >> >> >> >> >> -- >> Darshana Akalanka Pagoda Arachchi, >> Software Engineer >> 078-4721791 > > > Regards, > Nira > > -- > > Niranjan Karunanandham > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Adding H2 Driver as a Dependency only for the Destribution
I suppose at minimum, BPS, GREG needs a database by default to be packed. Therefore any thoughts? On Fri, Feb 12, 2016 at 10:46 AM, Akalanka Pagoda Arachchi <darsha...@wso2.com> wrote: > Hi All, > > In the previous distributions, we had H2 database driver as a dependency for > our features so that it will be copied to the plugins folder when the pack > is created.However, in this scenario, H2 database driver is not exactly a > dependency of the Andes Core feature since it is not using the H2 driver. > > Therefore, my suggestion is to avoid adding H2 database driver as a > dependency for the Andes Core feature, but rather add it as a dependency for > product distribution module so that when the distribution pack is created, > the H2 driver, which is required for default database configurations is > copied to the plugins folder. > > This will be useful in reducing the Andes Core feature bundle size as well. > > If any product is to install Andes Core feature, they will have to copy the > relevant jar file to the dropins folder if they don't already have it. > > WDYT? > > If we're to go ahead with this approach we need a way to install osgi > bundles to the distribution that are not available in the features or create > a new feature containing H2 database driver. > > Please provide your thoughts. > > Thanks, > Akalanka. > > -- > Darshana Akalanka Pagoda Arachchi, > Software Engineer > 078-4721791 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Message Broker 3.1.0 RC 2
I tested samples (with compression flag on) [+] Stable - go ahead and release On Thu, Feb 4, 2016 at 3:25 AM, Akalanka Pagoda Arachchi <darsha...@wso2.com> wrote: > Hi Devs, > > This is the second release candidate of WSO2 Message Broker 3.1.0. > > This release fixes the following issues: > https://wso2.org/jira/issues/?filter=12637 > > Please download MB 3.1.0 RC2 and test the functionality and vote. Vote will > be open for 72 hours or as needed. > > Source & binary distribution files: > https://github.com/wso2/product-mb/releases/tag/v3.1.0-RC2 > > Maven staging repo: > http://maven.wso2.org/nexus/content/repositories/orgwso2mb-323/ > > The tag to be voted upon: > https://github.com/wso2/product-mb/tree/v3.1.0-RC2 > > > [+] Stable - go ahead and release > [-] Broken - do not release (explain why) > > Thanks and Regards, > > ~ WSO2 MB Team ~ > > -- > Darshana Akalanka Pagoda Arachchi, > Software Engineer > 078-4721791 > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Message Broker 3.1.0 RC 1
-1. We came up following issues: https://wso2.org/jira/browse/MB-1625 https://wso2.org/jira/browse/MB-1624 https://wso2.org/jira/browse/MB-1622 they will be fixed in next RC. On Tue, Feb 2, 2016 at 4:37 AM, Akalanka Pagoda Arachchi <darsha...@wso2.com> wrote: > Hi Devs, > > This is the first release candidate of WSO2 Message Broker 3.0.0. > > This release fixes the following issues: > https://wso2.org/jira/issues/?filter=12633 > > Please download MB 3.1.0 RC1 and test the functionality and vote. Vote will > be open for 72 hours or as needed. > > Source & binary distribution files: > https://github.com/wso2/product-mb/releases/tag/v3.1.0-RC1 > > Maven staging repo: > http://maven.wso2.org/nexus/content/repositories/orgwso2mb-316/ > > The tag to be voted upon: > https://github.com/wso2/product-mb/tree/v3.1.0-RC1 > > > [+] Stable - go ahead and release > [-] Broken - do not release (explain why) > > Thanks and Regards, > > ~ WSO2 MB Team ~ > > -- > Darshana Akalanka Pagoda Arachchi, > Software Engineer > 078-4721791 > > > > -- > Darshana Akalanka Pagoda Arachchi, > Software Engineer > 078-4721791 > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2
HI, in : https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb I see that, false is not added to MB data-source (only MB data-source requires that). that would lead to problems. shall we fix that. regards Ramith On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa <isu...@wso2.com> wrote: > Hi devs, > > This is the second release candidate of WSO2 Puppet Modules 1.0.0. Please > download, test and vote. > > [ ] Broken - do not release (explain why) > [ ] Stable - go ahead and release > > The tag to be voted upon: > https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2 > > Source and binary distribution files: > https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2 > > The vote will be open for 72 hours or as needed. > > -- > Thanks, > The WSO2 Private PaaS Team > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2
had a chat with IsuruH and agreed to add the ability to configure this on next release. On Mon, Feb 1, 2016 at 11:25 AM, Ramith Jayasinghe <ram...@wso2.com> wrote: > HI, > in : > https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb > I see that, > false is not added to MB > data-source (only MB data-source requires that). that would lead to > problems. shall we fix that. > regards > Ramith > > On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa <isu...@wso2.com> wrote: >> Hi devs, >> >> This is the second release candidate of WSO2 Puppet Modules 1.0.0. Please >> download, test and vote. >> >> [ ] Broken - do not release (explain why) >> [ ] Stable - go ahead and release >> >> The tag to be voted upon: >> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2 >> >> Source and binary distribution files: >> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2 >> >> The vote will be open for 72 hours or as needed. >> >> -- >> Thanks, >> The WSO2 Private PaaS Team >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: ram...@wso2.com > P: +94 777542851 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7
carbon.core.init.CarbonServerManager}
>>>>>>>>> TID: [-1234] [] [2015-12-21 10:24:08,084] INFO
>>>>>>>>> {org.wso2.carbon.andes.core.internal.ds.QueueManagerServiceDS} -
>>>>>>>>> Successfully created the queue manager service
>>>>>>>>> {org.wso2.carbon.andes.core.internal.ds.QueueManagerServiceDS}
>>>>>>>>> TID: [-1234] [] [2015-12-2
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> On Mon, Dec 21, 2015 at 2:53 PM, Nadeesha Meegoda <
>>>>>>>>> nadees...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> Came across the $subject. [1] is the exception I get when
>>>>>>>>>> starting the server.
>>>>>>>>>>
>>>>>>>>>> Also did a diff check with IS 5.1.0 wso2server.bat file compared
>>>>>>>>>> with MB 3.0.0 wso2server.bat file. Please find the mismatches
>>>>>>>>>>
>>>>>>>>>> *MB 3.0.0 *
>>>>>>>>>>
>>>>>>>>>> set CMD_LINE_ARGS=-Xbootclasspath/a:%CARBON_XBOOTCLASSPATH% -Xms1024m
>>>>>>>>>> -Xmx2048m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError
>>>>>>>>>> -XX:HeapDumpPath="%CARBON_HOME%\repository\logs\heap-dump.hprof"
>>>>>>>>>> -Dcom.sun.management.jmxremote -classpath %CARBON_CLASSPATH%
>>>>>>>>>> %JAVA_OPTS%
>>>>>>>>>> -Djava.endorsed.dirs=%JAVA_ENDORSED% -DandesConfig=broker.xml
>>>>>>>>>> -Dcarbon.registry.root=/ -Dcarbon.home="%CARBON_HOME%"
>>>>>>>>>> -Dwso2.server.standalone=true -Djava.command="%JAVA_HOME%\bin\java"
>>>>>>>>>> -Djava.opts="%JAVA_OPTS%" -Djava.io.tmpdir="%CARBON_HOME%\tmp"
>>>>>>>>>> -Dcatalina.base="%CARBON_HOME%\lib\tomcat"
>>>>>>>>>> -Dwso2.carbon.xml=%CARBON_HOME%\repository\conf\carbon.xml
>>>>>>>>>> -Dwso2.registry.xml="%CARBON_HOME%\repository\conf\registry.xml"
>>>>>>>>>> -Dwso2.user.mgt.xml="%CARBON_HOME%\repository\conf\user-mgt.xml"
>>>>>>>>>> -Dwso2.transports.xml="%CARBON_HOME%\repository\conf\mgt-transports.xml"
>>>>>>>>>> -Djava.util.logging.config.file="%CARBON_HOME%\repository\conf\log4j.properties"
>>>>>>>>>> -Dcarbon.config.dir.path="%CARBON_HOME%\repository\conf"
>>>>>>>>>> -Dcarbon.logs.path="%CARBON_HOME%\repository\logs"
>>>>>>>>>> -Dcomponents.repo="%CARBON_HOME%\repository\components"
>>>>>>>>>> -Dconf.location="%CARBON_HOME%\repository\conf"
>>>>>>>>>> -Dcom.atomikos.icatch.file="%CARBON_HOME%\lib\transactions.properties"
>>>>>>>>>> -Dcom.atomikos.icatch.hide_init_file_path="true"
>>>>>>>>>> -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
>>>>>>>>>> -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
>>>>>>>>>> -Dcom.sun.jndi.ldap.connect.pool.authentication=simple
>>>>>>>>>> -Dcom.sun.jndi.ldap.connect.pool.timeout=3000
>>>>>>>>>> -Dorg.terracotta.quartz.skipUpdateCheck=true
>>>>>>>>>> -Dcarbon.classpath=%CARBON_CLASSPATH% -Dfile.encoding=UTF8
>>>>>>>>>>
>>>>>>>>>> *IS 5.1.0*
>>>>>>>>>>
>>>>>>>>>> set CMD_LINE_ARGS=-Xbootclasspath/a:%CARBON_XBOOTCLASSPATH% -Xms256m
>>>>>>>>>> -Xmx1024m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError
>>>>>>>>>> -XX:HeapDumpPath="%CARBON_HOME%\repository\logs\heap-dump.hprof"
>>>>>>>>>> -Dcom.sun.management.jmxremote -classpath %CARBON_CLASSPATH%
>>>>>>>>>> %JAVA_OPTS%
>>>>>>>>>> -Djava.endorsed.dirs=%JAVA_ENDORSED% -Dcarbon.registry.root=/
>>>>>>>>>> -Dcarbon.home="%CARBON_HOME%" -Dwso2.server.standalone=true
>>>>>>>>>> -Djava.command="%JAVA_HOME%\bin\java" -Djava.opts="%JAVA_OPTS%"
>>>>>>>>>> -Djava.io.tmpdir="%CARBON_HOME%\tmp"
>>>>>>>>>> -Dcatalina.base="%CARBON_HOME%\lib\tomcat"
>>>>>>>>>> -Dwso2.carbon.xml=%CARBON_HOME%\repository\conf\carbon.xml
>>>>>>>>>> -Dwso2.registry.xml="%CARBON_HOME%\repository\conf\registry.xml"
>>>>>>>>>> -Dwso2.user.mgt.xml="%CARBON_HOME%\repository\conf\user-mgt.xml"
>>>>>>>>>> -Dwso2.transports.xml="%CARBON_HOME%\repository\conf\mgt-transports.xml"
>>>>>>>>>>
>>>>>>>>>> -Djava.util.logging.config.file="%CARBON_HOME%\repository\conf\etc\logging-bridge.properties"
>>>>>>>>>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>>>>>>>>>> -Dcarbon.config.dir.path="%CARBON_HOME%\repository\conf"
>>>>>>>>>> -Dcomponents.repo="%CARBON_HOME%\repository\components"
>>>>>>>>>> -Dconf.location="%CARBON_HOME%\repository\conf"
>>>>>>>>>> -Dcom.atomikos.icatch.file="%CARBON_HOME%\lib\transactions.properties"
>>>>>>>>>> -Dcom.atomikos.icatch.hide_init_file_path="true"
>>>>>>>>>> -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
>>>>>>>>>> -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
>>>>>>>>>> -Dcom.sun.jndi.ldap.connect.pool.authentication=simple
>>>>>>>>>> -Dcom.sun.jndi.ldap.connect.pool.timeout=3000
>>>>>>>>>> -Dorg.terracotta.quartz.skipUpdateCheck=true
>>>>>>>>>> -Dcarbon.classpath=%CARBON_CLASSPATH% -Dfile.encoding=UTF8
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>>
>>>>>>>>>> The system cannot find the file specified. JAVA_HOME environment
>>>>>>>>>> variable is set to C:\Program Files (x86)\Java\jdk1.7.0_79
>>>>>>>>>> CARBON_HOME
>>>>>>>>>> environment variable is set to D:\Support\WSO2MB~1.0\bin\.. Error
>>>>>>>>>> occurred
>>>>>>>>>> during initialization of VM Could not reserve enough space for
>>>>>>>>>> object heap
>>>>>>>>>> Error: Could not create the Java Virtual Machine. Error: A fatal
>>>>>>>>>> exception
>>>>>>>>>> has occurred. Program will exit.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Nadeesha
>>>>>>>>>> --
>>>>>>>>>> *Nadeesha Meegoda*
>>>>>>>>>> Software Engineer - QA
>>>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>>>> lean.enterprise.middleware
>>>>>>>>>> email : nadees...@wso2.com
>>>>>>>>>> mobile: +94783639540
>>>>>>>>>> <%2B94%2077%202273555>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Yasassri Ratnayake
>>>>>>>>> Software Engineer - QA
>>>>>>>>> WSO2 Inc ; http://wso2.com
>>>>>>>>> lean.enterprise.middleware
>>>>>>>>> *Mobile : +94715933168 <%2B94715933168>*
>>>>>>>>> *Blogs : http://yasassriratnayake.blogspot.com
>>>>>>>>> <http://yasassriratnayake.blogspot.com/>*
>>>>>>>>> *http://wso2logs.blogspot.com
>>>>>>>>> <http://wso2logs.blogspot.com>*
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Nadeesha Meegoda*
>>>>>>>> Software Engineer - QA
>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>> lean.enterprise.middleware
>>>>>>>> email : nadees...@wso2.com
>>>>>>>> mobile: +94783639540
>>>>>>>> <%2B94%2077%202273555>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Isuru Perera
>>>>>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>>>>>>> Lean . Enterprise . Middleware
>>>>>>>
>>>>>>> about.me/chrishantha
>>>>>>> Contact: +IsuruPereraWSO2
>>>>>>> <https://www.google.com/+IsuruPereraWSO2/about>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Nadeesha Meegoda*
>>>>>> Software Engineer - QA
>>>>>> WSO2 Inc.; http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>> email : nadees...@wso2.com
>>>>>> mobile: +94783639540
>>>>>> <%2B94%2077%202273555>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jason De Silva
>>>>> *Software Engineer - QA*
>>>>> Mobile: +94 (0) 772 097 678
>>>>> Email: jas...@wso2.com
>>>>> WSO2 Inc. www.wso2.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Isuru Perera
>>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>> about.me/chrishantha
>>>> Contact: +IsuruPereraWSO2
>>>> <https://www.google.com/+IsuruPereraWSO2/about>
>>>>
>>>
>>>
>>>
>>> --
>>> *Nadeesha Meegoda*
>>> Software Engineer - QA
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>> email : nadees...@wso2.com
>>> mobile: +94783639540
>>> <%2B94%2077%202273555>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
>>
>>
>
>
> --
> Nilmini Perera
>
> Senior Technical Writer
> WSO2 Inc.
>
> Mobile: 0094776722152
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Documentation Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to documentation+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Evaluating the possibility of applying Goldmansachs ConcurrentHashMap in MB
Hi Malaka, lets report these findings on architecture group as a investigation we did. regards Ramtih On Tue, Jan 26, 2016 at 8:16 AM, Malaka Gangananda <mala...@wso2.com> wrote: > Hi, > > While profiling the MB we found out that there is a performance bottle > neck in using util.ConcurrentSkipListMap. Because every time size call is > made it has to loop through the data structure so it takes O(n) time. But > looking at GC ConcurrentHashMap we found out that it only takes constant > time (O(1) time) to make the size call.Other operations on GC > ConcurrentHashMap are also faster than uti.ConcurrentSkipListMap. > > Here I have attached JMH Benchmark results which acquired by testing > util.ConcurrentSkipListMap vs GC ConcurrentHashMap > > > ConcurrentSkipListMap Vs Goldmansachs Concurre... > <https://docs.google.com/a/wso2.com/spreadsheets/d/1y5w1aIDBN89C0ctB83iDOULtYPnB_-3OuGYArd0lbt0/edit?usp=drive_web> > > > Malaka Gangananda > Software Engineer Intern > mobile:0713564340 > mala...@wso2.com > <thila...@wso2.com> > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to select Leader/Contributer node in a cluster
MB also elects a leader/coordinator for the cluster (based on hezelcast.) On Fri, Jan 22, 2016 at 10:48 AM, Amila Maha Arachchi <ami...@wso2.com> wrote: > Nipun, > > May be you need to try it in a clustered environment or at least > clustering enabled. I assume you tried this with a single server. > > On Wed, Jan 20, 2016 at 9:42 AM, Nipuna Prashan <pras...@wso2.com> wrote: > >> Hi Krishanthan, >> >> Cloud team has developed three osgi components to delete tenants, but >> tenant deletion has to be done manually by adding components to >> dropping folder when we want to start tenant deletion. Now, my project >> is to automate this process by making one osgi component for every >> server and the component will be in the server every time. >> >> AxisConfiguration serverAxisConfig = >> >> ServiceHolder.getConfigurationContextService().getServerConfigContext().getAxisConfiguration(); >> ClusteringAgent agent = serverAxisConfig.getClusteringAgent(); >> boolean isCoordinator = agent.isCoordinator(); >> >> I tried this, but this always returns false. >> >> On Tue, Jan 19, 2016 at 9:08 PM, Kishanthan Thangarajah >> <kishant...@wso2.com> wrote: >> > IIRC, we already have a way (tool) to delete tenants in a cluster which >> is >> > used by cloud team. So what's the requirement for this component here? >> > >> > With hazelcast based clustering, we assume that the first (oldest) >> member as >> > the coordinator for the cluster. We set this member as the coordinator >> and >> > you can check whether the current node is the coordinator using >> > ClusteringAgent#isCoordinator method. >> > >> > On Mon, Jan 18, 2016 at 6:24 PM, Nipuna Prashan <pras...@wso2.com> >> wrote: >> >> >> >> Hi all, >> >> >> >> I am building an osgi component for tenant deletion task. This will be >> >> deployed in every server (APIM, AS, AF, BAM, IS..). I have a >> requirement to >> >> do this task in one node in the cluster while there is no single point >> of >> >> failure. Only one node should start deletion while other nodes waiting >> on >> >> the same server. >> >> Is there a way to find the leader node/ contributor in a cluster? Any >> help >> >> would be appreciated. >> >> >> >> >> >> >> >> -- >> >> Nipuna Prashan >> >> Software Engineering Intern >> >> +94711852792 >> > >> > >> > >> > >> > -- >> > Kishanthan Thangarajah >> > Associate Technical Lead, >> > Platform Technologies Team, >> > WSO2, Inc. >> > lean.enterprise.middleware >> > >> > Mobile - +94773426635 >> > Blog - http://kishanthan.wordpress.com >> > Twitter - http://twitter.com/kishanthan >> >> >> >> -- >> Nipuna Prashan >> Software Engineering Intern >> +94711852792 >> > > > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when installing MB features in products that use carbon.event.core
I propose changing the file name at MB side. so the changes are minimal. we plan to further optimize this area in upcoming versions. @Hemika, shall we do this? On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara <ruw...@wso2.com> wrote: > Hi All, > > We ran to in to the above problem when trying to install MB features in > the IOTServer. As we discovered when investigating, root cause of the > problem was the use of event-broker.xml, which is used for loading > configurations in both components. > > MB uses the andes.event.core component which has now come to replace the > event.core from back in the day (event.core is still referred to from > governance components and synapse). Since both components refer to the same > file, each try to load contradictory (internal) classes that lead to class > not found exceptions. > > As a workaround to overcome this problem, we will have to rename the > event-broker.xml file from event.core feature to something like > carbon-event-core.xml to ensure the co-existing of both components in > harmony. In addition we will also have to remove specific checks for > andes/qpid packages inside of the event.core. > > I have done the changes against the 4.4.8 tag in a separate branch on my > personal repository [1]. Can we get a 4.4.9 version released with this > change [2] for us to move forward with the milestone? > > [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 > [2] - > https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a > > Thanks and Regards, > > Ruwan Yatawara > > Senior Software Engineer, > WSO2 Inc. > > email : ruw...@wso2.com > mobile : +94 77 9110413 > blog : http://ruwansrants.blogspot.com/ > www: :http://wso2.com > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: MB Performance Test Graph Generator(MB Intern Project)
Shall we commit this (as per the chat) to some common place (git) On Mon, Nov 23, 2015 at 10:48 PM, Malaka Gangananda <mala...@wso2.com> wrote: > > -- Forwarded message -- > From: Malaka Gangananda <mala...@wso2.com> > Date: Mon, Nov 23, 2015 at 10:03 AM > Subject: MB Performance Test Graph Generator(MB Intern Project) > To: Akalanka Pagoda Arachchi <darsha...@wso2.com>, Anuja Herath < > an...@wso2.com>, Asanka Abeyweera <asank...@wso2.com>, Asitha Nanayakkara > <asi...@wso2.com>, Hasitha Amal De Silva <hasit...@wso2.com>, Hasitha > Hiranya <hasit...@wso2.com>, Hemika Kodikara <hem...@wso2.com>, Indika > Sampath <indi...@wso2.com>, Pamod Sylvester <pa...@wso2.com>, Pumudu > Ruhunage <pum...@wso2.com>, Ramith Jayasinghe <ram...@wso2.com>, Sajini > De Silva <saj...@wso2.com>, Sasikala Kottegoda <sasik...@wso2.com>, > Thilanka Bowala <thila...@wso2.com> > > > Hi, > I have attached the project folder related to $Subject with this mail. > Also here is the link to the git hub repository of the project > https://github.com/malakaganga/MB_GraphGen > This project can be used to visualize the performance test result > generated by the JMeter using graphs > Thanks, > -- > Malaka Ganganand > Software Engineer Intern > mobile:0713564340 > mala...@wso2.com > <thila...@wso2.com> > > > > -- > Malaka Gangananda > Software Engineer Intern > mobile:0713564340 > mala...@wso2.com > <thila...@wso2.com> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Shall we document CacheLevel for JMS inbound endpoint
in the UI we have only 1,2,3 in the drop down. it could be hard for user to figure it out. By going through the code I see : https://github.com/wso2/carbon-mediation/blob/master/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint/src/main/java/org/wso2/carbon/inbound/endpoint/protocol/jms/JMSConstants.java public static final int CACHE_NONE = 0; /** * Cache only the JMS connection between tasks (when receiving), or JMS CF's * (when sending) */ public static final int CACHE_CONNECTION = 1; /** * Cache only the JMS connection and Session between tasks (receiving), or * JMS CF's (sending) */ public static final int CACHE_SESSION = 2; /** * Cache the JMS connection, Session and Consumer between tasks when * receiving */ public static final int CACHE_CONSUMER = 3; -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Odata support for DSS is not enabled in Dev studio
$subject I created a jira for that[1] [1] https://wso2.org/jira/browse/TOOLS-3270 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2
could we hold the release until permission related issue is fixed?
On Tue, Oct 13, 2015 at 5:10 PM, Ramith Jayasinghe <ram...@wso2.com> wrote:
> could we hold the release until permission related issue?
>
> On Tue, Oct 13, 2015 at 5:06 PM, Rajith Vitharana <raji...@wso2.com>
> wrote:
>
>> Hi,
>>
>> We have tested Basic scenarios + installing DSS features in ESB 4.9.0 and
>> those are successful (there were some integration test failiers due to
>> configuration changes which needs some fixes in test cases in DSS)
>>
>> +1 to release
>>
>> Thanks,
>>
>> On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda <sasik...@wso2.com>
>> wrote:
>>
>>> Hi Manuri,
>>>
>>> We tested MB 3.0.0 with this release and our scenario of queue creation
>>> fails after giving a permission denied error. The scenario is as follows:
>>>
>>> 1. Create a user "user1" with a role assigned with permission to create
>>> queues.
>>> 2. Login from "user1" and try to create a queue, we get a permission
>>> denied error.
>>>
>>> When creating a queue the following happens from our code.
>>>
>>> 1. We create an internal role for the queue and assign it to the current
>>> user with permissions assigned.
>>>
>>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>>
>>> PERMISSION_CHANGE_PERMISSION);
>>>
>>> 2. Next, we create the queue and update permissions for the queue. In this
>>> step, we check if the current user has permissions to change the queue.
>>>
>>> String[] userRoles =
>>> userRealm.getUserStoreManager().getRoleListOfUser(loggedInUser);
>>> for (String userRole : userRoles) {
>>> if (userRealm.getAuthorizationManager().isRoleAuthorized(
>>> userRole, queueID, PERMISSION_CHANGE_PERMISSION)) {
>>> isUserHasChangePermission = true;
>>> }
>>> }
>>>
>>> At this stage, *'*(userRealm.getAuthorizationManager().isRoleAuthorized(
>>> userRole, queueID, PERMISSION_CHANGE_PERMISSION))' false
>>> implying that any of roles assigned to the user do not have permissions to
>>> change the queue, thus not allowing the user to create the queue.
>>>
>>>
>>> Thank you
>>>
>>>
>>> On Mon, Oct 12, 2015 at 9:24 PM, Manuri Amaya Perera <manu...@wso2.com>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> WSO2 Carbon Kernel 4.4.2 RC2 Release Vote.
>>>>
>>>> This release fixes the following issues:
>>>> https://wso2.org/jira/issues/?filter=12396
>>>>
>>>> Please download and test your products with kernel 4.4.2 RC2 and vote.
>>>> Vote will be open for 72 hours or longer as needed.
>>>>
>>>> *Source and binary distribution files:*
>>>> https://svn.wso2.org/repos/wso2/people/aruna/v4.4.2-rc2
>>>>
>>>> *Maven staging repository:*
>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-019/
>>>>
>>>> *The tag to be voted upon:*
>>>> https://github.com/wso2/carbon-kernel/tree/v4.4.2-rc2
>>>>
>>>>
>>>> [ ] Broken - do not release (explain why)
>>>> [ ] Stable - go ahead and release
>>>>
>>>>
>>>> Thank you
>>>> Carbon Team
>>>>
>>>> --
>>>>
>>>> *Manuri Amaya Perera*
>>>>
>>>> *Software Engineer*
>>>>
>>>> *WSO2 Inc.*
>>>>
>>>> *Blog: http://manuriamayaperera.blogspot.com
>>>> <http://manuriamayaperera.blogspot.com>*
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Sasikala Kottegoda
>>> *Software Engineer*
>>> WSO2 Inc., http://wso2.com/
>>> lean. enterprise. middleware
>>> Mobile: +94 774835928/712792401
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Vitharana
>>
>> Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94715883223
>> Blog : http://lankavitharana.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2
could we hold the release until permission related issue?
On Tue, Oct 13, 2015 at 5:06 PM, Rajith Vitharana <raji...@wso2.com> wrote:
> Hi,
>
> We have tested Basic scenarios + installing DSS features in ESB 4.9.0 and
> those are successful (there were some integration test failiers due to
> configuration changes which needs some fixes in test cases in DSS)
>
> +1 to release
>
> Thanks,
>
> On Tue, Oct 13, 2015 at 4:58 PM, Sasikala Kottegoda <sasik...@wso2.com>
> wrote:
>
>> Hi Manuri,
>>
>> We tested MB 3.0.0 with this release and our scenario of queue creation
>> fails after giving a permission denied error. The scenario is as follows:
>>
>> 1. Create a user "user1" with a role assigned with permission to create
>> queues.
>> 2. Login from "user1" and try to create a queue, we get a permission
>> denied error.
>>
>> When creating a queue the following happens from our code.
>>
>> 1. We create an internal role for the queue and assign it to the current
>> user with permissions assigned.
>>
>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>
>> PERMISSION_CHANGE_PERMISSION);
>>
>> 2. Next, we create the queue and update permissions for the queue. In this
>> step, we check if the current user has permissions to change the queue.
>>
>> String[] userRoles =
>> userRealm.getUserStoreManager().getRoleListOfUser(loggedInUser);
>> for (String userRole : userRoles) {
>> if (userRealm.getAuthorizationManager().isRoleAuthorized(
>> userRole, queueID, PERMISSION_CHANGE_PERMISSION)) {
>> isUserHasChangePermission = true;
>> }
>> }
>>
>> At this stage, *'*(userRealm.getAuthorizationManager().isRoleAuthorized(
>> userRole, queueID, PERMISSION_CHANGE_PERMISSION))' false
>> implying that any of roles assigned to the user do not have permissions to
>> change the queue, thus not allowing the user to create the queue.
>>
>>
>> Thank you
>>
>>
>> On Mon, Oct 12, 2015 at 9:24 PM, Manuri Amaya Perera <manu...@wso2.com>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> WSO2 Carbon Kernel 4.4.2 RC2 Release Vote.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12396
>>>
>>> Please download and test your products with kernel 4.4.2 RC2 and vote.
>>> Vote will be open for 72 hours or longer as needed.
>>>
>>> *Source and binary distribution files:*
>>> https://svn.wso2.org/repos/wso2/people/aruna/v4.4.2-rc2
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-019/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/carbon-kernel/tree/v4.4.2-rc2
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thank you
>>> Carbon Team
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> <http://manuriamayaperera.blogspot.com>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sasikala Kottegoda
>> *Software Engineer*
>> WSO2 Inc., http://wso2.com/
>> lean. enterprise. middleware
>> Mobile: +94 774835928/712792401
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Vitharana
>
> Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Sasikala Kottegoda
Hi Sasikala, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! regards, -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][MB][MQTT] How to handle permission denied to subscribe a topic due to tenancy
l, >>>>>> >>>>>> If a tenant don't have permission to subscribe to a given topic >>>>>> (tenant 'a.com' try to subscribe to tenant 'b.com') currently it >>>>>> will keep connected even though it's not subscribed, because user >>>>>> authentication was successful. This is misleading to subscriber as no >>>>>> return code sent and it's actively connected to broker. >>>>>> AFAIK mqtt don't define how to handle tenancy scenarios in it's spec. >>>>>> Couldn't find a definition in MQTT spec 3.1.0/3.1.1 on how to reject if >>>>>> permission denied to subscribe to a given topic(due to tenancy). >>>>>> >>>>>> One option to handle this scenario is to send return code 5 (Connection >>>>>> Refused, not authorized) to client if it doesn't have permission to >>>>>> subscribe to given topic. This way client will disconnect if it don't >>>>>> have >>>>>> permission to subscribe. Is this acceptable or are there any alternatives >>>>>> to handle this scenario? >>>>>> >>>>>> jira https://wso2.org/jira/browse/MB-1409 >>>>>> >>>>>> Thanks, >>>>>> Pumudu >>>>>> -- >>>>>> Pumudu Ruhunage >>>>>> Associate Software Engineer | WSO2 Inc >>>>>> M: +94 779 664493 | http://wso2.com >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Yasassri Ratnayake >>>>> Software Engineer - QA >>>>> WSO2 Inc ; http://wso2.com >>>>> lean.enterprise.middleware >>>>> *Mobile : +94715933168 <%2B94715933168>* >>>>> *Blogs : http://yasassriratnayake.blogspot.com >>>>> <http://yasassriratnayake.blogspot.com/>* >>>>> *http://wso2logs.blogspot.com >>>>> <http://wso2logs.blogspot.com>* >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Hasitha Abeykoon* >>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>> *cell:* *+94 719363063* >>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>> >>>> >>> >>> >>> -- >>> *Pamod Sylvester * >>> >>> *WSO2 Inc.; http://wso2.com <http://wso2.com>* >>> cell: +94 77 7779495 >>> >> >> >> >> -- >> Pumudu Ruhunage >> Associate Software Engineer | WSO2 Inc >> M: +94 779 664493 | http://wso2.com >> > > > -- > *Pamod Sylvester * > > *WSO2 Inc.; http://wso2.com <http://wso2.com>* > cell: +94 77 7779495 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1
Hi, If you are hoping to handle/catch 'IntegrityConstraintViolationException' consider following: 'IntegrityConstraintViolationException' is only thrown in Oracle and mysql database drivers ( check their driver source code and you will see). from what I know MSSQL drivers doesn't throw these. I have seen similar approach has been adapted in Hibernate (ORM) framework code as well. therefore, if you go down this path you need to check SQLState [1]. You might find[2] useful as reference. [1] http://docs.oracle.com/javase/7/docs/api/java/sql/SQLException.html#getSQLState() [2] https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/wso2/andes/store/rdbms/RDBMSStoreUtils.java#115 On Fri, Sep 25, 2015 at 11:16 AM, Darshana Gunawardana <darsh...@wso2.com> wrote: > Hi Indunil, > > On Fri, Sep 25, 2015 at 10:15 AM, Indunil Upeksha Rathnayake > <indu...@wso2.com> wrote: >> >> Hi, >> >> The deadlock issue(https://wso2.org/jira/browse/MB-1326) come up in oracle >> and mssql when clearResourceAuthorizations where permissions are deleted in >> UM_ROLE_PERMISSIONS, UM_USER_PERMISSIONS and UM_PERMISSION tables through >> one transaction. The fix would be using cascade delete for above tables. > > > +1 > >> >> But I think another issue(foreign key constraint violation) may come up >> when addAuthorizationForRole, as following example scenario. Ex: Node1 may >> be retrieve the permission entry in UM_PERMISSION table (in >> addAuthorizationForRole()) and just after that node2 may delete the entry >> (in clearResourceAuthorizations()) and after that when node1 trying to >> delete & add permissions in UM_ROLE_PERMISSIONS (in >> addAuthorizationForRole()) will return the above exception since the entry >> in UM_PERMISSION is already deleted. >> >> I think the fix need to be, if UM_ROLE_PERMISSIONS and UM_PERMISSION >> tables are going to update, first have to lock both tables, until all the >> required operations are finished. Then meanwhile another node can't delete >> any entries. > > > Have you able to reproduce this behavior? I guess we cannot lock those > tables from the java code in db in dependent manner. Please check with our > db experts. > > In worst case we could handle IntegrityConstraintViolationException since > its ok to avoiding addAuthorization for a permission which got deleted > later. > > Thanks, > >> >> Please provide your opinions regarding this. >> >> Thanks and Regards >> -- >> Indunil Upeksha Rathnayake >> Software Engineer | WSO2 Inc >> Emailindu...@wso2.com > > > > > -- > Regards, > > Darshana Gunawardana > Senior Software Engineer > WSO2 Inc.; http://wso2.com > E-mail: darsh...@wso2.com > Mobile: +94718566859 > Lean . Enterprise . Middleware -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1
do we have a fix for https://wso2.org/jira/browse/MB-1326 ? On Fri, Sep 18, 2015 at 4:51 PM, Manuri Amaya Perera <manu...@wso2.com> wrote: > Hi Kasun, > > Noted. > > Thank you. > > On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri <ka...@wso2.com> wrote: >> >> Hi Manuri, >> >> We don't have an immediate requirement to have these fixes for ESB as 4.9 >> is already released. But these are missing patches and we need to at least >> make them blockers for the next release. >> >> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera <manu...@wso2.com> >> wrote: >>> >>> Hi Kasun, >>> >>> [1] is already fixed. Regarding [2], according to the comment in the >>> jira, the fix is available in [3]. >>> >>> I suppose [4] also is fixed. @Ishara Could you please confirm ? >>> >>> Rest of the issues will be fixed in the next release. >>> >>> >>> [1] https://wso2.org/jira/browse/CARBON-15184 >>> [2] https://wso2.org/jira/browse/CARBON-14730 >>> [3] https://github.com/wso2/cipher-tool >>> [4] https://wso2.org/jira/browse/CARBON-14959 >>> >>> Thank you. >>> >>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri <ka...@wso2.com> wrote: >>>> >>>> We found that following fixes were missing in latest kernel release >>>> while doing ESB 4.9. >>>> Any plans to include them in this release. >>>> >>>> https://wso2.org/jira/browse/CARBON-14807 >>>> https://wso2.org/jira/browse/CARBON-14959 >>>> https://wso2.org/jira/browse/CARBON-14764 >>>> https://wso2.org/jira/browse/CARBON-15248 >>>> https://wso2.org/jira/browse/CARBON-15141 >>>> https://wso2.org/jira/browse/CARBON-15223 >>>> https://wso2.org/jira/browse/CARBON-15184 >>>> https://wso2.org/jira/browse/CARBON-14730 >>>> https://wso2.org/jira/browse/CARBON-15248 >>>> >>>> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera <manu...@wso2.com> >>>> wrote: >>>>> >>>>> Hi Devs, >>>>> >>>>> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote. >>>>> >>>>> This release fixes the following issues: >>>>> https://wso2.org/jira/issues/?filter=12396 >>>>> >>>>> Please download and test your products with kernel 4.4.2 RC1 and vote. >>>>> Vote will be open for 72 hours or as longer as needed. >>>>> >>>>> Source and binary distribution files: >>>>> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2 >>>>> >>>>> Maven staging repository: >>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/ >>>>> >>>>> The tag to be voted upon: >>>>> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1 >>>>> >>>>> >>>>> [ ] Broken - do not release (explain why) >>>>> [ ] Stable - go ahead and release >>>>> >>>>> >>>>> Thank you >>>>> Carbon Team >>>>> >>>>> >>>>> -- >>>>> Manuri Amaya Perera >>>>> Software Engineer >>>>> WSO2 Inc. >>>>> >>>>> Blog: http://manuriamayaperera.blogspot.com >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Kasun Indrasiri >>>> Software Architect >>>> WSO2, Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> cell: +94 77 556 5206 >>>> Blog : http://kasunpanorama.blogspot.com/ >>> >>> >>> >>> >>> -- >>> Manuri Amaya Perera >>> Software Engineer >>> WSO2 Inc. >>> >>> Blog: http://manuriamayaperera.blogspot.com >> >> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ > > > > > -- > Manuri Amaya Perera > Software Engineer > WSO2 Inc. > > Blog: http://manuriamayaperera.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need to Override "registry.xml" at Product Level to Work with Registry Search
s="org.wso2.carbon.registry.indexing.indexer.MSPowerpointIndexer" >>>>>>>> mediaTypeRegEx="application/vnd.ms-powerpoint"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.MSWordIndexer" >>>>>>>> mediaTypeRegEx="application/msword"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PDFIndexer" >>>>>>>> mediaTypeRegEx="application/pdf"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.XMLIndexer" >>>>>>>> mediaTypeRegEx="application/xml"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.XMLIndexer" >>>>>>>> mediaTypeRegEx="application/(.)+\+xml"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>> mediaTypeRegEx="application/swagger\+json"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>> mediaTypeRegEx="application/(.)+\+json"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>> mediaTypeRegEx="text/(.)+"/> >>>>>>>> >>>>>>> class="org.wso2.carbon.registry.indexing.indexer.PlainTextIndexer" >>>>>>>> mediaTypeRegEx="application/x-javascript"/> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> pathRegEx="/_system/config/repository/dashboards/gadgets/swfobject1-5/.*[.]html"/> >>>>>>>> >>>>>>> pathRegEx="/_system/local/repository/components/org[.]wso2[.]carbon[.]registry/mount/.*"/> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> We have 2 options >>>>>>> >>>>>>>1. We can override registry.xml file in product level with >>>>>>>required config >>>>>>>2. We can document that we need to add the necessary config to >>>>>>>registry.xml in order to make registry functionality work without >>>>>>>overriding it product level >>>>>>> >>>>>>> What would be the better approach? >>>>>>> >>>>>>> Thanks >>>>>>> /Thusitha >>>>>>> -- >>>>>>> Thusitha Dayaratne >>>>>>> Software Engineer >>>>>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>>>> >>>>>>> Mobile +94712756809 >>>>>>> Blog alokayasoya.blogspot.com >>>>>>> Abouthttp://about.me/thusithathilina >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Niranjan Karunanandham* >>>>>> Senior Software Engineer - WSO2 Inc. >>>>>> WSO2 Inc.: http://www.wso2.com >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> *Chandana Napagoda* >>>> Senior Software Engineer >>>> WSO2 Inc. - http://wso2.org >>>> >>>> *Email : chand...@wso2.com <chand...@wso2.com>**Mobile : >>>> +94718169299 <%2B94718169299>* >>>> >>>> *Blog :http://cnapagoda.blogspot.com >>>> <http://cnapagoda.blogspot.com>* >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> *S. Suhothayan* >>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>> *WSO2 Inc. *http://wso2.com >>> * <http://wso2.com/>* >>> lean . enterprise . middleware >>> >>> >>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >>> >> >> >> >> -- >> >> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> >> >> > > > > -- > > *S. Suhothayan* > Technical Lead & Team Lead of WSO2 Complex Event Processor > *WSO2 Inc. *http://wso2.com > * <http://wso2.com/>* > lean . enterprise . middleware > > > *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: > http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: > http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: > http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Prioritize requirements for MB
do we have hierarchical topics (for JMS and MQTT) covered? On Fri, Sep 4, 2015 at 6:30 PM, Indika Sampath <indi...@wso2.com> wrote: > Hi Dilini, > > We need to add shared durable topic subscription under JMS to this mind > map. > > Cheers! > > On Fri, Sep 4, 2015 at 5:31 PM, Dilini Gunatilake <dili...@wso2.com> > wrote: > >> Hi All, >> >> Please find the mind map attached herewith which includes the features of >> MB at high level. Out of that, we have prioritized the areas (with ! mark) >> which we believe that should be covered by 25th. More features should be >> added to MQTT section and please free to add and share anything you think >> important. >> >> As discussed, we can collaboratively decide who will perform certain >> tests as the QA team would not be able to cover all the prioritized areas >> by 25th. As for the Alpha2 release, we will select a subset of these areas >> by Monday and cover it before the Beta release. >> >> Please feel free to share your thoughts. >> >> Thank you. >> Regards, >> >> -- >> >> *Dilini GunatilakeSoftware Engineer - QA Team* >> Mobile : +94 (0) 771 162518 >> dili...@wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Indika Sampath > Senior Software Engineer > WSO2 Inc. > http://wso2.com > > Phone: +94 716 424 744 > Blog: http://indikasampath.blogspot.com/ > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Shared Subscription - unsubscribe operation - expected behavior
than when are you suggesting to do the actual 'unsubscribe' ? after last one says 'unsubscribe'? On Mon, Aug 31, 2015 at 11:16 AM, Asanka Abeyweera <asank...@wso2.com> wrote: > I think we should follow what we do with the queue subscriptions. For > queues we don't remove all the subscriptions when a single subscriber sends > an unsubscribe request. > > Therefore +1 for option 2. > . > > On Mon, Aug 31, 2015 at 11:02 AM, Pamod Sylvester <pa...@wso2.com> wrote: > >> Hi All, >> >> When enabled shared subscriptions, it creates subscription groups which >> are distinguished through the client ids of the consumers. hence, for a >> given durable topic it allows multiple subscriptions to be bound with the >> same client id, in return when a message is delivered, for the consumers >> bound with the same client id, the messages will be load balanced. >> >> The question is, >> >> in the event where one of the subscriptions with a given client id sends >> an unsubscribe request, >> >> 1) should we remove all the other subscriptions bound to the topic with >> the same client id or >> 2) should we remove only that particular subscription ? >> >> To elaborate more, the following is an example, >> >> i.e let's say there're 10 subscriptions with the same client id bound to >> a topic as shared durable subscriptions, if the 10th subscriber sends a >> un-subscription request should we remove all other 9 subscriptions >> belonging to the group or should we remove only that particular >> subscription and eventually remove the underlaying queue which persists >> offline messages when we identify when the request is sent by the last >> subscription belonging to the shared subscription group (client id). >> >> What should be the best way to handle this ? >> >> Thanks, >> Pamod >> -- >> *Pamod Sylvester * >> >> *WSO2 Inc.; http://wso2.com <http://wso2.com>* >> cell: +94 77 7779495 >> > > > > -- > Asanka Abeyweera > Software Engineer > WSO2 Inc. > > Phone: +94 712228648 > Blog: a5anka.github.io > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Shared Subscription - unsubscribe operation - expected behavior
I think we should remove everyone in such situation. 'unsubscribe' is a conscious decision compared to a disconnect which could happen even due to a network outage. Thoughts? On Mon, Aug 31, 2015 at 11:02 AM, Pamod Sylvester pa...@wso2.com wrote: Hi All, When enabled shared subscriptions, it creates subscription groups which are distinguished through the client ids of the consumers. hence, for a given durable topic it allows multiple subscriptions to be bound with the same client id, in return when a message is delivered, for the consumers bound with the same client id, the messages will be load balanced. The question is, in the event where one of the subscriptions with a given client id sends an unsubscribe request, 1) should we remove all the other subscriptions bound to the topic with the same client id or 2) should we remove only that particular subscription ? To elaborate more, the following is an example, i.e let's say there're 10 subscriptions with the same client id bound to a topic as shared durable subscriptions, if the 10th subscriber sends a un-subscription request should we remove all other 9 subscriptions belonging to the group or should we remove only that particular subscription and eventually remove the underlaying queue which persists offline messages when we identify when the request is sent by the last subscription belonging to the shared subscription group (client id). What should be the best way to handle this ? Thanks, Pamod -- *Pamod Sylvester * *WSO2 Inc.; http://wso2.com http://wso2.com* cell: +94 77 7779495 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Anuja Herath
Hi Anuja, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! regards, -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
Could we get a kernel release with this fixed?
On Sun, Aug 16, 2015 at 7:59 PM, Johann Nallathamby joh...@wso2.com wrote:
I have resolved CARBON-15265/IDENTITY-3511 as it seems to be related but
different. The current issue will be tracked in IDENTITY-3423.
On Fri, Aug 14, 2015 at 4:07 PM, Indika Sampath indi...@wso2.com wrote:
Hi Tharindu,
Please find the attach files which contains stack trace separately.
Cheers!
On Fri, Aug 14, 2015 at 3:55 PM, Tharindu Edirisinghe tharin...@wso2.com
wrote:
Hi Indika,
We are looking to identify the issue. Can you also send us the stack
trace of the two scenarios separately.
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 3:50 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Tharindu,
Above deadlock occurred when we remove topic subscription.
DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
We are getting another deadlock when we adding topic subscription also.
INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID,
UM_TENANT_ID, UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM
UM_HYBRID_ROLE WHERE UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND
UM_TENANT_ID=-1234), -1234, (SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE
UM_TENANT_ID=-1234 AND UM_DOMAIN_NAME='PRIMARY'))
Please find the attached text file which contains output of SHOW ENGINE
INNODB STATUS;
Cheers!
On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath indi...@wso2.com
wrote:
Hi Tharindu,
Please find the attach text file which contains output of above
command.
Cheers!
On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe
tharin...@wso2.com wrote:
Hi Ramith,
It seems this is not the exact same issue reported in [1]. For
investigating further can you connect to mysql database from
terminal/mysql
client and run the following command and share the output with us. We
should be able to see the database level errors caused from the output of
this command [2].
*SHOW ENGINE INNODB STATUS;*
[1] https://wso2.org/jira/browse/CARBON-15265
[2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
Thanks,
TharinduE
On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe ram...@wso2.com
wrote:
$subject. Could we have a look?
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
--
Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Identity Server Team
Blog : tharindue.blogspot.com
mobile : +94 775 181586
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Thanks Regards,
*Johann Dilantha Nallathamby*
Technical Lead Product Lead of WSO2 Identity Server
Integration Technologies Team
WSO2, Inc.
lean.enterprise.middleware
Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1
$subject. Could we have a look? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [MB] puppet scripts/modules
Hi Manula, It seems [1] is the place we maintain puppet modules for products. Shall we commit MB puppet modules also there? [1] https://github.com/wso2/Puppet-Modules regards -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] puppet scripts/modules
Hi Manula, No problem, lets commit to the new location once we have it. On Fri, Jul 17, 2015 at 9:50 PM, Manula Waidyanatha man...@wso2.com wrote: Hi Ramith, Yes. No problem. But we have planned to have a separate repo for each puppet module. But for now you can commit the MB module there. On Fri, Jul 17, 2015 at 7:37 AM, Ramith Jayasinghe ram...@wso2.com wrote: Hi Manula, It seems [1] is the place we maintain puppet modules for products. Shall we commit MB puppet modules also there? [1] https://github.com/wso2/Puppet-Modules regards -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware -- Regards, Manula Waidyanatha Systems Engineer, WSO2, Inc. Phone: +94 774 195853 Blog: blog.manula.org -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 4.9.0-M8-SNAPSHOT Unable to subscribe added topics
) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassCastException: org.wso2.carbon.registry.core.ResourceImpl cannot be cast to org.wso2.carbon.registry.core.Collection at org.wso2.carbon.event.core.internal.topic.registry.RegistryTopicManager.addSubscriptions(RegistryTopicManager.java:395) at org.wso2.carbon.event.core.internal.topic.registry.RegistryTopicManager.getSubscriptions(RegistryTopicManager.java:310) at org.wso2.carbon.event.admin.internal.TopicManagerAdminService.getWsSubscriptionsForTopic(TopicManagerAdminService.java:161) ... 63 more I repeated the same on ESB-4.8.1 and it didn't generate this exception and can run sample without any issue. [1] https://docs.wso2.com/display/IntegrationPatterns/Publish-Subscribe+Channel Thanks, /charithag -- *Charitha Goonetilleke* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 751 3669 %2B94777513669 Twitter:@CharithaWs https://twitter.com/CharithaWs, fb: charithag https://www.facebook.com/charithag, linkedin: charithag http://www.linkedin.com/in/charithag ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- *Charitha Goonetilleke* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 751 3669 %2B94777513669 Twitter:@CharithaWs https://twitter.com/CharithaWs, fb: charithag https://www.facebook.com/charithag, linkedin: charithag http://www.linkedin.com/in/charithag ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Defining bind addresses for each transport in MB 3.0.0
+1 On Tue, Jul 14, 2015 at 5:14 PM, Pumudu Ruhunage pum...@wso2.com wrote: Hi All, Currently for all the transports MB have a one global bind address defined in 'conf/broker.xml'. Since MB supports amqp and mqtt protocols, there should be a way to configure bind addresses for each transport separately. IMO defining bind addresses for each transport in 'broker.xml' instead of define it globally will solve this issue. WDYT ? Regards, Pumudu -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Load test with message store/proc with MB
Hasitha did some tests on MB v 3.0.0 early milestones + ESB (which is more relevant version at this point) . Yes. this falls under MB test scope. we can resolve once we test again. On Thu, Jul 9, 2015 at 2:10 PM, Kasun Indrasiri ka...@wso2.com wrote: I think this already in the MB test plan. Have we tested this? If so please resolve [1]. [1] https://wso2.org/jira/browse/ESBJAVA-3024 -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in removing messages of non durable topics
I think we can simplify this one. and do a delete without even getting
message ids.
On Mon, Jul 6, 2015 at 5:05 PM, Pamod Sylvester pa...@wso2.com wrote:
Hi Hasitha,
With reference to the discussion in [1], this was done to prevent
Tombstone overwhelming exception when Cassandra was used as the message
store.
AFAIR The process of purging was as follows,
1) From MessageMetaData CF, retrieve the corresponding message ids
2) Delete the corresponding messages from MessageMetaData and then delete
them from the MessageContent.
When transacting 1,000,000 messages and disconnection of the
subscription will go through the above mentioned process.
The issue is,
a) Message content is not partitioned based on the queue name as Message
Meta data. so we cannot delete the content row wise, which restricted us to
retrieve ids from Message Meta data and remove them from content.
b) When retrieving message meta data (let's say we used a range query to
select all the ids) there will be tombstones that will be selected with
that query that will hit the limit, causing the Tombstone overwhelming
exception.
As a solution, when removeMessagesOfDestinationForNode() is called we
get the current fresh slot, and the idea of getting the start id of the
slot is that it assures that the message ids that should be selected from
the message meta data should be greater than the value defined in the start
id (since messages with ids start id are the messages that have being
delivered already that has caused tombstones).
Also, I believe we could change the flow now since we discontinue
Cassandra. Since in RDBMS you could select all ids without any issue.
Hope this explains your query.
[1] [Dev][MB] TombstoneOverwhelmingException When Purge Operation is
Triggered When Subscription Disconnection/Deletion
Thanks,
Pamod
On Mon, Jul 6, 2015 at 7:00 AM, Hasitha Hiranya hasit...@wso2.com wrote:
Hi,
Identified an issue regarding message purging when last subscriber for a
topic is disconnected from broker cluster.
@org.wso2.andes.kernel.OrphanedMessageHandler
private void removeMessagesOfDestinationForNode(String destination,
String ownerName,
boolean isTopic) throws AndesException {
try {
Long startMessageID = null;
Long endMessageID = null;
//Will first retrieve the last unassigned slot id
String nodeID =
ClusterResourceHolder.getInstance().getClusterManager().getMyNodeID();
//Will get the storage queue name
*String storageQueue =
AndesUtils.getStorageQueueForDestination(destination, nodeID, isTopic);*
*//We get the relevant slot from the coordinator if running
on cluster mode*
*Slot unassignedSlot =
MessagingEngine.getInstance().getSlotCoordinator().getSlot(storageQueue);*
*//We need to get the starting message ID to inform the DB to
start slicing the message from there*
*//This step would be done in order to ensure that tombstones
will not be fetched during the querying*
*//operation*
*startMessageID = unassignedSlot.getStartMessageId();*
endMessageID = unassignedSlot.getEndMessageId();
// This is a class used by AndesSubscriptionManager. Andes
Subscription Manager is behind Disruptor layer.
// Hence the call should be made to MessagingEngine NOT Andes.
// Calling Andes methods from here will lead to probable
deadlocks if Futures are used.
// NOTE: purge call should be made to MessagingEngine not
Andes
if (0 endMessageID) {
//If the slot id is 0, which means for the given storage
queue there're no unassigned slots which means
//we don't need to purge messages in this case
//The purpose of purge operation is to make sure that
unassigned slots will be removed if no subs exists
MessagingEngine.getInstance().purgeMessages(destination,
ownerName, isTopic, startMessageID);
}
} catch (ConnectionException e) {
String mesage = Error while establishing a connection with
the thrift server;
log.error(mesage);
throw new AndesException(mesage, e);
}
}
Why we need a start message id here ?
What about purging the whole internal queue (related to topic) ?
*MessagingEngine.getInstance().purgeMessages(destination, ownerName,
isTopic, 0);*
Thanks
--
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2.com http://wso2.com*
cell: +94 77 7779495
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
Re: [Dev] make MB bind to 0.0.0.0 by default
could you create a public jira.? On Fri, Jun 26, 2015 at 11:34 AM, Manuranga Perera m...@wso2.com wrote: MB by default bind to 127.0.0.1 . This is not sometime visible through other interfaces such were Wi-Fi and has to be manually changed to IP form broker.xml. It's better if we can bind it to 0.0.0.0 or to :: .Please test this and make it the default. -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : manu@wso2.comint -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Pumudu Ruhunage
Hi Pumudu, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! regards, -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [MB]Shall we enable carbon matrices in MB by default?
$subject ? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Console allows the user to delete a queue when publishing
This is due to how we process any-inbound events ( queue add/delete, recieve messages etc). Yes, this is a edge case (- where user deletes a queue which is very active) therefore lets create a jira. regards Ramith On Mon, Jun 15, 2015 at 10:09 AM, Pamod Sylvester pa...@wso2.com wrote: Hi Jason et all, We restrict queue deletion if there're active subscribers for it. The messages published will not be accepted if the queue was deleted. The filtering is done on acceptance/rejection at Message Pre Processing stage. It seems that when the delete event is called some of the messages have passed the pre processing stage and were accepted in. Resulting in noticing messages after the queue is re added. @Ramith and team, should we introduce another filer before adding the messages to slots, db ? thoughts ? Thanks, Pamod On Mon, Jun 15, 2015 at 9:22 AM, Jason De Silva jas...@wso2.com wrote: Hi All, In MB 3.0.0 Alpha pack I observed that while a publisher is publishing messages to a queue it is possible to delete the queue from the console and a popup shows that it is deleted successfully. After couple of refreshes the queue is not shown in console. Later if the same queue is re-added via the console the queue will have some messages shown, is it valid? Regards, Jason -- Jason De Silva *Software Engineer - QA* Mobile: +94 (0) 772 097 678 Email: jas...@wso2.com WSO2 Inc. www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pamod Sylvester * *WSO2 Inc.; http://wso2.com http://wso2.com* cell: +94 77 7779495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Revamping MB Test Framework to cut down time.
+1 On Sat, Jun 13, 2015 at 1:59 AM, Akalanka Pagoda Arachchi darsha...@wso2.com wrote: Hi Hemika, Also I think we can use a subset of all the available test cases in the in-memory mode rather than running them all again in the in-memory mode. Since in-memory mode does not guarantee the delivery and was suggested to be used as a developer testing mode rather than a production deployment mode, this would be fine. WDYT Ramith? Thanks, Akalanka. On Tue, Jun 9, 2015 at 7:24 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi Ramith, Yes TestNg provides the facility of running tests in parallel. Considering carbon servers the only possible level is in methods level you can achieve this by defining parallel property in testNg.xml as follows suite name=Test-method Suite parallel=methods thread-count=2 Since we are performing configuration level changes such as server startup and user deployment in listener level , parallel level test execution on Test and Suite level will not be possible. But you may be able to execute test methods parallel. But we have to test what will happen is depend on and priorities are used in method level. As per our experience your test suite must be matured and 100% confident before peeping out to this. When it come to test failure it is really hard to debug. So what i recommend at the moment is make the tests stable and confident before moving in to this. Thank you, Dharshana. On Tue, Jun 9, 2015 at 3:19 PM, Waruna Perera waru...@wso2.com wrote: Adding Krishantha On Tue, Jun 9, 2015 at 1:41 PM, Ramith Jayasinghe ram...@wso2.com wrote: generally very nice to do this. @Krishantha, Can we run integration tests in parallel against a carbon server? On Tue, Jun 9, 2015 at 1:34 PM, Hemika Kodikara hem...@wso2.com wrote: Hi All, When executing the MB integration tests, we noticed that it takes a long time to get executed. I have several suggestions that could help us to cut down time. 1. Running tests classes in parallel [1]. Here we have to state how many classes to run in parallel. 2. Disable message receiving loggings in test cases. This can either be disabled or be turned into debug logs. If we are changing it to debug logs, we would need a way to enable debug logs(Have to look into this). 3. Reduce the number of messages published in each test case. What are your thoughts on the above suggestions ? [1] - http://howtodoinjava.com/2014/12/02/testng-executing-parallel-tests/ Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94770342233 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791 078-4721791* -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Viewing message content on DLC message list page.
+1 On Wed, Jun 10, 2015 at 2:40 PM, Asitha Nanayakkara asi...@wso2.com wrote: +1 On Wed, Jun 10, 2015 at 1:21 PM, Hemika Kodikara hem...@wso2.com wrote: Hi All, Currently in the DLC message list page, we are showing the only 15 characters of the message content in the table with a link to another page which shows the complete content. The issue that I am mentioning here is that even if the message content has less than 15 characters, still that link appears to show the complete content on another page(See attachment). The change that I am suggesting is to only show the link if the message content is more than 15 characters. If the message content has less that 15 characters, that link wont be shown. WDYT ? Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Revamping MB Test Framework to cut down time.
generally very nice to do this. @Krishantha, Can we run integration tests in parallel against a carbon server? On Tue, Jun 9, 2015 at 1:34 PM, Hemika Kodikara hem...@wso2.com wrote: Hi All, When executing the MB integration tests, we noticed that it takes a long time to get executed. I have several suggestions that could help us to cut down time. 1. Running tests classes in parallel [1]. Here we have to state how many classes to run in parallel. 2. Disable message receiving loggings in test cases. This can either be disabled or be turned into debug logs. If we are changing it to debug logs, we would need a way to enable debug logs(Have to look into this). 3. Reduce the number of messages published in each test case. What are your thoughts on the above suggestions ? [1] - http://howtodoinjava.com/2014/12/02/testng-executing-parallel-tests/ Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Adding the capability to enable/disable message status
In my opinion we need to check if we really need keep the history in on-flight-message tracker. If we can wire up the enums (at compile time) to model the state transitions then we don't need to use this ( - just like we did for SlotState) thoughts? On Thu, May 28, 2015 at 4:09 PM, Pamod Sylvester pa...@wso2.com wrote: Hi All, Currently in OnflightMessageTracker we have a list of message statuses maintained under MsgData. Based on the current observation, these statuses are being only used to dump it to a file, mainly for debugging purposes. The method gets invoked each time a message is delivered to subscriber/subscribers and the addition of the status should be a synchronous call. Would it be safe to move this into the configuration, giving the option to the users to enable it ? Thanks, Pamod -- *Pamod Sylvester * *WSO2 Inc.; http://wso2.com http://wso2.com* cell: +94 77 7779495 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error logged at INFO level when starting MB integration tests.
/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Jacoco based code coverage genration
with products already
migrated JDK 1.7. Specially products with multiple test modules
(ESB, G-Reg
BPS)
Lets focus on testing following scenarios before the release.
Test Scenarios for coverage :
1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage
numbers.
To get started with Jacoco coverage :
1. Edit your test module pom and replace emma copy dependency
execution configuration with below.
execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution
2. Include jacoco argent as a dependency to root pom.
dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency
jacoco.agent.version0.7.4.201502262128/jacoco.agent.version
3. Remove following system properties from surefire plugin.
emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output
You will find following log entries in console with required
details to view the report once coverage generation completed.
Available
report formats are XML, HTML and CSV
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage dump file path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco class file path :
/Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage report path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco/coverage
Thanks,
Krishantha.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
--
Waruna Perera
Senior Software Engineer - Test Automation
Mobile: +94 77 3867037
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] 'jmstansport' sample in MB is not related to JMS.
HI, I'm in favour of deprecating this one. @Shammi, @Hasitha: thoughts? On Thu, May 21, 2015 at 2:53 PM, Hemika Kodikara hem...@wso2.com wrote: Hi All, In MB 3.0.0, we have a sample called jmstansport. As far as I understood in this sample was that a service is hosted using a wsdl and its methods are called using generated stubs. So in my opinion, this is not related to JMS. I was looking into the sample because of the following JIRA : https://wso2.org/jira/browse/MB-536 Initially I got a different exception which I was able to fix using the following jar. axis2-transport-jms-1.1.0-wso2v11.jar My concern is that should we keep this in MB samples ? Correct me if my findings are wrong. Source code for sample [1]. [1] - https://github.com/wso2/product-mb/tree/master/modules/samples/product/jmstransport Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Error while starting MB 3.0.0 cluster setup
) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4237) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4169) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2617) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2778) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2825) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2156) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2323) at org.wso2.andes.store.rdbms.RDBMSAndesContextStoreImpl.getAllQueuesStored(RDBMSAndesContextStoreImpl.java:684) ... 112 more Thanks Amalka -- Indika Sampath Senior Software Engineer WSO2 Inc. http://wso2.com Phone: +94 716 424 744 Blog: http://indikasampath.blogspot.com/ -- Amalka Subasinghe Senior Software Engineer WSO2 Inc. Mobile: +94 77 9401267 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Amalka Subasinghe Senior Software Engineer WSO2 Inc. Mobile: +94 77 9401267 -- Indika Sampath Senior Software Engineer WSO2 Inc. http://wso2.com Phone: +94 716 424 744 Blog: http://indikasampath.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Carbon/AS] Could we commit patch attached at WSAS-1823
Hi Kishanthan, Could we have the diff attached in [1] WSAS-1823 reviewed and committed to git? [2] depends on it. [1] https://wso2.org/jira/browse/WSAS-1823 [2] https://wso2.org/jira/browse/MB-704 regards -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel
yes. But think about a situation where for some reason this message couldn't be received by the intended subscriber (may be because its crashed etc.) but the messages could be of value. So in my point view, its a conscious decision/task by user to select what to do with these messages in DLC (.e.g user may carefully select to where he wants them to be delivered). On Thu, Apr 9, 2015 at 12:38 PM, Pamod Sylvester pa...@wso2.com wrote: Also another question i have, let's say we're rerouting to among the consumers of the same topic. i.e for a given topic there're 3 durable subscriptions(A,B,C), When a message is sent two subscribers receive the message (A and B) and the message sent to C had failed and sent to the DLC. If we reroute the above to A, will it be the case where A received the same message which was received some time back. Thanks, Pamod On Thu, Apr 9, 2015 at 12:32 PM, Pamod Sylvester pa...@wso2.com wrote: Hi Pumudu, 1) Will it be the case where we specify the next route based on the subscription id ? Also in addition to the current flow, we might need to re create/activate a topic entry as well IMO since for durable subscriptions we create a queue and a topic entry 2) Also how with the permission model work in this case ? can there be a conflict of rerouting the message to a different subscriber of a different role? Thanks, Pamod On Thu, Apr 9, 2015 at 12:11 PM, Hasitha Hiranya hasit...@wso2.com wrote: Durable topic has a internal queue. we should be able to browse internal queue. Many people has asked for that feature. On Thu, Apr 9, 2015 at 1:27 AM, Pumudu Ruhunage pum...@wso2.com wrote: Hi Hasitha, Since this is a durable topic message will it make sense to reroute it to a queue ? Ideally shouldn't we reroute it to a durable topic, which is currently not handle by dlc? Thanks, On Wed, Apr 8, 2015 at 11:21 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi Pumudu, Yes. There will be cases where customers would like this reroute function. Make sure to reroute to the same queue for that sub ID. Also, make a note that, by the time you reroute, that subscription can be unsubscribed by user and queue is no longer there. Thanks On Wed, Apr 8, 2015 at 11:33 AM, Pumudu Ruhunage pum...@wso2.com wrote: Hi, Currently if a durable topic message didn't receive client acknowledgement from subscriber it will retry 10 times and move that durable topic message to dlc queue. dlc have 3 operations delete, restore and reroute. Out of these, delete and restore operations are functional for durable topic messages in dlc. But problem is that reroute operation only support for queues in dlc. Since dlc can contain durable topic messages, will it be possible to reroute dlc messages to topics as well ? WDYT ? Regards, -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] MB Recovery Code
Please create a L1. On Thu, Apr 2, 2015 at 3:11 AM, Hasitha Hiranya hasit...@wso2.com wrote: Hi Team, There is a code written to sync following memory caches time to time with the database. Individual node has a scheduled task to do this periodically. Idea is, if a hazelcast notification was lost, even late, try to act correct. 1. Subscriptions 2. Bindings 3. Exchanges 4. Queues I have put a warning of some entry is added or deleted from above caches by this task. I have seen this runs and prints warnings in long running tests. Butter to check this code before release. I had my developer testing at old times, but given this is critical for behavior of node, better double check. Thanks -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][MB] Truncate Tables Script MSSQL
could you host these in your git hub then we can download it from there. On Wed, Mar 25, 2015 at 7:25 PM, Pumudu Ruhunage pum...@wso2.com wrote: Hi, While doing mb cluster testing when i wants to start from clean database i've used attached db drop sql script with dsetup. only catch is that mssql user have to have drop/create database privileges to run this script. Make sure to changes database names if anyone using this script. Regards, On Tue, Feb 10, 2015 at 2:16 PM, Ramith Jayasinghe ram...@wso2.com wrote: shall we commit this to a scratch/personal area? On Tue, Feb 10, 2015 at 2:15 PM, Pamod Sylvester pa...@wso2.com wrote: Good stuff. This will be useful when carrying out tests, so that we will not need to drop the DB entirely. On Tue, Feb 10, 2015 at 2:10 PM, Akalanka Pagoda Arachchi darsha...@wso2.com wrote: Hi all, Attached truncate tables script to be used in testing/dev when MB is configured to be used with SQL Server. Thanks, Akalanka. -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791 078-4721791* -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Logging For WSO2 MB 3.0.0
+1. Good idea. On Wed, Mar 25, 2015 at 2:27 AM, Hasitha Hiranya hasit...@wso2.com wrote: Hi Team, In WSO2 MB there are several areas we need debug logs. 1. Inbound - when a message comes in , saving metadata and content to message store. 2. outbound - when a message is received and sent to subscribers 3. slot - slot manager related logs, what are the slots received by node 4. subscription - subscription created/disconnected/deleted/synced cache with DB/ sent cluster notification/got cluster notification 5. queues/bindings/exchanges related logs What about grouping them in log4j.properties file? So that when a issue comes, we can enable logs on the relevant section ? We can instruct the customers easily as well. WDYT? Thanks -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB + MB Testing - JMS Transactions
Shall we write a integration test case for this? On Fri, Mar 20, 2015 at 4:31 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi Team, Please refer following documentation from ESB https://docs.wso2.com/display/ESB481/JMS+Transactions If the back-end is down (or any error happened during mediation) message should not be removed from the queue. Many customers want this. So JMS transactions is the proper way to do this. We should focus our tests on that as well. Thanks -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB][Error] Server start up exception
)*
* at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)*
* at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)*
* at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)*
* at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)*
* at java.util.concurrent.FutureTask.run(FutureTask.java:262)*
* at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)*
* at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)*
* at java.lang.Thread.run(Thread.java:745)*
*Caused by: org.wso2.carbon.event.core.exception.EventBrokerException:
Cannot access the registry *
* at
org.wso2.carbon.event.core.internal.subscription.registry.RegistrySubscriptionManager.getAllSubscriptions(RegistrySubscriptionManager.java:291)*
* at
org.wso2.carbon.event.core.internal.CarbonEventBroker.loadExistingSubscriptions(CarbonEventBroker.java:78)*
* ... 103 more*
*Caused by:
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path /_system/governance/event/topicIndex*
* at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)*
* at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:172)*
* at
org.wso2.carbon.registry.core.session.UserRegistry.getInternal(UserRegistry.java:613)*
* at
org.wso2.carbon.registry.core.session.UserRegistry.access$400(UserRegistry.java:60)*
* at
org.wso2.carbon.registry.core.session.UserRegistry$5.run(UserRegistry.java:596)*
* at
org.wso2.carbon.registry.core.session.UserRegistry$5.run(UserRegistry.java:593)*
* at java.security.AccessController.doPrivileged(Native Method)*
* at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:593)*
* at
org.wso2.carbon.event.core.internal.subscription.registry.RegistrySubscriptionManager.getAllSubscriptions(RegistrySubscriptionManager.java:266)*
* ... 104 more*
On Fri, Mar 20, 2015 at 4:42 PM, Hemika Kodikara hem...@wso2.com wrote:
Hi Pranavan,
Will you be able to attach the wso2carbon.log file ?
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Fri, Mar 20, 2015 at 4:38 PM, Pranavan Theivendram pranav...@wso2.com
wrote:
[Looping in Hemika]
On Fri, Mar 20, 2015 at 3:27 PM, Pranavan Theivendram
pranav...@wso2.com wrote:
Hi All,
I am getting the following exception when I am starting a particular MB
node in the cluster. But the server is started.
*{org.wso2.carbon.event.core.internal.builder.EventBrokerHandler} -
Can not create the event broker
{org.wso2.carbon.event.core.internal.builder.EventBrokerHandler}*
*org.wso2.carbon.event.core.exception.EventBrokerConfigurationException:
Cannot get the subscriptions *
Can anyone please help me in his issue?
--
*Regards,*
*T.Pranavan*
*Software Engineering intern, WSO2*
*Mobile - +94775136836 %2B94775136836*
--
*Regards,*
*T.Pranavan*
*Software Engineering intern, WSO2*
*Mobile - +94775136836 %2B94775136836*
--
*Regards,*
*T.Pranavan*
*Software Engineering intern, WSO2*
*Mobile - +94775136836 %2B94775136836*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] How to handle flow controling in a event of fail-over
first one seems the correct way to me. thoughts? On Fri, Mar 20, 2015 at 5:55 PM, Asitha Nanayakkara asi...@wso2.com wrote: In MB Flow controlling mechanism is cluster unaware. Hence when one node enables flow control other node doesn't know about it. IMO we have two approaches to tackle this. - After client retries to connect to killed node (after failing to connect) it will try to connect to second node. At that time, since we are connecting to a new node, client can reset all flow control related information, from client, so that it can publish without waiting for flow control disable message from second node (That will never be sent to publisher by second node) - Or we can send a flow control disable message from MB node when a publisher connects (If global flow control is not enabled). I think the first option is better. Regards, On Fri, Mar 20, 2015 at 3:32 PM, Pumudu Ruhunage pum...@wso2.com wrote: Hi All, We did fail over testing on mb nodes in AWS instances and came across following issue. Following is the scenario tested in cluster. 1. Start 2 node mb cluster with nodeA (coordinator), nodeB. 2. Add queue subscriber MyQueue to nodeB. 3. Start publish MyQueue queue messages to nodeA. 4. After flow control enabled in nodeA, disconnect nodeA from the cluster. At a moment where flow control is enabled for the publisher, the coordinator is killed. Even though(assuming) that the publisher moves to the other node, it is still under flow control and the node does not disable the flow control for the publisher. Therefore the publisher does not publish any messages afterwards. How can we overcome this issue ? Regards, -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Out of memory error in long running mb cluster
Lets analyse the heap dump and see what caused the issue... also check the metrics recorded (via matric library) when server went OOM. On Wed, Mar 18, 2015 at 4:55 PM, Pumudu Ruhunage pum...@wso2.com wrote: Hi, I came across out of memory exception while doing long running test on mb cluster with oracle database as message store. Following was the scenario i tested. 1. Start two clustered mb nodes with serializers (nodeA(coordinator), nodeB). 2. Add queue subscriber MyQueue1, to nodeB and publish MyQueue1 messages to nodeA with average 1500 TPS. 3. Add queue subscriber MyQueue2 to nodeA and publish MyQueue2 messages to nodeB with average 1000 TPS. 4. After around 14 hours, om exception has thrown from nodeA and all operations has halted. After analysing heap dump i found which thread has thrown the error, and it's as follows. pool-25-thread-1 prio=5 tid=174 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:48) at java.lang.Long.toString(Long.java:267) at com.google.gson.stream.JsonReader.nextString(JsonReader.java:816) at com.google.gson.internal.bind.TypeAdapters$25.read(TypeAdapters.java:648) at com.google.gson.internal.bind.TypeAdapters$25.read(TypeAdapters.java:659) Local Variable: com.google.gson.internal.bind.TypeAdapters$25#1 Local Variable: com.google.gson.JsonArray#1 at com.google.gson.internal.bind.TypeAdapters$25.read(TypeAdapters.java:642) at com.google.gson.internal.Streams.parse(Streams.java:44) at com.google.gson.JsonParser.parse(JsonParser.java:84) at com.google.gson.JsonParser.parse(JsonParser.java:59) Local Variable: com.google.gson.stream.JsonReader#1 at com.google.gson.JsonParser.parse(JsonParser.java:45) at org.wso2.andes.server.cluster.coordination.hazelcast.custom.serializer.TreeSetLongWrapperSerializer.read(TreeSetLongWrapperSerializer.java:53) at org.wso2.andes.server.cluster.coordination.hazelcast.custom.serializer.TreeSetLongWrapperSerializer.read(TreeSetLongWrapperSerializer.java:33) at com.hazelcast.nio.serialization.StreamSerializerAdapter.read(StreamSerializerAdapter.java:59) Local Variable: com.hazelcast.nio.serialization.ByteArrayObjectDataInput#1 at com.hazelcast.nio.serialization.SerializationServiceImpl.toObject(SerializationServiceImpl.java:221) at com.hazelcast.spi.impl.NodeEngineImpl.toObject(NodeEngineImpl.java:156) at com.hazelcast.map.MapService.toObject(MapService.java:872) at com.hazelcast.map.proxy.MapProxyImpl.get(MapProxyImpl.java:53) at org.wso2.andes.kernel.slot.SlotManagerClusterMode.updateMessageID(SlotManagerClusterMode.java:347) Local Variable: java.util.TreeSet#1 at org.wso2.andes.thrift.SlotManagementServiceImpl.updateMessageId(SlotManagementServiceImpl.java:56) Local Variable: java.lang.String#2380 Local Variable: java.lang.String#2379 at org.wso2.andes.thrift.slot.gen.SlotManagementService$Processor$updateMessageId.getResult(SlotManagementService.java:440) Local Variable: org.wso2.andes.thrift.slot.gen.SlotManagementService$updateMessageId_result#2 at org.wso2.andes.thrift.slot.gen.SlotManagementService$Processor$updateMessageId.getResult(SlotManagementService.java:429) Local Variable: org.wso2.andes.thrift.slot.gen.SlotManagementService$updateMessageId_args#1 Local Variable: org.wso2.andes.thrift.SlotManagementServiceImpl#1 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) Local Variable: org.wso2.andes.thrift.slot.gen.SlotManagementService$Processor$updateMessageId#1 at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:176) Local Variable: org.apache.thrift.transport.TSocket#2 Local Variable: org.apache.thrift.protocol.TBinaryProtocol#2 Local Variable: org.apache.thrift.protocol.TBinaryProtocol#3 Local Variable: org.wso2.andes.thrift.slot.gen.SlotManagementService$Processor#1 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) Local Variable: org.apache.thrift.server.TThreadPoolServer$WorkerProcess#1 Local Variable: java.util.concurrent.ThreadPoolExecutor#26 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) Local Variable: java.util.concurrent.ThreadPoolExecutor$Worker#41 at java.lang.Thread.run(Thread.java:745) Have anyone faced similar issue ? What is the best method to handle this out of memory issue? Thanks, -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Hemika Kodikara
Hi Hemika, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! regards, -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] MB cluster throws 'hazelcast operation timeout' exception with long running tests
Looping in Kernel Team. On Mon, Mar 16, 2015 at 11:01 AM, Pumudu Ruhunage pum...@wso2.com wrote: Hi, I did a long running MB cluster test and got attached exceptions. Following is the test scenario i followed. 1. Start two MB nodes, nodeA(slot coordinator) and nodeB with shared oracle database. 2. Add two subscribers for queue messages (queue1 and queue2) to nodeB. 3. Start publish messages to 'queue1' with average 1000 TPS to nodeA. 4. Start publish messages to 'queue2' with average 300 TPS to nodeA. 5. After around 48 hours attached exceptions were thrown from nodeA. What will be the best approach to solve this issue. Thanks, Regards, -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Message Broker 3.0.0 Milestone 4 Released !
The WSO2 Message Broker team is pleased to announce the 4th milestone release of WSO2 Message Broker (MB) 3.0.0. WSO2 Message Broker (WSO2 MB) 3.0.0 is designed to be a fast, lightweight and user friendly open source distributed message brokering system under the Apache Software License v2.0 http://www.apache.org/licenses/LICENSE-2.0.html. It primarily allows system administrators and developers to easily configure JMS queues and topics which could be used for message routing, message stores and message processors. WSO2 MB is compliant with Advanced Message Queuing Protocol Version 0-9-1, Java Message Service Specification version 1.1 and MQTT protocol version 3.1. WSO2 MB 3.0.0 is developed on top of the revolutionary WSO2 Carbon platform http://wso2.org/projects/carbon (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via modularization. This release also contains many other new features and a range of optional components (add-ons) that can be installed to customize the behavior of the MB. Further, any existing features of the MB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In a nutshell, WSO2 MB can be fully customized and tailored to meet your exact SOA needs. You can download this distribution from [1]. Release notes for this milestone can be found at [2]. Known issues are listed at [3]. Apart from the bug fixes and improvements this mile stone adds 1) the ability to authenticate MQTT users against Carbon User stores 2) Inverse bitmaps based algorithm for fast topic matching. How You Can Contribute:Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List : dev@wso2.org | Subscribe | Mail Archive http://wso2.org/mailarchive/carbon-dev/ - User List : StackOverflow.com http://stackoverflow.com/questions/tagged/wso2 Reporting Issues WSO2 encourages you to report issues and your enhancement requests for the WSO2 MB using the public JIRA https://wso2.org/jira/browse/MB. You can also watch how they are resolved, and comment on the progress.. [1] *https://svn.wso2.org/repos/wso2/scratch/MB/3.0.0/M4/wso2mb-3.0.0-SNAPSHOT-m4.zip https://svn.wso2.org/repos/wso2/scratch/MB/3.0.0/M4/wso2mb-3.0.0-SNAPSHOT-m4.zip* [2] https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10200version=11592*https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10200version=11735 https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10200version=11735* [3] https://wso2.org/jira/browse/MB#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel https://wso2.org/jira/browse/MB#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Upgrading the disruptor version in orbit to 3.3.0
HI Krishantha, We would like to do $subject PR is at: https://github.com/wso2/orbit/pull/64 could you review and merge? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Upgrading the disruptor version in orbit to 3.3.0
do we have this uploaded to nexus? to me it looks like not. On Thu, Feb 19, 2015 at 4:28 PM, Maheshika Goonetilleke mahesh...@wso2.com wrote: Hi All Done. On Thu, Feb 19, 2015 at 3:32 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Maheshika, please release this orbit. On Thu, Feb 19, 2015 at 2:41 PM, Ramith Jayasinghe ram...@wso2.com wrote: FYI. sent to wrong person.! -- Forwarded message -- From: Ramith Jayasinghe ram...@wso2.com Date: Thu, Feb 19, 2015 at 2:19 PM Subject: Upgrading the disruptor version in orbit to 3.3.0 To: WSO2 Developers' List dev@wso2.org Cc: Krishantha Samaraweera krishan...@wso2.com HI Krishantha, We would like to do $subject PR is at: https://github.com/wso2/orbit/pull/64 could you review and merge? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* -- Thanks Best Regards, Maheshika Goonetilleke Engineering Process Coordinator *WSO2 Inc* *email : mahesh...@wso2.com mahesh...@wso2.com* *mobile : +94 773 596707 %2B94%20773%20596707* *www: :http://wso2.com http://wso2.com/*lean . enterprise . middleware -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Upgrading the disruptor version in orbit to 3.3.0
thanks! On Thu, Feb 19, 2015 at 7:37 PM, Maheshika Goonetilleke mahesh...@wso2.com wrote: Hi Ramith Please re-check as this has already been deployed. [image: Inline image 1] On Thu, Feb 19, 2015 at 6:48 PM, Ramith Jayasinghe ram...@wso2.com wrote: do we have this uploaded to nexus? to me it looks like not. On Thu, Feb 19, 2015 at 4:28 PM, Maheshika Goonetilleke mahesh...@wso2.com wrote: Hi All Done. On Thu, Feb 19, 2015 at 3:32 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Maheshika, please release this orbit. On Thu, Feb 19, 2015 at 2:41 PM, Ramith Jayasinghe ram...@wso2.com wrote: FYI. sent to wrong person.! -- Forwarded message -- From: Ramith Jayasinghe ram...@wso2.com Date: Thu, Feb 19, 2015 at 2:19 PM Subject: Upgrading the disruptor version in orbit to 3.3.0 To: WSO2 Developers' List dev@wso2.org Cc: Krishantha Samaraweera krishan...@wso2.com HI Krishantha, We would like to do $subject PR is at: https://github.com/wso2/orbit/pull/64 could you review and merge? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* -- Thanks Best Regards, Maheshika Goonetilleke Engineering Process Coordinator *WSO2 Inc* *email : mahesh...@wso2.com mahesh...@wso2.com* *mobile : +94 773 596707 %2B94%20773%20596707* *www: :http://wso2.com http://wso2.com/*lean . enterprise . middleware -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Thanks Best Regards, Maheshika Goonetilleke Engineering Process Coordinator *WSO2 Inc* *email : mahesh...@wso2.com mahesh...@wso2.com* *mobile : +94 773 596707 %2B94%20773%20596707* *www: :http://wso2.com http://wso2.com/*lean . enterprise . middleware -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Message Broker 3.0.0 Milestone 3 Released !
The WSO2 Message Broker team is pleased to announce the 3rd Milestone release of WSO2 Message Broker (MB) 3.0.0. WSO2 Message Broker (WSO2 MB) 3.0.0 is designed to be a fast, lightweight and user friendly open source distributed message brokering system under the Apache Software License v2.0 http://www.apache.org/licenses/LICENSE-2.0.html. It primarily allows system administrators and developers to easily configure JMS queues and topics which could be used for message routing, message stores and message processors. WSO2 MB is compliant with Advanced Message Queuing Protocol Version 0-9-1, Java Message Service Specification version 1.1 and MQTT protocol version 3.1. WSO2 MB 3.0.0 is developed on top of the revolutionary WSO2 Carbon platform http://wso2.org/projects/carbon (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via modularization. This release also contains many other new features and a range of optional components (add-ons) that can be installed to customize the behavior of the MB. Further, any existing features of the MB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In a nutshell, WSO2 MB can be fully customized and tailored to meet your exact SOA needs. You can download this distribution from [1]. Release notes for this milestone can be found at [2]. Known issues are listed at [3]. Apart from the lots of bug fixes and improvements we have added the ability to subscribe to a durable topic using same client ID. How You Can Contribute:Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List : dev@wso2.org | Subscribe | Mail Archive http://wso2.org/mailarchive/carbon-dev/ - User List : StackOverflow.com http://stackoverflow.com/questions/tagged/wso2 Reporting Issues WSO2 encourages you to report issues and your enhancement requests for the WSO2 MB using the public JIRA https://wso2.org/jira/browse/MB. You can also watch how they are resolved, and comment on the progress.. [1] https://svn.wso2.org/repos/wso2/scratch/MB/3.0.0/M3/wso2mb-3.0.0-SNAPSHOT-m3.zip [2] https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10200version=11632 https://wso2.org/jira/secure/ReleaseNote.jspa?projectId=10200version=11592 [3] https://wso2.org/jira/browse/MB#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel -- ~ The WSO2 MB Team ~ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB]Multi tenant topic and queue creation and subscription
how about this : https://docs.wso2.com/display/MB220/Multi-Tenancy+Support On Thu, Feb 12, 2015 at 11:11 AM, Mahesh Chinthaka mahe...@wso2.com wrote: And this too... :) https://docs.wso2.com/display/MB220/JMS+Client+Samples On Thu, Feb 12, 2015 at 11:09 AM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Megala, You may find these samples useful. https://docs.wso2.com/display/MB220/Creating+a+Durable+Topic+Subscription https://docs.wso2.com/display/MB220/Receiving+Messages+with+JMS+Message+Listener https://docs.wso2.com/display/MB220/Sending+and+Receiving+Messages+Using+Topics On Thu, Feb 12, 2015 at 10:55 AM, Megala Uthayakumar meg...@wso2.com wrote: Hi All, Is there are any sample codes in the existing documentation regarding the multi tenant topic and queue creation and subscription? I can not find the codes in the existing documentation[1]. Can someone help me on this please? [1]https://docs.wso2.com/display/MB220/WSO2+Message+Broker+Documentation Thanks. Regards Megala Uthayakumar *Software Engineering Intern *| *WSO2 Lanka* Mobile : +94 779 967 122 Tel : +94 112 733 667 E-mail : meg...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB]Multi tenant topic and queue creation and subscription
sounds good. Could you send a patch ? On Thu, Feb 12, 2015 at 12:02 PM, Megala Uthayakumar meg...@wso2.com wrote: Hi Mahesh and Ramith, Thanks for the references. I will go through those. @Ramith - If we can have a sample specific to multi tenancy support, it will be helpful to new users. Just an idea. On Thu, Feb 12, 2015 at 11:42 AM, Ramith Jayasinghe ram...@wso2.com wrote: how about this : https://docs.wso2.com/display/MB220/Multi-Tenancy+Support On Thu, Feb 12, 2015 at 11:11 AM, Mahesh Chinthaka mahe...@wso2.com wrote: And this too... :) https://docs.wso2.com/display/MB220/JMS+Client+Samples On Thu, Feb 12, 2015 at 11:09 AM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Megala, You may find these samples useful. https://docs.wso2.com/display/MB220/Creating+a+Durable+Topic+Subscription https://docs.wso2.com/display/MB220/Receiving+Messages+with+JMS+Message+Listener https://docs.wso2.com/display/MB220/Sending+and+Receiving+Messages+Using+Topics On Thu, Feb 12, 2015 at 10:55 AM, Megala Uthayakumar meg...@wso2.com wrote: Hi All, Is there are any sample codes in the existing documentation regarding the multi tenant topic and queue creation and subscription? I can not find the codes in the existing documentation[1]. Can someone help me on this please? [1] https://docs.wso2.com/display/MB220/WSO2+Message+Broker+Documentation Thanks. Regards Megala Uthayakumar *Software Engineering Intern *| *WSO2 Lanka* Mobile : +94 779 967 122 Tel : +94 112 733 667 E-mail : meg...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Megala Uthayakumar *Software Engineering Intern *| *WSO2 Lanka* Mobile : +94 779 967 122 Tel : +94 112 733 667 E-mail : meg...@wso2.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][MB] Truncate Tables Script MSSQL
shall we commit this to a scratch/personal area? On Tue, Feb 10, 2015 at 2:15 PM, Pamod Sylvester pa...@wso2.com wrote: Good stuff. This will be useful when carrying out tests, so that we will not need to drop the DB entirely. On Tue, Feb 10, 2015 at 2:10 PM, Akalanka Pagoda Arachchi darsha...@wso2.com wrote: Hi all, Attached truncate tables script to be used in testing/dev when MB is configured to be used with SQL Server. Thanks, Akalanka. -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791 078-4721791* -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Restriction to publish XML messages for topics in UI
I think this is because we are relying on old eventing UI.
For now I suppose we can/(rather have to) live with this.
Lets create a improvement Jira and move on.
On Sun, Feb 8, 2015 at 10:51 PM, Hemika Kodikara hem...@wso2.com wrote:
Any advice on this would be helpful.
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Mon, Jan 19, 2015 at 4:32 PM, Hemika Kodikara hem...@wso2.com wrote:
Hi All,
Currently in MB, a topic should be able to send any message in the format
as a normal text, XML, etc.
But in the UI, the topic details page(topic_manage.jsp) shows a
publishing message section which allows only to send XML messages.
Following code does the publishing of the message.
=
BrokerClient brokerClient = UIUtils.getBrokerClient(config, session,
request);
String topic = request.getParameter(topic);
String textMsg = request.getParameter(xmlMessage);
session.setAttribute(errorTopic, topic);
session.setAttribute(xmlMessage, textMsg);
OMElement message;
String messageToBePrinted = null;
StAXOMBuilder builder = null;
try {
builder = new StAXOMBuilder(new ByteArrayInputStream(textMsg.getBytes()));
message = builder.getDocumentElement();
if (message != null) {
brokerClient.publish(topic, message);
} else {
messageToBePrinted = Error: Failed to get document element from message
+ textMsg;
}
} catch (Exception e) {
messageToBePrinted = Error: while publishing the message +
e.getMessage();
}
if (messageToBePrinted == null) {
messageToBePrinted = Successfully published the message to the topic :
+ topic;
}
=
Is there a reason for this restriction ? i.e only allow to send XML
messages through UI ?
Refer [1][2][3] for more code information.
[1] -
https://github.com/wso2-dev/carbon-utils/blob/master/components/event/org.wso2.carbon.event.ui/src/main/resources/web/topics/topic_manage.jsp
[2] -
https://github.com/wso2-dev/carbon-utils/blob/master/components/event/org.wso2.carbon.event.ui/src/main/resources/web/topics/js/treecontrol.js
[3] -
https://github.com/wso2-dev/carbon-utils/blob/master/components/event/org.wso2.carbon.event.ui/src/main/resources/web/topics/try_it_out_invoke_ajaxprocessor.jsp
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] MB test cases improvements - check message counts
awsome idea. lets do that. On Tue, Jan 27, 2015 at 4:36 PM, Hasitha Hiranya hasit...@wso2.com wrote: For example following scenario should be testable. At least check message counts after sending to DLC/deleting/purging operations 1) Send couple of messages to MBQ1 queue. Make these messages end up in DLC 2) Disable the JMS consumer and send messages so that there will be message in MBQ1 queue. 3) Purge the MBQ1 ( so that messages in DLC and MBQ1 will be cleared) 4) Send messages to MQ1 again ... 5) Enable JMS Consumer (this will put messages to dlc again) 6) Browse the Queue you will see there are message in DLC and the queue and verify queue count=0 dlc count = x On Tue, Jan 27, 2015 at 9:01 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi, We need to be careful with message count display in UI in MB 3.0.0. For most of users this is the first impression about the product. If message counts are wrong and unpredictable, even for us developers, it is hard to isolate issues. Thus in the test suite via admin services we should be able to query the message count after doing some message publish/ consume. We need to add some tests (or do this at the end of each existing test standalone and cluster) checking message count and verify. Thanks -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Akalanka Darshana Pagoda Arachchi
Hi Akalanka, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! regards -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Remove or revamp 'Node List' page under 'Cluster Management' in MB 3.0.0
I also think we can live with proposed set of information displayed. On Tue, Jan 6, 2015 at 10:22 AM, Hemika Kodikara hem...@wso2.com wrote: Hi, I am ok with that. Shall I come up with a mock diagram for the table ? . If we have time before the release, then we can include more information on the nodes. WDYT ? Thanks, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Tue, Jan 6, 2015 at 8:57 AM, Hasitha Hiranya hasit...@wso2.com wrote: Hemika, I vote for now, let's have a plain table displaying nodes in the cluster with above properties, with coordinator highlighted. At the moment we do not have a lot of information to display via a drill down. WDYT? Thanks On Tue, Jan 6, 2015 at 7:13 AM, Pamod Sylvester pa...@wso2.com wrote: Hemika, you can have a separate section to display the cluster information which will contain info regarding all the nodes in the cluster (info as in ip, node id etc). There you could highlight the node which is the coordinator. Further you could have sort of a drill down option where you could click on the node an get more information regarding it, there you can display the slot information. The above is one approach that I could think of. There might be more ways of dealing with this. Thanks, On Tuesday, January 6, 2015, Hemika Kodikara hem...@wso2.com wrote: I was a bit stuck on the terminology there. But was able to figure it out with HasithH's help. :) So far from what I understood, following are the details that can be shown on this page and some of my suggestions. 1. Displaying the Node ID. 2. The IP and Port. 3. Showing the publishers and subscribers would be good as well. But the subscribers are already shown in another page. Instead, will it be useful if we show the number of publishers and subscribers ? 4. Displaying the coordinator node. What can be showing using the coordinator node ? Thanks, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Tue, Dec 23, 2014 at 10:03 AM, Ramith Jayasinghe ram...@wso2.com wrote: what are the stats that could be useful to display in coordinator node? (that is if we are going to specifically display coordinator specific stats) Information related to slot distribution etc... ( which will help us to see how the deployment performs?) On Tue, Dec 23, 2014 at 8:09 AM, Sajini De Silva saj...@wso2.com wrote: Hi, Coordinator node will be critical since slot coordination is happening via the coordinator node. Therefore +1 for Pamod's idea. Thank you, Sajini. On Tue, Dec 23, 2014 at 1:13 AM, Pamod Sylvester pa...@wso2.com wrote: Hi Hemika, Also will it make sense to display the coordinator node ? IMO this will be useful. Thanks, Pamod On Mon, Dec 22, 2014 at 10:48 PM, Hemika Kodikara hem...@wso2.com wrote: Thanks for the correction and feedback Asitha. Looping in Ramith and HasithaH. Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Mon, Dec 22, 2014 at 10:28 PM, Asitha Nanayakkara asi...@wso2.com wrote: On Mon, Dec 22, 2014 at 5:51 PM, Hemika Kodikara hem...@wso2.com wrote: Hi All, The page mentioned in $subject provides several information related to nodes in a clustered deployment in MB 2.2.0 (See attachment). The page displays the cassandra details, zookeeper details and the node number. In MB 3.0.0, several change are done so that, 1. Zookeeper is not being used. 2. No such thing as Node number as node queues and global queues are not there anymore. In 3.0.0 there is a node id for each node. And clustered/standalone mode information need to be displayed 3. Supports other databases including other than cassandra. +1 Share your idea on $subject. Something like number of subscribers and publishers handled by each node. This will give an idea of load distribution in a cluster. MQTT and AMQP ports used by the nodes Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 -- Sajini De SIlva Software Engineer; WSO2 Inc.; http://wso2.com , Email: saj...@wso2.com Blog: http://sajinid.blogspot.com/ Git hub profile: https://github.com/sajinidesilva Phone: +94 712797729
[Dev] WSO2 Committers += Hasitha Amal De Silva
Hi Hasitha, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB] Remove or revamp 'Node List' page under 'Cluster Management' in MB 3.0.0
what are the stats that could be useful to display in coordinator node? (that is if we are going to specifically display coordinator specific stats) Information related to slot distribution etc... ( which will help us to see how the deployment performs?) On Tue, Dec 23, 2014 at 8:09 AM, Sajini De Silva saj...@wso2.com wrote: Hi, Coordinator node will be critical since slot coordination is happening via the coordinator node. Therefore +1 for Pamod's idea. Thank you, Sajini. On Tue, Dec 23, 2014 at 1:13 AM, Pamod Sylvester pa...@wso2.com wrote: Hi Hemika, Also will it make sense to display the coordinator node ? IMO this will be useful. Thanks, Pamod On Mon, Dec 22, 2014 at 10:48 PM, Hemika Kodikara hem...@wso2.com wrote: Thanks for the correction and feedback Asitha. Looping in Ramith and HasithaH. Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Mon, Dec 22, 2014 at 10:28 PM, Asitha Nanayakkara asi...@wso2.com wrote: On Mon, Dec 22, 2014 at 5:51 PM, Hemika Kodikara hem...@wso2.com wrote: Hi All, The page mentioned in $subject provides several information related to nodes in a clustered deployment in MB 2.2.0 (See attachment). The page displays the cassandra details, zookeeper details and the node number. In MB 3.0.0, several change are done so that, 1. Zookeeper is not being used. 2. No such thing as Node number as node queues and global queues are not there anymore. In 3.0.0 there is a node id for each node. And clustered/standalone mode information need to be displayed 3. Supports other databases including other than cassandra. +1 Share your idea on $subject. Something like number of subscribers and publishers handled by each node. This will give an idea of load distribution in a cluster. MQTT and AMQP ports used by the nodes Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 -- Sajini De SIlva Software Engineer; WSO2 Inc.; http://wso2.com , Email: saj...@wso2.com Blog: http://sajinid.blogspot.com/ Git hub profile: https://github.com/sajinidesilva Phone: +94 712797729 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Upgrading CQL to the latest release version 2.1.3
Hi Sameera, Could we have this reviewed and merged? regards Ramith On Thu, Dec 18, 2014 at 4:02 PM, Harsha Kumara hars...@wso2.com wrote: Hi Ramith/Prabath, Asitha and myself tested the CQL upgrade and found that there a is a dependency issue with hector as it required cassandra thrift dependency. Previously, older version of CQL needed Cassandra as a dependency which includes thrift. With the latest upgrade, we CQL does not depend on Cassandra and can be used as it is because of it's already a OSGi bundle. Since cassandra thrift needed for hector, I have created orbit bundle for cassandra-thrift version 1.2.13.wso2v4. Previous versions of cassandra thrift has some issues with their dependencies. Pull request in [1] needs to merge and deploy before upgrading the CQL version in data reader component. [1] - https://github.com/wso2/orbit/pull/46/files Thanks, Harsha On Wed, Dec 10, 2014 at 4:08 PM, Ramith Jayasinghe ram...@wso2.com wrote: we need to test a new driver on cassandra ring (with a MB load test). On Wed, Dec 10, 2014 at 3:55 PM, Harsha Kumara hars...@wso2.com wrote: Hi All, Since there are number of improvements made for the latest CQL driver, we are going to upgrade CQL driver to the latest version which also need for MB as well. Current version is 1.0.8.wso2v1 which we added as orbit bundle due to dependency conflicts in OSGi environment. With the latest release, they have removed cassandra and jackson dependencies from CQL driver. We most probably can update the CQL driver to the 2.1.3 without a orbit bundle. Since there are some API changes, we will needs to fix them. Please find [1] and [2] as upgrade instructions from datastax. We are now testing the cql upgrade with latest version from https://github.com/wso2-dev/carbon-storage-management/tree/cql_upgrade branch, @Asitha,Madhawa can you update the thread whether data reader feature with the latest CQL driver works as expected in MB? [1] -hhttps:// github.com/datastax/java-driver/blob/2.0/driver-core/Upgrade_guide_to_2.0.rst [2] - https://github.com/datastax/java-driver/blob/2.1/driver-core/Upgrade_guide_to_2.1.rst [3] -https://github.com/datastax/java-driver Thanks, Harsha -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Preventing Topic Subscriptions getting unwanted messages
Good stuff! lets create a L1 (for docs team) stating that we need to have time synced in servers (in clustering guide). Otherwise we will miss it! On Mon, Dec 15, 2014 at 11:46 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi, I did following change to topic subscriptions. 1. say sub 1 subscribed to topic x. 2. say sub 2 subscribed to topic x. 3. say 10,000 msgs published to topic x. Now when sub 1 is closed and resubscribe, it should get no messages. This is now done comparing time stamps of subscription and message arrival time. This brings the need that all MB nodes MUST BE TIME SYNCED. Standalone Test case also added. Note that when all topic subscribers vanished from node, underlying storage queue is purged. A test case is added for this as well. Also added abt 10 durble topic test cases. Verified that all these pass in current MB 3.0.0 SNAPSAHOT. Thanks -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [MB][MQTT] By passing the message store for QoS 0 flows when running in stand alone mode
This needs to be implemented for topic matching as well. On Tue, Dec 16, 2014 at 9:58 AM, Pamod Sylvester pa...@wso2.com wrote: Sure, let's discuss and see how we could incorporate this algorithm, This could also be added into the Andes Kernal as well. Thanks, Pamod On Tue, Dec 16, 2014 at 7:54 AM, Asitha Nanayakkara asi...@wso2.com wrote: Hi Pamod, Inverted bitmap technique[1] looks good for the purpose. Algorithm is O(n) where n is number of sections in the destination, not subscribers. Only concern is memory consumption and updating the maps when new subscribers come while messages are flowing through the system at higher rates (This will introduce some pauses to delivery). Since adding and removing subscriptions doesn't happen frequently we can live with that I think. Need to look at the memory consumption to make sure this is feasible. [1] http://zeromq.org/whitepapers:message-matching On Mon, Dec 15, 2014 at 5:52 PM, Pamod Sylvester pa...@wso2.com wrote: Hi All, Since QoS 0 in MQTT is a performance oriented delivery mode, an in-memory based message store was implemented to bypass the message database when running MB in stand alone mode, however when running in cluster in-memory store will not be applicable, since in order to exchange messages across the cluster, it requires a mechanism to communicate between brokers (Which will be introduced in future MB versions) In Stand-Alone mode the current message flow would be similar to the following, Publisher --- Message --- Deliver from In-Memory Store --- Deliver from Andes Kernal Store --- Message --- Subscription In the above flow, the subscriptions with QoS 0 would receive the messages through the in-memory store and the also currently the published message would be sent to the Andes kernal as well. Since for the same topic there could be subscriptions which are QoS 0. Making a call to Andes Kernal strore would not make much sense if there're no subscriptions for a particular topic which is QoS 0, also it will cause additional operation overhead. Therefore, we're in the process of implementing a solution which would be able to identify whether there are subscriptions QoS 0 for a given topic to identify the necessity to perform a call to the store. If we maintain the state of topics which has subscriptions QoS 0, for each message published it would require to iterate through all the subscriptions O(n), since there will be cases where the published topic will not 1:1 map with the subscribed topic, (i.e hierarchical topics with wildcards). In order to minimize the iteration cycles one option would be to partition subscriptions based on its attributes such as hierarchy, inclusive of wild card characters etc so that we could omit odds and iterate only through the possibilities. WDYT ? Please do advice on most optimized ways of filtering out matching subscriptions. Thanks, Pamod -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Upgrading CQL to the latest release version 2.1.3
we need to test a new driver on cassandra ring (with a MB load test). On Wed, Dec 10, 2014 at 3:55 PM, Harsha Kumara hars...@wso2.com wrote: Hi All, Since there are number of improvements made for the latest CQL driver, we are going to upgrade CQL driver to the latest version which also need for MB as well. Current version is 1.0.8.wso2v1 which we added as orbit bundle due to dependency conflicts in OSGi environment. With the latest release, they have removed cassandra and jackson dependencies from CQL driver. We most probably can update the CQL driver to the 2.1.3 without a orbit bundle. Since there are some API changes, we will needs to fix them. Please find [1] and [2] as upgrade instructions from datastax. We are now testing the cql upgrade with latest version from https://github.com/wso2-dev/carbon-storage-management/tree/cql_upgrade branch, @Asitha,Madhawa can you update the thread whether data reader feature with the latest CQL driver works as expected in MB? [1] -hhttps:// github.com/datastax/java-driver/blob/2.0/driver-core/Upgrade_guide_to_2.0.rst [2] - https://github.com/datastax/java-driver/blob/2.1/driver-core/Upgrade_guide_to_2.1.rst [3] -https://github.com/datastax/java-driver Thanks, Harsha -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Custom Serializer property for hazelcast in Carbon
Just to give some context: we need to keep several maps in hazelcast ( where values are not primitives) for MB's new slot based message delivery scheme. By registering custom serializers we can optimize the information that’s been transmitted across the cluster ( reducing the overhead for hazelcast etc). On Wed, Dec 10, 2014 at 11:29 AM, Sajini De Silva saj...@wso2.com wrote: Hi, Yesterday I tested the patch gave by Azeez to enable custom serializing in hazelcast and its working. Are we going to ship this change with Carbon 4.3.0 release? Thank you, Sajini -- Sajini De SIlva Software Engineer; WSO2 Inc.; http://wso2.com , Email: saj...@wso2.com Blog: http://sajinid.blogspot.com/ Git hub profile: https://github.com/sajinidesilva Phone: +94 712797729 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Custom serialization in hazelcast is not working
could we have this in next kernel release? will make our life easy (with
the MB time line) :)
On Tue, Dec 9, 2014 at 10:07 AM, Sajini De Silva saj...@wso2.com wrote:
Hi Azeez,
I tested the above scenario and when the above code segment is added to
HazelcastClusteringAgent, the sysout are printed.
Thank you,
Sajini
On Mon, Dec 8, 2014 at 3:39 PM, Afkham Azeez az...@wso2.com wrote:
Change HazelcastClusteringAgent#init method to include the following and
see whether the sysouts are getting printed.
primaryHazelcastConfig.addMapConfig(mapConfig);
SerializerConfig sc = new SerializerConfig();
sc.setImplementation(new StreamSerializerTreeSetLong() {
@Override
public void write(ObjectDataOutput objectDataOutput,
TreeSetLong longs) throws IOException {
System.out.println(TreeSet StreamSerializer#write
called);
}
@Override
public TreeSetLong read(ObjectDataInput objectDataInput)
throws IOException {
System.out.println(TreeSet StreamSerializer#read
called);
return null;
}
@Override
public int getTypeId() {
return 0;
}
@Override
public void destroy() {
System.out.println(TreeSet StreamSerializer#destroy
called);
}
}).setTypeClass(new TreeSetLong().getClass());
primaryHazelcastConfig.getSerializationConfig().addSerializerConfig(sc);
On Mon, Dec 8, 2014 at 3:00 PM, Sajini De Silva saj...@wso2.com wrote:
Still its working.
On Mon, Dec 8, 2014 at 2:54 PM, Afkham Azeez az...@wso2.com wrote:
On Mon, Dec 8, 2014 at 2:50 PM, Sajini De Silva saj...@wso2.com
wrote:
SerializerConfig sc = new SerializerConfig()
.setImplementation(new TreeMapSerializer())
.setTypeClass(new TreeSetLong().getClass());
Config config = new Config();
config.getSerializationConfig().addSerializerConfig(sc);
HazelcastInstance primaryHazelcastInstance=
Hazelcast.newHazelcastInstance(config);
IMapString, TreeSetLong testMap =
primaryHazelcastInstance.getMap(testMap);
TreeSetLong slotIdSet = new TreeSetLong();
slotIdSet.add(Long.valueOf(1212121));
slotIdSet.add(Long.valueOf(3413131));
Change the code as follows see whether it still works. Most probably
it won't work:
SerializerConfig sc = new SerializerConfig()
.setImplementation(new TreeMapSerializer())
.setTypeClass(new TreeSetLong().getClass());
Config config = new Config();
HazelcastInstance primaryHazelcastInstance= Hazelcast.
newHazelcastInstance(config);
IMapString, TreeSetLong testMap = primaryHazelcastInstance.
getMap(testMap);
config.getSerializationConfig().addSerializerConfig(sc);
TreeSetLong slotIdSet = new TreeSetLong();
slotIdSet.add(Long.valueOf(1212121));
slotIdSet.add(Long.valueOf(3413131));
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 %2B94%2077%203320919blog: *
*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
http://lk.linkedin.com/in/afkhamazeez*
*Lean . Enterprise . Middleware*
--
Sajini De SIlva
Software Engineer; WSO2 Inc.; http://wso2.com ,
Email: saj...@wso2.com
Blog: http://sajinid.blogspot.com/
Git hub profile: https://github.com/sajinidesilva
Phone: +94 712797729
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/*
*email: **az...@wso2.com* az...@wso2.com
* cell: +94 77 3320919 %2B94%2077%203320919blog: *
*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
http://lk.linkedin.com/in/afkhamazeez*
*Lean . Enterprise . Middleware*
--
Sajini De SIlva
Software Engineer; WSO2 Inc.; http://wso2.com ,
Email: saj...@wso2.com
Blog: http://sajinid.blogspot.com/
Git hub profile: https://github.com/sajinidesilva
Phone: +94 712797729
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker][AS-6.0.0] Build failed at p2-profile-gen
HI, We are still seeing below error while building MB on clean repo. Could we have this solved please? Installing org.wso2.carbon.cassandra.datareader.feature.group 4.3.0.SNAPSHOT. Cannot satisfy dependency: From: WSO2 Tenant Common Composite Feature 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.common.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.tenant.common.server.feature.group [4.3.0.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Tenant Common Core Feature 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.common.server.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.tenant.keystore.mgt [4.3.0.SNAPSHOT] Cannot satisfy dependency: From: org.wso2.carbon.tenant.keystore.mgt 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.keystore.mgt 4.3.0.SNAPSHOT) To: package org.wso2.carbon.security.keystore 0.0.0 On Thu, Nov 27, 2014 at 1:01 PM, Pulasthi Mahawithana pulast...@wso2.com wrote: Hi Kishanthan, The repo was updated at wso2-dev[1] yesterday. However, the update also had a dependency on the new amber[2] version which was not available in nexus yesterday. We had to wait till amber is deployed to the nexus to create the PR to the wso2 repo[3]. The PR has been merged now and the code is updated. [1] https://github.com/wso2-dev/carbon-identity [2] https://github.com/wso2/wso2-amber [3] https://github.com/wso2/carbon-identity On Thu, Nov 27, 2014 at 12:32 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi IS Team, Can we update carbon-identity with axis2 released versions? We are trying to get some packs for testing. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: Identity Core Feature 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core.feature.group 4.3.0.SNAPSHOT) Missing requirement: WSO2 Carbon - Identity Core 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core 4.3.0.SNAPSHOT) requires 'package org.apache.axis2.context [1.6.1.wso2v11-SNAPSHOT,1.7.0)' but it could not be found Cannot satisfy dependency: From: Identity Core Feature 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.identity.core.server.feature.group [4.3.0.SNAPSHOT] Cannot satisfy dependency: From: Identity Core Server Feature 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core.server.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.identity.core [4.3.0.SNAPSHOT] Thanks, Kishanthan. -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pulasthi Mahawithana* Software Engineer WSO2 Inc., http://wso2.com/ Mobile: +94-71-5179022 Blog: http://blog.pulasthi.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker][AS-6.0.0] Build failed at p2-profile-gen
correct error: Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: WSO2 Tenant Common Composite Feature 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.common.feature.group 4.3.0.SNAPSHOT) Missing requirement: org.wso2.carbon.security.mgt 4.3.0.SNAPSHOT (org.wso2.carbon.security.mgt 4.3.0.SNAPSHOT) requires 'package org.apache.axis2 [1.6.1.wso2v11-SNAPSHOT,1.7.0)' but it could not be found Cannot satisfy dependency: From: WSO2 Tenant Common Composite Feature 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.common.feature.group 4.3.0.SNAPSHOT) Cannot satisfy dependency: From: org.wso2.carbon.tenant.keystore.mgt 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.keystore.mgt 4.3.0.SNAPSHOT) To: package org.wso2.carbon.security.keystore 0.0.0 On Thu, Nov 27, 2014 at 1:41 PM, Ramith Jayasinghe ram...@wso2.com wrote: HI, We are still seeing below error while building MB on clean repo. Could we have this solved please? Installing org.wso2.carbon.cassandra.datareader.feature.group 4.3.0.SNAPSHOT. Cannot satisfy dependency: From: WSO2 Tenant Common Composite Feature 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.common.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.tenant.common.server.feature.group [4.3.0.SNAPSHOT] Cannot satisfy dependency: From: WSO2 Tenant Common Core Feature 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.common.server.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.tenant.keystore.mgt [4.3.0.SNAPSHOT] Cannot satisfy dependency: From: org.wso2.carbon.tenant.keystore.mgt 4.3.0.SNAPSHOT (org.wso2.carbon.tenant.keystore.mgt 4.3.0.SNAPSHOT) To: package org.wso2.carbon.security.keystore 0.0.0 On Thu, Nov 27, 2014 at 1:01 PM, Pulasthi Mahawithana pulast...@wso2.com wrote: Hi Kishanthan, The repo was updated at wso2-dev[1] yesterday. However, the update also had a dependency on the new amber[2] version which was not available in nexus yesterday. We had to wait till amber is deployed to the nexus to create the PR to the wso2 repo[3]. The PR has been merged now and the code is updated. [1] https://github.com/wso2-dev/carbon-identity [2] https://github.com/wso2/wso2-amber [3] https://github.com/wso2/carbon-identity On Thu, Nov 27, 2014 at 12:32 PM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi IS Team, Can we update carbon-identity with axis2 released versions? We are trying to get some packs for testing. Installation failed. Cannot complete the install because one or more required items could not be found. Software being installed: Identity Core Feature 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core.feature.group 4.3.0.SNAPSHOT) Missing requirement: WSO2 Carbon - Identity Core 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core 4.3.0.SNAPSHOT) requires 'package org.apache.axis2.context [1.6.1.wso2v11-SNAPSHOT,1.7.0)' but it could not be found Cannot satisfy dependency: From: Identity Core Feature 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.identity.core.server.feature.group [4.3.0.SNAPSHOT] Cannot satisfy dependency: From: Identity Core Server Feature 4.3.0.SNAPSHOT (org.wso2.carbon.identity.core.server.feature.group 4.3.0.SNAPSHOT) To: org.wso2.carbon.identity.core [4.3.0.SNAPSHOT] Thanks, Kishanthan. -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pulasthi Mahawithana* Software Engineer WSO2 Inc., http://wso2.com/ Mobile: +94-71-5179022 Blog: http://blog.pulasthi.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Asitha Nanayakkara
Hi Asitha, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! thanks and best regards Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Sajini De Silva
Hi Sajini, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! thanks and best regards Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 MB - To Be Dones I tracked so far
On Sat, Nov 15, 2014 at 1:40 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi Team, Following are tasks TBD for M2 and M3 releases of MB. Thought of flushing my mind with the tasks that came up with last code review and some last for some time. 1. Add a warning if parts cache is growing. (Done) 2. Make message status block capital (Done) 3. Make message status commented (TBD) 4. Remove msgId2MsgData auto removal of IDs. And make it a concurrentHashMap. (Done) 5. Move Sent and Sent all status setting to correct places (). 6. Make send() of subscription impl logic free. If an exception came from there, catch it and do the work within QDW class. Need to define proper exceptions on why sending to subscriber failed (DLC sending if delivery rules failed, if exception came when sending try another subscriber if available, if not move them over in store with a new messageID, but keeping the old id somehow) (This is a task. Need to assign somebody). 7. When all nodes in the cluster is gone make the index again (Done by AsankaAb) 8. We decided to keep Acked by all and sent to all status, did not we? No need to write what Ramith suggested now. yes. 9. Add a delay when trying to delete slot to get over with Edge Case brought out by Indika (Is it solved now? Problem was elsewhere?) after the last perf tests we did, problem doesn't occur on H2, only with Cassandra ( CQL and Hector both). This is a real and Massive L1 10. Need to run all topic test cases and make them pass. 11. Need to introduce new ack handle mechanism (QOS 0,1,2) and AMQP ack means one of those. AMQP transactions, client acks also come into play here. We need to be careful. (This is a task. Should be assigned to somebody). 12. We still did not review purge and queue delete. Should be done soon. Topic deletion should be integrated with it. HasithaA can you schedule a review? +1 13. Hector code is committed now. We can choose hector or cql from config level. Are we maintaining both now? WDYT? My Opinion is we can keep both (atleast at this stage) 14. Need to fix packaging someday. I suggest one of us do this and commit (big bang). 15. Topic cluster wide tests needs to be written. There is a considerable number of scenarios. Shall we come up with scenarios (in a doc may be). the distribute. 16. Topic ack and requeing should be verified with the spec. Should we requeue topic messages if rejected by client, or if delivery failed? How this affect to MQTT impl? +1 lets check with the spec, and then chat 17. MQTT cluster tests needs to be written. Again lets see what are the scenarios and decide on a scope 18. Puppetizing MB deployment? Did we make any progress? We haven't done anything here. I checked with our cloud team there some puppet template written for 2.2.0 also. However, we are waiting on the initiative from automation team. 19. Remove zookeeper, node queue, qlobal queue, queueAddress, topic delivery worker concepts completely from the code. 20. We Must test and fix message counting. With concurrent publishers and subscribers we still have message counting probs. Lets open L2s for these to keep track. 21. Apply config revamp. Hasitha Amal can comment on this Suppose we can go to M2 when these are done. For M3 1. Fix all the UIs. This will take a considerable effort. 2. Merge remaining fixes from 2.2.0. And we need to keep on testing end to end fix issues ( M3 should have been all about bring stability, BUT given that there could be some other features/requirements we might have to deliver with v 3.0.0 - something we will decide next week) Thanks -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Asanka Abeyweera
Hi Asanka, Congratulations! It is with great pleasure that we welcome you as a WSO2 committer. Keep up the good work! thanks and best regards, -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Message Broker 3.0.0 Milestone 1 Released !
Hi All, We missed the list features completed in WSO2 MB v 3.0.0 milestone 1. Therefore, I'm listing there again: 1) RDBMS based Message store - Previous version of MB (v 2.2.0) used Cassandra as the message store. But with this milestone users can use a RDBMS as a message store ( e.g. MYSQL, H2, MSSQL) 2) HazelCast Based clustering - Previous versions used ZooKeeper for group communication. But we have removed that dependency with use of HazelCast. regards Ramith ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] It seems like org.wso2.carbon.cassandra.datareader.feature:zip not getting build properly
It seems like org.wso2.carbon:org.wso2.carbon.cassandra.datareader.feature:zip:4.3.0-SNAPSHOT is not getting build/deployed properly into snapshot repo. there. We include that feature in product-mb hence it fails. [1] is the lastest build triggered for carbon-storage-management. Shall we check? [1] https://wso2.org/jenkins/job/carbon-storage-management/168/consoleFull -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Concern when purging during active subscriptions - MB 3.0.0
I'm thinking out aloud here: What we when a queue is deleted we fire a event across the cluster and let every one know the queue is about to get deleted. Further processing everything related to queue should end there. what do you guys think? regards Ramith On Thu, Oct 23, 2014 at 10:34 PM, Hasitha Amal De Silva hasit...@wso2.com wrote: Hi all, Given our message processing model, we do not enqueue message content in memory, and only keep message metadata. So, at the final point of a message delivery, we retrieve the message content accordingly and send. However, if a user purges a queue while subscribers are receiving from it, all message content of that queue is deleted from the database, even though some messages might be at the final delivery stage. So when the message content of such a message is looked up, it will throw an NPE / NoSuchElementException. We cannot infer if the exception is due to a purge scenario or something else, because MessageContent can also be lost due to other reasons (e.g. : a message being acknowledged while it's second delivery attempt is on the way) I could think of following ways to handle this : 1. Catch the exception and add a general trace log explaining all possible reasons - clear the message from in memory collections since we can safely say that its already been acked / purged. 2. Figure out and skip deleting the (message content + metadata) of enqueued / redelivered messages in-memory, and assume they will be deleted later from normal delivery flow. This means that all the in-memory, undelivered messages will still be delivered even after the queue is purged. (User can interpret this as an issue) Better suggestions ? The ideal solution would be to exactly remove all undelivered messages (in-store and in-memory) at the moment of purge. But this is difficult since the in-memory message buffer maybe delegated very fast into delivery jobs. As at now, I feel that option 1 would be the most feasible solution. WDYT ? -- Cheers, Hasitha Amal De Silva Software Engineer Mobile : 0772037426 Blog: http://devnutshell.tumblr.com/ WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. ) -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] It seems like org.wso2.carbon.cassandra.datareader.feature:zip not getting build properly
Thanks Harsha! On Fri, Oct 24, 2014 at 11:13 AM, Prabath Abeysekera praba...@wso2.com wrote: Great. Thanks Harsha! On Thu, Oct 23, 2014 at 9:19 PM, Harsha Kumara hars...@wso2.com wrote: Hi Ramith, I think it was due to not merging the latest changes from the wso2-dev repo. I just check, there was another build triggered with changes. Things should be Ok now. [1] - http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/carbon/org.wso2.carbon.cassandra.datareader.feature/4.3.0-SNAPSHOT/ Thanks, Harsha On Thu, Oct 23, 2014 at 7:43 PM, Ramith Jayasinghe ram...@wso2.com wrote: It seems like org.wso2.carbon:org.wso2.carbon.cassandra.datareader.feature:zip:4.3.0-SNAPSHOT is not getting build/deployed properly into snapshot repo. there. We include that feature in product-mb hence it fails. [1] is the lastest build triggered for carbon-storage-management. Shall we check? [1] https://wso2.org/jenkins/job/carbon-storage-management/168/consoleFull -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [WSO2MB] Cannot start User Manager Core bundle error on server startup
is removed from providers
this doesn't happen. Due to this we can't connect an external
Cassandra
data source for MB. This is a blocker for WSO2 MB 3.0.0 M1 release.
(This
worked fine earlier)
Any idea why this is happening?
[1]
ERROR {org.wso2.carbon.user.core.internal.Activator} - Cannot
start User Manager Core bundle
java.lang.RuntimeException: Error in looking up data source:
Name [jdbc/WSO2CarbonDB] is not bound in this Context. Unable to
find
[jdbc].
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:86)
at
org.wso2.carbon.user.core.util.DatabaseUtil.createRealmDataSource(DatabaseUtil.java:172)
at
org.wso2.carbon.user.core.util.DatabaseUtil.getRealmDataSource(DatabaseUtil.java:66)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:89)
at
org.wso2.carbon.user.core.common.DefaultRealmService.init(DefaultRealmService.java:114)
at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: javax.naming.NameNotFoundException: Name
[jdbc/WSO2CarbonDB] is not bound in this Context. Unable to find
[jdbc].
at org.apache.naming.NamingContext.lookup(NamingContext.java:819)
at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:705)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.doLookup(InitialContext.java:284)
at
org.wso2.carbon.user.core.util.DatabaseUtil.lookupDataSource(DatabaseUtil.java:84)
... 21 more
Thanks.
--
*Asitha Nanayakkara*
Software Engineer
WSO2, Inc. http://wso2.com/
Mob: + 94 77 85 30 682
--
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
--
Asanka Abeyweera
Software Engineer
WSO2 Inc.
Phone: +94 712228648
--
*Asitha Nanayakkara*
Software Engineer
WSO2, Inc. http://wso2.com/
Mob: + 94 77 85 30 682
--
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
--
*Asitha Nanayakkara*
Software Engineer
WSO2, Inc. http://wso2.com/
Mob: + 94 77 85 30 682
--
Asanka Abeyweera
Software Engineer
WSO2 Inc.
Phone: +94 712228648
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Sameera Jayasoma,
Software Architect,
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
E: ram...@wso2.com
P: +94 777542851
