[Dev] WSO2 API Microgateway 3.2.0 Released!

[Menaka Jayawardena]

The WSO2 API Manager team is pleased to announce the release of version
3.2.0 of WSO2 API Microgateway.

The WSO2 API Microgateway is a cloud-native, developer-centric and
decentralized API gateway for microservices.
You can download the product from API Microgateway webpage
<https://wso2.com/api-management/api-microgateway/#>.

*What's new in 3.2.0*

*New Features*

   - Back end JWT generation
   - Custom claim mapping for JWT
   - Custom and blocking condition support for global rate limiting
   - Advance endpoint configurations
   More 3.2.0 new features...
   
<https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3A%22Type%2FNew+Feature%22>

*Improvements*

   - Support reading open API definition in interceptors
   - Support reading configurations from java interceptors
   - Per API mutual SSL support
   - Binary publisher to support publishing to multiple TMs
   More 3.2.0 improvements
   
<https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FImprovement>


*Bug Fixes*
Fixed Issues
<https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+>

*Known Issues*
Open Issues
<https://github.com/wso2/product-microgateway/issues?utf8=%E2%9C%93=is%3Aopen+is%3Aissue>

*Try It.*
https://mg.docs.wso2.com/en/latest/getting-started/quick-start-guide/quick-start-guide-docker/

*Documentation*
https://mg.docs.wso2.com/en/latest/

*How You Can Contribute*

   - *Reporting Issues*
   We encourage you to report issues, documentation faults, and feature
   requests regarding WSO2 API Microgateway through the Github Issues.

   - *Contributing Code*
   Read through project Contribution Guidelines
   <https://github.com/wso2/product-microgateway/blob/master/CONTRIBUTING.md>
to
   learn how to contribute with code.

   - *Mailing Lists*
   Join our mailing list and receive updates on product development.
   Developer List: dev@wso2.org

   -
*User Forum * StackOverflow
   <https://stackoverflow.com/questions/tagged/wso2-mgw>

   - Join us on Slack
   
<https://join.slack.com/t/wso2-apim/shared_invite/zt-93qbqzja-gIJ21SJNQgz9uPffte_yPQ>


*--WSO2 API Manager Team--*

-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture][Vote] Release of WSO2 API Microgateway 3.2.0 RC2

[Menaka Jayawardena]

Hi Amila,

I think what you have explained should be the migration guide for 3.2.0. I
> think we need to get it added to the docs. Even if there are zero steps to
> be followed, that itself should be mentioned in the docs under migration
> because otherwise the users will be in doubt.


Noted. We will update the docs.

Thanks and Regards,
Menaka

On Mon, Aug 24, 2020 at 2:08 PM Nadee Poornima  wrote:

> Hi Menaka,
> Thanks for the detailed explanation.
>
> I think what you have explained should be the migration guide for 3.2.0. I
>> think we need to get it added to the docs. Even if there are zero steps to
>> be followed, that itself should be mentioned in the docs under migration
>> because otherwise the users will be in doubt.
>
>
> +1 for this.
>
> Cheers,
> Nadee
>
> On Mon, Aug 24, 2020 at 2:00 PM Amila Maha Arachchi 
> wrote:
>
>> Hi Menaka,
>>
>> I think what you have explained should be the migration guide for 3.2.0.
>> I think we need to get it added to the docs. Even if there are zero steps
>> to be followed, that itself should be mentioned in the docs under migration
>> because otherwise the users will be in doubt.
>>
>> Regards,
>> Amila.
>>
>> On Mon, Aug 24, 2020 at 12:54 PM Menaka Jayawardena 
>> wrote:
>>
>>> Hi Nadee,
>>>
>>> By default, Microgateway does not require any migration process. You can
>>> build the mgw project using the Microgateway 3.2.0 toolkit and run with the
>>> Microgateway 3.2.0 runtime with the old configurations. (Ex. build 3.1.0
>>> project with 3.2.0 toolkit and run with 3.2.0 runtime with the 3.1.0
>>> configs)
>>> All most all of the configurations are backwards compatible and there
>>> are only few config level changes which will be updated in the docs.
>>> (related to authentication and subscription validation).
>>>
>>> Migration would only be required if you have any customizations written
>>> in ballerina.
>>>
>>> Thanks and Regards,
>>> Menaka
>>>
>>> On Mon, Aug 24, 2020 at 11:37 AM Nadee Poornima  wrote:
>>>
>>>> Hi Menaka,
>>>>
>>>> Analysed the Micro GW documents[1], however, didn't see any document
>>>> relating the migration process (upgrade process) from Micro GW 3.1.0 to
>>>> Micro GW 3.2.0.
>>>> Is there any specific process to migrate Micro GW product? How we can
>>>> do that?
>>>>
>>>> Appreciate your valuable thought here.
>>>>
>>>> [1]. https://mg.docs.wso2.com/en/latest/#
>>>>
>>>> Cheers,
>>>> Nadee
>>>>
>>>> On Sat, Aug 22, 2020 at 4:10 PM Menaka Jayawardena 
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> WSO2 Api Manager team is pleased to announce the second release
>>>>> candidate of WSO2 API Microgateway 3.2.0.
>>>>>
>>>>> The WSO2 API Microgateway is a lightweight, gateway distribution which
>>>>> can be used to expose single or multiple APIs.
>>>>>
>>>>> Please find the improvements and fixes related to this release in Fixed
>>>>> issues
>>>>> <https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+>
>>>>>
>>>>> Download the product from here
>>>>> <https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-rc2>
>>>>>
>>>>> The Tag to be voted upon is
>>>>> https://github.com/wso2/product-microgateway/tree/v3.2.0-rc2
>>>>>
>>>>> *Documentation*: https://mg.docs.wso2.com/en/latest/
>>>>>
>>>>> Please download, test the product and vote.
>>>>>
>>>>> *[+] Stable* - Go ahead and release
>>>>>
>>>>> *[-] Broken* - Do not release (explain why)
>>>>>
>>>>>
>>>>> Best Regards,
>>>>> WSO2 API Manager Team
>>>>>
>>>>>
>>>>> --
>>>>> *Menaka Jayawardena*
>>>>> Senior Software Engineer *|* *WSO2* *Inc*.
>>>>> +94 71 350 5470 | men...@wso2.com
>>>>>
>>>>> <https://wso2.com/signature>
>>>>>
>>>>>
>>>>
>>>> --
>>>> *Nadee Poornima*
>>>> Software Engineer | WSO2
>>>>
>>>> Email : nad...@wso2.com
>>>> Mobile : +94713441341
>>>> MyBlog: https://medium.com/nadees-tech-stories
>>>>
>>>> <https://wso2.com/signature>
>>>>
>>>
>>>
>>> --
>>> *Menaka Jayawardena*
>>> Senior Software Engineer *|* *WSO2* *Inc*.
>>> +94 71 350 5470 | men...@wso2.com
>>>
>>> <https://wso2.com/signature>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> *Amila Mahaarachchi*
>> VP of Engineering, Integration
>> WSO2, Inc.; http://wso2.com
>> Mobile: +94719371446
>>
>> <http://wso2.com/signature>
>>
>>
>
> --
> *Nadee Poornima*
> Software Engineer | WSO2
>
> Email : nad...@wso2.com
> Mobile : +94713441341
> MyBlog: https://medium.com/nadees-tech-stories
>
> <https://wso2.com/signature>
>


-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture][Vote] Release of WSO2 API Microgateway 3.2.0 RC2

[Menaka Jayawardena]

Hi Nadee,

By default, Microgateway does not require any migration process. You can
build the mgw project using the Microgateway 3.2.0 toolkit and run with the
Microgateway 3.2.0 runtime with the old configurations. (Ex. build 3.1.0
project with 3.2.0 toolkit and run with 3.2.0 runtime with the 3.1.0
configs)
All most all of the configurations are backwards compatible and there are
only few config level changes which will be updated in the docs. (related
to authentication and subscription validation).

Migration would only be required if you have any customizations written in
ballerina.

Thanks and Regards,
Menaka

On Mon, Aug 24, 2020 at 11:37 AM Nadee Poornima  wrote:

> Hi Menaka,
>
> Analysed the Micro GW documents[1], however, didn't see any document
> relating the migration process (upgrade process) from Micro GW 3.1.0 to
> Micro GW 3.2.0.
> Is there any specific process to migrate Micro GW product? How we can do
> that?
>
> Appreciate your valuable thought here.
>
> [1]. https://mg.docs.wso2.com/en/latest/#
>
> Cheers,
> Nadee
>
> On Sat, Aug 22, 2020 at 4:10 PM Menaka Jayawardena 
> wrote:
>
>> Hi All,
>>
>> WSO2 Api Manager team is pleased to announce the second release candidate
>> of WSO2 API Microgateway 3.2.0.
>>
>> The WSO2 API Microgateway is a lightweight, gateway distribution which
>> can be used to expose single or multiple APIs.
>>
>> Please find the improvements and fixes related to this release in Fixed
>> issues
>> <https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+>
>>
>> Download the product from here
>> <https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-rc2>
>>
>> The Tag to be voted upon is
>> https://github.com/wso2/product-microgateway/tree/v3.2.0-rc2
>>
>> *Documentation*: https://mg.docs.wso2.com/en/latest/
>>
>> Please download, test the product and vote.
>>
>> *[+] Stable* - Go ahead and release
>>
>> *[-] Broken* - Do not release (explain why)
>>
>>
>> Best Regards,
>> WSO2 API Manager Team
>>
>>
>> --
>> *Menaka Jayawardena*
>> Senior Software Engineer *|* *WSO2* *Inc*.
>> +94 71 350 5470 | men...@wso2.com
>>
>> <https://wso2.com/signature>
>>
>>
>
> --
> *Nadee Poornima*
> Software Engineer | WSO2
>
> Email : nad...@wso2.com
> Mobile : +94713441341
> MyBlog: https://medium.com/nadees-tech-stories
>
> <https://wso2.com/signature>
>


-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture][Vote] Release of WSO2 API Microgateway 3.2.0 RC2

[Menaka Jayawardena]

Hi All,

WSO2 Api Manager team is pleased to announce the second release candidate
of WSO2 API Microgateway 3.2.0.

The WSO2 API Microgateway is a lightweight, gateway distribution which can
be used to expose single or multiple APIs.

Please find the improvements and fixes related to this release in Fixed
issues
<https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+>

Download the product from here
<https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-rc2>

The Tag to be voted upon is
https://github.com/wso2/product-microgateway/tree/v3.2.0-rc2

*Documentation*: https://mg.docs.wso2.com/en/latest/

Please download, test the product and vote.

*[+] Stable* - Go ahead and release

*[-] Broken* - Do not release (explain why)


Best Regards,
WSO2 API Manager Team


-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [DEV][VOTE] Release WSO2 API Microgateway 3.2.0 RC1

[Menaka Jayawardena]

Hi all,

We are cancelling this vote since we have identified some issues in the
product.
We will send a new vote for Microgateway 3.2.0 RC2 with the issues fixed.

Thanks and regards,
Menaka

On Mon, Aug 17, 2020, 4:44 PM Viraj Gamage  wrote:

> Hi all,
>
> Tested the following scenarios.
>
>- Invoke APIs using JWT/ JTI claim with APIM 3.2.0
>- Check scopes functionality using JWT/ JTI claim with APIM 3.2.0
>- Subscription Validation using JWT/JTI claim with APIM 3.2.0
>- JWTs with JWKS endpoint
>- JWTs from Third party STS
>- Large payload downloads.
>
> Encountered the following issues.
>
>- When the third party token does not contain required scopes, the
>error message does not contain the microgateway specific error code.
>
> Hence -1.
>
> On Mon, Aug 17, 2020 at 1:31 PM Chashika Weerathunga 
> wrote:
>
>> Hi all,
>>
>> Tested followings scenarios,
>>
>>- Endpoint override for imported APIs
>>- Micro gw labeleing
>>- Load balance and fail over endpoints
>>- Custom header and header sent to back end
>>- Java interceptors
>>
>> No issues found.
>>
>> *[+] Stable* - Go ahead and release
>>
>> On Mon, Aug 17, 2020 at 1:23 PM Praminda Jayawardana 
>> wrote:
>>
>>> Tested followings scenarios,
>>>
>>>- Docker quick start guide
>>>- Securing APIs with basic auth
>>>- OpenAPI 2/3 and yaml/json compatibility
>>>- Resource level endpoint definitions
>>>- Basic auth protected backend endpoints
>>>- Compatibility with WSO2 APIM 2.6.0
>>>
>>> No issues found.
>>>
>>> *[+] Stable* - Go ahead and release
>>>
>>> On Fri, Aug 14, 2020 at 7:03 PM Menaka Jayawardena 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> WSO2 Api Manager team is pleased to announce the first release
>>>> candidate of WSO2 API Microgateway 3.2.0.
>>>>
>>>> The WSO2 API Microgateway is a lightweight, gateway distribution which
>>>> can be used to expose single or multiple APIs.
>>>>
>>>> Please find the improvements and fixes related to this release in Fixed
>>>> issues
>>>> <https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+>
>>>>
>>>> Download the product from here
>>>> <https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-rc1>
>>>>
>>>> The Tag to be voted upon is
>>>> https://github.com/wso2/product-microgateway/tree/v3.2.0-rc1
>>>>
>>>> *Documentation*: https://mg.docs.wso2.com/en/latest/
>>>>
>>>> Please download, test the product and vote.
>>>>
>>>> *[+] Stable* - Go ahead and release
>>>>
>>>> *[-] Broken* - Do not release (explain why)
>>>>
>>>>
>>>> Best Regards,
>>>> WSO2 API Manager Team
>>>>
>>>> --
>>>> *Menaka Jayawardena*
>>>> Senior Software Engineer *|* *WSO2* *Inc*.
>>>> +94 71 350 5470 | men...@wso2.com
>>>>
>>>> --
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>>
>>>> *Praminda Jayawardana* | Associate Technical Lead | WSO2 Inc.
>>>> 
>>>> (e) prami...@wso2.com
>>>>
>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>> GET INTEGRATION AGILE
>>>> Integration Agility for Digitally Driven Business
>>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> *Chashika Weerathunga* | Software Engineer | WSO2 Inc.
>> (m) +94713731206 | Email: chash...@wso2.com
>> [image: http://wso2.com]
>> <http://wso2.com>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc.
> +94 710 618 178
> GET INTEGRATION AGILE
> Integration Agility for Digitally Driven Business
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][VOTE] Release WSO2 API Microgateway 3.2.0 RC1

[Menaka Jayawardena]

Hi All,

WSO2 Api Manager team is pleased to announce the first release candidate of
WSO2 API Microgateway 3.2.0.

The WSO2 API Microgateway is a lightweight, gateway distribution which can
be used to expose single or multiple APIs.

Please find the improvements and fixes related to this release in Fixed
issues
<https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+project%3Awso2%2Fproduct-microgateway%2F9+is%3Aclosed+label%3AType%2FBug+>

Download the product from here
<https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-rc1>

The Tag to be voted upon is
https://github.com/wso2/product-microgateway/tree/v3.2.0-rc1

*Documentation*: https://mg.docs.wso2.com/en/latest/

Please download, test the product and vote.

*[+] Stable* - Go ahead and release

*[-] Broken* - Do not release (explain why)


Best Regards,
WSO2 API Manager Team

-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Microgateway 3.2.0-Beta Released!

[Menaka Jayawardena]

The WSO2 API Manager team is pleased to announce the release of API
Microgateway version 3.2.0-Beta.
It's now available to download.Download
wso2am-micro-gw-3.2.0-beta
<https://github.com/wso2/product-microgateway/releases/tag/v3.2.0-beta>

Bug Fixes and Improvements in 3.2.0-Beta

Fixed Issues
<https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+is%3Aclosed+milestone%3A3.2.0-beta>
Known Issues

Open Issues
<https://github.com/wso2/product-microgateway/issues?q=is%3Aopen+is%3Aissue>
Try it

https://mg.docs.wso2.com/en/latest/getting-started/quick-start-guide/quick-start-guide-overview/
Documentation

https://mg.docs.wso2.com/
How You Can Contribute

   -

   *Reporting Issues*
   We encourage you to report issues, documentation faults, and feature
   requests regarding WSO2 API Microgateway through the Github Issues
   <https://github.com/wso2/product-microgateway/issues>.
   -

   *Contributing Code*
   Read through project Contribution Guidelines
   <https://github.com/wso2/product-microgateway/blob/master/CONTRIBUTING.md>
to
   learn how to contribute with code.
   -

   *Mailing Lists*
   Join our mailing list and receive updates on product development.
   Developer List: dev@wso2.org
   -

   *User Forum*
   Go through the StackOverflow
   <https://stackoverflow.com/questions/tagged/wso2-mgw>
   -

   *Slack channels*
   Join us via our wso2-apim.slack.com for even better communication. You
   can talk to our developers directly regarding any issues, concerns about
   the product. We encourage you to start discussions or join any ongoing
   discussions with the team, via our slack channels.
 - Discussions about developments: Dev Channel
   <https://wso2-apim.slack.com/messages/microgateway>
 - New releases: Release Announcement Channel
   <https://wso2-apim.slack.com/messages/announcements>

*--WSO2 API Manager Team--*

-- 
*Menaka Jayawardena*
Senior Software Engineer *|* *WSO2* *Inc*.
+94 71 350 5470 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue while injecting mediation in api manager 2.6.0

[Menaka Jayawardena]

Seems like you are using a send mediator without an endpoint.

Could you please verify the endpoint url is set properly in the send
mediator in you script (if any) and/ or in the
/repository/deployment/server/synapse-configs/default/api/.xml

https://docs.wso2.com/display/ESB490/Send+Mediator

Thanks and Regards,
Menaka

On Thu, Nov 28, 2019 at 1:29 PM Priyadarshini Punjabi <
priyadarshinipunj...@gmail.com> wrote:

> Hi,
> Can you please tell me why I am getting this error .Please find the
> screenshot attached.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Menaka Jayawardena*
Senior Software Engineer | WSO2 Inc.
+94 71 350 5470 | +94 76 717 2511 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] javascript response from backend server not parsing properly

[Menaka Jayawardena]

You have to set proper MessageBuilder and Formatter in
/respository/conf/axis2/axis2.xml file.

Please add the following configuration and check.

/respository/conf/axis2/axis2.xml:



 /respository/conf/axis2/axis2.xml:


For more information on Message Builders and Formatters, please follow
https://docs.wso2.com/display/EI6xx/Working+with+Message+Builders+and+Formatters

Thanks and Regards,
Menaka

On Fri, Nov 15, 2019 at 1:00 AM Shiva Kumar 
wrote:

> Hi Team,
>
> One of my API sending a javascript file and it's content type is
> application/javascript, when I requested I am getting below error response
>
> 
> 0
> Status report
> Runtime Error
> Error while building message
> 
>
> Is there any way to send the response came from backend as it is?
>
>
> Thank You,
>
> Shiva
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Menaka Jayawardena*
Senior Software Engineer | WSO2 Inc.
+94 71 350 5470 | +94 76 717 2511 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is it possible to merge identity server 5.3.0 and api manager 2.1.0?

[Menaka Jayawardena]

Hi Shiva,

Yes, it is possible to install identity server features in the API Manager.
Please follow [1].

But, this approach is generally discouraged in production deployments
because of WSO2 updates cannot be delivered for combined products.

[1] https://docs.wso2.com/display/ADMIN44x/Working+with+Features

Thanks and Regards,
Menaka


On Thu, Nov 14, 2019 at 2:51 PM Shiva Kumar 
wrote:

> Hi Team,
>
> I was going through the document
>
> https://docs.wso2.com/display/AM210/Configuring+WSO2+Identity+Server+as+a+Key+Manager.
>
> This document says I have to spin both identity server and api manager.
> Is it possible deploy one server which works as identity server and API
> manager. I mean is possible to merge binary files of identity server
> into api manager and use api manager to get all facebook, twitter
> authentication of identity server in it.
>
>
> Thank You,
>
> Shiva
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Menaka Jayawardena*
Senior Software Engineer | WSO2 Inc.
+94 71 350 5470 | +94 76 717 2511 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC3

[Menaka Jayawardena]

gt;>>>> Hi All,
>>>>>>
>>>>>> We are pleased to announce the second release candidate of WSO2 API
>>>>>> Manager 3.0.0.
>>>>>>
>>>>>> This release fixes the following issues.
>>>>>>
>>>>>>- Fixes : product-apim
>>>>>>
>>>>>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24>
>>>>>>- Fixes : carbon-apimgt
>>>>>>
>>>>>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24+>
>>>>>>- Fixes : analytics-apim
>>>>>>
>>>>>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-24>
>>>>>>
>>>>>> Source and distribution,
>>>>>> Runtime :
>>>>>> https://github.com/wso2/product-apim/releases/tag/v3.0.0-rc3
>>>>>> Analytics :
>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v3.0.0-rc3
>>>>>> APIM Tooling :
>>>>>> https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-rc
>>>>>>
>>>>>> Please download, test the product and vote.
>>>>>>
>>>>>> [+] Stable - go ahead and release
>>>>>> [-] Broken - do not release (explain why)
>>>>>>
>>>>>> Thanks,
>>>>>> WSO2 API Manager Team
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Samitha Chathuranga*
>>>>>> *Senior Software Engineer*, *WSO2 Inc.*
>>>>>> lean.enterprise.middleware
>>>>>> Mobile: +94715123761
>>>>>>
>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Mushthaq Rumy
>>>>> *Senior Software Engineer*
>>>>> Mobile : +94 (0) 779 492140
>>>>> Email : musht...@wso2.com
>>>>> WSO2, Inc.; http://wso2.com/
>>>>> lean . enterprise . middleware.
>>>>>
>>>>> <http://wso2.com/signature>
>>>>> ___
>>>>> Architecture mailing list
>>>>> architect...@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>
>>>>
>>>> --
>>>> Chamin Dias
>>>> Mobile : 0716097455
>>>> Email : cham...@wso2.com
>>>> LinkedIn : https://www.linkedin.com/in/chamindias
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>
>>>
>>> --
>>> *Kavishka Fernando*
>>> *Software Engineer | WSO2*
>>> Email: kavis...@wso2.com
>>> Mobile:  +94773838069
>>> Web: http://wso2.com
>>> Blog: https://medium.com/@kavishkafernando
>>>
>>> <http://wso2.com/signature>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 

*Menaka Jayawardena*
Senior Software Engineer | WSO2 Inc.
+94 71 350 5470 | +94 76 717 2511 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC2

[Menaka Jayawardena]

Tested the following.

- New API creation/ invocation.
- Websocket api creation and invocation.
- API product creation and invocation
- Advanced throttling policies
- Create new version of the api
- Invoke api with dynamic ssl certificates applied. (Protected backends)
- Tested mock endpoints.

No blockers found. +1

On Thu, Oct 24, 2019 at 8:51 AM Mushthaq Rumy  wrote:

> Hi All,
>
> We are pleased to announce the second release candidate of WSO2 API
> Manager 3.0.0.
>
> This release fixes the following issues.
>
>- Fixes : carbon-apimgt
>
> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23+>
>- Fixes : product-apim
>
> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23>
>- Fixes : analytics-apim
>
> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+closed%3A2018-09-16..2019-10-23>
>
> Source and distribution,
> Runtime : https://github.com/wso2/product-apim/releases/tag/v3.0.0-rc2
> Analytics :
> https://github.com/wso2/analytics-apim/releases/tag/v3.0.0-rc2
> APIM Tooling :
> https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-rc
>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 API Manager Team
>
>
> --
> Mushthaq Rumy
> *Senior Software Engineer*
> Mobile : +94 (0) 779 492140
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> <http://wso2.com/signature>
> ___________
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 

*Menaka Jayawardena*
Senior Software Engineer | WSO2 Inc.
+94 71 350 5470 | +94 76 717 2511 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] Release WSO2 API Microgateway 3.0.1 RC3

[Menaka Jayawardena]

Tested following.
- Basic flow with JWT token
- Resource level throttling
- Request/ Response intercepting.

No blockers found.
*[+] Stable - Go ahead and release*

On Mon, Jun 10, 2019 at 4:26 PM Praminda Jayawardana 
wrote:

> Tested followings,
>
>- Basic flow with import APIs
>- Basic Auth
>- Analytics file writing/ uploading/ APIM Dashboard visibility
>
> No blockers found.
> *[+] Stable - Go ahead and release*
>
> Thanks,
> Praminda
>
> On Mon, Jun 10, 2019 at 2:01 PM Rajith Roshan  wrote:
>
>> Tested the following scenarios.
>>
>>
>>- Basic throttling
>>- Custom application throttling for open API based api and imported
>>APIs
>>- Custom subscription throttling for imported APIs
>>- Global throttling
>>- Basic flow in dev first approach
>>- Load balance and fail over endpoints
>>
>> No blockers found.
>> *[+] Stable - Go ahead and release*
>>
>> Thanks!
>> Rajith
>>
>> On Sun, Jun 9, 2019 at 10:25 AM Praminda Jayawardana 
>> wrote:
>>
>>> Hi All,
>>>
>>> WSO2 Api Manager team is pleased to announce the third release candidate
>>> of WSO2 API Microgateway 3.0.1.
>>>
>>> The WSO2 API Microgateway is a lightweight, gateway distribution which
>>> can be used with single or multiple APIs.
>>>
>>> Please find the improvements and fixes related to this release in Fixed
>>> issues
>>> <https://github.com/wso2/product-microgateway/issues?utf8=%E2%9C%93=is%3Aissue+closed%3A2018-10-12..2019-06-09>
>>>
>>> Download the product from here
>>> <https://github.com/wso2/product-microgateway/releases/tag/v3.0.1-rc3>
>>>
>>> The Tag to be voted upon is
>>> https://github.com/wso2/product-microgateway/releases/tag/v3.0.1-rc3
>>>
>>> Please download, test the product and vote.
>>>
>>> *[+] Stable - Go ahead and release*
>>>
>>> *[-] Broken - Do not release *(explain why)
>>>
>>>
>>> Documentation: https://docs.wso2.com/display/MG301/
>>>
>>> Best Regards,
>>> WSO2 API Manager Team
>>>
>>
>>
>> --
>> *Rajith Roshan* | Associate Technical Lead | WSO2 Inc.
>> (m) +94-717-064-214 |  (e) raji...@wso2.com 
>>
>> <https://wso2.com/signature>
>>
>
>
> --
>
> *Praminda Jayawardana* | Senior Software Engineer | WSO2 Inc.
> (m) +94 (0) 716 590918 | (e) prami...@wso2.com
> GET INTEGRATION AGILE
> Integration Agility for Digitally Driven Business
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Menaka Jayawardena*
Senior Software Engineer | WSO2 Inc.
+94 71 350 5470 | +94 76 717 2511 | men...@wso2.com

<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 small task/ project to practice

[Menaka Jayawardena]

Hi Aman,

You can try our ESB samples[1], which will give you the basic understanding
of the usage scenarios.

[1] https://docs.wso2.com/display/ESB500/Samples

Thanks and Regards,
Menaka

On Wed, Dec 19, 2018 at 11:13 AM Aman Singh  wrote:

> Hi Devs,
>
> I am learning WSO2 ESB and API manager by myself. Basically I am a
> beginner with understanding of different mediators. Can someone help me
> with like daily small tasks or some small project to work on. As I believe
> that working on some projects helps in better understanding of concepts.
>
> Any task or links where I can work on some task/project would be
> appreciated.
>
> Thank you,
> Aman.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 

*Menaka Jayawardena*
Senior Software Engineer
WSO2 Inc.

Phone: +94 71 350 5470
LinkedIn : https://lk.linkedin.com/in/menakajayawardena
Blog   : https://menakamadushanka.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] One Specific API not responding

[Menaka Jayawardena]

Hi Alapan Sur,

You can change the timeout configurations. Please refer the documentation
[1] and [2] for detailed information.

[1] https://docs.wso2.com/display/AM210/Prevent+API+Suspension
[2]
https://docs.wso2.com/display/AM210/Tuning+Performance#TuningPerformance-TimeoutconfigurationsforanAPIcall

Thank and Regards,
Menaka

On Thu, Apr 19, 2018 at 1:24 PM, <alapan@valuelabs.com> wrote:

> Hello Team,
>
>
>
> We are facing an issue file working with WSO2 API Manager 2.1.0.
>
>
>
> There is one request for a specific endpoint is continuously failing for
> some reason and as a result, this specific API is getting down and we are
> not getting an response from WSO2 APIM gateway  although we are receiving
> the response from backend API before the socket time out error.  Please
> find the below error we are getting :
>
>
>
> TID: [-1] [] [2018-04-19 04:54:24,294] WARN 
> {org.apache.synapse.transport.passthru.SourceHandler}
> - Connection time out after request is read: http-incoming-106261 Socket
> Timeout : 6 Remote Address : /10.138.120.228:36754
> <https://l.facebook.com/l.php?u=http%3A%2F%2F10.138.120.228%3A36754%2F=ATOl7IzK7wN9mVsfkzG0fh6ZtnMR7L9K40MZWk0LYuJEbmNeWspvtYMO4BNt3VE7oDGgr23jwDtmmzAmNzl9jDrCHFvSnNLITEmpFqP6iWx4v_OkfvIqNnIxGpvMv6PB>
> {org.apache.synapse.transport.passthru.SourceHandler}
>
>
> <http://l.facebook.com/l.php?u=http%3A%2F%2F10.138.120.228%3A36754%2F=ATPsubv-DfKlSaiNx21YeahwUalUYsKADBcz4F-OaA0nNb7IrCxSzP9E4OvrEmhKGyMow8idhB7i0Ij9HBZZRiJUfMgIi7R31JXKm0GM27z_dVvC_69FV9pEg9RG9I6_2afAkKPvJcE=1>
>
>
> Is there any threshold configuration which is configured to handle the
> multiple API failure and WSO2 skips suspend the end point ?
> <http://l.facebook.com/l.php?u=http%3A%2F%2F10.138.120.228%3A36754%2F=ATPsubv-DfKlSaiNx21YeahwUalUYsKADBcz4F-OaA0nNb7IrCxSzP9E4OvrEmhKGyMow8idhB7i0Ij9HBZZRiJUfMgIi7R31JXKm0GM27z_dVvC_69FV9pEg9RG9I6_2afAkKPvJcE=1>
>
>
>
> Can anyone help in this regard ?
>
> Best regards
>
> *Alapan Sur*
>
> Project Manager - SD
>
> ValueLabs - *'inspired by potential'*
>
> Desk: +91-40-6623-9000 | Ext: 32112
>
> Mobile: +91-7799681717
>
> This e-mail may contain information that is proprietary, confidential or
> otherwise protected from disclosure and is sent for the intended
> recipient(s) only. For email disclaimer details, please visit:
>  http://www.valuelabs.com/terms-of-use/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
Software Engineer
WSO2 Inc.

Phone: +94 71 350 5470
LinkedIn : https://lk.linkedin.com/in/menakajayawardena
Blog   : https://menakamadushanka.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues while using Store REST API

[Menaka Jayawardena]

t.ServletController.invokeDes
>> tination(ServletController.java:234)
>> at org.apache.cxf.transport.servlet.ServletController.invoke(
>> ServletController.java:208)
>> at org.apache.cxf.transport.servlet.ServletController.invoke(
>> ServletController.java:160)
>> at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(
>> CXFNonSpringServlet.java:180)
>> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleR
>> equest(AbstractHTTPServlet.java:299)
>> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(
>> AbstractHTTPServlet.java:223)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service
>> (AbstractHTTPServlet.java:274)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:303)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:241)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.core.StandardWrapperValve.invoke(Standar
>> dWrapperValve.java:218)
>> at org.apache.catalina.core.StandardContextValve.invoke(Standar
>> dContextValve.java:122)
>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(A
>> uthenticatorBase.java:505)
>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHo
>> stValve.java:169)
>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo
>> rtValve.java:103)
>> at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInv
>> ocation(CompositeValve.java:99)
>> at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke
>> (CarbonTomcatValve.java:47)
>> at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(Tena
>> ntLazyLoaderValve.java:57)
>> at org.wso2.carbon.event.receiver.core.internal.tenantmgt.Tenan
>> tLazyLoaderValve.invoke(TenantLazyLoaderValve.java:48)
>> at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invok
>> eValves(TomcatValveContainer.java:47)
>> at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(Comp
>> ositeValve.java:62)
>> at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetection
>> Valve.invoke(CarbonStuckThreadDetectionValve.java:159)
>> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogVa
>> lve.java:958)
>> at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.
>> invoke(CarbonContextCreatorValve.java:57)
>> at org.apache.catalina.core.StandardEngineValve.invoke(Standard
>> EngineValve.java:116)
>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd
>> apter.java:452)
>> at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>> tractHttp11Processor.java:1087)
>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
>> .process(AbstractProtocol.java:637)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>> (NioEndpoint.java:1756)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
>> NioEndpoint.java:1715)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>> run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>>
>>
>> Regards,
>> Sivaramya Sivanathan
>> Associate Software Engineer | WSO2
>> Tel: 0770874960
>> WSO2 Inc : http://wso2.org
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org=D=1=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
>> LinkedIn | www.linkedin.com/in/sivaramya
>>
>
>
>
> --
> Regards*,*
> *Viduranga Gunarathne*
> *Software Engineer*
> *WSO2 (Pvt) Ltd.*
>
> *Mobile : *+94712437484 <+94%2071%20243%207484>
> *Email   : *vidura...@wso2.com
> *Web : *http://wso2.com
> *Blog: *http://medium.com/@vlgunarathne
> <http://wso2.com/signature>
>



-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error when provisioning users with the SCIM API.

[Menaka Jayawardena]

Hi devs,

I configured outbound provisioning for Salesforce and invoked the SCIM API
as in the documentation[1].

Here is the curl command that I invoked.

curl -v -k --header "Content-Type:application/json" --user ad...@wso2.com:admin
--data '{"schemas":["urn:scim:schemas:core:1.0"],"userName":"q...@wso2.com
","password":"test25","name":{"familyName":"Menaka12"},"emails":["
q...@wso2.com"],"entitlements":[{"value":"00e7F02DkfY","display":"ChatterFreeUser"}]}'
https://localhost:9443/wso2/scim/Users

But it gives me an exception. (See the attached file).

I also tried the scim2 api as well.

curl -v -k --header "Content-Type:application/json" --user ad...@wso2.com:admin
--data '{"schemas":["urn:scim:schemas:core:1.0"],"userName":"q...@wso2.com
","password":"test25","name":{"familyName":"Menaka12"},"emails":["
q...@wso2.com"],"entitlements":[{"value":"00e7F02DkfY","display":"ChatterFreeUser"}]}'
https://localhost:9443/scim2/Users

But this also gives an error.

{"schemas":"urn:ietf:params:scim:api:messages:2.0:Error","scimType":"invalidSyntax","detail":"Unknown
JSON representation for the MultiValued attribute emails which has data
type as COMPLEX","status":"400"}%

There is no mentioning about the SCIM2 API in the documentation.

Highly appreciate any solution for this.

[1]
https://docs.wso2.com/display/IS540/Outbound+Provisioning+with+Salesforce


Thanks and Regards,
Menaka
-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
[2018-02-02 10:37:44,937] ERROR {org.apache.catalina.core.StandardWrapperValve} 
-  Servlet.service() for servlet [SCIMServlet] in context with path [/wso2] 
threw exception
java.lang.RuntimeException: org.apache.cxf.interceptor.Fault: 
org/wso2/carbon/identity/provisioning/IdentityProvisioningException
at 
org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:116)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:336)
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at 
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:249)
at 
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:248)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:222)
at 
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:153)
at 
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:289)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at 
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:265)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.wso2.carbon.ui.filters.cache.ContentTypeBasedCachePreventionFilter.doFilter(ContentTypeBasedCachePreventionFilter.java:53)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.wso2.carbon.webapp.mgt.filter.AuthorizationHeaderFilter.doFilter(AuthorizationHeaderFilter.java:128)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.c

Re: [Dev] Error when provisioning users with the SCIM API.

[Menaka Jayawardena]

I'm using Identity server v5.4.0-Update 6

On Fri, Feb 2, 2018 at 10:48 AM, Menaka Jayawardena <men...@wso2.com> wrote:

> Hi devs,
>
> I configured outbound provisioning for Salesforce and invoked the SCIM API
> as in the documentation[1].
>
> Here is the curl command that I invoked.
>
> curl -v -k --header "Content-Type:application/json" --user 
> ad...@wso2.com:admin
> --data '{"schemas":["urn:scim:schemas:core:1.0"],"userName":"q...@wso2.com
> ","password":"test25","name":{"familyName":"Menaka12"},"emails":["q123@
> wso2.com"],"entitlements":[{"value":"00e7F02DkfY","display":"ChatterFreeUser"}]}'
> https://localhost:9443/wso2/scim/Users
>
> But it gives me an exception. (See the attached file).
>
> I also tried the scim2 api as well.
>
> curl -v -k --header "Content-Type:application/json" --user 
> ad...@wso2.com:admin
> --data '{"schemas":["urn:scim:schemas:core:1.0"],"userName":"q...@wso2.com
> ","password":"test25","name":{"familyName":"Menaka12"},"emails":["q123@
> wso2.com"],"entitlements":[{"value":"00e7F02DkfY","display":"ChatterFreeUser"}]}'
> https://localhost:9443/scim2/Users
>
> But this also gives an error.
>
> {"schemas":"urn:ietf:params:scim:api:messages:2.0:Error","
> scimType":"invalidSyntax","detail":"Unknown JSON representation for the
> MultiValued attribute emails which has data type as
> COMPLEX","status":"400"}%
>
> There is no mentioning about the SCIM2 API in the documentation.
>
> Highly appreciate any solution for this.
>
> [1] https://docs.wso2.com/display/IS540/Outbound+Provisioning+
> with+Salesforce
>
>
> Thanks and Regards,
> Menaka
> --
> *Menaka Jayawardena*
> *Software Engineer - WSO2 Inc*
> *Tel : 071 350 5470*
> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
> <https://lk.linkedin.com/in/menakajayawardena>*
> *Blog: https://menakamadushanka.wordpress.com/
> <https://menakamadushanka.wordpress.com/>*
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running periodic task inside a microservice

[Menaka Jayawardena]

Hi Miraj,

I also agree with Godwin's idea and +1 for the 2nd option.

Thanks and Regards,
Menaka


On Thu, Jan 18, 2018 at 7:32 PM, Godwin Shrimal <god...@wso2.com> wrote:

> Hi Miraj,
>
> If the microservice only perform this particular task (periodically call
> the resource) I think it's useless to keep running a JVM and I am +1 for
> your second option.
>
>
> Thanks
> Godwin
>
> On Thu, Jan 18, 2018 at 2:58 PM, Miraj Abeysekara <mi...@wso2.com> wrote:
>
>> Hi all,
>>
>> I want to check for a response from 3rd party service to determine the
>> availability of a user in that system and send an email notification once
>> that user is available.
>>
>> I am planning to develop a microservice for the above requirement which
>> periodically calls to that 3rd party service. This can be achieved by,
>>
>>1. Running a timer inside the microservice which calls to the 3rd
>>party service or
>>2. Running an external cron task which calls a resource in my
>>microservice.
>>
>> What would be the good approach to use?
>>
>> Thank you and regards,
>> Miraj
>>
>> --
>> *Miraj Abeysekara*
>> Software Engineer
>> WSO2, Inc.
>>
>> Mobile : +94775690822 <+94%2077%20569%200822>
>> Twitter : https://twitter.com/miragecreator
>> <http://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> <https://www.linkedin.com/in/godwin-amila-2ba26844/>*
> twitter: https://twitter.com/godwinamila
> <http://wso2.com/signature>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Illegal Characters for Registry Resource Path

[Menaka Jayawardena]

Hi Indunil,

There is a set of reserved characters. [1] Those characters have a specific
meaning or usage.
I think due to that reason those are marked as illegal.

Thanks and Regards,
Menaka

[1] https://en.wikipedia.org/wiki/Percent-encoding

On Fri, Jan 12, 2018 at 6:18 PM, Danesh Kuruppu <dan...@wso2.com> wrote:

> Hi Induil,
>
> Don't know exact reason for making them as illegal characters. Found
> related discussion[1]  relates to this. According to the discussion, the
> characters restricted in G-Reg are those that are not allowed by SQL.
>
> 1. http://wso2-oxygen-tank.10903.n7.nabble.com/Using-the-same-
> invalid-characters-for-username-rolesnames-and-Registry-resources-td20256.
> html
> 2. https://wso2.org/jira/browse/CARBON-2980
>
> Thanks
> Danesh
>
> On Fri, Jan 12, 2018 at 5:05 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> For a registry resource path, we have considered following characters as
>> illegal characters (Refer [1]).
>>
>> *~!@#;%^*()+={}|\\<>\"\',*
>>
>> Anyone knows why we have considered that as a limitation in registry?
>> Appreciate your help on this.
>>
>> [1] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.
>> wso2.carbon.registry.core/src/main/java/org/wso2/carbon/regi
>> stry/core/jdbc/Repository.java#L261
>>
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>> Mobile   0772182255
>>
>
>
>
> --
>
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
>
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
> Web: WSO2 Inc <https://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Host name verification issue

[Menaka Jayawardena]

Hi Nuwan,

Thank you very much for the response. Actually, that was the issue. I
debugged through the code and identified that the CN is not equal to the
hostname.
After changing the CN in the backend, it worked properly.

Thanks and Regards,
Menaka

On Thu, Oct 26, 2017 at 11:56 PM, Nuwan Dias <nuw...@wso2.com> wrote:

> The reason for this error is because the cert on your back-end must be
> having a different host than 192.168.8.101:9443 as its CN. To rectify
> this error you either have to deploy a cert which bears 192.168.8.101:9443
> as its CN on the back-end or set the HostnameVerifier property to AllowAll
> on the transportSender of the axis2.xml.
>
> Thanks,
> NuwanD.
>
> On Thu, Oct 26, 2017 at 11:49 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I'm working on configuring API Manager for dynamic SSL profile loading
>> [1]. I need to enable this for PassthroughHTTPSender.
>> I did the configuration in API Manager, axis2.xml and created the custom
>> profile xml, senderprofiles.xml.
>>
>> My backend API is running on 192.168.8.101:9443 and API Manager is on
>> 192.168.8.101:9444.
>> When invoking the published API, I got the error below.
>>
>> [2017-10-26 23:34:50,389] ERROR - TargetHandler I/O error: Host name
>> verification failed for host : 192.168.8.101
>> javax.net.ssl.SSLException: Host name verification failed for host :
>> 192.168.8.101
>> at org.apache.synapse.transport.http.conn.ClientSSLSetupHandler
>> .verify(ClientSSLSetupHandler.java:171)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL
>> IOSession.java:308)
>> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady
>> (SSLIOSession.java:410)
>> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea
>> dy(AbstractIODispatch.java:119)
>> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(
>> BaseIOReactor.java:159)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>> ent(AbstractIOReactor.java:338)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv
>> ents(AbstractIOReactor.java:316)
>> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(
>> AbstractIOReactor.java:277)
>> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI
>> OReactor.java:105)
>> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto
>> r$Worker.run(AbstractMultiworkerIOReactor.java:586)
>> at java.lang.Thread.run(Thread.java:745)
>> [2017-10-26 23:34:50,593]  WARN - EndpointContext Endpoint :
>> admin--Echo_APIproductionEndpoint_0 with address
>> https://192.168.8.101:9443/RESTfulExample/rest/hello/sdsd will be marked
>> SUSPENDED as it failed
>>
>> Here is the configuration in sender profile.
>>
>> 
>> 
>> 192.168.8.101:9443
>> 
>> repository/resources/security/apim.jks
>> JKS
>> wso2carbon
>> wso2carbon
>> 
>> 
>> repository/resources/security/apimtruststore.jks> Location>
>> JKS
>> wso2carbon
>> 
>> 
>> 
>>
>> I added the client cert to apimtruststore.jks.
>>
>> What could be the possible reason for this?
>>
>> [1] https://docs.wso2.com/display/ESB490/Multi-HTTPS+Transpo
>> rt#Multi-HTTPSTransport-DynamicSSLprofiles
>>
>>
>> Thanks and Regards,
>> Menaka
>> --
>> *Menaka Jayawardena*
>> *Software Engineer - WSO2 Inc*
>> *Tel : 071 350 5470*
>> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>*
>> *Blog: https://menakamadushanka.wordpress.com/
>> <https://menakamadushanka.wordpress.com/>*
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <+94%2077%20777%205729>
>



-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Host name verification issue

[Menaka Jayawardena]

Hi,

I'm working on configuring API Manager for dynamic SSL profile loading [1].
I need to enable this for PassthroughHTTPSender.
I did the configuration in API Manager, axis2.xml and created the custom
profile xml, senderprofiles.xml.

My backend API is running on 192.168.8.101:9443 and API Manager is on
192.168.8.101:9444.
When invoking the published API, I got the error below.

[2017-10-26 23:34:50,389] ERROR - TargetHandler I/O error: Host name
verification failed for host : 192.168.8.101
javax.net.ssl.SSLException: Host name verification failed for host :
192.168.8.101
at
org.apache.synapse.transport.http.conn.ClientSSLSetupHandler.verify(ClientSSLSetupHandler.java:171)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:308)
at
org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:410)
at
org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:119)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:586)
at java.lang.Thread.run(Thread.java:745)
[2017-10-26 23:34:50,593]  WARN - EndpointContext Endpoint :
admin--Echo_APIproductionEndpoint_0 with address
https://192.168.8.101:9443/RESTfulExample/rest/hello/sdsd will be marked
SUSPENDED as it failed

Here is the configuration in sender profile.



192.168.8.101:9443

repository/resources/security/apim.jks
JKS
wso2carbon
wso2carbon



repository/resources/security/apimtruststore.jks
JKS
wso2carbon




I added the client cert to apimtruststore.jks.

What could be the possible reason for this?

[1]
https://docs.wso2.com/display/ESB490/Multi-HTTPS+Transport#Multi-HTTPSTransport-DynamicSSLprofiles


Thanks and Regards,
Menaka
-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 4

[Menaka Jayawardena]

Hi All,

I have tested the following functionalities for Android Sense device type.

1. Enrollment
2. Sensor Data publishing and viewing them in device view.
3. Removing device and re-enrolling to a new user.
4. Geo Fencing features.

+1 Stable - Go ahead and release.

Thanks and Regards,
Menaka


On Mon, Aug 14, 2017 at 5:03 PM, Madawa Soysa <mada...@wso2.com> wrote:

> Hi All,
>
> I have tested following functionalities for IOS device type. (v 10.1.1)
>
>- Enrolling device with/without ios-agent.
>- Operation execution (Device lock, Ring, Location, Notification,
>Enterprise-Wipe)
>- Changing platform configurations.
>- Passcode and restriction policies.
>
> No issues were found.
>
> [+] Stable - go ahead and release.
>
> Thanks,
> Madawa
>
> On Fri, Aug 11, 2017 at 7:06 PM, Milan Perera <mi...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> We are pleased to announce the release candidate version 4 of WSO2 IoT Server
>> 3.1.0.
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> Known issues : https://github.com/wso2/product-iots/issues-RC4
>> <https://github.com/wso2/product-iots/issues?q=is%3Aopen+is%3Aissue+label%3A3.1.0-RC3>
>>
>> Source and binary distribution files:
>> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC4
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-iots/tree/v3.1.0-RC4
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thank you
>>
>> Regards,
>> --
>> *Milan Perera *| Senior Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>> Email: mi...@wso2.com <ar...@wso2.com> | Web: www.wso2.com
>> <http://lk.linkedin.com/in/milanharinduperera>
>> <https://wso2.com/signature>
>>
>
>
>
> --
>
> Madawa Soysa / Software Engineer
> mada...@wso2.com / +94714616050 <+94%2071%20461%206050>
>
> *WSO2 Inc.*
> lean.enterprise.middleware
>
>   <https://wso2.com/signature>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 2

[Menaka Jayawardena]

Hi all,

I tested the following scenarios.

*Android Enterprise Install:*

*> Super Tenant mode: Admin User*


   1. Enrolled an Android device as the admin user.
   2. Create and publish an Android App.
   3. Installed the app to the admin user.


*> Super Tenant mode: Normal user.*


   1. Created a new user with proper permissions.
   2. Enrolled an Android Device to that user.
   3. Installed the application to the user.

*> Multitenant Mode.*


   1. Create a new Tenant.
   2. Enrolled an Android Device to the new Tenant user.
   3. Create and published a new Android App.
   4. Installed the app.



*Android Sense. *
1. Enrolled an Android Sense device.
2. Started the data publishing and verified in the UI.

Found no issues.

[+ Stable] Go ahead and Release.

Thanks and Regards,
Menaka


On Tue, Jul 25, 2017 at 5:27 PM, Hasunie Adikari <hasu...@wso2.com> wrote:

> Hi all,
>
> I have tested following scenarios for Windows 10.
>
> 1. Device enrollment.
> 2. Add windows operations
> 3. Create windows policy and apply to the device.
> 4. Edit Windows policy and done apply changes.
> 5. Create more policies and set priority and then apply to the device.
> 6. tested notification pane.
>
> Found no issues.
>
> [+]Stable - go ahead and release
>
>
>
>
>
>
>
> On Tue, Jul 25, 2017 at 5:03 PM, Pasindu Jayaweera <pasin...@wso2.com>
> wrote:
>
>> Hi all,
>> I have tested the following scenarios for Android.
>>
>>- Device enrollment
>>- Device grouping
>>- Device location
>>- Device status update
>>- Device search
>>- Operations (Mute, Message, Ring, Enterprise-Wipe)
>>- Policy (Restriction policy)
>>- App install
>>- Web-clip install
>>
>> Found no issues.
>>
>> [+] Stable - go ahead and release.
>>
>>
>>
>> On Mon, Jul 24, 2017 at 12:28 AM, Madhawa Perera <madha...@wso2.com>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> We are pleased to announce the release candidate version 2 of WSO2 IoT
>>> Server 3.1.0.
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> Known issues : https://github.com/wso2/produc
>>> t-iots/issues?q=is%3Aopen+is%3Aissue+label%3A3.1.0-RC1
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC2
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-iots/tree/v3.1.0-RC2
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thank you
>>> Best Regards,
>>> WSO2 IoT Team
>>>
>>> --
>>> Madhawa Perera
>>> *Software Engineer*
>>> Mobile : +94 (0) 773655496 <+94%2077%20365%205496>
>>> <%2B94%20%280%29%20773%20451194>
>>> madha...@wso2.com
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 IoT Team Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to iot-group+unsubscr...@wso2.com.
>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>
>>
>>
>>
>> --
>> *Pasindu Jayaweera*
>> Software Engineer | WSO2 Inc
>> Mobile: +94 718187375 <+94%2071%20818%207375>
>> Blog: blog.pasindujayaweera.com
>> <http://wso2.com/signature>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Hasunie Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> blog http://hasuniea.blogspot.com | https://medium.com/@Hasunie/
> Mobile:+94713350904 <+94%2071%20335%200904>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] Different logs for the account lock.

[Menaka Jayawardena]

Hi Danushka,

Thank you very much for the response.


On Thu, Jul 6, 2017 at 1:51 PM, Danushka Fernando <danush...@wso2.com>
wrote:

> Hi Menaka
> Reason is here in two methods its handled by two different handlers. What
> we can do is to improve logging in governance handler. You may create a
> jira for that as an improvement.
>
> Thanks & Regards
> Danushka Fernando
> Associate Tech Lead
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729 <+94%2071%20633%202729>
>
> On Thu, Jul 6, 2017 at 11:44 AM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hi,
>>
>> In IS 5.3.0, we can enable account lock in two methods.
>> 1. The file based method, which applies the configuration globally for
>> all the tenants.
>> 2. Enable through the management console.
>>
>> But, the logs in those two cases are looks different.
>>
>> When IS is configured using the method 1, the logs are as follows.
>> [2017-07-06 11:31:23,634]  WARN {org.wso2.carbon.core.services
>> .util.CarbonAuthenticationUtil} -  Failed Administrator login attempt
>> 'menaka[-1234]' at [2017-07-06 11:31:23,634+0530]
>> [2017-07-06 11:31:30,817]  INFO 
>> {org.wso2.carbon.identity.mgt.IdentityMgtEventListener}
>> -  User, menaka has exceed the max failed login attempts. User account
>> would be locked
>> [2017-07-06 11:31:30,839]  WARN {org.wso2.carbon.core.services
>> .util.CarbonAuthenticationUtil} -  Failed Administrator login attempt
>> 'menaka[-1234]' at [2017-07-06 11:31:30,839+0530]
>> [2017-07-06 11:31:36,746]  WARN 
>> {org.wso2.carbon.identity.mgt.IdentityMgtEventListener}
>> -  User account is locked for user : menaka. cannot login until the account
>> is unlocked
>> [2017-07-06 11:31:36,747] ERROR {org.wso2.carbon.core.services
>> .authentication.AuthenticationAdmin} -  System error while
>> Authenticating/Authorizing User : 17003 User account is locked for user :
>> menaka. cannot login until the account is unlocked
>> [2017-07-06 11:31:56,780]  WARN 
>> {org.wso2.carbon.identity.mgt.IdentityMgtEventListener}
>> -  User account is locked for user : menaka. cannot login until the account
>> is unlocked
>> [2017-07-06 11:31:56,785] ERROR {org.wso2.carbon.core.services
>> .authentication.AuthenticationAdmin} -  System error while
>> Authenticating/Authorizing User : 17003 User account is locked for user :
>> menaka. cannot login until the account is unlocked
>>
>> This clearly says that the number of login attempts has exceeded and the
>> account is locked.
>>
>> But, when configured from the Management Console, the logs do not say
>> anything about locked account.
>>
>> [2017-07-06 11:25:23,395]  WARN {org.wso2.carbon.core.services
>> .util.CarbonAuthenticationUtil} -  Failed Administrator login attempt
>> 'menaka[-1234]' at [2017-07-06 11:25:23,395+0530]
>> [2017-07-06 11:25:34,532]  WARN {org.wso2.carbon.core.services
>> .util.CarbonAuthenticationUtil} -  Failed Administrator login attempt
>> 'menaka[-1234]' at [2017-07-06 11:25:34,532+0530]
>> [2017-07-06 11:25:45,019]  WARN {org.wso2.carbon.identity.hand
>> ler.event.account.lock.AccountLockHandler} -  Error occurred while
>> calling triggerNotification, detail : Email notification sending failed.
>> Sending email address is not configured for the user.
>> [2017-07-06 11:25:45,021]  WARN {org.wso2.carbon.core.services
>> .util.CarbonAuthenticationUtil} -  Failed Administrator login attempt
>> 'menaka[-1234]' at [2017-07-06 11:25:45,021+0530]
>> [2017-07-06 11:26:08,792] ERROR {org.wso2.carbon.core.services
>> .authentication.AuthenticationAdmin} -  System error while
>> Authenticating/Authorizing User : Error when handling event :
>> PRE_AUTHENTICATION
>>
>> Can we use the same log for both the scenarios or more specific logs for
>> the second one?
>>
>> Thanks and Regards,
>> Menaka
>>
>> --
>> *Menaka Jayawardena*
>> *Software Engineer - WSO2 Inc*
>> *Tel : 071 350 5470*
>> *LinkedIn: https://lk.linkedin.com/in/menakajayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>*
>> *Blog: https://menakamadushanka.wordpress.com/
>> <https://menakamadushanka.wordpress.com/>*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] Different logs for the account lock.

[Menaka Jayawardena]

Hi,

In IS 5.3.0, we can enable account lock in two methods.
1. The file based method, which applies the configuration globally for all
the tenants.
2. Enable through the management console.

But, the logs in those two cases are looks different.

When IS is configured using the method 1, the logs are as follows.
[2017-07-06 11:31:23,634]  WARN
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
Administrator login attempt 'menaka[-1234]' at [2017-07-06
11:31:23,634+0530]
[2017-07-06 11:31:30,817]  INFO
{org.wso2.carbon.identity.mgt.IdentityMgtEventListener} -  User, menaka has
exceed the max failed login attempts. User account would be locked
[2017-07-06 11:31:30,839]  WARN
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
Administrator login attempt 'menaka[-1234]' at [2017-07-06
11:31:30,839+0530]
[2017-07-06 11:31:36,746]  WARN
{org.wso2.carbon.identity.mgt.IdentityMgtEventListener} -  User account is
locked for user : menaka. cannot login until the account is unlocked
[2017-07-06 11:31:36,747] ERROR
{org.wso2.carbon.core.services.authentication.AuthenticationAdmin} -
 System error while Authenticating/Authorizing User : 17003 User account is
locked for user : menaka. cannot login until the account is unlocked
[2017-07-06 11:31:56,780]  WARN
{org.wso2.carbon.identity.mgt.IdentityMgtEventListener} -  User account is
locked for user : menaka. cannot login until the account is unlocked
[2017-07-06 11:31:56,785] ERROR
{org.wso2.carbon.core.services.authentication.AuthenticationAdmin} -
 System error while Authenticating/Authorizing User : 17003 User account is
locked for user : menaka. cannot login until the account is unlocked

This clearly says that the number of login attempts has exceeded and the
account is locked.

But, when configured from the Management Console, the logs do not say
anything about locked account.

[2017-07-06 11:25:23,395]  WARN
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
Administrator login attempt 'menaka[-1234]' at [2017-07-06
11:25:23,395+0530]
[2017-07-06 11:25:34,532]  WARN
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
Administrator login attempt 'menaka[-1234]' at [2017-07-06
11:25:34,532+0530]
[2017-07-06 11:25:45,019]  WARN
{org.wso2.carbon.identity.handler.event.account.lock.AccountLockHandler} -
 Error occurred while calling triggerNotification, detail : Email
notification sending failed. Sending email address is not configured for
the user.
[2017-07-06 11:25:45,021]  WARN
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  Failed
Administrator login attempt 'menaka[-1234]' at [2017-07-06
11:25:45,021+0530]
[2017-07-06 11:26:08,792] ERROR
{org.wso2.carbon.core.services.authentication.AuthenticationAdmin} -
 System error while Authenticating/Authorizing User : Error when handling
event : PRE_AUTHENTICATION

Can we use the same log for both the scenarios or more specific logs for
the second one?

Thanks and Regards,
Menaka

-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Madhawa Perera

[Menaka Jayawardena]

Congratulations Madhawa!

On Mon, Jun 19, 2017 at 4:45 PM, Chathura Dilan <chathu...@wso2.com> wrote:

> Hi All,
>
> It's my pleasure to welcome Madhawa Perera as a WSO2 Committer.
>
> Madhawa has been a valuable contributor to the IoT team. In recognition
> of his contribution, dedication, and commitment he has been voted as a
> WSO2 committer.
>
> Madhawa, welcome aboard and keep up the good work!
>
> --
> Thanks and Best Regards,
>
> Chatura Dilan Perera
> *Associate Tech Lead** - WSO2 Inc.*
> +94777266673
> www.dilan.me
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Chathurika De Silva

[Menaka Jayawardena]

Congratulations Chathurika.

On Tue, Jun 13, 2017 at 2:33 PM, Dilini Gunatilake <dili...@wso2.com> wrote:

> Congratulations Chathurika :)
>
> On Tue, Jun 13, 2017 at 11:55 AM, Anupama Pathirage <anup...@wso2.com>
> wrote:
>
>> Congratulations Chathurika :)
>>
>> On Tue, Jun 13, 2017 at 11:34 AM, Aparna Karunarathna <apa...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce Chathurika De Silva as a WSO2 Committer.
>>> She is an active member of EE team and has given a great contribution
>>> to ESB, BPS, BRS, App Factory product releases.
>>>
>>> Congratulations Chathurika and keep up the good work...!
>>>
>>> --
>>> *Regards,*
>>>
>>> *Aparna Karunarathna.*
>>>
>>>
>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
>>>
>>> * <http://wso2.com/signature>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Anupama Pathirage
>> Associate Technical Lead
>> WSO2, Inc.  http://wso2.com/
>> Email: anup...@wso2.com
>> Mobile:+94 71 8273 979
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94771162518 <+94%2077%20116%202518>
> dili...@wso2.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Lakshani Gamage

[Menaka Jayawardena]

Congratz Lakshani!

On Tue, Mar 14, 2017 at 9:42 AM, Rushmin Fernando <rush...@wso2.com> wrote:

> Hi All,
>
> It's my pleasure to welcome Lakshani Gamage as a WSO2 Committer.
>
> Lakshani had been a valuable contributor to the App Manager team and she
> is currently a member of the IoT team. In recognition of her contribution,
> dedication, and commitment she has been voted as a WSO2 committer.
>
> Lakshani, welcome aboard and keep up the good work!
>
> Regards,
>
> --
> *Best Regards*
>
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware
>
> mobile : +94775615183
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Nisala Nanayakkara

[Menaka Jayawardena]

Congratz Nisala!

On Thu, Mar 2, 2017 at 3:51 PM, Prakhash Sivakumar <prakh...@wso2.com>
wrote:

> Congrats Nisala! :)
>
> On Thu, Mar 2, 2017 at 2:43 PM, Yasima Dewmini <yas...@wso2.com> wrote:
>
>> Congrats Nisala! :)
>>
>> On Tue, Feb 28, 2017 at 2:41 PM, Shan Mahanama <sh...@wso2.com> wrote:
>>
>>> Congratz nisala :)
>>>
>>> On Tue, Feb 28, 2017 at 2:23 PM, Irunika Weeraratne <irun...@wso2.com>
>>> wrote:
>>>
>>>> Congratulations Nisala
>>>>
>>>> *Irunika Weeraratne*
>>>> *Software Engineer | WSO2, Inc. <http://wso2.com/>*
>>>> *Email : irun...@wso2.com <irun...@wso2.com>*
>>>> *LinkedIn : https://lk.linkedin.com/in/irunika
>>>> <https://lk.linkedin.com/in/irunika>*
>>>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>>>> *Lean . Enterprise . Middleware*
>>>>
>>>>
>>>> On Tue, Feb 28, 2017 at 2:20 PM, Heshitha Hettihewa <heshit...@wso2.com
>>>> > wrote:
>>>>
>>>>> Congratz Nisala!!! :)
>>>>>
>>>>> On Tue, Feb 28, 2017 at 2:18 PM, Chanaka Cooray <chana...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Congratz Nisala :)
>>>>>>
>>>>>> On Tue, Feb 28, 2017 at 2:16 PM, Sinthuja Ragendran <
>>>>>> sinth...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> It's my pleasure to welcome Nisala Nanayakkara as a WSO2 Committer.
>>>>>>>
>>>>>>> Nisala has been a valuable contributor to the Dashboard Server Team
>>>>>>> and then Platform Team. In recognition of his contribution, dedication 
>>>>>>> and
>>>>>>> commitment he has been voted as a WSO2 committer.
>>>>>>>
>>>>>>> Nisala, welcome aboard and keep up the good work!
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sinthuja.
>>>>>>>
>>>>>>> --
>>>>>>> *Sinthuja Rajendran*
>>>>>>> Technical Lead
>>>>>>> WSO2, Inc.:http://wso2.com
>>>>>>>
>>>>>>> Blog: http://sinthu-rajan.blogspot.com/
>>>>>>> Mobile: +94774273955 <+94%2077%20427%203955>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Chanaka Cooray
>>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>>> Email: chana...@wso2.com
>>>>>> Mobile: +94713149860 <+94%2071%20314%209860>
>>>>>> <https://wso2.com/signature>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Heshitha Hettihewa
>>>>> *Software Engineer*
>>>>> Mobile : +94716866386
>>>>> <%2B94%20%280%29%20773%20451194>
>>>>> heshit...@wso2.com
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Shan Mahanama
>>>
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com=gAQEswASa>
>>> Email: sh...@wso2.com
>>> Mobile: +94 71 2000 498
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> http://wso2.com/signatureYasima Dewmini
>> Software Engineer, WSO2, Inc.
>> Email: yas...@wso2.com
>> Mobile: +94713117081 <+94%2071%20311%207081>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prakhash Sivakumar
> Software Engineer | WSO2 Inc
> Platform Security Team
> Mobile : +94771510080 <+94%2077%20151%200080>
> Blog : https://medium.com/@PrakhashS
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Chanaka Cooray

[Menaka Jayawardena]

Congratz Chanaka!

On Fri, Feb 24, 2017 at 3:37 PM, Nisala Nanayakkara <nis...@wso2.com> wrote:

> Congratz Chanaka :D
>
> On Fri, Feb 24, 2017 at 3:36 PM, Niranjan Karunanandham <niran...@wso2.com
> > wrote:
>
>> Hi All,
>>
>> It's my pleasure to welcome Chanaka Cooray as a WSO2 Committer.
>>
>> Chanaka has been a valuable contributor to the Platform Team. In
>> recognition of his contribution, dedication and commitment he has been
>> voted as a WSO2 committer.
>>
>> Chanaka, welcome aboard and keep up the good work!
>>
>> Regards,
>> Nira
>>
>> --
>>
>>
>> *Niranjan Karunanandham*
>> Associate Technical Lead - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Prabushi Samarakoon

[Menaka Jayawardena]

Congratulations Prabushi!

On Tue, Feb 7, 2017 at 9:02 AM, Megala Uthayakumar <meg...@wso2.com> wrote:

> Congrats prabushi :)
>
> On Tue, Feb 7, 2017 at 8:46 AM, Yasima Dewmini <yas...@wso2.com> wrote:
>
>> Congratz Prabushi! :)
>>
>> On Mon, Feb 6, 2017 at 2:13 PM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to welcome Prabushi Samarakoon as a WSO2 Committer.
>>>
>>> Prabushi has been a valuable contributor to WSO2 Dashboard Server and
>>> Integration products. In recognition of her contribution, dedication and
>>> commitment she has being voted as a WSO2 committer.
>>>
>>> Prabushi, welcome aboard and keep up the good work.!
>>>
>>> Thanks.
>>> --
>>> Jagath Ariyarathne
>>> Technical Lead
>>> WSO2 Inc.  http://wso2.com/
>>> Email: jaga...@wso2.com
>>> Mob  : +94 77 386 7048
>>> <http://wso2.com/signature>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> http://wso2.com/signatureYasima Dewmini
>> Software Engineer, WSO2, Inc.
>> Email: yas...@wso2.com
>> Mobile: +94713117081 <+94%2071%20311%207081>
>>
>> _______
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] wso2 iot 3.0 connectedup sample

[Menaka Jayawardena]

[+ Dev@]

On Tue, Jan 31, 2017 at 11:25 AM, Siddheshwar <
siddh...@infrarootsolutions.com> wrote:

> thanks its working...
>
> On 30-Jan-2017 10:44 pm, Menaka Jayawardena <men...@wso2.com> wrote:
>
> Hi Siddheshwar,
>
> Thank you very much for trying out WSO2 IoT Server.
>
> This is an issue with Java 8.
>
> Please replace the pom file in *samples/connectedcup/components/plugin*
> with the attached file.
>
> Thanks and Regards,
> Menaka
>
>
> On Mon, Jan 30, 2017 at 12:39 PM, Siddheshwar Borwandkar <
> siddh...@infrarootsolutions.com> wrote:
>
> i working on *connectedcup* sample .
> when i run "*mvn clean install -f samples-deployer.xml*"
>
> it return build failure.
>
>
>
> [INFO] 
> 
> [INFO] Building WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin 1.0.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @
> org.coffeeking.connectedcup.plugin ---
> [INFO] Deleting /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> org.coffeeking.connectedcup.plugin ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] File encoding has not been set, using platform encoding UTF-8,
> i.e. build is platform dependent!
> [INFO] Compiling 9 source files to /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target/classes
> [INFO]
> [INFO] --- maven-scr-plugin:1.7.2:scr (generate-scr-scrdescriptor) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Class org.coffeeking.connectedcup.pl
> ugin.internal.ConnectedCupServiceComponent is using deprecated javadoc
> tags  at file:/infralabs/servers/wso2iot-3.0.0/samples/connectedcup/
> component/plugin/src/main/java/org/coffeeking/connectedc
> up/plugin/internal/ConnectedCupServiceComponent.java:30
> [WARNING] It is highly recommended to fix these problems, as future
> versions might not support these features anymore.
> [INFO] Generating 2 MetaType Descriptors to /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target/scr-plugin-
> generated/OSGI-INF/metatype/metatype.xml
> [INFO] Writing abstract service descriptor /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target/scr-plugin-
> generated/OSGI-INF/scr-plugin/scrinfo.xml with 1 entries.
> [INFO] Generating 1 Service Component Descriptors to
> /infralabs/servers/wso2iot-3.0.0/samples/connectedcup/compon
> ent/plugin/target/scr-plugin-generated/OSGI-INF/serviceComponents.xml
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources
> (default-testResources) @ org.coffeeking.connectedcup.plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/src/test/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile)
> @ org.coffeeking.connectedcup.plugin ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.18:test (default-test) @
> org.coffeeking.connectedcup.plugin ---
> [INFO]
> [INFO] --- maven-bundle-plugin:1.4.0:bundle (default-bundle) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.bind.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.bind.annotation.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.parsers.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> org.wso2.carbon.context.*
> [WARNING] Warning building bundle org.coffeeking:org.co

Re: [Dev] wso2 iot 3.0 connectedup sample

[Menaka Jayawardena]

offeeking:org.coffeeking.connectedcup.plugin:bundle:1.0.0 : Unresolved
> references to [org.wso2.carbon.base] by class(es) on the
> Bundle-Classpath[Jar:dot]:
> [org/coffeeking/connectedcup/plugin/impl/ConnectedCupManagerService.class]*
> *[ERROR] Error(s) found in bundle configuration*
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Component . SUCCESS [0.730s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Component . SUCCESS [0.036s]
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Analytics capp  SUCCESS
> [1.028s]
> *[INFO] WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin  FAILURE
> [3.423s]*
> [INFO] WSO2 IoTS(Device Types) - Connected Cup API ... SKIPPED
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Agent Web app  SKIPPED
> [INFO] WSO2 IoTS(Device Types) - Connected Cup UI  SKIPPED
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Feature Parent  SKIPPED
> [INFO] WSO2 IoTS(Device Types) - Connected Cup Feature ... SKIPPED
> [INFO] Creating custom distribution .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 5.766s
> [INFO] Finished at: Mon Jan 30 12:15:17 IST 2017
> [INFO] Final Memory: 33M/297M
> [INFO] 
> 
> *[ERROR] Failed to execute goal
> org.apache.felix:maven-bundle-plugin:1.4.0:bundle (default-bundle) on
> project org.coffeeking.connectedcup.plugin: Error(s) found in bundle
> configuration -> [Help 1]*
> *[ERROR] *
> *[ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.*
> *[ERROR] Re-run Maven using the -X switch to enable full debug logging.*
> *[ERROR] *
> *[ERROR] For more information about the errors and possible solutions,
> please read the following articles:*
> *[ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> <http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>*
> *[ERROR] *
> *[ERROR] After correcting the problems, you can resume the build with the
> command*
> *[ERROR]   mvn  -rf :org.coffeeking.connectedcup.plugin*
>
>
>
>
>
> *please guide me .*
>
> *thank you*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*



http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
		 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;>
	
		device-mgt-iot-connectedcup
		org.coffeeking
		1.0.0
		../pom.xml
	

	4.0.0
	org.coffeeking.connectedcup.plugin
	1.0.0
	bundle
WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin
WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin
	http://wso2.org

	
		
			
org.apache.felix
maven-scr-plugin
			
			
maven-compiler-plugin

	1.7
	1.7

2.3.2
			
			
org.apache.felix
maven-bundle-plugin
1.4.0
true

	
		${project.artifactId}
		${project.artifactId}
		${carbon.device.mgt.plugin.version}
		IoT Server Impl Bundle
		org.coffeeking.connectedcup.plugin.internal
		
			org.osgi.framework,
			org.osgi.service.component,
			org.apache.commons.logging,
			javax.xml.bind.*;resolution:=optional,
			javax.naming;resolution:=optional,
			javax.sql;resolution:=optional,
			javax.xml.bind.annotation.*;resolution:=optional,
			javax.net;resolution:=optional,
			javax.net.ssl;resolution:=optional,
			org.w3c.dom;resolution:=optional,
			org.wso2.carbon.device.mgt.common.*,
			org.wso2.carbon.device.mgt.common,
			org.wso2.carbon.context.*,
			org.wso2.carbon.base.*,
			org.wso2.carbon.ndatasource.core,
			javax.xml.parsers.*;resolution:=optional
		

		
			!org.coffeeking.connectedcup.plugin.internal,
			org.coffeeking.connectedcup.plugin.*
		
	

			
		
	

	
		
			org.eclipse.osgi
			org.eclipse.osgi
		
		
			org.eclipse.osgi
			org.eclipse.osgi.services
		

		
			org.wso2.carbon
			org.wso2.carbon.logging
		

		
			org.wso2.carbon.devicemgt
			org.wso2.carbon.device.mgt.common
		
		
			org.wso2.carbon
			org.wso2.carbon.ndatasource.core
		
	


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

Re: [Dev] WSO2 Committers += Sudharma Subasinghe

[Menaka Jayawardena]

Congratulations Sudharma!

On Fri, Jan 27, 2017 at 9:14 AM, Hasitha Aravinda <hasi...@wso2.com> wrote:

> Hi All,
>
> It is my pleasure to welcome Sudharma Subasinghe as a WSO2 Committer.
> Sudharma has been a valuable contributor to WSO2 Business Process
> Server and in Integration space. In recognition of her commitment and
> contributions, she has been voted as a WSO2 Committer.
>
> Sudharma, welcome aboard and keep up the good work.!
>
> Thanks,
> Hasitha.
>
> --
> --
> Hasitha Aravinda,
> Associate Technical Lead,
> WSO2 Inc.
> Email: hasi...@wso2.com
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 IoT Server 3.0.0 RC2

[Menaka Jayawardena]

Hi I have tested the following,

1. Enrolling android sense.
2. Publishing data
3. View them in the portal dashboard graphs.
  - Sensor data
  - Realtime data
  - Location
  - Battery history
  - Communication

[+] Stable - go ahead and release.

Thanks,
Menaka


On Jan 21, 2017 10:33 AM, "Lakshani Gamage"  wrote:

Hi,

I have tested below.

   - App Management integration.
   - Add/Edit users and Roles.
   - Enroll Android devices

[+]Stable - go ahead and release
Thanks,

On Sat, Jan 21, 2017 at 10:09 AM, Kamidu Punchihewa 
wrote:

> Hi all,
>
> I have tested the followings.
>
>- Adding users and roles.
>   - Verify using both devicemgt cnsole and carbon console.
>- Assigning permissions to roles.
>   - Verify using both devicemgt cnsole and carbon console.
>- Enroll Android devices.
>- Enroll Androidsense devices.
>- Verify the device views
>   - Android device view
>   - Androidsense device view
>   - IOS device view
>- Device Search
>- Goe Dashboard
>   - For Android devices
>   - For Androidsense devices
>
> [+] Stable - go ahead and release.
>
> Thanks and Best Regards
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> On Sat, Jan 21, 2017 at 10:01 AM, Sameera Gunarathne 
> wrote:
>
>> Hi,
>>
>> I have tested followings:
>>
>>- Creating and updating device groups
>>- Group sharing among roles
>>- Group Policy appliance for android devices
>>- Group actions listing based on group owner permissions
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks & Regards,
>> Sameera.
>>
>> On Sat, Jan 21, 2017 at 9:14 AM, Geeth Munasinghe  wrote:
>>
>>> Hi all,
>>>
>>> I have tested the followings.
>>>
>>>- Adding users and roles.
>>>- Assigning permissions to roles.
>>>- Enroll Android devices.
>>>- Creating device groups.
>>>- Assigning devices to groups.
>>>- Creating policies.
>>>- Editing policies.
>>>- Changing policy priorities.
>>>- Applying changed policies to devices.
>>>- Device Search
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks
>>> Geeth
>>>
>>> On Sat, Jan 21, 2017 at 8:04 AM, Hasunie Adikari 
>>> wrote:
>>>
 Hi,

 I have tested following scenarios,

- Enroll Windows 10(version 1511,1607) and Windows 8.1 Devices
- Add Device lock, ring, wipe, location, lock-reset, reboot
operations.
- Add Passcode, Camera restriction and Storage encryption policies.
- Dis-enroll device
- Dis enroll device and re enroll the device from different user.
- Create new user with permissions.
- Enroll the device for that new user and execute operations and
policies for that user.
- Enroll 3 Android Devices and 3 Windows Devices and grouping them.
- Check Notification pane by adding notifications.

 [+] Stable - go ahead and release.

 Reagards
 Hasunie


 On Sat, Jan 21, 2017 at 6:13 AM, Chathura Dilan 
 wrote:

> Hi,
>
> I've tested
>
>- Android app enrollment installation and un-installation,
>policies and operations
>- App Management
>
>
>  [+] Stable - go ahead and release
>
>
> On Sat, Jan 21, 2017 at 5:18 AM, Jasintha Dasanayake <
> jasin...@wso2.com> wrote:
>
>> Hi All
>>
>> I have tested the following flows using the virtual firearm plugin :
>>
>>- Operation flows
>>- Grouping devices
>>- Applying and updating policy for individual & grouped devices
>>- Realtime analytics
>>
>> [+] Stable-go ahead and release
>>
>> Regards
>> /Jasintha
>>
>>
>> On Sat, Jan 21, 2017 at 2:27 AM, Ayyoob Hamza 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested following:
>>>
>>>- Tested below flows using the reference device types
>>>implementation(Virtual firealarm, Connected cup, Raspberry pi).
>>>- Operation flow
>>>   - Policy
>>>   - 

Re: [Dev] Integration tests for WSO2 IOT Server

[Menaka Jayawardena]

Hi,

The issue was fixed with custom extensions and it's working fine.

Thank you very much for the help guys.

Best regards,
Menaka


On Wed, Jan 4, 2017 at 10:27 AM, Menaka Jayawardena <men...@wso2.com> wrote:

> Hi Sumedha,
>
> When using the single script, it does not start the servers. It hangs
> until timeout.
>
> I think as Nuwan mentioned, we have to write a custom extension to start
> the servers that we need. But the problem it, if we do so we have to
> rewrite the whole flow as test framework has concrete classes to get the
> carbon home dir and start the server. We have to change that.
>
> I also spoke to Azeez regarding this issue and he said that we have to
> debug the test framework and find the issue. So we can fix it and get a
> release from them.
>
> Thanks and Regards,
> Menaka
>
>
> On Wed, Jan 4, 2017 at 9:31 AM, Sumedha Rubasinghe <sume...@wso2.com>
> wrote:
>
>> Menaka,
>> For now, shall we not start the servers using this single script?. It's
>> bit complex to trouble shoot with all logs going to a single file.
>>
>> On Tue, Jan 3, 2017 at 12:48 PM, Menaka Jayawardena <men...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> In IOTS we have 3 separate servers (Analytics, Broker and IOT Core),
>>> which are invoked by a single shell script. (Or we can manually start each
>>> server individually). And in order to execute a full IOT scenario, all the
>>> three servers have to be up and running.
>>>
>>> There were some integration tests which were written before this change
>>> (Separating the servers), which test scenarios such as user login, device
>>> type installation, and virtual device enrollment etc.
>>>
>>> As Test Automation Framework looks for wso2server.sh in
>>> {carbon_home}/bin directory, I renamed the script. (was start-all.sh)
>>>
>>> When running, I got the following error.
>>>
>>> I think as the servers are started in processes forked by the
>>> 'start-all' script TAF does not have the access to the logs.
>>>
>>> Is there any fix for this issue?
>>>
>>> Can we change the script location in test configuration file?
>>>
>>> - ERROR MSG --
>>>
>>> INFO: Starting carbon server.
>>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.ext
>>> ensions.servers.carbonserver.CarbonServerExtension handleException
>>> SEVERE: Fail to start carbon server
>>> java.lang.RuntimeException: Port 9763 is not open
>>> at org.wso2.carbon.automation.extensions.servers.utils.ClientCo
>>> nnectionUtil.waitForPort(ClientConnectionUtil.java:248)
>>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>>> arbonServerManager.startServerUsingCarbonHome(CarbonServerMa
>>> nager.java:120)
>>> at org.wso2.carbon.automation.extensions.servers.carbonserver.T
>>> estServerManager.startServer(TestServerManager.java:116)
>>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>>> arbonServerExtension.onExecutionStart(CarbonServerExtension.java:50)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.wso2.carbon.automation.engine.extensions.TestNGExtension
>>> Executor.executeExtensible(TestNGExtensionExecutor.java:75)
>>> at org.wso2.carbon.automation.engine.testlisteners.TestExecutio
>>> nListener.onExecutionStart(TestExecutionListener.java:47)
>>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
>>> at org.testng.TestNG.run(TestNG.java:1015)
>>> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGEx
>>> ecutor.java:295)
>>> at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(
>>> TestNGXmlTestSuite.java:84)
>>> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestN
>>> GProvider.java:90)
>>> at org.apache.maven.surefire.booter.ForkedBooter.invokeProvider
>>> InSameClassLoader(ForkedBooter.java:203)
>>> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro
>>> cess(ForkedBooter.java:155)
>>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo
>>> ter.java:103)
>>>
>>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.eng
>&

Re: [Dev] WSO2 Committers += Sajith Perera

[Menaka Jayawardena]

Congratulations Sajith..!

On Thu, Jan 5, 2017 at 11:16 AM, Fazlan Nazeem <fazl...@wso2.com> wrote:

> Congratulations Sajith!
>
> On Thu, Jan 5, 2017 at 11:07 AM, Grainier Perera <grain...@wso2.com>
> wrote:
>
>> Congratz Sajith..!! :)
>>
>> On Thu, Jan 5, 2017 at 8:32 AM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> It is my pleasure to welcome Sajith Perera as a WSO2 Committer. Sajith
>>> has been a valuable contributor in WSO2 analytics space and performed
>>> enormous tasks on CEP tooling, CEP HA and Log Analyzer.
>>>
>>> SajithD, welcome aboard and keep up the good work.
>>>
>>>
>>> Thanks,
>>> Mohan
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Associate Tech Lead,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com <http://wso2.com> *
>>> *lean.enterprise.middleware.*
>>>
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673 <+94%2077%20111%207673>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Grainier Perera
>> Software Engineer
>> Mobile : +94716122384 <+94%2071%20612%202384>
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> 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
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470/ 071 885 1183*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Integration tests for WSO2 IOT Server

[Menaka Jayawardena]

Hi Sumedha,

When using the single script, it does not start the servers. It hangs until
timeout.

I think as Nuwan mentioned, we have to write a custom extension to start
the servers that we need. But the problem it, if we do so we have to
rewrite the whole flow as test framework has concrete classes to get the
carbon home dir and start the server. We have to change that.

I also spoke to Azeez regarding this issue and he said that we have to
debug the test framework and find the issue. So we can fix it and get a
release from them.

Thanks and Regards,
Menaka


On Wed, Jan 4, 2017 at 9:31 AM, Sumedha Rubasinghe <sume...@wso2.com> wrote:

> Menaka,
> For now, shall we not start the servers using this single script?. It's
> bit complex to trouble shoot with all logs going to a single file.
>
> On Tue, Jan 3, 2017 at 12:48 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hi,
>>
>> In IOTS we have 3 separate servers (Analytics, Broker and IOT Core),
>> which are invoked by a single shell script. (Or we can manually start each
>> server individually). And in order to execute a full IOT scenario, all the
>> three servers have to be up and running.
>>
>> There were some integration tests which were written before this change
>> (Separating the servers), which test scenarios such as user login, device
>> type installation, and virtual device enrollment etc.
>>
>> As Test Automation Framework looks for wso2server.sh in {carbon_home}/bin
>> directory, I renamed the script. (was start-all.sh)
>>
>> When running, I got the following error.
>>
>> I think as the servers are started in processes forked by the 'start-all'
>> script TAF does not have the access to the logs.
>>
>> Is there any fix for this issue?
>>
>> Can we change the script location in test configuration file?
>>
>> - ERROR MSG --
>>
>> INFO: Starting carbon server.
>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.ext
>> ensions.servers.carbonserver.CarbonServerExtension handleException
>> SEVERE: Fail to start carbon server
>> java.lang.RuntimeException: Port 9763 is not open
>> at org.wso2.carbon.automation.extensions.servers.utils.ClientCo
>> nnectionUtil.waitForPort(ClientConnectionUtil.java:248)
>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>> arbonServerManager.startServerUsingCarbonHome(CarbonServerMa
>> nager.java:120)
>> at org.wso2.carbon.automation.extensions.servers.carbonserver.T
>> estServerManager.startServer(TestServerManager.java:116)
>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>> arbonServerExtension.onExecutionStart(CarbonServerExtension.java:50)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.wso2.carbon.automation.engine.extensions.TestNGExtension
>> Executor.executeExtensible(TestNGExtensionExecutor.java:75)
>> at org.wso2.carbon.automation.engine.testlisteners.TestExecutio
>> nListener.onExecutionStart(TestExecutionListener.java:47)
>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
>> at org.testng.TestNG.run(TestNG.java:1015)
>> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGEx
>> ecutor.java:295)
>> at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(
>> TestNGXmlTestSuite.java:84)
>> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestN
>> GProvider.java:90)
>> at org.apache.maven.surefire.booter.ForkedBooter.invokeProvider
>> InSameClassLoader(ForkedBooter.java:203)
>> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro
>> cess(ForkedBooter.java:155)
>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo
>> ter.java:103)
>>
>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.eng
>> ine.testlisteners.TestExecutionListener handleException
>> SEVERE: Execution error occurred in TestExecutionListener:-
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.wso2.carbon.automation.engine.extensions.TestNGExtension
&

Re: [Dev] Integration tests for WSO2 IOT Server

[Menaka Jayawardena]

Looping IOT team

On Tue, Jan 3, 2017 at 5:04 PM, Menaka Jayawardena <men...@wso2.com> wrote:

> Hi Nuwan,
>
> The Server does not start and the testing process hangs at 'INFO: Starting
> Carbon Server...' until the timeout.
>
> Another way is that You can write an extension to start the servers
>> separately
>
>
> Yes. I also think this would be a better option. I'll look into that.
>
> Thank you very much Nuwan.
>
> Best regards.
> Menaka
>
>
>
> On Tue, Jan 3, 2017 at 1:58 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Hi Menaka,
>>
>> Is the server started on port 9763? Please make sure that service is
>> started properly
>>
>> Another ways is that You can write a extension to start the servers
>> separately.
>>
>> Thanks,
>> Nuwanw
>>
>> On Tue, Jan 3, 2017 at 12:48 PM, Menaka Jayawardena <men...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> In IOTS we have 3 separate servers (Analytics, Broker and IOT Core),
>>> which are invoked by a single shell script. (Or we can manually start each
>>> server individually). And in order to execute a full IOT scenario, all the
>>> three servers have to be up and running.
>>>
>>> There were some integration tests which were written before this change
>>> (Separating the servers), which test scenarios such as user login, device
>>> type installation, and virtual device enrollment etc.
>>>
>>> As Test Automation Framework looks for wso2server.sh in
>>> {carbon_home}/bin directory, I renamed the script. (was start-all.sh)
>>>
>>> When running, I got the following error.
>>>
>>> I think as the servers are started in processes forked by the
>>> 'start-all' script TAF does not have the access to the logs.
>>>
>>> Is there any fix for this issue?
>>>
>>> Can we change the script location in test configuration file?
>>>
>>> - ERROR MSG --
>>>
>>> INFO: Starting carbon server.
>>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.ext
>>> ensions.servers.carbonserver.CarbonServerExtension handleException
>>> SEVERE: Fail to start carbon server
>>> java.lang.RuntimeException: Port 9763 is not open
>>> at org.wso2.carbon.automation.extensions.servers.utils.ClientCo
>>> nnectionUtil.waitForPort(ClientConnectionUtil.java:248)
>>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>>> arbonServerManager.startServerUsingCarbonHome(CarbonServerMa
>>> nager.java:120)
>>> at org.wso2.carbon.automation.extensions.servers.carbonserver.T
>>> estServerManager.startServer(TestServerManager.java:116)
>>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>>> arbonServerExtension.onExecutionStart(CarbonServerExtension.java:50)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:62)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at org.wso2.carbon.automation.engine.extensions.TestNGExtension
>>> Executor.executeExtensible(TestNGExtensionExecutor.java:75)
>>> at org.wso2.carbon.automation.engine.testlisteners.TestExecutio
>>> nListener.onExecutionStart(TestExecutionListener.java:47)
>>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
>>> at org.testng.TestNG.run(TestNG.java:1015)
>>> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGEx
>>> ecutor.java:295)
>>> at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(
>>> TestNGXmlTestSuite.java:84)
>>> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestN
>>> GProvider.java:90)
>>> at org.apache.maven.surefire.booter.ForkedBooter.invokeProvider
>>> InSameClassLoader(ForkedBooter.java:203)
>>> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro
>>> cess(ForkedBooter.java:155)
>>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo
>>> ter.java:103)
>>>
>>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.eng
>>> ine.testlisteners.TestExecutionListener handleException
>>> SEVERE: Execution error occurred in TestExecutionListener:-
>>> java.lang.reflect.InvocationTargetEx

Re: [Dev] Integration tests for WSO2 IOT Server

[Menaka Jayawardena]

Hi Nuwan,

The Server does not start and the testing process hangs at 'INFO: Starting
Carbon Server...' until the timeout.

Another way is that You can write an extension to start the servers
> separately


Yes. I also think this would be a better option. I'll look into that.

Thank you very much Nuwan.

Best regards.
Menaka



On Tue, Jan 3, 2017 at 1:58 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote:

> Hi Menaka,
>
> Is the server started on port 9763? Please make sure that service is
> started properly
>
> Another ways is that You can write a extension to start the servers
> separately.
>
> Thanks,
> Nuwanw
>
> On Tue, Jan 3, 2017 at 12:48 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hi,
>>
>> In IOTS we have 3 separate servers (Analytics, Broker and IOT Core),
>> which are invoked by a single shell script. (Or we can manually start each
>> server individually). And in order to execute a full IOT scenario, all the
>> three servers have to be up and running.
>>
>> There were some integration tests which were written before this change
>> (Separating the servers), which test scenarios such as user login, device
>> type installation, and virtual device enrollment etc.
>>
>> As Test Automation Framework looks for wso2server.sh in {carbon_home}/bin
>> directory, I renamed the script. (was start-all.sh)
>>
>> When running, I got the following error.
>>
>> I think as the servers are started in processes forked by the 'start-all'
>> script TAF does not have the access to the logs.
>>
>> Is there any fix for this issue?
>>
>> Can we change the script location in test configuration file?
>>
>> - ERROR MSG --
>>
>> INFO: Starting carbon server.
>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.ext
>> ensions.servers.carbonserver.CarbonServerExtension handleException
>> SEVERE: Fail to start carbon server
>> java.lang.RuntimeException: Port 9763 is not open
>> at org.wso2.carbon.automation.extensions.servers.utils.ClientCo
>> nnectionUtil.waitForPort(ClientConnectionUtil.java:248)
>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>> arbonServerManager.startServerUsingCarbonHome(CarbonServerMa
>> nager.java:120)
>> at org.wso2.carbon.automation.extensions.servers.carbonserver.T
>> estServerManager.startServer(TestServerManager.java:116)
>> at org.wso2.carbon.automation.extensions.servers.carbonserver.C
>> arbonServerExtension.onExecutionStart(CarbonServerExtension.java:50)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.wso2.carbon.automation.engine.extensions.TestNGExtension
>> Executor.executeExtensible(TestNGExtensionExecutor.java:75)
>> at org.wso2.carbon.automation.engine.testlisteners.TestExecutio
>> nListener.onExecutionStart(TestExecutionListener.java:47)
>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
>> at org.testng.TestNG.run(TestNG.java:1015)
>> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGEx
>> ecutor.java:295)
>> at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(
>> TestNGXmlTestSuite.java:84)
>> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestN
>> GProvider.java:90)
>> at org.apache.maven.surefire.booter.ForkedBooter.invokeProvider
>> InSameClassLoader(ForkedBooter.java:203)
>> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro
>> cess(ForkedBooter.java:155)
>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo
>> ter.java:103)
>>
>> Jan 03, 2017 12:08:15 PM org.wso2.carbon.automation.eng
>> ine.testlisteners.TestExecutionListener handleException
>> SEVERE: Execution error occurred in TestExecutionListener:-
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.wso2.carbon.automation.engine.extensions.TestNGExtension
>> Executor.executeExtensible(TestNGExtensionExecutor.java:75)
>> at org.wso2.carbon.automation.engine.testlisteners.TestExecutio
>> nLis

[Dev] Integration tests for WSO2 IOT Server

[Menaka Jayawardena]

:116)
at org.wso2.carbon.automation.extensions.servers.carbonserver.
CarbonServerExtension.onExecutionStart(CarbonServerExtension.java:50)
... 14 more

---


Thanks and regards,
Menaka

-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470/ 071 885 1183*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Kanapriya Kuleswararajan

[Menaka Jayawardena]

Congratulations Kanapriya!

Best Regards,
Menaka

On Tue, Dec 6, 2016 at 4:08 PM, Biruntha Gnaneswaran <birun...@wso2.com>
wrote:

> Congratulations Kanapriya
>
> Biruntha
>
> Associate Software Engineer
> WSO2
> Email : birun...@wso2.com
> Linkedin : https://lk.linkedin.com/in/biruntha
> Mobile : +94773718986 <+94%2077%20371%208986>
>
> On Tue, Dec 6, 2016 at 3:49 PM, Yashothara Shanmugarajah <
> yashoth...@wso2.com> wrote:
>
>> Congratulations Kanapriya :)
>>
>> Best Regards,
>> Yashothara.S
>> Software Engineer
>> WSO2
>> http://wso2.com
>> https://wso2.com/signature
>> <https://www.google.com/url?q=https%3A%2F%2Fwso2.com%2Fsignature=D=1=AFQjCNFqSCK3YQC9g0l53f6yjvsVrxRHXg>
>>
>> On Tue, Dec 6, 2016 at 3:44 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Congratulations Kanapriya :)
>>>
>>> On Tue, Dec 6, 2016 at 3:22 PM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> Its my pleasure to welcome Kanapriya Kuleswararajan as a WSO2
>>>> Committer.
>>>>
>>>> She has been working with the WSO2 Platform Extensions Team for a while
>>>> and has contributed to  ESB and IS product extensions,
>>>>
>>>> Kanapriya, welcome aboard and keep up the good work.
>>>>
>>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Technical Lead
>>>> M: +94 777 219 791 <+94%2077%20721%209791>
>>>> Tel : 94 11 214 5345
>>>> Fax :94 11 2145300
>>>> Skype : malaka.sampath.silva
>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>
>>>> WSO2, Inc.
>>>> lean . enterprise . middleware
>>>> https://wso2.com/signature
>>>> http://www.wso2.com/about/team/malaka-silva/
>>>> <http://wso2.com/about/team/malaka-silva/>
>>>> https://store.wso2.com/store/
>>>>
>>>> Don't make Trees rare, we should keep them with care
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167 <+94%2077%20436%203167>
>>>
>>> <http://wso2.com/signature>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470/ 071 885 1183*
*LinkedIn: https://lk.linkedin.com/in/menakajayawardena
<https://lk.linkedin.com/in/menakajayawardena>*
*Blog: https://menakamadushanka.wordpress.com/
<https://menakamadushanka.wordpress.com/>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Malintha Fernando

[Menaka Jayawardena]

Congratz Malintha.!

On Tue, Nov 8, 2016 at 2:46 PM, Irunika Weeraratne <irun...@wso2.com> wrote:

> Congratulations Malintha!!!
>
> Best Regards,
> Irunika
>
> *Irunika Weeraratne*
> *Software Engineer | WSO2, Inc. <http://wso2.com/>*
> *Email : irun...@wso2.com <irun...@wso2.com>*
> *LinkedIn : https://lk.linkedin.com/in/irunikaw
> <https://lk.linkedin.com/in/irunikaw>*
> *Mobile : +94712403314 <%2B94712403314>*
> *Lean . Enterprise . Middleware*
>
>
> On Tue, Nov 8, 2016 at 2:43 PM, Sameera Gunarathne <samee...@wso2.com>
> wrote:
>
>> Congrats Malintha!!!
>>
>> On Tue, Nov 8, 2016 at 2:38 PM, Maneesha Wijesekara <manee...@wso2.com>
>> wrote:
>>
>>> Congratulations Malintha..!!
>>>
>>> On Tue, Nov 8, 2016 at 1:47 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>>> wrote:
>>>
>>>> Congrats Malintha :)
>>>>
>>>> On Tue, Nov 8, 2016 at 1:45 PM, Heshitha Hettihewa <heshit...@wso2.com>
>>>> wrote:
>>>>
>>>>> Congratz Malintha!!!
>>>>>
>>>>> On Tue, Nov 8, 2016 at 1:32 PM, Chandana Napagoda <chand...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> It is my pleasure to welcome Malintha Fernando as a WSO2 Committer.
>>>>>> Malintha has made some great contributions to WSO2 Governance Registry 
>>>>>> and
>>>>>> WSO2 Enterprise Store products during the last few months and in
>>>>>> recognition of his commitment and contributions, he has been voted as a
>>>>>> Committer for WSO2.
>>>>>>
>>>>>> @Malintha, welcome aboard and keep up the good work.
>>>>>>
>>>>>> Best Regards,
>>>>>> Chandana
>>>>>>
>>>>>> --
>>>>>> *Chandana Napagoda*
>>>>>> Associate Technical Lead
>>>>>> WSO2 Inc. - http://wso2.org
>>>>>>
>>>>>> *Email  :  chand...@wso2.com <chand...@wso2.com>**Mobile :
>>>>>> +94718169299 <%2B94718169299>*
>>>>>>
>>>>>> *Blog  :http://cnapagoda.blogspot.com
>>>>>> <http://cnapagoda.blogspot.com> | http://chandana.napagoda.com
>>>>>> <http://chandana.napagoda.com>*
>>>>>>
>>>>>> *Linkedin : http://www.linkedin.com/in/chandananapagoda
>>>>>> <http://www.linkedin.com/in/chandananapagoda>*
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Heshitha Hettihewa
>>>>> *Software Engineer*
>>>>> Mobile : +94716866386
>>>>> <%2B94%20%280%29%20773%20451194>
>>>>> heshit...@wso2.com
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>>
>>>> Dilshani Subasinghe
>>>> Software Engineer - QA *|* WSO2
>>>> lean *|* enterprise *|* middleware
>>>>
>>>> Mobile : +94773375185
>>>> Blog: dilshani.me
>>>>
>>>> <https://wso2.com/signature>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Maneesha Wijesekara
>>> Software Engineer - EE 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
>>>
>>>
>>
>>
>> --
>> Sameera Gunarathne
>> Software Engineer, WSO2 Inc. http://wso2.com
>> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com=gAQEswASa>
>> Email: samee...@wso2.com
>> Mobile: +94714155561
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470/ 071 885 1183*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Shan Mahanama

[Menaka Jayawardena]

Congratz Shan!

On Mon, Nov 7, 2016 at 1:21 PM, Fathima Dilhasha <dilha...@wso2.com> wrote:

> Congratz Shan :)
>
> On Mon, Nov 7, 2016 at 1:05 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Congratz Shan!!!
>>
>> On Mon, Nov 7, 2016 at 12:14 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> It's my pleasure to announce Shan Mahanama as a WSO2 Committer. Shan has
>>> been a valuable contributor for Platform team. And in recognition of his
>>> contribution to WSO2, he has been voted as a WSO2 Committer.
>>>
>>> Shan, Congratulations and keep up the good work!
>>>
>>> Regards,
>>> Nira.
>>>
>>> --
>>>
>>>
>>> *Niranjan Karunanandham*
>>> Associate Technical Lead - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>> <http://wso2.com/signature>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Fathima Dilhasha
> *Software Engineer*
> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
> <%2B94%20%280%29%20773%20451194>
> dilha...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Menaka Jayawardena*
*Software Engineer - WSO2 Inc*
*Tel : 071 350 5470/ 071 885 1183*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Megala Uthayakumar

[Menaka Jayawardena]

Congratulations Megala!

On Wed, Nov 2, 2016 at 12:21 PM, Yasima Dewmini <yas...@wso2.com> wrote:

> Congratz Megala :)
>
> On Wed, Nov 2, 2016 at 11:06 AM, Biruntha Gnaneswaran <birun...@wso2.com>
> wrote:
>
>> Congratulations Megala.
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Wed, Nov 2, 2016 at 10:50 AM, Prabushi Samarakoon <prabus...@wso2.com>
>> wrote:
>>
>>> Congratulations Megala :)
>>>
>>> On Wed, Nov 2, 2016 at 10:29 AM, Fathima Dilhasha <dilha...@wso2.com>
>>> wrote:
>>>
>>>> Congratz Megala :D
>>>>
>>>> On Tue, Nov 1, 2016 at 2:21 PM, Sinthuja Ragendran <sinth...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> It's my pleasure to announce Megala Uthayakumar as a WSO2 Committer.
>>>>> Megala had been a valuable contributor for Dashboard Server product, and
>>>>> now for EMM/IoT Products. And in recognition of her contribution to WSO2,
>>>>> she has been voted as a WSO2 Committer.
>>>>>
>>>>> Megala, Keep up the good work and wish you all the best for your
>>>>> future endeavors!
>>>>>
>>>>> Thanks,
>>>>> Sinthuja.
>>>>>
>>>>> --
>>>>> *Sinthuja Rajendran*
>>>>> Technical Lead
>>>>> WSO2, Inc.:http://wso2.com
>>>>>
>>>>> Blog: http://sinthu-rajan.blogspot.com/
>>>>> Mobile: +94774273955
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Fathima Dilhasha
>>>> *Software Engineer*
>>>> Mobile : +94 (0) 771663314 <%2B94%20%280%29%20773655496>
>>>> <%2B94%20%280%29%20773%20451194>
>>>> dilha...@wso2.com
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Prabushi Samarakoon*
>>> Software Engineer
>>> Mobile: +94715434580
>>> Email: prabus...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> http://wso2.com/signatureYasima Dewmini
> Software Engineer, WSO2, Inc.
> Email: yas...@wso2.com
> Mobile: +94713117081
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Jayawardena
Software Engineer
Tel : 071 350 5470/ 071 885 1183
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Saad Sahibjan

[Menaka Jayawardena]

Congratulations Saad.!

On Mon, Oct 31, 2016 at 6:01 PM, Chathura Dilan <chathu...@wso2.com> wrote:

> ​Hi Devs,
>
> ​It's my pleasure to announce Saad Sahibjan as a WSO2 Committer. Saad has
> been a valuable contributor for WSO2 EMM product, and in recognition of his
> contribution to WSO2, he has been voted as a WSO2 Committer.​
>
> ​Saad, Keep up the good work and wish you all the best for your future
> endeavors!
>
>
> --
> Regards,
>
> Chatura Dilan Perera
> *Associate Tech Lead** - WSO2 Inc.*
> www.dilan.me
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Jayawardena
Software Engineer
Tel : 071 350 5470/ 071 885 1183
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoT] Android sense agent becomes non responsive issue

[Menaka Jayawardena]

Hi Inosh,

Yes it happens when agent could not connect to the host.
Did you check the host url and credentials?

Here you can find the agent code.
https://github.com/wso2-incubator/iot-server-agents/tree/master/wso2_sense_agent

Thanks and Regards
Menaka

On Sun, Feb 28, 2016 at 9:20 AM, Inosh Perera <ino...@wso2.com> wrote:

> Hi all,
>
> [Adding Docs]
> Could you also point me to the Android sense agent source? I could't find
> it in the Docs either[1]. Something similar to EMM docs[2], might need to
> be added in case someone needs to debug the agent/build the agent manually.
>
> [1].
> https://docs.wso2.com/display/IoTS100/Building+WSO2+IoT+Server+from+Source
> [2]. https://docs.wso2.com/display/EMM200/Creating+a+New+Android+APK+File
>
> Regards,
> Inosh
>
> On Sun, Feb 28, 2016 at 8:55 AM, Inosh Perera <ino...@wso2.com> wrote:
>
>> Hi all,
>>
>> I'm trying to enroll the Android sense agent with the IoT  server M3 and
>> I'm getting an Application non responsive(ANR) when I'm trying to enroll by
>> pressing the register button. I downloaded the agent that comes out of the
>> box. In Android this typically happen when a network call or any other
>> operation that takes long time is done on the UI thread. Is this a known
>> issue in the agent?
>>
>> Regards,
>> Inosh
>> --
>> Inosh Perera
>> Software Engineer, WSO2 Inc.
>> Tel: 077813 7285, 0785293686
>>
>
>
>
> --
> Inosh Perera
> Software Engineer, WSO2 Inc.
> Tel: 077813 7285, 0785293686
>



-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Null pointer exception when trying to restart the server - Test Automation

[Menaka Jayawardena]

Thanks a lot Thusitha...
It worked perfectly. :-)

Menaka

On Fri, Feb 26, 2016 at 12:00 PM, Menaka Jayawardena <men...@wso2.com>
wrote:

> Thank you very much Thusitha for the quick reply.
> I'll try it.
>
> On Fri, Feb 26, 2016 at 11:57 AM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Menaka,
>>
>> According to the debug info that you attached, AFAIU this caused because 
>> inputStreamHandler
>> is null and inputStreamHandler.getOutput() throws NPE.
>> I think you can use ServerConfigurationManager instead of CarbonServerManager
>> to do the restart.
>>
>> e.g.
>>
>> ServerConfigurationManager serverConfigManager = new 
>> ServerConfigurationManager(automationContext);
>> serverConfigManager.restartForcefully();
>>
>>
>> Thanks
>> Thsuitha
>>
>> On Fri, Feb 26, 2016 at 11:47 AM, Menaka Jayawardena <men...@wso2.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I tried to restart the server using Automation Framework but it throws
>>> the following exception.
>>>
>>> java.lang.NullPointerException
>>> at
>>> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager.restartGracefully(CarbonServerManager.java:306)
>>> at
>>> org.wso2.carbon.iot.integration.web.ui.test.samples.SampleInstallationTest.serverRestartTest(SampleInstallationTest.java:115)
>>> 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
>>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
>>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
>>> at
>>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>>> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>>> at org.testng.TestRunner.privateRun(TestRunner.java:767)
>>> at org.testng.TestRunner.run(TestRunner.java:617)
>>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>>> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
>>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
>>> at org.testng.TestNG.run(TestNG.java:1031)
>>> at
>>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
>>> at
>>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>>> at
>>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
>>> at
>>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>>> at
>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>>> at
>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
>>>
>>>
>>> I used the following piece of code for restart.
>>>
>>> CarbonServerManager serverManager = new 
>>> CarbonServerManager(automationContext);
>>> try {
>>> serverManager.restartGracefully();
>>> } catch (AutomationFrameworkException e) {
>>> log.error("Restart failed");
>>> }
>>>
>>> When I debug the code, I get null values for all the fields of
>>> serverManager.
>>> I have attached the screenshot here.
>>>
>>> ​
>>> What would be the reason for this?
>>>
>>> Thank you very much
>>> Menaka Madushanka
>>> --
>>> Menaka Madushanka Jayawardena
>>> Software Engineering Intern
>>> men...@wso2.com
>>> Mobile:- +94 71 8851183/ +94 71 3505470
>>> LinkedIn - Menaka Jayawardena
>>> <https://lk.linkedin.com/in/menakajayawardena>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>>
>>
>
>
> --
> Menaka Madushanka Jayawardena
> Software Engineering Intern
> men...@wso2.com
> Mobile:- +94 71 8851183/ +94 71 3505470
> LinkedIn - Menaka Jayawardena
> <https://lk.linkedin.com/in/menakajayawardena>
>



-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Null pointer exception when trying to restart the server - Test Automation

[Menaka Jayawardena]

Thank you very much Thusitha for the quick reply.
I'll try it.

On Fri, Feb 26, 2016 at 11:57 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Menaka,
>
> According to the debug info that you attached, AFAIU this caused because 
> inputStreamHandler
> is null and inputStreamHandler.getOutput() throws NPE.
> I think you can use ServerConfigurationManager instead of CarbonServerManager
> to do the restart.
>
> e.g.
>
> ServerConfigurationManager serverConfigManager = new 
> ServerConfigurationManager(automationContext);
> serverConfigManager.restartForcefully();
>
>
> Thanks
> Thsuitha
>
> On Fri, Feb 26, 2016 at 11:47 AM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hello,
>>
>> I tried to restart the server using Automation Framework but it throws
>> the following exception.
>>
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager.restartGracefully(CarbonServerManager.java:306)
>> at
>> org.wso2.carbon.iot.integration.web.ui.test.samples.SampleInstallationTest.serverRestartTest(SampleInstallationTest.java:115)
>> 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
>> at
>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>> at org.testng.TestRunner.privateRun(TestRunner.java:767)
>> at org.testng.TestRunner.run(TestRunner.java:617)
>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
>> at org.testng.TestNG.run(TestNG.java:1031)
>> at
>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
>> at
>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
>>
>>
>> I used the following piece of code for restart.
>>
>> CarbonServerManager serverManager = new 
>> CarbonServerManager(automationContext);
>> try {
>> serverManager.restartGracefully();
>> } catch (AutomationFrameworkException e) {
>> log.error("Restart failed");
>> }
>>
>> When I debug the code, I get null values for all the fields of
>> serverManager.
>> I have attached the screenshot here.
>>
>> ​
>> What would be the reason for this?
>>
>> Thank you very much
>> Menaka Madushanka
>> --
>> Menaka Madushanka Jayawardena
>> Software Engineering Intern
>> men...@wso2.com
>> Mobile:- +94 71 8851183/ +94 71 3505470
>> LinkedIn - Menaka Jayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Null pointer exception when trying to restart the server - Test Automation

[Menaka Jayawardena]

Hello,

I tried to restart the server using Automation Framework but it throws the
following exception.

java.lang.NullPointerException
at
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager.restartGracefully(CarbonServerManager.java:306)
at
org.wso2.carbon.iot.integration.web.ui.test.samples.SampleInstallationTest.serverRestartTest(SampleInstallationTest.java:115)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
at org.testng.TestNG.run(TestNG.java:1031)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


I used the following piece of code for restart.

CarbonServerManager serverManager = new CarbonServerManager(automationContext);
try {
serverManager.restartGracefully();
} catch (AutomationFrameworkException e) {
log.error("Restart failed");
}

When I debug the code, I get null values for all the fields of
serverManager.
I have attached the screenshot here.

​
What would be the reason for this?

Thank you very much
Menaka Madushanka
-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Kamidu Sachith Punchihewa

[Menaka Jayawardena]

Congratulations Kamidu.!!!

On Wed, Feb 24, 2016 at 11:48 AM, Prabath Abeysekera <praba...@wso2.com>
wrote:

> Hi Everyone,
>
> It's my pleasure to welcome Kamidu Sachith Punchihewa as a WSO2 Committer.
> Kamidu has been a key member of the EMM/IoT team contributing to many
> aspects of product development ever since he joined us. In recognition of
> his contributions, ownership shown towards the tasks/responsibilities
> assigned to him, and commitment, he's been voted as a WSO2 committer.
>
> Kamidu, Welcome aboard and keep up the awesome work!
>
> Cheers,
> Prabath
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Hasunie Adhikari

[Menaka Jayawardena]

Congratulations Hasuni...!!!

On Wed, Feb 24, 2016 at 11:46 AM, Prabath Abeysekera <praba...@wso2.com>
wrote:

> Hi Everyone,
>
> It's my pleasure to welcome Hasunie Adhikari as a WSO2 Committer. Hasunie
> has been a key member of the EMM/IoT team contributing to many aspects of
> product development ever since she joined us. In recognition of her
> contributions, ownership shown towards the tasks/responsibilities assigned
> to her, and commitment, she's been voted as a WSO2 committer.
>
> Hasunie, Welcome aboard and keep up the awesome work!
>
> Cheers,
> Prabath
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Printing ServerLogReader logs when running tests.

[Menaka Jayawardena]

Hello,

When running test cases in IOT server, I get this log.

.
.
.
Feb 23, 2016 5:05:46 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:46,700]  INFO
{org.wso2.carbon.databridge.receiver.binary.internal.BinaryDataReceiver} -
 Started Binary SSL Transport on port : 9711
Feb 23, 2016 5:05:46 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:46,713]  INFO
{org.wso2.carbon.databridge.receiver.binary.internal.BinaryDataReceiver} -
 Started Binary TCP Transport on port : 9611
Feb 23, 2016 5:05:46 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:46,720]  INFO
{org.wso2.carbon.databridge.core.internal.DataBridgeDS} -  Successfully
deployed Agent Server
Feb 23, 2016 5:05:47 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:47,217]  INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Configured
Registry in 283ms
Feb 23, 2016 5:05:47 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:47,888]  INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
 Registry Mode: READ-WRITE
Feb 23, 2016 5:05:51 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:51,112]  INFO
{org.wso2.carbon.metrics.impl.util.JmxReporterBuilder} -  Creating JMX
reporter for Metrics with domain 'org.wso2.carbon.metrics'
Feb 23, 2016 5:05:51 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:51,120]  INFO
{org.wso2.carbon.metrics.impl.util.JDBCReporterBuilder} -  Creating JDBC
reporter for Metrics with source 'menaka-ThinkPad-T530', data source
'jdbc/WSO2MetricsDB' and 60 seconds polling period
Feb 23, 2016 5:05:51 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:51,128]  INFO
{org.wso2.carbon.metrics.impl.reporter.AbstractReporter} -  Started JMX
reporter for Metrics
Feb 23, 2016 5:05:51 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:51,141]  INFO
{org.wso2.carbon.metrics.impl.reporter.AbstractReporter} -  Started JDBC
reporter for Metrics
Feb 23, 2016 5:05:57 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:57,440]  INFO
{org.wso2.carbon.registry.indexing.solr.SolrClient} -  Default Embedded
Solr Server Initialized
Feb 23, 2016 5:05:58 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
INFO: [2016-02-23 17:05:58,999]  INFO
{org.wso2.carbon.social.sql.SocialDBInitilizer} -  Social database already
exists. Not creating a new database.
Feb 23, 2016 5:05:59 PM
org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run
.
.
.
.

Why is it logging,


*org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader run*

every time?

Are there any fixes for this?

Thank you very much
Menaka Madushanka


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2016][CDMF][IOT] IOT SDK for creating device agents.

[Menaka Jayawardena]

Thank you very much Ayyoob for the reply and valuable information.
I'll go through the information.

Thanks and regards
Menaka Madushanka

On Mon, Feb 22, 2016 at 6:09 PM, Ayyoob Hamza <ayy...@wso2.com> wrote:

> Hi Menaka,
> The main idea is to provide SDKs that are catered for different languages,
> which can be used to design a device type agent/firmware to quickly and
> easily connect with IoT Server. This should hide the complexities of
> communicating  authentication, encryption with the IoT Server. This SDK
> should also have the capability to pick the desired transport protocols.
> The expected deliverable are auto-generated code, abstract the protocol
> complexities and should be easily portable for different hardware.
>
> It would be great if you could go through the existing agent code and
> study on how we can improve[1].
>
> [1] https://github.com/wso2/carbon-device-mgt-plugins/tree/IoTS-1.0.0-M4
>
> Thanks,
>
> *Ayyoob Hamza*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>
> On Sun, Feb 21, 2016 at 3:07 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hello,
>>
>> I'm Menaka Madushanka Jayawardena, a Final year undergraduate at Faculty
>> of Engineering, University of Peradeniya. I'm very much interested in doing
>> the above project. I have some experience with WSO2 IOT server and the
>> device types.
>>
>> I'd like to know more information about the project.
>> Also deliverable is not very clear to me, so I prefer some more
>> information about it.
>>
>> Thanks and regards
>> Menaka Madushanka
>> --
>> Menaka Madushanka Jayawardena
>> Software Engineering Intern
>> men...@wso2.com
>> Mobile:- +94 71 8851183/ +94 71 3505470
>> LinkedIn - Menaka Jayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>
>>
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC 2016][CDMF][IOT] IOT SDK for creating device agents.

[Menaka Jayawardena]

Hello,

I'm Menaka Madushanka Jayawardena, a Final year undergraduate at Faculty of
Engineering, University of Peradeniya. I'm very much interested in doing
the above project. I have some experience with WSO2 IOT server and the
device types.

I'd like to know more information about the project.
Also deliverable is not very clear to me, so I prefer some more information
about it.

Thanks and regards
Menaka Madushanka
-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Null pointer exception when running Test cases

[Menaka Jayawardena]

Hello Krishantha,

Here is the url for the repo.

https://github.com/menaka121/product-iot-server/tree/master/modules/integration

Thank you very much

On Wed, Feb 3, 2016 at 2:54 PM, Krishantha Samaraweera <krishan...@wso2.com>
wrote:

> Hi Menaka,
>
> Can you share the repo URL. So I can go though the configurations and see.
>
> Thanks,
> Krishantha.
>
> On Tue, Feb 2, 2016 at 10:47 AM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hello,
>>
>> I get this exception when trying to run tests in IOT server.
>>
>> But all test cases are running without any problem.
>>
>> Feb 02, 2016 10:44:42 AM
>> org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension
>> 
>> WARNING: Failed to initializing the Extension Class
>> Feb 02, 2016 10:44:42 AM
>> org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension
>> 
>> SEVERE: Error initializing the Automation Context
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.automation.engine.extensions.ListenerExtension.setParameterMap(ListenerExtension.java:51)
>> at
>> org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension.(ExecutionListenerExtension.java:31)
>> at
>> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.(CarbonServerExtension.java:29)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>> at java.lang.Class.newInstance(Class.java:383)
>> at
>> org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.initiate(TestNGExtensionExecutor.java:97)
>> at
>> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:46)
>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
>> at org.testng.TestNG.run(TestNG.java:1015)
>> at
>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
>> at
>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
>>
>>
>> I debugged the test platform and the parameter map gets null.
>>
>> What could be the reason for this?
>>
>>
>> Thanks and regards
>> Menaka Madusanka
>>
>> --
>> Menaka Madushanka Jayawardena
>> Software Engineering Intern
>> men...@wso2.com
>> Mobile:- +94 71 8851183/ +94 71 3505470
>> LinkedIn - Menaka Jayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>
>>
>> _______
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>



-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Malith Munasinghe

[Menaka Jayawardena]

Congratulations Malith

On Tue, Feb 2, 2016 at 4:52 PM, Shabir Mohamed <sha...@wso2.com> wrote:

> Congrats Bro :D
>
> -
> *Shabir Mohamed*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> Email: sha...@wso2.com <ayy...@wso2.com>
> Mobile: +94 77 3516019 | +94 71 6583393
>
> On Tue, Feb 2, 2016 at 4:48 PM, Jithendra Sirimanne <jithen...@wso2.com>
> wrote:
>
>> Congrats :)
>>
>> Best Regards
>> Jithendra
>>
>> --
>> Jithendra Sirimanne
>> *Systems Engineer*
>> Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
>> Tel  : +94 112 145 345
>> Email  : jithen...@wso2.com
>>
>> On Tue, Feb 2, 2016 at 4:38 PM, Amila Maha Arachchi <ami...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Its my pleasure to welcome Malith Munasinghe as a WSO2 Committer. Malith
>>> is a member of WSO2 Cloud Dev team and has been contributing to the team in
>>> development, integration, deployment and alerting work. In recognition of
>>> his contribution, he has been voted as a WSO2 Committer.
>>>
>>> Malith, welcome aboard and keep up the good work..
>>>
>>> Regards,
>>> Amila.
>>>
>>> --
>>> *Amila Maharachchi*
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Blog: http://maharachchi.blogspot.com
>>> Mobile: +94719371446
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> _______
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Null pointer exception when running Test cases

[Menaka Jayawardena]

Hello,

I get this exception when trying to run tests in IOT server.

But all test cases are running without any problem.

Feb 02, 2016 10:44:42 AM
org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension

WARNING: Failed to initializing the Extension Class
Feb 02, 2016 10:44:42 AM
org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension

SEVERE: Error initializing the Automation Context
java.lang.NullPointerException
at
org.wso2.carbon.automation.engine.extensions.ListenerExtension.setParameterMap(ListenerExtension.java:51)
at
org.wso2.carbon.automation.engine.extensions.ExecutionListenerExtension.(ExecutionListenerExtension.java:31)
at
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.(CarbonServerExtension.java:29)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:383)
at
org.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.initiate(TestNGExtensionExecutor.java:97)
at
org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:46)
at org.testng.TestNG.runExecutionListeners(TestNG.java:1068)
at org.testng.TestNG.run(TestNG.java:1015)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


I debugged the test platform and the parameter map gets null.

What could be the reason for this?


Thanks and regards
Menaka Madusanka

-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Isuru Wijesinghe

[Menaka Jayawardena]

Congratulations Isuru


On Thu, Jan 14, 2016 at 1:19 PM, Samitha Chathuranga <sami...@wso2.com>
wrote:

> Congrats Isuru..!
>
> On Thu, Jan 14, 2016 at 12:16 PM, Heshitha Hettihewa <heshit...@wso2.com>
> wrote:
>
>> Congrats Isuru..!!!
>>
>> On Thu, Jan 14, 2016 at 11:53 AM, Nandika Jayawardana <nand...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce Isuru Wijesinghe as a WSO2 Committer. He
>>> has been a key contributor to the WSO2 Business Process Server and WSO2
>>> Process Center Products and in recognition of his work, he had been voted
>>> as a WSO2 Committer.
>>>
>>> Congratulations Isuru 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
>>>
>>>
>>
>>
>> --
>> Heshitha Hettihewa
>> *Software Engineer*
>> Mobile : +94716866386
>> <%2B94%20%280%29%20773%20451194>
>> heshit...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Samitha Chathuranga
> Software Engineer, WSO2 Inc.
> lean.enterprise.middleware
> Mobile: +94715123761
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Fazlan Nazeem

[Menaka Jayawardena]

Congratulations Fazlan.

On Tue, Jan 12, 2016 at 8:59 PM, NIFRAS ISMAIL <nifrasism...@gmail.com>
wrote:

> Great Keep up Fazlan!
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn] <http://lk.linkedin.com/pub/nifras-ismail/54/343/94b>
>
>
>
> On Tue, Jan 12, 2016 at 7:10 PM, Mohamed ZAJITH <mohamedzaj...@gmail.com>
> wrote:
>
>> Congratulations Fazlan.  
>> On Jan 12, 2016 6:28 PM, "Nipuna Chandradasa" <nipu...@wso2.com> wrote:
>>
>>> Congratulations Fazlan .. :D
>>>
>>> On Tue, Jan 12, 2016 at 4:58 PM, Ashen Weerathunga <as...@wso2.com>
>>> wrote:
>>>
>>>> Congratulations Fazlan!!! :)
>>>>
>>>> On Tue, Jan 12, 2016 at 4:47 PM, Malintha Adikari <malin...@wso2.com>
>>>> wrote:
>>>>
>>>>> Congratulations..!!!
>>>>>
>>>>> On Tue, Jan 12, 2016 at 4:36 PM, Nirmal Fernando <nir...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> It's my pleasure to announce *Fazlan Nazeem* as a *WSO2 Committer*.
>>>>>> He has been a key contributor to the *WSO2 Machine Learner *Product
>>>>>> and in recognition of his work, he had been voted as a WSO2 Committer
>>>>>> .
>>>>>>
>>>>>> Congratulations Fazlan 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Malintha Adikari*
>>>>> Software Engineer
>>>>> WSO2 Inc.; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> Mobile: +94 71 2312958
>>>>> Blog:http://malinthas.blogspot.com
>>>>> Page:   http://about.me/malintha
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Ashen Weerathunga*
>>>> Software Engineer - Intern
>>>> WSO2 Inc.: http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> Email: as...@wso2.com
>>>> Mobile: +94 716042995 <94716042995>
>>>> LinkedIn:
>>>> *http://lk.linkedin.com/in/ashenweerathunga
>>>> <http://lk.linkedin.com/in/ashenweerathunga>*
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Nipuna Marcus
>>> *Software Engineer*
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>> Mobile : +94 (0) 713 667906
>>> nipu...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Communicating between two services

[Menaka Jayawardena]

Hello,

I'm creating an Android application which reads the sensor data and publish
them to the IOT server.

Here I need to display the sensor data in my Activity.
The sensor reading is done separately in a service.

My code files are attached herewith.

When I run the application it gives the following exception.


11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: FATAL EXCEPTION: main
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: Process: iot.carbon.wso2.org.androidsenseanget, PID: 5484
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast
Intent {
act=iot.carbon.wso2.org.androidsenseagent.util.SensorsDrawerActivity.displayData
flg=0x10 (has extras) } in
iot.carbon.wso2.org.androidsenseagent.util.SensorsDrawerActivity$2@772125a
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:882)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at android.os.Looper.loop(Looper.java:211)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
android.app.ActivityThread.main(ActivityThread.java:5373)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1020)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:815)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime:  Caused by: java.lang.NullPointerException: println needs
a message
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at android.util.Log.println_native(Native Method)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at android.util.Log.d(Log.java:139)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
iot.carbon.wso2.org.androidsenseagent.util.SensorsDrawerActivity.updateUI(SensorsDrawerActivity.java:264)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
iot.carbon.wso2.org.androidsenseagent.util.SensorsDrawerActivity$2.onReceive(SensorsDrawerActivity.java:258)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:872)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
android.os.Handler.handleCallback(Handler.java:739)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
android.os.Handler.dispatchMessage(Handler.java:95)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at android.os.Looper.loop(Looper.java:211)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
android.app.ActivityThread.main(ActivityThread.java:5373)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1020)

11-17 19:54:42.842 5484-5484/iot.carbon.wso2.org.androidsenseanget
E/AndroidRuntime: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:815)


Some one could help me to figure out what the problem is.

Thank you
Best Regards
Menaka Madushanka

-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
package iot.carbon.wso2.org.androidsenseagent.service;

import android.app.Service;
import android.content.Intent;
import android.content.IntentFilter;
import android.nfc.Tag;
import android.os.Handler;
import android.os.IBinder;
import android.support.annotation.Nullable;
import android.util.Log;

Re: [Dev] Product IOT server build failed

[Menaka Jayawardena]

Hi Prabath,

Thank you very much.
I'll check it.

Best Regards
Menaka

On Thu, Nov 5, 2015 at 7:58 AM, Prabath Abeysekera <praba...@wso2.com>
wrote:

> Hi Menaka,
>
> I'm seeing quite a few maven warnings printed as part of the above shared
> exception trace. Please fix those as well.
>
> Cheers,
> Prabath
>
> On Tue, Nov 3, 2015 at 12:51 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Build successful and server is running properly.
>>
>> Thank you very much :-)
>>
>> On Tue, Nov 3, 2015 at 12:13 PM, Rasika Perera <rasi...@wso2.com> wrote:
>>
>>> This is fixed now.
>>>
>>> On Tue, Nov 3, 2015 at 12:01 AM, Menaka Jayawardena <men...@wso2.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I built the given repositories in order with mvn clean install. All of
>>>> those build successfully except the IOT server. [1]
>>>>
>>>> [1]  https://github.com/wso2-incubator/product-iot-server
>>>>
>>>> This is the full stack trace.
>>>>
>>>> menaka@menaka-ThinkPad-T530:~/Documents/WSO2/product-iot-server$ mvn
>>>> clean install -e
>>>> [INFO] Error stacktraces are turned on.
>>>> [INFO] Scanning for projects...
>>>> [ERROR] The build could not read 1 project -> [Help 1]
>>>> org.apache.maven.project.ProjectBuildingException: Some problems were
>>>> encountered while processing the POMs:
>>>> [FATAL] Non-resolvable parent POM: Could not find artifact
>>>> org.wso2.iot:wso2iot-parent:pom:1.0.0-SNAPSHOT and 'parent.relativePath'
>>>> points at wrong local POM @ line 24, column 10
>>>> [WARNING]
>>>> 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
>>>> must be unique:
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.core:jar -> duplicate
>>>> declaration of version ${carbon.device.mgt.version} @
>>>> org.wso2.iot:wso2iot-parent:1.0.0-SNAPSHOT,
>>>> /home/menaka/Documents/WSO2/product-iot-server/pom.xml, line 415, column 25
>>>> [WARNING]
>>>> 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
>>>> must be unique:
>>>> org.wso2.carbon.devicemgt:org.wso2.carbon.policy.mgt.common:jar ->
>>>> duplicate declaration of version ${carbon.device.mgt.version} @
>>>> org.wso2.iot:wso2iot-parent:1.0.0-SNAPSHOT,
>>>> /home/menaka/Documents/WSO2/product-iot-server/pom.xml, line 420, column 25
>>>> [WARNING] 'version' contains an expression but should be a constant. @
>>>> org.wso2.carbon.device.mgt.iot.server.sample:org.wso2.carbon.device.mgt.iot.sample.firealarm.plugin.impl:${carbon.iot.device.mgt.version},
>>>> /home/menaka/Documents/WSO2/product-iot-server/modules/samples/firealarm/src/org.wso2.carbon.device.mgt.iot.sample.firealarm.plugin.impl/pom.xml,
>>>> line 24, column 11
>>>> [WARNING] 'version' contains an expression but should be a constant. @
>>>> org.wso2.carbon.device.mgt.iot.server.sample:org.wso2.carbon.device.mgt.iot.sample.firealarm:${carbon.iot.device.mgt.version},
>>>> /home/menaka/Documents/WSO2/product-iot-server/modules/samples/firealarm/src/pom.xml,
>>>> line 13, column 11
>>>> [WARNING] 'version' contains an expression but should be a constant. @
>>>> org.wso2.carbon.device.mgt.iot.server.sample:org.wso2.carbon.device.mgt.iot.sample.firealarm.service.impl:${carbon.iot.device.mgt.version},
>>>> /home/menaka/Documents/WSO2/product-iot-server/modules/samples/firealarm/src/org.wso2.carbon.device.mgt.iot.sample.firealarm.service.impl/pom.xml,
>>>> line 14, column 14
>>>> [WARNING] 'version' contains an expression but should be a constant. @
>>>> org.wso2.carbon.device.mgt.iot.server.sample:org.wso2.carbon.device.mgt.iot.sample.firealarm:${carbon.iot.device.mgt.version},
>>>> /home/menaka/Documents/WSO2/product-iot-server/modules/samples/firealarm/src/pom.xml,
>>>> line 13, column 11
>>>> [WARNING] 'version' contains an expression but should be a constant. @
>>>> org.wso2.carbon.device.mgt.iot.server.sample:iot-server-samples:${carbon.iot.device.mgt.version},
>>>> /home/menaka/Documents/WSO2/product-iot-server/modules/samples/pom.xml,
>>>> line 27, column 14
>>>> [WARNING] 'version' contains an expression but should be a constant. @
>>>> org.wso2.carbon.device.mgt.iot.server.sample:org.wso2.carbon.device.mgt.iot.sample.android.sense.plugin.impl:${carb

Re: [Dev] IOT-Server does not start-up correctly

[Menaka Jayawardena]

Thank you Ayyoob...!!!

On Wed, Nov 4, 2015 at 5:01 PM, Ayyoob Hamza <ayy...@wso2.com> wrote:

> Hi Menaka,
> Have raised this issue while back on https://wso2.org/jira/browse/CEP-1375.
> Will send a pull request to merge the changes.
>
> Thanks
> Ayyoob
>
> *Ayyoob Hamza*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>
> On Wed, Nov 4, 2015 at 2:57 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Thank you Charitha
>>
>>
>>
>> On Wed, Nov 4, 2015 at 2:54 PM, Charitha Goonetilleke <charit...@wso2.com
>> > wrote:
>>
>>> Hi Menaka,
>>>
>>> I found that, there are two versions of axis2 bundles available in the
>>> pack and seems they are conflicting with each other. So need to figure out
>>> what are the components that exporting those two different versions. I'll
>>> fix them and update the thread.
>>>
>>>
>>> Thanks & regards,
>>> /charithag
>>>
>>> On Wed, Nov 4, 2015 at 2:48 PM, Menaka Jayawardena <men...@wso2.com>
>>> wrote:
>>>
>>>> Thank you very much Aruna.
>>>>
>>>> I'll try it.
>>>>
>>>> On Wed, Nov 4, 2015 at 2:27 PM, Aruna Karunarathna <ar...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Nov 4, 2015 at 2:21 PM, Menaka Jayawardena <men...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I cloned the repositories for the iot-server project and built it.
>>>>>>
>>>>>> Build order:
>>>>>>
>>>>>> 1. https://github.com/ayyoob/carbon-identity (git checkout master)
>>>>>>
>>>>>> 2. https://github.com/ruwany/carbon-apimgt (git checkout
>>>>>> release-1.10.x)
>>>>>>
>>>>>> 3. https://github.com/ayyoob/carbon-store (git checkout build-pack)
>>>>>>
>>>>>> 4. https://github.com/ayyoob/carbon-device-mgt (git checkout
>>>>>> build-pack)
>>>>>>
>>>>>> 5. https://github.com/wso2-incubator/iot-server-extensions (git
>>>>>> checkout wso2con-sf)
>>>>>>
>>>>>> 6. https://github.com/ayyoob/carbon-event-processing (git checkout
>>>>>> buildpack4)
>>>>>>
>>>>>> 7.  https://github.com/wso2-incubator/product-iot-server (git
>>>>>> checkout master)
>>>>>>
>>>>>> Building was completed successfully.
>>>>>>
>>>>>> But when starting the iot-server, it starts-up and keep giving the
>>>>>> following message.
>>>>>>
>>>>>> [2015-11-04 14:07:13,794]  WARN
>>>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization 
>>>>>> is
>>>>>> delayed due to the following unsatisfied items:
>>>>>> [2015-11-04 14:07:13,795]  WARN
>>>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for
>>>>>> required OSGiAxis2Service: org.wso2.carbon.event.processor.admin-2.0.9
>>>>>>
>>>>>> What would be the solution for this issue?
>>>>>>
>>>>>
>>>>> Not sure about the repos and the order of the repos you have built.
>>>>> Seems like some required services are not present. You can get more
>>>>> insight running the server with -DosgiConsole and do some osgi service
>>>>> level debugging.
>>>>>
>>>>>>
>>>>>> Thank you very much.
>>>>>> Best Redards
>>>>>>
>>>>>> Menaka Madushanka
>>>>>>
>>>>>> --
>>>>>> Menaka Madushanka Jayawardena
>>>>>> Software Engineering Intern
>>>>>> men...@wso2.com
>>>>>> Mobile:- +94 71 8851183/ +94 71 3505470
>>>>>> LinkedIn - Menaka Jayawardena
>>>>>> <https://lk.linkedin.com/in/menakajayawardena>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>

Re: [Dev] IOT-Server does not start-up correctly

[Menaka Jayawardena]

Problem solved :-)

On Wed, Nov 4, 2015 at 5:05 PM, Menaka Jayawardena <men...@wso2.com> wrote:

> Thank you Ayyoob...!!!
>
> On Wed, Nov 4, 2015 at 5:01 PM, Ayyoob Hamza <ayy...@wso2.com> wrote:
>
>> Hi Menaka,
>> Have raised this issue while back on
>> https://wso2.org/jira/browse/CEP-1375. Will send a pull request to merge
>> the changes.
>>
>> Thanks
>> Ayyoob
>>
>> *Ayyoob Hamza*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>>
>> On Wed, Nov 4, 2015 at 2:57 PM, Menaka Jayawardena <men...@wso2.com>
>> wrote:
>>
>>> Thank you Charitha
>>>
>>>
>>>
>>> On Wed, Nov 4, 2015 at 2:54 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
>>>> Hi Menaka,
>>>>
>>>> I found that, there are two versions of axis2 bundles available in the
>>>> pack and seems they are conflicting with each other. So need to figure out
>>>> what are the components that exporting those two different versions. I'll
>>>> fix them and update the thread.
>>>>
>>>>
>>>> Thanks & regards,
>>>> /charithag
>>>>
>>>> On Wed, Nov 4, 2015 at 2:48 PM, Menaka Jayawardena <men...@wso2.com>
>>>> wrote:
>>>>
>>>>> Thank you very much Aruna.
>>>>>
>>>>> I'll try it.
>>>>>
>>>>> On Wed, Nov 4, 2015 at 2:27 PM, Aruna Karunarathna <ar...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Nov 4, 2015 at 2:21 PM, Menaka Jayawardena <men...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I cloned the repositories for the iot-server project and built it.
>>>>>>>
>>>>>>> Build order:
>>>>>>>
>>>>>>> 1. https://github.com/ayyoob/carbon-identity (git checkout master)
>>>>>>>
>>>>>>> 2. https://github.com/ruwany/carbon-apimgt (git checkout
>>>>>>> release-1.10.x)
>>>>>>>
>>>>>>> 3. https://github.com/ayyoob/carbon-store (git checkout build-pack)
>>>>>>>
>>>>>>> 4. https://github.com/ayyoob/carbon-device-mgt (git checkout
>>>>>>> build-pack)
>>>>>>>
>>>>>>> 5. https://github.com/wso2-incubator/iot-server-extensions (git
>>>>>>> checkout wso2con-sf)
>>>>>>>
>>>>>>> 6. https://github.com/ayyoob/carbon-event-processing (git checkout
>>>>>>> buildpack4)
>>>>>>>
>>>>>>> 7.  https://github.com/wso2-incubator/product-iot-server (git
>>>>>>> checkout master)
>>>>>>>
>>>>>>> Building was completed successfully.
>>>>>>>
>>>>>>> But when starting the iot-server, it starts-up and keep giving the
>>>>>>> following message.
>>>>>>>
>>>>>>> [2015-11-04 14:07:13,794]  WARN
>>>>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon 
>>>>>>> initialization is
>>>>>>> delayed due to the following unsatisfied items:
>>>>>>> [2015-11-04 14:07:13,795]  WARN
>>>>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for
>>>>>>> required OSGiAxis2Service:
>>>>>>> org.wso2.carbon.event.processor.admin-2.0.9
>>>>>>>
>>>>>>> What would be the solution for this issue?
>>>>>>>
>>>>>>
>>>>>> Not sure about the repos and the order of the repos you have built.
>>>>>> Seems like some required services are not present. You can get more
>>>>>> insight running the server with -DosgiConsole and do some osgi service
>>>>>> level debugging.
>>>>>>
>>>>>>>
>>>>>>> Thank you very much.
>>>>>>> Best Redards
>>>>>>>
>>>>>>> Menaka Madushanka
>>>>>>>
>>>>>>> --
>>>>>>> Menaka Madushanka Jayaw

Re: [Dev] IOT-Server does not start-up correctly

[Menaka Jayawardena]

Thank you very much Aruna.

I'll try it.

On Wed, Nov 4, 2015 at 2:27 PM, Aruna Karunarathna <ar...@wso2.com> wrote:

>
>
> On Wed, Nov 4, 2015 at 2:21 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Hello,
>>
>> I cloned the repositories for the iot-server project and built it.
>>
>> Build order:
>>
>> 1. https://github.com/ayyoob/carbon-identity (git checkout master)
>>
>> 2. https://github.com/ruwany/carbon-apimgt (git checkout release-1.10.x)
>>
>> 3. https://github.com/ayyoob/carbon-store (git checkout build-pack)
>>
>> 4. https://github.com/ayyoob/carbon-device-mgt (git checkout build-pack)
>>
>> 5. https://github.com/wso2-incubator/iot-server-extensions (git checkout
>> wso2con-sf)
>>
>> 6. https://github.com/ayyoob/carbon-event-processing (git checkout
>> buildpack4)
>>
>> 7.  https://github.com/wso2-incubator/product-iot-server (git checkout
>> master)
>>
>> Building was completed successfully.
>>
>> But when starting the iot-server, it starts-up and keep giving the
>> following message.
>>
>> [2015-11-04 14:07:13,794]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
>> delayed due to the following unsatisfied items:
>> [2015-11-04 14:07:13,795]  WARN
>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for
>> required OSGiAxis2Service: org.wso2.carbon.event.processor.admin-2.0.9
>>
>> What would be the solution for this issue?
>>
>
> Not sure about the repos and the order of the repos you have built.
> Seems like some required services are not present. You can get more
> insight running the server with -DosgiConsole and do some osgi service
> level debugging.
>
>>
>> Thank you very much.
>> Best Redards
>>
>> Menaka Madushanka
>>
>> --
>> Menaka Madushanka Jayawardena
>> Software Engineering Intern
>> men...@wso2.com
>> Mobile:- +94 71 8851183/ +94 71 3505470
>> LinkedIn - Menaka Jayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IOT-Server does not start-up correctly

[Menaka Jayawardena]

Thank you Charitha



On Wed, Nov 4, 2015 at 2:54 PM, Charitha Goonetilleke <charit...@wso2.com>
wrote:

> Hi Menaka,
>
> I found that, there are two versions of axis2 bundles available in the
> pack and seems they are conflicting with each other. So need to figure out
> what are the components that exporting those two different versions. I'll
> fix them and update the thread.
>
>
> Thanks & regards,
> /charithag
>
> On Wed, Nov 4, 2015 at 2:48 PM, Menaka Jayawardena <men...@wso2.com>
> wrote:
>
>> Thank you very much Aruna.
>>
>> I'll try it.
>>
>> On Wed, Nov 4, 2015 at 2:27 PM, Aruna Karunarathna <ar...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 4, 2015 at 2:21 PM, Menaka Jayawardena <men...@wso2.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I cloned the repositories for the iot-server project and built it.
>>>>
>>>> Build order:
>>>>
>>>> 1. https://github.com/ayyoob/carbon-identity (git checkout master)
>>>>
>>>> 2. https://github.com/ruwany/carbon-apimgt (git checkout
>>>> release-1.10.x)
>>>>
>>>> 3. https://github.com/ayyoob/carbon-store (git checkout build-pack)
>>>>
>>>> 4. https://github.com/ayyoob/carbon-device-mgt (git checkout
>>>> build-pack)
>>>>
>>>> 5. https://github.com/wso2-incubator/iot-server-extensions (git
>>>> checkout wso2con-sf)
>>>>
>>>> 6. https://github.com/ayyoob/carbon-event-processing (git checkout
>>>> buildpack4)
>>>>
>>>> 7.  https://github.com/wso2-incubator/product-iot-server (git checkout
>>>> master)
>>>>
>>>> Building was completed successfully.
>>>>
>>>> But when starting the iot-server, it starts-up and keep giving the
>>>> following message.
>>>>
>>>> [2015-11-04 14:07:13,794]  WARN
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
>>>> delayed due to the following unsatisfied items:
>>>> [2015-11-04 14:07:13,795]  WARN
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for
>>>> required OSGiAxis2Service: org.wso2.carbon.event.processor.admin-2.0.9
>>>>
>>>> What would be the solution for this issue?
>>>>
>>>
>>> Not sure about the repos and the order of the repos you have built.
>>> Seems like some required services are not present. You can get more
>>> insight running the server with -DosgiConsole and do some osgi service
>>> level debugging.
>>>
>>>>
>>>> Thank you very much.
>>>> Best Redards
>>>>
>>>> Menaka Madushanka
>>>>
>>>> --
>>>> Menaka Madushanka Jayawardena
>>>> Software Engineering Intern
>>>> men...@wso2.com
>>>> Mobile:- +94 71 8851183/ +94 71 3505470
>>>> LinkedIn - Menaka Jayawardena
>>>> <https://lk.linkedin.com/in/menakajayawardena>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>
>>
>>
>> --
>> Menaka Madushanka Jayawardena
>> Software Engineering Intern
>> men...@wso2.com
>> Mobile:- +94 71 8851183/ +94 71 3505470
>> LinkedIn - Menaka Jayawardena
>> <https://lk.linkedin.com/in/menakajayawardena>
>>
>
>
>
> --
> *Charitha Goonetilleke*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 751 3669 <%2B94777513669>
> Twitter:@CharithaWs <https://twitter.com/CharithaWs>, fb: charithag
> <https://www.facebook.com/charithag>, linkedin: charithag
> <http://www.linkedin.com/in/charithag>
>



-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] IOT-Server does not start-up correctly

[Menaka Jayawardena]

Hello,

I cloned the repositories for the iot-server project and built it.

Build order:

1. https://github.com/ayyoob/carbon-identity (git checkout master)

2. https://github.com/ruwany/carbon-apimgt (git checkout release-1.10.x)

3. https://github.com/ayyoob/carbon-store (git checkout build-pack)

4. https://github.com/ayyoob/carbon-device-mgt (git checkout build-pack)

5. https://github.com/wso2-incubator/iot-server-extensions (git checkout
wso2con-sf)

6. https://github.com/ayyoob/carbon-event-processing (git checkout
buildpack4)

7.  https://github.com/wso2-incubator/product-iot-server (git checkout
master)

Building was completed successfully.

But when starting the iot-server, it starts-up and keep giving the
following message.

[2015-11-04 14:07:13,794]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
delayed due to the following unsatisfied items:
[2015-11-04 14:07:13,795]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for
required OSGiAxis2Service: org.wso2.carbon.event.processor.admin-2.0.9

What would be the solution for this issue?

Thank you very much.
Best Redards

Menaka Madushanka

-- 
Menaka Madushanka Jayawardena
Software Engineering Intern
men...@wso2.com
Mobile:- +94 71 8851183/ +94 71 3505470
LinkedIn - Menaka Jayawardena <https://lk.linkedin.com/in/menakajayawardena>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev