date:20151026

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

2015-10-26 Thread Nipuna Chandradasa

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)

Is it a good practice to change a ID of a property and also allow user to
do the changing?
Can we keep separate fields for URL and ID in the page object?

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

2015-10-26 Thread Udara Rathnayake

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

[Dev] Can a network outage between two cluster members cause an OOM situation

2015-10-26 Thread Amila Maha Arachchi

Hi Azeez,

If two members in a cluster cannot communicate with each other for few mins
(lets say 5 mins), can that end up with the members going to an OOM
situation.

Recently we experience an OOM situation a api-gateway cluster (not under a
heavy load). When checking the logs, we found the following log being
printed many times around the time of incidents.

TID: [0] [AM] [2015-10-23 21:46:51,424] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} -  Error occurred while
running CacheCleanupTask {org.wso2.carbon.caching.impl.CacheCleanupTask}

com.hazelcast.core.OperationTimeoutException: No response for 12 ms.
Aborting invocation! Invocation{ serviceName='hz:impl:mapService',
op=SetOperation{$cache.$domain[clouddemo]registryCacheManager#$_timestamp_$REG_PATH_CACHE},
partitionId=30, replicaIndex=0, tryCount=250, tryPauseMillis=500,
invokeCount=1, callTimeout=6, target=Address[10.0.11.12]:4000,
backupsExpected=0, backupsCompleted=0} No response has been received!
backups-expected:0 backups-completed: 0

at
com.hazelcast.spi.impl.operationservice.impl.Invocation.newOperationTimeoutException(Invocation.java:491)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.waitForResponse(InvocationFuture.java:277)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:224)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)

at
com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:435)

at
com.hazelcast.map.impl.proxy.MapProxySupport.setInternal(MapProxySupport.java:487)

at
com.hazelcast.map.impl.proxy.MapProxyImpl.set(MapProxyImpl.java:171)

at
com.hazelcast.map.impl.proxy.MapProxyImpl.set(MapProxyImpl.java:161)

at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.put(HazelcastDistributedMapProvider.java:149)

at
org.wso2.carbon.caching.impl.CacheImpl.runCacheExpiry(CacheImpl.java:939)

at
org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)

at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)

at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:744)

at -- End remote and begin local stack-trace --.(Unknown
Source)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:384)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)

at
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)

at
com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:435)

at
com.hazelcast.map.impl.proxy.MapProxySupport.setInternal(MapProxySupport.java:487)

at
com.hazelcast.map.impl.proxy.MapProxyImpl.set(MapProxyImpl.java:171)

at
com.hazelcast.map.impl.proxy.MapProxyImpl.set(MapProxyImpl.java:161)

at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.put(HazelcastDistributedMapProvider.java:149)

at
org.wso2.carbon.caching.impl.CacheImpl.runCacheExpiry(CacheImpl.java:939)

at
org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)

at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)

at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)

at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:744)

-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] carbon-multitenancy-4.4.4 released !

2015-10-26 Thread Kalpa Welivitigoda

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

[Dev] [EMM] Roles and Permissions

2015-10-26 Thread Chathurika De Silva

Hi

In EMM for permissions the following structure is there

   -Device Management
  -Device Management Admin

User 1 -> Device Management (parent level permission)
User 2 -> Device Management Admin  (Child level permission only)

What are the contexts that above users can be used? Help regarding this is
highly appreciated.

Thank You
Erandi
-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Odata support for DSS is not enabled in Dev studio

2015-10-26 Thread Ramith Jayasinghe

$subject
I created a jira for that[1]
[1] https://wso2.org/jira/browse/TOOLS-3270

-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

2015-10-26 Thread Nuwan Dias

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

2015-10-26 Thread Madhawa Gunasekara

Hi,

I have tested followings,

   - MongoDB Output Mappings
  - JSON Arrays
  - JSON Complex Objects


   - JSON Mappings (Super/ Tenant)

[X] Stable - go ahead and release

On Mon, Oct 26, 2015 at 8:21 AM, Chanika Geeganage  wrote:

> Hi,
>
> I tested followings
>
>- New Google spreadsheet OAuth2 support
>
>  - public spreadsheet (for super-tenant & tenant)
>  - private spreadsheet (for super-tenant & tenant)
>  - Google driver with OAuth2 support (for super-tenant & tenant)
>  - verified JIRAs created for RC1 related to Google spreadsheet datasource.
>
>- Excel datasource - query mode
>
>
>- Tenant creation and adding dataservice in tenant space.
>
> [X] Stable - go ahead and release
> Thanks
>
>
> On Mon, Oct 26, 2015 at 5:17 AM, Anjana Fernando  wrote:
>
>> Hi,
>>
>> I tested the following:-
>>
>> * OData functionality
>>   - Read/write/update/delete
>>   - Reading metadata
>>   - Reading with conditions
>>
>> * New boxcarring functionality (request_box)
>>   - Multiple operation execution
>>   - Transaction commit/rollback on success/error
>>
>> * Verified RC1 blocker.
>>
>> [X] Stable - go ahead and release
>>
>> Cheers,
>> Anjana.
>>
>> 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
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Best Regards..
>
> Chanika Geeganage
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


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

[Dev] Attaching life cycle name to appinfo artifact when creating an application in AF(for custom life cycles)

2015-10-26 Thread Bimali Dayananda

Hi,

This is regarding adding custom life cycles for applications in AF. [1]

Currently in AF the life cycle is attached to the application version
artifact at the creation of application versions. If the app is uploaded
then it attaches 'UploadableApplicationLifeCycle' and if the app is created
then it  attaches 'ApplicationLifecycle'.

It doesn't store life cycle in 'appinfo' artifact.

But when changing life cycle name of an application, the current way of
attaching life cycle is not applicable.

The solution I found is attaching life cycle name to  'appinfo' artifact
when creating an application and do a data migration for old tenants.

Is it okay if I use the solution I suggested?

Your comments are highly valued.

[1] Please prefer Configurable Lifecycle Stages for AppFactory in
Architecture mailing list for details.

Thanks.

-- 
Bimali Dayananda
Intern-Software Engineering
Mobile : +94(77) 571 6618
bim...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

2015-10-26 Thread Nayomi Dayarathne

Hi Malith,

The solution that has given in the document[1] is working(only when the
client is inside the DAS server). Thanks for the help.

Hi DAS team,

The purpose of providing an API is not satisfying by the given solution in
the document[1]. Therefore, given the current state, a client cannot access
the JS API in DAS due to authentication issue and it is not resolved
yet.Reported a JIRA[2] on this.

[1] https://docs.wso2.com/display/DAS300/Analytics+JavaScript+%28JS%29+API
[2] https://wso2.org/jira/browse/DAS-305


Regards,

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

*nay...@wso2.com *

On Mon, Oct 26, 2015 at 11:01 AM, Malith Dhanushka  wrote:

> Hi Nayomi,
>
> I have tested this scenario and identified there is a limitation where
> authentication header is not getting passed in cross domain context.
> Updated documentation accordingly.[1]
>
> [1] https://docs.wso2.com/display/DAS300/Analytics+JavaScript+%28JS%29+API
>
> Thanks,
> Malith
>
>
> On Mon, Oct 26, 2015 at 10:32 AM, Nayomi Dayarathne 
> wrote:
>
>> Hi  Anjana,
>>
>>
>> We could not complete JS API testings due to unavailability of a working
>> reference to it.The solution dunith gave also didn't work and we did try
>> testings with malith as well.
>>
>> Information has given in documents also not completed.Hence has reported
>> following doc JIRA [1],[2].
>>
>> [1]https://wso2.org/jira/browse/DOCUMENTATION-2605
>> [2]https://wso2.org/jira/browse/DOCUMENTATION-2614
>>
>> Please do advice on this.
>>
>>
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>> On Fri, Oct 23, 2015 at 11:48 AM, Dunith Dhanushka 
>> wrote:
>>
>>> Hi Nayomi,
>>>
>>> Can you try following steps after adding * to cors.allowed.origins?
>>>
>>> 1. Upload analytics-client folder to a web server. You can simply use a
>>> Python server for this purpose [1].
>>>
>>> 2. Edit
>>> /repository/deployment/server/webapps/analytics/WEB-INF/
>>> web.xml fileand put * to allowed origins list.
>>>
>>> 3. Invokde http://:/analytics-client/index.html
>>>
>>>
>>>
>>> [1] https://docs.python.org/2/library/simplehttpserver.html
>>>
>>> On Fri, Oct 23, 2015 at 11:28 AM, Nayomi Dayarathne 
>>> wrote:
>>>
 Kind reminder.

 Nayomi Dayarathne

 *Software Engineer-QA*
 Mobile : +94 (0) 775246619 <+94+(0)+775246619>

 *nay...@wso2.com *

 On Wed, Oct 21, 2015 at 6:52 PM, Nayomi Dayarathne 
 wrote:

> Hi Gimantha,
>
>
> As the per the current JS API implementation, it was not allowed to
> access Analytics JS API of DAS due to authentication issue and got the
> following authentication warnings when we debug the java script we have
> written using fire bug.
>
> *This site makes use of a SHA-1 Certificate; it's recommended you use
> certificates with signature algorithms that use hash functions stronger
> than SHA-1.*
> *Cross-Origin Request Blocked: The Same Origin Policy disallows
> reading the remote resource at
> https://localhost:9443/portal/apis/analytics?type=9
> . (Reason: CORS 
> header
> 'Access-Control-Allow-Origin' missing).*
> *Cross-Origin Request Blocked: The Same Origin Policy disallows
> reading the remote resource at
> https://localhost:9443/portal/apis/analytics?type=9
> . (Reason: CORS
> request failed).*
>
> We have tried this scenario locally.And CORS settings has also added
> to the
> /repository/deployment/server/webapps/analytics/WEB-INF/
> web.xml file
>
> I have attached the relevant client files that we used to try this
> scenario, here with.
>
> Could you please provide the necessary and correct information to
> perform this properly?
>
> Regards,
>
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>


>>>
>>>
>>> --
>>> Regards,
>>>
>>> Dunith Dhanushka,
>>> Senior Software Engineer
>>> WSO2 Inc,
>>>
>>> Mobile - +94 71 8615744
>>> Blog - dunithd.wordpress.com 
>>> Twitter - @dunithd 
>>>
>>
>>
>
>
> --
> Malith Dhanushka
> Senior Software Engineer - Data Technologies
> *WSO2, Inc. : wso2.com *
> *Mobile*  : +94 716 506 693
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2EMM 2.0.0 Milestone 8 Released

2015-10-26 Thread Geeth Munasinghe

Hi all,

We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.

This release includes the following features and improvements.

   1. Adding users and sending email invitations.  (admin ui)
   2. Adding roles (admin ui)
   3. View device details (Admin ui)
   4. Android device management
  1. Device Enrollment
  2. Executing device operations (Admin ui & Android Agent)
   5. Windows
  1. Device Enrollment
  2. Executing device operations (Admin ui & Windows native agent)
   6. Operations
  1. Add operations to device  (Admin ui)
   7. Policy
  1. Add policy (Admin ui)
  2. Edit policy (Admin ui)
  3. Change priorities (Admin ui)
  4. Change management (When a policy changed, related devices should
  be notified to apply new changes)
  5. Monitoring the device to check whether applied policy is violated
  or not.


References

Product  can be downloaded from [1].
[1] https://svn.wso2.org/repos/wso2/people/prabatha/MDM/2.0.0-M8/

Thanks
Geeth




*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226
___
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 RC2

2015-10-26 Thread Niranda Perera

Hi all,

we are calling off the vote due to following reasons.

- DAS-289 [1]
- upgrading siddhi, which has a critical bug fix

rgds

[1] https://wso2.org/jira/browse/DAS-289



On Mon, Oct 26, 2015 at 1:31 PM, Sinthuja Ragendran 
wrote:

> Hi,
>
> I did a smoke test on below, and didn't get any issues.
>
> 1) Scripts add/edit/execute/execute-in-backgroud/scheduling
> 2) Activity Explorer
> 3) Message Explorer
> 4) Dashboard
>
> [x] Stable - Go ahead and Release
>
> Thanks,
> Sinthuja.
>
> On Mon, Oct 26, 2015 at 9:09 AM, Rukshan Premathunga 
> wrote:
>
>> Hi NuwanD,
>>
>> I'll test this.
>>
>> Thanks and Regards.
>>
>> On Mon, Oct 26, 2015 at 9:02 AM, Nuwan Dias  wrote:
>>
>>> Hi Rukshan,
>>>
>>> Shall we test this release with the CApp we created for API Analytics?
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Mon, Oct 26, 2015 at 1:18 AM, Sachith Withana 
>>> wrote:
>>>
 I've tested the following,

 * Stream creation / persistence / indexing / data explorer
 * Interactive Analytics Search

 * Both in the Standalone mode with H2/Cassandra and Clustered Mode with
 Cassandra,

 - Deploying and testing the Smart Home sample
 - UDF functionality of Spark
 - Backup Tool functionality
 - Migration Tool functionality

 [x] Stable - Go ahead and Release

 On Sun, Oct 25, 2015 at 3:01 PM, Anjana Fernando 
 wrote:

> I've tested the following:-
>
> * Stream creation / data persistence / data explorer
>   - Primary key based persistence
> * Interactive analytics search
> * Custom gadget/dashboard creation
> * Deployed and tested following samples:-
>   - HTTPD
>   - Smart Home
>   - Wikipedia
> * Spark script execution
>   - Scheduled execution
>   - Execute in foreground
>   - Execute in background
>
> [X] Stable - go ahead and release
>
> Cheers,
> Anjana.
>
> On Sat, Oct 24, 2015 at 8:34 PM, Gokul Balakrishnan 
> wrote:
>
>> Hi Devs,
>>
>> This is the second  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=12474
>>
>> Source & binary distribution files:
>> https://svn.wso2.org/repos/wso2/people/gokul/das/rc2/
>>
>> Maven staging repo:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2das-059/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-das/tree/v3.0.0-RC2
>>
>>
>> [ ] 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
>
>


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


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sinthuja Rajendran*
> Associate Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*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] [EMM 200][Docs] Improvements needed on EMM Documentation

2015-10-26 Thread Shavindri Dissanayake

+[Documentation]

Hi Sashika,

Thank you for the suggestion! I will work with the team to include this
content as it will be very useful to a user.

[1] https://wso2.org/jira/browse/DOCUMENTATION-2596

Thanks & Regards
Shavindri Dissanayake
Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Mon, Oct 26, 2015 at 1:54 PM, Sashika Wijesinghe 
wrote:

> Hi Shavindri,
>
> When updating "Setting up Mysql" documentation, please include
> configuration instructions for all the relevant data sources that needs to
> be configured. Further it would be better to add the purpose of each data
> source mentioned in "master-datasources.xml" and "cdm-datasources.xml",
> since it would be helpful for the user when configuring data sources.
>
> Thanks and Regards,
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Another log which needs to be descriptive

2015-10-26 Thread Amila Maha Arachchi

Hi APIM Team,

This is getting printed in apim gateway.

TID: [0] [AM] [2015-10-23 22:37:34,946]  INFO
{org.wso2.carbon.throttle.core.RoleBasedAccessRateController} -  You cannot
access this service since you have exceeded the allocated quota.
{org.wso2.carbon.throttle.core.RoleBasedAccessRateController}

This is useless unless we know who is the tenant and what is the API. And,
this is something which should be returned to the client, not something
which should get printed in the log IMO.

Regards,

Amila.

-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM 200][Docs] Improvements needed on EMM Documentation

2015-10-26 Thread Sashika Wijesinghe

Hi Shavindri,

When updating "Setting up Mysql" documentation, please include
configuration instructions for all the relevant data sources that needs to
be configured. Further it would be better to add the purpose of each data
source mentioned in "master-datasources.xml" and "cdm-datasources.xml",
since it would be helpful for the user when configuring data sources.

Thanks and Regards,
-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Possible Code Improvement in IOStreamUtils

2015-10-26 Thread Gayan Gunawardana

Hi Kernel Team,

Referring to location [1] there will be possible code Improvement.

public static void copyInputStream(InputStream in, OutputStream out) throws
IOException {
byte[] buf = new byte[BYTE_ARRAY_SIZE];
int len;
while ((len = in.read(buf)) > 0) {
out.write(buf, 0, len);
}

   in.close();
   out.close();
}

If in.close() throws an IOException, out.close() would not be executed. Can
you please look into this ?

[1]
https://github.com/wso2/carbon-kernel/blob/master/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/IOStreamUtils.java

Thanks,
Gayan
-- 
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
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 RC2

2015-10-26 Thread Sinthuja Ragendran

Hi,

I did a smoke test on below, and didn't get any issues.

1) Scripts add/edit/execute/execute-in-backgroud/scheduling
2) Activity Explorer
3) Message Explorer
4) Dashboard

[x] Stable - Go ahead and Release

Thanks,
Sinthuja.

On Mon, Oct 26, 2015 at 9:09 AM, Rukshan Premathunga 
wrote:

> Hi NuwanD,
>
> I'll test this.
>
> Thanks and Regards.
>
> On Mon, Oct 26, 2015 at 9:02 AM, Nuwan Dias  wrote:
>
>> Hi Rukshan,
>>
>> Shall we test this release with the CApp we created for API Analytics?
>>
>> Thanks,
>> NuwanD.
>>
>> On Mon, Oct 26, 2015 at 1:18 AM, Sachith Withana 
>> wrote:
>>
>>> I've tested the following,
>>>
>>> * Stream creation / persistence / indexing / data explorer
>>> * Interactive Analytics Search
>>>
>>> * Both in the Standalone mode with H2/Cassandra and Clustered Mode with
>>> Cassandra,
>>>
>>> - Deploying and testing the Smart Home sample
>>> - UDF functionality of Spark
>>> - Backup Tool functionality
>>> - Migration Tool functionality
>>>
>>> [x] Stable - Go ahead and Release
>>>
>>> On Sun, Oct 25, 2015 at 3:01 PM, Anjana Fernando 
>>> wrote:
>>>
 I've tested the following:-

 * Stream creation / data persistence / data explorer
   - Primary key based persistence
 * Interactive analytics search
 * Custom gadget/dashboard creation
 * Deployed and tested following samples:-
   - HTTPD
   - Smart Home
   - Wikipedia
 * Spark script execution
   - Scheduled execution
   - Execute in foreground
   - Execute in background

 [X] Stable - go ahead and release

 Cheers,
 Anjana.

 On Sat, Oct 24, 2015 at 8:34 PM, Gokul Balakrishnan 
 wrote:

> Hi Devs,
>
> This is the second  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=12474
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/people/gokul/das/rc2/
>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2das-059/
>
> The tag to be voted upon:
> https://github.com/wso2/product-das/tree/v3.0.0-RC2
>
>
> [ ] 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


>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sinthuja Rajendran*
Associate Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Login and Logout error in Store

2015-10-26 Thread Udara Rathnayake

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

2015-10-26 Thread Isuru Udana

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

2015-10-26 Thread Johann Nallathamby

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

Re: [Dev] Possible Code Improvement in IOStreamUtils

2015-10-26 Thread Kishanthan Thangarajah

You can always fix and send a PR :)

On Mon, Oct 26, 2015 at 12:19 PM, Gayan Gunawardana  wrote:

> Hi Kernel Team,
>
> Referring to location [1] there will be possible code Improvement.
>
> public static void copyInputStream(InputStream in, OutputStream out)
> throws IOException {
> byte[] buf = new byte[BYTE_ARRAY_SIZE];
> int len;
> while ((len = in.read(buf)) > 0) {
> out.write(buf, 0, len);
> }
>
>in.close();
>out.close();
> }
>
> If in.close() throws an IOException, out.close() would not be executed.
> Can you please look into this ?
>
> [1]
> https://github.com/wso2/carbon-kernel/blob/master/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/IOStreamUtils.java
>
> Thanks,
> Gayan
> --
> Gayan Gunawardana
> Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>



-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Clarification: Should users be allowed to create a new API version using a deprecated API version?

2015-10-26 Thread Pubudu Priyashan

Hello APIM team,

I have come across $subject while going through APIM functionality (1.9.1).
Currently, it is possible to create a new API version using a deprecated
API version. Shouldn't this be restricted? If not why?

The reason I'm asking this question is because, once users create the most
recent version of the API, shouldn't it be used to create later versions of
the same API rather than using older/deprecated versions?

Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

2015-10-26 Thread Chathurika De Silva

Hi

As of today EOD we have total number of 13 blockers [1] raised and these
have affected the following scenarios

1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
2. Unable to change default username and role
3. Unable to self enrol device
4. Unable to apply policies for QR enrolled devices since all requests are
in pending state
5. Unable to unregister the device and re-register.

Considering the above factors effective testing of the EMM cannot be done.
A solution is highly appreciated.

[1] https://wso2.org/jira/browse/EMM-880?filter=12478

Thank You
Erandi




On Mon, Oct 26, 2015 at 2:12 PM, Geeth Munasinghe  wrote:

> Hi all,
>
> We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.
>
> This release includes the following features and improvements.
>
>1. Adding users and sending email invitations.  (admin ui)
>2. Adding roles (admin ui)
>3. View device details (Admin ui)
>4. Android device management
>   1. Device Enrollment
>   2. Executing device operations (Admin ui & Android Agent)
>5. Windows
>   1. Device Enrollment
>   2. Executing device operations (Admin ui & Windows native agent)
>6. Operations
>   1. Add operations to device  (Admin ui)
>7. Policy
>   1. Add policy (Admin ui)
>   2. Edit policy (Admin ui)
>   3. Change priorities (Admin ui)
>   4. Change management (When a policy changed, related devices should
>   be notified to apply new changes)
>   5. Monitoring the device to check whether applied policy is
>   violated or not.
>
>
> References
>
> Product  can be downloaded from [1].
> [1] https://svn.wso2.org/repos/wso2/people/prabatha/MDM/2.0.0-M8/
>
> Thanks
> Geeth
>
>
>
>
> *G. K. S. Munasinghe*
> *Senior Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

2015-10-26 Thread Chathurika De Silva

Hi

As of today EOD we have total number of 13 blockers [1] raised and these
have affected the following scenarios

1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
2. Unable to change default username and role
3. Unable to self enrol device
4. Unable to apply policies for QR enrolled devices since all requests are
in pending state
5. Unable to unregister the device and re-register.

Considering the above factors effective testing of the EMM cannot be done.
A solution is highly appreciated.

[1] https://wso2.org/jira/browse/EMM-880?filter=12478

Thank You
Erandi

On Mon, Oct 26, 2015 at 6:36 PM, Chathurika De Silva 
wrote:

> Hi
>
> As of today EOD we have total number of 13 blockers [1] raised and these
> have affected the following scenarios
>
> 1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
> 2. Unable to change default username and role
> 3. Unable to self enrol device
> 4. Unable to apply policies for QR enrolled devices since all requests are
> in pending state
> 5. Unable to unregister the device and re-register.
>
> Considering the above factors effective testing of the EMM cannot be done.
> A solution is highly appreciated.
>
> [1] https://wso2.org/jira/browse/EMM-880?filter=12478
>
> Thank You
> Erandi
>
>
>
>
> On Mon, Oct 26, 2015 at 2:12 PM, Geeth Munasinghe  wrote:
>
>> Hi all,
>>
>> We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.
>>
>> This release includes the following features and improvements.
>>
>>1. Adding users and sending email invitations.  (admin ui)
>>2. Adding roles (admin ui)
>>3. View device details (Admin ui)
>>4. Android device management
>>   1. Device Enrollment
>>   2. Executing device operations (Admin ui & Android Agent)
>>5. Windows
>>   1. Device Enrollment
>>   2. Executing device operations (Admin ui & Windows native agent)
>>6. Operations
>>   1. Add operations to device  (Admin ui)
>>7. Policy
>>   1. Add policy (Admin ui)
>>   2. Edit policy (Admin ui)
>>   3. Change priorities (Admin ui)
>>   4. Change management (When a policy changed, related devices
>>   should be notified to apply new changes)
>>   5. Monitoring the device to check whether applied policy is
>>   violated or not.
>>
>>
>> References
>>
>> Product  can be downloaded from [1].
>> [1] https://svn.wso2.org/repos/wso2/people/prabatha/MDM/2.0.0-M8/
>>
>> Thanks
>> Geeth
>>
>>
>>
>>
>> *G. K. S. Munasinghe*
>> *Senior Software Engineer,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>
>
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.

*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

2015-10-26 Thread Prabath Abeysekera

Thanks for the update. EMM team will have an urgent look at all reported
bugs and revert with a resolution.

Cheers,
Prabath

On Mon, Oct 26, 2015 at 6:41 PM, Chathurika De Silva 
wrote:

> Hi
>
> As of today EOD we have total number of 13 blockers [1] raised and these
> have affected the following scenarios
>
> 1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
> 2. Unable to change default username and role
> 3. Unable to self enrol device
> 4. Unable to apply policies for QR enrolled devices since all requests are
> in pending state
> 5. Unable to unregister the device and re-register.
>
> Considering the above factors effective testing of the EMM cannot be done.
> A solution is highly appreciated.
>
> [1] https://wso2.org/jira/browse/EMM-880?filter=12478
>
> Thank You
> Erandi
>
> On Mon, Oct 26, 2015 at 6:36 PM, Chathurika De Silva  > wrote:
>
>> Hi
>>
>> As of today EOD we have total number of 13 blockers [1] raised and these
>> have affected the following scenarios
>>
>> 1. Unable to use MSSQL, Oracle, Mysql or PostgresSQL
>> 2. Unable to change default username and role
>> 3. Unable to self enrol device
>> 4. Unable to apply policies for QR enrolled devices since all requests
>> are in pending state
>> 5. Unable to unregister the device and re-register.
>>
>> Considering the above factors effective testing of the EMM cannot be
>> done. A solution is highly appreciated.
>>
>> [1] https://wso2.org/jira/browse/EMM-880?filter=12478
>>
>> Thank You
>> Erandi
>>
>>
>>
>>
>> On Mon, Oct 26, 2015 at 2:12 PM, Geeth Munasinghe  wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.
>>>
>>> This release includes the following features and improvements.
>>>
>>>1. Adding users and sending email invitations.  (admin ui)
>>>2. Adding roles (admin ui)
>>>3. View device details (Admin ui)
>>>4. Android device management
>>>   1. Device Enrollment
>>>   2. Executing device operations (Admin ui & Android Agent)
>>>5. Windows
>>>   1. Device Enrollment
>>>   2. Executing device operations (Admin ui & Windows native agent)
>>>6. Operations
>>>   1. Add operations to device  (Admin ui)
>>>7. Policy
>>>   1. Add policy (Admin ui)
>>>   2. Edit policy (Admin ui)
>>>   3. Change priorities (Admin ui)
>>>   4. Change management (When a policy changed, related devices
>>>   should be notified to apply new changes)
>>>   5. Monitoring the device to check whether applied policy is
>>>   violated or not.
>>>
>>>
>>> References
>>>
>>> Product  can be downloaded from [1].
>>> [1] https://svn.wso2.org/repos/wso2/people/prabatha/MDM/2.0.0-M8/
>>>
>>> Thanks
>>> Geeth
>>>
>>>
>>>
>>>
>>> *G. K. S. Munasinghe*
>>> *Senior Software Engineer,*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: ge...@wso2.com
>>> phone:(+94) 777911226
>>>
>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> *Chathurika Erandi*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.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] [APIM] Clarification: Should users be allowed to create a new API version using a deprecated API version?

2015-10-26 Thread Abimaran Kugathasan

Hi Pubudu,

We let the API Developer to decide it. There may be a requirement to create
another API version from the deprecated API version.

On Mon, Oct 26, 2015 at 5:47 PM, Pubudu Priyashan  wrote:

> Hello APIM team,
>
> I have come across $subject while going through APIM functionality
> (1.9.1). Currently, it is possible to create a new API version using a
> deprecated API version. Shouldn't this be restricted? If not why?
>
> The reason I'm asking this question is because, once users create the most
> recent version of the API, shouldn't it be used to create later versions of
> the same API rather than using older/deprecated versions?
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan

Software Engineer | WSO2 Inc
Data & APIs Technologies Team
Mobile : +94 773922820


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

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

2015-10-26 Thread Imesh Gunaratne

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.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:384)
>> at
>>

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

2015-10-26 Thread Afkham Azeez

Are the same settings working with the old kernel?

On Mon, Oct 26, 2015 at 10:21 PM, 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.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:384)
>> at
>> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)
>> at
>> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)
>> at
>> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)
>> at
>> com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:456)
>> at
>>

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

2015-10-26 Thread Maninda Edirisooriya

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.




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.operationservice.impl.InvocationFuture.resolveApplicationResponse(InvocationFuture.java:384)
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveApplicationResponseOrThrowException(InvocationFuture.java:334)
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:225)
> at
> com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.get(InvocationFuture.java:204)
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:456)
> at
> com.hazelcast.map.impl.proxy.MapProxySupport.getInternal(MapProxySupport.java:275)
> at
> com.hazelcast.map.impl.proxy.MapProxyImpl.get(MapProxyImpl.java:82)
> at
> org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.get(HazelcastDistributedMapProvider.java:141)
> at org.wso2.carbon.caching.impl.CacheImpl.get(CacheImpl.java:203)
>
>

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

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

[Dev] Can a network outage between two cluster members cause an OOM situation

[Dev] carbon-multitenancy-4.4.4 released !

[Dev] [EMM] Roles and Permissions

[Dev] Odata support for DSS is not enabled in Dev studio

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

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

[Dev] Attaching life cycle name to appinfo artifact when creating an application in AF(for custom life cycles)

Re: [Dev] Authentication issue in accessing analytics JS API in DAS

[Dev] WSO2EMM 2.0.0 Milestone 8 Released

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

Re: [Dev] [EMM 200][Docs] Improvements needed on EMM Documentation

[Dev] Another log which needs to be descriptive

[Dev] [EMM 200][Docs] Improvements needed on EMM Documentation

[Dev] Possible Code Improvement in IOStreamUtils

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

Re: [Dev] Login and Logout error in Store

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

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

Re: [Dev] Possible Code Improvement in IOStreamUtils

[Dev] [APIM] Clarification: Should users be allowed to create a new API version using a deprecated API version?

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

Re: [Dev] WSO2EMM 2.0.0 Milestone 8 Released

Re: [Dev] [APIM] Clarification: Should users be allowed to create a new API version using a deprecated API version?

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

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

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

29 matches

Site Navigation

Mail list logo

Footer information