Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Mohanadarshan Vivekanandalingam]

On Tue, Jan 26, 2016 at 4:52 PM, Sachith Withana  wrote:

> @Mohan: Do we have to release Siddhi as well? since there's a dependency
> on Siddhi from carbon-analytics-common.
>

No need a Siddhi release.. Please use the existing released Siddhi
dependency..


> On Tue, Jan 26, 2016 at 4:35 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> By the Sachith, please update once you are done with
>> carbon-analytics-common release..  Then I can move with
>> carbon-event-processing release..
>>
>> On Tue, Jan 26, 2016 at 3:23 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana 
>>> wrote:
>>>
 @Mohan: I can release the analytics-common now, if you guys are not
 doing any active development on it.

>>>
>>> Sachith, please go ahead and release it..
>>>
>>>

 On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara 
 wrote:

> Actually I was about to ask the same thing. Please correct me if I am
> wrong, but i didnt see there being a reference to event-processing in
> analytics-common.
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>
> On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
>> wrote:
>>
>>> Hi Mohan,
>>>
>>> Can you merge and release the Carbon-event-processing first? so that
>>> It can be included in carbon-analytics-common release?
>>>
>>
>> Sorry, why do you need a Carbon-event-processing release first?
>> carbon-analytics-common is not depend on that..
>>
>>
>>
>>>
>>> Thanks,
>>> Sachith
>>>
>>> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
>>> wrote:
>>>
 Hi Team,

 Ran in to a few OSGI issues again whilst packing DAS components in
 IoTS and did some fixes. Can we get the below PRs ([1] & [2]) merged 
 to the
 respective Repos and get them released?

 There is another fix that need to go in to carbon-analytics. But in
 order to add that fix, the following two repos need to be released as 
 they
 are inter-dependent.

 [1] - https://github.com/wso2/carbon-event-processing/pull/197
 [2] - https://github.com/wso2/carbon-analytics-common/pull/174

 Thanks and Regards,

 Ruwan Yatawara

 Senior Software Engineer,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 blog : http://ruwansrants.blogspot.com/
 www: :http://wso2.com


>>>
>>>
>>> --
>>> Sachith Withana
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> E-mail: sachith AT wso2.com
>>> M: +94715518127
>>> Linked-In: 
>>> https://lk.linkedin.com/in/sachithwithana
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>


 --
 Sachith Withana
 Software Engineer; WSO2 Inc.; http://wso2.com
 E-mail: sachith AT wso2.com
 M: +94715518127
 Linked-In: 
 https://lk.linkedin.com/in/sachithwithana

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Senior Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Ruwan Yatawara]

Actually I was about to ask the same thing. Please correct me if I am
wrong, but i didnt see there being a reference to event-processing in
analytics-common.

Thanks and Regards,

Ruwan Yatawara

Senior Software Engineer,
WSO2 Inc.

email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com


On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana  wrote:
>
>> Hi Mohan,
>>
>> Can you merge and release the Carbon-event-processing first? so that It
>> can be included in carbon-analytics-common release?
>>
>
> Sorry, why do you need a Carbon-event-processing release first?
> carbon-analytics-common is not depend on that..
>
>
>
>>
>> Thanks,
>> Sachith
>>
>> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara  wrote:
>>
>>> Hi Team,
>>>
>>> Ran in to a few OSGI issues again whilst packing DAS components in IoTS
>>> and did some fixes. Can we get the below PRs ([1] & [2]) merged to the
>>> respective Repos and get them released?
>>>
>>> There is another fix that need to go in to carbon-analytics. But in
>>> order to add that fix, the following two repos need to be released as they
>>> are inter-dependent.
>>>
>>> [1] - https://github.com/wso2/carbon-event-processing/pull/197
>>> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing the CORS issue in ML

[Fazlan Nazeem]

Adding  dev@

On Tue, Jan 26, 2016 at 3:06 PM, Fazlan Nazeem  wrote:

>
> Cross origin calls are not supported in ML at the moment. This issue was
> raised when Miyuru/Thamali were working with Swagger previously. Also I
> came across this issue when I had to make make REST api calls from Zeppelin
> notebook server and Nethaji was facing the same issue with building the
> recommendation site.
>
> The issue can be fixed by adding a filter with the following configuration
> to web.xml of api.war.
>
> 
> CorsFilter
> org.apache.catalina.filters.CorsFilter
> 
> cors.allowed.methods
> GET,POST,HEAD,OPTIONS,PUT,DELETE
> 
> 
> cors.allowed.headers
> 
>
> Content-Type,X-Requested-With,accept,Origin,Access-Control-Request-Method,Access-Control-Request-Headers,
> *Authorization*
> 
> 
> 
>
>
> There are couple of things which should be noted.
>
>- A cross origin call is identified by the "*Origin*" header of the
>request.
>- With this filter all cross origin calls will be diverted through
>this filter and the request will be successfully served.
>- The browser automatically adds the Origin header to a request if it
>sees that an api call is made to an external host.
>- If a cross origin request is invalid it will send a 403 forbidden
>error to the requester. (This is done by the filter)
>
>
> Importatnt:
>
>
>- With some reading[6] and debugging I have found out that
>Chrome/Safari adds the origin header to all* POST/PUT/DELETE *requests
>even if it is sent to the same origin. Firefox does not add the origin
>header for same origin requests.
>- Since Chrome adds the origin header to non-cors requests, all Ajax
>requests should be in valid format in order to avoid the 403 error
>mentioned above.
>- We have some Ajax calls which are not in valid format (The
>"contentType" header is missing). These requests will work without the
>filter. But will throw a 403 after adding the filter in Chrome and still
>remain to work in Firefox.
>
>
> I have found 5 places[1,2,3,4,5] where we have missed to mention the*
> contentType* of a (POST/PUT/DELETE) request. If you come across any such
> places, please fix them.
>
> Also would like to know if anyone is aware of fixing this issue from a
> better approach.
>
> [1]
> https://github.com/wso2/carbon-ml/blob/master/apps/ml/site/model/model.jag#L196
> [2]
> https://github.com/wso2/carbon-ml/blob/master/apps/ml/site/analysis/analysis.jag#L623
> [3]
> https://github.com/wso2/carbon-ml/blob/master/apps/ml/site/analysis/analysis.jag#L642
> [4]
> https://github.com/wso2/carbon-ml/blob/master/apps/ml/site/project/compare.jag#L832
> [5]
> https://github.com/wso2/carbon-ml/blob/master/apps/ml/site/project/compare.jag#L850
>
> [6] http://stackoverflow.com/questions/13851946/header-origin-vs-host
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>



-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Sachith Withana]

@Mohan: I can release the analytics-common now, if you guys are not doing
any active development on it.

On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara  wrote:

> Actually I was about to ask the same thing. Please correct me if I am
> wrong, but i didnt see there being a reference to event-processing in
> analytics-common.
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>
> On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
>> wrote:
>>
>>> Hi Mohan,
>>>
>>> Can you merge and release the Carbon-event-processing first? so that It
>>> can be included in carbon-analytics-common release?
>>>
>>
>> Sorry, why do you need a Carbon-event-processing release first?
>> carbon-analytics-common is not depend on that..
>>
>>
>>
>>>
>>> Thanks,
>>> Sachith
>>>
>>> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
>>> wrote:
>>>
 Hi Team,

 Ran in to a few OSGI issues again whilst packing DAS components in IoTS
 and did some fixes. Can we get the below PRs ([1] & [2]) merged to the
 respective Repos and get them released?

 There is another fix that need to go in to carbon-analytics. But in
 order to add that fix, the following two repos need to be released as they
 are inter-dependent.

 [1] - https://github.com/wso2/carbon-event-processing/pull/197
 [2] - https://github.com/wso2/carbon-analytics-common/pull/174

 Thanks and Regards,

 Ruwan Yatawara

 Senior Software Engineer,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 blog : http://ruwansrants.blogspot.com/
 www: :http://wso2.com


>>>
>>>
>>> --
>>> Sachith Withana
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> E-mail: sachith AT wso2.com
>>> M: +94715518127
>>> Linked-In: 
>>> https://lk.linkedin.com/in/sachithwithana
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Mohanadarshan Vivekanandalingam]

On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana  wrote:

> @Mohan: I can release the analytics-common now, if you guys are not doing
> any active development on it.
>

Sachith, please go ahead and release it..


>
> On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara  wrote:
>
>> Actually I was about to ask the same thing. Please correct me if I am
>> wrong, but i didnt see there being a reference to event-processing in
>> analytics-common.
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>> On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
>>> wrote:
>>>
 Hi Mohan,

 Can you merge and release the Carbon-event-processing first? so that It
 can be included in carbon-analytics-common release?

>>>
>>> Sorry, why do you need a Carbon-event-processing release first?
>>> carbon-analytics-common is not depend on that..
>>>
>>>
>>>

 Thanks,
 Sachith

 On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
 wrote:

> Hi Team,
>
> Ran in to a few OSGI issues again whilst packing DAS components in
> IoTS and did some fixes. Can we get the below PRs ([1] & [2]) merged to 
> the
> respective Repos and get them released?
>
> There is another fix that need to go in to carbon-analytics. But in
> order to add that fix, the following two repos need to be released as they
> are inter-dependent.
>
> [1] - https://github.com/wso2/carbon-event-processing/pull/197
> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>


 --
 Sachith Withana
 Software Engineer; WSO2 Inc.; http://wso2.com
 E-mail: sachith AT wso2.com
 M: +94715518127
 Linked-In: 
 https://lk.linkedin.com/in/sachithwithana

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Senior Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] EmptyStackException when resuming a paused message processor

[Sanjeewa Malalgoda]

Please find the complete error log below.

2016-01-26 15:30:27,128] ERROR - PassThroughHttpSender Failed to submit the
response
java.lang.NullPointerException
at
org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:493)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:108)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:155)
at org.apache.synapse.rest.Resource.process(Resource.java:297)
at org.apache.synapse.rest.API.process(API.java:335)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:86)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:52)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:295)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:251)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2016-01-26 15:30:27,138] ERROR - Axis2Sender
Accept-Ranges:bytes,Access-Control-Allow-Headers:authorization,Access-Control-Allow-Origin,Content-Type,Access-Control-Allow-Methods:POST,PATCH,GET,DELETE,PUT,Access-Control-Allow-Origin:*,ETag:"b1-4fdc9b19d2b93",Last-Modified:Wed,
09 Jul 2014 21:50:16 GMT,Vary:Accept-Encoding,http://schemas.xmlsoap.org/soap/envelope/;>
Unexpected error sending message back
org.apache.axis2.AxisFault: Failed to submit the response
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.handleException(PassThroughHttpSender.java:610)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:269)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:493)
at
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:108)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:155)
at org.apache.synapse.rest.Resource.process(Resource.java:297)
at org.apache.synapse.rest.API.process(API.java:335)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:86)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:52)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:295)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:251)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at
org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462)
at
org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267)
... 20 more
[2016-01-26 15:30:27,156]  INFO - LogMediator STATUS = Executing default
'fault' sequence, ERROR_CODE = 0, ERROR_MESSAGE =

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Sachith Withana]

@Mohan: Do we have to release Siddhi as well? since there's a dependency on
Siddhi from carbon-analytics-common.

On Tue, Jan 26, 2016 at 4:35 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> By the Sachith, please update once you are done with
> carbon-analytics-common release..  Then I can move with
> carbon-event-processing release..
>
> On Tue, Jan 26, 2016 at 3:23 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana 
>> wrote:
>>
>>> @Mohan: I can release the analytics-common now, if you guys are not
>>> doing any active development on it.
>>>
>>
>> Sachith, please go ahead and release it..
>>
>>
>>>
>>> On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara  wrote:
>>>
 Actually I was about to ask the same thing. Please correct me if I am
 wrong, but i didnt see there being a reference to event-processing in
 analytics-common.

 Thanks and Regards,

 Ruwan Yatawara

 Senior Software Engineer,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 blog : http://ruwansrants.blogspot.com/
 www: :http://wso2.com


 On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

>
>
> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
> wrote:
>
>> Hi Mohan,
>>
>> Can you merge and release the Carbon-event-processing first? so that
>> It can be included in carbon-analytics-common release?
>>
>
> Sorry, why do you need a Carbon-event-processing release first?
> carbon-analytics-common is not depend on that..
>
>
>
>>
>> Thanks,
>> Sachith
>>
>> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
>> wrote:
>>
>>> Hi Team,
>>>
>>> Ran in to a few OSGI issues again whilst packing DAS components in
>>> IoTS and did some fixes. Can we get the below PRs ([1] & [2]) merged to 
>>> the
>>> respective Repos and get them released?
>>>
>>> There is another fix that need to go in to carbon-analytics. But in
>>> order to add that fix, the following two repos need to be released as 
>>> they
>>> are inter-dependent.
>>>
>>> [1] - https://github.com/wso2/carbon-event-processing/pull/197
>>> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>


>>>
>>>
>>> --
>>> Sachith Withana
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> E-mail: sachith AT wso2.com
>>> M: +94715518127
>>> Linked-In: 
>>> https://lk.linkedin.com/in/sachithwithana
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MB] [MQTT] Bulk Messages on Carbon Logs from PublishDecoder

[Rasika Perera]

Hi All,

Currently we are using MB as our MQTT broker in our IoTS. We are seeing
bulk messages are printed when publishing MQTT message into broker[1].

[2016-01-26 16:46:16,450]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
[2016-01-26 16:46:17,946]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
[2016-01-26 16:46:19,068]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
[2016-01-26 16:46:21,824]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
[2016-01-26 16:46:31,451]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
[2016-01-26 16:46:32,945]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 16384)
[2016-01-26 16:46:34,068]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 16384)
[2016-01-26 16:46:36,823]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 8192)
[2016-01-26 16:46:46,449]  INFO
{org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 8192)

These messages are at INFO level. IMO this should be at TRACE level log.
WDYT?

​[1]
https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/dna/mqtt/moquette/parser/netty/PublishDecoder.java#L38
​

-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] [MQTT] Bulk Messages on Carbon Logs from PublishDecoder

[Rasika Perera]

Hi Pamod,

Many thanks for the prompt response. I created JIRA[1] for this issue.

[1] https://wso2.org/jira/browse/MB-1610

Regards
Rasika Perera

On Tue, Jan 26, 2016 at 5:10 PM, Pamod Sylvester  wrote:

> Yes, this comes from the Moqutte library when decoding a published
> message, since we've forked the repo we could add the change.
>
> Please create a jira.
>
> Thanks,
> Pamod
>
> On Tue, Jan 26, 2016 at 5:05 PM, Rasika Perera  wrote:
>
>> Hi All,
>>
>> Currently we are using MB as our MQTT broker in our IoTS. We are seeing
>> bulk messages are printed when publishing MQTT message into broker[1].
>>
>> [2016-01-26 16:46:16,450]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
>> [2016-01-26 16:46:17,946]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
>> [2016-01-26 16:46:19,068]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
>> [2016-01-26 16:46:21,824]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
>> [2016-01-26 16:46:31,451]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
>> [2016-01-26 16:46:32,945]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 16384)
>> [2016-01-26 16:46:34,068]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 16384)
>> [2016-01-26 16:46:36,823]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 8192)
>> [2016-01-26 16:46:46,449]  INFO
>> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
>> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 8192)
>>
>> These messages are at INFO level. IMO this should be at TRACE level log.
>> WDYT?
>>
>> ​[1]
>> https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/dna/mqtt/moquette/parser/netty/PublishDecoder.java#L38
>> ​
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com *
> cell: +94 77 7779495
>



-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error wile building carbon-feature-repository (branch: release-4.2.x)

[Niranjan Karunanandham]

Hi Tanya,

There was only a p2-repo release in the GIthub and there exists a branch
called release-4.2.x[1]. This is the release branch and this was done by
AmilaD for APIM. IMO if we are to do a new p2-repo release for kernel
4.2.0, then we need to rename this branch to 4.2.x and change the version
to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be sent to this
branch.

@Sameera / Kicha: WDYT?

[1] - https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x

Regards,
Nira

On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma  wrote:

> Hi Sameera,
>
> As per the offline chat I had with Niranjan and Nipuni, in order to fulfil
> the above request from the app manager team, we need to have  a development
> on-going branch for 4.2.x to send the PR with the missing features.
> But we couldn't locate such branch but the released branch (release-4.2.x)
> which has the version as 4.2.13
>
> Where should we send the PR to? Could you please advise.
>
> Thanks,
> Tanya
>
> On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran 
> wrote:
>
>> Hi Tanya,
>>
>> Please check on this.
>>
>> Thanks,
>> Sinthuja.
>>
>> On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray  wrote:
>>
>>> adding Manu and Sinthuja
>>>
>>> On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray  wrote:
>>>
 Hi Dakshika,
 Currently we are using Jaggery Server Feature 0.10.1 and this
 particular dependency is not included in released P2 repo.
 (https://github.com/wso2/carbon-feature-repository > release-4.2.x
 branch)

 Could you please update the repo with relevant dependencies so we can
 proceed further.

 Thank you.


 On Sat, Jan 9, 2016 at 4:02 PM, Lahiru Cooray  wrote:

> Hi Chamila,
> Thank you. Now its working.
>
> On Fri, Jan 8, 2016 at 6:09 PM, Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Hi Lahiru,
>> Released the missing repos. You can try building it now.
>>
>> Chamila
>>
>> On Wed, Jan 6, 2016 at 12:32 PM, Lahiru Cooray 
>> wrote:
>>
>>> Hi APIM team,
>>> Could you please update the repo with missing versions.
>>>
>>> Thank you..
>>>
>>> On Tue, Jan 5, 2016 at 7:06 PM, Lahiru Cooray 
>>> wrote:
>>>
 Hi,

 I get the below error while building the carbon-feature-repository (
 https://github.com/wso2/carbon-feature-repository > release-4.2.x
 branch)

 And the required version 
 (org.wso2.am:org.wso2.apimgt.gateway-manager.nested.category.feature:zip:1.9.1)
 is not available in the
 http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/am/org.wso2.apimgt.gateway-manager.nested.category.feature/



 [ERROR] Error occured when processing the Feature Artifact:
 org.wso2.am:
 org.wso2.apimgt.gateway-manager.nested.category.feature:1.9.1

 org.apache.maven.plugin.MojoExecutionException: Error occured when
 processing the Feature Artifact: org.wso2.am:
 org.wso2.apimgt.gateway-manager.nested.category.feature:1.9.1

 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 org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)

 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)

 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Mohanadarshan Vivekanandalingam]

On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana  wrote:

> Hi Mohan,
>
> Can you merge and release the Carbon-event-processing first? so that It
> can be included in carbon-analytics-common release?
>

Sorry, why do you need a Carbon-event-processing release first?
carbon-analytics-common is not depend on that..



>
> Thanks,
> Sachith
>
> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara  wrote:
>
>> Hi Team,
>>
>> Ran in to a few OSGI issues again whilst packing DAS components in IoTS
>> and did some fixes. Can we get the below PRs ([1] & [2]) merged to the
>> respective Repos and get them released?
>>
>> There is another fix that need to go in to carbon-analytics. But in order
>> to add that fix, the following two repos need to be released as they are
>> inter-dependent.
>>
>> [1] - https://github.com/wso2/carbon-event-processing/pull/197
>> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Rukshan Premathunga]

Hi Vithulan,

if you mean aggregate functions, known functions are

   - MAX
   - MIN
   - AVG
   - SUM

also you can refer these[1][2] docs for more about the API.

[1]
https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
[2]
http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html

Thanks and Regards.


On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan 
wrote:

> Hi,
>
> We need to have data aggregations for LogAnalyzer, log search requirement.
> What are the aggregations that are available in DAS REST API currently?
>
> Thanks.
>
> Regards,
> Vithulan.
>
> --
> *Vithulan MV*
>
> Intern-Software Engineering
> WSO2, Inc : wso2.com
> Mobile: +94712540524
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Mohanadarshan Vivekanandalingam]

By the Sachith, please update once you are done with
carbon-analytics-common release..  Then I can move with
carbon-event-processing release..

On Tue, Jan 26, 2016 at 3:23 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana  wrote:
>
>> @Mohan: I can release the analytics-common now, if you guys are not doing
>> any active development on it.
>>
>
> Sachith, please go ahead and release it..
>
>
>>
>> On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara  wrote:
>>
>>> Actually I was about to ask the same thing. Please correct me if I am
>>> wrong, but i didnt see there being a reference to event-processing in
>>> analytics-common.
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>> On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>


 On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
 wrote:

> Hi Mohan,
>
> Can you merge and release the Carbon-event-processing first? so that
> It can be included in carbon-analytics-common release?
>

 Sorry, why do you need a Carbon-event-processing release first?
 carbon-analytics-common is not depend on that..



>
> Thanks,
> Sachith
>
> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
> wrote:
>
>> Hi Team,
>>
>> Ran in to a few OSGI issues again whilst packing DAS components in
>> IoTS and did some fixes. Can we get the below PRs ([1] & [2]) merged to 
>> the
>> respective Repos and get them released?
>>
>> There is another fix that need to go in to carbon-analytics. But in
>> order to add that fix, the following two repos need to be released as 
>> they
>> are inter-dependent.
>>
>> [1] - https://github.com/wso2/carbon-event-processing/pull/197
>> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



 --
 *V. Mohanadarshan*
 *Senior Software Engineer,*
 *Data Technologies Team,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: mo...@wso2.com
 phone:(+94) 771117673

>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Gimantha Bandara]

Hi Vithulan,

Other than the aggregates Rukshan has mentioned, DAS supports COUNT also.
Are there any other aggregates required log analyzer functionalities?

On Tue, Jan 26, 2016 at 3:31 PM, Rukshan Premathunga 
wrote:

> Hi Vithulan,
>
> if you mean aggregate functions, known functions are
>
>- MAX
>- MIN
>- AVG
>- SUM
>
> also you can refer these[1][2] docs for more about the API.
>
> [1]
> https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
> [2]
> http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html
>
> Thanks and Regards.
>
>
> On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan 
> wrote:
>
>> Hi,
>>
>> We need to have data aggregations for LogAnalyzer, log search
>> requirement. What are the aggregations that are available in DAS REST API
>> currently?
>>
>> Thanks.
>>
>> Regards,
>> Vithulan.
>>
>> --
>> *Vithulan MV*
>>
>> Intern-Software Engineering
>> WSO2, Inc : wso2.com
>> Mobile: +94712540524
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> 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] Error wile building carbon-feature-repository (branch: release-4.2.x)

[KasunG Gajasinghe]

On Tue, Jan 26, 2016 at 2:37 PM, Niranjan Karunanandham 
wrote:

> Hi Tanya,
>
> There was only a p2-repo release in the GIthub and there exists a branch
> called release-4.2.x[1]. This is the release branch and this was done by
> AmilaD for APIM. IMO if we are to do a new p2-repo release for kernel
> 4.2.0, then we need to rename this branch to 4.2.x and change the version
> to 4.2.14-SNAPSHOT and new PRs for 4.2.x p2-repo need to be sent to this
> branch.
>
>
+1


> @Sameera / Kicha: WDYT?
>
> [1] - https://github.com/wso2/carbon-feature-repository/tree/release-4.2.x
>
> Regards,
> Nira
>
> On Tue, Jan 26, 2016 at 2:15 PM, Tanya Madurapperuma 
> wrote:
>
>> Hi Sameera,
>>
>> As per the offline chat I had with Niranjan and Nipuni, in order to
>> fulfil the above request from the app manager team, we need to have  a
>> development on-going branch for 4.2.x to send the PR with the missing
>> features.
>> But we couldn't locate such branch but the released branch
>> (release-4.2.x) which has the version as 4.2.13
>>
>> Where should we send the PR to? Could you please advise.
>>
>> Thanks,
>> Tanya
>>
>> On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi Tanya,
>>>
>>> Please check on this.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray  wrote:
>>>
 adding Manu and Sinthuja

 On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray 
 wrote:

> Hi Dakshika,
> Currently we are using Jaggery Server Feature 0.10.1 and this
> particular dependency is not included in released P2 repo.
> (https://github.com/wso2/carbon-feature-repository > release-4.2.x
> branch)
>
> Could you please update the repo with relevant dependencies so we can
> proceed further.
>
> Thank you.
>
>
> On Sat, Jan 9, 2016 at 4:02 PM, Lahiru Cooray 
> wrote:
>
>> Hi Chamila,
>> Thank you. Now its working.
>>
>> On Fri, Jan 8, 2016 at 6:09 PM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi Lahiru,
>>> Released the missing repos. You can try building it now.
>>>
>>> Chamila
>>>
>>> On Wed, Jan 6, 2016 at 12:32 PM, Lahiru Cooray 
>>> wrote:
>>>
 Hi APIM team,
 Could you please update the repo with missing versions.

 Thank you..

 On Tue, Jan 5, 2016 at 7:06 PM, Lahiru Cooray 
 wrote:

> Hi,
>
> I get the below error while building the carbon-feature-repository
> (https://github.com/wso2/carbon-feature-repository >
> release-4.2.x branch)
>
> And the required version 
> (org.wso2.am:org.wso2.apimgt.gateway-manager.nested.category.feature:zip:1.9.1)
> is not available in the
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/am/org.wso2.apimgt.gateway-manager.nested.category.feature/
>
>
>
> [ERROR] Error occured when processing the Feature Artifact:
> org.wso2.am:
> org.wso2.apimgt.gateway-manager.nested.category.feature:1.9.1
>
> org.apache.maven.plugin.MojoExecutionException: Error occured when
> processing the Feature Artifact: org.wso2.am:
> org.wso2.apimgt.gateway-manager.nested.category.feature:1.9.1
>
> 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] [ESB] EmptyStackException when resuming a paused message processor

[Sanjeewa Malalgoda]

Hi All,
Did this fix included to last release?
I'm getting exact same issue in API Manager 1.10 with high concurrency.
Getting exact same NPE mentioned in below JIRA[1]

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

Thanks,
sanjeewa.


On Wed, Oct 14, 2015 at 11:09 AM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi Nuwan,
>
> Our plan is to do the first milestone release end of next week. With this
> we hope to incorporate latest carbon-deployment and kernel releases (if it
> released during this week).
>
> Thanks.
>
> On Wed, Oct 14, 2015 at 11:07 AM, Chanaka Fernando 
> wrote:
>
>> [Adding Jagath]
>>
>> On Wed, Oct 14, 2015 at 10:17 AM, Nuwan Dias  wrote:
>>
>>> Hi ESB folks,
>>>
>>> Can we get a milestone release of synapse and carbon-mediation including
>>> this fix and another PR I sent to synapse? We have to do a milestone
>>> release of API Manager this week.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Mon, Oct 12, 2015 at 11:43 AM, Nuwan Dias  wrote:
>>>
 Thanks a lot Chanaka.

 On Mon, Oct 12, 2015 at 11:39 AM, Chanaka Fernando 
 wrote:

> Hi All,
>
> This issue is fixed with the following PR [1]. Thanks for reporting
> and helping us to figure out the issue.
>
> [1] https://github.com/wso2/carbon-mediation/pull/467
>
> On Fri, Oct 9, 2015 at 3:41 PM, Chanaka Fernando 
> wrote:
>
>> Hi Sameera,
>>
>> Your judgment is correct and it helped us to find the root cause :).
>> I'll fix the code from carbon-mediation side. Thanks for your input.
>>
>> On Fri, Oct 9, 2015 at 3:19 PM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Chanaka,
>>>
>>> You don't need to destroy the current context. This part is handle
>>> by the Kernel code. Users of the CarbonContext API do not need to worry
>>> about destroying the context.
>>>
>>> Who has done this change? So my initial judgment is correct. :)
>>> Stack cannot become empty.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Thu, Oct 8, 2015 at 6:14 PM, Chanaka Fernando 
>>> wrote:
>>>
 Hi All,

 At last, I was able to find the root cause for this behavior. This
 is actually coming from carbon-mediation code. What actually happens is
 that when ESB starts with a tenant, it will not load the tenant until 
 it
 receives the first request. When It receives the first request, it will
 call the MultitenantMessageReceiver.processRequest() method. Within 
 this
 method, it will call the following method.

 PrivilegedCarbonContext.startTenantFlow();


 This will get the ThreadLocal variable *parentContextHolderStack *and
 get the stack  and push the carbonContextDataHolder object to the
 stack. After this, tenant loading happens and within the 
 initialization of
 the carbon mediation registry we have the following code segment.

 *org.wso2.carbon.mediation.registry.WSO2Registry.java*

 /**
  *  Carbon Kernel mandates to set Threadlocal before calling anything 
 in kernel
  */
 private void setTenantInfo() {
 // Preserve user name
 String username = 
 PrivilegedCarbonContext.getThreadLocalCarbonContext().getUsername();
 *PrivilegedCarbonContext.destroyCurrentContext();*
 PrivilegedCarbonContext cc = 
 PrivilegedCarbonContext.getThreadLocalCarbonContext();
 cc.setTenantDomain(domain);
 cc.setTenantId(tenantId);
 if (username != null) { // Set back the user name
 
 PrivilegedCarbonContext.getThreadLocalCarbonContext().setUsername(username);
 }
 }

 Within the above method following line causes the issue.

 PrivilegedCarbonContext.destroyCurrentContext();

 When this method is called, it will reset the *parentContextHolderStack
 *and the initial object push into the stack is destroyed. Then
 after tenant loading, within the
 MultitenantMessageReceiver.processRequest() method, it tries to end the
 tenant flow within finally block and try to pop the object which it 
 pushes
 early. But right now, we have a new context stack and it will throw the
 emptyStackException due to that.

 @Sameera/KasunG: Do we really need to use the following code
 segment within the above method?


 *PrivilegedCarbonContext.destroyCurrentContext();*

 I saw this method called within carbon-mediation components in 3
 different locations. AFAIU, we don't need to destroy the current 
 

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Ramith Jayasinghe]

yes.

On Tue, Jan 26, 2016 at 4:06 PM, Nilmini Perera  wrote:

> Hi Hasitha,
> In short, WSO2 MB should always be run on 64bit JDK.
> Is this statement correct?
>
> Regards,
> Nilmini
>
> On Tue, Dec 22, 2015 at 11:30 AM, Hasitha Hiranya 
> wrote:
>
>> Is this worth mentioning in docs anyway?
>>
>> On Tue, Dec 22, 2015 at 11:21 AM, Nadeesha Meegoda 
>> wrote:
>>
>>> Hi all,
>>>
>>> Thanks for figuring this out.
>>>
>>> Regards,
>>> Nadeesha
>>>
>>> On Tue, Dec 22, 2015 at 11:19 AM, Isuru Perera  wrote:
>>>
 Yes! The 32-bit JVM cannot allocate enough memory for the MB.

 On Tue, Dec 22, 2015 at 11:14 AM, Jason De Silva 
 wrote:

> Hi Nadeesha,
>
> As Isuru pointed since you have tried it out with 32 bit JDK which
> will not be able to allocate 2 gb memory [1] whereas MB needs 2 gb memory
> [2] which was the cause for the product to not start on 32 bit JDK.
>
> [1]
> http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#gc_heap_32bit
> [2] https://docs.wso2.com/display/MB300/Installation+Prerequisites
>
> Regards,
>
>
> On Mon, Dec 21, 2015 at 9:20 PM, Nadeesha Meegoda 
> wrote:
>
>> Hi Isuru,
>>
>> Yes I am running MB on the 32-bit JDK. I have installed both 32 bit
>> and 64 bit JDK in my machine. However other products seems to start 
>> without
>> any error in both 32bit and 64bit JDK. I also checked MB in 64bit JDK 
>> now.
>> MB starts fine with that.
>>
>>
>> Thanks,
>> Nadeesha
>>
>> On Mon, Dec 21, 2015 at 6:13 PM, Isuru Perera 
>> wrote:
>>
>>> Looks like you are running MB on the 32-bit JDK. Can you try with
>>> 64-bit JDK?
>>>
>>> On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda <
>>> nadees...@wso2.com> wrote:
>>>
 Hi Yasassri,

 Thanks. I will investigate on this more. The other products in same
 directory are starting without any issue. That's why I raised the 
 concern.

 Regards,
 Nadeesha

 On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake <
 yasas...@wso2.com> wrote:

> Hi,
>
> We were able to successfully start MB without any issue with Java
> 1.8 and with Java 1.7 in windows environment. I tested with your 
> exact java
> version as well (1.7.0_79). I believe you haven't set your environment
> variables properly. As per your error it says "The system cannot
> find the file specified.".  I think this is self explanatory.
>
> Please compare with the following logs and check whats missing.
>
> TID: [] [] [2015-12-21 10:23:49,834]  WARN
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
> determine dialect of the StAX implementation at
> bundleresource://13.fwk2427473/
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
> TID: [] [] [2015-12-21 10:23:49,834]  WARN
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
> determine dialect of the StAX implementation at
> bundleresource://13.fwk2427473/
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
> TID: [] [] [2015-12-21 10:23:49,756]  INFO
> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting 
> BundleContext
> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating 
> System :
> Windows Server 2012 R2 6.3, amd64
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home  
>   :
> C:\Program Files\Java\jdk1.7.0_79\jre
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version   
>   :
> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM
>   :
> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> 

Re: [Dev] Puppet modules - Cleaned up jdk and product distribution

[Chamila De Alwis]

Great work Sajith! Nice to see you were able to reduce the size of the
image by over 1GB. :)


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Tue, Jan 26, 2016 at 1:44 PM, Imesh Gunaratne  wrote:

> Great work Sajith!! It's really important for us to reduce the docker
> image size.
>
> Thanks
>
> On Tue, Jan 26, 2016 at 11:51 AM, Sajith Kariyawasam 
> wrote:
>
>> Hi Devs,
>>
>> With the current puppet modules, when docker images are built it sized
>> around 2.216 GB and it seemed product and JDK binaries were not removed
>> after the installation.
>>
>> I have now updated the puppet modules to,
>>
>> 1) Remove java cache directory after java installation
>> 2) Remove wso2 product pack after installation
>>
>> Ideally, JDK distribution should be cleaned up by the 7-terminals [1]
>> module. I have sent a PR [2] with the improvement, until its merged and
>> available in puppet forge I have fixed that in java.pp
>>
>> Now the image size is reduced to around 1.417 GB
>>
>> [1] https://github.com/7terminals/puppet-java.git
>> [2] https://github.com/7terminals/puppet-java/pull/14
>>
>> Thanks,
>> Sajith
>>
>> --
>> Sajith Kariyawasam
>> *Committer and PMC member, Apache Stratos, *
>> *WSO2 Inc.; http://wso2.com *
>> *Mobile: 0772269575*
>>
>
>
>
> --
> *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] Request the PRs to be merged (analytics-common & event-processing repos)

[Ruwan Yatawara]

Thanks Everyone!

Thanks and Regards,

Ruwan Yatawara

Senior Software Engineer,
WSO2 Inc.

email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com


On Wed, Jan 27, 2016 at 11:19 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Carbon event processing 2.0.11 is released..
>
>
>
> On Wed, Jan 27, 2016 at 10:59 AM, Sachith Withana 
> wrote:
>
>> Carbon analytics common is released: version 5.0.9
>>
>> On Tue, Jan 26, 2016 at 4:55 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Jan 26, 2016 at 4:52 PM, Sachith Withana 
>>> wrote:
>>>
 @Mohan: Do we have to release Siddhi as well? since there's a
 dependency on Siddhi from carbon-analytics-common.

>>>
>>> No need a Siddhi release.. Please use the existing released Siddhi
>>> dependency..
>>>
>>>
 On Tue, Jan 26, 2016 at 4:35 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

> By the Sachith, please update once you are done with
> carbon-analytics-common release..  Then I can move with
> carbon-event-processing release..
>
> On Tue, Jan 26, 2016 at 3:23 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana 
>> wrote:
>>
>>> @Mohan: I can release the analytics-common now, if you guys are not
>>> doing any active development on it.
>>>
>>
>> Sachith, please go ahead and release it..
>>
>>
>>>
>>> On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara 
>>> wrote:
>>>
 Actually I was about to ask the same thing. Please correct me if I
 am wrong, but i didnt see there being a reference to event-processing 
 in
 analytics-common.

 Thanks and Regards,

 Ruwan Yatawara

 Senior Software Engineer,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 blog : http://ruwansrants.blogspot.com/
 www: :http://wso2.com


 On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

>
>
> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana  > wrote:
>
>> Hi Mohan,
>>
>> Can you merge and release the Carbon-event-processing first? so
>> that It can be included in carbon-analytics-common release?
>>
>
> Sorry, why do you need a Carbon-event-processing release first?
> carbon-analytics-common is not depend on that..
>
>
>
>>
>> Thanks,
>> Sachith
>>
>> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara > > wrote:
>>
>>> Hi Team,
>>>
>>> Ran in to a few OSGI issues again whilst packing DAS components
>>> in IoTS and did some fixes. Can we get the below PRs ([1] & [2]) 
>>> merged to
>>> the respective Repos and get them released?
>>>
>>> There is another fix that need to go in to carbon-analytics. But
>>> in order to add that fix, the following two repos need to be 
>>> released as
>>> they are inter-dependent.
>>>
>>> [1] - https://github.com/wso2/carbon-event-processing/pull/197
>>> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>


>>>
>>>
>>> --
>>> Sachith Withana
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> E-mail: sachith AT wso2.com
>>> M: +94715518127
>>> Linked-In: 
>>> https://lk.linkedin.com/in/sachithwithana
>>>
>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Senior Software Engineer,*
>> *Data 

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Anjana Fernando]

Hi Gimantha,

On Wed, Jan 27, 2016 at 11:26 AM, Gimantha Bandara 
wrote:

> @Vithulan/Malith
>
>
> On Tue, Jan 26, 2016 at 7:38 PM, Malith Dhanushka  wrote:
>
>> Hi Gimantha,
>>
>> I Think we can add Unique Count, Standard deviation and Percentile under
>> default matrices right?
>>
>
>  @Anjana Shall we add these matrices under default aggregate methods or
> shall we provide a extension point and these?
>

Yes, things we think that would be useful, we have to implement OOTB. And
also, we have to implement the extension as well.

Cheers,
Anjana.


>
>> And do we already have API support for grouping aggregations like range
>> and histograms?
>>
>
> Yes, we have APIs for ranges and histograms already
>
>>
>> Thanks,
>> Malith
>>
>> On Tue, Jan 26, 2016 at 6:51 PM, Vithulan Vijayanandan > > wrote:
>>
>>> Hi Rukshan,
>>> Oh. Thank you for the prompt reply and the links.
>>>
>>> Hi Gimantha,
>>> Yes, can we be able to have,
>>>
>>>- Unique Count - It will get a count in a field about how many
>>>unique values it has.
>>>- Standard deviation
>>>- Percentile
>>>
>>> I will look at Unique count, Standard deviation and Percentile. I think
> Unique count is something DAS already supports.
>
>>
>>>-
>>>
>>>And also some grouping aggregations,
>>>
>>>- Time-stamp based aggregation - Where we should be able to group
>>>the logs based on timestamp (Automatically/Hour/Day/etc)
>>>
>>> Given a specific timestamp range you can group the logs
>
>>
>>>- Date range - Where we should be able to group and analyze the logs
>>>within specific date range.
>>>- Integer range based aggregation - Where we should be able to group
>>>the events based on range of an integer field.
>>>
>>> Also you can group logs using Date range ( I think still if this is
> epoch time it comes under integer ranges. So since you can group by integer
> ranges using DAS, you will be able to group by date also.
>
>>
>>>- An aggregation where we should be able to compare all the log
>>>fields against existing all metric aggregations (count,sum,min,max,avg).
>>>(Eg:log_level vs count)
>>>
>>> This is can be done by defining the field as a "facet" field and using
> aggregate methods provided by DAS.
>
>>
>>> Thanks.
>>>
>>> Regards,
>>>
>>> Vithulan
>>>
>>> On Tue, Jan 26, 2016 at 4:25 PM, Gimantha Bandara 
>>> wrote:
>>>
 Hi Vithulan,

 Other than the aggregates Rukshan has mentioned, DAS supports COUNT
 also. Are there any other aggregates required log analyzer functionalities?

 On Tue, Jan 26, 2016 at 3:31 PM, Rukshan Premathunga 
 wrote:

> Hi Vithulan,
>
> if you mean aggregate functions, known functions are
>
>- MAX
>- MIN
>- AVG
>- SUM
>
> also you can refer these[1][2] docs for more about the API.
>
> [1]
> https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
> [2]
> http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html
>
> Thanks and Regards.
>
>
> On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan <
> vithu...@wso2.com> wrote:
>
>> Hi,
>>
>> We need to have data aggregations for LogAnalyzer, log search
>> requirement. What are the aggregations that are available in DAS REST API
>> currently?
>>
>> Thanks.
>>
>> Regards,
>> Vithulan.
>>
>> --
>> *Vithulan MV*
>>
>> Intern-Software Engineering
>> WSO2, Inc : wso2.com
>> Mobile: +94712540524
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> 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

>>>
>>>
>>>
>>> --
>>> *Vithulan MV*
>>>
>>> Intern-Software Engineering
>>> WSO2, Inc : wso2.com
>>> Mobile: +94712540524
>>>
>>
>>
>>
>> --
>> Malith Dhanushka
>> Senior Software Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com *
>> *Mobile*  : +94 716 506 693
>>
>
>
>
> --
> Gimantha Bandara
> Software Engineer
> WSO2. Inc : http://wso2.com
> Mobile : +94714961919
>



-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] 1.0, is appended to the version field when try to publish a mobile app

[Harshan Liyanage]

Hi,

I'm getting the following exception when try to add a mobile app using the
publisher console.

[2016-01-27 12:48:27,494] ERROR {JAGGERY.apis.v1.asset_api_router:jag} -
 org.mozilla.javascript.EcmaError: TypeError: Cannot find function trim in
object 1.0,2.5.0.
(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js#89)
at
org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3687)
at
org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3665)
at org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3693)
at org.mozilla.javascript.ScriptRuntime.typeError2(ScriptRuntime.java:3712)
at
org.mozilla.javascript.ScriptRuntime.notFunctionError(ScriptRuntime.java:3783)
at
org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThisHelper(ScriptRuntime.java:2269)
at
org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThis(ScriptRuntime.java:2251)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:83)
at
org.jaggeryjs.rhino.publisher.modules.ext.scripts.validations.c1._c_handleField_5(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js:89)
at
org.jaggeryjs.rhino.publisher.modules.ext.scripts.validations.c1.call(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.publisher.modules.ext.scripts.validations.c1._c_handleTable_4(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js:59)
at
org.jaggeryjs.rhino.publisher.modules.ext.scripts.validations.c1.call(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.publisher.modules.ext.scripts.validations.c1._c_execute_3(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js:39)
at
org.jaggeryjs.rhino.publisher.modules.ext.scripts.validations.c1.call(/publisher/modules/ext/scripts/validations/mandatory.field.validator.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.validations.c0._c_anonymous_5(/publisher/modules/validations/validation.manager.js:62)
at
org.jaggeryjs.rhino.publisher.modules.validations.c0.call(/publisher/modules/validations/validation.manager.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.ext.core.c3._c_anonymous_9(/publisher/modules/ext/core/extension.management.js:119)
at
org.jaggeryjs.rhino.publisher.modules.ext.core.c3.call(/publisher/modules/ext/core/extension.management.js)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1._c_addNewMobileApp_26(/publisher/apis/v1/asset_api_router.jag:949)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1.call(/publisher/apis/v1/asset_api_router.jag)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1._c_anonymous_18(/publisher/apis/v1/asset_api_router.jag:373)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1.call(/publisher/apis/v1/asset_api_router.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.publisher.modules.c4._c_anonymous_12(/publisher/modules/router-g.js:183)
at
org.jaggeryjs.rhino.publisher.modules.c4.call(/publisher/modules/router-g.js)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1._c_anonymous_1(/publisher/apis/v1/asset_api_router.jag:1285)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1.call(/publisher/apis/v1/asset_api_router.jag)
at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c6._c_anonymous_17(/publisher/modules/publisher.js:438)
at
org.jaggeryjs.rhino.publisher.modules.c6.call(/publisher/modules/publisher.js)
at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
at
org.jaggeryjs.rhino..scripts.c0._c_anonymous_17(/scripts/server.js:266)
at org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c6._c_anonymous_16(/publisher/modules/publisher.js:433)
at
org.jaggeryjs.rhino.publisher.modules.c6.call(/publisher/modules/publisher.js)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1._c_script_0(/publisher/apis/v1/asset_api_router.jag:17)
at
org.jaggeryjs.rhino.publisher.apis.v_1.c1.call(/publisher/apis/v1/asset_api_router.jag)
at 

Re: [Dev] Evaluating the possibility of applying Goldmansachs ConcurrentHashMap in MB

[Malaka Gangananda]

Hi,

Here I have attached the JMH benchmark.You can access source code using
following link and please note that this is written for my evaluation
purpose of two data structures only.

https://github.com/malakaganga/jmh-gc-csl

Thanks!

On Tue, Jan 26, 2016 at 2:23 PM, Isuru Perera  wrote:

> Hi Malaka,
>
> Great work! Could you please share the JMH benchmark?
>
> Thanks!
>
> On Tue, Jan 26, 2016 at 10:05 AM, Ramith Jayasinghe 
> wrote:
>
>> Hi Malaka,
>>  lets report these findings on architecture group as a investigation we
>> did.
>> regards
>> Ramtih
>>
>> On Tue, Jan 26, 2016 at 8:16 AM, Malaka Gangananda 
>> wrote:
>>
>>> Hi,
>>>
>>> While profiling the MB we found out that there is a performance bottle
>>> neck in using util.ConcurrentSkipListMap. Because every time size call is
>>> made it has to loop through the data structure so it takes O(n) time. But
>>> looking at GC ConcurrentHashMap we found out that it only takes constant
>>> time (O(1) time) to make the size call.Other operations on GC
>>> ConcurrentHashMap are also faster than uti.ConcurrentSkipListMap.
>>>
>>> Here I have attached JMH Benchmark results which acquired by testing
>>> util.ConcurrentSkipListMap vs GC ConcurrentHashMap
>>>
>>> ​​​
>>>  ConcurrentSkipListMap Vs Goldmansachs Concurre...
>>> 
>>> ​
>>>
>>> Malaka Gangananda
>>> Software Engineer Intern
>>> mobile:0713564340
>>> mala...@wso2.com
>>> 
>>>
>>
>>
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 777542851
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
Malaka Gangananda
Software Engineer Intern
mobile:0713564340
mala...@wso2.com

Benchmark(element)  (size)  
Mode  Cnt   Score   Error  Units
GSVsConSkipListMap.sizeCallConSkipList N/A 100  
avgt   20 877.625 ±25.773  ns/op
GSVsConSkipListMap.sizeCallConSkipList:·stack  N/A 100  
avgt  NaN---
GSVsConSkipListMap.sizeCallConSkipList N/A1000  
avgt   20   12996.301 ±   551.250  ns/op
GSVsConSkipListMap.sizeCallConSkipList:·stack  N/A1000  
avgt  NaN---
GSVsConSkipListMap.sizeCallConSkipList N/A   1  
avgt   20  158088.796 ± 13281.221  ns/op
GSVsConSkipListMap.sizeCallConSkipList:·stack  N/A   1  
avgt  NaN---
GSVsConSkipListMap.sizeCallConSkipList N/A   15000  
avgt   20  321088.363 ± 83457.575  ns/op
GSVsConSkipListMap.sizeCallConSkipList:·stack  N/A   15000  
avgt  NaN---
GSVsConSkipListMap.sizeCallGCHashMap   N/A 100  
avgt   20  30.233 ± 9.497  ns/op
GSVsConSkipListMap.sizeCallGCHashMap:·stackN/A 100  
avgt  NaN---
GSVsConSkipListMap.sizeCallGCHashMap   N/A1000  
avgt   20  30.862 ± 8.930  ns/op
GSVsConSkipListMap.sizeCallGCHashMap:·stackN/A1000  
avgt  NaN---
GSVsConSkipListMap.sizeCallGCHashMap   N/A   1  
avgt   20  78.022 ±21.543  ns/op
GSVsConSkipListMap.sizeCallGCHashMap:·stackN/A   1  
avgt  NaN---
GSVsConSkipListMap.sizeCallGCHashMap   N/A   15000  
avgt   20  91.657 ±34.659  ns/op
GSVsConSkipListMap.sizeCallGCHashMap:·stackN/A   15000  
avgt  NaN---
GSVsConSkipListMapPutOpNGetOp.getCallConSkipList 2 N/A  
avgt   20 891.813 ±   302.100  ns/op
GSVsConSkipListMapPutOpNGetOp.getCallConSkipList:·stack  2 N/A  
avgt  NaN---
GSVsConSkipListMapPutOpNGetOp.getCallConSkipList 5 N/A  
avgt   20 737.880 ±   250.744  ns/op
GSVsConSkipListMapPutOpNGetOp.getCallConSkipList:·stack  5 N/A  
avgt  NaN---
GSVsConSkipListMapPutOpNGetOp.getCallConSkipList 9 N/A  
avgt   20 685.134 ±   223.527  ns/op
GSVsConSkipListMapPutOpNGetOp.getCallConSkipList:·stack  9 N/A  
avgt  NaN---
GSVsConSkipListMapPutOpNGetOp.getCallGSHashMap   

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Sinthuja Ragendran]

On Wed, Jan 27, 2016 at 12:42 PM, Anjana Fernando  wrote:

> Hi Gimantha,
>
> On Wed, Jan 27, 2016 at 11:26 AM, Gimantha Bandara 
> wrote:
>
>> @Vithulan/Malith
>>
>>
>> On Tue, Jan 26, 2016 at 7:38 PM, Malith Dhanushka 
>> wrote:
>>
>>> Hi Gimantha,
>>>
>>> I Think we can add Unique Count, Standard deviation and Percentile
>>> under default matrices right?
>>>
>>
>>  @Anjana Shall we add these matrices under default aggregate methods or
>> shall we provide a extension point and these?
>>
>
> Yes, things we think that would be useful, we have to implement OOTB. And
> also, we have to implement the extension as well.
>

yeah +1, also we should have a document about the extension on how to use
it, etc similar to doc about spark UDF [1]. Do we have page on what are
the OOTB supported aggregate methods? I wasn't able to find it in the DAS
docs pages, in case if we don't have it, then we need to add docs on that
too.

[1]
https://docs.wso2.com/display/DAS300/Creating+Spark+User+Defined+Functions

Thanks,
Sinthuja.

>
> Cheers,
> Anjana.
>
>
>>
>>> And do we already have API support for grouping aggregations like range
>>> and histograms?
>>>
>>
>> Yes, we have APIs for ranges and histograms already
>>
>>>
>>> Thanks,
>>> Malith
>>>
>>> On Tue, Jan 26, 2016 at 6:51 PM, Vithulan Vijayanandan <
>>> vithu...@wso2.com> wrote:
>>>
 Hi Rukshan,
 Oh. Thank you for the prompt reply and the links.

 Hi Gimantha,
 Yes, can we be able to have,

- Unique Count - It will get a count in a field about how many
unique values it has.
- Standard deviation
- Percentile

 I will look at Unique count, Standard deviation and Percentile. I think
>> Unique count is something DAS already supports.
>>
>>>
-

And also some grouping aggregations,

- Time-stamp based aggregation - Where we should be able to group
the logs based on timestamp (Automatically/Hour/Day/etc)

 Given a specific timestamp range you can group the logs
>>
>>>
- Date range - Where we should be able to group and analyze the
logs within specific date range.
- Integer range based aggregation - Where we should be able to
group the events based on range of an integer field.

 Also you can group logs using Date range ( I think still if this is
>> epoch time it comes under integer ranges. So since you can group by integer
>> ranges using DAS, you will be able to group by date also.
>>
>>>
- An aggregation where we should be able to compare all the log
fields against existing all metric aggregations (count,sum,min,max,avg).
(Eg:log_level vs count)

 This is can be done by defining the field as a "facet" field and using
>> aggregate methods provided by DAS.
>>
>>>
 Thanks.

 Regards,

 Vithulan

 On Tue, Jan 26, 2016 at 4:25 PM, Gimantha Bandara 
 wrote:

> Hi Vithulan,
>
> Other than the aggregates Rukshan has mentioned, DAS supports COUNT
> also. Are there any other aggregates required log analyzer 
> functionalities?
>
> On Tue, Jan 26, 2016 at 3:31 PM, Rukshan Premathunga  > wrote:
>
>> Hi Vithulan,
>>
>> if you mean aggregate functions, known functions are
>>
>>- MAX
>>- MIN
>>- AVG
>>- SUM
>>
>> also you can refer these[1][2] docs for more about the API.
>>
>> [1]
>> https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
>> [2]
>> http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html
>>
>> Thanks and Regards.
>>
>>
>> On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan <
>> vithu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We need to have data aggregations for LogAnalyzer, log search
>>> requirement. What are the aggregations that are available in DAS REST 
>>> API
>>> currently?
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Vithulan.
>>>
>>> --
>>> *Vithulan MV*
>>>
>>> Intern-Software Engineering
>>> WSO2, Inc : wso2.com
>>> Mobile: +94712540524
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>> ___
>> 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
>



 --
 *Vithulan MV*

 Intern-Software 

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Sachith Withana]

Carbon analytics common is released: version 5.0.9

On Tue, Jan 26, 2016 at 4:55 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Tue, Jan 26, 2016 at 4:52 PM, Sachith Withana  wrote:
>
>> @Mohan: Do we have to release Siddhi as well? since there's a dependency
>> on Siddhi from carbon-analytics-common.
>>
>
> No need a Siddhi release.. Please use the existing released Siddhi
> dependency..
>
>
>> On Tue, Jan 26, 2016 at 4:35 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> By the Sachith, please update once you are done with
>>> carbon-analytics-common release..  Then I can move with
>>> carbon-event-processing release..
>>>
>>> On Tue, Jan 26, 2016 at 3:23 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>


 On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana 
 wrote:

> @Mohan: I can release the analytics-common now, if you guys are not
> doing any active development on it.
>

 Sachith, please go ahead and release it..


>
> On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara 
> wrote:
>
>> Actually I was about to ask the same thing. Please correct me if I am
>> wrong, but i didnt see there being a reference to event-processing in
>> analytics-common.
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>> On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
>>> wrote:
>>>
 Hi Mohan,

 Can you merge and release the Carbon-event-processing first? so
 that It can be included in carbon-analytics-common release?

>>>
>>> Sorry, why do you need a Carbon-event-processing release first?
>>> carbon-analytics-common is not depend on that..
>>>
>>>
>>>

 Thanks,
 Sachith

 On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
 wrote:

> Hi Team,
>
> Ran in to a few OSGI issues again whilst packing DAS components in
> IoTS and did some fixes. Can we get the below PRs ([1] & [2]) merged 
> to the
> respective Repos and get them released?
>
> There is another fix that need to go in to carbon-analytics. But
> in order to add that fix, the following two repos need to be released 
> as
> they are inter-dependent.
>
> [1] - https://github.com/wso2/carbon-event-processing/pull/197
> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>


 --
 Sachith Withana
 Software Engineer; WSO2 Inc.; http://wso2.com
 E-mail: sachith AT wso2.com
 M: +94715518127
 Linked-In: 
 https://lk.linkedin.com/in/sachithwithana

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Senior Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



 --
 *V. Mohanadarshan*
 *Senior Software Engineer,*
 *Data Technologies Team,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: mo...@wso2.com
 phone:(+94) 771117673

>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Senior Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com 

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Gimantha Bandara]

@Vithulan/Malith


On Tue, Jan 26, 2016 at 7:38 PM, Malith Dhanushka  wrote:

> Hi Gimantha,
>
> I Think we can add Unique Count, Standard deviation and Percentile under
> default matrices right?
>

 @Anjana Shall we add these matrices under default aggregate methods or
shall we provide a extension point and these?

>
> And do we already have API support for grouping aggregations like range
> and histograms?
>

Yes, we have APIs for ranges and histograms already

>
> Thanks,
> Malith
>
> On Tue, Jan 26, 2016 at 6:51 PM, Vithulan Vijayanandan 
> wrote:
>
>> Hi Rukshan,
>> Oh. Thank you for the prompt reply and the links.
>>
>> Hi Gimantha,
>> Yes, can we be able to have,
>>
>>- Unique Count - It will get a count in a field about how many unique
>>values it has.
>>- Standard deviation
>>- Percentile
>>
>> I will look at Unique count, Standard deviation and Percentile. I think
Unique count is something DAS already supports.

>
>>-
>>
>>And also some grouping aggregations,
>>
>>- Time-stamp based aggregation - Where we should be able to group the
>>logs based on timestamp (Automatically/Hour/Day/etc)
>>
>> Given a specific timestamp range you can group the logs

>
>>- Date range - Where we should be able to group and analyze the logs
>>within specific date range.
>>- Integer range based aggregation - Where we should be able to group
>>the events based on range of an integer field.
>>
>> Also you can group logs using Date range ( I think still if this is epoch
time it comes under integer ranges. So since you can group by integer
ranges using DAS, you will be able to group by date also.

>
>>- An aggregation where we should be able to compare all the log
>>fields against existing all metric aggregations (count,sum,min,max,avg).
>>(Eg:log_level vs count)
>>
>> This is can be done by defining the field as a "facet" field and using
aggregate methods provided by DAS.

>
>> Thanks.
>>
>> Regards,
>>
>> Vithulan
>>
>> On Tue, Jan 26, 2016 at 4:25 PM, Gimantha Bandara 
>> wrote:
>>
>>> Hi Vithulan,
>>>
>>> Other than the aggregates Rukshan has mentioned, DAS supports COUNT
>>> also. Are there any other aggregates required log analyzer functionalities?
>>>
>>> On Tue, Jan 26, 2016 at 3:31 PM, Rukshan Premathunga 
>>> wrote:
>>>
 Hi Vithulan,

 if you mean aggregate functions, known functions are

- MAX
- MIN
- AVG
- SUM

 also you can refer these[1][2] docs for more about the API.

 [1]
 https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
 [2]
 http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html

 Thanks and Regards.


 On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan <
 vithu...@wso2.com> wrote:

> Hi,
>
> We need to have data aggregations for LogAnalyzer, log search
> requirement. What are the aggregations that are available in DAS REST API
> currently?
>
> Thanks.
>
> Regards,
> Vithulan.
>
> --
> *Vithulan MV*
>
> Intern-Software Engineering
> WSO2, Inc : wso2.com
> Mobile: +94712540524
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 ___
 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
>>>
>>
>>
>>
>> --
>> *Vithulan MV*
>>
>> Intern-Software Engineering
>> WSO2, Inc : wso2.com
>> Mobile: +94712540524
>>
>
>
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>



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

[Dev] Carbon Messaging - Refining Code

[Imesh Gunaratne]

Hi Devs,

I have sent a pull request to carbon-messaging to add a missing license
header and remove blank lines, please review and merge:

https://github.com/wso2/carbon-messaging/pull/4

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

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Mohanadarshan Vivekanandalingam]

Carbon event processing 2.0.11 is released..



On Wed, Jan 27, 2016 at 10:59 AM, Sachith Withana  wrote:

> Carbon analytics common is released: version 5.0.9
>
> On Tue, Jan 26, 2016 at 4:55 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Tue, Jan 26, 2016 at 4:52 PM, Sachith Withana 
>> wrote:
>>
>>> @Mohan: Do we have to release Siddhi as well? since there's a dependency
>>> on Siddhi from carbon-analytics-common.
>>>
>>
>> No need a Siddhi release.. Please use the existing released Siddhi
>> dependency..
>>
>>
>>> On Tue, Jan 26, 2016 at 4:35 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>
 By the Sachith, please update once you are done with
 carbon-analytics-common release..  Then I can move with
 carbon-event-processing release..

 On Tue, Jan 26, 2016 at 3:23 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

>
>
> On Tue, Jan 26, 2016 at 3:06 PM, Sachith Withana 
> wrote:
>
>> @Mohan: I can release the analytics-common now, if you guys are not
>> doing any active development on it.
>>
>
> Sachith, please go ahead and release it..
>
>
>>
>> On Tue, Jan 26, 2016 at 3:03 PM, Ruwan Yatawara 
>> wrote:
>>
>>> Actually I was about to ask the same thing. Please correct me if I
>>> am wrong, but i didnt see there being a reference to event-processing in
>>> analytics-common.
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>> On Tue, Jan 26, 2016 at 3:01 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>


 On Tue, Jan 26, 2016 at 2:21 PM, Sachith Withana 
 wrote:

> Hi Mohan,
>
> Can you merge and release the Carbon-event-processing first? so
> that It can be included in carbon-analytics-common release?
>

 Sorry, why do you need a Carbon-event-processing release first?
 carbon-analytics-common is not depend on that..



>
> Thanks,
> Sachith
>
> On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara 
> wrote:
>
>> Hi Team,
>>
>> Ran in to a few OSGI issues again whilst packing DAS components
>> in IoTS and did some fixes. Can we get the below PRs ([1] & [2]) 
>> merged to
>> the respective Repos and get them released?
>>
>> There is another fix that need to go in to carbon-analytics. But
>> in order to add that fix, the following two repos need to be 
>> released as
>> they are inter-dependent.
>>
>> [1] - https://github.com/wso2/carbon-event-processing/pull/197
>> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



 --
 *V. Mohanadarshan*
 *Senior Software Engineer,*
 *Data Technologies Team,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: mo...@wso2.com
 phone:(+94) 771117673

>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Senior Software Engineer,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>



 --
 *V. Mohanadarshan*
 *Senior Software Engineer,*
 *Data Technologies Team,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: mo...@wso2.com
 phone:(+94) 771117673

>>>
>>>
>>>
>>> --
>>> Sachith Withana

[Dev] [DEV] [IS] Footer in SSO authentication page goes above on text fields in mobile view

[Lalanke Athauda]

Hi,
Tried to login to DS portal when SSO is enabled through a mobile, the
footer of the page goes above text fields and covers the text fields.
Though we can enter the username and passwords, it's bit confusing to find
the fields. Sample screenshot is attached.
We are using identity version 5.0.7. Appreciate your ideas to solve this.


​
Thanks.

-- 
Lalanke Athauda
Software Engineer
WSO2 Inc.
Mobile: 0772264301
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] New docker images for WSO2 products based on puppet modules

[Pubudu Gunatilaka]

Hi Devs,

Based on the latest puppet modules [1] we have recreated the Docker images
[2] for following WSO2 Products.

   - WSO2 API Manager
   - WSO2 Application Server
   - WSO2 Business Process Server
   - WSO2 Business Rules Server
   - WSO2 Complex Event Processor
   - WSO2 Data Analytics Server
   - WSO2 Data Services Server
   - WSO2 Enterprise Service Bus
   - WSO2 Enterprise Store
   - WSO2 Governance Registry
   - WSO2 Identity Server
   - WSO2 Message Broker

I have tested all the docker images and anyone can try out following [3].
For creating docker images you can clone the repo and use it until we
release the first version of puppet modules .

*What's new in Docker Images*

1. Puppet modules are introduced for docker images.
2. Configurator is removed and puppet apply is used.
3. Docker image is pre-built and server configurations happens at image
build.
4. Docker images are created per product profile. (eg: default, manager,
worker)

[1] - https://github.com/wso2/puppet-modules/
[2] - https://github.com/wso2-incubator/kubernetes-artifacts
[3] -
https://github.com/wso2-incubator/kubernetes-artifacts#building-the-docker-images


Thank you!
-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774079049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Evaluating the possibility of applying Goldmansachs ConcurrentHashMap in MB

[Isuru Perera]

Hi Malaka,

Great work! Could you please share the JMH benchmark?

Thanks!

On Tue, Jan 26, 2016 at 10:05 AM, Ramith Jayasinghe  wrote:

> Hi Malaka,
>  lets report these findings on architecture group as a investigation we
> did.
> regards
> Ramtih
>
> On Tue, Jan 26, 2016 at 8:16 AM, Malaka Gangananda 
> wrote:
>
>> Hi,
>>
>> While profiling the MB we found out that there is a performance bottle
>> neck in using util.ConcurrentSkipListMap. Because every time size call is
>> made it has to loop through the data structure so it takes O(n) time. But
>> looking at GC ConcurrentHashMap we found out that it only takes constant
>> time (O(1) time) to make the size call.Other operations on GC
>> ConcurrentHashMap are also faster than uti.ConcurrentSkipListMap.
>>
>> Here I have attached JMH Benchmark results which acquired by testing
>> util.ConcurrentSkipListMap vs GC ConcurrentHashMap
>>
>> ​​​
>>  ConcurrentSkipListMap Vs Goldmansachs Concurre...
>> 
>> ​
>>
>> Malaka Gangananda
>> Software Engineer Intern
>> mobile:0713564340
>> mala...@wso2.com
>> 
>>
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

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

Re: [Dev] Request the PRs to be merged (analytics-common & event-processing repos)

[Sachith Withana]

Hi Mohan,

Can you merge and release the Carbon-event-processing first? so that It can
be included in carbon-analytics-common release?

Thanks,
Sachith

On Tue, Jan 26, 2016 at 12:36 PM, Ruwan Yatawara  wrote:

> Hi Team,
>
> Ran in to a few OSGI issues again whilst packing DAS components in IoTS
> and did some fixes. Can we get the below PRs ([1] & [2]) merged to the
> respective Repos and get them released?
>
> There is another fix that need to go in to carbon-analytics. But in order
> to add that fix, the following two repos need to be released as they are
> inter-dependent.
>
> [1] - https://github.com/wso2/carbon-event-processing/pull/197
> [2] - https://github.com/wso2/carbon-analytics-common/pull/174
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Puppet modules - Cleaned up jdk and product distribution

[Imesh Gunaratne]

Great work Sajith!! It's really important for us to reduce the docker image
size.

Thanks

On Tue, Jan 26, 2016 at 11:51 AM, Sajith Kariyawasam 
wrote:

> Hi Devs,
>
> With the current puppet modules, when docker images are built it sized
> around 2.216 GB and it seemed product and JDK binaries were not removed
> after the installation.
>
> I have now updated the puppet modules to,
>
> 1) Remove java cache directory after java installation
> 2) Remove wso2 product pack after installation
>
> Ideally, JDK distribution should be cleaned up by the 7-terminals [1]
> module. I have sent a PR [2] with the improvement, until its merged and
> available in puppet forge I have fixed that in java.pp
>
> Now the image size is reduced to around 1.417 GB
>
> [1] https://github.com/7terminals/puppet-java.git
> [2] https://github.com/7terminals/puppet-java/pull/14
>
> Thanks,
> Sajith
>
> --
> Sajith Kariyawasam
> *Committer and PMC member, Apache Stratos, *
> *WSO2 Inc.; http://wso2.com *
> *Mobile: 0772269575*
>



-- 
*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] Error wile building carbon-feature-repository (branch: release-4.2.x)

[Tanya Madurapperuma]

Hi Sameera,

As per the offline chat I had with Niranjan and Nipuni, in order to fulfil
the above request from the app manager team, we need to have  a development
on-going branch for 4.2.x to send the PR with the missing features.
But we couldn't locate such branch but the released branch (release-4.2.x)
which has the version as 4.2.13

Where should we send the PR to? Could you please advise.

Thanks,
Tanya

On Mon, Jan 25, 2016 at 11:26 AM, Sinthuja Ragendran 
wrote:

> Hi Tanya,
>
> Please check on this.
>
> Thanks,
> Sinthuja.
>
> On Mon, Jan 18, 2016 at 5:09 PM, Lahiru Cooray  wrote:
>
>> adding Manu and Sinthuja
>>
>> On Mon, Jan 18, 2016 at 5:07 PM, Lahiru Cooray  wrote:
>>
>>> Hi Dakshika,
>>> Currently we are using Jaggery Server Feature 0.10.1 and this
>>> particular dependency is not included in released P2 repo.
>>> (https://github.com/wso2/carbon-feature-repository > release-4.2.x
>>> branch)
>>>
>>> Could you please update the repo with relevant dependencies so we can
>>> proceed further.
>>>
>>> Thank you.
>>>
>>>
>>> On Sat, Jan 9, 2016 at 4:02 PM, Lahiru Cooray  wrote:
>>>
 Hi Chamila,
 Thank you. Now its working.

 On Fri, Jan 8, 2016 at 6:09 PM, Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Hi Lahiru,
> Released the missing repos. You can try building it now.
>
> Chamila
>
> On Wed, Jan 6, 2016 at 12:32 PM, Lahiru Cooray 
> wrote:
>
>> Hi APIM team,
>> Could you please update the repo with missing versions.
>>
>> Thank you..
>>
>> On Tue, Jan 5, 2016 at 7:06 PM, Lahiru Cooray 
>> wrote:
>>
>>> Hi,
>>>
>>> I get the below error while building the carbon-feature-repository (
>>> https://github.com/wso2/carbon-feature-repository > release-4.2.x
>>> branch)
>>>
>>> And the required version 
>>> (org.wso2.am:org.wso2.apimgt.gateway-manager.nested.category.feature:zip:1.9.1)
>>> is not available in the
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/am/org.wso2.apimgt.gateway-manager.nested.category.feature/
>>>
>>>
>>>
>>> [ERROR] Error occured when processing the Feature Artifact:
>>> org.wso2.am:
>>> org.wso2.apimgt.gateway-manager.nested.category.feature:1.9.1
>>>
>>> org.apache.maven.plugin.MojoExecutionException: Error occured when
>>> processing the Feature Artifact: org.wso2.am:
>>> org.wso2.apimgt.gateway-manager.nested.category.feature:1.9.1
>>>
>>> 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 org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>
>>> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>>
>>> at
>>> 

[Dev] [Clustering] [WKA] Instances won't join if localMemberHost is using hostname and WKA members are using IP

[Isuru Haththotuwa]

Hi,

$subject. What I tried to do is:

   1. Create a manager node with localMemberHost set to a hostname resolved
   via /etc/hosts
   2. Create a worker node doing the same
   3. Enable clustering with WKA and point to each other using IP addresses
   for members
   4. Start manager node and then worker node

The worker node did not join to manager. Note that when I used hostnames
for both localMemberHost and WKA members, the worker node joined the
manager as expected.

Is this a known issue?

-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Vithulan Vijayanandan]

Hi Rukshan,
Oh. Thank you for the prompt reply and the links.

Hi Gimantha,
Yes, can we be able to have,

   - Unique Count - It will get a count in a field about how many unique
   values it has.
   - Standard deviation
   - Percentile

   And also some grouping aggregations,

   - Time-stamp based aggregation - Where we should be able to group the
   logs based on timestamp (Automatically/Hour/Day/etc)
   - Date range - Where we should be able to group and analyze the logs
   within specific date range.
   - Integer range based aggregation - Where we should be able to group the
   events based on range of an integer field.
   - An aggregation where we should be able to compare all the log fields
   against existing all metric aggregations (count,sum,min,max,avg).
   (Eg:log_level vs count)


Thanks.

Regards,

Vithulan

On Tue, Jan 26, 2016 at 4:25 PM, Gimantha Bandara  wrote:

> Hi Vithulan,
>
> Other than the aggregates Rukshan has mentioned, DAS supports COUNT also.
> Are there any other aggregates required log analyzer functionalities?
>
> On Tue, Jan 26, 2016 at 3:31 PM, Rukshan Premathunga 
> wrote:
>
>> Hi Vithulan,
>>
>> if you mean aggregate functions, known functions are
>>
>>- MAX
>>- MIN
>>- AVG
>>- SUM
>>
>> also you can refer these[1][2] docs for more about the API.
>>
>> [1]
>> https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
>> [2]
>> http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html
>>
>> Thanks and Regards.
>>
>>
>> On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan > > wrote:
>>
>>> Hi,
>>>
>>> We need to have data aggregations for LogAnalyzer, log search
>>> requirement. What are the aggregations that are available in DAS REST API
>>> currently?
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Vithulan.
>>>
>>> --
>>> *Vithulan MV*
>>>
>>> Intern-Software Engineering
>>> WSO2, Inc : wso2.com
>>> Mobile: +94712540524
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>> ___
>> 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
>



-- 
*Vithulan MV*

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

[Dev] [VOTE] Release WSO2 Business Process Server 3.5.1 RC1

[Hasitha Aravinda]

Hi Devs,

This is the first release candidate of WSO2 Business Process Server 3.5.1

The vote will be open for 72 hours or as needed. Please download, test the
product and vote.

*​​This release fixes the following issues:*
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide=12625


*​​Source & binary distribution files:*
​
https://github.com/wso2/product-bps/releases/tag/v3.5.1-RC1

*​​Maven staging repo:*
http://maven.wso2.org/nexus/content/repositories/orgwso2bps-308/

*​​The tag to be voted upon:*
​​
https://github.com/wso2/product-bps/releases/tag/v3.5.1-RC1


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


​Thanks,
​WSO2 BPS Team,

-- 
--
Hasitha Aravinda,
Senior Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Malith Dhanushka]

Hi Gimantha,

I Think we can add Unique Count, Standard deviation and Percentile under
default matrices right?

And do we already have API support for grouping aggregations like range and
histograms?

Thanks,
Malith

On Tue, Jan 26, 2016 at 6:51 PM, Vithulan Vijayanandan 
wrote:

> Hi Rukshan,
> Oh. Thank you for the prompt reply and the links.
>
> Hi Gimantha,
> Yes, can we be able to have,
>
>- Unique Count - It will get a count in a field about how many unique
>values it has.
>- Standard deviation
>- Percentile
>
>And also some grouping aggregations,
>
>- Time-stamp based aggregation - Where we should be able to group the
>logs based on timestamp (Automatically/Hour/Day/etc)
>- Date range - Where we should be able to group and analyze the logs
>within specific date range.
>- Integer range based aggregation - Where we should be able to group
>the events based on range of an integer field.
>- An aggregation where we should be able to compare all the log fields
>against existing all metric aggregations (count,sum,min,max,avg).
>(Eg:log_level vs count)
>
>
> Thanks.
>
> Regards,
>
> Vithulan
>
> On Tue, Jan 26, 2016 at 4:25 PM, Gimantha Bandara 
> wrote:
>
>> Hi Vithulan,
>>
>> Other than the aggregates Rukshan has mentioned, DAS supports COUNT also.
>> Are there any other aggregates required log analyzer functionalities?
>>
>> On Tue, Jan 26, 2016 at 3:31 PM, Rukshan Premathunga 
>> wrote:
>>
>>> Hi Vithulan,
>>>
>>> if you mean aggregate functions, known functions are
>>>
>>>- MAX
>>>- MIN
>>>- AVG
>>>- SUM
>>>
>>> also you can refer these[1][2] docs for more about the API.
>>>
>>> [1]
>>> https://docs.wso2.com/display/DAS300/Retrieving+Aggregated+Values+of+Given+Records+via+REST+API
>>> [2]
>>> http://blog.rukspot.com/2015/11/aggregate-functions-with-wso2-das-rest.html
>>>
>>> Thanks and Regards.
>>>
>>>
>>> On Tue, Jan 26, 2016 at 3:21 PM, Vithulan Vijayanandan <
>>> vithu...@wso2.com> wrote:
>>>
 Hi,

 We need to have data aggregations for LogAnalyzer, log search
 requirement. What are the aggregations that are available in DAS REST API
 currently?

 Thanks.

 Regards,
 Vithulan.

 --
 *Vithulan MV*

 Intern-Software Engineering
 WSO2, Inc : wso2.com
 Mobile: +94712540524

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


>>>
>>>
>>> --
>>> Rukshan Chathuranga.
>>> Software Engineer.
>>> WSO2, Inc.
>>>
>>> ___
>>> 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
>>
>
>
>
> --
> *Vithulan MV*
>
> Intern-Software Engineering
> WSO2, Inc : wso2.com
> Mobile: +94712540524
>



-- 
Malith Dhanushka
Senior Software Engineer - Data Technologies
*WSO2, Inc. : wso2.com *
*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Gateway 1.0.0 - Beta2 Released !

[Senduran Balasubramaniyam]

*WSO2 Gateway 1.0.0 - Beta2 Released !*


We are pleased to announce the beta2 release of WSO2 Gateway 1.0.0. It is
now available to download from here
.
The source and tag location for this release are available here
.


WSO2 Gateway (WSO2 GW) is an ultra high performance, lightweight and
configuration-driven message gateway based on standard gateway pattern. It
aims to encapsulate messaging between source and target systems that are
built with disparate technologies, protocols and standards. While it
includes messaging between two systems, message mediation can be controlled
by configuring WSO2 GW’s mediation logic.


The beta2 release of WSO2 Gateway 1.0.0 includes the following key
features. For further details please see the documentation
.


*Key Features*

   -

   Ultra high performance and low latency  HTTP/S messaging.
   -

   Supports thousands of concurrent connections/clients.
   -

   Header-based routing using Apache Camel
    as the message mediation engine.
   -

   Defines REST services/APIs using Camel REST DSL
   
   -

   Lightweight and stateless service orchestration.
   -

   Load balancing and failover messaging.
   -

   Error handling support.
   -

   Hot deploying routes.


How To Contribute

You can find more instructions on how to contribute on our documentation
 site.

If you have any suggestions or are interested in WSO2 Gateway discussions,
you can join the dev@wso2.org or architect...@wso2.org mailing lists.
Reporting Issues

We encourage you to report issues, documentation errors regarding WSO2
Gateway 1.0.0 beta2 through the public issue tracking system
.


Thanks,

WSO2 Gateway Team

-- 
*Senduran *
Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Log Analyzer] DAS REST API Data Aggregations support

[Vithulan Vijayanandan]

Hi,

We need to have data aggregations for LogAnalyzer, log search requirement.
What are the aggregations that are available in DAS REST API currently?

Thanks.

Regards,
Vithulan.

-- 
*Vithulan MV*

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

Re: [Dev] [MB] [MQTT] Bulk Messages on Carbon Logs from PublishDecoder

[Pamod Sylvester]

Yes, this comes from the Moqutte library when decoding a published message,
since we've forked the repo we could add the change.

Please create a jira.

Thanks,
Pamod

On Tue, Jan 26, 2016 at 5:05 PM, Rasika Perera  wrote:

> Hi All,
>
> Currently we are using MB as our MQTT broker in our IoTS. We are seeing
> bulk messages are printed when publishing MQTT message into broker[1].
>
> [2016-01-26 16:46:16,450]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
> [2016-01-26 16:46:17,946]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
> [2016-01-26 16:46:19,068]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
> [2016-01-26 16:46:21,824]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
> [2016-01-26 16:46:31,451]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 2048)
> [2016-01-26 16:46:32,945]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 16384)
> [2016-01-26 16:46:34,068]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 16384)
> [2016-01-26 16:46:36,823]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 8192)
> [2016-01-26 16:46:46,449]  INFO
> {org.dna.mqtt.moquette.parser.netty.PublishDecoder} -  decode invoked with
> buffer UnpooledUnsafeDirectByteBuf(ridx: 1, widx: 1113, cap: 8192)
>
> These messages are at INFO level. IMO this should be at TRACE level log.
> WDYT?
>
> ​[1]
> https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/dna/mqtt/moquette/parser/netty/PublishDecoder.java#L38
> ​
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com *
cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev