Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Isuru Wijesinghe]

I've tested with the BPMN data publisher and found no issues.

[x] Stable - Go ahead and release

Thanks and Regards,

On Wed, Oct 28, 2015 at 12:03 PM, Gokul Balakrishnan  wrote:

> I tested the following using both RDBMS and HBase/HDFS DAL components:
>
> - Installing Smart Home sample CApp
> - Publishing data
> - Running Spark queries (manual + scheduled)
> - Data Explorer and Analytics Dashboard
> - Index search
> - Publishing events to external sources (HTTP, logger) from DAS
>
> My vote - [X] Stable - go ahead and release
>
> Thanks,
>
> On 27 October 2015 at 17:53, Gokul Balakrishnan  wrote:
>
>> Hi all,
>>
>> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
>> test and vote. The vote will be open for 72 hours or as needed.
>>
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12485
>>
>> Source & binary distribution files:
>> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>>
>> Maven staging repo:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 DAS Team.
>>
>> --
>> Gokul Balakrishnan
>> Senior Software Engineer,
>> WSO2, Inc. http://wso2.com
>> Mob: +94 77 593 5789 | +1 650 272 9927
>>
>
>
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuru Wijesinghe
*Software Engineer*
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 DSS 3.5.0 RC2

[Madhawa Gunasekara]

Hi Sumedha,


Please find my comments inline.

But following did not work. May be my filter criteria is wrong.
> https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$filter=city
>

yes you query is wrong, if you need to filter by CITY then you need to
specify a string to filter for example,
https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$filter=CITY
eq 'Nantes' or if you need only to select CITY then you can use select
query option for that
https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$select=CITY



> I have a small complain about service name. In service detail page,
> service name appears as 'services/RDBMSSample'.  So if someone follows
> Madawa's blog, the endpoint would look like,
>
> https://localhost:9443/odata*/services/RDBMSSample*/default
>

yes we should consider service hierarchy when creating service endpoint, I
have created jira[1] for that. but I think it's fine for now.

[1] https://wso2.org/jira/browse/DS-1140

>
> Docs (https://docs.wso2.com/display/DSS350/OData+Sample) on OData on
> public doc portal should also improve to show more filter criteria.
>
we will improve the odata sample doc.

>
>
>
> Thanks,
Madhawa

-- 
*Madhawa Gunasekara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 DSS 3.5.0 RC2

[Rajith Vitharana]

Hi All,

Thank you for testing and verifying the WSO2 Data Services Server 3.5.0
RC2. We are closing this vote now. This vote has passed with 5 +1s and 0
-1s. Therefore we are proceeding with the WSO2 Data Services Server 3.5.0
release.

5 +1s
0  -1s

Thank you and Regards,
WSO2 DSS Team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] (no subject)

[Madhawa Gunasekara]

Hi Sumedha,

yes, if you need to filter by CITY then specify a string to filter like
this,  https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$filter=CITY
eq 'Nantes' or if you need only to select CITY then you can use this
https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$select=CITY

yes we should consider service hierarchy when creating service endpoint, I
have created jira[1] for that. but I think it's fine for now.

and also we will improve the odata sample doc.

[1] https://wso2.org/jira/browse/DS-1140

Thanks,
Madhawa

On Wed, Oct 28, 2015 at 11:23 AM, Sumedha Rubasinghe 
wrote:

> Hi,
> I tested the latest pack.
> I enabled OData on RDBMSSample.
>
> I was able to access following endpoints and get results as expected.
> https://localhost:9443/odata/RDBMSSample/default
> https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS
>
> But following did not work. May be my filter criteria is wrong.
> https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$filter=city
>
>
> I have a small complain about service name. In service detail page,
> service name appears as 'services/RDBMSSample'.  So if someone follows
> Madawa's blog, the endpoint would look like,
>
> https://localhost:9443/odata*/services/RDBMSSample*/default
>
> Docs (https://docs.wso2.com/display/DSS350/OData+Sample) on OData on
> public doc portal should also improve to show more filter criteria.
>
> [x ] Stable - go ahead and release
>
> OData feature is stable subjected to above minor fixes.
>
>
> Sumedha
>
>
> On Sat, Oct 24, 2015 at 1:33 AM, Rajith Vitharana 
> wrote:
>
>> Hi,
>>
>> This is the second release candidate of WSO2 DSS 3.5.0
>>
>> This release fixes the following issues:
>> *https://wso2.org/jira/issues/?filter=12469
>> *
>>
>> Please download, test and vote. The vote will be open for 72 hours or as
>> needed.
>>
>> Source & binary distribution files:
>> https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC2/wso2dss-3.5.0.zip
>> 
>>
>> JavaDocs
>> https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC2/javaDocs/index.html
>>
>> Maven staging repo:
>> *http://maven.wso2.org/nexus/content/repositories/orgwso2dss-058/
>> *
>>
>> The tag to be voted upon:
>> *https://github.com/wso2/product-dss/tree/v3.5.0-RC2
>> *
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thanks,
>> The WSO2 DSS Team
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madhawa Gunasekara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "carbon-appmgt" has classes named as "APIM*"?

[Prabath Abeysekera]

Hi Dinusha,

Okay great, thanks for the note.

I can even see classes like "Abstract*APIManager*" in "carbon-appmgt",
which indicates bad use of development practices. Hope all such instances
are already recorded and would get fixed.

Cheers,
Prabath

On Wed, Oct 28, 2015 at 11:56 AM, Dinusha Senanayaka 
wrote:

> Hi Prabath,
>
> Yeah, this is something we already doing in the master with the
> refactoring we are doing.
>
> Regards,
> Dinusha.
>
> On Wed, Oct 28, 2015 at 11:40 AM, Prabath Abeysekera 
> wrote:
>
>> Folks,
>>
>> Shouldn't these be renamed? Or completely removed and use appropriate
>> utilities available in "carbon-apimgt", instead?
>>
>> Cheers,
>> Prabath
>> --
>> Prabath Abeysekara
>> Technical Lead
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Gokul Balakrishnan]

I tested the following using both RDBMS and HBase/HDFS DAL components:

- Installing Smart Home sample CApp
- Publishing data
- Running Spark queries (manual + scheduled)
- Data Explorer and Analytics Dashboard
- Index search
- Publishing events to external sources (HTTP, logger) from DAS

My vote - [X] Stable - go ahead and release

Thanks,

On 27 October 2015 at 17:53, Gokul Balakrishnan  wrote:

> Hi all,
>
> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
> test and vote. The vote will be open for 72 hours or as needed.
>
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12485
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>
> The tag to be voted upon:
> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks,
> The WSO2 DAS Team.
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>



-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Redundant properties in "carbon-appmgt" parent POM

[Dinusha Senanayaka]

Hi Prabath,

Thanks for reporting. Will check them.

Regards,
Dinusha.

On Wed, Oct 28, 2015 at 11:20 AM, Prabath Abeysekera 
wrote:

> Folks,
>
> I can see the following two properties defined in the parent POM of
> "carbon-appmgt" repository, which appear to be redundant.
>
> 4.4.2 - This has to be
> replaced with "carbon.kernel.version" for better maintainability.
>
> 4.4.1 - This needs to
> be removed as none of the components seems to use it.
>
> Please fix.
>
> Cheers,
> Prabath
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "carbon-appmgt" has classes named as "APIM*"?

[Dinusha Senanayaka]

Hi Prabath,

Yeah, this is something we already doing in the master with the refactoring
we are doing.

Regards,
Dinusha.

On Wed, Oct 28, 2015 at 11:40 AM, Prabath Abeysekera 
wrote:

> Folks,
>
> Shouldn't these be renamed? Or completely removed and use appropriate
> utilities available in "carbon-apimgt", instead?
>
> Cheers,
> Prabath
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DS] Changing the page id in a dashboard using properties.

[Manuranga Perera]

Having the URL as id is much cleaner than we generating random ids. (ie.
Dashboard json will be more understandable) But as Udara said we have to
sanitize by removing all non alpha numeric expect '-'.

I don't understand how prefix will help. Anyway, we shouldn't add anything
extra since it is the URL and its visible to the end user.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] "carbon-appmgt" has classes named as "APIM*"?

[Prabath Abeysekera]

Folks,

Shouldn't these be renamed? Or completely removed and use appropriate
utilities available in "carbon-apimgt", instead?

Cheers,
Prabath
-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] carbon-multitenancy-4.4.4 released !

[Sasikala Kottegoda]

Hi all,

When I tried to upgrade to multitency 4.4.4, I get the following error

'Missing requirement: WSO2 Tenant Common Composite Feature 4.4.4
(org.wso2.carbon.tenant.common.feature.group 4.4.4) requires
'org.wso2.carbon.registry.core.feature.group [4.5.0,4.6.0)' but it could
not be found'

But there are no registry 4.5.x releases

Thank you

On Mon, Oct 26, 2015 at 3:30 PM, Kalpa Welivitigoda  wrote:

> Hi devs,
>
> Please note $subject,
>
> org.wso2.carbon.multitenancy
> carbon-multitenancy
> 4.4.4
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> Software Engineer, WSO2 Inc. http://wso2.com
> Email: kal...@wso2.com
> Mobile: +94776509215
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sasikala Kottegoda
*Software Engineer*
WSO2 Inc., http://wso2.com/
lean. enterprise. middleware
Mobile: +94 774835928/712792401
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 DSS 3.5.0 RC2

[Sumedha Rubasinghe]

Hi,
I tested the latest pack.
I enabled OData on RDBMSSample.

I was able to access following endpoints and get results as expected.
https://localhost:9443/odata/RDBMSSample/default
https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS

But following did not work. May be my filter criteria is wrong.
https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS?$filter=city


I have a small complain about service name. In service detail page, service
name appears as 'services/RDBMSSample'.  So if someone follows Madawa's
blog, the endpoint would look like,

https://localhost:9443/odata*/services/RDBMSSample*/default

Docs (https://docs.wso2.com/display/DSS350/OData+Sample) on OData on public
doc portal should also improve to show more filter criteria.

[x ] Stable - go ahead and release

OData feature is stable subjected to above minor fixes.


Sumedha


On Sat, Oct 24, 2015 at 1:33 AM, Rajith Vitharana  wrote:

> Hi,
>
> This is the second release candidate of WSO2 DSS 3.5.0
>
> This release fixes the following issues:
> *https://wso2.org/jira/issues/?filter=12469
> *
>
> Please download, test and vote. The vote will be open for 72 hours or as
> needed.
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC2/wso2dss-3.5.0.zip
> 
>
> JavaDocs
> https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC2/javaDocs/index.html
>
> Maven staging repo:
> *http://maven.wso2.org/nexus/content/repositories/orgwso2dss-058/
> *
>
> The tag to be voted upon:
> *https://github.com/wso2/product-dss/tree/v3.5.0-RC2
> *
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thanks,
> The WSO2 DSS Team
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Login and Logout error in Store

[Ayesha Dissanayaka]

Hi,

On Tue, Oct 27, 2015 at 5:53 PM, Manuranga Perera  wrote:

>
> add logic to check if instance of session object and set it to session obj
> if true else set to request obj
>

Chanaka and myself tested this fix and it works as expected.
Greg team will continue further testing the login/logout scenarios before
releasing jaggery and jaggery-extension.

Thanks!
-Ayesha


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

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

[Dev] Redundant properties in "carbon-appmgt" parent POM

[Prabath Abeysekera]

Folks,

I can see the following two properties defined in the parent POM of
"carbon-appmgt" repository, which appear to be redundant.

4.4.2 - This has to be
replaced with "carbon.kernel.version" for better maintainability.

4.4.1 - This needs to be
removed as none of the components seems to use it.

Please fix.

Cheers,
Prabath
-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard

[Aparna Karunarathna]

Hi Isuru,

I checked version from the ESB master branch pom[1].

4.1.2

[1] https://github.com/wso2/product-esb/blob/master/pom.xml

Regards,
Aparna.

On Tue, Oct 27, 2015 at 5:41 AM, Isuru Udana  wrote:

> Hi Aparna,
>
> We are using 4.3.1.
>
>
> Thanks.
>
> On Mon, Oct 26, 2015 at 10:36 AM, Aparna Karunarathna 
> wrote:
>
>> Hi Kasun/Isuru,
>>
>> Currently ESB uses Apache httpclient 4.1.2, shouldn't it upgrade to newer
>> version?
>>
>> @Deep, Thanks for the clarification.
>>
>> Regards,
>> Aparna
>>
>> On Sat, Oct 24, 2015 at 11:38 AM, Deependra Ariyadewa 
>> wrote:
>>
>>> Hi Aparna,
>>>
>>> This can happen when the client does not send the SNI[1][2] to the
>>> server side to select the proper HTTPS virtual host. In this case NGINX
>>> reverse proxy created in the vhost. Most of the modern browsers send SNI to
>>> server, therefore you will not observe this when you make the request via a
>>> modern browser.
>>>
>>> Most of the new Java HTTP client libraries also support SNI. As an
>>> example, Apache httpclient library support SNI from version 4.3.2 [3]. If
>>> you use a library which does not support SNI, you will get this error for
>>> HTTPS call going towards services hosted in virtual host environments.
>>>
>>> [1] https://en.wikipedia.org/wiki/Server_Name_Indication
>>> [2] https://www.ietf.org/rfc/rfc3546.txt
>>> [3] https://hc.apache.org/news.html
>>>
>>> On Fri, Oct 23, 2015 at 11:07 AM, Aparna Karunarathna 
>>> wrote:
>>>
 Hi all,

 I have encountered a weird "hostname in certificate didn't match:"
 issue when accessing IS dashboard. My setup details are as follows.

 *Setup Details*
 *IS cluster*
 - 3 nodes cluster
 - Hostname - mgt.is.wso2.com
 - Certificate CN - mgt.is.wso2.com

 *BPS cluster*
 - 2 nodes cluster (manager/worker)
 - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com
 - Certificate CN - *.bps.wso2.com

 * Both nodes are fronted by same Nginx plus load balancer.

 [1]
 javax.net.ssl.SSLException: hostname in certificate didn't match: <
 mgt.is.wso2.com> != <*.bps.wso2.com>
 at
 org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238)
 at
 org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
 
 

 When we check the browser cookie, it gave correct certificate. (
 mgt.is.wso2.com), but when we check it from java client[2] it gives
 the bps certificate (*.bps.wso2.com) instead of IS.

 [2]
 https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/

 What is the reason for this? Is it my config issue or Nginx issue or
 our product issue?

 --
 *Regards,*

 *Aparna Karunarathna.*


 *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*

>>>
>>>
>>>
>>> --
>>> Deependra Ariyadewa
>>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>>
>>> email d...@wso2.com; cell +94 71 403 5996 ;
>>> Blog http://risenfall.wordpress.com/
>>> PGP info: KeyID: 'DC627E6F'
>>>
>>> *WSO2 - Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> *Regards,*
>>
>> *Aparna Karunarathna.*
>>
>>
>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>
>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>



-- 
*Regards,*

*Aparna Karunarathna.*


*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Why does "carbon-appmgt" still depend on "4.2.x" versions with obsolete groupIds, etc?

[Prabath Abeysekera]

Folks,

Please see below copied out of the parent pom of carbon-appmgt repository.

4.2.2

4.2.0

4.2.0


4.2.0

4.2.0

4.2.0

Some of these still don't seem to use the latest groupIds introduced upon
the repositories that carry them, as well. Please fix.

Cheers,
Prabath
-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Sachith Withana]

I've tested the following:

- Interactive Analysis search ( Index Search)
- Spark UDFs
- Facets ( Both in Spark and Index Search)
- Backup Tool Functionality
- Migration Tool Functionality ( With and Without Indexing)

[x] Stable - Go ahead and Release

On Wed, Oct 28, 2015 at 10:55 AM, Malith Dhanushka  wrote:

> I've tested following :-
>
> * HL7 publisher and Med stat publisher (ESB 4.9.0)
> * Arbitrary fields with indexing
> * Index Search
>
> [X] Stable - go ahead and release
>
> Thanks,
> Malith
>
> On Wed, Oct 28, 2015 at 1:24 AM, Anjana Fernando  wrote:
>
>> I tested the following:-
>>
>> * Samples - HTTPD, SmartHome, Wikipedia
>> * Index Search (Interactive Analysis) - basic functionality
>> * Spark Execution - Foreground / Background execution
>> * Dashboards
>>   - Creating custom gadgets / dashboards
>> * ESB EventPublish Mediator -> DAS
>> * APIM Toolbox
>>
>> [X] Stable - go ahead and release
>>
>> Cheers,
>> Anjana.
>>
>> On Tue, Oct 27, 2015 at 5:53 PM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
>>> test and vote. The vote will be open for 72 hours or as needed.
>>>
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12485
>>>
>>> Source & binary distribution files:
>>> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>>>
>>> Maven staging repo:
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thanks,
>>> The WSO2 DAS Team.
>>>
>>> --
>>> Gokul Balakrishnan
>>> Senior Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> Mob: +94 77 593 5789 | +1 650 272 9927
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Malith Dhanushka]

I've tested following :-

* HL7 publisher and Med stat publisher (ESB 4.9.0)
* Arbitrary fields with indexing
* Index Search

[X] Stable - go ahead and release

Thanks,
Malith

On Wed, Oct 28, 2015 at 1:24 AM, Anjana Fernando  wrote:

> I tested the following:-
>
> * Samples - HTTPD, SmartHome, Wikipedia
> * Index Search (Interactive Analysis) - basic functionality
> * Spark Execution - Foreground / Background execution
> * Dashboards
>   - Creating custom gadgets / dashboards
> * ESB EventPublish Mediator -> DAS
> * APIM Toolbox
>
> [X] Stable - go ahead and release
>
> Cheers,
> Anjana.
>
> On Tue, Oct 27, 2015 at 5:53 PM, Gokul Balakrishnan 
> wrote:
>
>> Hi all,
>>
>> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
>> test and vote. The vote will be open for 72 hours or as needed.
>>
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12485
>>
>> Source & binary distribution files:
>> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>>
>> Maven staging repo:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 DAS Team.
>>
>> --
>> Gokul Balakrishnan
>> Senior Software Engineer,
>> WSO2, Inc. http://wso2.com
>> Mob: +94 77 593 5789 | +1 650 272 9927
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Concern about the column length of SESSION_ID in IDN_AUTH_SESSION_STORE table

[Nuwan Dias]

On Wed, Oct 28, 2015 at 10:20 AM, Darshana Gunawardana 
wrote:

>
>
> On Wed, Oct 28, 2015 at 10:18 AM, Darshana Gunawardana 
> wrote:
>
>>
>>
>> On Tue, Oct 27, 2015 at 10:24 AM, Johann Nallathamby 
>> wrote:
>>
>>> Yes. This is a problem. I also see few other related problems and looks
>>> like the code could be buggy as well.
>>>
>>> Looking at the code I see the following caches in oauth component.
>>> 1. OAuthCache
>>> 2. AppInfoCache
>>>
>>
>>
>>
>>> 3. AuthorizationGrantCache
>>>
>>
>> Checked with Pushpalanka on this. It seems we don't have other
>> persistence layer for AuthorizationGrantCache, hence we need to store this
>> on SessionDataStore.
>>
> And AuthorizationGrantCache use auth code or access token as its key,
> hence no issue regarding key size for AuthorizationGrantCache.
>

Hope you have considered the case of encrypting the access token (and the
auth code as well?). In which case the token string becomes much longer
than its equivalent plain text.

>
> Thanks,
> Darshana
>
>>
>>
>>> 4. ClaimCache
>>> 5. SessionDataCache
>>>
>>> No (5) looks like a duplicate of the SessionDataCache
>>> in authentication-framework component. In that case we should not use this
>>> and use the one in authentication-framework.
>>>
>>> (1) - (4) doesn't seem they need to go to SessionDataStore.
>>> SessionDataStore is used to store some values for a period of time that
>>> corresponds to a particular request / session. I don't think (1), (2) and
>>> (4) are of that sort. (1), (2) and (4) already have persistent storages and
>>> have no problem if the cache expires. I.e. (1) and (2) are persisted in
>>> OAuth2 tables and (4) in user store. So we shouldn't need SessionDataStore
>>> for those. Not sure about (3), have to look into that bit more closely.
>>>
>>> @Darshana/Maduranga, can you guys please look into this immediately.
>>> This could unnecessarily drop performance of OAuth2.
>>>
>>> Thanks.
>>>
>>> On Mon, Oct 26, 2015 at 5:18 PM, Nuwan Dias  wrote:
>>>
 Hi,

 The length of the column SESSION_ID of the IDN_AUTH_SESSION_STORE table
 is 100. But I see that the values written to that column are quite lengthy
 and inserts could fail for cases like email usernames or long tenant
 domains or long usernames, etc. See a sample value below.

 Eqnhj4j1X8ZJCW0ww56N7Hdzdvoa:nu...@gmail.com@carbon.super:am_application_scope
 default

 The value inserted to this column seem to be a combination of several
 values and hence has the potential to grow. Specially for tokens with
 several scopes.

 Is it right to insert values to this column in this format? Should we
 not change it since it looks to me like it'll be a problem with regard to
 column lengths?
 Thanks,
 NuwanD.

 --
 Nuwan Dias

 Technical Lead - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Johann Dilantha Nallathamby*
>>> Technical Lead & Product Lead of WSO2 Identity Server
>>> Governance Technologies Team
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - *+9476950*
>>> Blog - *http://nallaa.wordpress.com *
>>>
>>
>>
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Nuwan Dias

Technical Lead - 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] Concern about the column length of SESSION_ID in IDN_AUTH_SESSION_STORE table

[Darshana Gunawardana]

On Wed, Oct 28, 2015 at 10:18 AM, Darshana Gunawardana 
wrote:

>
>
> On Tue, Oct 27, 2015 at 10:24 AM, Johann Nallathamby 
> wrote:
>
>> Yes. This is a problem. I also see few other related problems and looks
>> like the code could be buggy as well.
>>
>> Looking at the code I see the following caches in oauth component.
>> 1. OAuthCache
>> 2. AppInfoCache
>>
>
>
>
>> 3. AuthorizationGrantCache
>>
>
> Checked with Pushpalanka on this. It seems we don't have other persistence
> layer for AuthorizationGrantCache, hence we need to store this on
> SessionDataStore.
>
And AuthorizationGrantCache use auth code or access token as its key, hence
no issue regarding key size for AuthorizationGrantCache.

Thanks,
Darshana

>
>
>> 4. ClaimCache
>> 5. SessionDataCache
>>
>> No (5) looks like a duplicate of the SessionDataCache
>> in authentication-framework component. In that case we should not use this
>> and use the one in authentication-framework.
>>
>> (1) - (4) doesn't seem they need to go to SessionDataStore.
>> SessionDataStore is used to store some values for a period of time that
>> corresponds to a particular request / session. I don't think (1), (2) and
>> (4) are of that sort. (1), (2) and (4) already have persistent storages and
>> have no problem if the cache expires. I.e. (1) and (2) are persisted in
>> OAuth2 tables and (4) in user store. So we shouldn't need SessionDataStore
>> for those. Not sure about (3), have to look into that bit more closely.
>>
>> @Darshana/Maduranga, can you guys please look into this immediately. This
>> could unnecessarily drop performance of OAuth2.
>>
>> Thanks.
>>
>> On Mon, Oct 26, 2015 at 5:18 PM, Nuwan Dias  wrote:
>>
>>> Hi,
>>>
>>> The length of the column SESSION_ID of the IDN_AUTH_SESSION_STORE table
>>> is 100. But I see that the values written to that column are quite lengthy
>>> and inserts could fail for cases like email usernames or long tenant
>>> domains or long usernames, etc. See a sample value below.
>>>
>>> Eqnhj4j1X8ZJCW0ww56N7Hdzdvoa:nu...@gmail.com@carbon.super:am_application_scope
>>> default
>>>
>>> The value inserted to this column seem to be a combination of several
>>> values and hence has the potential to grow. Specially for tokens with
>>> several scopes.
>>>
>>> Is it right to insert values to this column in this format? Should we
>>> not change it since it looks to me like it'll be a problem with regard to
>>> column lengths?
>>> Thanks,
>>> NuwanD.
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Technical Lead & Product Lead of WSO2 Identity Server
>> Governance Technologies Team
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com *
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Regards,


*Darshana Gunawardana*Senior Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Concern about the column length of SESSION_ID in IDN_AUTH_SESSION_STORE table

[Darshana Gunawardana]

On Tue, Oct 27, 2015 at 10:24 AM, Johann Nallathamby 
wrote:

> Yes. This is a problem. I also see few other related problems and looks
> like the code could be buggy as well.
>
> Looking at the code I see the following caches in oauth component.
> 1. OAuthCache
> 2. AppInfoCache
>



> 3. AuthorizationGrantCache
>

Checked with Pushpalanka on this. It seems we don't have other persistence
layer for AuthorizationGrantCache, hence we need to store this on
SessionDataStore.


> 4. ClaimCache
> 5. SessionDataCache
>
> No (5) looks like a duplicate of the SessionDataCache
> in authentication-framework component. In that case we should not use this
> and use the one in authentication-framework.
>
> (1) - (4) doesn't seem they need to go to SessionDataStore.
> SessionDataStore is used to store some values for a period of time that
> corresponds to a particular request / session. I don't think (1), (2) and
> (4) are of that sort. (1), (2) and (4) already have persistent storages and
> have no problem if the cache expires. I.e. (1) and (2) are persisted in
> OAuth2 tables and (4) in user store. So we shouldn't need SessionDataStore
> for those. Not sure about (3), have to look into that bit more closely.
>
> @Darshana/Maduranga, can you guys please look into this immediately. This
> could unnecessarily drop performance of OAuth2.
>
> Thanks.
>
> On Mon, Oct 26, 2015 at 5:18 PM, Nuwan Dias  wrote:
>
>> Hi,
>>
>> The length of the column SESSION_ID of the IDN_AUTH_SESSION_STORE table
>> is 100. But I see that the values written to that column are quite lengthy
>> and inserts could fail for cases like email usernames or long tenant
>> domains or long usernames, etc. See a sample value below.
>>
>> Eqnhj4j1X8ZJCW0ww56N7Hdzdvoa:nu...@gmail.com@carbon.super:am_application_scope
>> default
>>
>> The value inserted to this column seem to be a combination of several
>> values and hence has the potential to grow. Specially for tokens with
>> several scopes.
>>
>> Is it right to insert values to this column in this format? Should we not
>> change it since it looks to me like it'll be a problem with regard to
>> column lengths?
>> Thanks,
>> NuwanD.
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
Regards,


*Darshana Gunawardana*Senior Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DS] Changing the page id in a dashboard using properties.

[Nipuna Chandradasa]

Hi Udara,

Sanitizing the user input does not happen yet. I'll look in to that matter.
But can you explain a bit about how we can add a prefix to fix this issue?

Thank you

On Mon, Oct 26, 2015 at 5:23 PM, Udara Rathnayake  wrote:

> Hi Nipuna,
>
> Make sure we sanitize all user inputs before rendering.
>
> On Mon, Oct 26, 2015 at 4:50 PM, Nipuna Chandradasa 
> wrote:
>
>> Hi Team,
>>
>> In the current product-ues, we allow user to change the page id using the
>> URL field in the properties menu. This causes multiple issues as we also
>> use this page id to process the changes to the page.
>>
>> I fixed those issues that i could find ... (Seems like now it's working
>> fine as to tests i did)
>>
> Let's merge those changes to trunk.
>
>>
>> Is it a good practice to change a ID of a property and also allow user to
>> do the changing?
>>
> Can't we have a prefix+sanitized user input?
>
>> Can we keep separate fields for URL and ID in the page object?
>>
> If we are to use a prefix, is this requirement valid still?
>
>>
>> Appreciate your suggestions and comments.
>>
>> Thank you.
>> --
>> Nipuna Marcus
>> *Software Engineer*
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>> Mobile : +94 (0) 713 667906
>> nipu...@wso2.com
>>
>
>


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

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

[Madusanka Premaratne]

Hi Viral,
You can find carbon-apimgt[1] and product-apim[2]. But please note that
these two branches are not fully tested and released yet. Also make sure
that you build carbon-apimgt before building product-apim.

[1] - https://github.com/wso2/carbon-apimgt/tree/release-1.10.x
[2] - https://github.com/wso2/product-apim/tree/1.10.x

Thanks,
Madusanka

On Wed, Oct 28, 2015 at 8:34 AM, Viral Shah 
wrote:

> Hi Madusanka,
>
>
>
> Thanks for the quick response, I have tried restarting wso2server a bunch
> of times, with no avail. Is it possible for me to get my hands on 1.10?
>
>
>
> Thanks,
>
> Viral Shah
>
> (c): +1 312 375 2629
>
> AIM: budmiller75
>
> Yahoo/Skype: virals3
>
>
>
> *From:* Madusanka Premaratne [mailto:madusan...@wso2.com]
> *Sent:* Tuesday, October 27, 2015 10:02 PM
> *To:* WSO2 Developers' List ; Viral Shah <
> vs...@turnberrysolutions.com>
> *Subject:* Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to
> 0.10.0
>
>
>
> [Adding Dev]
>
> Hi Viral,
>
> This is due to a package exported by multiple bundles. The error occurs
> when OSGI picks wrong bundle while starting the server. As a quick
> workaround try restating WSO2 API manager, if OSGI picks the correct one it
> will work. Also please note that the issue is fixed in APIM 1.10.0 which is
> the next version of WSO2 API Manager.
>
>
>
> Thanks,
>
> Madusanka
>
>
>
> On Wed, Oct 28, 2015 at 7:45 AM, Viral Shah 
> wrote:
>
> Hi Madusanka,
>
>
>
> I just downloaded WSO2 API manager 1.9.1 and am running it on linux as is.
> For the most part it works fine, but when I go to the store and assign the
> API to the application, I see a bunch of errors in wso2carbon.log as
> follows:
>
>
>
> TID: [0] [AM] [2015-10-27 20:19:24,544] ERROR
> {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
> org.mozilla.javascript.EcmaError: TypeError: Cannot call property
> replaceEmailDomain in object [JavaPackage
> org.wso2.carbon.apimgt.impl.utils.APIUtil]. It is not a function, it is
> "object". (/store/site/themes/fancy/templates/api/swagger/template.jag#36)
> {org.jaggeryjs.jaggery.core.manager.WebAppManager}
>
> org.jaggeryjs.scriptengine.exceptions.ScriptException:
> org.mozilla.javascript.EcmaError: TypeError: Cannot call property
> replaceEmailDomain in object [JavaPackage
> org.wso2.carbon.apimgt.impl.utils.APIUtil]. It is not a function, it is
> "object". (/store/site/themes/fancy/templates/api/swagger/template.jag#36)
>
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
>
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
>
> at
> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:541)
>
>
>
> Here are the physical box specs:
>
> Machine: 14.04.1-Ubuntu
>
> JVM: java full version "1.7.0_79-b14"
>
> root:/usr/local/Wso2/wso2am-1.9.1/repository/logs# uname -a
>
> Linux itchil110 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> Any guidance is much appreciated.
>
>
>
> Thanks,
>
> Viral Shah
>
> (c): +1 312 375 2629
>
> AIM: budmiller75
>
> Yahoo/Skype: virals3
>
>
>
>
>
>
>
> --
>
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>
> Email: madusan...@wso2.com | Web: www.wso2.com
>
>
>
> [image: Facebook]  [image: Twitter]
>  [image: Google Plus]
>  [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>
>



-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]

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

Re: [Dev] [APIM] ScriptEngine Error after updating jaggery to 0.10.0

[Madusanka Premaratne]

[Adding Dev]
Hi Viral,
This is due to a package exported by multiple bundles. The error occurs
when OSGI picks wrong bundle while starting the server. As a quick
workaround try restating WSO2 API manager, if OSGI picks the correct one it
will work. Also please note that the issue is fixed in APIM 1.10.0 which is
the next version of WSO2 API Manager.

Thanks,
Madusanka

On Wed, Oct 28, 2015 at 7:45 AM, Viral Shah 
wrote:

> Hi Madusanka,
>
>
>
> I just downloaded WSO2 API manager 1.9.1 and am running it on linux as is.
> For the most part it works fine, but when I go to the store and assign the
> API to the application, I see a bunch of errors in wso2carbon.log as
> follows:
>
>
>
> TID: [0] [AM] [2015-10-27 20:19:24,544] ERROR
> {org.jaggeryjs.jaggery.core.manager.WebAppManager} -
> org.mozilla.javascript.EcmaError: TypeError: Cannot call property
> replaceEmailDomain in object [JavaPackage
> org.wso2.carbon.apimgt.impl.utils.APIUtil]. It is not a function, it is
> "object". (/store/site/themes/fancy/templates/api/swagger/template.jag#36)
> {org.jaggeryjs.jaggery.core.manager.WebAppManager}
>
> org.jaggeryjs.scriptengine.exceptions.ScriptException:
> org.mozilla.javascript.EcmaError: TypeError: Cannot call property
> replaceEmailDomain in object [JavaPackage
> org.wso2.carbon.apimgt.impl.utils.APIUtil]. It is not a function, it is
> "object". (/store/site/themes/fancy/templates/api/swagger/template.jag#36)
>
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:571)
>
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
>
> at
> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:541)
>
>
>
> Here are the physical box specs:
>
> Machine: 14.04.1-Ubuntu
>
> JVM: java full version "1.7.0_79-b14"
>
> root:/usr/local/Wso2/wso2am-1.9.1/repository/logs# uname -a
>
> Linux itchil110 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> Any guidance is much appreciated.
>
>
>
> Thanks,
>
> Viral Shah
>
> (c): +1 312 375 2629
>
> AIM: budmiller75
>
> Yahoo/Skype: virals3
>
>
>



-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]

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

[Dev] WSO2 Carbon Kernel 5.0.0 - Milestone 07 Released !

[Aruna Karunarathna]

WSO2 Carbon Kernel 5.0.0 - Milestone 07 Released !

We are pleased to announce that the seventh milestone release of Carbon
Kernel 5.0.0 is now available to download from here
.
The Source and Tag Location for this release are available here
.

Carbon Kernel 5.0.0 is the core of the next-generation WSO2 Carbon
platform. We have completely rearchitected Carbon Kernel from the ground up
with the latest technologies and patterns. Additionally, the Carbon Kernel
is now a lightweight, general-purpose OSGi runtime specializing in hosting
servers, providing key functionality for server developers. The result is a
streamlined and even more powerful middleware platform than ever before.

This milestone release is a step forward towards building the OSGi-based
server development framework. It includes the following new features.

New Features

   -

   Carbon Startup Order Resolver Framework
   -

   Dropins support for OSGi ready bundles
   -

   Jar to Bundle Conversion tool support


Improvements

   -

   Carbon Feature Plugin 2.0.0-alpha integration.


Key Features

   -

   Pluggable Runtime Framework
   -

   Java 8 Support


   -

   Centralized Logging Framework with Log4j 2.0 as the backend.
   -

   Carbon Launcher Framework
   -

   Transport Management Framework
   -

   Equipped with Eclipse Luna SR2 OSGi Framework
   -

   Pax Exam OSGi Test Framework Support

Fixed Issues

   -

   WSO2 Carbon Kernel 5.0.0 - Fixed Issues
   

How To Contribute

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

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

Carbon Kernel development is still in its early stages, and we encourage
you to report issues, documentation errors, and feature requests regarding
this milestone release of WSO2 Carbon Kernel 5.0.0 through the public issue
tracking system .


Thanks,

WSO2 Carbon Team

-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com




-- 

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

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Anjana Fernando]

I tested the following:-

* Samples - HTTPD, SmartHome, Wikipedia
* Index Search (Interactive Analysis) - basic functionality
* Spark Execution - Foreground / Background execution
* Dashboards
  - Creating custom gadgets / dashboards
* ESB EventPublish Mediator -> DAS
* APIM Toolbox

[X] Stable - go ahead and release

Cheers,
Anjana.

On Tue, Oct 27, 2015 at 5:53 PM, Gokul Balakrishnan  wrote:

> Hi all,
>
> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
> test and vote. The vote will be open for 72 hours or as needed.
>
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12485
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>
> The tag to be voted upon:
> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks,
> The WSO2 DAS Team.
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Niranda Perera]

Hi all,

I tested the following features (using Java 8) and found that they are
working as expected.

- Spark clustering
- Fail-over scenarios in the analytics member nodes (Master failover,
worker failover, analytics cluster failover)

my vote,
[X] Stable - go ahead and release

cheers

On Tue, Oct 27, 2015 at 11:58 PM, Vidura Gamini Abhaya 
wrote:

> Hi,
>
> I've tested the following features / samples and experienced no issues.
>
> - General functionality
> - Samples - Sending Notifications through Published events using spark,
> HTTPD logs, Smart Home, Realtime Service Stats, Wikipedia Data
> - CApp deployment
> - Gadget Creation
> - Custom Dashboard Creation
> - JVM Metrics
> - Siddhi Try It / Event Simulator
>
> My vote - [x] Stable - go ahead and release
>
> Thanks and Regards,
>
> Vidura
>
>
>
> On 27 October 2015 at 17:53, Gokul Balakrishnan  wrote:
>
>> Hi all,
>>
>> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
>> test and vote. The vote will be open for 72 hours or as needed.
>>
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12485
>>
>> Source & binary distribution files:
>> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>>
>> Maven staging repo:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 DAS Team.
>>
>> --
>> Gokul Balakrishnan
>> Senior Software Engineer,
>> WSO2, Inc. http://wso2.com
>> Mob: +94 77 593 5789 | +1 650 272 9927
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vidura Gamini Abhaya, Ph.D.
> Director of Engineering
> M:+94 77 034 7754
> E: vid...@wso2.com
>
> WSO2 Inc. (http://wso2.com)
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Vidura Gamini Abhaya]

Hi,

I've tested the following features / samples and experienced no issues.

- General functionality
- Samples - Sending Notifications through Published events using spark,
HTTPD logs, Smart Home, Realtime Service Stats, Wikipedia Data
- CApp deployment
- Gadget Creation
- Custom Dashboard Creation
- JVM Metrics
- Siddhi Try It / Event Simulator

My vote - [x] Stable - go ahead and release

Thanks and Regards,

Vidura



On 27 October 2015 at 17:53, Gokul Balakrishnan  wrote:

> Hi all,
>
> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
> test and vote. The vote will be open for 72 hours or as needed.
>
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12485
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>
> The tag to be voted upon:
> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks,
> The WSO2 DAS Team.
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vidura Gamini Abhaya, Ph.D.
Director of Engineering
M:+94 77 034 7754
E: vid...@wso2.com

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

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

[Maninda Edirisooriya]

I setup two Carbon 4.4.2 servers in two EC2 nodes and added the above
mentioned configurations in the axis2.xml and started (one after the other)
and the same issue was observed. No message was logged once one server was
shut down in the other node backend logs.

Thanks.


*Maninda Edirisooriya*
Senior Software Engineer

*WSO2, Inc.*lean.enterprise.middleware.

*Blog* : http://maninda.blogspot.com/
*E-mail* : mani...@wso2.com
*Skype* : @manindae
*Twitter* : @maninda

On Tue, Oct 27, 2015 at 4:33 PM, Maninda Edirisooriya 
wrote:

> No. It is because the cluster was not properly set. I could access other
> nodes from these nodes. Even though the cluster was setup it seems nodes
> does not recognize other nodes as members.
>
>
>
> On Tue, Oct 27, 2015 at 2:02 PM, Imesh Gunaratne  wrote:
>
>> On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
>>  wrote:
>>
>>>
>>> Here I have started each node one after the other. And once a member was
>>> stopped also any message was not printed.
>>>
>>
>> Then it might be a connection issue between nodes.
>>
>> On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
>> wrote:
>>
>>> We have not tested AWS clustering with old kernel. We moved to AWS
>>> clustering with new kernel. I thought it was due to new kernel version as I
>>> have heard AWS was working properly with products released with older
>>> kernel.
>>> Here I have started each node one after the other. And once a member was
>>> stopped also any message was not printed.
>>>
>>>
>>>
>>> On Mon, Oct 26, 2015 at 11:26 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Member joined message may not come with AWS membership scheme if all
 the members were started at the same time. However the member left message
 should appear if a member is stopped afterwards.


 On Monday, October 26, 2015, Maninda Edirisooriya 
 wrote:

> I have setup the AWS clustering according to [1] but it seems the 
> "AWSBasedMembershipScheme
> Member joined" message is not displayed once a new member is joined
> and no message when it left. This seems to be an issue with new kernel
> version.
>
>  class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
> enable="true">
>
>
> aws
>
>
> 5701
>
>
> xxx
> zzz
> sg-16f4b571
> us-east-1
> a_tag_key
> a_tag_value
>
>
> [1]
> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>
>
> Thanks.
>
>
> *Maninda Edirisooriya*
> Senior Software Engineer
>
> *WSO2, Inc.*lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *E-mail* : mani...@wso2.com
> *Skype* : @manindae
> *Twitter* : @maninda
>
> On Sun, Oct 25, 2015 at 6:59 PM, Afkham Azeez  wrote:
>
>> In EC2 with AWS mode, you should use ports 5701 to 5800
>>
>> On Sun, Oct 25, 2015 at 5:52 PM, Niranda Perera 
>> wrote:
>>
>>> Hi Thusitha,
>>>
>>> 4000 is the local host port specified in the axis2.xml
>>>
>>> quote axis2.xml
>>> "
>>>
>>> 10.100.5.109
>>>
>>> 
>>> 
>>>
>>> 
>>> 4000"
>>>
>>> in DAS we are using wka as the membership scheme.
>>>
>>> cheers
>>>
>>> On Sun, Oct 25, 2015 at 4:47 PM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
 Hi Anjana,

 I noticed following error line on the error stack that you posted.

 com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
> this:Address[172.18.1.227]:4000


 Here it tries to connect using the port 4000. But AFAIK we usually
 use ports between 5701 to 5800. Did you set the port to 4000 in any
 instance?

 Thanks
 Thusitha

 On Sat, Oct 24, 2015 at 5:27 PM, Anjana Fernando 
 wrote:

> Hi,
>
> So I'd a chat with Azeez, and the first thing he mentioned was, we
> should be using the AWS mode in EC2 it seems, the docs can be found 
> for
> this here [1]. And his comments are, these kind of issues can be seen
> sometimes there, but if it recovers eventually it would be okay, but 
> if it
> continues to give same kind of errors always, that would be a problem.
>
> [1]
> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>
> Cheers,
> Anjana.
>
> On Sat, Oct 24, 2015 at 5:11 PM, Anjana Fernando 
> wrote:
>
>> Hi everyone,
>>
>> When testing DAS in EC2, and also with the latest Kernel 4.4.2,
>> QA has reported some Hazlecast issues, specifically [1] and [2]. 
>> Some of
>> the errors as follows:-
>>
>>

Re: [Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Seshika Fernando]

Hi

I've tested the following and encountered no problems.

* Analytics Event Tables
* Comprehensive Siddhi functionality (complex queries)
* Comprehensive CEP functionality (Receivers, Streams, Execution Plans,
Publishers)
* Index Search

My vote - [x ] Stable - go ahead and release

seshi

On Tue, Oct 27, 2015 at 5:53 PM, Gokul Balakrishnan  wrote:

> Hi all,
>
> This is the third release candidate of WSO2 DAS 3.0.0. Please download,
> test and vote. The vote will be open for 72 hours or as needed.
>
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12485
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/
>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/
>
> The tag to be voted upon:
> https://github.com/wso2/product-das/tree/v3.0.0-RC3
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks,
> The WSO2 DAS Team.
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] UserStore in JWT Token

[Júnior]

Hi,

Is it possible to return the User Store in the JWT token?

I saw it returns the username, but I'd like to know from which user store
is this ser from.

Does anyone know if this is possible?

Thanks
-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 developer Studio Kernel 4.0.0 Milestone-1 Released

[Kavith Lokuhewage]

We are pleased to announce the first milestone release of WSO2 developer
Studio Kernel 4.0.0.

P2 repository of WSO2 developer Studio kernel 4.0.0-M1 is available here
.
Source
and Tag Location for this release is available here
.

This is the first milestone release in the new path of WSO2 Developer
Studio to separate the common kernel with WSO2 specific common tooling
components and providing product specific tooling components to be
installed on-top of the Developer Studio kernel.

We are moving into a new development and release architecture from 4.0.0
on-wards where WSO2 Developer Studio Kernel team will be responsible on
implementing, maintaining and supporting a common kernel platform on-top of
which the respective product teams would be able to develop, install and
run their tooling components.

Milestone zero (4.0.0-M0) release of the kernel contained an initial
separation of common kernel components from the existing WSO2 Developer
Studio.

In this first milestone release, we have improved the separated kernel and
added several new features on top of it. Furthermore, in an effort to
adhere to eclipse way of doing things, we have completely moved to eclipse
Tycho[1] based build for features and update site projects.

Below is the list of new features added to the kernel in M1.

   - Carbon Application Tools
   - Carbon Registry Tools
   - Plugin Samples Extensions
   - Carbon User Management Tools
   - Web Based Editor Framework

*How to Contribute*

Please report issues at WSO2 JIRA 
Send your pull requests to developer-studio-kernel-4.0.0 branch


*Contact us*

WSO2 developers can be contacted via the mailing lists:

WSO2 Developers List : dev@wso2.org
WSO2 Architecture List : architect...@wso2.org

Thanks,
Developer Studio Team

[1] https://eclipse.org/tycho/

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

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

[Dev] [VOTE] Release WSO2 Data Analytics Server 3.0.0 RC3

[Gokul Balakrishnan]

Hi all,

This is the third release candidate of WSO2 DAS 3.0.0. Please download,
test and vote. The vote will be open for 72 hours or as needed.


This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12485

Source & binary distribution files:
https://svn.wso2.org/repos/wso2/people/gokul/das/rc3/

Maven staging repo:
http://maven.wso2.org/nexus/content/repositories/orgwso2das-077/

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


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


Thanks,
The WSO2 DAS Team.

-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Login and Logout error in Store

[Manuranga Perera]

fix:
inSessionHostObject java class, in jsConstructor method, change

if (!(args[0] instanceof HttpServletRequest)) {
HostObjectUtil.getReservedHostObjectWarn(hostObjectName);
}

add logic to check if instance of session object and set it to session obj
if true else set to request obj




-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Login and Logout error in Store

[Chanaka Jayasena]

The initial issue Chandana has mentioned is fixed by the commit to acs.jag.

Now the issue is is with session.invalidate method. Following is the
exception. Tried to catch the exception from the session host object but
didn't work. Following is the stack trace.

[2015-10-27 17:35:39,036]  WARN
{org.jaggeryjs.scriptengine.util.HostObjectUtil} -  Session Object has been
reserved and cannot be instantiated by a script.
[2015-10-27 17:35:39,038] ERROR
{org.apache.catalina.session.StandardSession} -  Session event listener
threw exception
org.mozilla.javascript.WrappedException: Wrapped
org.jaggeryjs.scriptengine.exceptions.ScriptException: Session Object has
been reserved and cannot be instantiated by a script.
(/store/controllers/acs.jag#117)
at
org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)
at org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)
at org.mozilla.javascript.Context.newObject(Context.java:1504)
at
org.jaggeryjs.jaggery.core.listeners.WebAppSessionListener.sessionDestroyed(WebAppSessionListener.java:113)
at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:809)
at
org.apache.catalina.session.StandardSession.expire(StandardSession.java:741)
at
org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1277)
at
org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:188)
at
org.jaggeryjs.hostobjects.web.SessionHostObject.jsFunction_invalidate(SessionHostObject.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
at
org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)
at
org.jaggeryjs.rhino.store.controllers.c3._c_anonymous_1(/store/controllers/acs.jag:117)
at
org.jaggeryjs.rhino.store.controllers.c3.call(/store/controllers/acs.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
at
org.jaggeryjs.rhino.store.controllers.c3._c_script_0(/store/controllers/acs.jag:20)
at
org.jaggeryjs.rhino.store.controllers.c3.call(/store/controllers/acs.jag)
at
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at
org.jaggeryjs.rhino.store.controllers.c3.call(/store/controllers/acs.jag)
at
org.jaggeryjs.rhino.store.controllers.c3.exec(/store/controllers/acs.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:273)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.exec(WebAppManager.java:587)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:507)
at
org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
at
org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(S

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

[Maninda Edirisooriya]

No. It is because the cluster was not properly set. I could access other
nodes from these nodes. Even though the cluster was setup it seems nodes
does not recognize other nodes as members.


On Tue, Oct 27, 2015 at 2:02 PM, Imesh Gunaratne  wrote:

> On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
>  wrote:
>
>>
>> Here I have started each node one after the other. And once a member was
>> stopped also any message was not printed.
>>
>
> Then it might be a connection issue between nodes.
>
> On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
> wrote:
>
>> We have not tested AWS clustering with old kernel. We moved to AWS
>> clustering with new kernel. I thought it was due to new kernel version as I
>> have heard AWS was working properly with products released with older
>> kernel.
>> Here I have started each node one after the other. And once a member was
>> stopped also any message was not printed.
>>
>>
>>
>> On Mon, Oct 26, 2015 at 11:26 PM, Imesh Gunaratne  wrote:
>>
>>> Member joined message may not come with AWS membership scheme if all the
>>> members were started at the same time. However the member left message
>>> should appear if a member is stopped afterwards.
>>>
>>>
>>> On Monday, October 26, 2015, Maninda Edirisooriya 
>>> wrote:
>>>
 I have setup the AWS clustering according to [1] but it seems the 
 "AWSBasedMembershipScheme
 Member joined" message is not displayed once a new member is joined
 and no message when it left. This seems to be an issue with new kernel
 version.

 >>> class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
 enable="true">


 aws


 5701


 xxx
 zzz
 sg-16f4b571
 us-east-1
 a_tag_key
 a_tag_value


 [1]
 https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode


 Thanks.


 *Maninda Edirisooriya*
 Senior Software Engineer

 *WSO2, Inc.*lean.enterprise.middleware.

 *Blog* : http://maninda.blogspot.com/
 *E-mail* : mani...@wso2.com
 *Skype* : @manindae
 *Twitter* : @maninda

 On Sun, Oct 25, 2015 at 6:59 PM, Afkham Azeez  wrote:

> In EC2 with AWS mode, you should use ports 5701 to 5800
>
> On Sun, Oct 25, 2015 at 5:52 PM, Niranda Perera 
> wrote:
>
>> Hi Thusitha,
>>
>> 4000 is the local host port specified in the axis2.xml
>>
>> quote axis2.xml
>> "
>>
>> 10.100.5.109
>>
>> 
>> 
>>
>> 
>> 4000"
>>
>> in DAS we are using wka as the membership scheme.
>>
>> cheers
>>
>> On Sun, Oct 25, 2015 at 4:47 PM, Thusitha Thilina Dayaratne <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Anjana,
>>>
>>> I noticed following error line on the error stack that you posted.
>>>
>>> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
 this:Address[172.18.1.227]:4000
>>>
>>>
>>> Here it tries to connect using the port 4000. But AFAIK we usually
>>> use ports between 5701 to 5800. Did you set the port to 4000 in any
>>> instance?
>>>
>>> Thanks
>>> Thusitha
>>>
>>> On Sat, Oct 24, 2015 at 5:27 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi,

 So I'd a chat with Azeez, and the first thing he mentioned was, we
 should be using the AWS mode in EC2 it seems, the docs can be found for
 this here [1]. And his comments are, these kind of issues can be seen
 sometimes there, but if it recovers eventually it would be okay, but 
 if it
 continues to give same kind of errors always, that would be a problem.

 [1]
 https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode

 Cheers,
 Anjana.

 On Sat, Oct 24, 2015 at 5:11 PM, Anjana Fernando 
 wrote:

> Hi everyone,
>
> When testing DAS in EC2, and also with the latest Kernel 4.4.2, QA
> has reported some Hazlecast issues, specifically [1] and [2]. Some of 
> the
> errors as follows:-
>
> TID: [-1234] [] [2015-10-24 08:40:05,130] ERROR
> {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler} -
> Unable to test existence of resource
> {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler}
> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
> this:Address[172.18.1.227]:4000, target:Address[172.18.1.228]:4000,
> partitionId: 5, replicaIndex: 0, operation:
> com.hazelcast.map.impl.operation.GetOperation, service: 
> hz:impl:mapService
> at
> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureNoPartitionProblems(OperationRunnerImpl.java:246)
>

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

[Imesh Gunaratne]

On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
 wrote:

>
> Here I have started each node one after the other. And once a member was
> stopped also any message was not printed.
>

Then it might be a connection issue between nodes.

On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
wrote:

> We have not tested AWS clustering with old kernel. We moved to AWS
> clustering with new kernel. I thought it was due to new kernel version as I
> have heard AWS was working properly with products released with older
> kernel.
> Here I have started each node one after the other. And once a member was
> stopped also any message was not printed.
>
>
>
> On Mon, Oct 26, 2015 at 11:26 PM, Imesh Gunaratne  wrote:
>
>> Member joined message may not come with AWS membership scheme if all the
>> members were started at the same time. However the member left message
>> should appear if a member is stopped afterwards.
>>
>>
>> On Monday, October 26, 2015, Maninda Edirisooriya 
>> wrote:
>>
>>> I have setup the AWS clustering according to [1] but it seems the 
>>> "AWSBasedMembershipScheme
>>> Member joined" message is not displayed once a new member is joined and
>>> no message when it left. This seems to be an issue with new kernel version.
>>>
>>> >> class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
>>> enable="true">
>>>
>>>
>>> aws
>>>
>>>
>>> 5701
>>>
>>>
>>> xxx
>>> zzz
>>> sg-16f4b571
>>> us-east-1
>>> a_tag_key
>>> a_tag_value
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>>>
>>>
>>> Thanks.
>>>
>>>
>>> *Maninda Edirisooriya*
>>> Senior Software Engineer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>
>>> *Blog* : http://maninda.blogspot.com/
>>> *E-mail* : mani...@wso2.com
>>> *Skype* : @manindae
>>> *Twitter* : @maninda
>>>
>>> On Sun, Oct 25, 2015 at 6:59 PM, Afkham Azeez  wrote:
>>>
 In EC2 with AWS mode, you should use ports 5701 to 5800

 On Sun, Oct 25, 2015 at 5:52 PM, Niranda Perera 
 wrote:

> Hi Thusitha,
>
> 4000 is the local host port specified in the axis2.xml
>
> quote axis2.xml
> "
>
> 10.100.5.109
>
> 
> 
>
> 
> 4000"
>
> in DAS we are using wka as the membership scheme.
>
> cheers
>
> On Sun, Oct 25, 2015 at 4:47 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Anjana,
>>
>> I noticed following error line on the error stack that you posted.
>>
>> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
>>> this:Address[172.18.1.227]:4000
>>
>>
>> Here it tries to connect using the port 4000. But AFAIK we usually
>> use ports between 5701 to 5800. Did you set the port to 4000 in any
>> instance?
>>
>> Thanks
>> Thusitha
>>
>> On Sat, Oct 24, 2015 at 5:27 PM, Anjana Fernando 
>> wrote:
>>
>>> Hi,
>>>
>>> So I'd a chat with Azeez, and the first thing he mentioned was, we
>>> should be using the AWS mode in EC2 it seems, the docs can be found for
>>> this here [1]. And his comments are, these kind of issues can be seen
>>> sometimes there, but if it recovers eventually it would be okay, but if 
>>> it
>>> continues to give same kind of errors always, that would be a problem.
>>>
>>> [1]
>>> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Sat, Oct 24, 2015 at 5:11 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi everyone,

 When testing DAS in EC2, and also with the latest Kernel 4.4.2, QA
 has reported some Hazlecast issues, specifically [1] and [2]. Some of 
 the
 errors as follows:-

 TID: [-1234] [] [2015-10-24 08:40:05,130] ERROR
 {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler} -
 Unable to test existence of resource
 {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler}
 com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
 this:Address[172.18.1.227]:4000, target:Address[172.18.1.228]:4000,
 partitionId: 5, replicaIndex: 0, operation:
 com.hazelcast.map.impl.operation.GetOperation, service: 
 hz:impl:mapService
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureNoPartitionProblems(OperationRunnerImpl.java:246)
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:127)
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:315)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142)
 at
 com.hazelcast

[Dev] [Announce] WSO2 Private PaaS 4.1.0 Released!

[Imesh Gunaratne]

WSO2 Private PaaS team is pleased to announce the release of WSO2 Private
PaaS 4.1.0.


WSO2 Private PaaS is a complete, enterprise-grade solution, offering an
open Platform as a Service (PaaS) built on top of Apache Stratos. It is
released under Apache Software License Version 2.0. Mostly enterprise
software solutions are built on heterogeneous software systems with diverse
dependencies & requirements. Moving an equivalent system to the cloud with
automated deployment, dependency management, artifact distribution,
autoscaling, dynamic load balancing, multi-region, multi-IaaS & cloud
bursting features is be a tedious task. Moreover automating advanced
middleware configurations such as cluster discovery & single sign on is
bound to add more complexity.


WSO2 provides a complete solution to meet these requirements, with WSO2
Private PaaS. WSO2 Private PaaS is an enterprise grade Platform as a
Service (PaaS) that delivers standard, on-premise, application,
integration, data, identity, governance, and analytics PaaS solutions for
IT projects.


This release includes two major features; Docker support with Kubernetes
and Composite Application Model for modelling and deploying an entire
software solution platform in cloud.


Architecture


https://docs.wso2.com/display/PP410/Architecture


Cartridges


WSO2 ships cartridges separately, currently following cartridges are
available for WSO2 Private PaaS 4.1.0:



   -

   WSO2 API Manager (AM) 1.9.1
   -

   WSO2 Application Server (AS) 5.2.1
   -

   WSO2 Business Process Server (BPS) 3.5.0
   -

   WSO2 Business Rules Server (BRS) 2.1.0
   -

   WSO2 Data Analytics Server (DAS) 3.0.0
   -

   WSO2 Data Services Server (DSS) 3.2.2
   -

   WSO2 Enterprise Service Bus (ESB) 4.8.1
   -

   WSO2 Governance Registry (G-REG) 5.0.0
   -

   WSO2 Identity Server (IS) 5.0.0
   -

   WSO2 Message Broker (MB) 3.0.0


New Features

   -

   [PAAS-280 ] - A Lightweight
   Cartridge Agent written in Python
   -

   [PAAS-281 ] - Docker support with
   Kubernetes
   -

   [PAAS-282 ] - Metadata API as a
   Key Value Store
   -

   [PAAS-283 ] - Composite
   Application Model
   -

   [PAAS-284 ] - Metering Dashboard
   with Data Analytics Server
   -

   [PAAS-285 ] - Monitoring
   Dashboard with Data Analytics Server
   -

   [PAAS-286 ] - Private PaaS UI
   Theme
   -

   [PAAS-288 ] - Automated Carbon
   Cluster Discovery on Private PaaS
   -

   [PAAS-289 ] - Mock IaaS for
   Simulating IaaS Features


Improvements

   -

   [PAAS-51 ] - Handle hazelcast
   clustering in a multiple network partitions scenario
   -

   [PAAS-115 ] - Docs don't state
   next step after configuring a cartridge
   -

   [PAAS-131 ] - Improve Messaging
   Model
   -

   [PAAS-168 ] - Calculate more
   accurate memory consumption and load average values
   -

   [PAAS-173 ] - Applying Secure
   Vault to passwords used in Cartridge Agent's stratos.sh file
   -

   [PAAS-185 ] - Support graceful
   shutdown for the cartridges when termination happens
   -

   [PAAS-202 ] - Refactor POM
   structure of product-private-paas
   -

   [PAAS-250 ] - Git repo username
   and password should be updatable via ArtifactUpdatedEvent
   -

   [PAAS-256 ] - Allow use of
   message broker credentials in Message component and Python Cartridge Agent
   -

   [PAAS-274 ] - Create a P2 profile
   for PPaaS without CEP features
   -

   [PAAS-290 ] - Statistics to be
   published to multiple CEP endpoints from Cartridge Agent
   -

   [PAAS-296 ] - Thrift publisher in
   LB extensions should be able to send messages to multiple endpoints
   -

   [PAAS-297 ] - Move PCA artifact
   distribution coordinator logic to a separate plugin


Bug Fixes

   -

   [PAAS-85 ] - Users and Roles can
   not be created via Carbon UI
   -

   [PAAS-89 ] - PP does not scale up
   across multiple network partitions
   -

   [PAAS-128 ] - Stratos Config
   Manager not displaying all service properties
   -

   [PAAS-136 ] - UI does not update

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

[Maninda Edirisooriya]

And also I have tested the cluster with WKA membership scheme with old
kernel previously and it worked fine. But with new kernel version we got
some issues and that is why we had to move to AWS clustering mode.


On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya 
wrote:

> We have not tested AWS clustering with old kernel. We moved to AWS
> clustering with new kernel. I thought it was due to new kernel version as I
> have heard AWS was working properly with products released with older
> kernel.
> Here I have started each node one after the other. And once a member was
> stopped also any message was not printed.
>
>
>
> On Mon, Oct 26, 2015 at 11:26 PM, Imesh Gunaratne  wrote:
>
>> Member joined message may not come with AWS membership scheme if all the
>> members were started at the same time. However the member left message
>> should appear if a member is stopped afterwards.
>>
>>
>> On Monday, October 26, 2015, Maninda Edirisooriya 
>> wrote:
>>
>>> I have setup the AWS clustering according to [1] but it seems the 
>>> "AWSBasedMembershipScheme
>>> Member joined" message is not displayed once a new member is joined and
>>> no message when it left. This seems to be an issue with new kernel version.
>>>
>>> >> class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
>>> enable="true">
>>>
>>>
>>> aws
>>>
>>>
>>> 5701
>>>
>>>
>>> xxx
>>> zzz
>>> sg-16f4b571
>>> us-east-1
>>> a_tag_key
>>> a_tag_value
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>>>
>>>
>>> Thanks.
>>>
>>>
>>> *Maninda Edirisooriya*
>>> Senior Software Engineer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>
>>> *Blog* : http://maninda.blogspot.com/
>>> *E-mail* : mani...@wso2.com
>>> *Skype* : @manindae
>>> *Twitter* : @maninda
>>>
>>> On Sun, Oct 25, 2015 at 6:59 PM, Afkham Azeez  wrote:
>>>
 In EC2 with AWS mode, you should use ports 5701 to 5800

 On Sun, Oct 25, 2015 at 5:52 PM, Niranda Perera 
 wrote:

> Hi Thusitha,
>
> 4000 is the local host port specified in the axis2.xml
>
> quote axis2.xml
> "
>
> 10.100.5.109
>
> 
> 
>
> 
> 4000"
>
> in DAS we are using wka as the membership scheme.
>
> cheers
>
> On Sun, Oct 25, 2015 at 4:47 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Anjana,
>>
>> I noticed following error line on the error stack that you posted.
>>
>> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
>>> this:Address[172.18.1.227]:4000
>>
>>
>> Here it tries to connect using the port 4000. But AFAIK we usually
>> use ports between 5701 to 5800. Did you set the port to 4000 in any
>> instance?
>>
>> Thanks
>> Thusitha
>>
>> On Sat, Oct 24, 2015 at 5:27 PM, Anjana Fernando 
>> wrote:
>>
>>> Hi,
>>>
>>> So I'd a chat with Azeez, and the first thing he mentioned was, we
>>> should be using the AWS mode in EC2 it seems, the docs can be found for
>>> this here [1]. And his comments are, these kind of issues can be seen
>>> sometimes there, but if it recovers eventually it would be okay, but if 
>>> it
>>> continues to give same kind of errors always, that would be a problem.
>>>
>>> [1]
>>> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Sat, Oct 24, 2015 at 5:11 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi everyone,

 When testing DAS in EC2, and also with the latest Kernel 4.4.2, QA
 has reported some Hazlecast issues, specifically [1] and [2]. Some of 
 the
 errors as follows:-

 TID: [-1234] [] [2015-10-24 08:40:05,130] ERROR
 {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler} -
 Unable to test existence of resource
 {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler}
 com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
 this:Address[172.18.1.227]:4000, target:Address[172.18.1.228]:4000,
 partitionId: 5, replicaIndex: 0, operation:
 com.hazelcast.map.impl.operation.GetOperation, service: 
 hz:impl:mapService
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureNoPartitionProblems(OperationRunnerImpl.java:246)
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:127)
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:315)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142)
 at
 com.hazelcast.spi.impl.operationexecutor.

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

[Maninda Edirisooriya]

We have not tested AWS clustering with old kernel. We moved to AWS
clustering with new kernel. I thought it was due to new kernel version as I
have heard AWS was working properly with products released with older
kernel.
Here I have started each node one after the other. And once a member was
stopped also any message was not printed.


On Mon, Oct 26, 2015 at 11:26 PM, Imesh Gunaratne  wrote:

> Member joined message may not come with AWS membership scheme if all the
> members were started at the same time. However the member left message
> should appear if a member is stopped afterwards.
>
>
> On Monday, October 26, 2015, Maninda Edirisooriya 
> wrote:
>
>> I have setup the AWS clustering according to [1] but it seems the 
>> "AWSBasedMembershipScheme
>> Member joined" message is not displayed once a new member is joined and
>> no message when it left. This seems to be an issue with new kernel version.
>>
>> > class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
>> enable="true">
>>
>>
>> aws
>>
>>
>> 5701
>>
>>
>> xxx
>> zzz
>> sg-16f4b571
>> us-east-1
>> a_tag_key
>> a_tag_value
>>
>>
>> [1]
>> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>>
>>
>> Thanks.
>>
>>
>> *Maninda Edirisooriya*
>> Senior Software Engineer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>>
>> *Blog* : http://maninda.blogspot.com/
>> *E-mail* : mani...@wso2.com
>> *Skype* : @manindae
>> *Twitter* : @maninda
>>
>> On Sun, Oct 25, 2015 at 6:59 PM, Afkham Azeez  wrote:
>>
>>> In EC2 with AWS mode, you should use ports 5701 to 5800
>>>
>>> On Sun, Oct 25, 2015 at 5:52 PM, Niranda Perera 
>>> wrote:
>>>
 Hi Thusitha,

 4000 is the local host port specified in the axis2.xml

 quote axis2.xml
 "

 10.100.5.109

 
 

 
 4000"

 in DAS we are using wka as the membership scheme.

 cheers

 On Sun, Oct 25, 2015 at 4:47 PM, Thusitha Thilina Dayaratne <
 thusit...@wso2.com> wrote:

> Hi Anjana,
>
> I noticed following error line on the error stack that you posted.
>
> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
>> this:Address[172.18.1.227]:4000
>
>
> Here it tries to connect using the port 4000. But AFAIK we usually use
> ports between 5701 to 5800. Did you set the port to 4000 in any instance?
>
> Thanks
> Thusitha
>
> On Sat, Oct 24, 2015 at 5:27 PM, Anjana Fernando 
> wrote:
>
>> Hi,
>>
>> So I'd a chat with Azeez, and the first thing he mentioned was, we
>> should be using the AWS mode in EC2 it seems, the docs can be found for
>> this here [1]. And his comments are, these kind of issues can be seen
>> sometimes there, but if it recovers eventually it would be okay, but if 
>> it
>> continues to give same kind of errors always, that would be a problem.
>>
>> [1]
>> https://docs.wso2.com/display/CLUSTER420/Setting+up+a+Cluster+in+AWS+Mode
>>
>> Cheers,
>> Anjana.
>>
>> On Sat, Oct 24, 2015 at 5:11 PM, Anjana Fernando 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> When testing DAS in EC2, and also with the latest Kernel 4.4.2, QA
>>> has reported some Hazlecast issues, specifically [1] and [2]. Some of 
>>> the
>>> errors as follows:-
>>>
>>> TID: [-1234] [] [2015-10-24 08:40:05,130] ERROR
>>> {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler} -
>>> Unable to test existence of resource
>>> {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler}
>>> com.hazelcast.spi.exception.WrongTargetException: WrongTarget!
>>> this:Address[172.18.1.227]:4000, target:Address[172.18.1.228]:4000,
>>> partitionId: 5, replicaIndex: 0, operation:
>>> com.hazelcast.map.impl.operation.GetOperation, service: 
>>> hz:impl:mapService
>>> at
>>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureNoPartitionProblems(OperationRunnerImpl.java:246)
>>> at
>>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:127)
>>> at
>>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:315)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:115)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.doRun(OperationThread.java:101)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.run(OperationThread.java:76)
>>> at -- End remote and begin local stack-trace --.(Unknown
>>> Source)
>>> at
>>> com.hazelcast.spi.impl.operatio

Re: [Dev] Login and Logout error in Store

[Udara Rathnayake]

Hi Chandana,

On Tue, Oct 27, 2015 at 12:33 PM, Chandana Napagoda 
wrote:

> Hi Udara,
>
> Changing host name using carbon.xml will not work, since it will break the
> subscriptions and notifications.
>
> I have checked with Chanaka's fix, but it doesn't resolve the complete
> story. When user clicks on the Logout link in the Store, it still throws
> same exception I have pointed in my first mail.
>
Let's improve this fix then.

>
> Regards,
> Chandana
>
> On Tue, Oct 27, 2015 at 11:54 AM, Udara Rathnayake 
> wrote:
>
>> Hi Chandana,
>>
>> Please check whether we are shifting host name in this process, eg :- IP
>> to Host or vice versa.
>> If this is the problem we can avoid by using consistent host-name.
>>
> I mean not to update hostname within carbon.xml, but to use consistent
(hostname or IP) in URL while browsing.

>
>> Anyway noticed that Chanaka solving this issue by not using session to
>> store relaystate. Hope this will solve this problem.
>>
>> Regards,
>> UdaraR
>>
>>
>> On Tue, Oct 27, 2015 at 11:41 AM, Chandana Napagoda 
>> wrote:
>>
>>> Hi Udara,
>>>
>>> I am not clicking on "Go to Store" link shown in the publisher. Steps I
>>> am following are as below.
>>>
>>>- Go to Store URL and access it through anonymous mode.
>>>- Then access the Publisher URL in a different tab of the same
>>>browser.
>>>- Then log  into Publisher app and navigate to Store app which was
>>>already opened in a different tab.
>>>- Click "Signin" link.
>>>
>>> Also, please note that same behavior works fine with G-Reg 5.0.1 and
>>> 5.0.0 packs.
>>>
>>> Regards,
>>> Chandana
>>>
>>>
>>> On Mon, Oct 26, 2015 at 1:59 PM, Udara Rathnayake 
>>> wrote:
>>>
 Hi All,

 As we understood this happens only when we navigate to the store via
 "Go to Store" link which is provided by GREG extensions.
 Problem here is you are initially logging in to the publisher using
 hostname "localhost" and then redirect to the store using IP.

 In publisher.json you have defined  "storeUrl" : "%https.host%/store",
 you can avoid https.host and have it like "storeUrl" : "/store"

 So this is not due to any of the SSO related changes we have done
 recently(inorder to fix XSS/RFI issues).

 Regards,
 UdaraR


 On Sun, Oct 25, 2015 at 10:19 AM, Chandana Napagoda 
 wrote:

> Hi Udara,
>
> Here are the steps to reproduce this issue:
>
> 1). Unzip G-Reg 5.1.0-SNAPSHOT pack an start it.
> 2). Load Store and Publisher sites in the same browser, different tabs.
> 3). Login to the publisher and perform some operations.
> 4). Then navigate to Store tab and click on Signin link. Then a 500
> error page is displayed and an exception is thrown in the backend.
> 5). After that change the URL to "http://localhost:9443/store"; which
> shows in logged in view.
> 6). Then click on the Signout link in the top right corner. Same 500
> error page is displayed and again an exception is thrown in the backend.
>
> Regards,
> Chandana
>
> On Sat, Oct 24, 2015 at 10:17 AM, Udara Rathnayake 
> wrote:
>
>> Hi Chandana,
>>
>> Had a look at this in a ES pack with all latest fixes done for
>> (jaggeryapps + jaggery-extensions[1]), But haven't face such issue. Let 
>> me
>> know the exact steps to reproduce.
>>
>> [1]
>> https://github.com/wso2/jaggery-extensions/commit/6a572c32de0b4f2ab9a1e52a3b5c62af5f7294a6
>>
>> Regards,
>> UdaraR
>>
>> On Sat, Oct 24, 2015 at 9:32 AM, Chandana Napagoda > > wrote:
>>
>>> Hi ES team,
>>>
>>> With the latest carbon store changes, we have noticed that if the
>>> very first logged in user first access the publisher and then login to
>>> store using SSO, an exception is logged. Further if user click on 
>>> logout,
>>> again another exception is logged. Is this errors occurring due to 
>>> recent
>>> SSO changes done in store side?
>>>
>>> Regards,
>>> Chandana
>>>
>>> --
>>> *Chandana Napagoda*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.org
>>>
>>> *Email  :  chand...@wso2.com **Mobile :
>>> +94718169299 <%2B94718169299>*
>>>
>>> *Blog  :http://cnapagoda.blogspot.com
>>> *
>>>
>>>
>>
>
>
> --
> *Chandana Napagoda*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile :
> +94718169299 <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com
> *
>
>

>>>
>>>
>>> --
>>> *Chandana Napagoda*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.org
>>>
>>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>>> <%2B94718169299>*
>>>
>>> *Blog  :http://cnapagoda.blogspot.com
>>> *

Re: [Dev] Login and Logout error in Store

[Chandana Napagoda]

Hi Udara,

Changing host name using carbon.xml will not work, since it will break the
subscriptions and notifications.

I have checked with Chanaka's fix, but it doesn't resolve the complete
story. When user clicks on the Logout link in the Store, it still throws
same exception I have pointed in my first mail.

Regards,
Chandana

On Tue, Oct 27, 2015 at 11:54 AM, Udara Rathnayake  wrote:

> Hi Chandana,
>
> Please check whether we are shifting host name in this process, eg :- IP
> to Host or vice versa.
> If this is the problem we can avoid by using consistent host-name.
>
> Anyway noticed that Chanaka solving this issue by not using session to
> store relaystate. Hope this will solve this problem.
>
> Regards,
> UdaraR
>
>
> On Tue, Oct 27, 2015 at 11:41 AM, Chandana Napagoda 
> wrote:
>
>> Hi Udara,
>>
>> I am not clicking on "Go to Store" link shown in the publisher. Steps I
>> am following are as below.
>>
>>- Go to Store URL and access it through anonymous mode.
>>- Then access the Publisher URL in a different tab of the same
>>browser.
>>- Then log  into Publisher app and navigate to Store app which was
>>already opened in a different tab.
>>- Click "Signin" link.
>>
>> Also, please note that same behavior works fine with G-Reg 5.0.1 and
>> 5.0.0 packs.
>>
>> Regards,
>> Chandana
>>
>>
>> On Mon, Oct 26, 2015 at 1:59 PM, Udara Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> As we understood this happens only when we navigate to the store via "Go
>>> to Store" link which is provided by GREG extensions.
>>> Problem here is you are initially logging in to the publisher using
>>> hostname "localhost" and then redirect to the store using IP.
>>>
>>> In publisher.json you have defined  "storeUrl" : "%https.host%/store",
>>> you can avoid https.host and have it like "storeUrl" : "/store"
>>>
>>> So this is not due to any of the SSO related changes we have done
>>> recently(inorder to fix XSS/RFI issues).
>>>
>>> Regards,
>>> UdaraR
>>>
>>>
>>> On Sun, Oct 25, 2015 at 10:19 AM, Chandana Napagoda 
>>> wrote:
>>>
 Hi Udara,

 Here are the steps to reproduce this issue:

 1). Unzip G-Reg 5.1.0-SNAPSHOT pack an start it.
 2). Load Store and Publisher sites in the same browser, different tabs.
 3). Login to the publisher and perform some operations.
 4). Then navigate to Store tab and click on Signin link. Then a 500
 error page is displayed and an exception is thrown in the backend.
 5). After that change the URL to "http://localhost:9443/store"; which
 shows in logged in view.
 6). Then click on the Signout link in the top right corner. Same 500
 error page is displayed and again an exception is thrown in the backend.

 Regards,
 Chandana

 On Sat, Oct 24, 2015 at 10:17 AM, Udara Rathnayake 
 wrote:

> Hi Chandana,
>
> Had a look at this in a ES pack with all latest fixes done for
> (jaggeryapps + jaggery-extensions[1]), But haven't face such issue. Let me
> know the exact steps to reproduce.
>
> [1]
> https://github.com/wso2/jaggery-extensions/commit/6a572c32de0b4f2ab9a1e52a3b5c62af5f7294a6
>
> Regards,
> UdaraR
>
> On Sat, Oct 24, 2015 at 9:32 AM, Chandana Napagoda 
> wrote:
>
>> Hi ES team,
>>
>> With the latest carbon store changes, we have noticed that if the
>> very first logged in user first access the publisher and then login to
>> store using SSO, an exception is logged. Further if user click on logout,
>> again another exception is logged. Is this errors occurring due to recent
>> SSO changes done in store side?
>>
>> Regards,
>> Chandana
>>
>> --
>> *Chandana Napagoda*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile :
>> +94718169299 <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com
>> *
>>
>>
>


 --
 *Chandana Napagoda*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.org

 *Email  :  chand...@wso2.com **Mobile :
 +94718169299 <%2B94718169299>*

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


>>>
>>
>>
>> --
>> *Chandana Napagoda*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com *
>>
>>
>


-- 
*Chandana Napagoda*
Senior Software Engineer
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299*

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