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

[Ajanthan Balachandran]

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

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

[Srinath Perera]

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
>
> 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 locate destination : BURL:StratosHealth
> javax.naming.NamingException: scheme BURL not recognized
> at org.wso2.andes.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:250)
> at org.w
>
> what is the right way to do this?
>
> --Srinath
>
> --
> 
> Srinath Perera, Ph.D.
>   Director, Research, WSO2 Inc.
>   Visiting Faculty, University of Moratuwa
>   Member, Apache Software Foundation
>   Research Scientist, Lanka Software Foundation
>   Blog: http://srinathsview.blogspot.com/
>   Photos: http://www.flickr.com/photos/hemapani/
>Phone: 0772360902
>



-- 

Srinath Perera, Ph.D.
  Director, Research, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
   Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Where should I use BURL with MB topics

[Srinath Perera]

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 locate destination : BURL:StratosHealth
javax.naming.NamingException: scheme BURL not recognized
at org.wso2.andes.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:250)
at org.w

what is the right way to do this?

--Srinath

-- 

Srinath Perera, Ph.D.
  Director, Research, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
   Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Refactor jaggery app

[Harsha Thirimanna]

+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 side we can
> do a grep from appmgt folder and find out where it is referred and we can
> decide whether it is used or not. If we don't do it at-least this way this
> code is going to be much more unreadable.
> About integration tests, they are not updated to multitenanted AF AFAIK.
> But yeah we need to make sure we are not going to cause any regressions.
> Thats why we needs to findout it is really unused. When it comes to jaggery
> its not a big issue to find out the usages. WDYT?
>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
>
> On Thu, Sep 19, 2013 at 6:42 AM, Shiroshica Kulatilake wrote:
>
>> 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 have a
>> guarantee that the tests are covering all the scenarios - otherwise there
>> is no point in using them as a benchmark.
>>
>> I'm +1 for cleaning BUT we are also time constrained to get the features
>> done and stabilizing the pack - prioritizing what needs to be done first
>> and how to approach this without affecting the timelines need to be
>> considered. So if we can't guarantee against regressions - not now.
>>
>> Thank you,
>> Shiro
>>
>>
>> On Thu, Sep 19, 2013 at 2:23 AM, Ramith Jayasinghe wrote:
>>
>>> 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
 Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729

 ___
 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 776715671
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Shiroshica Kulatilake
>>
>> Architect,
>> WSO2, Inc. http://wso2.com/
>> Phone: +94 776523867
>>
>
>
> ___
> 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

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

[Suresh Attanayaka]

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
create the correct SOAP message with proper security. But why do you want
to secure the services with WS-Security ? What about the option of Basic
Authentication over SSL/TLS ?

Thanks,
-Suresh


On Thu, Sep 19, 2013 at 1:53 AM, Danushka Fernando wrote:

> 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 & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Suresh Attanayake
Senior Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Web : http://www.ssoarcade.com/
Facebook : https://www.facebook.com/IdentityWorld
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060
Mobile : +01-616-617-1172
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Refactor jaggery app

[Danushka Fernando]

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
decide whether it is used or not. If we don't do it at-least this way this
code is going to be much more unreadable.
About integration tests, they are not updated to multitenanted AF AFAIK.
But yeah we need to make sure we are not going to cause any regressions.
Thats why we needs to findout it is really unused. When it comes to jaggery
its not a big issue to find out the usages. WDYT?

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Thu, Sep 19, 2013 at 6:42 AM, Shiroshica Kulatilake wrote:

> 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 have a
> guarantee that the tests are covering all the scenarios - otherwise there
> is no point in using them as a benchmark.
>
> I'm +1 for cleaning BUT we are also time constrained to get the features
> done and stabilizing the pack - prioritizing what needs to be done first
> and how to approach this without affecting the timelines need to be
> considered. So if we can't guarantee against regressions - not now.
>
> Thank you,
> Shiro
>
>
> On Thu, Sep 19, 2013 at 2:23 AM, Ramith Jayasinghe wrote:
>
>> 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
>>> Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729
>>>
>>> ___
>>> 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 776715671
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Refactor jaggery app

[Shiroshica Kulatilake]

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 have a
guarantee that the tests are covering all the scenarios - otherwise there
is no point in using them as a benchmark.

I'm +1 for cleaning BUT we are also time constrained to get the features
done and stabilizing the pack - prioritizing what needs to be done first
and how to approach this without affecting the timelines need to be
considered. So if we can't guarantee against regressions - not now.

Thank you,
Shiro


On Thu, Sep 19, 2013 at 2:23 AM, Ramith Jayasinghe  wrote:

> 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
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> ___
>> 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 776715671
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Shiroshica Kulatilake

Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Refactor jaggery app

[Ramith Jayasinghe]

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
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> ___
> 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 776715671
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AF] Refactor jaggery app

[Danushka Fernando]

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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [AF] Jaggery service calls with rampart

[Danushka Fernando]

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 & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Gillian Dass]

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 shall we
have a note mentioning that these configs are for AM1.3.0? Are there any
other changes that need to be considered?

> .
>
> On Wed, Sep 18, 2013 at 6:46 PM, Chamara Silva  wrote:
>
>> 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://docs.wso2.org/display/Cluster/Clustering+API+Manager
>>
>> Thanks,
>> Chamara Silva
>>
>> --
>> A. Suminda Chamara Silva
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile: +94718302858
>> blog: http://chamaras.blogspot.com
>>
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



-- 
Gillian Dass
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware

Mobile: +94 77 757 6331

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Ruwan Yatawara]

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
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Isuru Udana]

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 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 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, Ruwan Yatawara  wrote:
>>
>>> 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
>>> UserStoreMgtDSComponent activated successfully.
>>> [2013-09-18 16:51:01,511]  INFO - TaglibUriRule TLD skipped. URI:
>>> http://tiles.apache.org/tags-tiles is already defined
>>> [2013-09-18 16:51:02,426] FATAL - CarbonServerManager WSO2 Carbon
>>> initialization Failed
>>> org.apache.axis2.AxisFault: Exception occured while loading the Axis
>>> configuration from
>>> /build/branches/platform/products/apimgt/1.5.0/modules/distribution/product/target/wso2am-1.5.0/repository/conf/axis2/axis2.xml
>>>  at
>>> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
>>> at
>>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>>>  at
>>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>>>  at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>  at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>  at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>  at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>  at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>  at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>  at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>  at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>  at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>>  at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>>  at
>>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>>> at
>>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>>  at
>>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>>> at
>>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>>  at
>>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>>> at
>>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>>  at
>>> org.apache.catalina.cor

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

[Ruwan Yatawara]

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.com
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com



On Wed, Sep 18, 2013 at 11:33 PM, Isuru Udana  wrote:

> 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 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 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, Ruwan Yatawara wrote:
>>>
 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
 UserStoreMgtDSComponent activated successfully.
 [2013-09-18 16:51:01,511]  INFO - TaglibUriRule TLD skipped. URI:
 http://tiles.apache.org/tags-tiles is already defined
 [2013-09-18 16:51:02,426] FATAL - CarbonServerManager WSO2 Carbon
 initialization Failed
 org.apache.axis2.AxisFault: Exception occured while loading the Axis
 configuration from
 /build/branches/platform/products/apimgt/1.5.0/modules/distribution/product/target/wso2am-1.5.0/repository/conf/axis2/axis2.xml
  at
 org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
 at
 org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
  at
 org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
 at
 org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
  at
 org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
 at
 org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
  at
 org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
  at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
  at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
 at
 org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
  at
 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
  at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
  at
 org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
  at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
  at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
  at
 org.eclipse.equinox.http.servlet.internal.Activa

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

[Isuru Perera]

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 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, Ruwan Yatawara  wrote:
>
>> 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
>> UserStoreMgtDSComponent activated successfully.
>> [2013-09-18 16:51:01,511]  INFO - TaglibUriRule TLD skipped. URI:
>> http://tiles.apache.org/tags-tiles is already defined
>> [2013-09-18 16:51:02,426] FATAL - CarbonServerManager WSO2 Carbon
>> initialization Failed
>> org.apache.axis2.AxisFault: Exception occured while loading the Axis
>> configuration from
>> /build/branches/platform/products/apimgt/1.5.0/modules/distribution/product/target/wso2am-1.5.0/repository/conf/axis2/axis2.xml
>>  at
>> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>>  at
>> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>>  at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>  at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>  at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>  at
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>  at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>>  at
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>>  at
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>>  at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>  at
>> org.apache.catalina.core.C

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

[Isuru Udana]

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, Ruwan Yatawara  wrote:

> 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
> UserStoreMgtDSComponent activated successfully.
> [2013-09-18 16:51:01,511]  INFO - TaglibUriRule TLD skipped. URI:
> http://tiles.apache.org/tags-tiles is already defined
> [2013-09-18 16:51:02,426] FATAL - CarbonServerManager WSO2 Carbon
> initialization Failed
> org.apache.axis2.AxisFault: Exception occured while loading the Axis
> configuration from
> /build/branches/platform/products/apimgt/1.5.0/modules/distribution/product/target/wso2am-1.5.0/repository/conf/axis2/axis2.xml
>  at
> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>  at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>  at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>  at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>  at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>  at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
>  at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
>  at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
>  at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
> 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$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Th

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

[Ruwan Yatawara]

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
UserStoreMgtDSComponent activated successfully.
[2013-09-18 16:51:01,511]  INFO - TaglibUriRule TLD skipped. URI:
http://tiles.apache.org/tags-tiles is already defined
[2013-09-18 16:51:02,426] FATAL - CarbonServerManager WSO2 Carbon
initialization Failed
org.apache.axis2.AxisFault: Exception occured while loading the Axis
configuration from
/build/branches/platform/products/apimgt/1.5.0/modules/distribution/product/target/wso2am-1.5.0/repository/conf/axis2/axis2.xml
at
org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:190)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
at
org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1186)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1081)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
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$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.deployment.DeploymentException:
org/apache/http/nio/reactor/IOReactorException
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:704)
at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:124)
at
org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(C

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

[Nuwan Dias]

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.
>
> 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 the receiver is down.
>
> 2) Also both analytic scripts in the BAM node should be pointing to the
> one RDBMS database from which the dashboard is going to render the data.
>
> The BAM nodes should be configured as above, then only you can validate
> the load-balancing/fail-over functionality in proper way. When you have
> separate Cassandra instance/RDBMS instance, then both BAM summarization
> will be independent and  will consider only the data local to that
> particular BAM instance.
>
> So please setup the BAM as above mentioned, with cassandra cluster and
> single RDBMS and test the functionality.
>
> Thanks,
> Sinthuja.
>
>
> On Wed, Sep 18, 2013 at 8:52 AM, Sinthuja Ragendran wrote:
>
>> 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 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 ESB and AS are capable to handling failovers
>>> with zero data loss.
>>>
>>> [1] - https://wso2.org/jira/browse/APIMANAGER-1658.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>>
>>> On Wed, Sep 18, 2013 at 8:34 PM, Sinthuja Ragendran 
>>> wrote:
>>>
 AFAIK yes.

 Thanks,
 Sinthuja.


 On Tue, Sep 17, 2013 at 10:19 PM, Chamara Ariyarathne <
 chama...@wso2.com> 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; *+94772786766*
>



 --
 *Sinthuja Rajendran*
 Software Engineer 
 WSO2, Inc.:http://wso2.com

 Blog: http://sinthu-rajan.blogspot.com/
 Mobile: +94774273955



>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>>>  email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Software Engineer 
>> WSO2, Inc.:http://wso2.com
>>
>> Blog: http://sinthu-rajan.blogspot.com/
>> Mobile: +94774273955
>>
>>
>>
>
>
> --
> *Sinthuja Rajendran*
> Software Engineer 
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>


-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Sinthuja Ragendran]

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 the receiver is down.

2) Also both analytic scripts in the BAM node should be pointing to the one
RDBMS database from which the dashboard is going to render the data.

The BAM nodes should be configured as above, then only you can validate the
load-balancing/fail-over functionality in proper way. When you have
separate Cassandra instance/RDBMS instance, then both BAM summarization
will be independent and  will consider only the data local to that
particular BAM instance.

So please setup the BAM as above mentioned, with cassandra cluster and
single RDBMS and test the functionality.

Thanks,
Sinthuja.


On Wed, Sep 18, 2013 at 8:52 AM, Sinthuja Ragendran wrote:

> 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 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 ESB and AS are capable to handling failovers
>> with zero data loss.
>>
>> [1] - https://wso2.org/jira/browse/APIMANAGER-1658.
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Wed, Sep 18, 2013 at 8:34 PM, Sinthuja Ragendran wrote:
>>
>>> 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; *+94772786766*

>>>
>>>
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Software Engineer 
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>>  email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Software Engineer 
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>


-- 
*Sinthuja Rajendran*
Software Engineer 
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Sinthuja Ragendran]

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 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 ESB and AS are capable to handling failovers
> with zero data loss.
>
> [1] - https://wso2.org/jira/browse/APIMANAGER-1658.
>
> Thanks,
> NuwanD.
>
>
> On Wed, Sep 18, 2013 at 8:34 PM, Sinthuja Ragendran wrote:
>
>> 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; *+94772786766*
>>>
>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Software Engineer 
>> WSO2, Inc.:http://wso2.com
>>
>> Blog: http://sinthu-rajan.blogspot.com/
>> Mobile: +94774273955
>>
>>
>>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
>  email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
*Sinthuja Rajendran*
Software Engineer 
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Suneth Ranasinghe]

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 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 the receiver is down.
>>
>> 2) Also both analytic scripts in the BAM node should be pointing to the
>> one RDBMS database from which the dashboard is going to render the data.
>>
>> The BAM nodes should be configured as above, then only you can validate
>> the load-balancing/fail-over functionality in proper way. When you have
>> separate Cassandra instance/RDBMS instance, then both BAM summarization
>> will be independent and  will consider only the data local to that
>> particular BAM instance.
>>
>> So please setup the BAM as above mentioned, with cassandra cluster and
>> single RDBMS and test the functionality.
>>
>> Thanks,
>> Sinthuja.
>>
>>
>> On Wed, Sep 18, 2013 at 8:52 AM, Sinthuja Ragendran wrote:
>>
>>> 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 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 ESB and AS are capable to handling failovers
 with zero data loss.

 [1] - https://wso2.org/jira/browse/APIMANAGER-1658.

 Thanks,
 NuwanD.


 On Wed, Sep 18, 2013 at 8:34 PM, Sinthuja Ragendran 
 wrote:

> AFAIK yes.
>
> Thanks,
> Sinthuja.
>
>
> On Tue, Sep 17, 2013 at 10:19 PM, Chamara Ariyarathne <
> chama...@wso2.com> 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; *+94772786766*
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Software Engineer 
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>


 --
 Nuwan Dias

 Senior Software Engineer - WSO2, Inc. http://wso2.com
  email : nuw...@wso2.com
 Phone : +94 777 775 729

>>>
>>>
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Software Engineer 
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Software Engineer 
>> WSO2, Inc.:http://wso2.com
>>
>> Blog: http://sinthu-rajan.blogspot.com/
>> Mobile: +94774273955
>>
>>
>>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
Suneth Ranasinghe
Senior Software Engineer - QA
Mobile: +94717387198
*
*
wso2.com
Lean Enterprise Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nuwan Dias]

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.
>
>
> 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 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 ESB and AS are capable to handling failovers
>> with zero data loss.
>>
>> [1] - https://wso2.org/jira/browse/APIMANAGER-1658.
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Wed, Sep 18, 2013 at 8:34 PM, Sinthuja Ragendran wrote:
>>
>>> 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; *+94772786766*

>>>
>>>
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Software Engineer 
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>>  email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Software Engineer 
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>


-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Shafreen Anfar]

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
> creates a subscription for every message processor. Currently, these
> message processors are creating subscriptions when the ESB startup. That's
> why this message is printing.
>
> @Shafreen/Ishan: Can you elaborate more on this?
>
> Thanks,
> Chanaka
>
>
> On Tue, Sep 17, 2013 at 11:32 PM, Hasitha Hiranya wrote:
>
>> Hi,
>>
>> Chanaka is correct. MB prints this message when a subscription is done to
>> a message queue and when it vanishes.
>> Argument is why ESB makes a separate subscription for each and every
>> message? (create connection >> get message >> close connection).
>> This is an unnecessary overhead. If you can cache consumer and re-use
>> that would be the ideal way.
>>
>> If above can be done this log will be printed when connection
>> (subscription) is initially happens (when ESB starts) and when it closes
>> (ESB stops).
>>
>> Thanks.
>>
>>
>> On Tue, Sep 17, 2013 at 2:00 PM, Ishara Premadasa wrote:
>>
>>> Hi Dushan/Chanaka,
>>>
>>> The log message is added after creating a new subscription as below and
>>> it is not just increasing a number.
>>>
>>> Subscription subscription =
>>>
>>> SubscriptionFactoryImpl.INSTANCE.createSubscription(_channelId, _session,
>>> tag, acks, filters, noLocal, _creditManager);
>>> return new SubscriptionImpl.AckSubscription(channel, protocolSession,
>>> consumerTag,  filters, noLocal, creditManager, clientMethod, recordMethod);
>>>
>>>
>>> What is the ESB version you are observing this and is this whole log is
>>> seen at the server start up? If this is with ESB 4.8 MS/MP implementation,
>>> I also tried and noticed a similar scenario where i have a MP named
>>> RequestProcessor which listens on queue, request_queue, which is bound to
>>> MS, RequestStore. If i add only a new MesageStore (say ResponseStore) i can
>>> see the following log.
>>>
>>> [2013-09-17 13:49:37,902]  INFO
>>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>>> -  Removing Subscription 2 from queue request_queue
>>> [2013-09-17 13:49:38,639]  INFO
>>> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
>>> -  Binding Subscription 3 to queue request_queue
>>>
>>> The again i edited a name of a proxy  service in my ESB pack and saved
>>> the configuration back, and again there were two similar logs for removing
>>> and binding existing MB subscription. Therefore i think MS/MP
>>> implementation is written to create a new Subscription every time when
>>> synapse configuration is changed?
>>>
>>> On Tue, Sep 17, 2013 at 12:12 PM, Chanaka Fernando wrote:
>>>
 Hi Dushan,

 As per my understanding, this message is printed since the MB is
 creating a temporary subscription to the queue to create the queue
 dynamically (It will remove the subscription instantly). This happens at
 the startup to create the queue in MB side dynamically.

>>>
>>> When adding the queue dynamically, it is true that a new subscription is
>>> created. However in that case subscription is created and closed a single
>>> time and it happens within few seconds. but when seen the logs it seems
>>> removing of subscription  has happened after around 1 minute. Therefore i
>>> feel this is not what has happened here.
>>>
>>> Thanks!
>>> Ishara
>>>

 +1 for the suggestion that we need to either remove the log or print a
 proper log message like "Creating the Queue JMSMS in the Message Broker"


  On Tue, Sep 17, 2013 at 11:51 AM, Dushan Abeyruwan wrote:

>  Hi
>   Once MSMP configured, and  every time ESB starts,from MB side we can
> see following logs [1], it seems like creating new subscription. as how 
> the
> * log message depicted*, but Isuruu pointed that it does not create
> any new subscription, yet it will increase some number.
>   Anyway the logs interprets a wrong message to the end users, so we
> need to get rid of this or need a better message ..rather confusing ppl 
> who
> uses MB..
>
> [1]
> [2013-09-17 11:32:23,104]  INFO
> {org.wso2.andes.server.cassandra.QueueDeliveryWorker} -  Queue worker
> started for queue: JMSMS with on flight message checks
> [2013-09-17 11:32:23,140]  INFO
> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
> -  Binding Subscription 0 to queue JMSMS
> [2013-09-17 11:34:55,843]  INFO
> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
> -  Removing Subscription 0 from queue JMSMS
> [2013-09-17 11:40:05,774]  INFO
> {org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
> - * Binding Subscription 1 to queue JM

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

[Sinthuja Ragendran]

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; *+94772786766*
>



-- 
*Sinthuja Rajendran*
Software Engineer 
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nuwan Dias]

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 ESB and AS are capable to handling failovers
with zero data loss.

[1] - https://wso2.org/jira/browse/APIMANAGER-1658.

Thanks,
NuwanD.


On Wed, Sep 18, 2013 at 8:34 PM, Sinthuja Ragendran wrote:

> 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; *+94772786766*
>>
>
>
>
> --
> *Sinthuja Rajendran*
> Software Engineer 
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>


-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Ravi Undupitiya]

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
> 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
>
>


-- 
*Ravi Undupitiya*
Software Engineer; WSO2 Inc.; http://wso2.com
*
*
*E-mail: r...@wso2.com
**M: **+94 772 930 712*
*
*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Sumedha Rubasinghe]

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
> 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://docs.wso2.org/display/Cluster/Clustering+API+Manager
>
> Thanks,
> Chamara Silva
>
> --
> A. Suminda Chamara Silva
> Senior Software Engineer
> WSO2 Inc.
> Mobile: +94718302858
> blog: http://chamaras.blogspot.com
>
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Isuru Perera]

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, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API Manager clustering guide need to be update

[Chamara Silva]

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://docs.wso2.org/display/Cluster/Clustering+API+Manager

Thanks,
Chamara Silva

-- 
A. Suminda Chamara Silva
Senior Software Engineer
WSO2 Inc.
Mobile: +94718302858
blog: http://chamaras.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Amila Maha Arachchi]

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/mailman/listinfo/dev

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

[Isuruwan Herath]

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 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.*
>
> *In Greg.*
>
> [2013-09-18 15:10:30,491] ERROR {org.apache.catalina.core.ContainerBase} -
>  A child container failed during stop
> java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to stop component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/juddiv3]]
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>  at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at
> org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1179)
>  at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> at
> org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575)
>  at
> org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.catalina.LifecycleException: Failed to stop
> component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/juddiv3]]
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
>  ... 7 more
> Caused by: org.apache.catalina.LifecycleException: Failed to stop
> component [org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager[/juddiv3]]
>  at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
> at
> org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5474)
>  at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> ... 7 more
> Caused by: java.lang.SecurityException: Illegal access attempt by
>  tenant[-1] to sessions owned by tenant[-1234]
>  at
> org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager.checkAccess(CarbonTomcatSessionManager.java:126)
> at
> org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager.findSessions(CarbonTomcatSessionManager.java:78)
>  at
> org.apache.catalina.session.StandardManager.stopInternal(StandardManager.java:525)
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
>  ... 9 more
> [2013-09-18 15:10:30,492] ERROR {org.apache.catalina.core.ContainerBase} -
>  A child container failed during stop
> java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to stop component
> [StandardEngine[Catalina].StandardHost[localhost]]
>  at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>
>
> *In CEP*
>
> [2013-09-18 14:04:37,275] ERROR - {ContainerBase}  A child container
> failed during stop
> java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to stop component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/shindig]]
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>  at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at
> org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1179)
>  at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> at
> org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575)
>  at
> org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.catalina.LifecycleException: Failed to stop
> component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/shindig]]
> at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
>  ... 7 more
> Caused by: org.apache.catalina.LifecycleException: Failed to stop
> component [org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager[/shindig]]
>  at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
> at
> org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5474)
>  at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
> ... 7 more
> Ca

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

[Dhanushka Ranasinghe]

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
>> preparation for chunk02 release.
>> It will still remain open for teams who are releasing.
>>
>>
>> --
>> /sumedha
>> b :  bit.ly/sumedha
>>
>> ___
>> 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 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Dhanushka Ranasinghe,
WSO2 lnc  http://wso2.com
E-mail : dhanush...@wso2.com
Mobile : +94771928269
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Kernel patch for REGISTRY-1889

[Isuruwan Herath]

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/REGISTRY-1881

Regs!


On Wed, Sep 18, 2013 at 12:45 PM, Manoj Kumara  wrote:

> 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-4.2.0-0001
> *and on readme.txt file we can add instruction on how to replace the
> script file.
>
> Is this process correct.
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Wed, Sep 18, 2013 at 11:45 AM, Pulasthi Supun wrote:
>
>> Hi,
>>
>> As per the offline discussion that was done regarding this we decided to
>> add the changed mysql db script into the kernel patch folder. the products
>> that require the changed mysql script file will have to copy the file from
>> location in the kernel patch folder and replace the existing script file.
>> FYI this change will not involve any kind of data migration. @sameera
>> correct me if i missed something.
>>
>> @manoj i have attached the changed mysql script can you work on getting
>> this into the kernel patch folder.
>>
>>
>>
>>  On Tue, Sep 17, 2013 at 5:37 PM, Pulasthi Supun wrote:
>>
>>> Hi Sameera,
>>>
>>> Sure lets have a discussion to solve this ASAP.
>>>
>>> Regards,
>>> Pulasthi
>>>
>>>
>>> On Tue, Sep 17, 2013 at 5:28 PM, Sameera Jayasoma wrote:
>>>
 HI Pulasthi,

 These sql scripts which in kernel/carbon-home/dbscripts/ cannot be
 patched using the normal kernel patching model. We need to think about the
 different approaches to solve this problem. Lets have a discussion on this.


 Thanks,
 Sameera.




 On Tue, Sep 17, 2013 at 11:54 AM, Pulasthi Supun wrote:

> Hi Carbon team,
>
> Can you please verify and apply the patch for issue [1].
>
> [1] https://wso2.org/jira/browse/REGISTRY-1889
>
> Regards,
> Pulasthi
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>



 --
 Sameera Jayasoma,
 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

>>>
>>>
>>>
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuruwan Herath
Technical Lead

Contact: +94 776 273 296


db2.patch
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Kasun Indrasiri]

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.
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>
> ___
> 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 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Mohanadarshan Vivekanandalingam]

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.*

*In Greg.*

[2013-09-18 15:10:30,491] ERROR {org.apache.catalina.core.ContainerBase} -
 A child container failed during stop
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/juddiv3]]
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1179)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
at
org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575)
at
org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/juddiv3]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager[/juddiv3]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
at
org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5474)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 7 more
Caused by: java.lang.SecurityException: Illegal access attempt by
 tenant[-1] to sessions owned by tenant[-1234]
at
org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager.checkAccess(CarbonTomcatSessionManager.java:126)
at
org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager.findSessions(CarbonTomcatSessionManager.java:78)
at
org.apache.catalina.session.StandardManager.stopInternal(StandardManager.java:525)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 9 more
[2013-09-18 15:10:30,492] ERROR {org.apache.catalina.core.ContainerBase} -
 A child container failed during stop
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Catalina].StandardHost[localhost]]
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)


*In CEP*

[2013-09-18 14:04:37,275] ERROR - {ContainerBase}  A child container failed
during stop
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/shindig]]
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at
org.apache.catalina.core.ContainerBase.stopInternal(ContainerBase.java:1179)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
at
org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1575)
at
org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1564)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/shindig]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to stop component
[org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager[/shindig]]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:236)
at
org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5474)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
... 7 more
Caused by: java.lang.SecurityException: Illegal access attempt by
 tenant[-1] to sessions owned by tenant[-1234]
at
org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager.checkAccess(CarbonTomcatSessionManager.java:126)
at
org.wso2.carbon.webapp.mgt.CarbonTomcatSessionManager.findSessions(CarbonTomcatSessionManager.java:78)
at
org.apache.catalina.session.StandardManager.stopInternal(StandardManager.java:525)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:

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

[Sumedha Rubasinghe]

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, 2013 at 12:38 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 cause.
>
> But came through this [1] which says this is due to duplicate dependencies
> of taglibs. Hence seems it is harmless. Please correct me if I'm wrong.
>
> [1]
> http://thinkinginsoftware.blogspot.com/2011/10/tomcat-7-tld-skipped-is-already-defined.html
>
> Thanks,
> Tanya.
>
>
> On Wed, Sep 18, 2013 at 10:06 AM, Tanya Madurapperuma wrote:
>
>> I will have a look whether this causes due to commit r174306.
>>
>> Thanks,
>> Tanya
>>
>>
>> On Wed, Sep 18, 2013 at 9:58 AM, Ajith Vitharana  wrote:
>>
>>> Hi All,
>>>
>>> I can see the following INFO log starting the server. Is this harmless ?
>>>
>>>  INFO {org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI:
>>> http://tiles.apache.org/tags-tiles is already defined
>>>
>>> [1]https://wso2.org/jira/browse/CARBON-14122
>>> [2https://wso2.org/jira/browse/REGISTRY-1934
>>>
>>>
>>> --
>>> Ajith Vitharana.
>>> WSO2 Inc. - http://wso2.org
>>>  Email  :  aji...@wso2.com
>>> Mobile : +94772217350
>>>
>>>
>>
>>
>> --
>> Tanya Madurapperuma
>>
>> Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94718184439
>>
>
>
>
> --
> Tanya Madurapperuma
>
> Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94718184439
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chuck 02 Build failure

[Sanjeewa Malalgoda]

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 following error while
>> building greg product. Please have a look at.
>>
>> Thanks,
>> Sanjeewa.
>>
>> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Registry Content Search Feature
>> 4.2.1 (org.wso2.carbon.registry.contentsearch.feature.group 4.2.1)
>>  Missing requirement: WSO2 Carbon - Registry Core Server Feature 4.2.1
>> (org.wso2.carbon.registry.core.server.feature.group 4.2.1) requires
>> 'org.wso2.carbon.registry.core.common.feature.group [4.2.1,4.3.0)' but it
>> could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Registry Content Search Feature 4.2.1
>> (org.wso2.carbon.registry.contentsearch.feature.group 4.2.1)
>>   To: org.wso2.carbon.registry.contentsearch.server.feature.group [4.2.1]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Registry Content Search Server Feature 4.2.1
>> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.1)
>>   To: org.wso2.carbon.registry.core.server.feature.group [4.2.0,4.3.0)
>> Application failed, log file location:
>> /home/wso2/4.1.5/m2-clean-repo-6/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1379448694834.log
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 API Manager - Integration Test Module  SUCCESS
>> [15.928s]
>> [INFO] WSO2 API Manager - Integration UI Test Module . SUCCESS
>> [2.436s]
>> [INFO] WSO2 API Manager - Integration Tests .. SUCCESS
>> [0.013s]
>> [INFO] WSO2 API Manager - Aggregator Module .. SUCCESS
>> [0.054s]
>> [INFO] WSO2 Governance Registry .. SUCCESS
>> [0.147s]
>> [INFO] WSO2 Governance Registry Styles Parent  SUCCESS
>> [0.055s]
>> [INFO] WSO2 Governance Registry - UI Styles .. SUCCESS
>> [4.836s]
>> [INFO] WSO2 Stratos - Cloud Governance UI styles . SUCCESS
>> [1.367s]
>> [INFO] WSO2 Governance Registry - Dashboard .. SUCCESS
>> [1.040s]
>> [INFO] WSO2 Governance Registry - Check-in Client  SUCCESS
>> [6.892s]
>> [INFO] WSO2 Governance Registry - JUDDI Listener . SUCCESS
>> [5.096s]
>> [INFO] jUDDI war construction  SUCCESS
>> [5.323s]
>> [INFO] WSO2 Governance Registry - CMIS Integration ... SUCCESS
>> [1.407s]
>> [INFO] WSO2 Governance Registry - Samples  SUCCESS
>> [0.080s]
>> [INFO] WSO2 Governance Registry - Shutterbug Sample .. SUCCESS
>> [0.032s]
>> [INFO] WSO2 Governance Registry - Shutterbug Sample BE ... SUCCESS
>> [4.470s]
>> [INFO] WSO2 Governance Registry - Shutterbug Sample FE ... SUCCESS
>> [5.088s]
>> [INFO] WSO2 Carbon - Registry - Sample Custom UI - Topics BE  SUCCESS
>> [3.083s]
>> [INFO] WSO2 Carbon - Registry - Sample Custom UI - Topics UI  SUCCESS
>> [3.282s]
>> [INFO] WSO2 Carbon - Registry - Handler Sample ... SUCCESS
>> [2.106s]
>> [INFO] WSO2 Governance Registry - JCR Client . SUCCESS
>> [0.119s]
>> [INFO] WSO2 Governance Registry - JCR Client . SUCCESS
>> [1.614s]
>> [INFO] WSO2 Governance Registry Features Parent .. SUCCESS
>> [0.048s]
>> [INFO] WSO2 Governance Registry - Features Aggregator Module  SUCCESS
>> [0.019s]
>> [INFO] WSO2 Governance Registry - Styles Feature . SUCCESS
>> [0.533s]
>> [INFO] WSO2 Stratos - Cloud Governance Dashboard User Interface  SUCCESS
>> [3.573s]
>> [INFO] WSO2 Stratos - Cloud Governance Login User Interface  SUCCESS
>> [1.025s]
>> [INFO] WSO2 Stratos - Cloud Governance Features Aggregator Module
>>  SUCCESS [0.080s]
>> [INFO] WSO2 Carbon - Cloud Governance UI Feature . SUCCESS
>> [0.887s]
>> [INFO] WSO2 Governance Registry - P2 Profile Generation .. FAILURE
>> [45.127s]
>> [INFO] WSO2 API Manager - BAM Toolbox  SKIPPED
>> [INFO] WSO2 Governance Registry - Distribution ... SKIPPED
>> [INFO] WSO2 Governance Registry - Integration Tests .. SKIPPED
>> [INFO] WSO2 Governance Registry Test Framework - Registry Test Module
>> Group  SKIPPED
>> [INFO] Registry TCK Test Module .. SKIPPED
>> [INFO] Registry TestNG Test Samples .. SKIPPED
>> [INFO] Backward association handler Sample ... SKIPPED
>> [INFO] Registry TestNG Test Module ... SKIPPED
>> [INFO] Registry Resources TestNG Test Module . SKIPPED
>> [INFO] Registry Metadata TestNG Test Module .. SKIPPED
>> [INFO] Registry Extensibility TestNG Test Module . SKIPPED
>> [INFO] Registry JIRA TestNG Test Module ..

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

[Isuru Perera]

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 cause.
>
> But came through this [1] which says this is due to duplicate dependencies
> of taglibs. Hence seems it is harmless. Please correct me if I'm wrong.
>
> [1]
> http://thinkinginsoftware.blogspot.com/2011/10/tomcat-7-tld-skipped-is-already-defined.html
>
> Thanks,
> Tanya.
>
>
> On Wed, Sep 18, 2013 at 10:06 AM, Tanya Madurapperuma wrote:
>
>> I will have a look whether this causes due to commit r174306.
>>
>> Thanks,
>> Tanya
>>
>>
>> On Wed, Sep 18, 2013 at 9:58 AM, Ajith Vitharana  wrote:
>>
>>> Hi All,
>>>
>>> I can see the following INFO log starting the server. Is this harmless ?
>>>
>>>  INFO {org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI:
>>> http://tiles.apache.org/tags-tiles is already defined
>>>
>>> [1]https://wso2.org/jira/browse/CARBON-14122
>>> [2https://wso2.org/jira/browse/REGISTRY-1934
>>>
>>>
>>> --
>>> Ajith Vitharana.
>>> WSO2 Inc. - http://wso2.org
>>>  Email  :  aji...@wso2.com
>>> Mobile : +94772217350
>>>
>>>
>>
>>
>> --
>> Tanya Madurapperuma
>>
>> Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94718184439
>>
>
>
>
> --
> Tanya Madurapperuma
>
> Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94718184439
>
> ___
> 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

Re: [Dev] Kernel patch for REGISTRY-1889

[Manoj Kumara]

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-4.2.0-0001
*and on readme.txt file we can add instruction on how to replace the script
file.

Is this process correct.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Wed, Sep 18, 2013 at 11:45 AM, Pulasthi Supun  wrote:

> Hi,
>
> As per the offline discussion that was done regarding this we decided to
> add the changed mysql db script into the kernel patch folder. the products
> that require the changed mysql script file will have to copy the file from
> location in the kernel patch folder and replace the existing script file.
> FYI this change will not involve any kind of data migration. @sameera
> correct me if i missed something.
>
> @manoj i have attached the changed mysql script can you work on getting
> this into the kernel patch folder.
>
>
>
>  On Tue, Sep 17, 2013 at 5:37 PM, Pulasthi Supun wrote:
>
>> Hi Sameera,
>>
>> Sure lets have a discussion to solve this ASAP.
>>
>> Regards,
>> Pulasthi
>>
>>
>> On Tue, Sep 17, 2013 at 5:28 PM, Sameera Jayasoma wrote:
>>
>>> HI Pulasthi,
>>>
>>> These sql scripts which in kernel/carbon-home/dbscripts/ cannot be
>>> patched using the normal kernel patching model. We need to think about the
>>> different approaches to solve this problem. Lets have a discussion on this.
>>>
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>
>>>
>>>
>>> On Tue, Sep 17, 2013 at 11:54 AM, Pulasthi Supun wrote:
>>>
 Hi Carbon team,

 Can you please verify and apply the patch for issue [1].

 [1] https://wso2.org/jira/browse/REGISTRY-1889

 Regards,
 Pulasthi
 --
 --
 Pulasthi Supun
 Software Engineer; WSO2 Inc.; http://wso2.com,
 Email: pulas...@wso2.com
 Mobile: +94 (71) 9258281
 Blog : http://pulasthisupun.blogspot.com/
 Git hub profile: https://github.com/pulasthi

>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> 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
>>>
>>
>>
>>
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>
>
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Tanya Madurapperuma]

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 - RegistryCoreServiceComponent Registry
> Mode: READ-WRITE
> [2013-09-12 10:13:46,023]  INFO - UserStoreMgtDSComponent Carbon
> UserStoreMgtDSComponent activated successfully.
> *[2013-09-12 10:14:02,909]  INFO - TaglibUriRule TLD skipped. URI:
> http://tiles.apache.org/tags-tiles is already defined*
>
>
> Cheers,
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Tanya Madurapperuma

Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Tanya Madurapperuma]

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 me if I'm wrong.

[1]
http://thinkinginsoftware.blogspot.com/2011/10/tomcat-7-tld-skipped-is-already-defined.html

Thanks,
Tanya.


On Wed, Sep 18, 2013 at 10:06 AM, Tanya Madurapperuma wrote:

> I will have a look whether this causes due to commit r174306.
>
> Thanks,
> Tanya
>
>
> On Wed, Sep 18, 2013 at 9:58 AM, Ajith Vitharana  wrote:
>
>> Hi All,
>>
>> I can see the following INFO log starting the server. Is this harmless ?
>>
>>  INFO {org.apache.catalina.startup.TaglibUriRule} -  TLD skipped. URI:
>> http://tiles.apache.org/tags-tiles is already defined
>>
>> [1]https://wso2.org/jira/browse/CARBON-14122
>> [2https://wso2.org/jira/browse/REGISTRY-1934
>>
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>>  Email  :  aji...@wso2.com
>> Mobile : +94772217350
>>
>>
>
>
> --
> Tanya Madurapperuma
>
> Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94718184439
>



-- 
Tanya Madurapperuma

Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev