Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hello Kasun,

Currently the OOM scenario is mapped to "OOM" event in the  ESB flight
recorder. And CPU Spinning is mapped to "High CPU Usage" event in the tool.
The requested resources for those events can be configured by the user of
ESB Flight Recorder.

Thanks,
Dinanjana.

On Tue, Aug 23, 2016 at 11:32 PM, Kasun Indrasiri  wrote:

> Thanks, Dinanjana. I think it's good to have how different scenarios can
> be handled from ESB flight recorder information.
> - OOM
> - CPU spinning
> - Deadlock
> etc.
>
> Thanks,
> Kasun.
>
> On Mon, Aug 22, 2016 at 11:02 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi all,
>> Currently the tool supports generating jfr along with thread dumps and
>> heap dumps. And the report template has been changed so that it reflects a
>> lot more details on environmental details during an event. All collectibles
>> along with thread dumps and jfrs will be bundled in to a zip archive now.
>> This zip archive will be generated for each "event". This contains the
>> report, thread dumps(if user requested) & jfr (if user requested). Report
>> is a HTML file. Thread dumps are also viewable through this report.User can
>> change the template as he wish by changing the report template HTML file
>>
>> On Tue, Aug 23, 2016 at 11:28 AM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Dear all,
>>> This[1]
>>> 
>>>  is
>>> the blog post I made for final work product submission. Please have a look.
>>> :)
>>> [1]http://dinanjanagunaratne.blogspot.com/2016/08/during-pas
>>> t-3-months-i-was-engaged-in.html
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Director, Integration Technologies
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +1 650 450 2293
> Blog : http://kasunpanorama.blogspot.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Problem with integrating Event Stream OSGi Service

[Mohanadarshan Vivekanandalingam]

HI Malintha/Nuwan,

I have few queries and like to provide few clarifications on this..

Actually most of the points that you guys raised are discussed before and
changed based on some experiences..

- Defining stream from client side  : We had this in old datapublisher
component and removed due to various complications.. As Srinath mentioned
this was done after many rounds of discussions..

- Having single configuration file to add DAS endpoint : In past, we had
two level of configs (one for adapter which deals with transport and one
for event formatting which deals with stream). That means we can use one
event adapter for multiple streams.. But, there were some complaints saying
it is not user friendly and should have one config to publish events..

And also, event publisher is also another deployable artifact like other
synapse files.. In APIM, we are configuring key manager url in multiple api
configs (revoke api and etc.. ), event publisher is also similar to that..

But, I do understand that your points are valid and think we have two
options..

- Have a global property in output-adapter-config.xml and use that in
Thrift event publisher (if that property exists)..
- Allow to keep the DAS endpoint as a registry resource and use that..

Thanks,
Mohan


On Wed, Aug 24, 2016 at 10:05 AM, Nuwan Dias  wrote:

> Hi,
>
> I spoke with Srinath regarding this too. It would be ideal to have a
> global config which can override the per-stream configs so that we won't
> have to maintain the DAS configs in multiple places. In all cases we've
> come across so far we've only seen people use a single DAS (or cluster) and
> publish all streams to that DAS cluster. So at least as of now I don't see
> much value in having per stream config files.
>
> It would also be good if we can omit the necessity of having to define the
> streams on the client side (because they're already defined on the server).
> I see two main problems of having to define them on the clients.
>
> 1. When we have multiple event generators (a gateway cluster), the streams
> will have to be defined on all nodes. Do we use dep-sync to sync up the
> configs on the clients? Even if we do, I think its better to not depend on
> dep-sync for the new stuff we're developing because we're moving away from
> dep-sync soon.
>
> 2. Problems in upgrading to newer product versions. When upgrading the
> product version, if a schema change has occurred, currently we only have to
> worry about changing the schema on the server side. With the above
> limitation, we now have to worry about changing the clients too.
>
> Thanks,
> NuwanD.
>
> On Tue, Aug 23, 2016 at 10:16 PM, Malintha Amarasinghe  > wrote:
>
>> Hi All,
>>
>> Currently APIM is using an internal APIM specific configuration resides
>> in api-manager.xml which include DAS server URL, username, password etc.
>> Those configuration are used to instantiate an org.wso2.carbon.databridge.
>> agent.DataPublisher object, which is then used to publish events
>> directly to streams in DAS.
>>
>> As it is an APIM specific configuration, it is not reusable by other
>> non-APIM features. Also org.wso2.carbon.databridge.agent.DataPublisher is
>> intended to be used in non-carbon environments, for carbon environments,
>> the recommended way is to use the Event Stream OSGi Service.
>>
>> So we were trying to re-structure APIM data publishing code to use new
>> Event Stream OSGi service explained in [1].
>>
>> 1. Create all the streams defined in DAS in APIM.
>> 2. Create an *event publisher per each stream *which takes data from the
>> stream and publish to DAS.
>> 3. In each event publisher we need to configure DAS specific
>> configuration.
>>
>> Ex:
>> 
>> http://wso2.org/carbon/eventpublisher;>
>>   
>>   
>>   
>> admin
>> thrift
>> non-blocking
>> 0
>> tcp://localhost:7611
>> 
>>   
>> 
>>
>> But we are facing a small problem here; in APIM there are many event
>> streams being used. If there's a change happen to DAS configuration, we
>> need to change it in all the event publishers which makes it difficult to
>> maintain. As per the offline chat with DAS team, this is a current
>> limitation.
>>
>> Are we going to move forward with the existing implementation?
>>
>> Thanks,
>> Malintha
>>
>> [1] [Dev] Common configuration for publishing events from carbon servers
>> to DAS/CEP
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*V. Mohanadarshan*
*Associate Tech Lead,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: 

Re: [Dev] How to get the page title of a dashboard page

[Kalpa Welivitigoda]

Hi Lasantha,

On Mon, Aug 22, 2016 at 5:09 PM, Lasantha Samarakoon 
wrote:

> Hi Kalpa,
>
> As  it seems, the best way to proceed with your requirement is introducing
> a meta data API. It is not a good practice access parent window within a
> gadget as it may cause cross domain issues.
>
> WRT to pages with multiple words page titles, did you try fetching the
> page title from the parents respective DOM element, instead of the URL? If
> we can get that from the DOM, spaces won't be an issue anymore.
>
>
Thanks for the suggestion. I could do so by accessing the active element in
the ues-pages list. I will fix it properly once the meta data API is
available.


>
> Regards,
>
> *Lasantha Samarakoon* | Software Engineer
> WSO2, Inc.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 (71) 214 1576
> Email:  lasant...@wso2.com
> Web:www.wso2.com
>
> lean . enterprise . middleware
>
> On Mon, Aug 22, 2016 at 12:42 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi Lasantha,
>>
>> I have a breadcrumb (this is a separate gadget) in the dashboard in which
>> I display the navigation and the webapp filtering. Please refer the screen
>> capture attached herewith. There, 'browser' is the page and 'examples' is
>> the webapp name. When a user clickes 'browser', the page (other gadgets)
>> updates to fetch and show statistics related to all webapps.
>>
>> How 'browser' is fetched at the moment is via the dashboard URL, we do a
>> parent.window.location.href and get the page URL. This is also not good
>> since we are using parent inside a gadget. May be we can consider adding
>> page URL as well for the meta data in the API.
>>
>> The breadcrumb in the screen capture looks nice since it only has one
>> word for the page title/URL. When we have pages like 'HTTP Status Code'
>> with multiple words, it looks ugly since we cannot have spaces in the URL.
>>
>> On Mon, Aug 22, 2016 at 12:22 PM, Lasantha Samarakoon > > wrote:
>>
>>> @Kalpa, Can you please explain the use case of having the page title in
>>> a gadget?
>>>
>>>
>>> Regards,
>>>
>>> *Lasantha Samarakoon* | Software Engineer
>>> WSO2, Inc.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 (71) 214 1576
>>> Email:  lasant...@wso2.com
>>> Web:www.wso2.com
>>>
>>> lean . enterprise . middleware
>>>
>>> On Mon, Aug 22, 2016 at 12:07 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi Kalpa,

 I have created jira for this issue [1]. We will implement an api to get
 dashboard-meta data information in the next release. So you can get
 relevant meta data information of the dashboard using the api.

 [1] - https://wso2.org/jira/browse/UES-1036

 Thanks,
 Nisala

 On Mon, Aug 22, 2016 at 12:03 PM, Nipuna Chandradasa 
 wrote:

> Hi Kalpa,
>
> We currently have a API to send dashboard name and id. But we don't
> have a api to get the page details. But we will create a jira for this and
> add this as an improvement on next release.
>
> Thank you,
>
> On Mon, Aug 22, 2016 at 11:29 AM, Kalpa Welivitigoda 
> wrote:
>
>> Hi devs,
>>
>> I have a dashboard with multiple pages. From a gadget in a page, I
>> need to get the current page title. What would be the recommended 
>> approach
>> to do this?
>>
>>
>>
>> --
>> Best Regards,
>>
>> Kalpa Welivitigoda
>> Senior Software Engineer, WSO2 Inc. http://wso2.com
>> Email: kal...@wso2.com
>> Mobile: +94776509215
>>
>> [image: http://wso2.com/signature] 
>>
>> ___
>> 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
>
>


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


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Best Regards,
>>
>> Kalpa Welivitigoda
>> Senior Software Engineer, WSO2 Inc. http://wso2.com
>> Email: kal...@wso2.com
>> Mobile: +94776509215
>>
>> [image: http://wso2.com/signature] 
>>
>
>


-- 
Best Regards,

Kalpa Welivitigoda
Senior Software Engineer, WSO2 Inc. 

Re: [Dev] Possible bottleneck in the updatePermissionTree() method of user.core.authorization.PermissionTree class

[Chalitha Kulathunga]

Hi Jayanga,

I will send a PR.

Thanks,
Chalitha

On Tue, Aug 23, 2016 at 4:15 PM, Jayanga Kaushalya 
wrote:

> Hi Chalitha,
>
> Thanks for checking up on this. It's great if you can send a PR for
> carbon-kernel 4.4.x branch on this.
>
> Thanks!
>
> *Jayanga Kaushalya*
> Software Engineer
> Mobile: +94777860160
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
> On Fri, Jun 24, 2016 at 2:00 PM, Chalitha Kulathunga 
> wrote:
>
>> + IS team members
>>
>> On Fri, Jun 24, 2016 at 1:37 PM, Chalitha Kulathunga 
>> wrote:
>>
>>> Hi kernal team,
>>>
>>> When multiple threads access updatePermissionTree() method for the first
>>> time, they all will end up in the else block. Those threads will call the
>>> updatePermissionTreeFromDB() method one by one. Seems like this is creating
>>> a bottleneck in the execution flow.
>>>
>>> void updatePermissionTree() throws UserStoreException {
>>> PermissionTreeCacheKey cacheKey = new 
>>> PermissionTreeCacheKey(cacheIdentifier, tenantId);
>>> GhostResource cacheEntry = (GhostResource) 
>>> permissionCache.get(cacheKey);
>>> if (permissionCache.containsKey(cacheKey)) {
>>> if (cacheEntry.getResource() == null) {
>>> synchronized (this) {
>>> cacheEntry = (GhostResource) 
>>> permissionCache.get(cacheKey);
>>> if (cacheEntry.getResource() == null) {
>>> updatePermissionTreeFromDB();
>>> cacheEntry.setResource(root);
>>> if (log.isDebugEnabled()) {
>>> log.debug("Set resource to true");
>>> }
>>> }
>>> }
>>> }
>>> } else {
>>> synchronized (this) {
>>> updatePermissionTreeFromDB();
>>> cacheKey = new PermissionTreeCacheKey(cacheIdentifier, 
>>> tenantId);
>>> cacheEntry = new GhostResource(root);
>>> permissionCache.put(cacheKey, cacheEntry);
>>> if (log.isDebugEnabled()) {
>>> log.debug("Loaded from database");
>>> }
>>> }
>>> }
>>> }
>>>
>>>
>>> Can this be modified as follows to avoid the above mentioned issue?
>>>
>>> void updatePermissionTree() throws UserStoreException {
>>> PermissionTreeCacheKey cacheKey = new 
>>> PermissionTreeCacheKey(cacheIdentifier, tenantId);
>>> GhostResource cacheEntry = (GhostResource) 
>>> permissionCache.get(cacheKey);
>>> if (cacheEntry != null && cacheEntry.getResource() != null) {
>>> return;
>>> }
>>> synchronized (this) {
>>> if (cacheEntry != null && cacheEntry.getResource() != null) {
>>> return;
>>> }
>>> if (cacheEntry == null) {
>>> cacheEntry = new GhostResource(null);
>>> permissionCache.put(cacheKey, cacheEntry);
>>> }
>>> if (cacheEntry.getResource() == null) {
>>> updatePermissionTreeFromDB();
>>> cacheEntry.setResource(root);
>>> if (log.isDebugEnabled()) {
>>> log.debug("Resource Loaded from database for cachekey: " + 
>>> cacheEntry);
>>> }
>>> }
>>> }
>>> }
>>>
>>>
>>> Thanks,
>>> Chalitha
>>>
>>>
>>> --
>>> *Chalitha Sanyuja Kulathunga*
>>> *Software Engineer*
>>> WSO2 Inc.; http://wso2.com
>>> email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
>>>
>>
>>
>>
>> --
>> *Chalitha Sanyuja Kulathunga*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
>>
>
>


-- 
*Chalitha Sanyuja Kulathunga*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: chalit...@wso2.com cell: +94 77 5927581 <+94+77+5927581>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Orbit] Adding Storm 00.10.1 orbit bundle

[Jayanga Dissanayake]

Hi Sajith,

Thusitha has put some inline comments in the PR.
Can you please make the necessary changes and send the PR back.

Thanks,
Jayanga.

*Jayanga Dissanayake*
Associate Technical Lead
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259


On Wed, Aug 24, 2016 at 10:34 AM, Sajith Ravindra  wrote:

> ping
>
> Thanks
> *,Sajith Ravindra*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
> blog: http://sajithr.blogspot.com/
> 
>
> On Mon, Aug 22, 2016 at 11:22 AM, Sajith Ravindra 
> wrote:
>
>> Hi Kernal team,
>>
>> Could you please review and merge the pull request
>> https://github.com/wso2/orbit/pull/226 to add the new storm version
>> 0.10.1.
>>
>> Thanks
>> *,Sajith Ravindra*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273550
>> blog: http://sajithr.blogspot.com/
>> 
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Orbit] Adding Storm 00.10.1 orbit bundle

[Sajith Ravindra]

ping

Thanks
*,Sajith Ravindra*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 2273550
blog: http://sajithr.blogspot.com/


On Mon, Aug 22, 2016 at 11:22 AM, Sajith Ravindra  wrote:

> Hi Kernal team,
>
> Could you please review and merge the pull request
> https://github.com/wso2/orbit/pull/226 to add the new storm version
> 0.10.1.
>
> Thanks
> *,Sajith Ravindra*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273550
> blog: http://sajithr.blogspot.com/
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Problem with integrating Event Stream OSGi Service

[Srinath Perera]

+1 actually keeping the event stream definitions in the client as well lead
to lot of complications when server and client versions does not match. We
had this problem with BAM and decided to keep it only in the server. ( I
can find and send the mailing thread if needed)

If clients need it, he should get it from the server.

--Srinath

On Wed, Aug 24, 2016 at 10:05 AM, Nuwan Dias  wrote:

> Hi,
>
> I spoke with Srinath regarding this too. It would be ideal to have a
> global config which can override the per-stream configs so that we won't
> have to maintain the DAS configs in multiple places. In all cases we've
> come across so far we've only seen people use a single DAS (or cluster) and
> publish all streams to that DAS cluster. So at least as of now I don't see
> much value in having per stream config files.
>
> It would also be good if we can omit the necessity of having to define the
> streams on the client side (because they're already defined on the server).
> I see two main problems of having to define them on the clients.
>
> 1. When we have multiple event generators (a gateway cluster), the streams
> will have to be defined on all nodes. Do we use dep-sync to sync up the
> configs on the clients? Even if we do, I think its better to not depend on
> dep-sync for the new stuff we're developing because we're moving away from
> dep-sync soon.
>
> 2. Problems in upgrading to newer product versions. When upgrading the
> product version, if a schema change has occurred, currently we only have to
> worry about changing the schema on the server side. With the above
> limitation, we now have to worry about changing the clients too.
>
> Thanks,
> NuwanD.
>
> On Tue, Aug 23, 2016 at 10:16 PM, Malintha Amarasinghe  > wrote:
>
>> Hi All,
>>
>> Currently APIM is using an internal APIM specific configuration resides
>> in api-manager.xml which include DAS server URL, username, password etc.
>> Those configuration are used to instantiate an org.wso2.carbon.databridge.
>> agent.DataPublisher object, which is then used to publish events
>> directly to streams in DAS.
>>
>> As it is an APIM specific configuration, it is not reusable by other
>> non-APIM features. Also org.wso2.carbon.databridge.agent.DataPublisher is
>> intended to be used in non-carbon environments, for carbon environments,
>> the recommended way is to use the Event Stream OSGi Service.
>>
>> So we were trying to re-structure APIM data publishing code to use new
>> Event Stream OSGi service explained in [1].
>>
>> 1. Create all the streams defined in DAS in APIM.
>> 2. Create an *event publisher per each stream *which takes data from the
>> stream and publish to DAS.
>> 3. In each event publisher we need to configure DAS specific
>> configuration.
>>
>> Ex:
>> 
>> http://wso2.org/carbon/eventpublisher;>
>>   
>>   
>>   
>> admin
>> thrift
>> non-blocking
>> 0
>> tcp://localhost:7611
>> 
>>   
>> 
>>
>> But we are facing a small problem here; in APIM there are many event
>> streams being used. If there's a change happen to DAS configuration, we
>> need to change it in all the event publishers which makes it difficult to
>> maintain. As per the offline chat with DAS team, this is a current
>> limitation.
>>
>> Are we going to move forward with the existing implementation?
>>
>> Thanks,
>> Malintha
>>
>> [1] [Dev] Common configuration for publishing events from carbon servers
>> to DAS/CEP
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

Srinath Perera, Ph.D.
   http://people.apache.org/~hemapani/
   http://srinathsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Problem with integrating Event Stream OSGi Service

[Nuwan Dias]

Hi,

I spoke with Srinath regarding this too. It would be ideal to have a global
config which can override the per-stream configs so that we won't have to
maintain the DAS configs in multiple places. In all cases we've come across
so far we've only seen people use a single DAS (or cluster) and publish all
streams to that DAS cluster. So at least as of now I don't see much value
in having per stream config files.

It would also be good if we can omit the necessity of having to define the
streams on the client side (because they're already defined on the server).
I see two main problems of having to define them on the clients.

1. When we have multiple event generators (a gateway cluster), the streams
will have to be defined on all nodes. Do we use dep-sync to sync up the
configs on the clients? Even if we do, I think its better to not depend on
dep-sync for the new stuff we're developing because we're moving away from
dep-sync soon.

2. Problems in upgrading to newer product versions. When upgrading the
product version, if a schema change has occurred, currently we only have to
worry about changing the schema on the server side. With the above
limitation, we now have to worry about changing the clients too.

Thanks,
NuwanD.

On Tue, Aug 23, 2016 at 10:16 PM, Malintha Amarasinghe 
wrote:

> Hi All,
>
> Currently APIM is using an internal APIM specific configuration resides in
> api-manager.xml which include DAS server URL, username, password etc. Those
> configuration are used to instantiate an org.wso2.carbon.databridge.agent.
> DataPublisher object, which is then used to publish events directly to
> streams in DAS.
>
> As it is an APIM specific configuration, it is not reusable by other
> non-APIM features. Also org.wso2.carbon.databridge.agent.DataPublisher is
> intended to be used in non-carbon environments, for carbon environments,
> the recommended way is to use the Event Stream OSGi Service.
>
> So we were trying to re-structure APIM data publishing code to use new
> Event Stream OSGi service explained in [1].
>
> 1. Create all the streams defined in DAS in APIM.
> 2. Create an *event publisher per each stream *which takes data from the
> stream and publish to DAS.
> 3. In each event publisher we need to configure DAS specific configuration.
>
> Ex:
> 
> http://wso2.org/carbon/eventpublisher;>
>   
>   
>   
> admin
> thrift
> non-blocking
> 0
> tcp://localhost:7611
> 
>   
> 
>
> But we are facing a small problem here; in APIM there are many event
> streams being used. If there's a change happen to DAS configuration, we
> need to change it in all the event publishers which makes it difficult to
> maintain. As per the offline chat with DAS team, this is a current
> limitation.
>
> Are we going to move forward with the existing implementation?
>
> Thanks,
> Malintha
>
> [1] [Dev] Common configuration for publishing events from carbon servers
> to DAS/CEP
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>



-- 
Nuwan Dias

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

Re: [Dev] GSoC2016-Contact Development Team Feature

[Awanthika Senarath]

Hello Susinda,

If the email address is configured by us to send the reports, it is true
that we should not allow the user to edit it, since it may prevent us
getting the reports,

But the user should be able to see it. we can leave it visible un-editable.
WDYT? Given the deadlines, aren't we too late to be discussing this anyway?

Anyways Nathiesha good work, the blog posts were great! I felt the same as
Jasintha, please replace the background image so that your content is more
visible to the reader :)

Regards
Awanthika

On Wed, Aug 24, 2016 at 12:43 PM, Susinda Perera  wrote:

>
>
> On Wed, Aug 24, 2016 at 8:03 AM, Danushka Fernando 
> wrote:
>
>> Hi
>> test4475 is the organization name. You can either try with some other
>> organization name or you can use the custom url feature in App Cloud. But
>> you will need to add a cname entry in a name service provider.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Senior Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> On Wed, Aug 24, 2016 at 7:52 AM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Regarding the app cloud URL, the URL I got was "
>>> http://test4475-error-publisher-4-0-0.wso2apps.com/;. I can change the
>>> "error-publisher" part in the URL. But I cannot edit the "test4475" part. I
>>> will inquire from the App Cloud team regarding that and see if it is
>>> possible to get a new URL. Since I created a WSO2 app cloud account for
>>> temporary testing purposes, that URL was added to the preferences page and
>>> added the screenshot of it for demonstration purposes.
>>>
>>> I removed the "devstu...@gmail.com" email address and added a new
>>> screenshot to the blog post.
>>>
>> Hi Nathesha
> What i mean was, we dont need to let this information to be edited by
> users, Isnt it?, This may be a mail address that we configured which is to
> be used in sending reports. Souser may not need to see this or edit this.
>
>>
>>> I made the submission to GSOC Final Evaluation. But I can update the
>>> blog post contents where necessary.
>>> Thank you for the support and guidance given through out this period.
>>>
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>>
>>>
>>> On Tue, Aug 23, 2016 at 10:38 AM, Susinda Perera 
>>> wrote:
>>>
 In the [2], Cant we get some other url from wso2apss.com, Also I dont
 think that we need to show the devstu...@gmail.com mail address
 [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
 use-of-error-reporting.html

 On Tue, Aug 23, 2016 at 10:27 AM, Kavith Lokuhewage 
 wrote:

> Hi Nathiesha,
>
> Blog post looks good enough and it provides enough information about
> the work you have done.
>
> Please let us know if you find any issues related to submission. Since
> tomorrow is the last day for your submission, we can have a meeting today
> or tomorrow to clear out any issues.
>
> Please let us know.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Sun, Aug 21, 2016 at 11:53 AM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi,
>>
>> This is the link to the blog post regarding my project [1].
>> There I have added a brief introduction about the project, and how
>> the plugin works. I also added the links to the GitHub repositories. 
>> Since
>> it was advised to add the URLs of the commits, in the email I got from
>> Google regarding the final evaluations, I added the links of my commits 
>> as
>> well. Please have a look and let me know if the post is good enough for
>> submission.
>>
>> I also created a blog post [2] on the use of the plugin, and added
>> that link as well in the above mentioned post[1]. Please let me know
>> whether it is good enough or any changes need to be done for that.
>>
>> [1]. http://nathiesha.blogspot.com/2016/08/contact-developme
>> nt-team-feature-in.html
>> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
>> use-of-error-reporting.html
>>
>> Thanks and regards
>>
>> Nathiesha
>>
>>
>> On Sat, Aug 20, 2016 at 10:13 AM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi ,
>>>
>>> Thank you for the suggestion. I started writing a blog post with all
>>> the repository links in it as you have suggested.
>>> I will send the link of the blog post as soon as possible.
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>> On Fri, Aug 19, 2016 at 8:31 AM, Kavith Lokuhewage 
>>> wrote:
>>>

Re: [Dev] GSoC2016-Contact Development Team Feature

[Susinda Perera]

On Wed, Aug 24, 2016 at 8:03 AM, Danushka Fernando 
wrote:

> Hi
> test4475 is the organization name. You can either try with some other
> organization name or you can use the custom url feature in App Cloud. But
> you will need to add a cname entry in a name service provider.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
> On Wed, Aug 24, 2016 at 7:52 AM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi,
>>
>> Regarding the app cloud URL, the URL I got was "
>> http://test4475-error-publisher-4-0-0.wso2apps.com/;. I can change the
>> "error-publisher" part in the URL. But I cannot edit the "test4475" part. I
>> will inquire from the App Cloud team regarding that and see if it is
>> possible to get a new URL. Since I created a WSO2 app cloud account for
>> temporary testing purposes, that URL was added to the preferences page and
>> added the screenshot of it for demonstration purposes.
>>
>> I removed the "devstu...@gmail.com" email address and added a new
>> screenshot to the blog post.
>>
> Hi Nathesha
What i mean was, we dont need to let this information to be edited by
users, Isnt it?, This may be a mail address that we configured which is to
be used in sending reports. Souser may not need to see this or edit this.

>
>> I made the submission to GSOC Final Evaluation. But I can update the blog
>> post contents where necessary.
>> Thank you for the support and guidance given through out this period.
>>
>>
>> Thanks and regards
>>
>> Nathiesha
>>
>>
>>
>> On Tue, Aug 23, 2016 at 10:38 AM, Susinda Perera 
>> wrote:
>>
>>> In the [2], Cant we get some other url from wso2apss.com, Also I dont
>>> think that we need to show the devstu...@gmail.com mail address
>>> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
>>> use-of-error-reporting.html
>>>
>>> On Tue, Aug 23, 2016 at 10:27 AM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Nathiesha,

 Blog post looks good enough and it provides enough information about
 the work you have done.

 Please let us know if you find any issues related to submission. Since
 tomorrow is the last day for your submission, we can have a meeting today
 or tomorrow to clear out any issues.

 Please let us know.

 Thanks,

 *Kavith Lokuhewage*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com
 lean . enterprise . middleware
 Mobile - +94779145123
 Linkedin 
 Twitter 

 On Sun, Aug 21, 2016 at 11:53 AM, Nathiesha Maddage <
 nathieshamadd...@gmail.com> wrote:

> Hi,
>
> This is the link to the blog post regarding my project [1].
> There I have added a brief introduction about the project, and how the
> plugin works. I also added the links to the GitHub repositories. Since it
> was advised to add the URLs of the commits, in the email I got from Google
> regarding the final evaluations, I added the links of my commits as well.
> Please have a look and let me know if the post is good enough for
> submission.
>
> I also created a blog post [2] on the use of the plugin, and added
> that link as well in the above mentioned post[1]. Please let me know
> whether it is good enough or any changes need to be done for that.
>
> [1]. http://nathiesha.blogspot.com/2016/08/contact-developme
> nt-team-feature-in.html
> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
> use-of-error-reporting.html
>
> Thanks and regards
>
> Nathiesha
>
>
> On Sat, Aug 20, 2016 at 10:13 AM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi ,
>>
>> Thank you for the suggestion. I started writing a blog post with all
>> the repository links in it as you have suggested.
>> I will send the link of the blog post as soon as possible.
>>
>> Thanks and regards
>>
>> Nathiesha
>>
>> On Fri, Aug 19, 2016 at 8:31 AM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Nathiesha,
>>>
>>> You already have two standalone github repos for the plugin and
>>> micro-service. Furthermore, you have a fork of devs-kernel repo with the
>>> code for the plugin is merged - the one you have prepared to send the 
>>> pull
>>> request.
>>>
>>> Since there are multiple places and we cannot submit a single link
>>> for them - in my point of view - the best option is to write a blog 
>>> post as
>>> they have suggested. You can include the links to individual repos and
>>> forked repo with a filter for your commits. Importantly, you can put the
>>> link for pull request too - once you sent it.
>>>
>>> This way, everyone will have a clear picture of your 

Re: [Dev] Getting accumulative values from stream

[Grainier Perera]

Hi Aneela,

At glace, there's some issues with your query. Is there a particular reason
for you to use `group by milliseconds`? otherwise you shouldn't be group by
such rapidly changing variable.  And also, the count aggregate  function
does not require any parameters and it does not have to be casted in to
int. Try the following query and see whether it works, if it doesn't can
you provide us with sample data and stream definitions?, then we can test
the query.

from FTPInStream[command == 'USER']
> select time:timestampInMilliseconds(time:dateAdd(str:replaceAll(ts,'T','
> '), 5, 'hour',"-MM-dd HH:mm:ss"),'-MM-dd HH:mm*:ss*') as
> milliseconds , uid, id_orig_h, id_orig_p, id_resp_h, id_resp_p
> insert into intermediateStream;



>
> from intermediateStream#window.externalTimeBatch( milliseconds ,1 min,
> milliseconds, 1 min)
> select time:dateFormat(milliseconds, '-MM-dd HH:mm' ) as ts , count() as
> ftp_requests
> insert into FTPOutStream;


Regards,
Grainier

On Tue, Aug 23, 2016 at 2:16 PM, Aneela Safdar  wrote:

> Hi,
>
> I have been using following siddhi query to get the events count per
> minute;  ts as timestamp (string) and ftp_requests as count (int)
>
> from FTPInStream[command == 'USER']
> select time:timestampInMilliseconds(time:dateAdd(str:replaceAll(ts,'T','
> '), 5, 'hour',"-MM-dd HH:mm:ss"),'-MM-dd HH:mm') as milliseconds ,
> uid, id_orig_h, id_orig_p, id_resp_h, id_resp_p
> insert into intermediateStream;
>
> from intermediateStream#window.externalTimeBatch( milliseconds ,1 min,
> milliseconds, 1 min)
> select time:dateFormat(milliseconds, '-MM-dd HH:mm' ) as ts ,
> cast(count(milliseconds), 'int') as ftp_requests
> group by milliseconds
> insert into FTPOutStream;
>
> There is a need to populate ftp_requests parameter of FTPOutStream as
> accumulative i.e. (each new no of requests is addition of itself and
> previously added to stream). To achieve this I changed the query as below:
>
> from FTPInStream[command == 'USER']
> select time:timestampInMilliseconds(time:dateAdd(str:replaceAll(ts,'T','
> '), 5, 'hour',"-MM-dd HH:mm:ss"),'-MM-dd HH:mm') as milliseconds ,
> uid, id_orig_h, id_orig_p, id_resp_h, id_resp_p
> insert into intermediateStream;
>
> from intermediateStream
> select milliseconds, cast(count(milliseconds), 'int') as ftp_request
> group by milliseconds
> insert into intermediateStream111;
>
> from intermediateStream111#window.externalTimeBatch( milliseconds ,1 min,
> milliseconds, 1 min)
> select time:dateFormat(milliseconds, '-MM-dd HH:mm' ) as ts ,
> cast(sum(ftp_request), 'int') as ftp_requests
> insert into FTPOutStream;
>
> But I am getting nothing in ftp_requests parameter.
>
> Any suggestions?
>
> Regards,
> Aneela Safdar
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi,

Regarding the app cloud URL, the URL I got was "
http://test4475-error-publisher-4-0-0.wso2apps.com/;. I can change the
"error-publisher" part in the URL. But I cannot edit the "test4475" part. I
will inquire from the App Cloud team regarding that and see if it is
possible to get a new URL. Since I created a WSO2 app cloud account for
temporary testing purposes, that URL was added to the preferences page and
added the screenshot of it for demonstration purposes.

I removed the "devstu...@gmail.com" email address and added a new
screenshot to the blog post.

I made the submission to GSOC Final Evaluation. But I can update the blog
post contents where necessary.
Thank you for the support and guidance given through out this period.


Thanks and regards

Nathiesha



On Tue, Aug 23, 2016 at 10:38 AM, Susinda Perera  wrote:

> In the [2], Cant we get some other url from wso2apss.com, Also I dont
> think that we need to show the devstu...@gmail.com mail address
> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
> use-of-error-reporting.html
>
> On Tue, Aug 23, 2016 at 10:27 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> Blog post looks good enough and it provides enough information about the
>> work you have done.
>>
>> Please let us know if you find any issues related to submission. Since
>> tomorrow is the last day for your submission, we can have a meeting today
>> or tomorrow to clear out any issues.
>>
>> Please let us know.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Sun, Aug 21, 2016 at 11:53 AM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> This is the link to the blog post regarding my project [1].
>>> There I have added a brief introduction about the project, and how the
>>> plugin works. I also added the links to the GitHub repositories. Since it
>>> was advised to add the URLs of the commits, in the email I got from Google
>>> regarding the final evaluations, I added the links of my commits as well.
>>> Please have a look and let me know if the post is good enough for
>>> submission.
>>>
>>> I also created a blog post [2] on the use of the plugin, and added that
>>> link as well in the above mentioned post[1]. Please let me know whether it
>>> is good enough or any changes need to be done for that.
>>>
>>> [1]. http://nathiesha.blogspot.com/2016/08/contact-developme
>>> nt-team-feature-in.html
>>> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
>>> use-of-error-reporting.html
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>>
>>> On Sat, Aug 20, 2016 at 10:13 AM, Nathiesha Maddage <
>>> nathieshamadd...@gmail.com> wrote:
>>>
 Hi ,

 Thank you for the suggestion. I started writing a blog post with all
 the repository links in it as you have suggested.
 I will send the link of the blog post as soon as possible.

 Thanks and regards

 Nathiesha

 On Fri, Aug 19, 2016 at 8:31 AM, Kavith Lokuhewage 
 wrote:

> Hi Nathiesha,
>
> You already have two standalone github repos for the plugin and
> micro-service. Furthermore, you have a fork of devs-kernel repo with the
> code for the plugin is merged - the one you have prepared to send the pull
> request.
>
> Since there are multiple places and we cannot submit a single link for
> them - in my point of view - the best option is to write a blog post as
> they have suggested. You can include the links to individual repos and
> forked repo with a filter for your commits. Importantly, you can put the
> link for pull request too - once you sent it.
>
> This way, everyone will have a clear picture of your work and the best
> part - what is the final work that is going to be merged into WSO2
> repository.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Thu, Aug 18, 2016 at 11:55 AM, Nathiesha Maddage <
> nathieshamadd...@gmail.com> wrote:
>
>> Hi,
>>
>> I have completed almost all of the coding part now, and working with
>> fixing a few left errors and tidying the code.
>>
>> I plan to submit the plugin project, feature project and the
>> documentation as the deliverable.
>> For the final submission, I need to upload a URL that contains our
>> project. For that Google has provided certain examples such as the link 
>> of
>> Git Hub commits, a web page or a blog post, 

Re: [Dev] [GSoC Final Evaluation] Proposal 21: [IS] Document Based NoSQL Support for WSO2 Identity Server Database

[Tharindu Edirisinghe]

Excellent work Asantha.

We really appreciate your effort put towards making this project a success
!

On Mon, Aug 22, 2016 at 8:52 PM, Asantha Thilina 
wrote:

> Hi all,
>
> I have prepared my final report in GSoC[1] and there i have added all my
> repositories,PR,blog posts,documents and mail threads and i have prepared a
> final blog post here[2] mentioning all my experience in GSoC 2016
>
> [1] https://asanthamax.github.io/mongodbuserstore/
> [2] http://asanthamax.blogspot.com/2016/08/my-gsoc-final-summary.html
>
> Thanks,
> Asantha
>
>
> On Sat, Aug 20, 2016 at 1:23 AM, Asantha Thilina  > wrote:
>
>> Hi Chamila,
>>
>> I have added new pull requests to orbit[1] for new org.json version
>>
>> [1]https://github.com/wso2/orbit/pull/225
>>
>> thanks,
>> Asantha
>>
>> On Fri, Aug 19, 2016 at 9:58 PM, Chamila Wijayarathna <
>> cdwijayarat...@gmail.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> For creating new orbit, you will have to send 1 PR to wso2/orbit
>>> repository[1] as well. There inside json folder, you'll have to define a
>>> new json orbit with new version (eg: 3.0.0wso2v2) and there you will have
>>> to refer the new json version you are depending on.
>>>
>>> In your PR, you are referring to 3.0.0wso2v1 which is depending on the
>>> older version we are talking about. So this will still cause the issue you
>>> are talking.
>>>
>>> Thank You!
>>>
>>> On Sat, Aug 20, 2016 at 12:47 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Johann,

 first of all ,sorry for the late reply earlier i wasn't added org.json
 to bundleDef now i have fixed the issue and i have added new orbit as
 chamila mentioned for org.json as defined in here[1] i have added version
 20160212 because version 20140107  which is already in IS causing some
 problems for my userstore methods even it successfully deployed ,after
 adding version 20160212 solved the issue now my userstore is deploy
 org.json  20160212  also to the IS during packaging and i have updated
 the PR[2] with the latest modifications

 [1]https://github.com/wso2/orbit/blob/master/json/3.0.0.wso2v1/pom.xml
 [2]https://github.com/wso2-extensions/identity-userstore-mongodb/pull/1

 thanks,
 Asantha

 On Fri, Aug 19, 2016 at 5:45 AM, Johann Nallathamby 
 wrote:

> Hi Asantha,
>
> As Chamila mentioned you need to bundle the required library in your
> feature as well, so that it is self contained, and can be installed
> independently in any carbon server.
>
> Have you added that in your PR? I couldn't see a bundleDef for
> org.json.
>
> Regards,
> Johann.
>
> On Fri, Aug 19, 2016 at 3:04 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi all,
>>
>> First of all let me apologize for the late reply ,I have changed the
>> org.json version as chamila said and now it's working no need to add json
>> lib manually and version changed will not affected to any of my code i 
>> have
>> updated the PR[1] with latest modifications now it's need
>> mongodb-java-driver only to run the module no other extra library 
>> required
>>
>> [1]https://github.com/wso2-extensions/identity-userstore-mon
>> godb/pull/1
>>
>> Thanks,
>> Asantha
>>
>> On Fri, Aug 19, 2016 at 1:26 AM, Chamila Wijayarathna <
>> cdwijayarat...@gmail.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> If you have used any new features of org.json which is not available
>>> in that old version, I think you will have to create an orbit with new
>>> org.json version.
>>>
>>> And I think it (either new or old version) need to be packed in your
>>> feature, so it can be installed into any carbon based product.
>>>
>>> Thanks!
>>>
>>> On Fri, Aug 19, 2016 at 3:17 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Chamila,

 ok thanks for the comment then i will change the version of my
 dependency and test it

 Thanks,
 Asantha

 On Fri, Aug 19, 2016 at 1:13 AM, Chamila Wijayarathna <
 cdwijayarat...@gmail.com> wrote:

> Hi Asantha, Tharindu,
>
> I think IS already packs json, but the version is 20140107 which
> comes from wso2 orbit bundle [1]. You are receiving the error due to
> version mismatch, because you are using  version 20160212.
>
> Can you try using existing dependency and check if your features
> work okay with that version?\\
>
> Thank You!
>
> [1]. https://github.com/wso2/orbit/blob/master/json/3.0.0.wso2v1
>
> On Fri, Aug 19, 2016 at 3:03 PM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> I meant shipping with 

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

On Wed, Aug 24, 2016 at 12:10 AM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I submitted my final evaluation with this link [1]. It contains all the
> information including what's done, what's yet to be done, repos and the
> blogspot.
>

​Great! Thanks Osura! We will go through everything.

Thanks​


>
> [1] https://github.com/osuran/GSoC-16-final-submission/blob/
> master/README.md
>
> Thanks
>
> On Tue, Aug 23, 2016 at 5:11 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Tue, Aug 23, 2016 at 2:48 PM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Issue #6 was fixed.
>>>
>> great! thanks.
>>
>>>
>>> Thanks,
>>>
>>> On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 I'm fixing issue #6 and  almost done. I will fix other issues soon
 after finishing #6.

 Thanks,

 On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> Several issues reported against the membership scheme is still in open
> state [1]. Other than issue 6, all others are straightforward to fix.
> Please fix those asap.
>
> [1]. https://github.com/osuran/azure-membership-scheme/issues
>
> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> current status: I'm trying to implement the deploy.sh by trying to
>> invoke puppet to install product configuration at the startup of a puppet
>> installed VM. But still couldn't come up with a presentable outcome.
>>
>> Thanks,
>>
>> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake <
>> osura...@gmail.com> wrote:
>>
>>> Thank you
>>>
>>>
>>> On Thursday, August 18, 2016, Imesh Gunaratne 
>>> wrote:
>>>


 On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Imesh,
>
> Yes now I understand that creating VM images for each product
> profile will not going to work out.
>
> Can you please give me a step by step guideline on what I should
> do to achieve this?
>

 ​Please refer [1] and [2].

 [1] https://github.com/wso2/puppet-modules
 [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
 mentation​


 ​Thanks​

 .
>  Thank you,
>
> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
> wrote:
>
>>
>>
>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne > > wrote:
>>>
>>>
>>> ​There are many spelling mistakes on this file [2], please
>>> review it again.
>>>
>>
>> ​Correction: s/on this file/in this file/g
>>
>> Thanks
>> ​
>>
>>
>>> Overall I see very less attention to detail in this repository
>>> and the membership scheme implementation.
>>>
>>>
 There I mentioned the things that should be kept in mind while
 configuring wso2 AS and did not go in to detail on hot to 
 configure as it
 can be found in the wso2 documentation. Would that be okay?

>>>
>>> ​I don't think this is helpful. Without having detailed steps
>>> users might not be able to do a complete deployment.
>>>
>>> Few questions:
>>>
>>>- How do you create a distributed deployment​
>>>
>>>​of AS ​or any other product (say for an example WSO2 API-M)
>>>with this approach? As I explained earlier creating a VM image 
>>> per product
>>>profile is an unnecessary overhead (time consumption, disk space 
>>> needed,
>>>maintenance, etc).
>>>
>>>- ​What would be the approach of applying​
>>> a patch or do
>>>​ing​
>>>a configuration change in a such deployment?
>>>
>>> ​IMO it is really important to understand the concepts well and
>>> solve problems with the most efficient manner. Otherwise the 
>>> outcome of
>>> this project might not be usable.
>>>
>>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>>
>>> Thanks
>>>
>>>
 user do not need to change anything in template.json, so should
 I explain the parameters in that too?

 in the paramters.json, except for the vm_image parameter, all
 of the parameters are just for the naming of the elements that you 
 find in
 a VM, for an example, the name of 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I submitted my final evaluation with this link [1]. It contains all the
information including what's done, what's yet to be done, repos and the
blogspot.

[1] https://github.com/osuran/GSoC-16-final-submission/blob/master/README.md

Thanks

On Tue, Aug 23, 2016 at 5:11 PM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Tue, Aug 23, 2016 at 2:48 PM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Issue #6 was fixed.
>>
> great! thanks.
>
>>
>> Thanks,
>>
>> On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> I'm fixing issue #6 and  almost done. I will fix other issues soon after
>>> finishing #6.
>>>
>>> Thanks,
>>>
>>> On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 Several issues reported against the membership scheme is still in open
 state [1]. Other than issue 6, all others are straightforward to fix.
 Please fix those asap.

 [1]. https://github.com/osuran/azure-membership-scheme/issues

 On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> current status: I'm trying to implement the deploy.sh by trying to
> invoke puppet to install product configuration at the startup of a puppet
> installed VM. But still couldn't come up with a presentable outcome.
>
> Thanks,
>
> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake  > wrote:
>
>> Thank you
>>
>>
>> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Imesh,

 Yes now I understand that creating VM images for each product
 profile will not going to work out.

 Can you please give me a step by step guideline on what I should do
 to achieve this?

>>>
>>> ​Please refer [1] and [2].
>>>
>>> [1] https://github.com/wso2/puppet-modules
>>> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
>>> mentation​
>>>
>>>
>>> ​Thanks​
>>>
>>> .
  Thank you,

 On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
 wrote:

>
>
> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
> wrote:
>>
>>
>> ​There are many spelling mistakes on this file [2], please review
>> it again.
>>
>
> ​Correction: s/on this file/in this file/g
>
> Thanks
> ​
>
>
>> Overall I see very less attention to detail in this repository
>> and the membership scheme implementation.
>>
>>
>>> There I mentioned the things that should be kept in mind while
>>> configuring wso2 AS and did not go in to detail on hot to configure 
>>> as it
>>> can be found in the wso2 documentation. Would that be okay?
>>>
>>
>> ​I don't think this is helpful. Without having detailed steps
>> users might not be able to do a complete deployment.
>>
>> Few questions:
>>
>>- How do you create a distributed deployment​
>>
>>​of AS ​or any other product (say for an example WSO2 API-M)
>>with this approach? As I explained earlier creating a VM image 
>> per product
>>profile is an unnecessary overhead (time consumption, disk space 
>> needed,
>>maintenance, etc).
>>
>>- ​What would be the approach of applying​
>> a patch or do
>>​ing​
>>a configuration change in a such deployment?
>>
>> ​IMO it is really important to understand the concepts well and
>> solve problems with the most efficient manner. Otherwise the outcome 
>> of
>> this project might not be usable.
>>
>> [2] https://github.com/osuran/azure-artifacts/issues/2
>>
>> Thanks
>>
>>
>>> user do not need to change anything in template.json, so should
>>> I explain the parameters in that too?
>>>
>>> in the paramters.json, except for the vm_image parameter, all of
>>> the parameters are just for the naming of the elements that you 
>>> find in a
>>> VM, for an example, the name of the network interface. Therefore I 
>>> have
>>> given instructions on how to set the vm_image parameter.
>>>
>>> current progress: The script which was generated by Azure does
>>> not have the capability to add a custom VM image. I modified it so 
>>> that now
>>> it 

Re: [Dev] GSOC 2016: Proposal 7

[Kasun Indrasiri]

Thanks, Dinanjana. I think it's good to have how different scenarios can be
handled from ESB flight recorder information.
- OOM
- CPU spinning
- Deadlock
etc.

Thanks,
Kasun.

On Mon, Aug 22, 2016 at 11:02 PM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Hi all,
> Currently the tool supports generating jfr along with thread dumps and
> heap dumps. And the report template has been changed so that it reflects a
> lot more details on environmental details during an event. All collectibles
> along with thread dumps and jfrs will be bundled in to a zip archive now.
> This zip archive will be generated for each "event". This contains the
> report, thread dumps(if user requested) & jfr (if user requested). Report
> is a HTML file. Thread dumps are also viewable through this report.User can
> change the template as he wish by changing the report template HTML file
>
> On Tue, Aug 23, 2016 at 11:28 AM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Dear all,
>> This[1]
>> 
>>  is
>> the blog post I made for final work product submission. Please have a look.
>> :)
>> [1]http://dinanjanagunaratne.blogspot.com/2016/08/during-pas
>> t-3-months-i-was-engaged-in.html
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kasun Indrasiri
Director, Integration Technologies
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +1 650 450 2293
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Notification facility in Analytics Dashboard

[Aneela Safdar]

Hi,
I am generating a bar chart from some log files in dashboard, there are times 
when bar raises high due to huge amount of  network traffic and as it is 
happening in real time, there might come a scenario when some body would 
overlook those high bars as chart is continuously being updated. I was 
wondering is there any notification or alert service available that I can use 
if bar goes higher than a certain threshold value?? If so what are my options? 
Regards, Aneela Safdar___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Problem with integrating Event Stream OSGi Service

[Malintha Amarasinghe]

Hi All,

Currently APIM is using an internal APIM specific configuration resides in
api-manager.xml which include DAS server URL, username, password etc. Those
configuration are used to instantiate an org.wso2.carbon.databridge.agent.
DataPublisher object, which is then used to publish events directly to
streams in DAS.

As it is an APIM specific configuration, it is not reusable by other
non-APIM features. Also org.wso2.carbon.databridge.agent.DataPublisher is
intended to be used in non-carbon environments, for carbon environments,
the recommended way is to use the Event Stream OSGi Service.

So we were trying to re-structure APIM data publishing code to use new
Event Stream OSGi service explained in [1].

1. Create all the streams defined in DAS in APIM.
2. Create an *event publisher per each stream *which takes data from the
stream and publish to DAS.
3. In each event publisher we need to configure DAS specific configuration.

Ex:

http://wso2.org/carbon/eventpublisher;>
  
  
  
admin
thrift
non-blocking
0
tcp://localhost:7611

  


But we are facing a small problem here; in APIM there are many event
streams being used. If there's a change happen to DAS configuration, we
need to change it in all the event publishers which makes it difficult to
maintain. As per the offline chat with DAS team, this is a current
limitation.

Are we going to move forward with the existing implementation?

Thanks,
Malintha

[1] [Dev] Common configuration for publishing events from carbon servers to
DAS/CEP
-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

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

Re: [Dev] [Gsoc2016] [PC] Web (Javascript / D3) based BPMN editor to support a subset of commonly used BPMN constructs

[Heshan Jayasinghe]

Hi All,

I completed and submit "Web (Javascript / D3) based BPMN editor to support
a subset of commonly used BPMN constructs"  project in google summer of
code dashboard.Hope i completed most of the task you gave to me in this
project.I have some known issues in the project.I published my last commit
in GSoC project but fixing existing known issues is still in progress. I
will like to work on those issues if you give your support.

You all can access my project using this document :
https://gist.github.com/heshanjse/25e727ce17e8b76619f70fbb91b4226f

Chathura,Isuru and your team helped me a lot to complete this project.you
all kept meetings every week and spent more time for my project.
Thank you so much for your help

Thank you!
regards,
Heshan Jayasinghe


On Tue, Aug 16, 2016 at 8:08 AM, Heshan Jayasinghe 
wrote:

> HI Chathura,
>
> I completed both download and upload json file functionalities.now I am
> working on few fixes that we discussed on last meeting.i will fix above
> mention bugs too.
>
> Thank You!
>
> Regards,
> Heshan Jayasinghe
>
> On Mon, Aug 15, 2016 at 10:35 AM, Chathura Ekanayake 
> wrote:
>
>> Hi Heshan,
>>
>> It looks good so far.. However, there are few fixes to be done.
>>
>> - Properties box cannot be closed.
>> - Circles in bending positions of edges have to be shown only when mouse
>> gets over them
>> - Gateways should allow multiple connection points (at least 4)
>>
>> Regards,
>> Chathura
>>
>> On Fri, Aug 12, 2016 at 6:33 PM, Heshan Jayasinghe 
>> wrote:
>>
>>> Hi All,
>>> After 3 months contributing on Web based BPMN editor i completed
>>> following tasks
>>>
>>>- drag and drop elements(start event/end event/gateway/task) from
>>>tool box to drawing canvas
>>>- display popup tool box with element(start event/end
>>>event/gateway/task) on click event
>>>- flow drawing to connect elements
>>>- Implement element deleting functionality (using delete button in
>>>toolbox)
>>>
>>> -delete only element if there no any flow connections
>>> -delete element with flows if there any flows connected
>>> to that element
>>> -delete flows separately
>>>
>>>- drag elements in the Canvas to change position
>>>- add flow button to toolbox and give flow drawing using toolbox
>>>shortcut
>>>- add property button to tool box and give change properties of the
>>>elements one by one (properties changed according to to element so popup
>>>window changed according to the element)
>>>- add all sub elements to the toolbox and add all above
>>>functionalities to those sub element (sub element icons changed with sub
>>>element type)
>>>
>>>-  start events (default start events,error start
>>> events,message start events,time start events)
>>>-  end event (default end events,error end events,terminate
>>> end events,cancel end events)
>>>-  gateway (parallel gateway , exclusive gateway, inclusive
>>> gateway ,event gateway )
>>>-  task (user task, script task, mail task, manual task)
>>>
>>>- add task resizing functionality
>>>- add text to task (user can change text of the task text entered in
>>>the task element)
>>>- change flow connections with element drag events (if we change
>>>element position using drag and drop,flows connected to that element also
>>>changed according to element new position)
>>>- flow can be changed using multiple connection points
>>>- create JSON array and record all date one by one inside that
>>>array(element x/y coordinates,width,height,element type,element
>>>subtype,properties,etc..)
>>>- JSON array update x,y coordinates when we drag a element
>>>
>>> task on prosess
>>>
>>>- download json file
>>>- upload json file and draw graph according to json file
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Jul 30, 2016 at 11:46 PM, Heshan Jayasinghe 
>>> wrote:
>>>
 HI Hasitha,

 My git repo is up to date .please check develop
  branch in
 GitHub.I completed task text and new flow drawing.now i am working on flow
 change with element drag events and text area resize with task resizing.
  Thank you!
 regards,
 Heshan Jyasinghe


 On Thu, Jul 28, 2016 at 12:27 PM, Hasitha Aravinda 
 wrote:

> Heshan,
>
> Could you please update this mail with your current progress ? Also
> can you update the git repo with latest code base. It was last updated 23
> days ago.
>
> Thanks,
> Hasitha.
>
> On Thu, Jul 14, 2016 at 9:25 AM, Heshan Jayasinghe  > wrote:
>
>> Hi,
>> I added following element to BPMN tool box.I added only boundary
>> events instead of Intermediate event because both look like same and 

Re: [Dev] [ESB] Error connecting to esb-analutics

[Supun Malinga]

Hi All,

Thanks for the help, got it fixed! Issue was that I only changed the config
in worker nodes and depsync had reset the changes... It's working fine now.


On Tue, Aug 23, 2016 at 7:45 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Tue, Aug 23, 2016 at 7:32 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> I already configured MessageFlowConfigurationPublisher.xml and
>> MessageFlowStatisticsPublisher.xml files.
>> tcp://esb-analytics:7612
>>
>> This is the http port I believe. But the error saying it cannot connect
>> to the ssl port 7712 which is not in the configuration..
>>
>> analytics server runs on a different docker container.
>> http : tcp://esb-analytics:7612
>> https: tcp://esb-analytics:7712
>>
>
> @Supun, this is a Thrift communication which uses TCP underneath..
>
> By default thrift port is 7611 and corresponding ssl thrift port is 7711
> (7611+100), check the data-bridge-config.xml file which is in analytics
> server config directory . Since we are shipping analytics products in
> offset 1 then thrift port is 7612 and ssl port is 7712.. Here, ssl port
> (7712) is used for initial authentication purposes of data publisher
> afterwards it uses the thrift port (7612) for event publishing..
>
> Thanks,
> Mohan
>
>
>>
>>
>>
>> On Tue, Aug 23, 2016 at 7:28 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Supun,
>>>
>>> Where did you configure the hostname for the analytics server node?
>>> Publisher configurations files are in the 
>>> ESB_HOME/repository/deployment/server/eventpublishers/
>>> directory. According to the error log, ESB is trying to connect to
>>> localhost:7712 port. Are you starting the analytics server on the same node?
>>>
>>> On Tue, Aug 23, 2016 at 7:11 PM, Supun Malinga  wrote:
>>>
 Hi,

 I configured a ESB cluster with analytics in docker. Followed the guide
 [1] and updated the hostname/port in event publisher artifacts. But still
 ESB gives and error when I try to anable statistics in a proxy service.

 Looks like some configuration is missing. However I searched in configs
 and find any place to change the hostname to the analytics server
 connection. Can someone point me to the correct config pls ?.

 esb_worker1  | [2016-08-23 11:58:51,041]  WARN - DataEndpointGroup
 No receiver is reachable at reconnection, will try to reconnect every 30 
 sec
 esb_worker1  | [2016-08-23 11:58:51,044] ERROR -
 DataEndpointConnectionWorker Error while trying to connect to
 ssl://localhost:7712
 esb_worker1  | org.wso2.carbon.databridge.age
 nt.exception.DataEndpointSecurityException: Error while trying to
 connect to ssl://localhost:7712
 esb_worker1  | at org.wso2.carbon.databridge.age
 nt.endpoint.thrift.ThriftSecureClientPoolFactory.createClien
 t(ThriftSecureClientPoolFactory.java:61)
 esb_worker1  | at org.wso2.carbon.databridge.age
 nt.client.AbstractClientPoolFactory.makeObject(AbstractClien
 tPoolFactory.java:39)
 esb_worker1  | at org.apache.commons.pool.impl.G
 enericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
 esb_worker1  | at org.wso2.carbon.databridge.age
 nt.endpoint.DataEndpointConnectionWorker.connect(DataEndpoin
 tConnectionWorker.java:91)
 esb_worker1  | at org.wso2.carbon.databridge.age
 nt.endpoint.DataEndpointConnectionWorker.run(DataEndpointCon
 nectionWorker.java:42)
 esb_worker1  | at java.util.concurrent.Executors
 $RunnableAdapter.call(Executors.java:471)
 esb_worker1  | at java.util.concurrent.FutureTas
 k.run(FutureTask.java:262)
 esb_worker1  | at java.util.concurrent.ThreadPoo
 lExecutor.runWorker(ThreadPoolExecutor.java:1145)
 esb_worker1  | at java.util.concurrent.ThreadPoo
 lExecutor$Worker.run(ThreadPoolExecutor.java:615)
 esb_worker1  | at java.lang.Thread.run(Thread.java:745)
 esb_worker1  | Caused by: 
 org.apache.thrift.transport.TTransportException:
 Could not connect to localhost on port 7712
 esb_worker1  | at org.apache.thrift.transport.TS
 SLTransportFactory.createClient(TSSLTransportFactory.java:237)
 esb_worker1  | at org.apache.thrift.transport.TS
 SLTransportFactory.getClientSocket(TSSLTransportFactory.java:169)
 esb_worker1  | at org.wso2.carbon.databridge.age
 nt.endpoint.thrift.ThriftSecureClientPoolFactory.createClien
 t(ThriftSecureClientPoolFactory.java:56)
 esb_worker1  | ... 9 more
 esb_worker1  | Caused by: java.net.ConnectException: Connection
 refused
 esb_worker1  | at java.net.PlainSocketImpl.socketConnect(Native
 Method)
 esb_worker1  | at java.net.AbstractPlainSocketIm
 pl.doConnect(AbstractPlainSocketImpl.java:339)
 esb_worker1  | at java.net.AbstractPlainSocketIm
 

[Dev] [IS]SCIM API doesn't list internal roles

[Chamara Philips]

I have created a tenant and added an internal role using the carbon console
in IS 5.1.0. Then tried to list the roles using the SCIM API with command

*curl -v -k --user u...@tenant.com:12345 
https://localhost:9443/wso2/scim/Groups
*

Only the primary roles were listed.

I added an internal role with command

*curl -v -k --user u...@tenant.com:12345
 --data '{"displayName":
"Internal/engineer","members": []}' --header
"Content-Type:application/json" https://localhost:9443/wso2/scim/Groups
*

and listed the groups again.

This time all the primary roles and the internal role added with SCIM
command was listed. In carbon console the new role is listed under internal
roles. Doesn't SCIM API list all the internal roles added from carbon
console by default? Is there any settings to be set for this.


-- 
Hareendra Chamara Philips
*Software  Engineer*
Mobile : +94 (0) 767 184161
chama...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error connecting to esb-analutics

[Mohanadarshan Vivekanandalingam]

On Tue, Aug 23, 2016 at 7:32 PM, Supun Malinga  wrote:

> Hi,
>
> I already configured MessageFlowConfigurationPublisher.xml and
> MessageFlowStatisticsPublisher.xml files.
> tcp://esb-analytics:7612
>
> This is the http port I believe. But the error saying it cannot connect to
> the ssl port 7712 which is not in the configuration..
>
> analytics server runs on a different docker container.
> http : tcp://esb-analytics:7612
> https: tcp://esb-analytics:7712
>

@Supun, this is a Thrift communication which uses TCP underneath..

By default thrift port is 7611 and corresponding ssl thrift port is 7711
(7611+100), check the data-bridge-config.xml file which is in analytics
server config directory . Since we are shipping analytics products in
offset 1 then thrift port is 7612 and ssl port is 7712.. Here, ssl port
(7712) is used for initial authentication purposes of data publisher
afterwards it uses the thrift port (7612) for event publishing..

Thanks,
Mohan


>
>
>
> On Tue, Aug 23, 2016 at 7:28 PM, Chanaka Fernando 
> wrote:
>
>> Hi Supun,
>>
>> Where did you configure the hostname for the analytics server node?
>> Publisher configurations files are in the 
>> ESB_HOME/repository/deployment/server/eventpublishers/
>> directory. According to the error log, ESB is trying to connect to
>> localhost:7712 port. Are you starting the analytics server on the same node?
>>
>> On Tue, Aug 23, 2016 at 7:11 PM, Supun Malinga  wrote:
>>
>>> Hi,
>>>
>>> I configured a ESB cluster with analytics in docker. Followed the guide
>>> [1] and updated the hostname/port in event publisher artifacts. But still
>>> ESB gives and error when I try to anable statistics in a proxy service.
>>>
>>> Looks like some configuration is missing. However I searched in configs
>>> and find any place to change the hostname to the analytics server
>>> connection. Can someone point me to the correct config pls ?.
>>>
>>> esb_worker1  | [2016-08-23 11:58:51,041]  WARN - DataEndpointGroup
>>> No receiver is reachable at reconnection, will try to reconnect every 30 sec
>>> esb_worker1  | [2016-08-23 11:58:51,044] ERROR -
>>> DataEndpointConnectionWorker Error while trying to connect to
>>> ssl://localhost:7712
>>> esb_worker1  | org.wso2.carbon.databridge.age
>>> nt.exception.DataEndpointSecurityException: Error while trying to
>>> connect to ssl://localhost:7712
>>> esb_worker1  | at org.wso2.carbon.databridge.age
>>> nt.endpoint.thrift.ThriftSecureClientPoolFactory.createClien
>>> t(ThriftSecureClientPoolFactory.java:61)
>>> esb_worker1  | at org.wso2.carbon.databridge.age
>>> nt.client.AbstractClientPoolFactory.makeObject(AbstractClien
>>> tPoolFactory.java:39)
>>> esb_worker1  | at org.apache.commons.pool.impl.G
>>> enericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
>>> esb_worker1  | at org.wso2.carbon.databridge.age
>>> nt.endpoint.DataEndpointConnectionWorker.connect(DataEndpoin
>>> tConnectionWorker.java:91)
>>> esb_worker1  | at org.wso2.carbon.databridge.age
>>> nt.endpoint.DataEndpointConnectionWorker.run(DataEndpointCon
>>> nectionWorker.java:42)
>>> esb_worker1  | at java.util.concurrent.Executors
>>> $RunnableAdapter.call(Executors.java:471)
>>> esb_worker1  | at java.util.concurrent.FutureTas
>>> k.run(FutureTask.java:262)
>>> esb_worker1  | at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> esb_worker1  | at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> esb_worker1  | at java.lang.Thread.run(Thread.java:745)
>>> esb_worker1  | Caused by: 
>>> org.apache.thrift.transport.TTransportException:
>>> Could not connect to localhost on port 7712
>>> esb_worker1  | at org.apache.thrift.transport.TS
>>> SLTransportFactory.createClient(TSSLTransportFactory.java:237)
>>> esb_worker1  | at org.apache.thrift.transport.TS
>>> SLTransportFactory.getClientSocket(TSSLTransportFactory.java:169)
>>> esb_worker1  | at org.wso2.carbon.databridge.age
>>> nt.endpoint.thrift.ThriftSecureClientPoolFactory.createClien
>>> t(ThriftSecureClientPoolFactory.java:56)
>>> esb_worker1  | ... 9 more
>>> esb_worker1  | Caused by: java.net.ConnectException: Connection
>>> refused
>>> esb_worker1  | at java.net.PlainSocketImpl.socketConnect(Native
>>> Method)
>>> esb_worker1  | at java.net.AbstractPlainSocketIm
>>> pl.doConnect(AbstractPlainSocketImpl.java:339)
>>> esb_worker1  | at java.net.AbstractPlainSocketIm
>>> pl.connectToAddress(AbstractPlainSocketImpl.java:200)
>>> esb_worker1  | at java.net.AbstractPlainSocketIm
>>> pl.connect(AbstractPlainSocketImpl.java:182)
>>> esb_worker1  | at java.net.SocksSocketImpl.conne
>>> ct(SocksSocketImpl.java:392)
>>> esb_worker1  | at java.net.Socket.connect(Socket.java:579)
>>> esb_worker1  | at sun.security.ssl.SSLSocketImpl
>>> .connect(SSLSocketImpl.java:625)
>>> 

Re: [Dev] [ESB] Error connecting to esb-analutics

[Supun Malinga]

Hi,

I already configured MessageFlowConfigurationPublisher.xml and
MessageFlowStatisticsPublisher.xml files.
tcp://esb-analytics:7612

This is the http port I believe. But the error saying it cannot connect to
the ssl port 7712 which is not in the configuration..

analytics server runs on a different docker container.
http : tcp://esb-analytics:7612
https: tcp://esb-analytics:7712



On Tue, Aug 23, 2016 at 7:28 PM, Chanaka Fernando  wrote:

> Hi Supun,
>
> Where did you configure the hostname for the analytics server node?
> Publisher configurations files are in the ESB_HOME/repository/
> deployment/server/eventpublishers/ directory. According to the error log,
> ESB is trying to connect to localhost:7712 port. Are you starting the
> analytics server on the same node?
>
> On Tue, Aug 23, 2016 at 7:11 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> I configured a ESB cluster with analytics in docker. Followed the guide
>> [1] and updated the hostname/port in event publisher artifacts. But still
>> ESB gives and error when I try to anable statistics in a proxy service.
>>
>> Looks like some configuration is missing. However I searched in configs
>> and find any place to change the hostname to the analytics server
>> connection. Can someone point me to the correct config pls ?.
>>
>> esb_worker1  | [2016-08-23 11:58:51,041]  WARN - DataEndpointGroup No
>> receiver is reachable at reconnection, will try to reconnect every 30 sec
>> esb_worker1  | [2016-08-23 11:58:51,044] ERROR -
>> DataEndpointConnectionWorker Error while trying to connect to
>> ssl://localhost:7712
>> esb_worker1  | org.wso2.carbon.databridge.age
>> nt.exception.DataEndpointSecurityException: Error while trying to
>> connect to ssl://localhost:7712
>> esb_worker1  | at org.wso2.carbon.databridge.age
>> nt.endpoint.thrift.ThriftSecureClientPoolFactory.createClien
>> t(ThriftSecureClientPoolFactory.java:61)
>> esb_worker1  | at org.wso2.carbon.databridge.age
>> nt.client.AbstractClientPoolFactory.makeObject(AbstractClien
>> tPoolFactory.java:39)
>> esb_worker1  | at org.apache.commons.pool.impl.G
>> enericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
>> esb_worker1  | at org.wso2.carbon.databridge.age
>> nt.endpoint.DataEndpointConnectionWorker.connect(DataEndpoin
>> tConnectionWorker.java:91)
>> esb_worker1  | at org.wso2.carbon.databridge.age
>> nt.endpoint.DataEndpointConnectionWorker.run(DataEndpointCon
>> nectionWorker.java:42)
>> esb_worker1  | at java.util.concurrent.Executors
>> $RunnableAdapter.call(Executors.java:471)
>> esb_worker1  | at java.util.concurrent.FutureTas
>> k.run(FutureTask.java:262)
>> esb_worker1  | at java.util.concurrent.ThreadPoo
>> lExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> esb_worker1  | at java.util.concurrent.ThreadPoo
>> lExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> esb_worker1  | at java.lang.Thread.run(Thread.java:745)
>> esb_worker1  | Caused by: 
>> org.apache.thrift.transport.TTransportException:
>> Could not connect to localhost on port 7712
>> esb_worker1  | at org.apache.thrift.transport.TS
>> SLTransportFactory.createClient(TSSLTransportFactory.java:237)
>> esb_worker1  | at org.apache.thrift.transport.TS
>> SLTransportFactory.getClientSocket(TSSLTransportFactory.java:169)
>> esb_worker1  | at org.wso2.carbon.databridge.age
>> nt.endpoint.thrift.ThriftSecureClientPoolFactory.createClien
>> t(ThriftSecureClientPoolFactory.java:56)
>> esb_worker1  | ... 9 more
>> esb_worker1  | Caused by: java.net.ConnectException: Connection
>> refused
>> esb_worker1  | at java.net.PlainSocketImpl.socketConnect(Native
>> Method)
>> esb_worker1  | at java.net.AbstractPlainSocketIm
>> pl.doConnect(AbstractPlainSocketImpl.java:339)
>> esb_worker1  | at java.net.AbstractPlainSocketIm
>> pl.connectToAddress(AbstractPlainSocketImpl.java:200)
>> esb_worker1  | at java.net.AbstractPlainSocketIm
>> pl.connect(AbstractPlainSocketImpl.java:182)
>> esb_worker1  | at java.net.SocksSocketImpl.conne
>> ct(SocksSocketImpl.java:392)
>> esb_worker1  | at java.net.Socket.connect(Socket.java:579)
>> esb_worker1  | at sun.security.ssl.SSLSocketImpl
>> .connect(SSLSocketImpl.java:625)
>> esb_worker1  | at sun.security.ssl.SSLSocketImpl
>> .(SSLSocketImpl.java:413)
>> esb_worker1  | at sun.security.ssl.SSLSocketFact
>> oryImpl.createSocket(SSLSocketFactoryImpl.java:88)
>> esb_worker1  | at org.apache.thrift.transport.TS
>> SLTransportFactory.createClient(TSSLTransportFactory.java:233)
>> esb_worker1  | ... 11 more
>> esb_worker1  | [2016-08-23 11:58:51,046] ERROR -
>> DataEndpointConnectionWorker Error while trying to connect to the endpoint.
>> Cannot borrow client for ssl://localhost:7712
>> esb_worker1  | org.wso2.carbon.databridge.age
>> nt.exception.DataEndpointAuthenticationException: Cannot borrow client
>> for ssl://localhost:7712
>> 

Re: [Dev] [ESB] Error connecting to esb-analutics

[Chanaka Fernando]

Hi Supun,

Where did you configure the hostname for the analytics server node?
Publisher configurations files are in the
ESB_HOME/repository/deployment/server/eventpublishers/ directory. According
to the error log, ESB is trying to connect to localhost:7712 port. Are you
starting the analytics server on the same node?

On Tue, Aug 23, 2016 at 7:11 PM, Supun Malinga  wrote:

> Hi,
>
> I configured a ESB cluster with analytics in docker. Followed the guide
> [1] and updated the hostname/port in event publisher artifacts. But still
> ESB gives and error when I try to anable statistics in a proxy service.
>
> Looks like some configuration is missing. However I searched in configs
> and find any place to change the hostname to the analytics server
> connection. Can someone point me to the correct config pls ?.
>
> esb_worker1  | [2016-08-23 11:58:51,041]  WARN - DataEndpointGroup No
> receiver is reachable at reconnection, will try to reconnect every 30 sec
> esb_worker1  | [2016-08-23 11:58:51,044] ERROR -
> DataEndpointConnectionWorker Error while trying to connect to
> ssl://localhost:7712
> esb_worker1  | 
> org.wso2.carbon.databridge.agent.exception.DataEndpointSecurityException:
> Error while trying to connect to ssl://localhost:7712
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.thrift.
> ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.
> java:61)
> esb_worker1  | at org.wso2.carbon.databridge.agent.client.
> AbstractClientPoolFactory.makeObject(AbstractClientPoolFactory.java:39)
> esb_worker1  | at org.apache.commons.pool.impl.GenericKeyedObjectPool.
> borrowObject(GenericKeyedObjectPool.java:1212)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:91)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:42)
> esb_worker1  | at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:471)
> esb_worker1  | at java.util.concurrent.FutureTask.run(FutureTask.
> java:262)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:615)
> esb_worker1  | at java.lang.Thread.run(Thread.java:745)
> esb_worker1  | Caused by: org.apache.thrift.transport.TTransportException:
> Could not connect to localhost on port 7712
> esb_worker1  | at org.apache.thrift.transport.TSSLTransportFactory.
> createClient(TSSLTransportFactory.java:237)
> esb_worker1  | at org.apache.thrift.transport.TSSLTransportFactory.
> getClientSocket(TSSLTransportFactory.java:169)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.thrift.
> ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.
> java:56)
> esb_worker1  | ... 9 more
> esb_worker1  | Caused by: java.net.ConnectException: Connection refused
> esb_worker1  | at java.net.PlainSocketImpl.socketConnect(Native
> Method)
> esb_worker1  | at java.net.AbstractPlainSocketImpl.doConnect(
> AbstractPlainSocketImpl.java:339)
> esb_worker1  | at java.net.AbstractPlainSocketImpl.connectToAddress(
> AbstractPlainSocketImpl.java:200)
> esb_worker1  | at java.net.AbstractPlainSocketImpl.connect(
> AbstractPlainSocketImpl.java:182)
> esb_worker1  | at java.net.SocksSocketImpl.
> connect(SocksSocketImpl.java:392)
> esb_worker1  | at java.net.Socket.connect(Socket.java:579)
> esb_worker1  | at sun.security.ssl.SSLSocketImpl.connect(
> SSLSocketImpl.java:625)
> esb_worker1  | at sun.security.ssl.SSLSocketImpl.(
> SSLSocketImpl.java:413)
> esb_worker1  | at sun.security.ssl.SSLSocketFactoryImpl.createSocket(
> SSLSocketFactoryImpl.java:88)
> esb_worker1  | at org.apache.thrift.transport.TSSLTransportFactory.
> createClient(TSSLTransportFactory.java:233)
> esb_worker1  | ... 11 more
> esb_worker1  | [2016-08-23 11:58:51,046] ERROR -
> DataEndpointConnectionWorker Error while trying to connect to the endpoint.
> Cannot borrow client for ssl://localhost:7712
> esb_worker1  | org.wso2.carbon.databridge.agent.exception.
> DataEndpointAuthenticationException: Cannot borrow client for
> ssl://localhost:7712
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:99)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:42)
> esb_worker1  | at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:471)
> esb_worker1  | at java.util.concurrent.FutureTask.run(FutureTask.
> java:262)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> esb_worker1   

Re: [Dev] [ESB] Error connecting to esb-analutics

[Rajith Vitharana]

Hi Supun,

You only need to change file [1] and [2].

[1]
- 
/repository/deployment/server/eventpublishers/MessageFlowConfigurationPublisher.xml
[2]
- 
/repository/deployment/server/eventpublishers/MessageFlowStatisticsPublisher.xml

Thanks,

On 23 August 2016 at 19:11, Supun Malinga  wrote:

> Hi,
>
> I configured a ESB cluster with analytics in docker. Followed the guide
> [1] and updated the hostname/port in event publisher artifacts. But still
> ESB gives and error when I try to anable statistics in a proxy service.
>
> Looks like some configuration is missing. However I searched in configs
> and find any place to change the hostname to the analytics server
> connection. Can someone point me to the correct config pls ?.
>
> esb_worker1  | [2016-08-23 11:58:51,041]  WARN - DataEndpointGroup No
> receiver is reachable at reconnection, will try to reconnect every 30 sec
> esb_worker1  | [2016-08-23 11:58:51,044] ERROR -
> DataEndpointConnectionWorker Error while trying to connect to
> ssl://localhost:7712
> esb_worker1  | 
> org.wso2.carbon.databridge.agent.exception.DataEndpointSecurityException:
> Error while trying to connect to ssl://localhost:7712
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.thrift.
> ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.
> java:61)
> esb_worker1  | at org.wso2.carbon.databridge.agent.client.
> AbstractClientPoolFactory.makeObject(AbstractClientPoolFactory.java:39)
> esb_worker1  | at org.apache.commons.pool.impl.GenericKeyedObjectPool.
> borrowObject(GenericKeyedObjectPool.java:1212)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:91)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:42)
> esb_worker1  | at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:471)
> esb_worker1  | at java.util.concurrent.FutureTask.run(FutureTask.
> java:262)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:615)
> esb_worker1  | at java.lang.Thread.run(Thread.java:745)
> esb_worker1  | Caused by: org.apache.thrift.transport.TTransportException:
> Could not connect to localhost on port 7712
> esb_worker1  | at org.apache.thrift.transport.TSSLTransportFactory.
> createClient(TSSLTransportFactory.java:237)
> esb_worker1  | at org.apache.thrift.transport.TSSLTransportFactory.
> getClientSocket(TSSLTransportFactory.java:169)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.thrift.
> ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.
> java:56)
> esb_worker1  | ... 9 more
> esb_worker1  | Caused by: java.net.ConnectException: Connection refused
> esb_worker1  | at java.net.PlainSocketImpl.socketConnect(Native
> Method)
> esb_worker1  | at java.net.AbstractPlainSocketImpl.doConnect(
> AbstractPlainSocketImpl.java:339)
> esb_worker1  | at java.net.AbstractPlainSocketImpl.connectToAddress(
> AbstractPlainSocketImpl.java:200)
> esb_worker1  | at java.net.AbstractPlainSocketImpl.connect(
> AbstractPlainSocketImpl.java:182)
> esb_worker1  | at java.net.SocksSocketImpl.
> connect(SocksSocketImpl.java:392)
> esb_worker1  | at java.net.Socket.connect(Socket.java:579)
> esb_worker1  | at sun.security.ssl.SSLSocketImpl.connect(
> SSLSocketImpl.java:625)
> esb_worker1  | at sun.security.ssl.SSLSocketImpl.(
> SSLSocketImpl.java:413)
> esb_worker1  | at sun.security.ssl.SSLSocketFactoryImpl.createSocket(
> SSLSocketFactoryImpl.java:88)
> esb_worker1  | at org.apache.thrift.transport.TSSLTransportFactory.
> createClient(TSSLTransportFactory.java:233)
> esb_worker1  | ... 11 more
> esb_worker1  | [2016-08-23 11:58:51,046] ERROR -
> DataEndpointConnectionWorker Error while trying to connect to the endpoint.
> Cannot borrow client for ssl://localhost:7712
> esb_worker1  | org.wso2.carbon.databridge.agent.exception.
> DataEndpointAuthenticationException: Cannot borrow client for
> ssl://localhost:7712
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:99)
> esb_worker1  | at org.wso2.carbon.databridge.agent.endpoint.
> DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:42)
> esb_worker1  | at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:471)
> esb_worker1  | at java.util.concurrent.FutureTask.run(FutureTask.
> java:262)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> esb_worker1  | at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> 

[Dev] [ESB] Error connecting to esb-analutics

[Supun Malinga]

Hi,

I configured a ESB cluster with analytics in docker. Followed the guide [1]
and updated the hostname/port in event publisher artifacts. But still ESB
gives and error when I try to anable statistics in a proxy service.

Looks like some configuration is missing. However I searched in configs and
find any place to change the hostname to the analytics server connection.
Can someone point me to the correct config pls ?.

esb_worker1  | [2016-08-23 11:58:51,041]  WARN - DataEndpointGroup No
receiver is reachable at reconnection, will try to reconnect every 30 sec
esb_worker1  | [2016-08-23 11:58:51,044] ERROR -
DataEndpointConnectionWorker Error while trying to connect to
ssl://localhost:7712
esb_worker1  |
org.wso2.carbon.databridge.agent.exception.DataEndpointSecurityException:
Error while trying to connect to ssl://localhost:7712
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.thrift.ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.java:61)
esb_worker1  | at
org.wso2.carbon.databridge.agent.client.AbstractClientPoolFactory.makeObject(AbstractClientPoolFactory.java:39)
esb_worker1  | at
org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:91)
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:42)
esb_worker1  | at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
esb_worker1  | at
java.util.concurrent.FutureTask.run(FutureTask.java:262)
esb_worker1  | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
esb_worker1  | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
esb_worker1  | at java.lang.Thread.run(Thread.java:745)
esb_worker1  | Caused by:
org.apache.thrift.transport.TTransportException: Could not connect to
localhost on port 7712
esb_worker1  | at
org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:237)
esb_worker1  | at
org.apache.thrift.transport.TSSLTransportFactory.getClientSocket(TSSLTransportFactory.java:169)
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.thrift.ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.java:56)
esb_worker1  | ... 9 more
esb_worker1  | Caused by: java.net.ConnectException: Connection refused
esb_worker1  | at java.net.PlainSocketImpl.socketConnect(Native Method)
esb_worker1  | at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
esb_worker1  | at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
esb_worker1  | at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
esb_worker1  | at
java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
esb_worker1  | at java.net.Socket.connect(Socket.java:579)
esb_worker1  | at
sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
esb_worker1  | at
sun.security.ssl.SSLSocketImpl.(SSLSocketImpl.java:413)
esb_worker1  | at
sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88)
esb_worker1  | at
org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:233)
esb_worker1  | ... 11 more
esb_worker1  | [2016-08-23 11:58:51,046] ERROR -
DataEndpointConnectionWorker Error while trying to connect to the endpoint.
Cannot borrow client for ssl://localhost:7712
esb_worker1  |
org.wso2.carbon.databridge.agent.exception.DataEndpointAuthenticationException:
Cannot borrow client for ssl://localhost:7712
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:99)
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:42)
esb_worker1  | at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
esb_worker1  | at
java.util.concurrent.FutureTask.run(FutureTask.java:262)
esb_worker1  | at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
esb_worker1  | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
esb_worker1  | at java.lang.Thread.run(Thread.java:745)
esb_worker1  | Caused by:
org.wso2.carbon.databridge.agent.exception.DataEndpointSecurityException:
Error while trying to connect to ssl://localhost:7712
esb_worker1  | at
org.wso2.carbon.databridge.agent.endpoint.thrift.ThriftSecureClientPoolFactory.createClient(ThriftSecureClientPoolFactory.java:61)
esb_worker1  | at

Re: [Dev] [Mesos artifacts] Use Docker --dns and --dns-search for hostname DNS resolution

[Isuru Haththotuwa]

+1 to the idea. Using service ports becomes unmanageable when there are
multiple products with lots of ports exposed.

AFAIU Udara has a point as well. The routing inside mesos-marathon
framework will work seamlessly with this. However to access it from the
outside (browser, etc.), we would need to add the DNS server we are running
in mesos as a nameserver in the local machine, or else simply add a
/etc/hosts entry.

On Tue, Aug 23, 2016 at 10:28 AM, Akila Ravihansa Perera  wrote:

> Hi Udara,
>
> My idea was to map all wso2 server hostnames to Marathon-LB, not to other
> containers directly. We should route all traffic via Marathon-LB.
> We can always use "add-host" properties to add entries to /etc/hosts but
> that looks like a hack. Using DNS is a much cleaner and flexible approach.
> We can always run DNS server as another container [1].
>
> [1] https://github.com/skynetservices/skydns
>
> Thanks.
>
> On Tue, Aug 23, 2016 at 10:18 AM, Udara Liyanage  wrote:
>
>> Hi,
>>
>> Container to contianer communication can be done by this as long as we
>> run a dns server.
>> However when users/browser wants to access a service running on a
>> container (say ESB maagement console) don't they have to come via marathon
>> lb? Or else do the they have to add our dns server to their resolve.conf ?
>>
>> How about load balancing features such as sticky sessions and round
>> robbing load balancing. Round robbing load balancing can be done using DNS
>> server itself, but not sure about sticky session.
>>
>>
>> On Tue, Aug 23, 2016 at 10:07 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Currently we are using Marathon-LB hostname and service ports in product
>>> configuration when deploying on DC/OS (Apache Mesos). We can set the
>>> --dns-search and --dns properties and set a DOMAIN and DNS server in
>>> /etc/resolve.conf to resolve hostnames which are not found in /etc/hosts
>>> [1].
>>>
>>> This is a much cleaner approach than using Marathon-LB hostname and
>>> service ports. WDYT?
>>>
>>>
>>> [1] https://docs.docker.com/v1.7/articles/networking/#dns
>>>
>>> Thanks.
>>>
>>> --
>>> Akila Ravihansa Perera
>>> WSO2 Inc.;  http://wso2.com/
>>>
>>> Blog: http://ravihansa3000.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> Blog: http://udaraliyanage.wordpress.com
>>
>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

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

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Kasun Bandara]

Hi Biruntha,

This issue has been already fixed in the public branch [1]. You can verify
your use-case with the latest pack available in [2]

Thanks,
Kasun.

[1]
https://github.com/wso2-extensions/identity-inbound-auth-saml/blob/master/components/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderServlet.java

[2]
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/is/wso2is/5.2.0-SNAPSHOT/

Thanks,
Kasun

On Tue, Aug 23, 2016 at 5:43 PM, Kasun Bandara  wrote:

> Hi Biruntha,
>
> Thanks for fixing the issue. Can you please send the relevant PR to [1]
> extension. We don't use the carbon-identity repository now.
>
> Thanks,
> Kasun.
>
> [1] https://github.com/wso2-extensions/identity-inbound-
> auth-saml/blob/master/components/org.wso2.carbon.
> identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/
> SAMLSSOProviderServlet.java
>
> On Tue, Aug 23, 2016 at 4:48 PM, Johann Nallathamby 
> wrote:
>
>>
>>
>> On Tue, Aug 23, 2016 at 4:14 PM, Biruntha Gnaneswaran 
>> wrote:
>>
>>> Hi,
>>>
>>> I created jira [1] and fixed in [2].
>>>
>>> @ IS team please verify and merge.
>>>
>>> [1] - https://wso2.org/jira/browse/IDENTITY-5027
>>>
>>> [2] - https://github.com/wso2/carbon-identity/pull/1748
>>>
>>> Thanks,
>>>
>>> Biruntha
>>>
>>> Associate Software Engineer
>>> WSO2
>>> Email : birun...@wso2.com
>>> Linkedin : https://lk.linkedin.com/in/biruntha
>>> Mobile : +94773718986
>>>
>>> On Tue, Aug 23, 2016 at 6:05 AM, Malaka Silva  wrote:
>>>
 Hi Biruntha,

 Good investigation on this matter. However we are not sure the impact
 of this change. Can you create a jira [1] and add the PR so that IS team
 can verify this in coming releases?

 [1] https://wso2.org/jira/browse/IDENTITY

 On Mon, Aug 22, 2016 at 6:04 PM, Biruntha Gnaneswaran <
 birun...@wso2.com> wrote:

> Hi All,
>
> While posting a form from Mepin Authenticator to Authentication
> endpoint, [1] will be executed. So it goes to [2]. From that method, it
> only support for url redirecting not support for form posting. So, I
> replace the logic [3] by [4]. Now it is working fine .So, To support post
> request in authentication endpoint, we need to modify sso-saml module.
>
> [1] - https://github.com/wso2/carbon-identity/blob/master/componen
> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
> vlet.java#L157-#L161
>
> [2] - https://github.com/wso2/carbon-identity/blob/master/componen
> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
> vlet.java#L980
>
> [3] - https://github.com/wso2/carbon-identity/blob/master/componen
> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
> vlet.java#L992
>
> [4] - https://github.com/wso2/carbon-identity/blob/master/componen
> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
> vlet.java#L1031-#L1035
>
>
> Thanks,
>
> Biruntha
>
> Associate Software Engineer
> WSO2
> Email : birun...@wso2.com
> Linkedin : https://lk.linkedin.com/in/biruntha
> Mobile : +94773718986
>
> On Fri, Aug 12, 2016 at 10:18 PM, Biruntha Gnaneswaran <
> birun...@wso2.com> wrote:
>
>> Hi All,
>>
>>
>> To solve the issue in $subject, i tried to post a html form from
>> Authenticator to mepin.jsp using [1]. But still i couldn't solve that
>> issue. It's again redirected to [2].
>> Can anyone help me to solve this issue?
>>
>> [1]
>>
>> response.setContentType(*"text/html"*);java.io.PrintWriter out = 
>> response.getWriter();
>> out.println(*""*);out.println(*""*);out.println(*">  name=**\"**loginform**\"* *method=**\"**post**\"* 
>> *action=**\"**/mepinauthenticationendpoint/mepin.jsp**\"**>"*);out.println(*">  type=**\"**hidden**\"* *id=**\"**param1**\"* *name=**\"**param1**\"* 
>> *value=**\"**"*+param1+*"**\"**/>"*);out.println(*"> type=**\"**hidden**\"* *id=**\"**param2**\"* *name=**\"**param2**\"* 
>> *value=**\"**"*+param2+*"**\"**/>"*);out.println(*""*);
>>
>> [2] https://localhost:9443/samlsso
>>
>> Thanks,
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran <
>> birun...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> In Mepin authenticator, some URL parameters are send to Mepin UI

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Kasun Bandara]

Hi Biruntha,

Thanks for fixing the issue. Can you please send the relevant PR to [1]
extension. We don't use the carbon-identity repository now.

Thanks,
Kasun.

[1]
https://github.com/wso2-extensions/identity-inbound-auth-saml/blob/master/components/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderServlet.java

On Tue, Aug 23, 2016 at 4:48 PM, Johann Nallathamby  wrote:

>
>
> On Tue, Aug 23, 2016 at 4:14 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi,
>>
>> I created jira [1] and fixed in [2].
>>
>> @ IS team please verify and merge.
>>
>> [1] - https://wso2.org/jira/browse/IDENTITY-5027
>>
>> [2] - https://github.com/wso2/carbon-identity/pull/1748
>>
>> Thanks,
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Tue, Aug 23, 2016 at 6:05 AM, Malaka Silva  wrote:
>>
>>> Hi Biruntha,
>>>
>>> Good investigation on this matter. However we are not sure the impact of
>>> this change. Can you create a jira [1] and add the PR so that IS team can
>>> verify this in coming releases?
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY
>>>
>>> On Mon, Aug 22, 2016 at 6:04 PM, Biruntha Gnaneswaran >> > wrote:
>>>
 Hi All,

 While posting a form from Mepin Authenticator to Authentication
 endpoint, [1] will be executed. So it goes to [2]. From that method, it
 only support for url redirecting not support for form posting. So, I
 replace the logic [3] by [4]. Now it is working fine .So, To support post
 request in authentication endpoint, we need to modify sso-saml module.

 [1] - https://github.com/wso2/carbon-identity/blob/master/componen
 ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
 org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
 vlet.java#L157-#L161

 [2] - https://github.com/wso2/carbon-identity/blob/master/componen
 ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
 org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
 vlet.java#L980

 [3] - https://github.com/wso2/carbon-identity/blob/master/componen
 ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
 org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
 vlet.java#L992

 [4] - https://github.com/wso2/carbon-identity/blob/master/componen
 ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
 org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSer
 vlet.java#L1031-#L1035


 Thanks,

 Biruntha

 Associate Software Engineer
 WSO2
 Email : birun...@wso2.com
 Linkedin : https://lk.linkedin.com/in/biruntha
 Mobile : +94773718986

 On Fri, Aug 12, 2016 at 10:18 PM, Biruntha Gnaneswaran <
 birun...@wso2.com> wrote:

> Hi All,
>
>
> To solve the issue in $subject, i tried to post a html form from
> Authenticator to mepin.jsp using [1]. But still i couldn't solve that
> issue. It's again redirected to [2].
> Can anyone help me to solve this issue?
>
> [1]
>
> response.setContentType(*"text/html"*);java.io.PrintWriter out = 
> response.getWriter();
> out.println(*""*);out.println(*""*);out.println(*"  name=**\"**loginform**\"* *method=**\"**post**\"* 
> *action=**\"**/mepinauthenticationendpoint/mepin.jsp**\"**>"*);out.println(*"  type=**\"**hidden**\"* *id=**\"**param1**\"* *name=**\"**param1**\"* 
> *value=**\"**"*+param1+*"**\"**/>"*);out.println(*" type=**\"**hidden**\"* *id=**\"**param2**\"* *name=**\"**param2**\"* 
> *value=**\"**"*+param2+*"**\"**/>"*);out.println(*""*);
>
> [2] https://localhost:9443/samlsso
>
> Thanks,
>
> Biruntha
>
> Associate Software Engineer
> WSO2
> Email : birun...@wso2.com
> Linkedin : https://lk.linkedin.com/in/biruntha
> Mobile : +94773718986
>
> On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran <
> birun...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> In Mepin authenticator, some URL parameters are send to Mepin UI page
>> using GET method [1]. When I try to send these parameters via POST method
>> using HttpURLConnection class [2], it redirects to [3] not to the
>> actual Mepin UI page. While I try, I got the following Log .
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler}
>> - In authentication flow
>>
>> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
>> ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
>> - Executing the Step Based Authentication...
>>
>> [2016-07-29 23:30:00,903] DEBUG 

Re: [Dev] [GSOC 16] Initial Project Progress

[Isuru Haththotuwa]

Hi Osura,

On Tue, Aug 23, 2016 at 2:48 PM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Issue #6 was fixed.
>
great! thanks.

>
> Thanks,
>
> On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> I'm fixing issue #6 and  almost done. I will fix other issues soon after
>> finishing #6.
>>
>> Thanks,
>>
>> On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Several issues reported against the membership scheme is still in open
>>> state [1]. Other than issue 6, all others are straightforward to fix.
>>> Please fix those asap.
>>>
>>> [1]. https://github.com/osuran/azure-membership-scheme/issues
>>>
>>> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Mentors,

 current status: I'm trying to implement the deploy.sh by trying to
 invoke puppet to install product configuration at the startup of a puppet
 installed VM. But still couldn't come up with a presentable outcome.

 Thanks,

 On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
 wrote:

> Thank you
>
>
> On Thursday, August 18, 2016, Imesh Gunaratne  wrote:
>
>>
>>
>> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Imesh,
>>>
>>> Yes now I understand that creating VM images for each product
>>> profile will not going to work out.
>>>
>>> Can you please give me a step by step guideline on what I should do
>>> to achieve this?
>>>
>>
>> ​Please refer [1] and [2].
>>
>> [1] https://github.com/wso2/puppet-modules
>> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
>> mentation​
>>
>>
>> ​Thanks​
>>
>> .
>>>  Thank you,
>>>
>>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
>>> wrote:
>>>


 On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
 wrote:
>
>
> ​There are many spelling mistakes on this file [2], please review
> it again.
>

 ​Correction: s/on this file/in this file/g

 Thanks
 ​


> Overall I see very less attention to detail in this repository and
> the membership scheme implementation.
>
>
>> There I mentioned the things that should be kept in mind while
>> configuring wso2 AS and did not go in to detail on hot to configure 
>> as it
>> can be found in the wso2 documentation. Would that be okay?
>>
>
> ​I don't think this is helpful. Without having detailed steps
> users might not be able to do a complete deployment.
>
> Few questions:
>
>- How do you create a distributed deployment​
>
>​of AS ​or any other product (say for an example WSO2 API-M)
>with this approach? As I explained earlier creating a VM image per 
> product
>profile is an unnecessary overhead (time consumption, disk space 
> needed,
>maintenance, etc).
>
>- ​What would be the approach of applying​
> a patch or do
>​ing​
>a configuration change in a such deployment?
>
> ​IMO it is really important to understand the concepts well and
> solve problems with the most efficient manner. Otherwise the outcome 
> of
> this project might not be usable.
>
> [2] https://github.com/osuran/azure-artifacts/issues/2
>
> Thanks
>
>
>> user do not need to change anything in template.json, so should I
>> explain the parameters in that too?
>>
>> in the paramters.json, except for the vm_image parameter, all of
>> the parameters are just for the naming of the elements that you find 
>> in a
>> VM, for an example, the name of the network interface. Therefore I 
>> have
>> given instructions on how to set the vm_image parameter.
>>
>> current progress: The script which was generated by Azure does
>> not have the capability to add a custom VM image. I modified it so 
>> that now
>> it has that capability. Normally when you login to azure from CLI, 
>> it needs
>> web interaction to authenticate. I modified deploy.sh in a way that 
>> it
>> authenticates the user without web interaction, this will be useful 
>> if we
>> run deploy.sh in a minimal version of linux.
>>
>> currently I'm working on adding deployment patterns to deploy.sh
>> and undeploy.sh
>>
>>
>> [1] 

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Johann Nallathamby]

On Tue, Aug 23, 2016 at 4:14 PM, Biruntha Gnaneswaran 
wrote:

> Hi,
>
> I created jira [1] and fixed in [2].
>
> @ IS team please verify and merge.
>
> [1] - https://wso2.org/jira/browse/IDENTITY-5027
>
> [2] - https://github.com/wso2/carbon-identity/pull/1748
>
> Thanks,
>
> Biruntha
>
> Associate Software Engineer
> WSO2
> Email : birun...@wso2.com
> Linkedin : https://lk.linkedin.com/in/biruntha
> Mobile : +94773718986
>
> On Tue, Aug 23, 2016 at 6:05 AM, Malaka Silva  wrote:
>
>> Hi Biruntha,
>>
>> Good investigation on this matter. However we are not sure the impact of
>> this change. Can you create a jira [1] and add the PR so that IS team can
>> verify this in coming releases?
>>
>> [1] https://wso2.org/jira/browse/IDENTITY
>>
>> On Mon, Aug 22, 2016 at 6:04 PM, Biruntha Gnaneswaran 
>> wrote:
>>
>>> Hi All,
>>>
>>> While posting a form from Mepin Authenticator to Authentication
>>> endpoint, [1] will be executed. So it goes to [2]. From that method, it
>>> only support for url redirecting not support for form posting. So, I
>>> replace the logic [3] by [4]. Now it is working fine .So, To support post
>>> request in authentication endpoint, we need to modify sso-saml module.
>>>
>>> [1] - https://github.com/wso2/carbon-identity/blob/master/componen
>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSe
>>> rvlet.java#L157-#L161
>>>
>>> [2] - https://github.com/wso2/carbon-identity/blob/master/componen
>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSe
>>> rvlet.java#L980
>>>
>>> [3] - https://github.com/wso2/carbon-identity/blob/master/componen
>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSe
>>> rvlet.java#L992
>>>
>>> [4] - https://github.com/wso2/carbon-identity/blob/master/componen
>>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/
>>> org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProviderSe
>>> rvlet.java#L1031-#L1035
>>>
>>>
>>> Thanks,
>>>
>>> Biruntha
>>>
>>> Associate Software Engineer
>>> WSO2
>>> Email : birun...@wso2.com
>>> Linkedin : https://lk.linkedin.com/in/biruntha
>>> Mobile : +94773718986
>>>
>>> On Fri, Aug 12, 2016 at 10:18 PM, Biruntha Gnaneswaran <
>>> birun...@wso2.com> wrote:
>>>
 Hi All,


 To solve the issue in $subject, i tried to post a html form from
 Authenticator to mepin.jsp using [1]. But still i couldn't solve that
 issue. It's again redirected to [2].
 Can anyone help me to solve this issue?

 [1]

 response.setContentType(*"text/html"*);java.io.PrintWriter out = 
 response.getWriter();
 out.println(*""*);out.println(*""*);out.println(*">>>  name=**\"**loginform**\"* *method=**\"**post**\"* 
 *action=**\"**/mepinauthenticationendpoint/mepin.jsp**\"**>"*);out.println(*">>>  type=**\"**hidden**\"* *id=**\"**param1**\"* *name=**\"**param1**\"* 
 *value=**\"**"*+param1+*"**\"**/>"*);out.println(*">>> type=**\"**hidden**\"* *id=**\"**param2**\"* *name=**\"**param2**\"* 
 *value=**\"**"*+param2+*"**\"**/>"*);out.println(*""*);

 [2] https://localhost:9443/samlsso

 Thanks,

 Biruntha

 Associate Software Engineer
 WSO2
 Email : birun...@wso2.com
 Linkedin : https://lk.linkedin.com/in/biruntha
 Mobile : +94773718986

 On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran <
 birun...@wso2.com> wrote:

> Hi Devs,
>
> In Mepin authenticator, some URL parameters are send to Mepin UI page
> using GET method [1]. When I try to send these parameters via POST method
> using HttpURLConnection class [2], it redirects to [3] not to the
> actual Mepin UI page. While I try, I got the following Log .
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
> ication.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler}
> - In authentication flow
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
> ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
> - Executing the Step Based Authentication...
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
> ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
> - Starting Step: 1
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
> ication.authentication.framework.util.FrameworkUtils} - Finding
> already authenticated IdPs of the Step
>
> [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
> ication.authentication.framework.handler.step.impl.DefaultStepHandler}
> - Receive a response from the external party
>
> [2016-07-29 23:30:00,903] DEBUG 

Re: [Dev] Possible bottleneck in the updatePermissionTree() method of user.core.authorization.PermissionTree class

[Jayanga Kaushalya]

Hi Chalitha,

Thanks for checking up on this. It's great if you can send a PR for
carbon-kernel 4.4.x branch on this.

Thanks!

*Jayanga Kaushalya*
Software Engineer
Mobile: +94777860160
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware

On Fri, Jun 24, 2016 at 2:00 PM, Chalitha Kulathunga 
wrote:

> + IS team members
>
> On Fri, Jun 24, 2016 at 1:37 PM, Chalitha Kulathunga 
> wrote:
>
>> Hi kernal team,
>>
>> When multiple threads access updatePermissionTree() method for the first
>> time, they all will end up in the else block. Those threads will call the
>> updatePermissionTreeFromDB() method one by one. Seems like this is creating
>> a bottleneck in the execution flow.
>>
>> void updatePermissionTree() throws UserStoreException {
>> PermissionTreeCacheKey cacheKey = new 
>> PermissionTreeCacheKey(cacheIdentifier, tenantId);
>> GhostResource cacheEntry = (GhostResource) 
>> permissionCache.get(cacheKey);
>> if (permissionCache.containsKey(cacheKey)) {
>> if (cacheEntry.getResource() == null) {
>> synchronized (this) {
>> cacheEntry = (GhostResource) 
>> permissionCache.get(cacheKey);
>> if (cacheEntry.getResource() == null) {
>> updatePermissionTreeFromDB();
>> cacheEntry.setResource(root);
>> if (log.isDebugEnabled()) {
>> log.debug("Set resource to true");
>> }
>> }
>> }
>> }
>> } else {
>> synchronized (this) {
>> updatePermissionTreeFromDB();
>> cacheKey = new PermissionTreeCacheKey(cacheIdentifier, tenantId);
>> cacheEntry = new GhostResource(root);
>> permissionCache.put(cacheKey, cacheEntry);
>> if (log.isDebugEnabled()) {
>> log.debug("Loaded from database");
>> }
>> }
>> }
>> }
>>
>>
>> Can this be modified as follows to avoid the above mentioned issue?
>>
>> void updatePermissionTree() throws UserStoreException {
>> PermissionTreeCacheKey cacheKey = new 
>> PermissionTreeCacheKey(cacheIdentifier, tenantId);
>> GhostResource cacheEntry = (GhostResource) 
>> permissionCache.get(cacheKey);
>> if (cacheEntry != null && cacheEntry.getResource() != null) {
>> return;
>> }
>> synchronized (this) {
>> if (cacheEntry != null && cacheEntry.getResource() != null) {
>> return;
>> }
>> if (cacheEntry == null) {
>> cacheEntry = new GhostResource(null);
>> permissionCache.put(cacheKey, cacheEntry);
>> }
>> if (cacheEntry.getResource() == null) {
>> updatePermissionTreeFromDB();
>> cacheEntry.setResource(root);
>> if (log.isDebugEnabled()) {
>> log.debug("Resource Loaded from database for cachekey: " + 
>> cacheEntry);
>> }
>> }
>> }
>> }
>>
>>
>> Thanks,
>> Chalitha
>>
>>
>> --
>> *Chalitha Sanyuja Kulathunga*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
>>
>
>
>
> --
> *Chalitha Sanyuja Kulathunga*
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: chalit...@wso2.com cell: +94 77 5927581 <%2B94%2077%207779495>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [Mepin Authenticator] Problem while sending URL parameters using POST method

[Biruntha Gnaneswaran]

Hi,

I created jira [1] and fixed in [2].

@ IS team please verify and merge.

[1] - https://wso2.org/jira/browse/IDENTITY-5027

[2] - https://github.com/wso2/carbon-identity/pull/1748

Thanks,

Biruntha

Associate Software Engineer
WSO2
Email : birun...@wso2.com
Linkedin : https://lk.linkedin.com/in/biruntha
Mobile : +94773718986

On Tue, Aug 23, 2016 at 6:05 AM, Malaka Silva  wrote:

> Hi Biruntha,
>
> Good investigation on this matter. However we are not sure the impact of
> this change. Can you create a jira [1] and add the PR so that IS team can
> verify this in coming releases?
>
> [1] https://wso2.org/jira/browse/IDENTITY
>
> On Mon, Aug 22, 2016 at 6:04 PM, Biruntha Gnaneswaran 
> wrote:
>
>> Hi All,
>>
>> While posting a form from Mepin Authenticator to Authentication endpoint,
>> [1] will be executed. So it goes to [2]. From that method, it only support
>> for url redirecting not support for form posting. So, I replace the logic
>> [3] by [4]. Now it is working fine .So, To support post request in
>> authentication endpoint, we need to modify sso-saml module.
>>
>> [1] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L157-#L161
>>
>> [2] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L980
>>
>> [3] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L992
>>
>> [4] - https://github.com/wso2/carbon-identity/blob/master/componen
>> ts/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/
>> java/org/wso2/carbon/identity/sso/saml/servlet/SAMLSSOProvid
>> erServlet.java#L1031-#L1035
>>
>>
>> Thanks,
>>
>> Biruntha
>>
>> Associate Software Engineer
>> WSO2
>> Email : birun...@wso2.com
>> Linkedin : https://lk.linkedin.com/in/biruntha
>> Mobile : +94773718986
>>
>> On Fri, Aug 12, 2016 at 10:18 PM, Biruntha Gnaneswaran > > wrote:
>>
>>> Hi All,
>>>
>>>
>>> To solve the issue in $subject, i tried to post a html form from
>>> Authenticator to mepin.jsp using [1]. But still i couldn't solve that
>>> issue. It's again redirected to [2].
>>> Can anyone help me to solve this issue?
>>>
>>> [1]
>>>
>>> response.setContentType(*"text/html"*);java.io.PrintWriter out = 
>>> response.getWriter();
>>> out.println(*""*);out.println(*""*);out.println(*">>  name=**\"**loginform**\"* *method=**\"**post**\"* 
>>> *action=**\"**/mepinauthenticationendpoint/mepin.jsp**\"**>"*);out.println(*">>  type=**\"**hidden**\"* *id=**\"**param1**\"* *name=**\"**param1**\"* 
>>> *value=**\"**"*+param1+*"**\"**/>"*);out.println(*">> type=**\"**hidden**\"* *id=**\"**param2**\"* *name=**\"**param2**\"* 
>>> *value=**\"**"*+param2+*"**\"**/>"*);out.println(*""*);
>>>
>>> [2] https://localhost:9443/samlsso
>>>
>>> Thanks,
>>>
>>> Biruntha
>>>
>>> Associate Software Engineer
>>> WSO2
>>> Email : birun...@wso2.com
>>> Linkedin : https://lk.linkedin.com/in/biruntha
>>> Mobile : +94773718986
>>>
>>> On Fri, Jul 29, 2016 at 11:46 PM, Biruntha Gnaneswaran <
>>> birun...@wso2.com> wrote:
>>>
 Hi Devs,

 In Mepin authenticator, some URL parameters are send to Mepin UI page
 using GET method [1]. When I try to send these parameters via POST method
 using HttpURLConnection class [2], it redirects to [3] not to the
 actual Mepin UI page. While I try, I got the following Log .

 [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
 ication.authentication.framework.handler.request.impl.DefaultAuthenticationRequestHandler}
 - In authentication flow

 [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
 ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
 - Executing the Step Based Authentication...

 [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
 ication.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
 - Starting Step: 1

 [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
 ication.authentication.framework.util.FrameworkUtils} - Finding
 already authenticated IdPs of the Step

 [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
 ication.authentication.framework.handler.step.impl.DefaultStepHandler}
 - Receive a response from the external party

 [2016-07-29 23:30:00,903] DEBUG {org.wso2.carbon.identity.appl
 ication.authentication.framework.handler.step.impl.DefaultStepHandler}
 - BasicAuthenticator can handle the request.

 [2016-07-29 23:30:00,929] DEBUG {org.wso2.carbon.identity.appl

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Manujith Pallewatte]

Thank you Omindu!
I'll check back for the review date and time

Sanjeewa, the API definition can be found at [1] and it also has a swagger
definition available at the url [2]  once the service is running. So a
client can use that.

Thank You
Manujith

[1] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide
[2] */Decision/api/swagger.json*

On Tue, Aug 23, 2016 at 3:24 PM, Sanjeewa Malalgoda 
wrote:

> First sorry about asking this in last minute. We can we find API
> definition for this API?
> Have we documented somewhere with all requests paths, payloads responses
> etc? I
>
> Thanks,
> sanjeewa.
>
> On Tue, Aug 23, 2016 at 3:05 PM, Omindu Rathnaweera 
> wrote:
>
>> Great work Manujith! Let's schedule a demo and a code review within next
>> week.
>>
>> Regards,
>> Omindu.
>>
>> On Tue, Aug 23, 2016 at 2:27 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Coming to the conclusion of the project, here's the progress so far
>>> The project description can be seen at [1]. The goal was to provide
>>> RESTful access to the PDP of the IS
>>>
>>> Progress
>>> 
>>> 1) REST implementation done using Apache CXF framework
>>> 2) JSON compatibility added using Jackson jax-rs
>>> 3) REST service supports consuming and producing JSON and XML
>>> 4) REST API fully compliant with the XACML 3.0 REST profile [2] and
>>> XACML 3.0 JSON profile [3]
>>> 5) Using swagger to populate service method
>>> 6) Integration tests and documentation done
>>>
>>> Deliverables
>>> -
>>> 1) REST implementation for the IS PDP [4]
>>> 2) Developer[5] and User[6] documentation
>>> 3) Integration tests
>>>
>>> In addition the following blog post covers the progress in detail [7]
>>> and it was submitted as the work product submission link for student's
>>> final evaluation form.
>>>
>>> Finally i would like to thank all my mentors for the immense support and
>>> the community for their prompt assistance.
>>>
>>> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for
>>> +2016#ProjectProposalsfor2016-Proposal22:[IS]RESTfulFineGrai
>>> nedAuthorization-as-a-Service(AZaaS)
>>> [2] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
>>> /xacml-rest-v1.0-csprd03.html
>>> [3] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa
>>> cml-json-http-v1.0.html
>>> [4] https://github.com/ManZzup/identity-framework/tree/maste
>>> r/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint
>>> [5] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc/
>>> [6] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide
>>> [7] http://manzzup.blogspot.com/2016/08/gsoc-2016-rest-imple
>>> mentation-for-wso2.html
>>>
>>> Thank You
>>> Manujith
>>>
>>> On Sun, Aug 14, 2016 at 1:39 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi Pushpalanka,

 Thank you for the comments

 1) I added a list of required changes at [1]

 2) The blog post will be link for now from the github readme, since I'm
 adding additional blog posts to support the content of the above post
 (mostly in depth implementation details for source), I thought of keeping
 the blogpost and linking from the repo. But I will have a markdown version
 of the blogpost as well.

 On other updates,

 1) Swagger is now implemented
 2) Integration tests are done using Jetty
 3) Added the Jira ticket at [2], will add the PR as soon as the tests
 are done



 [1] https://github.com/ManZzup/identity-framework/blob/maste
 r/components/entitlement/org.wso2.carbon.identity.entitlemen
 t.endpoint/REQUIRED_CHANGES.md
 [2] https://wso2.org/jira/browse/IDENTITY-4985

 Thank You
 Manujith

 On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana <
 la...@wso2.com> wrote:

> Hi Manujith,
>
> Good to see the project reaching final stages.
> Please find the comments inline.
>
> Thanks,
> Pushpalanka
>
> On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> UPDATE
>>
>> Adding missing links
>> [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
>> /xacml-rest-v1.0-csprd03.html
>> [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa
>> cml-json-http-v1.0.html
>> [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc
>>
>> On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> To update on the current status
>>> 1) The endpoint is fully compliant with the XACML REST profile as
>>> stated here [1]
>>> 2) It is also in accordance with the JSON XACML request/response
>>> profile as stated in [2], except few things that require changes to 
>>> balana
>>>
>> Can you please list down these things 

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Sanjeewa Malalgoda]

First sorry about asking this in last minute. We can we find API definition
for this API?
Have we documented somewhere with all requests paths, payloads responses
etc? I

Thanks,
sanjeewa.

On Tue, Aug 23, 2016 at 3:05 PM, Omindu Rathnaweera  wrote:

> Great work Manujith! Let's schedule a demo and a code review within next
> week.
>
> Regards,
> Omindu.
>
> On Tue, Aug 23, 2016 at 2:27 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi all,
>>
>> Coming to the conclusion of the project, here's the progress so far
>> The project description can be seen at [1]. The goal was to provide
>> RESTful access to the PDP of the IS
>>
>> Progress
>> 
>> 1) REST implementation done using Apache CXF framework
>> 2) JSON compatibility added using Jackson jax-rs
>> 3) REST service supports consuming and producing JSON and XML
>> 4) REST API fully compliant with the XACML 3.0 REST profile [2] and XACML
>> 3.0 JSON profile [3]
>> 5) Using swagger to populate service method
>> 6) Integration tests and documentation done
>>
>> Deliverables
>> -
>> 1) REST implementation for the IS PDP [4]
>> 2) Developer[5] and User[6] documentation
>> 3) Integration tests
>>
>> In addition the following blog post covers the progress in detail [7] and
>> it was submitted as the work product submission link for student's final
>> evaluation form.
>>
>> Finally i would like to thank all my mentors for the immense support and
>> the community for their prompt assistance.
>>
>> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+
>> for+2016#ProjectProposalsfor2016-Proposal22:[IS]RESTfulFineG
>> rainedAuthorization-as-a-Service(AZaaS)
>> [2] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
>> /xacml-rest-v1.0-csprd03.html
>> [3] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/
>> xacml-json-http-v1.0.html
>> [4] https://github.com/ManZzup/identity-framework/tree/
>> master/components/entitlement/org.wso2.carbon.identity.
>> entitlement.endpoint
>> [5] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc/
>> [6] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide
>> [7] http://manzzup.blogspot.com/2016/08/gsoc-2016-rest-imple
>> mentation-for-wso2.html
>>
>> Thank You
>> Manujith
>>
>> On Sun, Aug 14, 2016 at 1:39 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> Hi Pushpalanka,
>>>
>>> Thank you for the comments
>>>
>>> 1) I added a list of required changes at [1]
>>>
>>> 2) The blog post will be link for now from the github readme, since I'm
>>> adding additional blog posts to support the content of the above post
>>> (mostly in depth implementation details for source), I thought of keeping
>>> the blogpost and linking from the repo. But I will have a markdown version
>>> of the blogpost as well.
>>>
>>> On other updates,
>>>
>>> 1) Swagger is now implemented
>>> 2) Integration tests are done using Jetty
>>> 3) Added the Jira ticket at [2], will add the PR as soon as the tests
>>> are done
>>>
>>>
>>>
>>> [1] https://github.com/ManZzup/identity-framework/blob/maste
>>> r/components/entitlement/org.wso2.carbon.identity.entitleme
>>> nt.endpoint/REQUIRED_CHANGES.md
>>> [2] https://wso2.org/jira/browse/IDENTITY-4985
>>>
>>> Thank You
>>> Manujith
>>>
>>> On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana <
>>> la...@wso2.com> wrote:
>>>
 Hi Manujith,

 Good to see the project reaching final stages.
 Please find the comments inline.

 Thanks,
 Pushpalanka

 On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte <
 manujith...@gmail.com> wrote:

> UPDATE
>
> Adding missing links
> [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
> /xacml-rest-v1.0-csprd03.html
> [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa
> cml-json-http-v1.0.html
> [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc
>
> On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi all,
>>
>> To update on the current status
>> 1) The endpoint is fully compliant with the XACML REST profile as
>> stated here [1]
>> 2) It is also in accordance with the JSON XACML request/response
>> profile as stated in [2], except few things that require changes to 
>> balana
>>
> Can you please list down these things and the changes required in
 Balana, so that we can address them at least later.

> 3) Developer documentation was generated after fully commenting the
>> important codes and available for now at [3]
>>
> Additionally would be good to have the design details at github it
 self as well or linked to your blog at http://manzzup.blogspot.com/20
 16/08/gsoc-2016-rest-implementation-for-wso2.html.

>
>> Hoping to work on user documentation and integration tests and submit
>> a new PR within next week
>> Any ideas for 

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Omindu Rathnaweera]

Great work Manujith! Let's schedule a demo and a code review within next
week.

Regards,
Omindu.

On Tue, Aug 23, 2016 at 2:27 PM, Manujith Pallewatte 
wrote:

> Hi all,
>
> Coming to the conclusion of the project, here's the progress so far
> The project description can be seen at [1]. The goal was to provide
> RESTful access to the PDP of the IS
>
> Progress
> 
> 1) REST implementation done using Apache CXF framework
> 2) JSON compatibility added using Jackson jax-rs
> 3) REST service supports consuming and producing JSON and XML
> 4) REST API fully compliant with the XACML 3.0 REST profile [2] and XACML
> 3.0 JSON profile [3]
> 5) Using swagger to populate service method
> 6) Integration tests and documentation done
>
> Deliverables
> -
> 1) REST implementation for the IS PDP [4]
> 2) Developer[5] and User[6] documentation
> 3) Integration tests
>
> In addition the following blog post covers the progress in detail [7] and
> it was submitted as the work product submission link for student's final
> evaluation form.
>
> Finally i would like to thank all my mentors for the immense support and
> the community for their prompt assistance.
>
> [1] https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#
> ProjectProposalsfor2016-Proposal22:[IS]RESTfulFineGrainedAuthorizatio
> n-as-a-Service(AZaaS)
> [2] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/
> csprd03/xacml-rest-v1.0-csprd03.html
> [3] http://docs.oasis-open.org/xacml/xacml-json-http/v1.
> 0/xacml-json-http-v1.0.html
> [4] https://github.com/ManZzup/identity-framework/tree/master/components/
> entitlement/org.wso2.carbon.identity.entitlement.endpoint
> [5] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc/
> [6] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide
> [7] http://manzzup.blogspot.com/2016/08/gsoc-2016-rest-
> implementation-for-wso2.html
>
> Thank You
> Manujith
>
> On Sun, Aug 14, 2016 at 1:39 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi Pushpalanka,
>>
>> Thank you for the comments
>>
>> 1) I added a list of required changes at [1]
>>
>> 2) The blog post will be link for now from the github readme, since I'm
>> adding additional blog posts to support the content of the above post
>> (mostly in depth implementation details for source), I thought of keeping
>> the blogpost and linking from the repo. But I will have a markdown version
>> of the blogpost as well.
>>
>> On other updates,
>>
>> 1) Swagger is now implemented
>> 2) Integration tests are done using Jetty
>> 3) Added the Jira ticket at [2], will add the PR as soon as the tests are
>> done
>>
>>
>>
>> [1] https://github.com/ManZzup/identity-framework/blob/
>> master/components/entitlement/org.wso2.carbon.identity.
>> entitlement.endpoint/REQUIRED_CHANGES.md
>> [2] https://wso2.org/jira/browse/IDENTITY-4985
>>
>> Thank You
>> Manujith
>>
>> On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana > > wrote:
>>
>>> Hi Manujith,
>>>
>>> Good to see the project reaching final stages.
>>> Please find the comments inline.
>>>
>>> Thanks,
>>> Pushpalanka
>>>
>>> On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 UPDATE

 Adding missing links
 [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
 /xacml-rest-v1.0-csprd03.html
 [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa
 cml-json-http-v1.0.html
 [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc

 On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte <
 manujith...@gmail.com> wrote:

> Hi all,
>
> To update on the current status
> 1) The endpoint is fully compliant with the XACML REST profile as
> stated here [1]
> 2) It is also in accordance with the JSON XACML request/response
> profile as stated in [2], except few things that require changes to balana
>
 Can you please list down these things and the changes required in
>>> Balana, so that we can address them at least later.
>>>
 3) Developer documentation was generated after fully commenting the
> important codes and available for now at [3]
>
 Additionally would be good to have the design details at github it self
>>> as well or linked to your blog at http://manzzup.blogspot.com/20
>>> 16/08/gsoc-2016-rest-implementation-for-wso2.html.
>>>

> Hoping to work on user documentation and integration tests and submit
> a new PR within next week
> Any ideas for improvements / ideas / changes to be done prior to the
> PR?
>
> Thank You
> Manujith
>
>
>
> On Wed, Jul 13, 2016 at 2:49 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi all,
>>
>> With the previous suggestions i'm currently working on having Swagger
>> integrated to the service. According to the Apache CXF documentation [1]
>> Swagger can be 

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Isuru,

Issue #6 was fixed.

Thanks,

On Tue, Aug 23, 2016 at 10:27 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> I'm fixing issue #6 and  almost done. I will fix other issues soon after
> finishing #6.
>
> Thanks,
>
> On Tue, Aug 23, 2016 at 7:50 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Several issues reported against the membership scheme is still in open
>> state [1]. Other than issue 6, all others are straightforward to fix.
>> Please fix those asap.
>>
>> [1]. https://github.com/osuran/azure-membership-scheme/issues
>>
>> On Sun, Aug 21, 2016 at 1:49 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Mentors,
>>>
>>> current status: I'm trying to implement the deploy.sh by trying to
>>> invoke puppet to install product configuration at the startup of a puppet
>>> installed VM. But still couldn't come up with a presentable outcome.
>>>
>>> Thanks,
>>>
>>> On Thu, Aug 18, 2016 at 11:32 PM, Osura Rathnayake 
>>> wrote:
>>>
 Thank you


 On Thursday, August 18, 2016, Imesh Gunaratne  wrote:

>
>
> On Thu, Aug 18, 2016 at 7:56 PM, Osura Rathnayake 
> wrote:
>
>> Hi Imesh,
>>
>> Yes now I understand that creating VM images for each product profile
>> will not going to work out.
>>
>> Can you please give me a step by step guideline on what I should do
>> to achieve this?
>>
>
> ​Please refer [1] and [2].
>
> [1] https://github.com/wso2/puppet-modules
> [2] https://docs.wso2.com/display/PM210/WSO2+Puppet+Modules+Docu
> mentation​
>
>
> ​Thanks​
>
> .
>>  Thank you,
>>
>> On Wed, Aug 17, 2016 at 10:41 PM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Wed, Aug 17, 2016 at 10:19 PM, Imesh Gunaratne 
>>> wrote:


 ​There are many spelling mistakes on this file [2], please review
 it again.

>>>
>>> ​Correction: s/on this file/in this file/g
>>>
>>> Thanks
>>> ​
>>>
>>>
 Overall I see very less attention to detail in this repository and
 the membership scheme implementation.


> There I mentioned the things that should be kept in mind while
> configuring wso2 AS and did not go in to detail on hot to configure 
> as it
> can be found in the wso2 documentation. Would that be okay?
>

 ​I don't think this is helpful. Without having detailed steps users
 might not be able to do a complete deployment.

 Few questions:

- How do you create a distributed deployment​

​of AS ​or any other product (say for an example WSO2 API-M)
with this approach? As I explained earlier creating a VM image per 
 product
profile is an unnecessary overhead (time consumption, disk space 
 needed,
maintenance, etc).

- ​What would be the approach of applying​
 a patch or do
​ing​
a configuration change in a such deployment?

 ​IMO it is really important to understand the concepts well and
 solve problems with the most efficient manner. Otherwise the outcome of
 this project might not be usable.

 [2] https://github.com/osuran/azure-artifacts/issues/2

 Thanks


> user do not need to change anything in template.json, so should I
> explain the parameters in that too?
>
> in the paramters.json, except for the vm_image parameter, all of
> the parameters are just for the naming of the elements that you find 
> in a
> VM, for an example, the name of the network interface. Therefore I 
> have
> given instructions on how to set the vm_image parameter.
>
> current progress: The script which was generated by Azure does not
> have the capability to add a custom VM image. I modified it so that 
> now it
> has that capability. Normally when you login to azure from CLI, it 
> needs
> web interaction to authenticate. I modified deploy.sh in a way that it
> authenticates the user without web interaction, this will be useful 
> if we
> run deploy.sh in a minimal version of linux.
>
> currently I'm working on adding deployment patterns to deploy.sh
> and undeploy.sh
>
>
> [1] https://github.com/osuran/azure-artifacts/tree/master/wso2as
>
> thank you,
>
> On Tue, Aug 16, 2016 at 10:10 AM, Isuru Haththotuwa <
> isu...@wso2.com> wrote:
>
>> Hi Osura,
>>
>> Can you please send an update on the 

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Manujith Pallewatte]

Hi all,

Coming to the conclusion of the project, here's the progress so far
The project description can be seen at [1]. The goal was to provide RESTful
access to the PDP of the IS

Progress

1) REST implementation done using Apache CXF framework
2) JSON compatibility added using Jackson jax-rs
3) REST service supports consuming and producing JSON and XML
4) REST API fully compliant with the XACML 3.0 REST profile [2] and XACML
3.0 JSON profile [3]
5) Using swagger to populate service method
6) Integration tests and documentation done

Deliverables
-
1) REST implementation for the IS PDP [4]
2) Developer[5] and User[6] documentation
3) Integration tests

In addition the following blog post covers the progress in detail [7] and
it was submitted as the work product submission link for student's final
evaluation form.

Finally i would like to thank all my mentors for the immense support and
the community for their prompt assistance.

[1]
https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal22:[IS]RESTfulFineGrainedAuthorization-as-a-Service(AZaaS)
[2]
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html
[3]
http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
[4]
https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint
[5] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc/
[6] https://manzzup.atlassian.net/wiki/display/WIRA/IS+REST+API+Guide
[7]
http://manzzup.blogspot.com/2016/08/gsoc-2016-rest-implementation-for-wso2.html

Thank You
Manujith

On Sun, Aug 14, 2016 at 1:39 PM, Manujith Pallewatte 
wrote:

> Hi Pushpalanka,
>
> Thank you for the comments
>
> 1) I added a list of required changes at [1]
>
> 2) The blog post will be link for now from the github readme, since I'm
> adding additional blog posts to support the content of the above post
> (mostly in depth implementation details for source), I thought of keeping
> the blogpost and linking from the repo. But I will have a markdown version
> of the blogpost as well.
>
> On other updates,
>
> 1) Swagger is now implemented
> 2) Integration tests are done using Jetty
> 3) Added the Jira ticket at [2], will add the PR as soon as the tests are
> done
>
>
>
> [1] https://github.com/ManZzup/identity-framework/blob/master/components/
> entitlement/org.wso2.carbon.identity.entitlement.endpoint/
> REQUIRED_CHANGES.md
> [2] https://wso2.org/jira/browse/IDENTITY-4985
>
> Thank You
> Manujith
>
> On Fri, Aug 12, 2016 at 3:45 PM, Pushpalanka Jayawardhana 
> wrote:
>
>> Hi Manujith,
>>
>> Good to see the project reaching final stages.
>> Please find the comments inline.
>>
>> Thanks,
>> Pushpalanka
>>
>> On Thu, Aug 11, 2016 at 1:23 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> UPDATE
>>>
>>> Adding missing links
>>> [1] http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03
>>> /xacml-rest-v1.0-csprd03.html
>>> [2] http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xa
>>> cml-json-http-v1.0.html
>>> [3] http://manzzup.github.io/wso2-entitlement-endpoint/devdoc
>>>
>>> On Thu, Aug 11, 2016 at 1:22 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi all,

 To update on the current status
 1) The endpoint is fully compliant with the XACML REST profile as
 stated here [1]
 2) It is also in accordance with the JSON XACML request/response
 profile as stated in [2], except few things that require changes to balana

>>> Can you please list down these things and the changes required in
>> Balana, so that we can address them at least later.
>>
>>> 3) Developer documentation was generated after fully commenting the
 important codes and available for now at [3]

>>> Additionally would be good to have the design details at github it self
>> as well or linked to your blog at http://manzzup.blogspot.com/20
>> 16/08/gsoc-2016-rest-implementation-for-wso2.html.
>>
>>>
 Hoping to work on user documentation and integration tests and submit a
 new PR within next week
 Any ideas for improvements / ideas / changes to be done prior to the PR?

 Thank You
 Manujith



 On Wed, Jul 13, 2016 at 2:49 PM, Manujith Pallewatte <
 manujith...@gmail.com> wrote:

> Hi all,
>
> With the previous suggestions i'm currently working on having Swagger
> integrated to the service. According to the Apache CXF documentation [1]
> Swagger can be implemented easily by using its Swagger2Feature library. 
> But
> their documentation provides no integration details.
>
> So i integrated the library using some other docs [2], which now shows
> no errors in integration, but when I try to access the api-docs usrl (ex:
> https://localhost:9443/wso2-entitlement/api-docs) it simply shows
>
> *"No 

[Dev] Getting accumulative values from stream

[Aneela Safdar]

Hi,
I have been using following siddhi query to get the events count per minute;  
ts as timestamp (string) and ftp_requests as count (int)

from FTPInStream[command == 'USER']
select time:timestampInMilliseconds(time:dateAdd(str:replaceAll(ts,'T',' '), 5, 
'hour',"-MM-dd HH:mm:ss"),'-MM-dd HH:mm') as milliseconds , uid, 
id_orig_h, id_orig_p, id_resp_h, id_resp_p
insert into intermediateStream;

from intermediateStream#window.externalTimeBatch( milliseconds ,1 min, 
milliseconds, 1 min)
select time:dateFormat(milliseconds, '-MM-dd HH:mm' ) as ts , 
cast(count(milliseconds), 'int') as ftp_requests
group by milliseconds
insert into FTPOutStream; There is a need to populate ftp_requests parameter of 
FTPOutStream as accumulative i.e. (each new no of requests is addition of 
itself and previously added to stream). To achieve this I changed the query as 
below:
from FTPInStream[command == 'USER']
select time:timestampInMilliseconds(time:dateAdd(str:replaceAll(ts,'T',' '), 5, 
'hour',"-MM-dd HH:mm:ss"),'-MM-dd HH:mm') as milliseconds , uid, 
id_orig_h, id_orig_p, id_resp_h, id_resp_p
insert into intermediateStream;

from intermediateStream
select milliseconds, cast(count(milliseconds), 'int') as ftp_request
group by milliseconds
insert into intermediateStream111;

from intermediateStream111#window.externalTimeBatch( milliseconds ,1 min, 
milliseconds, 1 min)
select time:dateFormat(milliseconds, '-MM-dd HH:mm' ) as ts , 
cast(sum(ftp_request), 'int') as ftp_requests
insert into FTPOutStream;

But I am getting nothing in ftp_requests parameter.
Any suggestions?
Regards, Aneela Safdar___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] My GSoC experience - GSoC students please read!

[Abhishek Tiwari]

Thanks Imesh.

Sincerely appreciate the response. The same guide also talks about
MENTORING [1]. Specifically and I quote

"*Don't Be That Guy*: No one likes dictators.  Work with your student on
the development of expectations, rather then barking out orders."

On my last call with Chamila, this is exactly what happened. He literally
shouted at me and threatened to fail me on the project. Forget mentorship,
is this even professional? I sent you PM to address this situation but you
never cared to reply it. You were creating Github issues even after that,
but you simply ignored my email.

The goal of the project never included K8 and I have evidence to support it
(design doc, project proposal and community bonding conversation). However,
when community asked about it, I started working on addressing that, I was
very close to complete it. I was pretty much done with that work, when I
started getting these chats and issues from Chamila about changing names
and params and so many things that were completely out of the scope
considering the timeline. The code in question had been in github for about
2 months and no one ever cared to bring it up until 2 days before the
deadline. Is this how software projects are managed ?

I was always willing to work on everything, and was very interested to work
even after GSoC period. My biggest problem is the way Chamila talked to me,
it was completely unprofessional and disrespectful.

Anyways, there is no point arguing over it, since at some point its going
to become my voice against your voice and nothing productive will come out
of it.  I just hope that I will receive an honest evaluation of my work!

[1]. http://write.flossmanuals.net/gsoc-mentoring/setting-expectations/

On Mon, Aug 22, 2016 at 7:59 PM, Imesh Gunaratne  wrote:

> Hi Abhishek,
>
> Thanks for your feedback! We are really sorry to hear what you
> experienced.
>
> We at WSO2, participated in GSoC for many years now with the intention of
> giving students opportunities to contribute to open source projects for the
> benefit of the entire community. This allows students to learn how open
> source communities work, new technologies related to their academic
> pursuits, give exposure to real world software development processes, etc.
> In the open source world, there is no labour concept, no one is paid for
> doing open source work. If someone is willing to contribute, they are most
> welcome to share their ideas and send contributions. GSoC program is trying
> to give opportunities for students to experience this and be a part of it
> [3]. If you do not like that idea, you should have opted out of this
> project at the very early stages.
>
> The GSoC Student Guide [4] has explained clearly how students should work
> with mentors and what to expect from them. Mentors are voluntarily
> contributing their time to GSoC projects with the intention of adding value
> to open source projects. They do this while working on many other things.
> Therefore delays in meetings and such occurrences may happen due to
> unavoidable circumstances. Please accept our apologies for any
> inconveniences caused in that regard. Please feel free to refer [5], [6],
> [7], [8], [9], [10] on how WSO2 community and your mentors have appreciated
> your contributions then and there.
>
> Changing requirements is part and parcel of software projects and software
> world. However we believe that we did our very best to keep the high level
> requirements of the project fixed. On high level, the main goal of this
> project was to implement a test framework to invoke bash scripts provided
> in WSO2 Dockerfiles and K8S Artifacts repositories for verifying WSO2
> container images. As we believe that is a straightforward goal and nothing
> much need to be changed at the middle of the project except for refinements.
>
> [3] http://write.flossmanuals.net/gsocstudentguide/what-is-
> google-summer-of-code/
> [4] http://write.flossmanuals.net/gsocstudentguide/working-with-
> your-mentor/
> [5] [DEV] [GSoC Dockerfiles] Project update - Migration to Golang,
> http://mail.wso2.org/mailarchive/dev/2016-July/065571.html
> [6] [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test
> framework, http://mail.wso2.org/mailarchive/dev/2016-August/066879.html
> [7] [Dev] GSoC Dockerfiles weekly status meeting minutes,
> http://mail.wso2.org/mailarchive/dev/2016-May/063294.html
> [8] [Dev] [GSoC Dockerfiles] Status update, http://mail.wso2.org/
> mailarchive/dev/2016-June/065107.html
> [9] [Dev] [DEV] [GSoC] Meeting minutes from Dockerfiles test framework
> demo, http://mail.wso2.org/mailarchive/dev/2016-June/065162.html
> [10] [GSoC Dockerfiles] Meeting minutes, http://mail.wso2.org/
> mailarchive/dev/2016-July/066247.html
>
> Thanks
>
> On Mon, Aug 22, 2016 at 2:06 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hello Everyone,
>>
>> There are some organizations that looks at GSoC as getting free labour
>> and use 

Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hi all,
Currently the tool supports generating jfr along with thread dumps and heap
dumps. And the report template has been changed so that it reflects a lot
more details on environmental details during an event. All collectibles
along with thread dumps and jfrs will be bundled in to a zip archive now.
This zip archive will be generated for each "event". This contains the
report, thread dumps(if user requested) & jfr (if user requested). Report
is a HTML file. Thread dumps are also viewable through this report.User can
change the template as he wish by changing the report template HTML file

On Tue, Aug 23, 2016 at 11:28 AM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Dear all,
> This[1]
> 
>  is
> the blog post I made for final work product submission. Please have a look.
> :)
> [1]http://dinanjanagunaratne.blogspot.com/2016/08/during-pas
> t-3-months-i-was-engaged-in.html
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev