Re: [Dev] TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined

Hi, Got a checkout upto r174306 and the product build out of that revision does not have the above mentioned INFO log. Therefore the commit r174306 is not the cause. But came through this [1] which says this is due to duplicate dependencies of taglibs. Hence seems it is harmless. Please correct m

Re: [Dev] INFO - TaglibUriRule TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined (what is this)

Same is discussed in the thread with the subject 'TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined'. Thanks, Tanya. On Thu, Sep 12, 2013 at 10:16 AM, Dushan Abeyruwan wrote: > Hi > Why we see a log when startup CARBON products ? > > [2013-09-12 10:13:45,686] INFO - Re

Re: [Dev] Kernel patch for REGISTRY-1889

Hi Sameera, What I think is was to create same directory structure on patch0001 as, *patch0001/distribution/kernel/carbon-home/dbscripts* * * and attach the required script file to the above directory. During build time this script file can be copied to the patch archive inside *WSO2-CARBON-PATCH

Re: [Dev] TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined

Even though it is harmless, we should fix that. -- Sent from mobile On Sep 18, 2013 12:41 PM, "Tanya Madurapperuma" wrote: > Hi, > > Got a checkout upto r174306 and the product build out of that revision > does not have the above mentioned INFO log. Therefore the commit r174306 > is not the caus

Re: [Dev] Chuck 02 Build failure

Thanks. Added new greg pack to nightly builds. Thanks, Sanjeewa. On Wed, Sep 18, 2013 at 9:10 AM, Eranda Sooriyabandara wrote: > Fixed. > > thanks > Eranda > > > On Wed, Sep 18, 2013 at 1:41 AM, Sanjeewa Malalgoda wrote: > >> Hi Team, >> Took full update and built from chuck 02 level. Got follow

Re: [Dev] TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined

The reason for this error could be due to TLD (http://tiles.apache.org/tags- tiles) being duplicated in multiple jar files. @ the runtime , these TLDs try to get registered. If the same TLD (uri) is already registered, this error gets thrown. Search all jar files for this TLD. On Wed, Sep 18, 20

[Dev] Exception when Shutdown server in Forced mode and Graceful mode from UI

Hi All, I have observed some errors when shutdown the carbon servers in graceful mode and forced mode from UI. (Not happened when Ctrl + C ). I can see these errors in Greg, CEP and also in APIM (not in graceful mode). I think root cause should be same. *In Forced mode below errors are coming.*

Re: [Dev] Code Freeze for Carbon 4.2.0 - chunk 02 release - after 3pm today

Please grant commit rights to Ravi and Dushan from ESB team. On Wed, Sep 18, 2013 at 11:12 AM, Sumedha Rubasinghe wrote: > Devs, > Carbon 4.2.0 branch will be frozen for commits after 3pm today in > preparation for chunk02 release. > It will still remain open for teams who are releasing. > > > -

Re: [Dev] Kernel patch for REGISTRY-1889

Hi, DB2 sql file also have some changes with reference to issue [2] . G-Reg could not be started with DB2 since the script had not been updated with changes. Please verify and commit the attached patch for db2.sql to the kernel patch folder mentioned above. [2] https://wso2.org/jira/browse/REGIST

Re: [Dev] Code Freeze for Carbon 4.2.0 - chunk 02 release - after 3pm today

Done Thank You Dhanushka On Wed, Sep 18, 2013 at 3:47 PM, Kasun Indrasiri wrote: > Please grant commit rights to Ravi and Dushan from ESB team. > > > On Wed, Sep 18, 2013 at 11:12 AM, Sumedha Rubasinghe wrote: > >> Devs, >> Carbon 4.2.0 branch will be frozen for commits after 3pm today in >> p

Re: [Dev] Exception when Shutdown server in Forced mode and Graceful mode from UI

Hi, Yes, I too noticed the same in G-Reg and reported in [1 ]. [1] https://wso2.org/jira/browse/CARBON-14470 Regs! Isuruwan On Wed, Sep 18, 2013 at 3:36 PM, Mohanadarshan Vivekanandalingam < mo...@wso2.com> wrote: > Hi All, > > I have observed some e

[Dev] Need a latest ELB pack with the spinning issue fixed

Hi Isuru, $Subject. Is it available? Regards, AmilaM. -- *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/mailma

[Dev] API Manager clustering guide need to be update

In APIM clustering guide says publisher directly interact with key manager. But i got to know there's no meaningful of having key manager URL in publisher configuration. So it would be great to change both images of doc [1] (Arrow from publisher to key manager) and related configurations. 1.http:/

Re: [Dev] Need a latest ELB pack with the spinning issue fixed

Hi Amila, It is not yet available. We should be able to build a pack today with all related fixes. Thanks! On Wed, Sep 18, 2013 at 6:35 PM, Amila Maha Arachchi wrote: > Hi Isuru, > > $Subject. Is it available? > > Regards, > AmilaM. > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2,

Re: [Dev] API Manager clustering guide need to be update

Looping in Gillian. There was a requirement to connect Publisher to Key Manager in AM130. But this is no longer the case from AM140 onwards. Please change the doc. On Wed, Sep 18, 2013 at 6:46 PM, Chamara Silva wrote: > In APIM clustering guide says publisher directly interact with key > manage

Re: [Dev] Need a latest ELB pack with the spinning issue fixed

The changes have been made and committed, once the kernel changes are committed, we should be able to build a pack. On Wed, Sep 18, 2013 at 6:35 PM, Amila Maha Arachchi wrote: > Hi Isuru, > > $Subject. Is it available? > > Regards, > AmilaM. > > -- > *Amila Maharachchi* > Senior Technical Lead >

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

I believe this concern is regarding issue [1]. @Sinthuja, can you please go through this and see whether reducing the polling interval is a valid workaround for the problem. If not, what other ways does the data-publishing-agent provide of immediately detecting failures? According to Chamara, both

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

AFAIK yes. Thanks, Sinthuja. On Tue, Sep 17, 2013 at 10:19 PM, Chamara Ariyarathne wrote: > Is it implemented the way ESB and AS does it? > > As Load Balancing and Failover both ways. > > -- > *Chamara Ariyarathne* > Senior Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; *+9

Re: [Dev] MB Log message {Binding Subscription x to queue JMSMS}

Hi Hasitha, Yes. As Chanak explained we do not create a connection for each request but instead we create a connection for each message processor. On Wed, Sep 18, 2013 at 8:36 AM, Chanaka Fernando wrote: > Hi Hasitha, > > ESB does not create a subscription for each and every message. It only >

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

AFAIK Cassandra is not clustered. Its just 2 BAM nodes pointed to a single relational DB. Thanks, NuwanD. On Wed, Sep 18, 2013 at 9:22 PM, Sinthuja Ragendran wrote: > Hi chamara, > > whether the cassandra is clustered within these two BAM setups? Please > confirm. > > Thanks, > Sinthuja. > > >

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

Noted, we'll set up our servers accordingly. On Wed, Sep 18, 2013 at 9:45 PM, Nuwan Dias wrote: > Thanks for the explanations Sinthuja. @Suneth, please test this by > clustering the Cassandra servers. > > Thanks, > NuwanD. > > > On Wed, Sep 18, 2013 at 9:36 PM, Sinthuja Ragendran wrote: > >> Hi

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

Hi chamara, whether the cassandra is clustered within these two BAM setups? Please confirm. Thanks, Sinthuja. On Wed, Sep 18, 2013 at 8:35 AM, Nuwan Dias wrote: > I believe this concern is regarding issue [1]. @Sinthuja, can you please > go through this and see whether reducing the polling in

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

Hi Nuwan/Chamara, For the load-balancing/fail-over data publishing, we need to have the following BAM setup. 1) Cassandra servers should be clustered within both BAM nodes. Only then all the data received by the BAM will go to the cassandra cluster, and there won't be any data loss regardless of

Re: [Dev] BAM Statstics Publishing in API Manager 1.5.0

Thanks for the explanations Sinthuja. @Suneth, please test this by clustering the Cassandra servers. Thanks, NuwanD. On Wed, Sep 18, 2013 at 9:36 PM, Sinthuja Ragendran wrote: > Hi Nuwan/Chamara, > > For the load-balancing/fail-over data publishing, we need to have the > following BAM setup. >

[Dev] [BLOCKER] Startup failure in AM and ELB Nightly packs

Hi All, API Manager and ELB packs fail to startup with the following error. Removing the patch0001 however resolves the error. [2013-09-18 16:50:57,979] INFO - RegistryCoreServiceComponent Registry Mode: READ-WRITE [2013-09-18 16:50:58,957] INFO - UserStoreMgtDSComponent Carbon UserStoreMgt

Re: [Dev] [BLOCKER] Startup failure in AM and ELB Nightly packs

Hi Ruwan, Can you please check whether r185869 is updated in your checkout. You are getting this since still httpcore-nio version is 4.3.0 in your built pack. I tried manually removing that and adding the older version and managed to start the pack. Thanks. On Wed, Sep 18, 2013 at 10:25 PM, R

Re: [Dev] [BLOCKER] Startup failure in AM and ELB Nightly packs

Yes Isuru. It seems to be a problem with httpcore-nio version and the mentioned revision change is not there in the pack. Ruwan will check and confirm. Thanks for checking! On Wed, Sep 18, 2013 at 11:07 PM, Isuru Udana wrote: > Hi Ruwan, > > Can you please check whether r185869 is updated in

Re: [Dev] [BLOCKER] Startup failure in AM and ELB Nightly packs

Hi All, This issue got resolved, apparently there has been two parts to the fix, updating the synapse feature did the trick.. Thanks Ravi, IsuruU and IsuruP for the assitance! Thanks and Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.co

Re: [Dev] [BLOCKER] Startup failure in AM and ELB Nightly packs

I just built a ELB pack with updating kernel patches and synapse nhttp feature and it starts without a problem. So problem should be with outdated svn in builder machine. On Wed, Sep 18, 2013 at 11:23 PM, Isuru Perera wrote: > Yes Isuru. > > It seems to be a problem with httpcore-nio version an

[Dev] Nightly Build Packs - 18/09/2013

QA Team, Packs from revision 185866 (API Manager, GREG, CEP, ELB) can be downloaded from [1]. [1] : http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N-18_09_2013/ Thanks and Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com

Re: [Dev] API Manager clustering guide need to be update

On Wed, Sep 18, 2013 at 7:11 PM, Sumedha Rubasinghe wrote: > Looping in Gillian. > There was a requirement to connect Publisher to Key Manager in AM130. But > this is no longer the case from AM140 onwards. > Please change the doc. > We will consider this when updating the clustering doc. For now

[Dev] [AF] Jaggery service calls with rampart

Hi >From jaggery app we are calling lot of services with rampart policies. In 1.0.0 we passed that magic user credentials there. But now we cant do that. In other service calls we are sending the cookie in header. Is there a way to use a cookie for authentication with rampart policies. Thanks & R

[Dev] [AF] Refactor jaggery app

Hi, In our jaggery app (appmgt) there are lot of unused codes. These makes it difficult to change something. So shall we remove these unused codes when we found one? Thanks & Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 __

Re: [Dev] [AF] Refactor jaggery app

yea. thats cool. On Thu, Sep 19, 2013 at 2:16 AM, Danushka Fernando wrote: > Hi, > In our jaggery app (appmgt) there are lot of unused codes. These makes it > difficult to change something. So shall we remove these unused codes when > we found one? > > Thanks & Regards > Danushka Fernando > Soft

Re: [Dev] [AF] Refactor jaggery app

Hi Danushka, Do you have the integration tests up and running ? If so the correct way would be to run these before any changes - see whether all is ok and then start the clean up - step by step running the integration tests after each step- so that we don't add any regressions. We also need to ha

Re: [Dev] [AF] Refactor jaggery app

Hi Shiro I am not going to clean up everything. And also I am not proposing to cleanup in one day or one time. I proposed that when we saw something unused find-out is it really unused and remove it. In jaggery side we can do a grep from appmgt folder and find out where it is referred and we can de

Re: [Dev] [AF] Jaggery service calls with rampart

Hi Dhanuska, There are no WS-Security Policies for cookie based authentication. What are these services and what are the policies currently the services are secured with ? And what is this "magic" credential you were using ? If the services are secured with WS-Security Policies you will have to c

Re: [Dev] [AF] Refactor jaggery app

+1 , yes, it is good. On Sep 19, 2013 9:45 AM, "Danushka Fernando" wrote: > Hi Shiro > I am not going to clean up everything. And also I am not proposing to > cleanup in one day or one time. I proposed that when we saw something > unused find-out is it really unused and remove it. In jaggery sid

[Dev] Where should I use BURL with MB topics

Hi Mohan, I am configuring CEP with MB2. If I configure in event builder with the destination as StratosHealth it throws java.lang.UnsupportedOperationException: The new addressing based sytanx is not supported for AMQP 0-8/0-9 versions If I configure it as BURL:StratosHealth I get Cannot

Re: [Dev] Where should I use BURL with MB topics

Resolved. It worked after adding the queue do jndi.properties file. As per docs, it is Burl : not BURL. --Srinath On Thu, Sep 19, 2013 at 11:38 AM, Srinath Perera wrote: > Hi Mohan, > > I am configuring CEP with MB2. > > If I configure in event builder with the destination as > > StratosHealt

Re: [Dev] [AF] Jaggery service calls with rampart

Danushka, Secure your service/BPEL with policy SgnEncrAnonymous(SAML token) and call the service with SAML token. Thanks ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev