Re: [Dev] [VOTE] Release of WSO2 Stream Processor 4.3.0 RC3

[Sajith Perera]

Tested the following.

Siddhi Stores Query API[editor/worker runtime]
Distributed Message Tracer[worker/dashboard runtime]
SP Distributed Deployment[2 Manger/ 5 Worker(including single receiver)
runtimes]
Editor Sample:
 - Store RDBMS MySQL/Oracle[editor]
 - Store Cassedra[editor]

No blockers found.

[+] Stable - go ahead and release

Thanks,
SajithD

On Sat, Sep 15, 2018 at 1:05 AM, Dilini Muthumala  wrote:

> Hi all,
>
>
> WSO2 Stream Processor team is pleased to announce the third
> release candidate of WSO2 Stream Processor 4.3.0.
>
>
> WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics
> platform, of which the real-time, incremental & intelligent data processing
> capabilities let digital businesses create actionable business insights and
> data products.
>
>
> Please find the improvements and fixes related to this release:
>
> - siddhi
> 
>
> - carbon-analytics-common
> 
>
> - carbon-analytics
> 
>
> - carbon-dashboards
> 
>
> - analytics-solutions
> 
>
> - product-sp
> 
>
>
> You can download the product distribution from: https://github.com/wso2/
> product-sp/releases/download/v4.3.0-rc3/wso2sp-4.3.0-rc3.zip
>
>
> The tag to be voted upon: 
> *https://github.com/wso2/product-sp/releases/tag/v4.3.0-rc3
> *
>
>
> Please download, test the product and vote.
>
>
> [+] Stable - go ahead and release
>
> [-] Broken - do not release (explain why)
>
>
> Thanks,
>
> - WSO2 Stream Processor Team -
>



-- 

Sajith Dimal
Seniror Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware


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

Re: [Dev] Using regex in Siddhi SQL queries

[Sajith Perera]

Hi,

Let me explain how we evaluate the on condition with respect to the RDBMS
store. in the find() method location[1], all the condition expressions are
converted the RDBMS queries with SQL WHERE Clauses. But as per your
requirement instead of converted to WHERE Clause, it should be converted
to Regular Expression Operator.

ex:
SELECT 'Michael' WHERE age>24;

SELECT 'Michael' REGEXP '.*';

@Thisaru
We need to further check the feasibility of this, as this is a new feature.

[1] -
https://github.com/wso2-extensions/siddhi-store-rdbms/blob/master/component/src/main/java/org/wso2/extension/siddhi/store/rdbms/RDBMSEventTable.java#L438

Regards,
SajithD

On Thu, Aug 9, 2018 at 11:28 AM, Sajith Ariyarathna 
wrote:

> Hi Nivethika,
>
> Have you tried
>
> on str:regexp(S.symbol, "WSO2(.*)")
>
> ?
>
> Thanks.
>
> On Thu, Aug 9, 2018 at 11:20 AM Niveathika Rajendran 
> wrote:
>
>> Hi Sajith,
>>
>> The use case is when retrieving data from aggregations,
>>
>> from StockStream as S join TradeAggregation as T
>>   on S.symbol == T.symbol
>>   within "2014-02-15 00:00:00 +05:30", "2014-03-16 00:00:00 +05:30"
>>   per "days" select S.symbol, T.total, T.avgPrice insert into 
>> AggregateStockStream;
>>
>>
>> Here,  On condition equals should support a regex match, for instance,
>> S.symbol == "WSO2(.*)". As of now the equal operator only supports object
>> match[1].
>>
>> [1] https://github.com/wso2/siddhi/blob/master/modules/
>> siddhi-core/src/main/java/org/wso2/siddhi/core/executor/
>> condition/compare/equal/EqualCompareConditionExpressio
>> nExecutorStringString.java#L34
>>
>>
>> Best Regards,
>> *Niveathika Rajendran,*
>> *Software Engineer.*
>> *Mobile : +94 077 903 7536*
>>
>>
>>
>>
>>
>> On Thu, Aug 9, 2018 at 11:04 AM Thisaru Guruge  wrote:
>>
>>> Here's my Siddhi Code:
>>>
>>> @App:name("IsAnalytics_Authentication_Aggregations")
>>> @App:description("Handle Event from IS and save data in a table for
>>> Overall Authentication")
>>>
>>> @source(type='inMemory', topic='IsAnalytics.Authentication.Common.
>>> OutputSinkFromProcessedAuthenticationDataStream',
>>> @map(type='passThrough'))
>>> define stream ProcessedAuthenticationDataStream (
>>> meta_tenantId int,
>>> eventId string,
>>> username string,
>>> localUsername string,
>>> userStoreDomain string,
>>> tenantDomain string,
>>> remoteIp string,
>>> region string,
>>> inboundAuthType string,
>>> serviceProvider string,
>>> rememberMeEnabled bool,
>>> forceAuthEnabled bool,
>>> passiveAuthEnabled bool,
>>> rolesCommaSeparated string,
>>> authenticationStep string,
>>> identityProvider string,
>>> authStepSuccess bool,
>>> stepAuthenticator string,
>>> isFirstLogin bool,
>>> successValue int,
>>> failureValue int,
>>> stepSuccessValue int,
>>> firstLoginValue int,
>>> identityProviderType string,
>>> timestamp long
>>> );
>>>
>>> define stream PerUserRolesDuplicateEventStream (
>>> meta_tenantId int,
>>> eventId string,
>>> username string,
>>> localUsername string,
>>> userStoreDomain string,
>>> tenantDomain string,
>>> remoteIp string,
>>> region string,
>>> inboundAuthType string,
>>> serviceProvider string,
>>> rememberMeEnabled bool,
>>> forceAuthEnabled bool,
>>> passiveAuthEnabled bool,
>>> rolesCommaSeparated string,
>>> authenticationStep string,
>>> identityProvider string,
>>> authStepSuccess bool,
>>> stepAuthenticator string,
>>> isFirstLogin bool,
>>> successValue int,
>>> failureValue int,
>>> stepSuccessValue int,
>>> firstLoginValue int,
>>> identityProviderType string,
>>> timestamp long,
>>> token string
>>> );
>>>
>>> @store(type='rdbms', datasource='IS_ANALYTICS_DB')
>>> define aggregation RoleAggregation
>>> from PerUserRolesDuplicateEventStream
>>> select
>>> meta_tenantId,
>>> username,
>>> serviceProvider,
>>> identityProvider,
>>> token as role,
>>> remoteIp,
>>> region,
>>> userStoreDomain,
>>> sum(successValue) as authSuccessCount,
>>> sum(failureValue) as authFailureCount,
>>> sum(stepSuccessValue) as authStepSuccessCount,
>>> identityProviderType,
>>> timestamp
>>> group by
>>> meta_tenantId,
>>> username,
>>> serviceProvider,
>>> token
>>> aggregate by timestamp every second ... year;
>>>
>>> @store(type='rdbms', datasource='IS_ANALYTICS_DB')
>>> define aggregation AuthenticationStatAggregation
>>> from ProcessedAuthenticationDataStream
>>> select
>>> meta_tenantId,
>>> username,
>>> localUsername,
>>> rolesCommaSeparated,
>>> serviceProvider,
>>> identityProvider,
>>> remoteIp,
>>> region,
>>> userStoreDomain,
>>> sum(successValue) as authSuccessCount,
>>> sum(failureValue) as authFailureCount,
>>> sum(stepSuccessValue) as authStepSuccessCount,
>>> sum(firstLoginValue) as  authFirstSuccessCount,
>>> 

Re: [Dev] How to check whether an SP node is in Active or Passive state

[Sajith Perera]

Also, there are CLI logs where it’s print the status of the node. Please
refer the doc[2]

[2017-10-23 08:56:57,380]  INFO
{org.wso2.carbon.stream.processor.core.internal.ServiceComponent} - WSO2
Stream Processor Starting in Two Node Minimum HA Deployment
[2017-10-23 08:56:57,392]  INFO
{org.wso2.carbon.stream.processor.core.ha.HAManager} - HA Deployment:
Starting up as Active Node


[2] -
https://docs.wso2.com/plugins/servlet/mobile?contentId=68701902#content/view/68701902

On Tue, Jul 24, 2018 at 11:58 PM Damith Wickramasinghe 
wrote:

> Hi fazlan,
>
> we have apis exposed where you can get the information.
>
> eg:- curl -k -X GET http://localhost:9090/statistics -H "accept:
> application/json" -u admin:admin -k -v
>
> will provide you a json with all the information. see[1]
>
> [1] https://docs.wso2.com/display/SP420/Stream+Processor+REST+API+Guide
>
> Is this what you are asking for ?
>
> Regards,
> Damoth
>
> On Tue, Jul 24, 2018 at 6:07 PM, Fazlan Nazeem  wrote:
>
>> Hi,
>>
>> How is $subject done in SP? Can you point me to a source location?
>>
>> --
>> Thanks & Regards,
>>
>> *Fazlan Nazeem*
>> Senior Software Engineer
>> WSO2 Inc
>> Mobile : +94772338839
>> fazl...@wso2.com
>>
>
>
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Connect to a RDMBS datastore to retrieve data for a SP dashboard widget

[Sajith Perera]

Hi,

Please have a look on the sample doc:
https://docs.wso2.com/display/SP4xx/Generating+Widgets

Regards,
SajithD

On Thu, Jul 5, 2018 at 10:56 AM, Thisaru Guruge  wrote:

> Hi,
>
> I am looking for a way to retrieve data from a RDBMS to show them in a
> widget in SP dashboard.
>
> I found an example from this link
> 
>  thanks
> to Nisala, and followed it. But widget is not showing the data.
>
> Is there any documentation where I can refer about this ?
>
> --
> Thanks and Best Regards,
> Thisaru Guruge
> Software Engineer
> Mobile: +94 71 720 9720
>
>
> WSO2 Inc.: http://www.wso2.com
>
>
>


-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Inferring actual table name from the table's encoded name

[Sajith Perera]

Hi Rukshani,

Reviewed!, Looks good.

Regards,
SajithD

On Tue, May 1, 2018 at 1:49 PM, Rukshani Weerasinha <ruksh...@wso2.com>
wrote:

> Hello Sajith,
>
> Thank you for this information. Now the documentation is updated
> accordingly. Can you please check [1]?
>
> [1] https://docs.wso2.com/display/DAS320/Inferring+the+
> Actual+Table+Name+from+the+Encoded+Name
>
> Best Regards,
> Rukshani.
>
> On Tue, Apr 24, 2018 at 3:42 PM, Sajith Perera <saji...@wso2.com> wrote:
>
>> Hi Rukshani,
>>
>> Please find the requested information:
>>
>> Sample cURL command
>> curl -H "Content-Type: application/json" -H "Authorization: Basic
>> YWRtaW46YWRtaW4=" -v https://localhost:9443/analyti
>> cs/tables/ANX___7LtvlqNk_/actualName -k
>>
>> Example
>> GET (with auth) https://:9443/analytics/tables/ANX___7LtvlqNk_/
>> actualName
>>
>> Sample output
>> SAMPLE_TABLE
>>
>> REST API response
>> HTTP status code 200
>> For descriptions of the HTTP status codes, see HTTP Status Codes.
>>
>> Regards,
>> SajithD
>>
>> On Mon, Apr 23, 2018 at 4:27 PM, Rukshani Weerasinha <ruksh...@wso2.com>
>> wrote:
>>
>>> Hi Sajith,
>>>
>>> I will do this within the week. Thank you for sharing this information.
>>>
>>> Best Regards,
>>> Rukshani.
>>>
>>> On Fri, Apr 20, 2018 at 11:59 AM, Sajith Perera <saji...@wso2.com>
>>> wrote:
>>>
>>>> +[Rukshani]
>>>>
>>>> Hi All,
>>>>
>>>> We need to update the documentation [1] by adding the following entry
>>>> for the $subject implementation.
>>>>
>>>> GET (with auth) https://:9443/analytics/tables/
>>>> /actualName
>>>>
>>>> [1] - https://docs.wso2.com/display/DAS320/Analytics+REST+API+Guide
>>>>
>>>> Regards,
>>>> SajithD
>>>>
>>>> On Fri, Apr 20, 2018 at 11:30 AM, Gimantha Bandara <giman...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Fazlan,
>>>>>
>>>>> It is there in apim analytics 2.2.0 and also as a WUM update in 2.1.0
>>>>>
>>>>> On Fri, Apr 20, 2018 at 5:19 AM, Fazlan Nazeem <fazl...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Was this implemented? if so can someone point me to the
>>>>>> documentation? I need to find the actual table name using the encoded 
>>>>>> name.
>>>>>> If there is any other alternative please let me know.
>>>>>>
>>>>>> On Thu, Jan 11, 2018 at 8:21 AM, Sajith Ravindra <saji...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Have to agree with Sinthuja on this.
>>>>>>>
>>>>>>> IMO this is a simple utility function. People will be mostly using
>>>>>>> this while debugging an issue to get the actual table name. Having 
>>>>>>> script
>>>>>>> makes things much easy and simple IMO.
>>>>>>>
>>>>>>> Thanks
>>>>>>> *,Sajith Ravindra*
>>>>>>> Associate Technical Lead
>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> mobile: +94 77 2273550
>>>>>>> blog: http://sajithr.blogspot.com/
>>>>>>> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab>
>>>>>>>
>>>>>>> On Thu, Jan 11, 2018 at 12:21 AM, Sinthuja Rajendran <
>>>>>>> sinth...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Gokul,
>>>>>>>>
>>>>>>>> On Thu, Jan 11, 2018 at 11:41 AM, Gokul Balakrishnan <
>>>>>>>> go...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Sinthuja,
>>>>>>>>>
>>>>>>>>> Agree with your point. However, a new script will come with its
>>>>>>>>> own complexities such as segregating permissions and preventing users 
>>>>>>>>> from
>>>>>>>>> retrieving names of tables not belonging to their tenant.
>>>>>>>>>
>>>>&g

Re: [Dev] [DAS] Inferring actual table name from the table's encoded name

[Sajith Perera]

Hi Rukshani,

Please find the requested information:

Sample cURL command
curl -H "Content-Type: application/json" -H "Authorization: Basic
YWRtaW46YWRtaW4=" -v
https://localhost:9443/analytics/tables/ANX___7LtvlqNk_/actualName -k

Example
GET (with auth) https://
:9443/analytics/tables/ANX___7LtvlqNk_/actualName

Sample output
SAMPLE_TABLE

REST API response
HTTP status code 200
For descriptions of the HTTP status codes, see HTTP Status Codes.

Regards,
SajithD

On Mon, Apr 23, 2018 at 4:27 PM, Rukshani Weerasinha <ruksh...@wso2.com>
wrote:

> Hi Sajith,
>
> I will do this within the week. Thank you for sharing this information.
>
> Best Regards,
> Rukshani.
>
> On Fri, Apr 20, 2018 at 11:59 AM, Sajith Perera <saji...@wso2.com> wrote:
>
>> +[Rukshani]
>>
>> Hi All,
>>
>> We need to update the documentation [1] by adding the following entry for
>> the $subject implementation.
>>
>> GET (with auth) https://:9443/analytics/tables/
>> /actualName
>>
>> [1] - https://docs.wso2.com/display/DAS320/Analytics+REST+API+Guide
>>
>> Regards,
>> SajithD
>>
>> On Fri, Apr 20, 2018 at 11:30 AM, Gimantha Bandara <giman...@wso2.com>
>> wrote:
>>
>>> Hi Fazlan,
>>>
>>> It is there in apim analytics 2.2.0 and also as a WUM update in 2.1.0
>>>
>>> On Fri, Apr 20, 2018 at 5:19 AM, Fazlan Nazeem <fazl...@wso2.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Was this implemented? if so can someone point me to the documentation?
>>>> I need to find the actual table name using the encoded name. If there is
>>>> any other alternative please let me know.
>>>>
>>>> On Thu, Jan 11, 2018 at 8:21 AM, Sajith Ravindra <saji...@wso2.com>
>>>> wrote:
>>>>
>>>>> Have to agree with Sinthuja on this.
>>>>>
>>>>> IMO this is a simple utility function. People will be mostly using
>>>>> this while debugging an issue to get the actual table name. Having script
>>>>> makes things much easy and simple IMO.
>>>>>
>>>>> Thanks
>>>>> *,Sajith Ravindra*
>>>>> Associate Technical Lead
>>>>> WSO2 Inc.; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> mobile: +94 77 2273550
>>>>> blog: http://sajithr.blogspot.com/
>>>>> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab>
>>>>>
>>>>> On Thu, Jan 11, 2018 at 12:21 AM, Sinthuja Rajendran <
>>>>> sinth...@wso2.com> wrote:
>>>>>
>>>>>> Hi Gokul,
>>>>>>
>>>>>> On Thu, Jan 11, 2018 at 11:41 AM, Gokul Balakrishnan <go...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Sinthuja,
>>>>>>>
>>>>>>> Agree with your point. However, a new script will come with its own
>>>>>>> complexities such as segregating permissions and preventing users from
>>>>>>> retrieving names of tables not belonging to their tenant.
>>>>>>>
>>>>>>
>>>>>> Anyhow, this is devops/advanced user related work, and not a general
>>>>>> user related operation. Because inorder to get the encoded table name, 
>>>>>> the
>>>>>> user should have the access to the database and knowing the table
>>>>>> name/schema will not impose any security threat. So I don't think having
>>>>>> shell script will reveal any additional security threat, given that the
>>>>>> user who will be using this feature will be already having the db level
>>>>>> access.
>>>>>>
>>>>>>
>>>>>>> In addition, we already have a REST API operation for doing it the
>>>>>>> other way (human-readable name to encoded name) already, hence the 
>>>>>>> decision
>>>>>>> to add this to the REST API too.
>>>>>>>
>>>>>>
>>>>>> Hmm.. Ok..
>>>>>>
>>>>>> Thanks,
>>>>>> Sinthuja.
>>>>>>
>>>>>> Best,
>>>>>>>
>>>>>>> On 11 January 2018 at 11:17, Sinthuja Rajendran <sinth...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Gok

Re: [Dev] [DAS] Inferring actual table name from the table's encoded name

[Sajith Perera]

+[Rukshani]

Hi All,

We need to update the documentation [1] by adding the following entry for
the $subject implementation.

GET (with auth) https://:9443/analytics/tables/
/actualName

[1] - https://docs.wso2.com/display/DAS320/Analytics+REST+API+Guide

Regards,
SajithD

On Fri, Apr 20, 2018 at 11:30 AM, Gimantha Bandara 
wrote:

> Hi Fazlan,
>
> It is there in apim analytics 2.2.0 and also as a WUM update in 2.1.0
>
> On Fri, Apr 20, 2018 at 5:19 AM, Fazlan Nazeem  wrote:
>
>> Hi all,
>>
>> Was this implemented? if so can someone point me to the documentation? I
>> need to find the actual table name using the encoded name. If there is any
>> other alternative please let me know.
>>
>> On Thu, Jan 11, 2018 at 8:21 AM, Sajith Ravindra 
>> wrote:
>>
>>> Have to agree with Sinthuja on this.
>>>
>>> IMO this is a simple utility function. People will be mostly using this
>>> while debugging an issue to get the actual table name. Having script makes
>>> things much easy and simple IMO.
>>>
>>> Thanks
>>> *,Sajith Ravindra*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 77 2273550
>>> blog: http://sajithr.blogspot.com/
>>> 
>>>
>>> On Thu, Jan 11, 2018 at 12:21 AM, Sinthuja Rajendran 
>>> wrote:
>>>
 Hi Gokul,

 On Thu, Jan 11, 2018 at 11:41 AM, Gokul Balakrishnan 
 wrote:

> Hi Sinthuja,
>
> Agree with your point. However, a new script will come with its own
> complexities such as segregating permissions and preventing users from
> retrieving names of tables not belonging to their tenant.
>

 Anyhow, this is devops/advanced user related work, and not a general
 user related operation. Because inorder to get the encoded table name, the
 user should have the access to the database and knowing the table
 name/schema will not impose any security threat. So I don't think having
 shell script will reveal any additional security threat, given that the
 user who will be using this feature will be already having the db level
 access.


> In addition, we already have a REST API operation for doing it the
> other way (human-readable name to encoded name) already, hence the 
> decision
> to add this to the REST API too.
>

 Hmm.. Ok..

 Thanks,
 Sinthuja.

 Best,
>
> On 11 January 2018 at 11:17, Sinthuja Rajendran 
> wrote:
>
>> Hi Gokul,
>>
>> +1 to have a feature which returns the actual table name from the
>> encoded table name that exists in the data storage.
>>
>> But IMHO, having REST API for this is not a correct way of doing,
>> because REST APIs are intended to integrate this with external systems, 
>> and
>> hence core analytics data operations need to be exposed via the REST API.
>> But this feature is kind of a utility operation for debugging and not 
>> meant
>> to be used by the users for normal table operations and also AFAIR it's
>> applicable for RDBMS analytics data sources, not for others such as 
>> HBase.
>>
>> Therefore I propose, we'll have a utility shell script like a tool,
>> which will take the encoded table name, and the data source type as 
>> params,
>> and prompt the user-defined table name.
>>
>> Thanks,
>> Sinthuja.
>>
>> On Thu, Jan 11, 2018 at 11:01 AM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi,
>>>
>>> We have come across many cases where DAS tables stored in the EVENT
>>> or PROCESSED stores (which have encoded names to comply with DB vendor
>>> limitations) cannot be identified as representing which actual table 
>>> just
>>> by looking at them. This is a very useful functionality to have, 
>>> especially
>>> when debugging issues.
>>>
>>> In order to address this, I've implemented a DAS REST API operation
>>> which will simply examine the calling user's tables and print out the 
>>> name
>>> of the actual table if a match is found.
>>>
>>> The usage will be as follows:
>>>
>>> GET (with auth) https://:9443/analyt
>>> ics/tables//actualName
>>>
>>> Example cURL command:
>>>
>>> curl -k -H "Authorization: Basic YWRtaW46YWRtaW4="
>>> https://localhost:9443/analytics/tables/ANX___7Lleafa0_/actualName
>>>
>>> We're planning to release this as a WUM update for DAS 3.1.0 and
>>> related products.
>>>
>>> --
>>> Gokul Balakrishnan
>>> Senior Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>>>
>>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Senior Technical Lead
>> WSO2, 

Re: [Dev] Problems with multiple RDBMS hits within the stream

[Sajith Perera]

Hi All,

We have identified an issue in the RDBMS update flow.
Please track the issue in [1].

[1] - https://github.com/wso2-extensions/siddhi-store-rdbms/issues/78

Thanks,
SajithD

On Sun, Apr 8, 2018 at 10:15 PM, Gihan Anuruddha  wrote:

> [+ Mohan, Tishan]
>
> On Sun, Apr 8, 2018 at 9:21 PM, Bahtiyar KARANLIK 
> wrote:
>
>>
>> Hi All,
>>
>> Please find below a sample siddhi file, and the related exception. Any
>> comments are highly appreciated.
>>
>> First the exception:
>>
>> Caused by: java.sql.BatchUpdateException: Batch entry 0 UPDATE
>> my_test_table SET occurrence = (my_test_table.occurrence + '_str' ) WHERE (
>> my_test_table.id = 2 ) was aborted: ERROR: operator does not exist:
>> bigint + character varying
>>   Hint: No operator matches the given name and argument type(s). You
>> might need to add explicit type casts.
>>   Position: 65  Call getNextException to see other errors in the batch.
>> at org.postgresql.jdbc.BatchResultHandler.handleCompletion(Batc
>> hResultHandler.java:166)
>> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecut
>> orImpl.java:490)
>> at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:835)
>> at org.postgresql.jdbc.PgPreparedStatement.executeBatch(PgPrepa
>> redStatement.java:1556)
>> at com.zaxxer.hikari.proxy.StatementProxy.executeBatch(Statemen
>> tProxy.java:127)
>> at com.zaxxer.hikari.proxy.HikariPreparedStatementProxy.execute
>> Batch(HikariPreparedStatementProxy.java)
>> at org.wso2.extension.siddhi.store.rdbms.RDBMSEventTable.batchP
>> rocessSQLUpdates(RDBMSEventTable.java:558)
>>
>>
>>
>> Siddhi file to re-produce the exception;
>>
>> ———
>>
>> @App:name("Test App")
>> @App:description("App_Description")
>> -- Please refer to http://wso2.github.io/siddhi/documentation/siddhi-4.0/
>>
>> -- insert into my_test_table (id, occurrence, some_key) values(1, 1, 'o');
>> -- insert into my_test_table (id, occurrence, some_key) values(2, 1000,
>> 'nok');
>>
>> define trigger TriggerStream at every 10 sec;
>>
>> @Store(type = "rdbms", jdbc.url = "jdbc:postgresql://localhost:5432/my_db",
>> username = "my_user", password = "my_password" , jdbc.driver.name =
>> "org.postgresql.Driver", table.name = 'my_test_table')
>> @primaryKey('id')
>> define table TestTable(id long, occurrence long, some_key string);
>>
>> @sink(type='log')
>> define stream UpdateNumeric(triggered_time long, id long, occurrence
>> long, some_key string);
>>
>> @sink(type='log')
>> define stream UpdateString(triggered_time long, id long, occurrence long,
>> some_key string);
>>
>> from TriggerStream left outer join TestTable
>> on TestTable.id==1
>> select *
>> insert into UpdateNumeric;
>>
>> from TriggerStream left outer join TestTable
>> on TestTable.id==2
>> select *
>> insert into UpdateString;
>>
>> from UpdateNumeric
>> select *
>> update TestTable
>>  set TestTable.occurrence = TestTable.occurrence + 1
>>   on TestTable.id == id;
>>
>> from UpdateString
>> select *
>> update TestTable
>>  set TestTable.some_key = TestTable.some_key + "_str"
>>   on TestTable.id == id;
>>
>> ———
>>
>>
>>
>> Best regards,
>>
>> Bahtiyar.
>>
>>
>> On 4 Apr 2018, at 17:27, Bahtiyar KARANLIK  wrote:
>>
>> Hi All,
>>
>> I'm working on an "alarm management" test app. The idea is as follows:
>>
>> - I've an EventStream with following important fields:
>> -- event_type = type of the event. i.e. threshold_exceeded_event
>> -- event_source = the entity that is going to be monitored. i.e.
>> region1.router1.cpu_utilization
>> -- level = severity of the Event (i.e. 0 -> Info, 1-> warning, 2 ->
>> critical)
>> -- level_changed = boolean flag (whether the level has changed from the
>> previous event item. i.e. if level is info at t0, and warning at t1, then
>> t1 event has this level_changed flag set to true)
>>
>> Then my algorithm comes in:
>>
>> 1) if the level_changed flag is false and if it is not Info;
>> --> Then I should have an "Active" (status == 1) alarm in the DB, and
>> should update its occurence count.
>>
>> 2) if the level_changed flag is true;
>> 2.a) I'm going to "clear" the alarm in the DB table (keywords: RDBMS
>> Store Extension + PostgreSQL)
>> 2.b) check 'level' field, and if it is not "Info" (==0), then Create a
>> NEW alarm in the table with the current level (level = severity).
>>
>> Here starts the problem;
>>
>> for events with "level_changed" set to true, updating the active Alarms's
>> status field is not executed at all!! I can create Alarms (AlarmsToCreate),
>> Increment their Occurence count (AlarmsToIncrement), but can not set their
>> status fields (AlarmsToClear).
>>
>> I guess, there is a problem with multiple DB hits (i.e. clear the
>> Alarm-set status to 0 for alarm with id 3 and create a new Alarm) for the
>> same event (within a stream). I can see that the logic can decide that it
>> needs to Clear an alarm, and create a new one (logs with AlarmsToClear and
>> AlarmsToCreate are there !. 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Data Analytics Server 3.2.0 RC2

[Sajith Perera]

Hi All,

I have tested following,

DAS 2 Node Minimum HA
Following fixes ported from DAS 3.1.0
Unregister mbeanEventQueue when shutdown the DataEndpointGroup object.
Re-enabling single node persistence.
Allowing null values for strings in RDBMS event adaptor.
Siddhi Groupby Aggregate Object Accumulating Issue.
Fixes for the Databrige SSL connection.

[+] Stable go ahead and release

Best Regards,
SajithD


On Fri, Mar 16, 2018 at 1:15 PM, Chiran Fernando  wrote:

> Hi all
>
> I tested the DAS 3.2.0-RC2 pack for the following functionality
> - Event Simulator
> - 2 Node Minimum HA
> - Anonymization-tool
> - Adding project on Machine learner
> - Existance of cookie and privacy policy
> - Indexing
>
> Therefore,
>
> [+] Stable go ahead and release.
>
>
> On Fri, Mar 16, 2018 at 11:01 AM, Meruja Selvamanikkam 
> wrote:
>
>> Hi all
>>
>> I tested the DAS 3.2.0-RC2 pack for the following Samples
>>
>> -Publishing and Receiving Events via HTTP and MQTT Transport
>> -Calculations over time using Windows
>> -Pass-Through/Projection Query in an Execution Plan
>> -Projections, Transformations and Enrichment for events
>>
>> Hence,
>>
>> [+] Stable go ahead and release.
>>
>> Regards,
>> Meruja
>>
>>
>> On Fri, Mar 16, 2018 at 10:56 AM, Gowthamy Vaseekaran 
>> wrote:
>>
>>> Hi all
>>>
>>> I tested the DAS 3.2.0-RC2 pack for the following transport
>>>
>>>- Receiving Events via kafka
>>>- Receiving Events via HTTP
>>>- Publishing Events via various transport (Logger, WSO2 Event, SOAP,
>>>Email, SMS, MQTT, JMS)
>>>- Samples under Processing Events
>>>
>>> Therefore,
>>>
>>> [+] Stable go ahead and release
>>> Thank you.
>>> Gowthamy
>>>
>>>
>>> On Fri, Mar 16, 2018 at 10:15 AM, Gowthamy Vaseekaran >> > wrote:
>>>
 Hi all

 I tested the DAS 3.2.0-RC2 pack for the following transport

- Receiving Events via kafka
- Receiving Events via HTTP
- Publishing Events via various transport (Logger, WSO2 Event,
SOAP,Email,SMS,MQTT,JMS)
- Samples under Processing Events

 Therefore,

 [+] Stable go ahead and release.

 Regards,
 Gowthamy


 On Fri, Mar 16, 2018 at 10:04 AM, Anusha Jayasundara 
 wrote:

> Tested setting up JMX profiles, adding user secondary store.
>
> [+] Stable go head and release.
>
> On Fri, Mar 16, 2018 at 3:28 AM, Sajith Ravindra 
> wrote:
>
>> Hi all
>>
>> I tested the DAS 3.2.0-RC2 pack for the following functionality
>> - Event Simulator
>> - Event receiving and publishing with HTTP transport
>> - Adding/listing users
>> - Creating dashboards
>> - Exisitance of cookie and privacy policy
>>
>> Therefore,
>>
>> [+] Stable go ahead and release.
>>
>> Thanks
>> *,Sajith Ravindra*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273550
>> blog: http://sajithr.blogspot.com/
>> 
>>
>> On Fri, Mar 16, 2018 at 2:39 AM, Chiran Fernando 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> We are pleased to announce the release candidate of WSO2 Data
>>> Analytics Server 3.2.0.
>>>
>>> This is the Release Candidate version 2 of the WSO2 Data Analytics
>>> Server 3.2.0
>>>
>>> Please download, test the product and vote. The vote will be open
>>> for 72 hours or as needed.
>>>
>>> *Known issues*: https://github.com/wso2/product-das/issues
>>>
>>> *Source and binary distribution files*:
>>> https://github.com/wso2/product-das/releases/tag/v3.2.0-RC2
>>>
>>> The tag to be voted upon: https://github.com/wso2/produc
>>> t-das/tree/v3.2.0-RC2
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> ~ The WSO2 Analytics Team ~
>>> --
>>> *Chiran Fernando*
>>> Software Engineer | WSO2
>>>
>>> Email : chi...@wso2.com
>>> Mobile : +94716007376 <+94%2071%20600%207376>
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Anusha Jayasundara*
> Software Engineer | WSO2
>
> Email : anus...@wso2.com
> Mobile : +94772601160 <+94%2077%20260%201160>
> Web : http://wso2.com
> Lean.Enterprise.Middleware
> 
>

[Dev] [VOTE] Release WSO2 Data Analytics Server 3.2.0 RC1

[Sajith Perera]

Hi Devs,

We are pleased to announce the release candidate of WSO2 Data Analytics
Server 3.2.0.

This is the Release Candidate version 1 of the WSO2 Data Analytics Server
3.2.0

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

Known issues: https://github.com/wso2/product-das/issues

Source and binary distribution files:
https://github.com/wso2/product-das/releases/tag/v3.2.0-RC1

The tag to be voted upon:
https://github.com/wso2/product-das/tree/v3.2.0-RC1

Please vote as follows.
[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

~ The WSO2 Analytics Team ~

Thanks.
-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM-ANALYTICS-2.1.0] Error ORG_WSO2_APIMGT_STATISTICS_PERHOURREQUES does not exist

[Sajith Perera]

Hi Chaminda

Is this single node analytics setup? could you attach the full server log
files?
In the product analytics and DAS deployment if server pack is replaced and
pointing to the same database we need to mount the following file
directories as there are files will be updated during the server runtime.
But only concern if this is the case it should happen for the vanilla pack
as well.

   1. repository/data
   2. repository/config/analytics

Thanks,
SajithD

On Mon, Jan 29, 2018 at 6:22 PM, Harsha Kumara  wrote:

>
>
> On Mon, Jan 29, 2018 at 6:20 PM, Chaminda Jayawardena 
> wrote:
>
>> Hi All,
>>
>> Getting below error continuously on an apim-analytics-2.10 server
>> instance.
>> We are using latest wum updated apim-analytics2.1.0 pack with fresh
>> databases.
>>
>> Configured the pack using puppet in an apim cluster pattern-6[1].
>>
>> The error encountered only when the wum updated pack is used.
>>
>> Note: as suggested in several threads, I cleaned the databases and tried
>> again but had no luck. Complete error log has been attached in the file -
>> analytics_error.rtf
>>
>>
>>
>> *Caused by:
>> org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsTableNotAvailableException:
>> [-1234:ORG_WSO2_APIMGT_STATISTICS_PERHOURREQUEST] does not exist*
>>
>> * at *org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRec
>> ordStore.get(RDBMSAnalyticsRecordStore.java:420)
>>
>> at org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServ
>> iceImpl.getByRange(AnalyticsDataServiceImpl.java:961)
>>
>> at org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServ
>> iceImpl.get(AnalyticsDataServiceImpl.java:910)
>>
>> at org.wso2.carbon.analytics.spark.core.rdd.AnalyticsRDD.getPar
>> titions(AnalyticsRDD.java:119)
>>
>> ... 100 more
>>
>>
>> [1] https://docs.wso2.com/display/AM2xx/Using+Puppet+Modules
>> +to+Set+up+WSO2+API-M+with+Pattern+6
>>
>> --
>> Thanks & Regards
>>
>> *Chaminda Jayawardena*
>> Associate Technical Lead - QA
>> WSO2 Inc. - http://wso2.com
>> +94-77-7725234 <+94%2077%20772%205234>
>>
>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Stream Processor (SP) 4.0.0-RC3

[Sajith Perera]

Hi All,

Tested SP Dashboard Widget Generation:

   - RDBMS Batch Scenario
   - RDBMS Streaming Scenario

[+] Stable - Go ahead and release

On Fri, Dec 22, 2017 at 10:01 PM, Niveathika Rajendran 
wrote:

> Hi all,
>
> Tested SP Monitoring dashboard,
>
> [+] Stable - Go ahead and release
>
>
> On Fri, Dec 22, 2017 at 9:54 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> Tested the editor, event simulation, dashboard creation, widget
>> generation.
>>
>> Suho
>>
>>
>> On Fri, Dec 22, 2017 at 9:24 PM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the third release candidate (RC) of WSO2 Stream Processor 4.0.0
>>> release.
>>>
>>> New / Improvements In This Release after RC2
>>>
>>>- Bug fixes in editor and the RDBMS store
>>>- UI Improvements
>>>
>>> Reported Issues
>>>
>>>- https://github.com/wso2/product-sp/issues
>>>
>>> Source and distribution packages:
>>>
>>>- https://github.com/wso2/product-sp/releases/tag/v4.0.0-RC3
>>>
>>> Tag to be voted upon:
>>>
>>>- https://github.com/wso2/product-sp/releases/tag/v4.0.0-RC3
>>>
>>> Please download, test, and vote. The README file under the distribution
>>> contains guide and instructions on how to try it out locally.
>>>
>>> [+] Stable - Go ahead and release
>>> [-] Broken - Do not release (explain why)
>>>
>>> This vote will be open for 72 hours or as needed.
>>>
>>> Regards,
>>> The WSO2 Analytics Team.
>>>
>>> --
>>> Gokul Balakrishnan
>>> Senior Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> M +94 77 5935 789 | +44 7563 570502 <+44%207563%20570502>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *S. Suhothayan*
>> Associate Director / Architect
>> *WSO2 Inc. *http://wso2.com
>> * *
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
>> http://suhothayan.blogspot.com/ twitter:
>> http://twitter.com/suhothayan  | linked-in:
>> http://lk.linkedin.com/in/suhothayan *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards,
> *Niveathika Rajendran,*
> *Software Engineer.*
> *Mobile : +94 077 903 7536 <+94%2077%20903%207536>*
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Stream Processor Editor - Fixing Veracode reported issues.

[Sajith Perera]

Hi All,

In the stream processor editor, we are using absolute paths when referring
the Siddhi App files and other simulation files in the editor worker
directory. But in the editor app, it should call the backend API with the
relative path based on the "{product-home}/wso2/editor/deployment".

Ex:

   1. "deployment/worker" should be changed to "/worker" (all subdirectory
   paths should be relative to deployment)
   2. "{product-home}/wso2/editor/deployment/csv-files" should be changed
   to "/csv-files" (avoid  using the absolute paths in the API invocation)

We can change the backend API along with the above changes, but editor UI
components invoke the API with the absolute paths and subpaths.
Any suggestions for fixing the mentioned issues in the Editor UI Components.

Regards,
SajithD

-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] How to configure DAS_AGENT.url for multiple DAS nodes?

[Sajith Perera]

Hi Preminda,

DAS_AGENT uses databridge publisher, so you can setup the DAS thrift urls
relevant to your use case. Pleas follow the steps given in the doc 1.

[1] - https://docs.wso2.com/m/mobile.action#page/47530694

On Wed, Nov 29, 2017 at 3:57 PM Praminda Jayawardana 
wrote:

> Hi All,
>
> If I have multiple analytics nodes configured and I need to publish to all
> nodes, how can I configure DAS_AGENT.url in log4j.properties? Will comma
> separated values work?
> Ex:
> log4j.appender.DAS_AGENT.url=tcp://localhost:7612,tcp://localhost:7613
>
> Thanks,
> Praminda
>
> --
>
> *Praminda Jayawardana*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> Mobile : +94 (0) 716 590918
>
-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 Stream Processor 4.0.0-Alpha Released!

[Sajith Perera]

Hi All,

The WSO2 Analytics team is pleased to announce the release of *WSO2
Stream Processor Version
4.0.0 Alpha*.

WSO2 Smart Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's real-time, incremental & intelligent data processing
 capabilities.

WSO2 Stream Processor can:

   -

   Receive events from various data sources
   -

   Process & correlate them in real-time with the state-of-the-art
   high-performance real-time Siddhi Complex Event Processing Engine that
   works with easy to learn the SQL-Like query language.
   -

   Conduct analysis that spans for longer time duration with its
   incremental processing capability by achieving high performance with low
   infrastructure cost.
   -

   Use Machine Learning to drive intelligent insights from the data
   -

   Notify interesting event occurrences as alerts via multiple types of
   transports & let users visualize the results via customizable dashboards.


WSO2 SP is released under Apache Software License Version 2.0, one of the
most business-friendly licenses available today.

You can find the product at
https://github.com/wso2/product-sp/releases/download/v4.0.0-Alpha/wso2sp-4.0.0-Alpha.zip

Documentation at
*https://docs.wso2.com/display/SP400/Introducing+the+Stream+Processor
*
Source code at *https://github.com/wso2/product-sp
/*

*WSO2 SP 4.0.0-Alpha includes the following*

*New Features*

   - Business Rules Manager
   - Authenticator and KeyManager Support
   - Dashboard Permission Model
   - Editor Console Log Event Appender
   - Status Dashboard
   - Distributed Deployment
   - RDBMS Data Provider

*Improvements*

   - Editor tooltip and auto-completion
   - Editor samples improvements
   - Dashboard sample gadgets

*Reporting Issues*


Issues can be reported using the GitHub issue tracker available at
https://github.com/wso2/product-sp

*Contact us*

WSO2 Stream Processor developers can be contacted via the mailing lists:

Developer List: dev@wso2.org | Subscribe
 | M



Alternatively, questions can also be raised in the Stackoverflow:

Forum http://stackoverflow.com/questwso2/



*Support *

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support/.  

For more information on WSO2 Smart Analytics and Smart Analytics Solutions,
visit the WSO2 Smart Analytics Page .


*~ The WSO2 Analytics Team ~*

-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoiding Carbon Metrics releases every time the Databridge component is released.

[Sajith Perera]

Noted!, Please find the relevant GitHub issue :
https://github.com/wso2/carbon-analytics-common/issues/397

On Thu, Nov 2, 2017 at 12:12 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Thu, Nov 2, 2017 at 12:08 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> We need to avoid releasing Carbon Metrics every time the Data bridge
>> related components are released. It should be possible if Carbon Metrics
>> can depend on a Data Publisher feature.
>>
>> Shall we fix this soon?
>>
>
> Yes, we have to fix this. Data publisher features are implemented but
> faced some issues when embedding the features with carbon-metrics. We'll
> take this for our next release and fix it.
>
> @SajithD, let's create a github issue for this.
>
> Thanks,
> Mohan
>
>
>> Thank you.
>>
>> --
>> Isuru Perera
>> Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
> *V. Mohanadarshan*
> *Technical Lead,*
> *Data Technologies Team,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673 <+94%2077%20111%207673>
>



-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Samples config files for each product in puppet common

[Sajith Perera]

Noted !

Thanks

On Wed, Nov 23, 2016 at 12:07 PM Imesh Gunaratne  wrote:

> [Adding Jagath, Prasanna, Harsha and Sajith]
>
> On Wed, Nov 23, 2016 at 12:05 PM, Imesh Gunaratne  wrote:
>
> Hi Vishanth,
>
> On Tue, Nov 22, 2016 at 8:44 PM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
> Hi Imesh,
>
> Have we removed the $subject?
>
>
> ​Yes, apologies for not notifying this. We moved vagrant samples to
> puppet- repositories as those get changed with product
> requirements:
>
> https://github.com/wso2/puppet-apim/tree/master/vagrant-samples
> https://github.com/wso2/puppet-esb/tree/master/vagrant-samples
> https://github.com/wso2/puppet-is/tree/master/vagrant-samples
> https://github.com/wso2/puppet-cep/tree/master/vagrant-samples
> https://github.com/wso2/puppet-das/tree/master/vagrant-samples
>
> Thanks​
>
>
> Regards,
> Vishanth
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth *
>
>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [PUPPET][CEP/DAS] Releasing puppet modules for restructured CEP-4.0.0 and DAS-3.0.1 puppet module distribution.

[Sajith Perera]

Hi All,

We are planning to do a release on Puppet modules related to Complex Event
Processor 4.0.0 and Data Analytics Server 3.0.1.
Current puppet module for DAS 3.0.1 and CEP 4.0.0 supports following
deployment patterns.

Pattern-1: Standalone server with default profile.
Pattern-2: Clustered environment (minimum HA)

Also we are required to release puppet-common[2] 1.0.0 prior to these
releases.
I have tested the deployment scenarios via Puppet using VM and Docker build
as explained in [4].

[1] https://github.com/wso2/puppet-cep
[2] https://github.com/wso2/puppet-das 
[3] https://github.com/wso2/puppet-common
[4]
https://github.com/wso2/puppet-base/wiki/Setting-up-the-Development-Environment

Thanks,
SajithD

-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Ashen Weerathunga

[Sajith Perera]

Congratulations Ashen!

On Tue, Oct 4, 2016 at 11:03 AM, Nirmal Fernando  wrote:

> Hi all,
>
> It is my pleasure to welcome Ashen Weerathunga as a WSO2 Committer. In
> recognition of Ashen's contributions to ML, Siddhi and IoT analytics, he
> has been voted as a Committer.
>
> Ashen, welcome aboard and keep up the good work.
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Sajith Dimal
Software Engineer
Email : saji...@wso2.com
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Inclusion of available APIs under Deleted APIs list in API Deployment Stats in Log Analyzer

[Sajith Perera]

Hi Maneesha,

Log analyzer purely based on the log events which are generated by a
particular product. For each stat, there are set of keywords and rules in
log lines, which we are identifying as unique for that scenario.

Regarding the above mentioned scenario, if there is an update on an API in
given time frame, there will be two log lines printed with "Destroying" and
"Initiating" keywords.

1. Deleted Artifact X
2. Created Artifact X

These events are listed as "Deployed Api X" and "Deleted Api X" tables in
the given time frame, as they are the "facts" within the given time frame.

Thanks,
SajithD

On Tue, Jul 5, 2016 at 12:44 PM, Maneesha Wijesekara 
wrote:

> Hi all,
>
> Currently 'API Deployment Stats' in Log Analyzer listed both Deployed APIs
> and Deleted APIs. But I've noticed that some available APIs (not yet
> deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
> is when an API is edited, it will destroyed and again re-deployed. That log
> will cause to include an available API under 'Deleted APIs'. But when it
> comes to the function 'Deleted APIs', it should only list the names of APIs
> which are actually deleted.
>
> Any thoughts on this ?
>
> [1] https://wso2.org/jira/browse/ANLYAPIM-79
>
> --
> Maneesha Wijesekara
> Software Engineer - QA Team
> WSO2 Inc.
>
> Email: manee...@wso2.com
> Linkedin: http://linkedin.com/in/maneeshawijesekara
> Mobile: +94712443119
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Natasha Wijesekara

[Sajith Perera]

Congratulations Natasha..!!! :)

On Wed, Jun 29, 2016 at 10:49 AM, Natasha Wijesekara 
wrote:

> Thank you all !!!
>
> On Wed, Jun 29, 2016 at 10:45 AM, Natasha Wijesekara 
> wrote:
>
>> Thank you akki ! :)
>>
>> On Wed, Jun 29, 2016 at 10:32 AM, Himasha Guruge 
>> wrote:
>>
>>> Congrats Natasha! :)
>>>
>>> On Wed, Jun 29, 2016 at 10:23 AM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi All,

 It's my pleasure to announce Natasha Wijesekara as a WSO2 Committer.
 Natasha has been a great contributor to BPS and PC products and in
 recognition of her contributions, she's been voted as a WSO2 Committer.

 Congratulations Natasha and keep up the good work!

 Regards
 Nandika

 --
 Nandika Jayawardana
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware

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


>>>
>>>
>>> --
>>> Himasha Guruge
>>> *Software Engineer*
>>> WS*O2* *Inc.*
>>> Mobile: +94 777459299
>>> himas...@wso2.com
>>>
>>
>>
>>
>> --
>> *Natasha Wijesekare*
>>
>> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
>> *
>> *email  : nata...@wso2.com *
>> *mobile: +94 771358651 <%2B94%20771358651>*
>>
>
>
>
> --
> *Natasha Wijesekare*
>
> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
> *
> *email  : nata...@wso2.com *
> *mobile: +94 771358651 <%2B94%20771358651>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Navigation buttons not visible in Custom Time picker in Log Analyzer

[Sajith Perera]

No, it's not a blocking issue . Please merge it if new release is planned.

Thanks,
SajithD

On Wed, Jun 8, 2016 at 12:17 PM, Bhathiya Jayasekara <bhath...@wso2.com>
wrote:

> Is this a blocker? If not, I prefer to go with as it is, because we have
> already built Beta candidate pack and completed most of the test scenarios.
> If we have to do another build we have to do all the tests again, which
> takes a lot of time.
>
> Thanks,
> Bhathiya
>
> On Wed, Jun 8, 2016 at 12:12 PM, Sajith Perera <saji...@wso2.com> wrote:
>
>> +Jerad and Dunith
>>
>> On Wed, Jun 8, 2016 at 12:11 PM, Sajith Perera <saji...@wso2.com> wrote:
>>
>>>
>>> Hi All,
>>>
>>> We have faced issue while embedding date range picker gadget in to the
>>> API-M admin dashboard jira [1] and [2]. Since this is major concern from
>>> the user's point of view we need to have fixes before API-M beta release.
>>>
>>> Issue is  date range picker gadget used bootstrap-min.css and API-M
>>> admin dashboard hasn't got this css and also its not compatible with admin
>>> dashboard.
>>>
>>> As a solution I would like to suggest to adding styling and fonts files
>>> inside the loganalyzer template.
>>> as in this PR [3] and it is not a proper fix, and need to be looked
>>> properly later.
>>>
>>> As per the offline chat I had with Jerad, the better fix is to use wso2
>>> fonts rather than use external font icons.
>>>
>>> [1] - https://wso2.org/jira/browse/ANLYAPIM-54
>>> [2] - https://wso2.org/jira/browse/ANLYAPIM-53
>>> [3] - https://github.com/wso2/carbon-apimgt/pull/2488
>>>
>>> WDYT?
>>>
>>> Thanks,
>>> SajithD
>>> --
>>> Sajith Dimal
>>> Software Engineer
>>> Mobile : +94783101496
>>> WSO2 Inc. | http://wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> Sajith Dimal
>> Software Engineer
>> Mobile : +94783101496
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com <http://wso2.com>*
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> <http://www.linkedin.com/in/bhathiyaj>*
> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
> *Blog: http://movingaheadblog.blogspot.com
> <http://movingaheadblog.blogspot.com/>*
>



-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Navigation buttons not visible in Custom Time picker in Log Analyzer

[Sajith Perera]

+Jerad and Dunith

On Wed, Jun 8, 2016 at 12:11 PM, Sajith Perera <saji...@wso2.com> wrote:

>
> Hi All,
>
> We have faced issue while embedding date range picker gadget in to the
> API-M admin dashboard jira [1] and [2]. Since this is major concern from
> the user's point of view we need to have fixes before API-M beta release.
>
> Issue is  date range picker gadget used bootstrap-min.css and API-M admin
> dashboard hasn't got this css and also its not compatible with admin
> dashboard.
>
> As a solution I would like to suggest to adding styling and fonts files
> inside the loganalyzer template.
> as in this PR [3] and it is not a proper fix, and need to be looked
> properly later.
>
> As per the offline chat I had with Jerad, the better fix is to use wso2
> fonts rather than use external font icons.
>
> [1] - https://wso2.org/jira/browse/ANLYAPIM-54
> [2] - https://wso2.org/jira/browse/ANLYAPIM-53
> [3] - https://github.com/wso2/carbon-apimgt/pull/2488
>
> WDYT?
>
> Thanks,
> SajithD
> --
> Sajith Dimal
> Software Engineer
> Mobile : +94783101496
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Navigation buttons not visible in Custom Time picker in Log Analyzer

[Sajith Perera]

Hi All,

We have faced issue while embedding date range picker gadget in to the
API-M admin dashboard jira [1] and [2]. Since this is major concern from
the user's point of view we need to have fixes before API-M beta release.

Issue is  date range picker gadget used bootstrap-min.css and API-M admin
dashboard hasn't got this css and also its not compatible with admin
dashboard.

As a solution I would like to suggest to adding styling and fonts files
inside the loganalyzer template.
as in this PR [3] and it is not a proper fix, and need to be looked
properly later.

As per the offline chat I had with Jerad, the better fix is to use wso2
fonts rather than use external font icons.

[1] - https://wso2.org/jira/browse/ANLYAPIM-54
[2] - https://wso2.org/jira/browse/ANLYAPIM-53
[3] - https://github.com/wso2/carbon-apimgt/pull/2488

WDYT?

Thanks,
SajithD
-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ERROR - No trustStore found Error when initializing the DataPublisher

[Sajith Perera]

Thanks for the reply and I have tried suggested method and yet nothing
works for me. Another approach  we could take client-trustStore key path
from log4j.property file and then setup the system property inside the log
appender. Since we are in the development stage of this log appender, so
now we have decided to proceed with this approach.


Please let me know if you have any suggestions on above methods.

Thanks.

On Tue, Mar 8, 2016 at 10:36 AM, Omindu Rathnaweera <omi...@wso2.com> wrote:

> You can try pointing them to trust-stores in respective products.
> Generally it's located at /repository/resources/security/
> directory.
>
> Regards,
> Omindu.
>
> On Tue, Mar 8, 2016 at 10:09 AM, Sajith Perera <saji...@wso2.com> wrote:
>
>> Hi Omindu,
>>
>> Thanks for the suggestions.
>> I have checked the following configuration files [1],[2],
>>
>> [1] wso2cep-4.1.0/repository/conf/data-bridge/data-agent-config.xml
>> [2] wso2am-1.10.0/repository/conf/data-bridge/thrift-agent-config.xml
>>
>> And observed that by default they were commented as on product cep [3]
>> and product apim [4]:
>>
>> [3] 
>> 
>>
>> [4] 
>>
>> From looking at those commented paths, it seems they are pointing to
>> the different locations.
>> Do i need mannualy configuer on properties for the correct location ?
>>
>> Regards,
>> sajithD
>>
>> On Tue, Mar 8, 2016 at 2:10 AM, Omindu Rathnaweera <omi...@wso2.com>
>> wrote:
>>
>>> Hi Sajith,
>>>
>>> From looking at [1], it seems the AgentHolder first tries to load the
>>> truststore property from the data-agent-config.xml and then from
>>> the system property javax.net.ssl.trustStore if it's not there in the
>>> config file. The error seems to occur because the property is not set in
>>> either of these places. Better to check the data-agent-config file and
>>> see whether you have the property there (may be it's commented).
>>>
>>>
>>> [1] -
>>> https://github.com/wso2/carbon-analytics-common/blob/master/components/data-bridge/org.wso2.carbon.databridge.agent/src/main/java/org/wso2/carbon/databridge/agent/AgentHolder.java#L93
>>>
>>> Regards,
>>> Omindu.
>>>
>>> On Mon, Mar 7, 2016 at 3:01 PM, Sajith Perera <saji...@wso2.com> wrote:
>>>
>>>> Hi all,
>>>> I'm currently working on log4j log appender for log analyzer works, In
>>>> there i used thrift publisher using
>>>> org.wso2.carbon.databridge.agent.DataPublisher.
>>>> But getting below error while initiating the data publisher instance.
>>>>
>>>> [2016-03-07 14:13:51,516] ERROR
>>>> {org.wso2.carbon.databridge.agent.AgentHolder} -  Unable to complete
>>>> initialization of agents.No trustStore found
>>>> org.wso2.carbon.databridge.agent.exception.DataEndpointAgentConfigurationException:
>>>> No trustStore found
>>>> at
>>>> org.wso2.carbon.databridge.agent.AgentHolder.loadConfiguration(AgentHolder.java:110)
>>>> at
>>>> org.wso2.carbon.databridge.agent.AgentHolder.(AgentHolder.java:59)
>>>> at
>>>> org.wso2.carbon.databridge.agent.AgentHolder.getInstance(AgentHolder.java:73)
>>>> at
>>>> org.wso2.carbon.databridge.agent.DataPublisher.(DataPublisher.java:108)
>>>> at
>>>> org.wso2.analytics.data.agent.logging.service.appender.LogEventAppender$LogPublisherTask.publishLogEvent(LogEventAppender.java:310)
>>>> at
>>>> org.wso2.analytics.data.agent.logging.service.appender.LogEventAppender$LogPublisherTask.run(LogEventAppender.java:254)
>>>> at
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>>>> at
>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>>>> at
>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>> at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>>
>>>> Any suggestion on this is greatly appreciated.
>>>>
>>>> Best Regards,
>>>&g

Re: [Dev] ERROR - No trustStore found Error when initializing the DataPublisher

[Sajith Perera]

Hi Omindu,

Thanks for the suggestions.
I have checked the following configuration files [1],[2],

[1] wso2cep-4.1.0/repository/conf/data-bridge/data-agent-config.xml
[2] wso2am-1.10.0/repository/conf/data-bridge/thrift-agent-config.xml

And observed that by default they were commented as on product cep [3] and
product apim [4]:

[3] 


[4] 

>From looking at those commented paths, it seems they are pointing to
the different locations.
Do i need mannualy configuer on properties for the correct location ?

Regards,
sajithD

On Tue, Mar 8, 2016 at 2:10 AM, Omindu Rathnaweera <omi...@wso2.com> wrote:

> Hi Sajith,
>
> From looking at [1], it seems the AgentHolder first tries to load the
> truststore property from the data-agent-config.xml and then from
> the system property javax.net.ssl.trustStore if it's not there in the
> config file. The error seems to occur because the property is not set in
> either of these places. Better to check the data-agent-config file and
> see whether you have the property there (may be it's commented).
>
>
> [1] -
> https://github.com/wso2/carbon-analytics-common/blob/master/components/data-bridge/org.wso2.carbon.databridge.agent/src/main/java/org/wso2/carbon/databridge/agent/AgentHolder.java#L93
>
> Regards,
> Omindu.
>
> On Mon, Mar 7, 2016 at 3:01 PM, Sajith Perera <saji...@wso2.com> wrote:
>
>> Hi all,
>> I'm currently working on log4j log appender for log analyzer works, In
>> there i used thrift publisher using
>> org.wso2.carbon.databridge.agent.DataPublisher.
>> But getting below error while initiating the data publisher instance.
>>
>> [2016-03-07 14:13:51,516] ERROR
>> {org.wso2.carbon.databridge.agent.AgentHolder} -  Unable to complete
>> initialization of agents.No trustStore found
>> org.wso2.carbon.databridge.agent.exception.DataEndpointAgentConfigurationException:
>> No trustStore found
>> at
>> org.wso2.carbon.databridge.agent.AgentHolder.loadConfiguration(AgentHolder.java:110)
>> at
>> org.wso2.carbon.databridge.agent.AgentHolder.(AgentHolder.java:59)
>> at
>> org.wso2.carbon.databridge.agent.AgentHolder.getInstance(AgentHolder.java:73)
>> at
>> org.wso2.carbon.databridge.agent.DataPublisher.(DataPublisher.java:108)
>> at
>> org.wso2.analytics.data.agent.logging.service.appender.LogEventAppender$LogPublisherTask.publishLogEvent(LogEventAppender.java:310)
>> at
>> org.wso2.analytics.data.agent.logging.service.appender.LogEventAppender$LogPublisherTask.run(LogEventAppender.java:254)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Any suggestion on this is greatly appreciated.
>>
>> Best Regards,
>>
>> --
>> Sajith Dimal
>> Software Engineer
>> Mobile : +94783101496
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Omindu Rathnaweera
> Software Engineer, WSO2 Inc.
> Mobile: +94 771 197 211
>



-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ERROR - No trustStore found Error when initializing the DataPublisher

[Sajith Perera]

Hi all,
I'm currently working on log4j log appender for log analyzer works, In
there i used thrift publisher using
org.wso2.carbon.databridge.agent.DataPublisher.
But getting below error while initiating the data publisher instance.

[2016-03-07 14:13:51,516] ERROR
{org.wso2.carbon.databridge.agent.AgentHolder} -  Unable to complete
initialization of agents.No trustStore found
org.wso2.carbon.databridge.agent.exception.DataEndpointAgentConfigurationException:
No trustStore found
at
org.wso2.carbon.databridge.agent.AgentHolder.loadConfiguration(AgentHolder.java:110)
at
org.wso2.carbon.databridge.agent.AgentHolder.(AgentHolder.java:59)
at
org.wso2.carbon.databridge.agent.AgentHolder.getInstance(AgentHolder.java:73)
at
org.wso2.carbon.databridge.agent.DataPublisher.(DataPublisher.java:108)
at
org.wso2.analytics.data.agent.logging.service.appender.LogEventAppender$LogPublisherTask.publishLogEvent(LogEventAppender.java:310)
at
org.wso2.analytics.data.agent.logging.service.appender.LogEventAppender$LogPublisherTask.run(LogEventAppender.java:254)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Any suggestion on this is greatly appreciated.

Best Regards,

-- 
Sajith Dimal
Software Engineer
Mobile : +94783101496
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev