[Dev] cron job on MessageProcessor?

[John Hawkins]

Hi All,

I'm trying to figure out when does the "cron  schedule" get used that I can
configure on the MessageProcessor?

The logic that I think is happening is - if the message fails to get sent
'retry' number of times then it's put to the dead letter queue (or DLC as
its called in qpid) . The Message Processor then looks at the DLC based on
when the cron job tells it to?

If this logic is correct (?)  then I have a number of other questions
please:

1) what if this cron job is not set - does the message remain on the DLQ?
2) Where is the DLQ defined  to synapse/the message processor so that it
knows where to go?
3) What if the message gets removed from the DLC for some reason (manually
or otherwise)? Do we fail quietly or log it somewhere?
4) What if other messages from other parts of the ESB get put to the DLQ ?
How does the MessageProcessor know which messages are for it?


many thanks for your help !
john.


John Hawkins
Director: Solutions Architecture
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cron job on MessageProcessor?

[Ravindra Ranwala]

Hi John,

The Cron expression in MP is used to create firing schedules such as "At
8:00am every Monday through Friday" [1]. If it is set the MP will run
according to that. Otherwise MP will poll the queue with the specified
interval value continuously.

Also the MP has a parameter called max_delivery_attempts (defaults to 4),
which defines the maximum retry attempts in case of a failure in end point.
By default if the MP could not send the message to the end point after this
number of retry count, it deactivates itself. But that message remains in
the queue. After that you have to activate the MP explicitly to make the
next schedule to be effective. Otherwise it will remain deactivated.

If you need to override the above behaviour, you need to enable
max-delivery-drop parameter, so that if the MP could not send the message
after this number of attempts, it merely drops the message and continues.
Here you loose the message if the endpoint is down.


[1]
http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger


Thanks & Regards,

On Thu, Sep 3, 2015 at 8:05 PM, John Hawkins  wrote:

> Hi All,
>
> I'm trying to figure out when does the "cron  schedule" get used that I
> can configure on the MessageProcessor?
>
> The logic that I think is happening is - if the message fails to get sent
> 'retry' number of times then it's put to the dead letter queue (or DLC as
> its called in qpid) . The Message Processor then looks at the DLC based on
> when the cron job tells it to?
>
> If this logic is correct (?)  then I have a number of other questions
> please:
>
> 1) what if this cron job is not set - does the message remain on the DLQ?
> 2) Where is the DLQ defined  to synapse/the message processor so that it
> knows where to go?
> 3) What if the message gets removed from the DLC for some reason (manually
> or otherwise)? Do we fail quietly or log it somewhere?
> 4) What if other messages from other parts of the ESB get put to the DLQ ?
> How does the MessageProcessor know which messages are for it?
>
>
> many thanks for your help !
> john.
>
>
> John Hawkins
> Director: Solutions Architecture
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com

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

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Thayalan]

Hi Team,

I've observed from the standalone pack without any changes user has not
been allowed to re-login  to the store [1]. However this is working fine
for publisher. As per the suggestion in [1] hostname has to be set in
carbon.xml. However in the default pack SSO enabled for store/publisher and
Hostname tag is commented. Even uncomment them and set to IP or localhost
too not working as suggested in the JIRA. From the end user perspective
user should allow to re-login from the same window session from the fresh
pack. Is this is something we need to fix before releasing them?

1.REGISTRY-2927 

On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda  wrote:

> -1,
>
> We found an issue with solr related logging configuration and this issue
> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>
> Step to reproduce this issue:
>
> Go to Main --> Registry search and search by any value.
> Then navigate to Configure --> Logging section.
> Exceptions are logged in console and "Global Log4J Configuration" and
> "Configure Log4J Appenders" views are not loading due to the above issue.
>
> Created a JIRA[1] to track above issue and will release release G-Reg
> 5.0.0 RC3 pack ASAP.
>
> [1]. https://wso2.org/jira/browse/WSAS-2120
>
> Regards,
> Chandana
>
>
> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
> wrote:
>
>> Hi Pubudu,
>>
>> Since we have already released RC2 pack and component repos, we can not
>> update above pages now. We will update context specific pages for coming up
>> 5.0.1 release. Meantime, you can refer wiki based documentation available
>> here [1].
>>
>> [1].
>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>
>> Regards,
>> Chandana
>>
>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Chandana,
>>>
>>> Since the Help page, context specific pages are out-dated we need to
>>> update those to reflect most recent information. Can you please address
>>> this issue as required? Please find the relevant ticket below. Thanks.
>>>
>>> https://wso2.org/jira/browse/REGISTRY-2910
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe 
>>> wrote:
>>>
 The context sensitive help links are in the product UIs. AFAIK, these
 links are component-based rather than product based? Please correct me if I
 am wrong.

 If they are component-based, we cannot link to the wiki of a specific
 product from there as many other products might also be using the same
 component.

 Maybe we should simply disable these help links until we find a better
 way to maintain them.

 Thanks,
 -Nirdesha

 On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
 wrote:

> Hi Nirdesha,
>
> Can we please point the current context sensitive help pages to
> relevant product documentation of GReg 5.0.0 release?
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
> wrote:
>
>>
>>
>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
>> evanth...@wso2.com> wrote:
>>
>>> Ack!
>>>
>>> @Chalitha/Thaya/Pubudu. Please note.
>>>
>>
>> And all the context sensitive help pages  are outdated .
>>
>> -Ajith
>>
>>
>>>
>>> Regards,
>>> Evanthika Amarasiri
>>> Senior Technical Lead  - Quality Assurance
>>> Mobile: +94773125935
>>> Blog: evanthika.blogspot.com
>>>
>>> wso2.com lean.enterprise.middleware
>>>
>>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All

 This is non a bug but please fix the about page if possible because
 this is a major release. (find the attached image)

 -Ajith





 On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
 prasa...@wso2.com> wrote:

> Hi All,
>
> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>
> This release fixes the following issues:
>
> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
> https://wso2.org/jira/browse/REGISTRY-2908
>
> Please download, test and vote. Please refer the release
> verification guide for detailed information on verifying this release.
>
> *Source & binary distribution files:*
>
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/
>
> *Maven staging repo:*
>

Re: [Dev] Email-Templates UI in G-Reg 5.0

[Shazni Nazeer]

Hi Ajith,

FYI
identity­-mgt.properties is now moved to epository/conf/identity directory.

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Tue, Sep 1, 2015 at 10:42 PM, Ajith Vitharana  wrote:

>
>
> On Wed, Sep 2, 2015 at 1:32 AM, Chalitha Waldeniyage 
> wrote:
>
>> Hi Ajith,
>>
>> This is discussed in Architecture mail in [1]  . Please refer [2] for
>> more information.
>>
>> [1] Tenant wise email templates improvement
>>
>> [2]
>> https://docs.wso2.com/display/IS450/Self+Sign+Up+and+Account+Confirmation
>> 
>>
>
> This usage in Identity Server. What is the usage of having this UI in
> Governance Registry ? AFAIU this is redundant UI for G-Reg.  However if we
> support same thing  in G-Reg we should have identity­-mgt.properties file
> inside the wso2greg-5.0.0/repository/conf/security, But I can't find that ?
>
>
> -Ajith
>
>>
>>
>> Thank you,
>> Chalitha.
>>
>> On Wed, Sep 2, 2015 at 9:47 AM, Ajith Vitharana  wrote:
>>
>>> Hi All,
>>>
>>> What is the feature  and usage of this UI in G-Reg 5.0 ?
>>>
>>> -Ajith
>>>
>>> --
>>> Ajith Vitharana.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Chalitha Maheshwari*
>> Software Engineer-QA,
>> WSO2 Inc.
>>
>> *E-mail:* chali...@wso2.com
>> *Mobile: *+94710 411 112
>>
>
>
>
> --
> Ajith Vitharana.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>
> ___
> 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] How to call "IdentityApplicationManagementService" admin service as a tenant user

[Sanjeewa Malalgoda]

API Manager/ APP Manager applications are super tenant deployed
multitenanted SaaS applications.
So its common to have some operations perform as admin users. Actually in
that cases application act as super users and handle tenants and other user
flows.
So i dont see big issue with this. And We may not need call these admin
services as tenant users(users will call APIs but actual operation and
admin service call done by super tenant deployed app).

Thanks,
sanjeewa.

On Thu, Sep 3, 2015 at 10:56 PM, Amila De Silva  wrote:

> Hi,
>
> If this is about calling *ApplicationManagementAdmin**Service *using 
> MutualSSL,
> then still this would be only available to admin users, isn't it. A similar
> approach was attempted while trying to create SP for AM_Application, at the
> time of Generating a key. The problem was, even mutual SSL allows user to
> authenticate, since this is an admin service, users are failed at the
> authorising step unless they are admin users.
>
> On Thu, Sep 3, 2015 at 12:20 AM, Sanjeewa Malalgoda 
> wrote:
>
>> If you are trying to implement tenant SP creation for App manager then we
>> can easily do it using mutual SSL with tenant user name.
>> We have implemented something similar and we can share code with you soon.
>>
>> Thanks,
>> sanjeewa.
>>
>> On Thu, Sep 3, 2015 at 12:13 AM, Lakshani Gamage 
>> wrote:
>>
>>> Hi all,
>>>
>>> I want to call "*IdentityApplicationManagementService*" admin service
>>> as a tenant user.
>>>
>>> I gave super tenant credentials to that stub and called  "
>>> *createApplication*" method by changing tenant flow. But still the SP
>>> is created in ST space.
>>>
>>> If you have any idea, how to call this Service as a tenant user, Please
>>> share it.
>>>
>>> Thanks,
>>> Lakshani
>>>
>>>
>>>
>>> --
>>> Lakshani Gamage
>>>
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 5478184 <%2B94%20%280%29%20773%20451194>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>> blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> 
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

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

Re: [Dev] Need help and suggestions for Unified dashboard work

[Dunith Dhanushka]

Hi Nashry,

Charts look appealing! good job on that.

Please find my answers inline.

On Wed, Sep 2, 2015 at 12:54 AM, Aaquibah Nashry  wrote:

> Hi Manu/Dunith,
>
> I am in the process of creating gadgets for the unified dashboard. I am
> using the wso2das-3.0.0-SNAPSHOT dashboard for this purpose. I have
> attached images of the current state of the gadgets i have created. Kindly
> shed light on the following 3 points.
>
>- I need guidance to do the following:
>
>
>1. Need to customize and format the gadget container (padding, etc...).
>
> I'm not quite how to do this in UES level. Perhaps Manu can shed some
light into that.

>
>1. Create a custom layout for the dashboard page
>
>
>- I am creating gadgets with graphs (with controls such as drop
>downs). I would like to know if the controls have to be included in the
>gadget itself or whether it should be placed as a separate gadget, or any
>other manner.
>
> AFAIK this can be achieved by using inter gadget communication currently
available with UES .2.0. You don't have to put those dropdowns in the same
gadgets, instead you can have them in a seperate gadget and enable two
gadgets to communicate with each other. Also you can consider creating your
own widgets for controls like dropdowns, texboxes etc. Please have a look
at default widgets available in the dashboard. That'll give you a headstart.

>
>-
>
>
>- I am using jaggery for database connectivity. I am unable to host
>the jaggery files in the shindig server. When i hosted the jaggery files
>separately i was able to get the data for the gadget graphs. Is it not
>possible to host jaggery files in the shindig server? Kindly provide
>alternatives if it is not.
>
> Why do you host your jaggery files inside Shindig? Shindig is not a
Jaggery runtime and it only provides container services for gadgets. So the
best option is to host your jaggery files seperatley and let your gadgets
to talk to them through AJAX. That is how gadgets that are generated using
Wizard fetch data from backend. Go through the main.js of a generated
gadget so that it'll give you an idea about this.

>
>-
>
> Thanks in advance
>
> Regards,
>
> M.R.Aaquibah Nashry
> *Intern, Engineering**| **WSO2, Inc.*
> Mobile : +94 773946123
> Tel  : +94 112662541
> Email : nas...@wso2.com 
>



-- 
Regards,

Dunith Dhanushka,
Senior Software Engineer
WSO2 Inc,

Mobile - +94 71 8615744
Blog - dunithd.wordpress.com 
Twitter - @dunithd 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Nayomi Dayarathne]

Hi ESB team,

I tested the kafka inbound endpoint in a esb cluster where there is one
manager and two worker nodes.

Below are the steps i did when testing the kafka inbound endpoint.

1. Start the zookeeper
2.Start the kafka server

Zookeeper and kafka server started in my local machine.

3.Create a kafka inbound endpoint in cluster

it gets deployed in all three nodes.

4.Then create a topic in kafka broker.


then, in one of the worker nodes i get the following error,

 ERROR {kafka.producer.SyncProducer} -  Producer connection to
localhost:9092 unsuccessful {kafka.producer.SyncProducer}
java.net.ConnectException: Connection refused
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Net.java:435)
at sun.nio.ch.Net.connect(Net.java:427)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
at
kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
at
kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)



the above message is throwing continuously by the worker node.

I assume this issue is related to some configurations of kafka server.

*Any ideas of solving this issue ?*





Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

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

Re: [Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Nayomi Dayarathne]

Hi all,

This issue is not related to the jira[1]  i have reported.

According to my understanding this is something related to kafka server.
Therefore i assumed this issue is not related to kafka inbound endpoint.


[1]https://wso2.org/jira/browse/ESBJAVA-4153

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

*nay...@wso2.com *

On Thu, Sep 3, 2015 at 9:32 PM, Chanaka Fernando  wrote:

> Viraj is looking into this.
>
> On Thu, Sep 3, 2015 at 9:24 PM, Nayomi Dayarathne  wrote:
>
>> Hi ESB team,
>>
>> I tested the kafka inbound endpoint in a esb cluster where there is one
>> manager and two worker nodes.
>>
>> Below are the steps i did when testing the kafka inbound endpoint.
>>
>> 1. Start the zookeeper
>> 2.Start the kafka server
>>
>> Zookeeper and kafka server started in my local machine.
>>
>> 3.Create a kafka inbound endpoint in cluster
>>
>> it gets deployed in all three nodes.
>>
>> 4.Then create a topic in kafka broker.
>>
>>
>> then, in one of the worker nodes i get the following error,
>>
>>  ERROR {kafka.producer.SyncProducer} -  Producer connection to
>> localhost:9092 unsuccessful {kafka.producer.SyncProducer}
>> java.net.ConnectException: Connection refused
>> at sun.nio.ch.Net.connect0(Native Method)
>> at sun.nio.ch.Net.connect(Net.java:435)
>> at sun.nio.ch.Net.connect(Net.java:427)
>> at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
>> at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
>> at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
>> at
>> kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
>> at
>> kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
>> at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
>> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
>> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
>> at
>> kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
>> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
>>
>>
>>
>> the above message is throwing continuously by the worker node.
>>
>> I assume this issue is related to some configurations of kafka server.
>>
>> *Any ideas of solving this issue ?*
>>
>>
>>
>>
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>
>
>
> --
> --
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
> Wordpress:http://chanakaudaya.wordpress.com
>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DAS] Configuring Cross Origin Resource Sharing in DAS

[Madawa Soysa]

Hi All,

I need to send JSON events from different domains to a DAS HTTP input
receiver. Since browsers does not allow cross origin scripting I user CORS
[1]  to send a
POST request to DAS input receiver. I get the following error when the
request is send.

XMLHttpRequest cannot load http://192.168.0.171:9763/endpoints/test. No
'Access-Control-Allow-Origin' header is present on the requested resource.

Even though the above error occurred, the events gets stored in the event
stream without a problem; but the client program do not get the 'success'
response. As I read at [2]
,
additional headers should be included in the server response. Is there a
way to configure this in DAS.

[1] - https://en.wikipedia.org/wiki/Cross-origin_resource_sharing
[2] -
http://stackoverflow.com/questions/10636611/how-does-access-control-allow-origin-header-work
-- 

*_**Madawa Soysa*

Undergraduate,

Department of Computer Science and Engineering,

University of Moratuwa.


Mobile: +94 71 461 6050 <%2B94%2075%20812%200726> | Email:
madawa...@cse.mrt.ac.lk
LinkedIn  | Twitter
 | Tumblr 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] Nginx extension is available in Private PaaS 4.1.0

[Imesh Gunaratne]

Great work Reka on fixing the SSL configuration!!

On Tue, Sep 1, 2015 at 3:17 PM, Reka Thirunavukkarasu  wrote:

> Please find the missing section as below:
>
> - Update /bin/nginx-extension.sh with below
> parameters
> -Dnginx.cert.path=/etc/nginx/ssl/server.cert
> -Dnginx.key.path=/etc/nginx/ssl/server.key
> -Dnginx.server.names.hash.bucket.size=128
> -Dconf.file.path=/etc/nginx/nginx.conf
>
> - Start /bin/nginx-extension.sh
>
> Extension will auto configure the nginx.conf with the members found from
> the Topology and it will start the nginx server.
>
> Thanks,
> Reka
>
>
> On Tue, Sep 1, 2015 at 3:13 PM, Reka Thirunavukkarasu 
> wrote:
>
>> Hi All,
>>
>> Nginx extension has been tested with SSL and made the necessary
>> configuration to be available with the default nginx extension. Please
>> follow below steps to configure nginx extension with PPaaS.
>>
>> - Install nginx with SSL module
>> - Build the niginx extension from [1].
>> - Deploy the built niginx extension
>> apache-stratos-nginx-extension-4.1.0-SNAPSHOT.zip to the machine where
>> nginx is installed to a preferred place
>> - unzip the extension
>> - Setup java
>> - Update /conf/jndi.properties with the activemq ip
>> which is used by PPaaS server
>> - Update /bin/nginx-extension.sh with below
>> parameters
>>
>>
>>
>> [1]
>> https://github.com/wso2/product-private-paas/tree/master/extensions/load-balancer/nginx-extension
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to call "IdentityApplicationManagementService" admin service as a tenant user

[Amila De Silva]

Hi,

If this is about calling *ApplicationManagementAdmin**Service *using MutualSSL,
then still this would be only available to admin users, isn't it. A similar
approach was attempted while trying to create SP for AM_Application, at the
time of Generating a key. The problem was, even mutual SSL allows user to
authenticate, since this is an admin service, users are failed at the
authorising step unless they are admin users.

On Thu, Sep 3, 2015 at 12:20 AM, Sanjeewa Malalgoda 
wrote:

> If you are trying to implement tenant SP creation for App manager then we
> can easily do it using mutual SSL with tenant user name.
> We have implemented something similar and we can share code with you soon.
>
> Thanks,
> sanjeewa.
>
> On Thu, Sep 3, 2015 at 12:13 AM, Lakshani Gamage 
> wrote:
>
>> Hi all,
>>
>> I want to call "*IdentityApplicationManagementService*" admin service as
>> a tenant user.
>>
>> I gave super tenant credentials to that stub and called  "
>> *createApplication*" method by changing tenant flow. But still the SP is
>> created in ST space.
>>
>> If you have any idea, how to call this Service as a tenant user, Please
>> share it.
>>
>> Thanks,
>> Lakshani
>>
>>
>>
>> --
>> Lakshani Gamage
>>
>> *Software Engineer*
>> Mobile : +94 (0) 71 5478184 <%2B94%20%280%29%20773%20451194>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM][Mediator] CNF while publishing APIs

[Amila De Silva]

The main problem here is APIMgtResponseHandler not being visible to synapse
bundle. Both the bundles involved here (synapse-core_2.1.3.wso2v7 and
org.wso2.carbon.apimgt.usage.publisher_1.3.0.SNAPSHOT) were in ACTIVE state
and org.wso2.carbon.apimgt.usage.publisher package was only exported by
usage.publisher bundle.
While comparing synapse-core bundle on previous version and the current
version, made the following observations on Import-Package section.

In 1.9.1


org.wso2.carbon.mediation.registry;
version="4.2.1"
*org.wso2.carbon.apimgt.usage.publisher;
version="1.2.0"*
*org.wso2.carbon.apimgt.gateway.handlers.common;
version="1.2.0"*
*org.wso2.carbon.apimgt.gateway.handlers.ext;
version="1.2.0"*
org.wso2.carbon.mediation.security.vault.xpath;
version="4.2.0"
org.wso2.carbon.mediation.initializer.handler;
version="4.2.3"
javax.activation; version="1.1.0"
org.wso2.eventing; version="0.0.0"
org.wso2.eventing.exceptions; version="0.0.0"
sun.misc; version="0.0.0"
javax.activation; version="[1.1.0,2.0.0)"
javax.activation; version="[1.1.0,2.0.0)"
javax.activation; version="1.1.0"
javax.xml.xquery; version="0.0.0"
net.sf.saxon.xqj; version="0.0.0"


In 1.10.0-SNAPSHOT


org.wso2.carbon.mediation.registry;
version="4.4.5"
*org.wso2.carbon.apimgt.gateway.handlers.common;
version="1.3.0.SNAPSHOT"*
*org.wso2.carbon.apimgt.gateway.handlers.ext;
version="1.3.0.SNAPSHOT"*
org.wso2.carbon.mediation.security.vault.xpath;
version="4.4.5"
org.wso2.carbon.mediation.initializer.handler;
version="4.4.5"
org.wso2.carbon.inbound.endpoint.persistence.service;
version="4.4.5"
com.rabbitmq.client; version="3.4.0"
javax.activation; version="1.1.0"
javax.servlet; version="3.0.0"
javax.servlet.http; version="3.0.0"
org.wso2.eventing; version="0.0.0"
org.wso2.eventing.exceptions; version="0.0.0"
sun.misc; version="0.0.0"
javax.activation; version="[1.1.0,2.0.0)"
javax.activation; version="[1.1.0,2.0.0)"
javax.activation; version="1.1.0"
net.sf.saxon.s9api; version="0.0.0"

In the previous version, *org.wso2.carbon.apimgt.usage.publisher *is
included as an import, but on the latest version this couldn't be seen. To
narrow down the issue, the new synapse_core bundle was deployed on 1.9.1
distribution. Even then *org.wso2.carbon.apimgt.usage.publisher *bundle,
could be seen under Import-Packages.


On Thu, Sep 3, 2015 at 6:08 PM, Madusanka Premaratne 
wrote:

> Hi Devs,
> I am getting following error after upgrading carbon kernel to 4.4.1 and
> synapse version to 2.1.3.wso2v7. As per my
> observations, APIMgtResponseHandler extends AbstractMediator. I checked the
> bundles from osgi console and there are no errors. Please note that all the
> dynamic imports has been removed from all the the particular bundle.
>
> Can someone point me what could be the issue/ where did I go wrong?
>
> The error is,
>
> java.lang.ClassNotFoundException:
> org.wso2.carbon.apimgt.usage.publisher.APIMgtResponseHandler cannot be
> found by synapse-core_2.1.3.wso2v7
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at
> org.apache.synapse.config.xml.ClassMediatorFactory.createSpecificMediator(ClassMediatorFactory.java:102)
> at
> org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:94)
> at
> org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:224)
> at
> org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:46)
> at
> org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:70)
> at
> org.apache.synapse.config.xml.rest.ResourceFactory.configureSequences(ResourceFactory.java:119)
> at
> org.apache.synapse.config.xml.rest.ResourceFactory.createResource(ResourceFactory.java:50)
> at
> org.apache.synapse.config.xml.rest.APIFactory.createAPI(APIFactory.java:86)
> at
> org.apache.synapse.config.xml.rest.APIFactory.createAPI(APIFactory.java:51)
> at
> org.wso2.carbon.rest.api.service.RestApiAdmin.addApi(RestApiAdmin.java:662)
> at
> org.wso2.carbon.rest.api.service.RestApiAdmin.addApiFromString(RestApiAdmin.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> 

[Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

[Ravindra Ranwala]

Hi Devs,

WSO2 ESB 4.9.0 RC3 Release Vote

This release fixes the following issues:
https://wso2.org/jira/browse/ESBJAVA-4138?filter=12385

Please download ESB 4.9.0 RC3 and test the functionality and vote. Vote
will be open for 72 hours or as needed.

Source & binary distribution files:
http://maven.wso2.org/nexus/content/repositories/orgwso2esb-041/org/wso2/esb/wso2esb/4.9.0-RC3/

Maven staging repository:
http://maven.wso2.org/nexus/content/repositories/orgwso2esb-041/

The tag to be voted upon :
https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC3


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release


Thanks and Regards,
~ WSO2 ESB Team ~



-- 
Ravindra Ranwala
Software Engineer
WSO2, Inc: http://wso2.com

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

Re: [Dev] Need help and suggestions for Unified dashboard work

[Jonathan Marsh]

This looks really promising!  Sometime you will have to share your tips and
tricks with me.  I tried to do just this in UES, gadgets powered by jaggery
scripts, and could not get it to work because of permissions and failing to
find any guidance on where the .xml and .jag etc should each live.



A sample showing a gadget, backed up through ajax with a jaggery script,
which also has access to the gadget user’s role to filter information if
necessary, would be very helpful.



-Jonathan



*From:* Dunith Dhanushka [mailto:dun...@wso2.com]
*Sent:* Thursday, September 03, 2015 12:45 PM
*To:* Aaquibah Nashry
*Cc:* Manuranga Perera; Seshika Fernando; Srinath Perera; Shevan
Goonetilleke; WSO2 Developers' List; WSO2 Training Group
*Subject:* Re: Need help and suggestions for Unified dashboard work



Hi Nashry,



Charts look appealing! good job on that.



Please find my answers inline.



On Wed, Sep 2, 2015 at 12:54 AM, Aaquibah Nashry  wrote:

Hi Manu/Dunith,

I am in the process of creating gadgets for the unified dashboard. I am
using the wso2das-3.0.0-SNAPSHOT dashboard for this purpose. I have
attached images of the current state of the gadgets i have created. Kindly
shed light on the following 3 points.

   - I need guidance to do the following:


   1. Need to customize and format the gadget container (padding, etc...).

I'm not quite how to do this in UES level. Perhaps Manu can shed some light
into that.


   1. Create a custom layout for the dashboard page


   - I am creating gadgets with graphs (with controls such as drop downs).
   I would like to know if the controls have to be included in the gadget
   itself or whether it should be placed as a separate gadget, or any other
   manner.

AFAIK this can be achieved by using inter gadget communication currently
available with UES .2.0. You don't have to put those dropdowns in the same
gadgets, instead you can have them in a seperate gadget and enable two
gadgets to communicate with each other. Also you can consider creating your
own widgets for controls like dropdowns, texboxes etc. Please have a look
at default widgets available in the dashboard. That'll give you a headstart.


   -


   - I am using jaggery for database connectivity. I am unable to host the
   jaggery files in the shindig server. When i hosted the jaggery files
   separately i was able to get the data for the gadget graphs. Is it not
   possible to host jaggery files in the shindig server? Kindly provide
   alternatives if it is not.

Why do you host your jaggery files inside Shindig? Shindig is not a Jaggery
runtime and it only provides container services for gadgets. So the best
option is to host your jaggery files seperatley and let your gadgets to
talk to them through AJAX. That is how gadgets that are generated using
Wizard fetch data from backend. Go through the main.js of a generated
gadget so that it'll give you an idea about this.


   -

Thanks in advance

Regards,

M.R.Aaquibah Nashry

*Intern, Engineering**| **WSO2, Inc.*

Mobile : +94 773946123

Tel  : +94 112662541

Email : nas...@wso2.com 





-- 

Regards,

Dunith Dhanushka,

Senior Software Engineer

WSO2 Inc,



Mobile - +94 71 8615744

Blog - dunithd.wordpress.com 

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

Re: [Dev] [DAS] Configuring Cross Origin Resource Sharing in DAS

[Gimantha Bandara]

Hi Madawa,

Can you please try to follow [1] and see if the issue can be fixed? This
will apply the CORS settings for the whole tomcat container.

[1]
https://docs.wso2.com/display/DAS300/CORS+Settings+for+the+Analytics+REST+API

On Thu, Sep 3, 2015 at 1:00 PM, Madawa Soysa 
wrote:

> Hi All,
>
> I need to send JSON events from different domains to a DAS HTTP input
> receiver. Since browsers does not allow cross origin scripting I user CORS
> [1]  to send
> a POST request to DAS input receiver. I get the following error when the
> request is send.
>
> XMLHttpRequest cannot load http://192.168.0.171:9763/endpoints/test. No
> 'Access-Control-Allow-Origin' header is present on the requested resource.
>
> Even though the above error occurred, the events gets stored in the event
> stream without a problem; but the client program do not get the 'success'
> response. As I read at [2]
> ,
> additional headers should be included in the server response. Is there a
> way to configure this in DAS.
>
> [1] - https://en.wikipedia.org/wiki/Cross-origin_resource_sharing
> [2] -
> http://stackoverflow.com/questions/10636611/how-does-access-control-allow-origin-header-work
> --
>
> *_**Madawa Soysa*
>
> Undergraduate,
>
> Department of Computer Science and Engineering,
>
> University of Moratuwa.
>
>
> Mobile: +94 71 461 6050 <%2B94%2075%20812%200726> | Email:
> madawa...@cse.mrt.ac.lk
> LinkedIn  | Twitter
>  | Tumblr 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Need to check whether IP address ranges works with C5 clustering

[Kishanthan Thangarajah]

ACK.

@Aruna, can we do this as part of the clustering testing effort? For the
moment, lets test this manually.

On Mon, Aug 24, 2015 at 6:57 PM, Afkham Azeez  wrote:

> $subject
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need to check whether IP address ranges works with C5 clustering

[Aruna Karunarathna]

On Thu, Sep 3, 2015 at 11:33 AM, Kishanthan Thangarajah  wrote:

> ACK.
>
> @Aruna, can we do this as part of the clustering testing effort? For the
> moment, lets test this manually.
>

Sure will test this.

>
> On Mon, Aug 24, 2015 at 6:57 PM, Afkham Azeez  wrote:
>
>> $subject
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Associate Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] API-M VM/Docker Cartridge

[Vishanth Balasubramaniam]

Hi Pubudu,

The path to the dockerfile in [1] is incorrect. It should be corrected to
https://github.com/wso2/product-private-paas/blob/master/cartridges/docker/wso2am-1.9.0

[1] - https://hub.docker.com/r/wso2/am/

Regards,
Vishanth

On Wed, Sep 2, 2015 at 6:55 PM, Pubudu Gunatilaka  wrote:

> Hi Imesh,
>
> Will update API-Manager to 1.9.1 for the Private-Paas 4.1.0-GA. Now the
> API-Manager 1.9.0 docker image is available in docker hub[1].
>
> [1] - https://hub.docker.com/r/wso2/am/
>
> Thank you!
>
> On Mon, Aug 31, 2015 at 1:06 PM, Imesh Gunaratne  wrote:
>
>> Hi Devs,
>>
>> API-M has released 1.9.1 [1]. We might need to use this for Private PaaS
>> 4.1.0-GA
>> [1] http://wso2.com/api-management/try-it/
>>
>> Thanks
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
>
> *Pubudu Gunatilaka*
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 77 4078049
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94771737718*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS][IS] Admin console stuck with bpel/human task deployment

[Harsha Thirimanna]

Hi Nandika,

I tested this with your new bpel package and it was successfully deployed
withing short time and not an any blocker anymore. Thanks for your quick
solution.




*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
* *
*email: **hars...@wso2.com* * cell: +94 71 5186770 *
*twitter: **http://twitter.com/ *
*harshathirimannlinked-in: **http:
**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
*

*Lean . Enterprise . Middleware*


On Wed, Sep 2, 2015 at 6:11 PM, Harsha Thirimanna  wrote:

> Hi Nandika,
>
> Thanks for this quick solution and I will check this and reply.
>
> thanks
>
>
>
> *Harsha Thirimanna*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> * *
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ *
> *harshathirimannlinked-in: **http:
> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> *
>
> *Lean . Enterprise . Middleware*
>
>
> On Wed, Sep 2, 2015 at 6:07 PM, Nandika Jayawardana 
> wrote:
>
>> Hi Harsha,
>>
>> Can you try with the attached bpel. There was an unwanted namespace in
>> the xsd and removing it reduced the deployment time from 77 seconds to 1
>> second in bps.
>>
>> Regards
>> Nandika
>>
>> On Wed, Sep 2, 2015 at 5:47 PM, Vinod Kavinda  wrote:
>>
>>> Hi Harsha,
>>> Why are you deploying two bpel packages. Our purpose of using a
>>> generalized bpel process is to reuse it right? So why can't you use several
>>> instances of the same process?
>>>
>>> Please explain.
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Wed, Sep 2, 2015 at 4:58 PM, Waruna De Silva 
>>> wrote:
>>>
 Thanks Nandika for the update. Hope this will get sorted before the
 beta dates.

 Regards!
 Waruna

 On Wed, Sep 2, 2015 at 4:45 PM, Nandika Jayawardana 
 wrote:

> Hi Waruna,
>
> We are checking this issue. It is strange that UI get blocked as
> deployment happens independent of ui threads .
>
> Regards
> Nandika
>
> On Wed, Sep 2, 2015 at 1:59 PM, Waruna De Silva 
> wrote:
>
>> Hi Nandika,
>>
>> Do you have any update on this as this seems a blocker for the IS
>> 5.1.0 release? Appreciate if you can provide an ETA for a workaround or 
>> the
>> permanent fix.
>>
>> Regards!
>> Waruna
>>
>> On Tue, Sep 1, 2015 at 11:48 AM, Harsha Thirimanna 
>> wrote:
>>
>>> Hi Nandika,
>>>
>>> Since IS(with BPEL/HT features) server stuck for more than 15min if
>>> we deploy only two bpel and we can experience that in BPS as well. We 
>>> are
>>> bit stuck with this for this release as well. Are there any way to avoid
>>> this until we get proper solution ? Please advice us.
>>>
>>> thanks
>>>
>>>
>>>
>>> *Harsha Thirimanna*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> * *
>>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>>> *twitter: **http://twitter.com/ *
>>> *harshathirimannlinked-in: **http:
>>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Wed, Aug 26, 2015 at 5:57 PM, Harsha Thirimanna >> > wrote:
>>>
 Hi Nandika,

 As We discussed, I have created a Jira [1] for this. It is better
 if we can get fix for this before our release on next month  :).

 And thanks for your help to solve other issues and everything are
 working fine now except the  above issue.

 [1] https://wso2.org/jira/browse/BPS-818


 *Harsha Thirimanna*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 * *
 *email: **hars...@wso2.com* * cell: +94 71
 5186770 *
 *twitter: **http://twitter.com/ *
 *harshathirimannlinked-in: **http:
 **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
 *

 *Lean . Enterprise . Middleware*


 On Mon, Aug 24, 2015 at 2:44 PM, Harsha Thirimanna <
 hars...@wso2.com> wrote:

> Hi Vinod,

Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded

[Supun Malinga]

On Thu, Sep 3, 2015 at 12:24 PM, Nuwan Wimalasekara  wrote:

> Hi Manuri,
> There are some test classes which start a new server with a port offset
> and those port configuration are kept in automation.xml and referred by a
> name.
>

This is true Nuwan. But the concern is that in the test cases where we use
a offset. We have the offset hardcoded. Instead we need to read it from the
config file (automation.xml).
So what we thought is to put it as a property in the config of the
instances.
eg:


localhost


9764
9444

**
**
**


thanks,


>

> Ex: if the portOffset is 1, then the config is as bellow. Then the test
> class refer the post and hot config by referring the name
> "appServerInstance0002" and generate the server URLs.
>
>  nonBlockingTransportEnabled="false">
> 
> localhost
> 
> 
> 9764
> 9444
> 
> 
>
> Now you have to increase the port offset in this classes to be 100 +
> portOffset and according to new port offset you have to change the
> configuration as well.
>
>  nonBlockingTransportEnabled="false">
> 
> localhost
> 
> 
> 9864
> 9544
> 
> 
>
> Thanks,
> Nuwanw
>
> On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera 
> wrote:
>
>> Adding Dev
>>
>> On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi,
>>>
>>> At the moment, in automation.xml in test modules, the -DportOffset
>>> parameter has been set to 100 and the port values in relevant instances
>>> also have been changed accordingly.
>>>
>>> But in the test cases where internally a server is set up, the port
>>> offset values are being hard coded. These values also need to be moved
>>> forward by 100. A configuration can be added to automation.xml which can be
>>> read and used to do this.
>>>
>>> I'd like to discuss the best way to address this problem.
>>>
>>> Thank you.
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [App Cloud] AF Datasource API takes a long time to respond

[Kavith Lokuhewage]

Hi all,

While testing DevStudio with latest app cloud, I could notice that
following API  takes a very long time to respond.

API :
https://apps.cloud.wso2.com/appmgt/site/blocks/resources/datasource/get/ajax/list.jag?action=getDatasources=testapplicationone


This is invoked (along with three other APIs) once a user opens an
application from AF Application List View in DevStudio. However, due to
this application open doesn't work smoothly.

Just wanted to know whether this is something temporary. FYI, this was not
experienced in previous testing round with App Cloud ( old version).

Thanks,

*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

Re: [Dev] [Private PaaS] API-M VM/Docker Cartridge

[Pubudu Gunatilaka]

Hi Vishanth,

Thank you for correcting that.

On Thu, Sep 3, 2015 at 12:58 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:

> Hi,
>
> I corrected the URL.
>
> Regards,
> Vishanth
>
> On Thu, Sep 3, 2015 at 11:42 AM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> The path to the dockerfile in [1] is incorrect. It should be corrected to
>>
>> https://github.com/wso2/product-private-paas/blob/master/cartridges/docker/wso2am-1.9.0
>>
>> [1] - https://hub.docker.com/r/wso2/am/
>>
>> Regards,
>> Vishanth
>>
>> On Wed, Sep 2, 2015 at 6:55 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> Will update API-Manager to 1.9.1 for the Private-Paas 4.1.0-GA. Now the
>>> API-Manager 1.9.0 docker image is available in docker hub[1].
>>>
>>> [1] - https://hub.docker.com/r/wso2/am/
>>>
>>> Thank you!
>>>
>>> On Mon, Aug 31, 2015 at 1:06 PM, Imesh Gunaratne  wrote:
>>>
 Hi Devs,

 API-M has released 1.9.1 [1]. We might need to use this for Private
 PaaS 4.1.0-GA
 [1] http://wso2.com/api-management/try-it/

 Thanks

 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware


>>>
>>>
>>> --
>>>
>>> *Pubudu Gunatilaka*
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>> mobile:  +94 77 4078049
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94771737718*
>> about me: *http://about.me/vishanth *
>>
>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94771737718*
> about me: *http://about.me/vishanth *
>



-- 

*Pubudu Gunatilaka*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 77 4078049
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded

[Nuwan Wimalasekara]

Hi Manuri,
There are some test classes which start a new server with a port offset and
those port configuration are kept in automation.xml and referred by a name.

Ex: if the portOffset is 1, then the config is as bellow. Then the test
class refer the post and hot config by referring the name
"appServerInstance0002" and generate the server URLs.



localhost


9764
9444



Now you have to increase the port offset in this classes to be 100 +
portOffset and according to new port offset you have to change the
configuration as well.



localhost


9864
9544



Thanks,
Nuwanw

On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera 
wrote:

> Adding Dev
>
> On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera 
> wrote:
>
>> Hi,
>>
>> At the moment, in automation.xml in test modules, the -DportOffset
>> parameter has been set to 100 and the port values in relevant instances
>> also have been changed accordingly.
>>
>> But in the test cases where internally a server is set up, the port
>> offset values are being hard coded. These values also need to be moved
>> forward by 100. A configuration can be added to automation.xml which can be
>> read and used to do this.
>>
>> I'd like to discuss the best way to address this problem.
>>
>> Thank you.
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded

[Nuwan Wimalasekara]

HI Supun,


On Thu, Sep 3, 2015 at 12:29 PM, Supun Malinga  wrote:

>
>
> On Thu, Sep 3, 2015 at 12:24 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Manuri,
>> There are some test classes which start a new server with a port offset
>> and those port configuration are kept in automation.xml and referred by a
>> name.
>>
>
> This is true Nuwan. But the concern is that in the test cases where we use
> a offset. We have the offset hardcoded. Instead we need to read it from the
> config file (automation.xml).
> So what we thought is to put it as a property in the config of the
> instances.
> eg:
>  nonBlockingTransportEnabled="false">
> 
> localhost
> 
> 
> 9764
> 9444
> 
> **
> **
> **
> 
>
+1. This is better approach.  Then we can read the offset from the config
property and set

Thanks,
Nuwanw

>
> thanks,
>
>
>>
>
>> Ex: if the portOffset is 1, then the config is as bellow. Then the test
>> class refer the post and hot config by referring the name
>> "appServerInstance0002" and generate the server URLs.
>>
>> > nonBlockingTransportEnabled="false">
>> 
>> localhost
>> 
>> 
>> 9764
>> 9444
>> 
>> 
>>
>> Now you have to increase the port offset in this classes to be 100 +
>> portOffset and according to new port offset you have to change the
>> configuration as well.
>>
>> > nonBlockingTransportEnabled="false">
>> 
>> localhost
>> 
>> 
>> 9864
>> 9544
>> 
>> 
>>
>> Thanks,
>> Nuwanw
>>
>> On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Adding Dev
>>>
>>> On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera 
>>> wrote:
>>>
 Hi,

 At the moment, in automation.xml in test modules, the -DportOffset
 parameter has been set to 100 and the port values in relevant instances
 also have been changed accordingly.

 But in the test cases where internally a server is set up, the port
 offset values are being hard coded. These values also need to be moved
 forward by 100. A configuration can be added to automation.xml which can be
 read and used to do this.

 I'd like to discuss the best way to address this problem.

 Thank you.

 --

 *Manuri Amaya Perera*

 *Software Engineer*

 *WSO2 Inc.*

 *Blog: http://manuriamayaperera.blogspot.com
 *

>>>
>>>
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
> Supun Malinga,
>
> Senior Software Engineer,
> WSO2 Inc.
> http://wso2.com
> email: sup...@wso2.com 
> mobile: +94 (0)71 56 91 321
>



-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OAuth Flow - Persisting configuration parameters in WSO2 ESB Registry and reading/writing their values using Synapse

[Malaka Silva]

Hi Nadeeshaan,

I think we have provided this feature in esb 490.

Can you please send more details on this?

On Thu, Sep 3, 2015 at 9:29 AM, Asitha Nanayakkara  wrote:

> Hi Palamayuran,
>
> You can either write a class mediator[1] to do this or use the script
> mediator[2],
>
> Java code for saving and retrieving a String to/from registry is as follows
>
> Writing to registry
>
> String resourcePath = "conf/wsdl/myWSDL";
>> mc.getConfiguration().getRegistry().newResource(resourcePath, false);
>> mc.getConfiguration().getRegistry().updateResource(resourcePath,
>> mc.getProperty("MyProperty").toString().getBytes());
>
>
> Reading from registry
>
> Object resourceObj = mc.getConfiguration().getRegistry().getResource(new
>> Entry(resourcePath), new Properties());
>> if(resourceObj != null) {
>> mc.setProperty("MyProperty", ((OMTextImpl) resourceObj).getText());
>> }
>
>
> You can use something similar to following in Script mediator
>
> > importPackage(Packages.org.apache.synapse.config);
>> mc.getConfiguration().getRegistry().newResource("conf/wsdl/myWSDL
>> ",false);
>> mc.getConfiguration().getRegistry().updateResource("conf/wsdl/myWSDL
>> ", mc.getProperty("MyProperty").toString());
>> ]]>
>
>
> As far as I know writing to registry using the property mediators registry
> scope is supported from ESB 4.9.0.
>
> Hope this serves your purpose.
>
> [1] https://docs.wso2.com/display/ESB481/Class+Mediator
> [2] https://docs.wso2.com/display/ESB481/Script+Mediator
>
> Regards,
> Asitha
>
> On Wed, Sep 2, 2015 at 9:37 PM, Palamayuran 
> wrote:
>
>> *Hi Guys,*
>>
>> I'm trying to develop a component that implements OAuth flow to supplement
>> connectors that use the OAuth 2.0 for authentication.
>>
>> In order to accomplish the task I have a requirement where I have to
>> persist
>> certain API specific values (access token, refresh token etc) in the WSO2
>> ESB registry so that any subsequent calls can access them. Also when any
>> of
>> them expires/changes they have to be updated appropriately using synapse
>> code.
>>
>> Can someone please point out to me how to persist parameters (key/value
>> pairs) onto the WSO2 registry using synapse mediators to achieve the
>> above.
>>
>> *Thanks in Advance,*
>> Palamayuran
>>
>>
>>
>> --
>> View this message in context:
>> http://wso2-oxygen-tank.10903.n7.nabble.com/OAuth-Flow-Persisting-configuration-parameters-in-WSO2-ESB-Registry-and-reading-writing-their-valuese-tp124630.html
>> Sent from the WSO2 Development mailing list archive at Nabble.com.
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> *Asitha Nanayakkara*
> Software Engineer
> WSO2, Inc. http://wso2.com/
> Mob: + 94 77 85 30 682
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/


Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] API-M VM/Docker Cartridge

[Vishanth Balasubramaniam]

Hi,

I corrected the URL.

Regards,
Vishanth

On Thu, Sep 3, 2015 at 11:42 AM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:

> Hi Pubudu,
>
> The path to the dockerfile in [1] is incorrect. It should be corrected to
>
> https://github.com/wso2/product-private-paas/blob/master/cartridges/docker/wso2am-1.9.0
>
> [1] - https://hub.docker.com/r/wso2/am/
>
> Regards,
> Vishanth
>
> On Wed, Sep 2, 2015 at 6:55 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Imesh,
>>
>> Will update API-Manager to 1.9.1 for the Private-Paas 4.1.0-GA. Now the
>> API-Manager 1.9.0 docker image is available in docker hub[1].
>>
>> [1] - https://hub.docker.com/r/wso2/am/
>>
>> Thank you!
>>
>> On Mon, Aug 31, 2015 at 1:06 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Devs,
>>>
>>> API-M has released 1.9.1 [1]. We might need to use this for Private PaaS
>>> 4.1.0-GA
>>> [1] http://wso2.com/api-management/try-it/
>>>
>>> Thanks
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>>
>> *Pubudu Gunatilaka*
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> mobile:  +94 77 4078049
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94771737718*
> about me: *http://about.me/vishanth *
>



-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94771737718*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded

[Manuri Amaya Perera]

Adding Dev

On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera 
wrote:

> Hi,
>
> At the moment, in automation.xml in test modules, the -DportOffset
> parameter has been set to 100 and the port values in relevant instances
> also have been changed accordingly.
>
> But in the test cases where internally a server is set up, the port offset
> values are being hard coded. These values also need to be moved forward by
> 100. A configuration can be added to automation.xml which can be read and
> used to do this.
>
> I'd like to discuss the best way to address this problem.
>
> Thank you.
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM][DAS]Error in Installing DAS Feature

[Sachith Punchihewa]

Hi Gokul,

EMM's Carbon version is 4.4.0.I tried changing the Carbon version to
4.4.1.Still it gives an error.the error and the log is given below.
Is there any other required features or version i need to install before
installing the above DAS feature?

Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - Analytics Lite Feature
> 1.0.3.SNAPSHOT (org.wso2.carbon.analytics.lite.feature.group 1.0.3.SNAPSHOT)
>  Missing requirement: WSO2 Carbon - Analytics Core Server Feature
> 1.0.3.SNAPSHOT (org.wso2.carbon.analytics.core.server.feature.group
> 1.0.3.SNAPSHOT) requires 'org.wso2.carbon.ntask.core.feature.group
> [4.4.4,4.5.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Analytics Lite Feature 1.0.3.SNAPSHOT
> (org.wso2.carbon.analytics.lite.feature.group 1.0.3.SNAPSHOT)
>   To: org.wso2.carbon.analytics.core.server.feature.group [1.0.3.SNAPSHOT]
> Application failed,



[ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen
> (3-p2-profile-generation) on project wso2mdm-profile-gen: P2 publisher
> return code was 13 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :wso2mdm-profile-gen



Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Wed, Sep 2, 2015 at 6:51 PM, Gokul Balakrishnan  wrote:

> Hi Sachith,
>
> You do not need to build carbon-analytics locally, since Jenkins artefact
> builds are cached on Nexus. In any case, your second entry appears correct,
> however the issue seems to be a mismatch in Carbon versions. Can you please
> check EMM's Carbon version? Since DAS features are on 4.4.1, Carbon 4.4.1
> or greater is required.
>
> Thanks,
>
> On 2 September 2015 at 18:40, Sachith Punchihewa 
> wrote:
>
>> Hi DAS Team,
>>
>> I tried installing *WSO2 Carbon - Analytics Lite Feature* to EMM using
>> the following entries in P2 Profile Gen Pom.
>>
>>> 
>>> org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
>>> 
>>
>> and
>>
>> 
>>> analytics-lite-feature.group
>>> 1.0.3-SNAPSHOT
>>> 
>>
>>
>> When i use above entries  it gives the following error.
>>
>> [INFO] --- carbon-p2-plugin:1.5.4:p2-repo-gen (2-p2-repo-generation) @
>>> wso2mdm-profile-gen ---
>>> [ERROR] Error occured when processing the Feature Artifact:
>>> org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
>>> org.apache.maven.plugin.MojoExecutionException: Error occured when
>>> processing the Feature Artifact:
>>> org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.getProcessedFeatureArtifacts(RepositoryGenMojo.java:322)
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:197)
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at 

Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded

[Manuri Amaya Perera]

Hi Nuwan,

In this case shifting the values in automation.xml would suffice but where
offsets are hard coded we have to look for some other solution right?

On Thu, Sep 3, 2015 at 12:24 PM, Nuwan Wimalasekara  wrote:

> Hi Manuri,
> There are some test classes which start a new server with a port offset
> and those port configuration are kept in automation.xml and referred by a
> name.
>
> Ex: if the portOffset is 1, then the config is as bellow. Then the test
> class refer the post and hot config by referring the name
> "appServerInstance0002" and generate the server URLs.
>
>  nonBlockingTransportEnabled="false">
> 
> localhost
> 
> 
> 9764
> 9444
> 
> 
>
> Now you have to increase the port offset in this classes to be 100 +
> portOffset and according to new port offset you have to change the
> configuration as well.
>
>  nonBlockingTransportEnabled="false">
> 
> localhost
> 
> 
> 9864
> 9544
> 
> 
>
> Thanks,
> Nuwanw
>
> On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera 
> wrote:
>
>> Adding Dev
>>
>> On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi,
>>>
>>> At the moment, in automation.xml in test modules, the -DportOffset
>>> parameter has been set to 100 and the port values in relevant instances
>>> also have been changed accordingly.
>>>
>>> But in the test cases where internally a server is set up, the port
>>> offset values are being hard coded. These values also need to be moved
>>> forward by 100. A configuration can be added to automation.xml which can be
>>> read and used to do this.
>>>
>>> I'd like to discuss the best way to address this problem.
>>>
>>> Thank you.
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Cloud] AF Datasource API takes a long time to respond

[Mahesh Chinthaka]

Hi Kavith,

I had a quick run through this rest API and the flow. We haven't done any
modifications /code changes with our latest release.
Anyway I will check this and get back to you.

Thanks

On Thu, Sep 3, 2015 at 12:58 PM, Kavith Lokuhewage  wrote:

> Hi all,
>
> While testing DevStudio with latest app cloud, I could notice that
> following API  takes a very long time to respond.
>
> API :
> https://apps.cloud.wso2.com/appmgt/site/blocks/resources/datasource/get/ajax/list.jag?action=getDatasources=testapplicationone
> 
>
> This is invoked (along with three other APIs) once a user opens an
> application from AF Application List View in DevStudio. However, due to
> this application open doesn't work smoothly.
>
> Just wanted to know whether this is something temporary. FYI, this was not
> experienced in previous testing round with App Cloud ( old version).
>
> Thanks,
>
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Mahesh Chinthaka Vidanagama* | Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 63 63 083 | Work: +94 112 145 345
Email: mahe...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Using OSGi annotations from kernel 4.5.0 onwards

[Kishanthan Thangarajah]

We are already using this for C5. But IMO, we need to do the same for any
new kernel releases from now onwards (4.4.2 ?). It does not have to be
strictly for kernel releases, but can be followed for any new component
repo releases. An effort has to be put on to convert the java tag based
service components. I wrote blog on how to use annotations sometime back
[1].

The reason is the current java tag based scr descriptions is very old and
deprecated. Even scr plugin has removed this support after 1.8 version
(2012).

Advantages on moving to annotations are :

1. Bundle plugin it self can be used to process the annotations. We do not
need scr plugin anymore.
2. The change is required only for compile time as the runtime only looks
for component.xml file. This file will be generated by the bundle plugin
during compile time.

Thoughts?

Thanks,
Kishanthan.
[1]
https://kishanthan.wordpress.com/2014/03/29/using-annotation-with-osgi-declarative-services/

-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM][DAS]Error in Installing DAS Feature

[Gokul Balakrishnan]

Sure Anjana. @Sachith, for the time being, you can specify the ntask
feature manually in the EMM P2 profile and try.

Thanks,

On 3 September 2015 at 12:42, Anjana Fernando  wrote:

> Hi Gokul,
>
> I guess, the ntask feature is not mentioend as a required import feature
> in the analytics-core feature, can we get that added.
>
> Cheers,
> Anjana.
>
> On Thu, Sep 3, 2015 at 12:15 PM, Sachith Punchihewa 
> wrote:
>
>> Hi Gokul,
>>
>> EMM's Carbon version is 4.4.0.I tried changing the Carbon version to
>> 4.4.1.Still it gives an error.the error and the log is given below.
>> Is there any other required features or version i need to install before
>> installing the above DAS feature?
>>
>> Installation failed.
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Analytics Lite Feature
>>> 1.0.3.SNAPSHOT (org.wso2.carbon.analytics.lite.feature.group 1.0.3.SNAPSHOT)
>>>  Missing requirement: WSO2 Carbon - Analytics Core Server Feature
>>> 1.0.3.SNAPSHOT (org.wso2.carbon.analytics.core.server.feature.group
>>> 1.0.3.SNAPSHOT) requires 'org.wso2.carbon.ntask.core.feature.group
>>> [4.4.4,4.5.0)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Analytics Lite Feature 1.0.3.SNAPSHOT
>>> (org.wso2.carbon.analytics.lite.feature.group 1.0.3.SNAPSHOT)
>>>   To: org.wso2.carbon.analytics.core.server.feature.group
>>> [1.0.3.SNAPSHOT]
>>> Application failed,
>>
>>
>>
>> [ERROR] Failed to execute goal
>>> org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen
>>> (3-p2-profile-generation) on project wso2mdm-profile-gen: P2 publisher
>>> return code was 13 -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR]   mvn  -rf :wso2mdm-profile-gen
>>
>>
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> On Wed, Sep 2, 2015 at 6:51 PM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi Sachith,
>>>
>>> You do not need to build carbon-analytics locally, since Jenkins
>>> artefact builds are cached on Nexus. In any case, your second entry appears
>>> correct, however the issue seems to be a mismatch in Carbon versions. Can
>>> you please check EMM's Carbon version? Since DAS features are on 4.4.1,
>>> Carbon 4.4.1 or greater is required.
>>>
>>> Thanks,
>>>
>>> On 2 September 2015 at 18:40, Sachith Punchihewa 
>>> wrote:
>>>
 Hi DAS Team,

 I tried installing *WSO2 Carbon - Analytics Lite Feature* to EMM using
 the following entries in P2 Profile Gen Pom.

> 
> org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
> 

 and

 
> analytics-lite-feature.group
> 1.0.3-SNAPSHOT
> 


 When i use above entries  it gives the following error.

 [INFO] --- carbon-p2-plugin:1.5.4:p2-repo-gen (2-p2-repo-generation) @
> wso2mdm-profile-gen ---
> [ERROR] Error occured when processing the Feature Artifact:
> org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
> org.apache.maven.plugin.MojoExecutionException: Error occured when
> processing the Feature Artifact:
> org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
> at
> org.wso2.maven.p2.RepositoryGenMojo.getProcessedFeatureArtifacts(RepositoryGenMojo.java:322)
> at
> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:197)
> at
> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> 

Re: [Dev] Discussion about DAS Analytics Dashboard

[Thanuja Uruththirakodeeswaran]

Hi Dunith,

Thanks for the update. What I need is when I navigate to this dashboard
page, a particular application_id(a) and cluster_id(c) will be passed and
by default 30 min time interval(t) will be selected. So I need to visualize
data corresponding to filter a,c and t in Line Chart Gadget which is
already added to the dashboard page. For that I need to query process store
db(mysql db) table using where clause with a,c,t and update data in Line
Chart Gadget.

The table I'm using for Line Chart Gadget contains columns: Time,
ApplicationId, ClusterId, CreatedMemberCount, InitializedmemberCount,
TerminatedMemberCount


​
So how can I connect to process store db/ send an API call to back end from
dashboard and update Gadget?
You are saying using a lucene query, we can filter data and generate
gadget. So can I use the same for update the gadget every time user try to
do filtering in UI?

Thanks.

On Wed, Sep 2, 2015 at 6:21 PM, Dunith Dhanushka  wrote:

> Hi Thanuja,
>
> I'm working on adding the Lucene based filtering facility to gadget
> generation wizard [1]. That will provide you a way of specifying a Lucene
> query during gadget generation so that you can filter out your input data
> table. I'm hoping to finish it within this week.
>
> But you might need to get help from UES team (if they are not busy with a
> release) for the gadget maximizing feature.
>
> [1] https://wso2.org/jira/browse/DAS-28
>
> Regards,
> Dunith
>
>
>
> On Tue, Sep 1, 2015 at 10:05 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi Dunith,
>>
>> Yes, I need filtering facility when generating a gadget to filter out the
>> records and I'm wondering where can I add queries for filtering and how can
>> I invoke the filtering logic from dashboard. I'll have a offline discussion
>> with Maninda, since as you said he is the one currently responsible for
>> dashboard side and let you know.
>>
>> Thanks.
>>
>> On Wed, Sep 2, 2015 at 12:12 AM, Dunith Dhanushka 
>> wrote:
>>
>>> Hi Thanuja,
>>>
>>> Can you explain the requirement for filtering a little bit further? What
>>> I understood is you need a filtering facility when generating a gadget  to
>>> filter out  the records for the visualization. (like having a where clause)
>>>
>>> Regards,
>>> Dunith
>>>
>>> On Tue, Sep 1, 2015 at 8:04 AM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 Hi Dunith,

 I'm implementing Metering dashboard for Stratos using DAS. You can find
 more details and dashboard UI design in the dev thread[1]. Currently I'm
 trying to create a line chart and table gadgets in dashboard and I need to
 do some filtering in dashboard. I tried with DAS samples and they don't
 have the filtering part. So I need to discuss and clarify about it. Also
 I've discussed about Table Gadget column order problem in thread [2] and
 need to clarify about that one also.

 [1]. [Dev] [PPaaS] Integrating DAS with Stratos for Metering Service
 and Monitoring Health Statistics
 [2]. [Dev] [DAS] DAS dashboard table-gadget column order

 Thanks.

 --
 Thanuja Uruththirakodeeswaran
 Software Engineer
 WSO2 Inc.;http://wso2.com
 lean.enterprise.middleware

 mobile: +94 774363167

>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Dunith Dhanushka,
>>> Senior Software Engineer
>>> WSO2 Inc,
>>>
>>> Mobile - +94 71 8615744
>>> Blog - dunithd.wordpress.com 
>>> Twitter - @dunithd 
>>>
>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> Regards,
>
> Dunith Dhanushka,
> Senior Software Engineer
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - dunithd.wordpress.com 
> Twitter - @dunithd 
>



-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded

[KasunG Gajasinghe]

Hi,

We can introduce a parameter, say, defaultPortOffset, in to the
automation.xml. This should be set to 100 in the case of AS. Then, the test
cases that need to spin up servers should set the port offset value as
"defaultPortOffset + X" where the X could range from 1-100.

On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera 
wrote:

> Adding Dev
>
> On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera 
> wrote:
>
>> Hi,
>>
>> At the moment, in automation.xml in test modules, the -DportOffset
>> parameter has been set to 100 and the port values in relevant instances
>> also have been changed accordingly.
>>
>> But in the test cases where internally a server is set up, the port
>> offset values are being hard coded. These values also need to be moved
>> forward by 100. A configuration can be added to automation.xml which can be
>> read and used to do this.
>>
>> I'd like to discuss the best way to address this problem.
>>
>> Thank you.
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM][DAS]Error in Installing DAS Feature

[Anjana Fernando]

Hi Gokul,

I guess, the ntask feature is not mentioend as a required import feature in
the analytics-core feature, can we get that added.

Cheers,
Anjana.

On Thu, Sep 3, 2015 at 12:15 PM, Sachith Punchihewa 
wrote:

> Hi Gokul,
>
> EMM's Carbon version is 4.4.0.I tried changing the Carbon version to
> 4.4.1.Still it gives an error.the error and the log is given below.
> Is there any other required features or version i need to install before
> installing the above DAS feature?
>
> Installation failed.
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Analytics Lite Feature
>> 1.0.3.SNAPSHOT (org.wso2.carbon.analytics.lite.feature.group 1.0.3.SNAPSHOT)
>>  Missing requirement: WSO2 Carbon - Analytics Core Server Feature
>> 1.0.3.SNAPSHOT (org.wso2.carbon.analytics.core.server.feature.group
>> 1.0.3.SNAPSHOT) requires 'org.wso2.carbon.ntask.core.feature.group
>> [4.4.4,4.5.0)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Analytics Lite Feature 1.0.3.SNAPSHOT
>> (org.wso2.carbon.analytics.lite.feature.group 1.0.3.SNAPSHOT)
>>   To: org.wso2.carbon.analytics.core.server.feature.group [1.0.3.SNAPSHOT]
>> Application failed,
>
>
>
> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen
>> (3-p2-profile-generation) on project wso2mdm-profile-gen: P2 publisher
>> return code was 13 -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf :wso2mdm-profile-gen
>
>
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> On Wed, Sep 2, 2015 at 6:51 PM, Gokul Balakrishnan  wrote:
>
>> Hi Sachith,
>>
>> You do not need to build carbon-analytics locally, since Jenkins artefact
>> builds are cached on Nexus. In any case, your second entry appears correct,
>> however the issue seems to be a mismatch in Carbon versions. Can you please
>> check EMM's Carbon version? Since DAS features are on 4.4.1, Carbon 4.4.1
>> or greater is required.
>>
>> Thanks,
>>
>> On 2 September 2015 at 18:40, Sachith Punchihewa 
>> wrote:
>>
>>> Hi DAS Team,
>>>
>>> I tried installing *WSO2 Carbon - Analytics Lite Feature* to EMM using
>>> the following entries in P2 Profile Gen Pom.
>>>
 
 org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
 
>>>
>>> and
>>>
>>> 
 analytics-lite-feature.group
 1.0.3-SNAPSHOT
 
>>>
>>>
>>> When i use above entries  it gives the following error.
>>>
>>> [INFO] --- carbon-p2-plugin:1.5.4:p2-repo-gen (2-p2-repo-generation) @
 wso2mdm-profile-gen ---
 [ERROR] Error occured when processing the Feature Artifact:
 org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
 org.apache.maven.plugin.MojoExecutionException: Error occured when
 processing the Feature Artifact:
 org.wso2.carbon.analytics:analytics-lite-feature:1.0.3-SNAPSHOT
 at
 org.wso2.maven.p2.RepositoryGenMojo.getProcessedFeatureArtifacts(RepositoryGenMojo.java:322)
 at
 org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:197)
 at
 org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
 at
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
 at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
 at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 at
 

Re: [Dev] Retrying faulty CApps

[Kishanthan Thangarajah]

+1, but there should be a limit for the number of retry right?

On Thu, Aug 27, 2015 at 9:23 AM, Afkham Azeez  wrote:

> Yes this can be done. What should happen perhaps is if deploying even one
> artifact in the capp fails, we need to undeploy all other artifacts in the
> capp that got successfully deployed & then try redeployment periodically.
> On Aug 24, 2015 11:41 AM, "Kasun Indrasiri"  wrote:
>
>> Hi,
>>
>> Is it possible to add this as a new feature at carbon level? I think when
>> a CApp deployment initially fails due to intermittent resources/databases
>> unavailability etc., it may be required to have a re-try mechanism for
>> re-deploying artifacts without user intervention.
>>
>> Thanks.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>


-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets

[Manuri Amaya Perera]

​​Hi Nuwan,

According to our offline discussion I set the carbon home system property
in CarbonServerWithReadWriteLdapUSerStoreExtension inside onExecutionStart
method. Now the problem in carbon home not being set is solved.

Now, when running the testcase these exceptions occur and build fails.

configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
 Time elapsed: 2,284.473 sec  <<< FAILURE!
org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
at
org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
at
org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
at
org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)

restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
 Time elapsed: 0.003 sec  <<< FAILURE!
java.lang.NullPointerException: null
at
org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)

I think these are authorization issues relevant to LDAP. Can you be of any
help regarding this ?

Thank you.


-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Error when execute "insert overwrite" query using CarbonJDBC

[Niranda Perera]

Hi,

this is fixed now. :-)

On Tue, Sep 1, 2015 at 10:19 AM, Rukshan Premathunga 
wrote:

> Yes Niranda.
>
> Thanks and Regards.
>
> On Tue, Sep 1, 2015 at 10:18 AM, Niranda Perera  wrote:
>
>> Hi Rukshan,
>>
>> Are you using a latest DAS pack?
>>
>> On Tue, Sep 1, 2015 at 9:49 AM, Rukshan Premathunga 
>> wrote:
>>
>>>
>>>
>>> On Tue, Sep 1, 2015 at 9:48 AM, Rukshan Premathunga 
>>> wrote:
>>>
 Hi Niranda,

 please find the attachment for stacktrace.

 Thanks and Regards.

 On Tue, Sep 1, 2015 at 9:45 AM, Niranda Perera 
 wrote:

> Hi Rukshan,
>
> Can you put the full stacktrace?
>
> Rgds
>
> On Tue, Sep 1, 2015, 09:44 Rukshan Premathunga 
> wrote:
>
>> Hi,
>>
>> i created two temp table as below.
>>
>> *create temporary table APIRequestSummaryData using CarbonJDBC
>> options (dataSource "WSO2_AM_STAT", tableName "API_REQUEST_SUMMARY");*
>>
>> *create temporary table APIRequestData USING CarbonAnalytics
>> OPTIONS(tableName "ORG_WSO2_APIMGT_STATISTICS_REQUEST"); *
>>
>> when i execute query,
>>
>> *insert overwrite table APIRequestSummaryData select query  *
>>
>> I get the following error.
>>
>> *org.apache.axis2.AxisFault: Can't DROP
>> 'API_REQUEST_SUMMARY_PARTITION_KEY'; check that column/key exists*
>>
>>
>> did anyone encounter this?
>>
>>
>> Thanks and Regards.
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>


 --
 Rukshan Chathuranga.
 Software Engineer.
 WSO2, Inc.

>>>
>>>
>>>
>>> --
>>> Rukshan Chathuranga.
>>> Software Engineer.
>>> WSO2, Inc.
>>>
>>
>>
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>



-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need to check whether IP address ranges works with C5 clustering

[Aruna Karunarathna]

I'am getting the following error with ip ranges testing. [1]

My IP is 10.100.5.41 and i gave the range as follows 10.100.5.30-41, but it
connects to a 10.100.5.42 node, and giving the following exception.
The exception may be because of hazelcast version mismatch. But as per the
IP range I've given it shouldn't connect to the 10.100.5.42 right?..

Any thoughts?..

[1].
[2015-09-03 17:42:46,335]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.31]:4001 is
added to the blacklist.
[2015-09-03 17:42:46,335]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.30]:4001 is
added to the blacklist.
[2015-09-03 17:42:46,337]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
10.100.5.39:4000. Reason: SocketException[No route to host to address /
10.100.5.39:4000]
[2015-09-03 17:42:46,337]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
10.100.5.39:4001. Reason: SocketException[No route to host to address /
10.100.5.39:4001]
[2015-09-03 17:42:46,337]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.39]:4000 is
added to the blacklist.
[2015-09-03 17:42:46,337]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.39]:4001 is
added to the blacklist.
[2015-09-03 17:42:46,339]  INFO
{com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
[wso2.carbon.domain] [3.5] Established socket connection between /
10.100.5.41:4000
[2015-09-03 17:42:46,341]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
10.100.5.38:4001. Reason: SocketException[No route to host to address /
10.100.5.38:4001]
[2015-09-03 17:42:46,341]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
10.100.5.38:4000. Reason: SocketException[No route to host to address /
10.100.5.38:4000]
[2015-09-03 17:42:46,341]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.38]:4001 is
added to the blacklist.
[2015-09-03 17:42:46,341]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.38]:4000 is
added to the blacklist.
[2015-09-03 17:42:46,342]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.41]:4001 is
removed from the blacklist.
[2015-09-03 17:42:47,320]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Connecting to /
10.100.5.42:4000, timeout: 0, bind-any: true
[2015-09-03 17:42:47,320]  WARN {com.hazelcast.cluster.ClusterService} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not create connection
to possible master Address[10.100.5.42]:4000
[2015-09-03 17:42:47,321]  WARN {com.hazelcast.cluster.ClusterService} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not create connection
to possible master Address[10.100.5.42]:4000
[2015-09-03 17:42:47,324]  INFO
{com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
[wso2.carbon.domain] [3.5] Established socket connection between /
10.100.5.41:38318
[2015-09-03 17:42:53,364]  INFO {com.hazelcast.nio.tcp.SocketAcceptor} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Accepting socket connection
from /10.100.5.42:37180
[2015-09-03 17:42:53,366]  INFO
{com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
[wso2.carbon.domain] [3.5] Established socket connection between /
10.100.5.41:4000
[2015-09-03 17:42:53,372]  INFO {com.hazelcast.cluster.ClusterService} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5]

Members [4] {
Member [10.100.5.42]:4000
Member [10.100.5.42]:4002
Member [10.100.5.41]:4001
Member [10.100.5.41]:4000 this
}

[2015-09-03 17:42:53,396] ERROR
{com.hazelcast.cache.impl.operation.PostJoinCacheOperation} -
 [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Service with name
'hz:impl:cacheService' not found!
com.hazelcast.core.HazelcastException: Service with name
'hz:impl:cacheService' not found!
at com.hazelcast.spi.Operation.getService(Operation.java:213)
at
com.hazelcast.cache.impl.operation.PostJoinCacheOperation.run(PostJoinCacheOperation.java:44)
at
com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:137)
at
com.hazelcast.spi.impl.operationexecutor.classic.ClassicOperationExecutor.runOnCallingThread(ClassicOperationExecutor.java:380)
at
com.hazelcast.spi.impl.operationservice.impl.OperationServiceImpl.runOperationOnCallingThread(OperationServiceImpl.java:252)
at
com.hazelcast.cluster.impl.operations.PostJoinOperation.run(PostJoinOperation.java:93)
at

[Dev] [ES] fault in validateRequiredFeilds method

[Lakshman Udayakantha]

I can see some value is assigning to *provider* field rather validating it
in *validateRequiredFeilds* method in publisher/modules/asset-api.js. This
happens in 2.3.4 code version.see below code in that method




*var provider = rxtManager.getProviderAttribute(type);if(provider &&
provider.length >1 &&
assetReq.hasOwnProperty('attributes')){assetReq.attributes[provider] =
user.username;}*

shouldn't this be changed to




*var provider = rxtManager.getProviderAttribute(type);if(provider &&
provider.length >1 &&
assetReq.hasOwnProperty('attributes')){validateRequiredFeild(provider,
assetReq);}*

WDYT?
Thanks
-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0711241005*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS][BPMN] Undeployment of BPMN packages

[Firzhan Naqash]

Hi All,

Currently we are having a requirement to support undeployment of BPMN
packages which are having corresponding both active and completed
instances. Therefore, before removing the BPMN package, these instances
should be cleaned from the database.
If the number of instances are quite high, it will take some considerable
amount of time to delete all the instances.


As a solution we decided to add another configuration value to restrict the
maximum number of instances before proceeding to remove the BPMN package.
Removal of the BPMN package is only allowed if the number of instances for
that package is less than the config value.

If the number of instances are greater than the defined maximum threshold
value, undeployment  operation will fail. In this case users have to clean
the existing instances by using the provided clean up scripts. Then again
they can try to undeploy the BPMN package.

Any thoughts or ideas are welcome

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

Re: [Dev] [ES] fault in validateRequiredFeilds method

[Ayesha Dissanayaka]

Hi Lakshman,

The value of provider in below line refers to the user who is adding the
particular asset.

*var provider = rxtManager.getProviderAttribute(type);*

The intended behavior is not allowing users to change that provider value
other than to the username value of the user who is trying to add the asset.
That is why above code overrides the provider value. Also, provider is a
required field at the time asset is added to the registry, but since we
already have the username of the user who is adding the asset we don't need
to make it mandatory in the user request.

It might be wrong to have this particular code snippet inside this validate
method, if so we can take that out.

Thanks!
-Ayesha



On Thu, Sep 3, 2015 at 5:17 PM, Lakshman Udayakantha 
wrote:

> I can see some value is assigning to *provider* field rather validating
> it in *validateRequiredFeilds* method in publisher/modules/asset-api.js.
> This happens in 2.3.4 code version.see below code in that method
>
>
>
>
> *var provider = rxtManager.getProviderAttribute(type);if(provider &&
> provider.length >1 &&
> assetReq.hasOwnProperty('attributes')){assetReq.attributes[provider] =
> user.username;}*
>
> shouldn't this be changed to
>
>
>
>
> *var provider = rxtManager.getProviderAttribute(type);if(provider &&
> provider.length >1 &&
> assetReq.hasOwnProperty('attributes')){validateRequiredFeild(provider,
> assetReq);}*
>
> WDYT?
> Thanks
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0711241005*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets

[Nuwan Wimalasekara]

Hi Manuri,

in ReadOnlyLDAPUserStoreManagerTestCase,  UserStoreManager configuration is
changed in user-mgt.xml for read only user store. user-mgt.xml is kept in
the artifacts/AS/configs/readonlyldap/user-mgt.xml and the LDAP url is hard
coded in this resource.

ldap://localhost:10389

Please change the URL as below since the server is starting with port
offset(100) now. Otherwise it will failed to start the server with read
only user store configuration

ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}

Thanks,
Nuwanw

On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera 
wrote:

> ​​Hi Nuwan,
>
> According to our offline discussion I set the carbon home system property
> in CarbonServerWithReadWriteLdapUSerStoreExtension inside onExecutionStart
> method. Now the problem in carbon home not being set is solved.
>
> Now, when running the testcase these exceptions occur and build fails.
>
> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>  Time elapsed: 2,284.473 sec  <<< FAILURE!
> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
> at
> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>
> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>  Time elapsed: 0.003 sec  <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>
> I think these are authorization issues relevant to LDAP. Can you be of any
> help regarding this ?
>
> Thank you.
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Malaka Silva]

Hi Kathees,

Seems like issue when configuring/starting server.

Can you help on this matter pls?

On Thu, Sep 3, 2015 at 9:48 PM, Nayomi Dayarathne  wrote:

> Hi all,
>
> This issue is not related to the jira[1]  i have reported.
>
> According to my understanding this is something related to kafka server.
> Therefore i assumed this issue is not related to kafka inbound endpoint.
>
>
> [1]https://wso2.org/jira/browse/ESBJAVA-4153
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>
> On Thu, Sep 3, 2015 at 9:32 PM, Chanaka Fernando 
> wrote:
>
>> Viraj is looking into this.
>>
>> On Thu, Sep 3, 2015 at 9:24 PM, Nayomi Dayarathne 
>> wrote:
>>
>>> Hi ESB team,
>>>
>>> I tested the kafka inbound endpoint in a esb cluster where there is one
>>> manager and two worker nodes.
>>>
>>> Below are the steps i did when testing the kafka inbound endpoint.
>>>
>>> 1. Start the zookeeper
>>> 2.Start the kafka server
>>>
>>> Zookeeper and kafka server started in my local machine.
>>>
>>> 3.Create a kafka inbound endpoint in cluster
>>>
>>> it gets deployed in all three nodes.
>>>
>>> 4.Then create a topic in kafka broker.
>>>
>>>
>>> then, in one of the worker nodes i get the following error,
>>>
>>>  ERROR {kafka.producer.SyncProducer} -  Producer connection to
>>> localhost:9092 unsuccessful {kafka.producer.SyncProducer}
>>> java.net.ConnectException: Connection refused
>>> at sun.nio.ch.Net.connect0(Native Method)
>>> at sun.nio.ch.Net.connect(Net.java:435)
>>> at sun.nio.ch.Net.connect(Net.java:427)
>>> at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
>>> at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
>>> at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
>>> at
>>> kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
>>> at
>>> kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
>>> at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
>>> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
>>> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
>>> at
>>> kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
>>> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
>>>
>>>
>>>
>>> the above message is throwing continuously by the worker node.
>>>
>>> I assume this issue is related to some configurations of kafka server.
>>>
>>> *Any ideas of solving this issue ?*
>>>
>>>
>>>
>>>
>>>
>>> Nayomi Dayarathne
>>>
>>> *Software Engineer-QA*
>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>>
>>> *nay...@wso2.com *
>>>
>>
>>
>>
>> --
>> --
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>> Wordpress:http://chanakaudaya.wordpress.com
>>
>>
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/


Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Private PaaS build fails with Stratos 412

[Imesh Gunaratne]

Do you still see this issue?

On Mon, Aug 31, 2015 at 6:19 PM, Udara Liyanage  wrote:

>
> HI,
>
> With the intention of getting the latest Stratos, I build Stratos from 41x
> branch and changed Stratos version in PP to 412 and build PP. However I get
> the following error. Seems it tries to install 412-SNAPSHOT of  RESTful
> admin services feature.
>
>
> Installing org.wso2.carbon.event.server.feature.group 4.2.1.
> Installing org.wso2.carbon.event.common.feature.group 4.2.0.
> Installing org.wso2.carbon.captcha.mgt.server.feature.group 4.2.0.
> Installing org.jaggeryjs.feature.group 0.0.0.0_9_0_ALPHA4_wso2v3.
> Installing caramel.feature.group 1.0.1.
> Installing org.wso2.store.feature.group 1.0.1.
> Installing org.wso2.carbon.idp.mgt.feature.group 4.2.3.
> Installing org.wso2.carbon.as.runtimes.cxf.feature.group 4.2.2.
> Installing org.wso2.carbon.user.mgt.feature.group 4.2.1.
> Installation failed.
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: Apache Stratos - RESTful admin services feature
> 4.1.2 (org.apache.stratos.rest.endpoint.feature.group 4.1.2)
>  Software currently installed: Apache Stratos - RESTful admin services
> feature 4.1.2.SNAPSHOT (org.apache.stratos.rest.endpoint.feature.group
> 4.1.2.SNAPSHOT)
>  Only one of the following can be installed at once:
>   Apache Stratos - RESTful admin services feature 4.1.2
> (org.apache.stratos.rest.endpoint.feature.jar 4.1.2)
>   Apache Stratos - RESTful admin services feature 4.1.2.SNAPSHOT
> (org.apache.stratos.rest.endpoint.feature.jar 4.1.2.SNAPSHOT)
>  Cannot satisfy dependency:
>   From: Apache Stratos - RESTful admin services feature 4.1.2
> (org.apache.stratos.rest.endpoint.feature.group 4.1.2)
>   To: org.apache.stratos.rest.endpoint.feature.jar [4.1.2]
>  Cannot satisfy dependency:
>   From: Apache Stratos - RESTful admin services feature 4.1.2.SNAPSHOT
> (org.apache.stratos.rest.endpoint.feature.group 4.1.2.SNAPSHOT)
>   To: org.apache.stratos.rest.endpoint.feature.jar [4.1.2.SNAPSHOT]
> Application failed, log file location:
> /home/udara/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1440999235703.log
>
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 PPaaS - Parent ... SUCCESS [
>  0.830 s]
> [INFO] WSO2 PPaaS - Cartridges ... SUCCESS [
>  0.025 s]
> [INFO] WSO2 PPaaS - Cartridges - Template Modules  SUCCESS [
>  0.021 s]
> [INFO] WSO2 PPaaS - WSO2 AM 1.9.0 Template Module  SUCCESS [
>  0.457 s]
> [INFO] WSO2 PPaaS - WSO2 AS 5.2.1 Template Module  SUCCESS [
>  0.074 s]
> [INFO] WSO2 PPaaS - WSO2 ESB 4.8.1 Template Module ... SUCCESS [
>  0.047 s]
> [INFO] WSO2 PPaaS - WSO2 IS 5.0.0 Template Module  SUCCESS [
>  0.050 s]
> [INFO] WSO2 PPaaS - Components ... SUCCESS [
>  0.021 s]
> [INFO] WSO2 PPaaS - Python Configurator .. SUCCESS [
>  0.082 s]
> [INFO] WSO2 PPaaS - Features . SUCCESS [
>  0.024 s]
> [INFO] WSO2 PPaaS - Products . SUCCESS [
>  0.020 s]
> [INFO] WSO2 PPaaS - Product .. SUCCESS [
>  0.018 s]
> [INFO] WSO2 PPaaS - Profile Generation ... FAILURE [
> 47.325 s]
> [INFO] WSO2 PPaaS - Product - Distribution ... SKIPPED
> [INFO] WSO2 Private PaaS - Integration Tests . SKIPPED
> [INFO] WSO2 PPaaS - Configurator - Product ... SKIPPED
> [INFO] WSO2 PPaaS - Extensions ... SKIPPED
> [INFO] WSO2 PPaaS - Carbon Extensions  SKIPPED
> [INFO] WSO2 PPaaS - Carbon Extensions - Membership Scheme  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 49.852 s
> [INFO] Finished at: 2015-08-31T11:04:01+05:30
> [INFO] Final Memory: 30M/424M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen (p2 profile generation
> for stratos manager) on project ppaas-p2-profile-gen: P2 publisher return
> code was 13 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf :ppaas-p2-profile-gen
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: 

Re: [Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Kathees Rajendram]

Hi Malaka.

I will have a look.

Thanks,
Kathees

On Fri, Sep 4, 2015 at 9:36 AM, Malaka Silva  wrote:

> Hi Kathees,
>
> Seems like issue when configuring/starting server.
>
> Can you help on this matter pls?
>
> On Thu, Sep 3, 2015 at 9:48 PM, Nayomi Dayarathne  wrote:
>
>> Hi all,
>>
>> This issue is not related to the jira[1]  i have reported.
>>
>> According to my understanding this is something related to kafka server.
>> Therefore i assumed this issue is not related to kafka inbound endpoint.
>>
>>
>> [1]https://wso2.org/jira/browse/ESBJAVA-4153
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>> On Thu, Sep 3, 2015 at 9:32 PM, Chanaka Fernando 
>> wrote:
>>
>>> Viraj is looking into this.
>>>
>>> On Thu, Sep 3, 2015 at 9:24 PM, Nayomi Dayarathne 
>>> wrote:
>>>
 Hi ESB team,

 I tested the kafka inbound endpoint in a esb cluster where there is one
 manager and two worker nodes.

 Below are the steps i did when testing the kafka inbound endpoint.

 1. Start the zookeeper
 2.Start the kafka server

 Zookeeper and kafka server started in my local machine.

 3.Create a kafka inbound endpoint in cluster

 it gets deployed in all three nodes.

 4.Then create a topic in kafka broker.


 then, in one of the worker nodes i get the following error,

  ERROR {kafka.producer.SyncProducer} -  Producer connection to
 localhost:9092 unsuccessful {kafka.producer.SyncProducer}
 java.net.ConnectException: Connection refused
 at sun.nio.ch.Net.connect0(Native Method)
 at sun.nio.ch.Net.connect(Net.java:435)
 at sun.nio.ch.Net.connect(Net.java:427)
 at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
 at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
 at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
 at
 kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
 at
 kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
 at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
 at
 kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
 at
 kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
 at
 kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
 at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)



 the above message is throwing continuously by the worker node.

 I assume this issue is related to some configurations of kafka server.

 *Any ideas of solving this issue ?*





 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 <+94+(0)+775246619>

 *nay...@wso2.com *

>>>
>>>
>>>
>>> --
>>> --
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>> Wordpress:http://chanakaudaya.wordpress.com
>>>
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] C5 List of bundles to be provisioned for PAX Exam unit tests

[Aruna Karunarathna]

Hi all,

Shall we finalize the list of bundles to be provisioned in order the core
module to be tested.
Currently I have provisioned all the bundles available, when a regular
server start up. [1]

mavenBundle().artifactId("testng").groupId("org.testng").versionAsInProject(),
mavenBundle().artifactId("org.wso2.carbon.core").groupId("org.wso2.carbon").versionAsInProject(),
mavenBundle().artifactId("hazelcast").groupId("org.wso2.orbit.com.hazelcast").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.simpleconfigurator").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("javax.servlet-api").groupId("javax.servlet").versionAsInProject(),
mavenBundle().artifactId("org.apache.felix.gogo.command").groupId("org.apache.felix").versionAsInProject(),
mavenBundle().artifactId("org.apache.felix.gogo.runtime").groupId("org.apache.felix").versionAsInProject(),
mavenBundle().artifactId("org.apache.felix.gogo.shell").groupId("org.apache.felix").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.core.contenttype").groupId("org.eclipse.core").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.core.expressions").groupId("org.eclipse.core").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.core.jobs
").groupId("org.eclipse.core").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.core.runtime").groupId("org.eclipse.core").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.ecf").groupId("org.eclipse.ecf").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.ecf.filetransfer").groupId("org.eclipse.ecf").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.ecf.identity").groupId("org.eclipse.ecf").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.ecf.provider.filetransfer").groupId("org.eclipse.ecf").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.app").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.common").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.concurrent").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.console").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.ds").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.frameworkadmin").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.frameworkadmin.equinox").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.http.servlet").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.launcher").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.preferences").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.registry").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.simpleconfigurator.manipulator").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.equinox.util").groupId("org.eclipse.equinox").versionAsInProject(),
mavenBundle().artifactId("org.eclipse.osgi.services").groupId("org.eclipse.osgi").versionAsInProject()

[1].
https://github.com/arunasujith/carbon-kernel/blob/pax-exam-integration/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/config/CarbonOSGiConfiguration.java

Regards,
Aruna
-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Private PaaS build fails with Stratos 412

[Udara Liyanage]

Hi,

Issue vanished after I install the newer mvn. Thanks Thanuja for looking
into this.

On Fri, Sep 4, 2015 at 10:07 AM, Imesh Gunaratne  wrote:

> Do you still see this issue?
>
> On Mon, Aug 31, 2015 at 6:19 PM, Udara Liyanage  wrote:
>
>>
>> HI,
>>
>> With the intention of getting the latest Stratos, I build Stratos from
>> 41x branch and changed Stratos version in PP to 412 and build PP. However I
>> get the following error. Seems it tries to install 412-SNAPSHOT of  RESTful
>> admin services feature.
>>
>>
>> Installing org.wso2.carbon.event.server.feature.group 4.2.1.
>> Installing org.wso2.carbon.event.common.feature.group 4.2.0.
>> Installing org.wso2.carbon.captcha.mgt.server.feature.group 4.2.0.
>> Installing org.jaggeryjs.feature.group 0.0.0.0_9_0_ALPHA4_wso2v3.
>> Installing caramel.feature.group 1.0.1.
>> Installing org.wso2.store.feature.group 1.0.1.
>> Installing org.wso2.carbon.idp.mgt.feature.group 4.2.3.
>> Installing org.wso2.carbon.as.runtimes.cxf.feature.group 4.2.2.
>> Installing org.wso2.carbon.user.mgt.feature.group 4.2.1.
>> Installation failed.
>> Cannot complete the install because of a conflicting dependency.
>>  Software being installed: Apache Stratos - RESTful admin services
>> feature 4.1.2 (org.apache.stratos.rest.endpoint.feature.group 4.1.2)
>>  Software currently installed: Apache Stratos - RESTful admin services
>> feature 4.1.2.SNAPSHOT (org.apache.stratos.rest.endpoint.feature.group
>> 4.1.2.SNAPSHOT)
>>  Only one of the following can be installed at once:
>>   Apache Stratos - RESTful admin services feature 4.1.2
>> (org.apache.stratos.rest.endpoint.feature.jar 4.1.2)
>>   Apache Stratos - RESTful admin services feature 4.1.2.SNAPSHOT
>> (org.apache.stratos.rest.endpoint.feature.jar 4.1.2.SNAPSHOT)
>>  Cannot satisfy dependency:
>>   From: Apache Stratos - RESTful admin services feature 4.1.2
>> (org.apache.stratos.rest.endpoint.feature.group 4.1.2)
>>   To: org.apache.stratos.rest.endpoint.feature.jar [4.1.2]
>>  Cannot satisfy dependency:
>>   From: Apache Stratos - RESTful admin services feature 4.1.2.SNAPSHOT
>> (org.apache.stratos.rest.endpoint.feature.group 4.1.2.SNAPSHOT)
>>   To: org.apache.stratos.rest.endpoint.feature.jar [4.1.2.SNAPSHOT]
>> Application failed, log file location:
>> /home/udara/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1440999235703.log
>>
>> [INFO]
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 PPaaS - Parent ... SUCCESS [
>>  0.830 s]
>> [INFO] WSO2 PPaaS - Cartridges ... SUCCESS [
>>  0.025 s]
>> [INFO] WSO2 PPaaS - Cartridges - Template Modules  SUCCESS [
>>  0.021 s]
>> [INFO] WSO2 PPaaS - WSO2 AM 1.9.0 Template Module  SUCCESS [
>>  0.457 s]
>> [INFO] WSO2 PPaaS - WSO2 AS 5.2.1 Template Module  SUCCESS [
>>  0.074 s]
>> [INFO] WSO2 PPaaS - WSO2 ESB 4.8.1 Template Module ... SUCCESS [
>>  0.047 s]
>> [INFO] WSO2 PPaaS - WSO2 IS 5.0.0 Template Module  SUCCESS [
>>  0.050 s]
>> [INFO] WSO2 PPaaS - Components ... SUCCESS [
>>  0.021 s]
>> [INFO] WSO2 PPaaS - Python Configurator .. SUCCESS [
>>  0.082 s]
>> [INFO] WSO2 PPaaS - Features . SUCCESS [
>>  0.024 s]
>> [INFO] WSO2 PPaaS - Products . SUCCESS [
>>  0.020 s]
>> [INFO] WSO2 PPaaS - Product .. SUCCESS [
>>  0.018 s]
>> [INFO] WSO2 PPaaS - Profile Generation ... FAILURE [
>> 47.325 s]
>> [INFO] WSO2 PPaaS - Product - Distribution ... SKIPPED
>> [INFO] WSO2 Private PaaS - Integration Tests . SKIPPED
>> [INFO] WSO2 PPaaS - Configurator - Product ... SKIPPED
>> [INFO] WSO2 PPaaS - Extensions ... SKIPPED
>> [INFO] WSO2 PPaaS - Carbon Extensions  SKIPPED
>> [INFO] WSO2 PPaaS - Carbon Extensions - Membership Scheme  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 49.852 s
>> [INFO] Finished at: 2015-08-31T11:04:01+05:30
>> [INFO] Final Memory: 30M/424M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.4:p2-profile-gen (p2 profile generation
>> for stratos manager) on project ppaas-p2-profile-gen: P2 publisher return
>> code was 13 -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> 

Re: [Dev] [ML] Wrangler Integration

[Nirmal Fernando]

Also please send a PR to our repos.

On Fri, Sep 4, 2015 at 8:59 AM, Nirmal Fernando  wrote:

> Thanks Danula.
>
> ML team like to do the integration of this, since there're few things we
> need to clear up in ML side.
>
> Can you please come up with a clearly explained document on the project
> work carried out during the summer?
>
> On Wed, Sep 2, 2015 at 12:41 AM, Danula Eranjith 
> wrote:
>
>> Hi,
>>
>> I have made the changes you suggested at [1] and created a API to access
>> the wrangler service at [2].
>>
>> Also added a new step in the wizard at [3] with the wrangler interface.
>> Please have a look.
>>
>> How can we create a sample of the dataset to be passed to wrangler? I
>> couldn't find any current implementation capable of this.
>>
>> Another concern is if we are adding the feature selection step after the
>> cleaning step, we need to reflect the changes done in step one at step two.
>> But since we do not apply transformations to RDD initially, we need to come
>> up an alternative approach.
>>
>> [1] -
>> https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler/src/main/java/org/wso2/carbon/ml/wrangler
>>
>> [2] -
>> https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.rest.api/src/main/java/org/wso2/carbon/ml/rest/api/WranglerApiV10.java
>> 
>>
>> [3] -
>> https://github.com/danula/carbon-ml/blob/master/apps/ml/site/clean/clean.jag
>>
>> Thanks,
>> Danula
>>
>>
>> On Thu, Aug 27, 2015 at 9:41 AM, Danula Eranjith 
>> wrote:
>>
>>> Basically script exported from Wrangler tool has list of operations.
>>> Wrangler class parse that script and create WranglerOperation object for
>>> each operation with its parameters.
>>> Then when WranglerOperation.executeOperation() is invoked, it creates
>>> the respective SparkOperation object and then applies operations to the
>>> JavaRDD
>>>
>>> On Thu, Aug 27, 2015 at 9:35 AM, Nirmal Fernando 
>>> wrote:
>>>
 What does WranglerOperation class do?

 On Thu, Aug 27, 2015 at 9:24 AM, Danula Eranjith 
 wrote:

> Currently Wrangler Operation is the class that holds details related
> to wrangler and SparkOperation contains the relevant Spark transformation.
>
> If we are changing SparkOperation as WranglerOperation, we need to
> rename the current WranglerOperation into something else.
>
> On Thu, Aug 27, 2015 at 9:18 AM, Nirmal Fernando 
> wrote:
>
>> /s/SparkOpration/SparkOperation
>>
>> May be as Supun said, I too think we should call them as
>> 'WranglerOperation'.
>>
>> On Thu, Aug 27, 2015 at 7:02 AM, Nirmal Fernando 
>> wrote:
>>
>>> Also, avoid static methods in transformations.
>>>
>>> On Thu, Aug 27, 2015 at 2:48 AM, Supun Sethunga 
>>> wrote:
>>>
 Hi Danula,

 Few comments:

- You might have to register the component in the OSGI
environment, to be able to call the services from a another 
 component.
Refer [1] on how to do this.
- Better to introduce an interface for WranglerOperation class.
- Add class level/ method level comments.
- Use logger in-place of System.out.println

 [1]
 https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.database/src/main/java/org/wso2/carbon/ml/database/internal/ds/MLDatabaseServiceDS.java

 Thanks,
 Supun

 On Wed, Aug 26, 2015 at 1:32 PM, Danula Eranjith <
 hmdanu...@gmail.com> wrote:

> Hi,
>
> I added the component at [1]
> 
> Please have a look.
>
> [1] -
> https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler
>
> Danula
>
> On Tue, Aug 25, 2015 at 8:35 PM, Danula Eranjith <
> hmdanu...@gmail.com> wrote:
>
>> Thanks Supun
>>
>> On Tue, Aug 25, 2015 at 7:25 PM, Supun Sethunga 
>> wrote:
>>
>>> You can integrate it to [1], by adding a new component
>>> "org.wso2.carbon.ml.wrangler". Each component is a carbon component.
>>>
>>> Please follow the naming conventions used in the other
>>> components, for package names and etc..
>>>
>>> [1] https://github.com/wso2/carbon-ml/tree/master/components/ml
>>>
>>> Thanks,
>>> Supun
>>>
>>> On Tue, Aug 25, 2015 at 

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC3

[Yasassri Ratnayake]

Hi ESB Team,

Found out that Deployment synchronizing functionality is broken in the
latest RC3 pack. It's reported at [1].

[1] - https://wso2.org/jira/browse/ESBJAVA-4156

Regards,

On Fri, Sep 4, 2015 at 2:09 AM, Ravindra Ranwala  wrote:

> Hi Devs,
>
> WSO2 ESB 4.9.0 RC3 Release Vote
>
> This release fixes the following issues:
> https://wso2.org/jira/browse/ESBJAVA-4138?filter=12385
>
> Please download ESB 4.9.0 RC3 and test the functionality and vote. Vote
> will be open for 72 hours or as needed.
>
> Source & binary distribution files:
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-041/org/wso2/esb/wso2esb/4.9.0-RC3/
>
> Maven staging repository:
> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-041/
>
> The tag to be voted upon :
> https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC3
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks and Regards,
> ~ WSO2 ESB Team ~
>
>
>
> --
> Ravindra Ranwala
> Software Engineer
> WSO2, Inc: http://wso2.com
> 
> Mobile: +94714198770
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Yasassri Ratnayake
Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets

[Manuri Amaya Perera]

Hi Nuwan,

Build is successful. Thank you.

On Thu, Sep 3, 2015 at 6:16 PM, Nuwan Wimalasekara  wrote:

> Hi Manuri
>
> There is a port bind exception in the log file. Seems the LDAP server is
> not shutdown properly. Please kill the process before executing the tests.
>
> ERR_171 Failed to bind an LDAP service (10,489) to the service registry.
>
> Thanks,
> Nuwanw
>
> On Thu, Sep 3, 2015 at 6:12 PM, Manuri Amaya Perera 
> wrote:
>
>> Please find the attached logs.
>>
>> On Thu, Sep 3, 2015 at 6:08 PM, Nuwan Wimalasekara 
>> wrote:
>>
>>> Can you please share the full log of the test module tests-ldap-userstore
>>>
>>> On Thu, Sep 3, 2015 at 6:04 PM, Manuri Amaya Perera 
>>> wrote:
>>>
 Hi Nuwan,

 I changed it but now there is some other exception.

 org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException:
 UserAdminUserAdminException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
 at java.lang.Class.newInstance(Class.java:379)
 at
 org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1577)
 at
 org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
 at
 org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)

 restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
  Time elapsed: 0.002 sec  <<< FAILURE!
 java.lang.NullPointerException: null
 at
 org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)

 Thank you.

 On Thu, Sep 3, 2015 at 5:29 PM, Nuwan Wimalasekara 
 wrote:

> Hi Manuri,
>
> in ReadOnlyLDAPUserStoreManagerTestCase,  UserStoreManager
> configuration is changed in user-mgt.xml for read only user store.
> user-mgt.xml is kept in the artifacts/AS/configs/readonlyldap/user-mgt.xml
> and the LDAP url is hard coded in this resource.
>
> ldap://localhost:10389
>
> Please change the URL as below since the server is starting with port
> offset(100) now. Otherwise it will failed to start the server with read
> only user store configuration
>
>  name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
>
> Thanks,
> Nuwanw
>
> On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera 
> wrote:
>
>> ​​Hi Nuwan,
>>
>> According to our offline discussion I set the carbon home system
>> property in CarbonServerWithReadWriteLdapUSerStoreExtension
>> inside onExecutionStart method. Now the problem in carbon home not being
>> set is solved.
>>
>> Now, when running the testcase these exceptions occur and build fails.
>>
>> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>  Time elapsed: 2,284.473 sec  <<< FAILURE!
>> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
>> at
>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
>> at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
>> at
>> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
>> at
>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>>
>> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>  Time elapsed: 0.003 

Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets

[Nuwan Wimalasekara]

Hi Manuri

There is a port bind exception in the log file. Seems the LDAP server is
not shutdown properly. Please kill the process before executing the tests.

ERR_171 Failed to bind an LDAP service (10,489) to the service registry.

Thanks,
Nuwanw

On Thu, Sep 3, 2015 at 6:12 PM, Manuri Amaya Perera 
wrote:

> Please find the attached logs.
>
> On Thu, Sep 3, 2015 at 6:08 PM, Nuwan Wimalasekara 
> wrote:
>
>> Can you please share the full log of the test module tests-ldap-userstore
>>
>> On Thu, Sep 3, 2015 at 6:04 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> I changed it but now there is some other exception.
>>>
>>> org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException:
>>> UserAdminUserAdminException
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>> at java.lang.Class.newInstance(Class.java:379)
>>> at
>>> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1577)
>>> at
>>> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>>>
>>> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>>  Time elapsed: 0.002 sec  <<< FAILURE!
>>> java.lang.NullPointerException: null
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>>>
>>> Thank you.
>>>
>>> On Thu, Sep 3, 2015 at 5:29 PM, Nuwan Wimalasekara 
>>> wrote:
>>>
 Hi Manuri,

 in ReadOnlyLDAPUserStoreManagerTestCase,  UserStoreManager
 configuration is changed in user-mgt.xml for read only user store.
 user-mgt.xml is kept in the artifacts/AS/configs/readonlyldap/user-mgt.xml
 and the LDAP url is hard coded in this resource.

 ldap://localhost:10389

 Please change the URL as below since the server is starting with port
 offset(100) now. Otherwise it will failed to start the server with read
 only user store configuration

 >>> name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}

 Thanks,
 Nuwanw

 On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera 
 wrote:

> ​​Hi Nuwan,
>
> According to our offline discussion I set the carbon home system
> property in CarbonServerWithReadWriteLdapUSerStoreExtension
> inside onExecutionStart method. Now the problem in carbon home not being
> set is solved.
>
> Now, when running the testcase these exceptions occur and build fails.
>
> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>  Time elapsed: 2,284.473 sec  <<< FAILURE!
> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
> at
> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>
> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>  Time elapsed: 0.003 sec  <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>
> I think 

Re: [Dev] Need to check whether IP address ranges works with C5 clustering

[Aruna Karunarathna]

Is this because running on the same domain? "wso2.carbon.domain"

If that is the case shouldn't it be prevented by IP ranges?..

On Thu, Sep 3, 2015 at 5:50 PM, Aruna Karunarathna  wrote:

> I'am getting the following error with ip ranges testing. [1]
>
> My IP is 10.100.5.41 and i gave the range as follows 10.100.5.30-41, but
> it connects to a 10.100.5.42 node, and giving the following exception.
> The exception may be because of hazelcast version mismatch. But as per the
> IP range I've given it shouldn't connect to the 10.100.5.42 right?..
>
> Any thoughts?..
>
> [1].
> [2015-09-03 17:42:46,335]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.31]:4001 is
> added to the blacklist.
> [2015-09-03 17:42:46,335]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.30]:4001 is
> added to the blacklist.
> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
> 10.100.5.39:4000. Reason: SocketException[No route to host to address /
> 10.100.5.39:4000]
> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
> 10.100.5.39:4001. Reason: SocketException[No route to host to address /
> 10.100.5.39:4001]
> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.39]:4000 is
> added to the blacklist.
> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.39]:4001 is
> added to the blacklist.
> [2015-09-03 17:42:46,339]  INFO
> {com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
> [wso2.carbon.domain] [3.5] Established socket connection between /
> 10.100.5.41:4000
> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
> 10.100.5.38:4001. Reason: SocketException[No route to host to address /
> 10.100.5.38:4001]
> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
> 10.100.5.38:4000. Reason: SocketException[No route to host to address /
> 10.100.5.38:4000]
> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.38]:4001 is
> added to the blacklist.
> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.38]:4000 is
> added to the blacklist.
> [2015-09-03 17:42:46,342]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.41]:4001 is
> removed from the blacklist.
> [2015-09-03 17:42:47,320]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Connecting to /
> 10.100.5.42:4000, timeout: 0, bind-any: true
> [2015-09-03 17:42:47,320]  WARN {com.hazelcast.cluster.ClusterService} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not create connection
> to possible master Address[10.100.5.42]:4000
> [2015-09-03 17:42:47,321]  WARN {com.hazelcast.cluster.ClusterService} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not create connection
> to possible master Address[10.100.5.42]:4000
> [2015-09-03 17:42:47,324]  INFO
> {com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
> [wso2.carbon.domain] [3.5] Established socket connection between /
> 10.100.5.41:38318
> [2015-09-03 17:42:53,364]  INFO {com.hazelcast.nio.tcp.SocketAcceptor} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Accepting socket connection
> from /10.100.5.42:37180
> [2015-09-03 17:42:53,366]  INFO
> {com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
> [wso2.carbon.domain] [3.5] Established socket connection between /
> 10.100.5.41:4000
> [2015-09-03 17:42:53,372]  INFO {com.hazelcast.cluster.ClusterService} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5]
>
> Members [4] {
> Member [10.100.5.42]:4000
> Member [10.100.5.42]:4002
> Member [10.100.5.41]:4001
> Member [10.100.5.41]:4000 this
> }
>
> [2015-09-03 17:42:53,396] ERROR
> {com.hazelcast.cache.impl.operation.PostJoinCacheOperation} -
>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Service with name
> 'hz:impl:cacheService' not found!
> com.hazelcast.core.HazelcastException: Service with name
> 'hz:impl:cacheService' not found!
> at com.hazelcast.spi.Operation.getService(Operation.java:213)
> at
> com.hazelcast.cache.impl.operation.PostJoinCacheOperation.run(PostJoinCacheOperation.java:44)
> at
> 

Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets

[Manuri Amaya Perera]

Hi Nuwan,

I changed it but now there is some other exception.

org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException:
UserAdminUserAdminException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:379)
at
org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1577)
at
org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
at
org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)

restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
 Time elapsed: 0.002 sec  <<< FAILURE!
java.lang.NullPointerException: null
at
org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)

Thank you.

On Thu, Sep 3, 2015 at 5:29 PM, Nuwan Wimalasekara  wrote:

> Hi Manuri,
>
> in ReadOnlyLDAPUserStoreManagerTestCase,  UserStoreManager configuration
> is changed in user-mgt.xml for read only user store. user-mgt.xml is kept
> in the artifacts/AS/configs/readonlyldap/user-mgt.xml and the LDAP url is
> hard coded in this resource.
>
> ldap://localhost:10389
>
> Please change the URL as below since the server is starting with port
> offset(100) now. Otherwise it will failed to start the server with read
> only user store configuration
>
>  name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
>
> Thanks,
> Nuwanw
>
> On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera 
> wrote:
>
>> ​​Hi Nuwan,
>>
>> According to our offline discussion I set the carbon home system property
>> in CarbonServerWithReadWriteLdapUSerStoreExtension inside onExecutionStart
>> method. Now the problem in carbon home not being set is solved.
>>
>> Now, when running the testcase these exceptions occur and build fails.
>>
>> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>  Time elapsed: 2,284.473 sec  <<< FAILURE!
>> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
>> at
>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
>> at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
>> at
>> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
>> at
>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>>
>> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>  Time elapsed: 0.003 sec  <<< FAILURE!
>> java.lang.NullPointerException: null
>> at
>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>>
>> I think these are authorization issues relevant to LDAP. Can you be of
>> any help regarding this ?
>>
>> Thank you.
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets

[Nuwan Wimalasekara]

Can you please share the full log of the test module tests-ldap-userstore

On Thu, Sep 3, 2015 at 6:04 PM, Manuri Amaya Perera 
wrote:

> Hi Nuwan,
>
> I changed it but now there is some other exception.
>
> org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException:
> UserAdminUserAdminException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:379)
> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1577)
> at
> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>
> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>  Time elapsed: 0.002 sec  <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>
> Thank you.
>
> On Thu, Sep 3, 2015 at 5:29 PM, Nuwan Wimalasekara 
> wrote:
>
>> Hi Manuri,
>>
>> in ReadOnlyLDAPUserStoreManagerTestCase,  UserStoreManager configuration
>> is changed in user-mgt.xml for read only user store. user-mgt.xml is kept
>> in the artifacts/AS/configs/readonlyldap/user-mgt.xml and the LDAP url is
>> hard coded in this resource.
>>
>> ldap://localhost:10389
>>
>> Please change the URL as below since the server is starting with port
>> offset(100) now. Otherwise it will failed to start the server with read
>> only user store configuration
>>
>> > name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
>>
>> Thanks,
>> Nuwanw
>>
>> On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> ​​Hi Nuwan,
>>>
>>> According to our offline discussion I set the carbon home system
>>> property in CarbonServerWithReadWriteLdapUSerStoreExtension
>>> inside onExecutionStart method. Now the problem in carbon home not being
>>> set is solved.
>>>
>>> Now, when running the testcase these exceptions occur and build fails.
>>>
>>> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>>  Time elapsed: 2,284.473 sec  <<< FAILURE!
>>> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
>>> at
>>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
>>> at
>>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>>> at
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>>> at
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>> at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>> at
>>> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
>>> at
>>> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>>>
>>> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>>  Time elapsed: 0.003 sec  <<< FAILURE!
>>> java.lang.NullPointerException: null
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>>>
>>> I think these are authorization issues relevant to LDAP. Can you be of
>>> any help regarding this ?
>>>
>>> Thank you.
>>>
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> 

[Dev] [APIM][Mediator] CNF while publishing APIs

[Madusanka Premaratne]

Hi Devs,
I am getting following error after upgrading carbon kernel to 4.4.1 and
synapse version to 2.1.3.wso2v7. As per my
observations, APIMgtResponseHandler extends AbstractMediator. I checked the
bundles from osgi console and there are no errors. Please note that all the
dynamic imports has been removed from all the the particular bundle.

Can someone point me what could be the issue/ where did I go wrong?

The error is,

java.lang.ClassNotFoundException:
org.wso2.carbon.apimgt.usage.publisher.APIMgtResponseHandler cannot be
found by synapse-core_2.1.3.wso2v7
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
org.apache.synapse.config.xml.ClassMediatorFactory.createSpecificMediator(ClassMediatorFactory.java:102)
at
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:94)
at
org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:224)
at
org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:46)
at
org.apache.synapse.config.xml.SequenceMediatorFactory.createAnonymousSequence(SequenceMediatorFactory.java:70)
at
org.apache.synapse.config.xml.rest.ResourceFactory.configureSequences(ResourceFactory.java:119)
at
org.apache.synapse.config.xml.rest.ResourceFactory.createResource(ResourceFactory.java:50)
at
org.apache.synapse.config.xml.rest.APIFactory.createAPI(APIFactory.java:86)
at
org.apache.synapse.config.xml.rest.APIFactory.createAPI(APIFactory.java:51)
at
org.wso2.carbon.rest.api.service.RestApiAdmin.addApi(RestApiAdmin.java:662)
at
org.wso2.carbon.rest.api.service.RestApiAdmin.addApiFromString(RestApiAdmin.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at

[Dev] How to define version ranges for orbit bundles

[Rajith Vitharana]

Hi,

How should we do the $subject? Asking this since in carbon commons axis2
version range is defined as in [1] don't we follow the same concept for
orbit bundles? shouldn't this be as [2]?

[1] - [1.6.1.wso2v14,
1.7.0)
[2] - [1.6, 1.7)

Thanks,

-- 
Rajith Vitharana

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

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Thayalan]

Thanks Prasanna. Please update the JIRA as well.

In between there was a dep sync issue reported with ESB [1] with the recent
fix from carbon commons. Just want to find out whether this has any effect
on GREG product for scenarios like secondary user store, API-M integration
(May not be an issue since we suggest to use APIM 1.9.1 for GW) or install
WSO2 AS features and use it (which is anyway very unlikely scenario).

1. ESBJAVA-4156 





On Fri, Sep 4, 2015 at 7:53 AM, Prasanna Dangalla  wrote:

> Hi Thayalan,
>
> We fixed the issue REGISTRY-2927
>  . Now users can re-login
> from the same window in a fresh pack.
>
> Thanks
>
> On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:
>
>> Hi Team,
>>
>> I've observed from the standalone pack without any changes user has not
>> been allowed to re-login  to the store [1]. However this is working fine
>> for publisher. As per the suggestion in [1] hostname has to be set in
>> carbon.xml. However in the default pack SSO enabled for store/publisher and
>> Hostname tag is commented. Even uncomment them and set to IP or localhost
>> too not working as suggested in the JIRA. From the end user perspective
>> user should allow to re-login from the same window session from the fresh
>> pack. Is this is something we need to fix before releasing them?
>>
>> 1.REGISTRY-2927 
>>
>> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
>> wrote:
>>
>>> -1,
>>>
>>> We found an issue with solr related logging configuration and this issue
>>> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>>
>>> Step to reproduce this issue:
>>>
>>> Go to Main --> Registry search and search by any value.
>>> Then navigate to Configure --> Logging section.
>>> Exceptions are logged in console and "Global Log4J Configuration" and
>>> "Configure Log4J Appenders" views are not loading due to the above issue.
>>>
>>> Created a JIRA[1] to track above issue and will release release G-Reg
>>> 5.0.0 RC3 pack ASAP.
>>>
>>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>>
>>> Regards,
>>> Chandana
>>>
>>>
>>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
>>> wrote:
>>>
 Hi Pubudu,

 Since we have already released RC2 pack and component repos, we can not
 update above pages now. We will update context specific pages for coming up
 5.0.1 release. Meantime, you can refer wiki based documentation available
 here [1].

 [1].
 https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation

 Regards,
 Chandana

 On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
 wrote:

> Hi Chandana,
>
> Since the Help page, context specific pages are out-dated we need to
> update those to reflect most recent information. Can you please address
> this issue as required? Please find the relevant ticket below. Thanks.
>
> https://wso2.org/jira/browse/REGISTRY-2910
>
> Cheers,
>
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe <
> nirde...@wso2.com> wrote:
>
>> The context sensitive help links are in the product UIs. AFAIK, these
>> links are component-based rather than product based? Please correct me 
>> if I
>> am wrong.
>>
>> If they are component-based, we cannot link to the wiki of a specific
>> product from there as many other products might also be using the same
>> component.
>>
>> Maybe we should simply disable these help links until we find a
>> better way to maintain them.
>>
>> Thanks,
>> -Nirdesha
>>
>> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
>> wrote:
>>
>>> Hi Nirdesha,
>>>
>>> Can we please point the current context sensitive help pages to
>>> relevant product documentation of GReg 5.0.0 release?
>>>
>>> Cheers,
>>>
>>> Pubudu D.P
>>> Senior Software Engineer - QA Team | WSO2 inc.
>>> Mobile : +94775464547
>>>
>>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
>>> wrote:
>>>


 On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
 evanth...@wso2.com> wrote:

> Ack!
>
> @Chalitha/Thaya/Pubudu. Please note.
>

 And all the context sensitive help pages  are outdated .

 -Ajith


>
> Regards,
> Evanthika Amarasiri
> Senior Technical Lead  - Quality Assurance
> Mobile: +94773125935
> Blog: evanthika.blogspot.com
>
> wso2.com lean.enterprise.middleware
>
> On Wed, 

Re: [Dev] Need to check whether IP address ranges works with C5 clustering

[Kishanthan Thangarajah]

Looks like an issue with a node based on C4 clustering is trying to join C5
cluster. Thats the reason for the CNF : Caused by:
java.lang.ClassNotFoundException:
org.apache.axis2.clustering.Member.

Your cluster and another cluster is using the same cluster domain.

On Thu, Sep 3, 2015 at 6:01 PM, Aruna Karunarathna  wrote:

> Is this because running on the same domain? "wso2.carbon.domain"
>
> If that is the case shouldn't it be prevented by IP ranges?..
>
> On Thu, Sep 3, 2015 at 5:50 PM, Aruna Karunarathna  wrote:
>
>> I'am getting the following error with ip ranges testing. [1]
>>
>> My IP is 10.100.5.41 and i gave the range as follows 10.100.5.30-41, but
>> it connects to a 10.100.5.42 node, and giving the following exception.
>> The exception may be because of hazelcast version mismatch. But as per
>> the IP range I've given it shouldn't connect to the 10.100.5.42 right?..
>>
>> Any thoughts?..
>>
>> [1].
>> [2015-09-03 17:42:46,335]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.31]:4001
>> is added to the blacklist.
>> [2015-09-03 17:42:46,335]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.30]:4001
>> is added to the blacklist.
>> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
>> 10.100.5.39:4000. Reason: SocketException[No route to host to address /
>> 10.100.5.39:4000]
>> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
>> 10.100.5.39:4001. Reason: SocketException[No route to host to address /
>> 10.100.5.39:4001]
>> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.39]:4000
>> is added to the blacklist.
>> [2015-09-03 17:42:46,337]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.39]:4001
>> is added to the blacklist.
>> [2015-09-03 17:42:46,339]  INFO
>> {com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
>> [wso2.carbon.domain] [3.5] Established socket connection between /
>> 10.100.5.41:4000
>> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
>> 10.100.5.38:4001. Reason: SocketException[No route to host to address /
>> 10.100.5.38:4001]
>> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not connect to: /
>> 10.100.5.38:4000. Reason: SocketException[No route to host to address /
>> 10.100.5.38:4000]
>> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.38]:4001
>> is added to the blacklist.
>> [2015-09-03 17:42:46,341]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.38]:4000
>> is added to the blacklist.
>> [2015-09-03 17:42:46,342]  INFO {com.hazelcast.cluster.impl.TcpIpJoiner}
>> -  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Address[10.100.5.41]:4001
>> is removed from the blacklist.
>> [2015-09-03 17:42:47,320]  INFO {com.hazelcast.nio.tcp.SocketConnector} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Connecting to /
>> 10.100.5.42:4000, timeout: 0, bind-any: true
>> [2015-09-03 17:42:47,320]  WARN {com.hazelcast.cluster.ClusterService} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not create connection
>> to possible master Address[10.100.5.42]:4000
>> [2015-09-03 17:42:47,321]  WARN {com.hazelcast.cluster.ClusterService} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Could not create connection
>> to possible master Address[10.100.5.42]:4000
>> [2015-09-03 17:42:47,324]  INFO
>> {com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
>> [wso2.carbon.domain] [3.5] Established socket connection between /
>> 10.100.5.41:38318
>> [2015-09-03 17:42:53,364]  INFO {com.hazelcast.nio.tcp.SocketAcceptor} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5] Accepting socket connection
>> from /10.100.5.42:37180
>> [2015-09-03 17:42:53,366]  INFO
>> {com.hazelcast.nio.tcp.TcpIpConnectionManager} -  [10.100.5.41]:4000
>> [wso2.carbon.domain] [3.5] Established socket connection between /
>> 10.100.5.41:4000
>> [2015-09-03 17:42:53,372]  INFO {com.hazelcast.cluster.ClusterService} -
>>  [10.100.5.41]:4000 [wso2.carbon.domain] [3.5]
>>
>> Members [4] {
>> Member [10.100.5.42]:4000
>> Member [10.100.5.42]:4002
>> Member [10.100.5.41]:4001
>> Member [10.100.5.41]:4000 this
>> }
>>
>> [2015-09-03 17:42:53,396] ERROR
>> {com.hazelcast.cache.impl.operation.PostJoinCacheOperation} -
>>  

Re: [Dev] [ESB] Error in kafka inbound endpoint when start consuming messages.

[Kathees Rajendram]

Hi Niyomi,

Can you change to the IP address instead of localhost in server.properties
file as you use the IP address in the Kafka inbound.

zookeeper.connect=localhost:2181

Thanks,
Kathees.

On Fri, Sep 4, 2015 at 10:31 AM, Kathees Rajendram  wrote:

> Hi Malaka.
>
> I will have a look.
>
> Thanks,
> Kathees
>
> On Fri, Sep 4, 2015 at 9:36 AM, Malaka Silva  wrote:
>
>> Hi Kathees,
>>
>> Seems like issue when configuring/starting server.
>>
>> Can you help on this matter pls?
>>
>> On Thu, Sep 3, 2015 at 9:48 PM, Nayomi Dayarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> This issue is not related to the jira[1]  i have reported.
>>>
>>> According to my understanding this is something related to kafka server.
>>> Therefore i assumed this issue is not related to kafka inbound endpoint.
>>>
>>>
>>> [1]https://wso2.org/jira/browse/ESBJAVA-4153
>>>
>>> Nayomi Dayarathne
>>>
>>> *Software Engineer-QA*
>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>>
>>> *nay...@wso2.com *
>>>
>>> On Thu, Sep 3, 2015 at 9:32 PM, Chanaka Fernando 
>>> wrote:
>>>
 Viraj is looking into this.

 On Thu, Sep 3, 2015 at 9:24 PM, Nayomi Dayarathne 
 wrote:

> Hi ESB team,
>
> I tested the kafka inbound endpoint in a esb cluster where there is
> one manager and two worker nodes.
>
> Below are the steps i did when testing the kafka inbound endpoint.
>
> 1. Start the zookeeper
> 2.Start the kafka server
>
> Zookeeper and kafka server started in my local machine.
>
> 3.Create a kafka inbound endpoint in cluster
>
> it gets deployed in all three nodes.
>
> 4.Then create a topic in kafka broker.
>
>
> then, in one of the worker nodes i get the following error,
>
>  ERROR {kafka.producer.SyncProducer} -  Producer connection to
> localhost:9092 unsuccessful {kafka.producer.SyncProducer}
> java.net.ConnectException: Connection refused
> at sun.nio.ch.Net.connect0(Native Method)
> at sun.nio.ch.Net.connect(Net.java:435)
> at sun.nio.ch.Net.connect(Net.java:427)
> at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:643)
> at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
> at kafka.producer.SyncProducer.connect(SyncProducer.scala:141)
> at
> kafka.producer.SyncProducer.getOrMakeConnection(SyncProducer.scala:156)
> at
> kafka.producer.SyncProducer.kafka$producer$SyncProducer$$doSend(SyncProducer.scala:68)
> at kafka.producer.SyncProducer.send(SyncProducer.scala:112)
> at
> kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:53)
> at
> kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
> at
> kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
> at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
>
>
>
> the above message is throwing continuously by the worker node.
>
> I assume this issue is related to some configurations of kafka server.
>
> *Any ideas of solving this issue ?*
>
>
>
>
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>



 --
 --
 Chanaka Fernando
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 773337238
 Blog : http://soatutorials.blogspot.com
 LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
 Twitter:https://twitter.com/chanakaudaya
 Wordpress:http://chanakaudaya.wordpress.com




>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>



-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to define version ranges for orbit bundles

[Sameera Jayasoma]

Hi Rajith,

The correct one should be  [1.6.1, 1.7) AFAIK.

Niranjan please update the document.

Thanks,
Sameera.

On Fri, Sep 4, 2015 at 11:02 AM, Rajith Vitharana  wrote:

> Hi,
>
> How should we do the $subject? Asking this since in carbon commons axis2
> version range is defined as in [1] don't we follow the same concept for
> orbit bundles? shouldn't this be as [2]?
>
> [1] - [1.6.1.wso2v14,
> 1.7.0)
> [2] - [1.6, 1.7)
>
> Thanks,
>
> --
> Rajith Vitharana
>
> Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94715883223
> Blog : http://lankavitharana.blogspot.com/
>



-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

Re: [Dev] How to define version ranges for orbit bundles

[Niranjan Karunanandham]

Ack.

On Fri, Sep 4, 2015 at 11:22 AM, Sameera Jayasoma  wrote:

> Hi Rajith,
>
> The correct one should be  [1.6.1, 1.7) AFAIK.
>
> Niranjan please update the document.
>
> Thanks,
> Sameera.
>
> On Fri, Sep 4, 2015 at 11:02 AM, Rajith Vitharana 
> wrote:
>
>> Hi,
>>
>> How should we do the $subject? Asking this since in carbon commons axis2
>> version range is defined as in [1] don't we follow the same concept for
>> orbit bundles? shouldn't this be as [2]?
>>
>> [1] - [1.6.1.wso2v14,
>> 1.7.0)
>> [2] - [1.6, 1.7)
>>
>> Thanks,
>>
>> --
>> Rajith Vitharana
>>
>> Software Engineer,
>> WSO2 Inc. : wso2.com
>> Mobile : +94715883223
>> Blog : http://lankavitharana.blogspot.com/
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>


-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2

[Prasanna Dangalla]

Hi Thayalan,

We fixed the issue REGISTRY-2927
 . Now users can re-login from
the same window in a fresh pack.

Thanks

On Thu, Sep 3, 2015 at 7:40 PM, Thayalan  wrote:

> Hi Team,
>
> I've observed from the standalone pack without any changes user has not
> been allowed to re-login  to the store [1]. However this is working fine
> for publisher. As per the suggestion in [1] hostname has to be set in
> carbon.xml. However in the default pack SSO enabled for store/publisher and
> Hostname tag is commented. Even uncomment them and set to IP or localhost
> too not working as suggested in the JIRA. From the end user perspective
> user should allow to re-login from the same window session from the fresh
> pack. Is this is something we need to fix before releasing them?
>
> 1.REGISTRY-2927 
>
> On Wed, Sep 2, 2015 at 6:39 PM, Chandana Napagoda 
> wrote:
>
>> -1,
>>
>> We found an issue with solr related logging configuration and this issue
>> is reproducible in G-Reg, ESB and AS packs based on carbon 4.4.1.
>>
>> Step to reproduce this issue:
>>
>> Go to Main --> Registry search and search by any value.
>> Then navigate to Configure --> Logging section.
>> Exceptions are logged in console and "Global Log4J Configuration" and
>> "Configure Log4J Appenders" views are not loading due to the above issue.
>>
>> Created a JIRA[1] to track above issue and will release release G-Reg
>> 5.0.0 RC3 pack ASAP.
>>
>> [1]. https://wso2.org/jira/browse/WSAS-2120
>>
>> Regards,
>> Chandana
>>
>>
>> On Wed, Sep 2, 2015 at 11:47 AM, Chandana Napagoda 
>> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Since we have already released RC2 pack and component repos, we can not
>>> update above pages now. We will update context specific pages for coming up
>>> 5.0.1 release. Meantime, you can refer wiki based documentation available
>>> here [1].
>>>
>>> [1].
>>> https://docs.wso2.com/display/Governance500/WSO2+Governance+Registry+Documentation
>>>
>>> Regards,
>>> Chandana
>>>
>>> On Wed, Sep 2, 2015 at 10:49 AM, Pubudu Priyashan 
>>> wrote:
>>>
 Hi Chandana,

 Since the Help page, context specific pages are out-dated we need to
 update those to reflect most recent information. Can you please address
 this issue as required? Please find the relevant ticket below. Thanks.

 https://wso2.org/jira/browse/REGISTRY-2910

 Cheers,

 Pubudu D.P
 Senior Software Engineer - QA Team | WSO2 inc.
 Mobile : +94775464547

 On Wed, Sep 2, 2015 at 10:41 AM, Nirdesha Munasinghe  wrote:

> The context sensitive help links are in the product UIs. AFAIK, these
> links are component-based rather than product based? Please correct me if 
> I
> am wrong.
>
> If they are component-based, we cannot link to the wiki of a specific
> product from there as many other products might also be using the same
> component.
>
> Maybe we should simply disable these help links until we find a better
> way to maintain them.
>
> Thanks,
> -Nirdesha
>
> On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan 
> wrote:
>
>> Hi Nirdesha,
>>
>> Can we please point the current context sensitive help pages to
>> relevant product documentation of GReg 5.0.0 release?
>>
>> Cheers,
>>
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547
>>
>> On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana 
>> wrote:
>>
>>>
>>>
>>> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <
>>> evanth...@wso2.com> wrote:
>>>
 Ack!

 @Chalitha/Thaya/Pubudu. Please note.

>>>
>>> And all the context sensitive help pages  are outdated .
>>>
>>> -Ajith
>>>
>>>

 Regards,
 Evanthika Amarasiri
 Senior Technical Lead  - Quality Assurance
 Mobile: +94773125935
 Blog: evanthika.blogspot.com

 wso2.com lean.enterprise.middleware

 On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana 
 wrote:

> Hi All
>
> This is non a bug but please fix the about page if possible
> because this is a major release. (find the attached image)
>
> -Ajith
>
>
>
>
>
> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <
> prasa...@wso2.com> wrote:
>
>> Hi All,
>>
>> *This is the RC 2 release candidate of G-Reg 5.0.0 *
>>
>> This release fixes the following issues:
>>
>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384
>> 

Re: [Dev] [ML] Wrangler Integration

[Nirmal Fernando]

Thanks Danula.

ML team like to do the integration of this, since there're few things we
need to clear up in ML side.

Can you please come up with a clearly explained document on the project
work carried out during the summer?

On Wed, Sep 2, 2015 at 12:41 AM, Danula Eranjith 
wrote:

> Hi,
>
> I have made the changes you suggested at [1] and created a API to access
> the wrangler service at [2].
>
> Also added a new step in the wizard at [3] with the wrangler interface.
> Please have a look.
>
> How can we create a sample of the dataset to be passed to wrangler? I
> couldn't find any current implementation capable of this.
>
> Another concern is if we are adding the feature selection step after the
> cleaning step, we need to reflect the changes done in step one at step two.
> But since we do not apply transformations to RDD initially, we need to come
> up an alternative approach.
>
> [1] -
> https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler/src/main/java/org/wso2/carbon/ml/wrangler
>
> [2] -
> https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.rest.api/src/main/java/org/wso2/carbon/ml/rest/api/WranglerApiV10.java
> 
>
> [3] -
> https://github.com/danula/carbon-ml/blob/master/apps/ml/site/clean/clean.jag
>
> Thanks,
> Danula
>
>
> On Thu, Aug 27, 2015 at 9:41 AM, Danula Eranjith 
> wrote:
>
>> Basically script exported from Wrangler tool has list of operations.
>> Wrangler class parse that script and create WranglerOperation object for
>> each operation with its parameters.
>> Then when WranglerOperation.executeOperation() is invoked, it creates the
>> respective SparkOperation object and then applies operations to the JavaRDD
>>
>> On Thu, Aug 27, 2015 at 9:35 AM, Nirmal Fernando  wrote:
>>
>>> What does WranglerOperation class do?
>>>
>>> On Thu, Aug 27, 2015 at 9:24 AM, Danula Eranjith 
>>> wrote:
>>>
 Currently Wrangler Operation is the class that holds details related to
 wrangler and SparkOperation contains the relevant Spark transformation.

 If we are changing SparkOperation as WranglerOperation, we need to
 rename the current WranglerOperation into something else.

 On Thu, Aug 27, 2015 at 9:18 AM, Nirmal Fernando 
 wrote:

> /s/SparkOpration/SparkOperation
>
> May be as Supun said, I too think we should call them as
> 'WranglerOperation'.
>
> On Thu, Aug 27, 2015 at 7:02 AM, Nirmal Fernando 
> wrote:
>
>> Also, avoid static methods in transformations.
>>
>> On Thu, Aug 27, 2015 at 2:48 AM, Supun Sethunga 
>> wrote:
>>
>>> Hi Danula,
>>>
>>> Few comments:
>>>
>>>- You might have to register the component in the OSGI
>>>environment, to be able to call the services from a another 
>>> component.
>>>Refer [1] on how to do this.
>>>- Better to introduce an interface for WranglerOperation class.
>>>- Add class level/ method level comments.
>>>- Use logger in-place of System.out.println
>>>
>>> [1]
>>> https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.database/src/main/java/org/wso2/carbon/ml/database/internal/ds/MLDatabaseServiceDS.java
>>>
>>> Thanks,
>>> Supun
>>>
>>> On Wed, Aug 26, 2015 at 1:32 PM, Danula Eranjith <
>>> hmdanu...@gmail.com> wrote:
>>>
 Hi,

 I added the component at [1]
 
 Please have a look.

 [1] -
 https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler

 Danula

 On Tue, Aug 25, 2015 at 8:35 PM, Danula Eranjith <
 hmdanu...@gmail.com> wrote:

> Thanks Supun
>
> On Tue, Aug 25, 2015 at 7:25 PM, Supun Sethunga 
> wrote:
>
>> You can integrate it to [1], by adding a new component
>> "org.wso2.carbon.ml.wrangler". Each component is a carbon component.
>>
>> Please follow the naming conventions used in the other
>> components, for package names and etc..
>>
>> [1] https://github.com/wso2/carbon-ml/tree/master/components/ml
>>
>> Thanks,
>> Supun
>>
>> On Tue, Aug 25, 2015 at 7:33 AM, Danula Eranjith <
>> hmdanu...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Can you suggest where I should be ideally integrating these files
>>> [1]
>>> 

Re: [Dev] [DAS] Configuring Cross Origin Resource Sharing in DAS

[Madawa Soysa]

Hi Gimantha,

I tried that but the issue won't fix.

On 4 September 2015 at 01:19, Gimantha Bandara  wrote:

> Hi Madawa,
>
> Can you please try to follow [1] and see if the issue can be fixed? This
> will apply the CORS settings for the whole tomcat container.
>
> [1]
> https://docs.wso2.com/display/DAS300/CORS+Settings+for+the+Analytics+REST+API
>
> On Thu, Sep 3, 2015 at 1:00 PM, Madawa Soysa 
> wrote:
>
>> Hi All,
>>
>> I need to send JSON events from different domains to a DAS HTTP input
>> receiver. Since browsers does not allow cross origin scripting I user CORS
>> [1]  to
>> send a POST request to DAS input receiver. I get the following error when
>> the request is send.
>>
>> XMLHttpRequest cannot load http://192.168.0.171:9763/endpoints/test. No
>> 'Access-Control-Allow-Origin' header is present on the requested resource.
>>
>> Even though the above error occurred, the events gets stored in the event
>> stream without a problem; but the client program do not get the 'success'
>> response. As I read at [2]
>> ,
>> additional headers should be included in the server response. Is there a
>> way to configure this in DAS.
>>
>> [1] - https://en.wikipedia.org/wiki/Cross-origin_resource_sharing
>> [2] -
>> http://stackoverflow.com/questions/10636611/how-does-access-control-allow-origin-header-work
>> --
>>
>> *_**Madawa Soysa*
>>
>> Undergraduate,
>>
>> Department of Computer Science and Engineering,
>>
>> University of Moratuwa.
>>
>>
>> Mobile: +94 71 461 6050 <%2B94%2075%20812%200726> | Email:
>> madawa...@cse.mrt.ac.lk
>> LinkedIn  | Twitter
>>  | Tumblr 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Gimantha Bandara
> Software Engineer
> WSO2. Inc : http://wso2.com
> Mobile : +94714961919
>



-- 

*_**Madawa Soysa*

Undergraduate,

Department of Computer Science and Engineering,

University of Moratuwa.


Mobile: +94 71 461 6050 <%2B94%2075%20812%200726> | Email:
madawa...@cse.mrt.ac.lk
LinkedIn  | Twitter
 | Tumblr 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to call "IdentityApplicationManagementService" admin service as a tenant user

[Amila De Silva]

On Thu, Sep 3, 2015 at 11:35 PM, Sanjeewa Malalgoda 
wrote:

> API Manager/ APP Manager applications are super tenant deployed
> multitenanted SaaS applications.
> So its common to have some operations perform as admin users. Actually in
> that cases application act as super users and handle tenants and other user
> flows.
>
Correct.

> So i dont see big issue with this. And We may not need call these admin
> services as tenant users(users will call APIs but actual operation and
> admin service call done by super tenant deployed app).
>

The problem is, ApplicationManagementAdminService creates SP in the logged
in user's space. So if the service is invoked using Admin Credentials, then
the SP will be created for Admin user. If the subscriber later happens to
log into management console and change the SP, then he/she won't be able to
see it.
>
>
> Thanks,
> sanjeewa.
>
> On Thu, Sep 3, 2015 at 10:56 PM, Amila De Silva  wrote:
>
>> Hi,
>>
>> If this is about calling *ApplicationManagementAdmin**Service *using 
>> MutualSSL,
>> then still this would be only available to admin users, isn't it. A similar
>> approach was attempted while trying to create SP for AM_Application, at the
>> time of Generating a key. The problem was, even mutual SSL allows user to
>> authenticate, since this is an admin service, users are failed at the
>> authorising step unless they are admin users.
>>
>> On Thu, Sep 3, 2015 at 12:20 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> If you are trying to implement tenant SP creation for App manager then
>>> we can easily do it using mutual SSL with tenant user name.
>>> We have implemented something similar and we can share code with you
>>> soon.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Thu, Sep 3, 2015 at 12:13 AM, Lakshani Gamage 
>>> wrote:
>>>
 Hi all,

 I want to call "*IdentityApplicationManagementService*" admin service
 as a tenant user.

 I gave super tenant credentials to that stub and called  "
 *createApplication*" method by changing tenant flow. But still the SP
 is created in ST space.

 If you have any idea, how to call this Service as a tenant user, Please
 share it.

 Thanks,
 Lakshani



 --
 Lakshani Gamage

 *Software Engineer*
 Mobile : +94 (0) 71 5478184 <%2B94%20%280%29%20773%20451194>

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


>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>> blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> 
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev