date:20151025

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

2015-10-25 Thread Anjana Fernando

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

[Dev] [Architecture] WSO2 Message Broker 3.0.0 Beta Released !

2015-10-25 Thread Hasitha Hiranya

Hi All,

WSO2  MB Team is pleased to announce the release of WSO2 Message Broker
3.0.0-Beta. You can now download the distribution which is at [1].
Bug

   - [MB-378 ] - Permission handling
   with "Topic and children" option
   - [MB-698 ] - Messages disappear
   from queue after rerouting/restoring from DeadLetterChannel
   - [MB-1014 ] - Messages left on
   database when subscriber failover
   - [MB-1050 ] - Exception thrown
   when publisher removed
   - [MB-1113 ] - In multiple
   publisher subscriber scenario exception thrown - "Exception occurred while
   processing inbound events"
   - [MB-1115 ] - Exception thrown
   when tried to reroute messages in DLC
   - [MB-1128 ] - MySQL Deadlock when
   killing the publishers/subscribers
   - [MB-1162 ] - Exception thrown
   when restored and rerouted messages in dlc
   - [MB-1163 ] - Exception thrown
   when RDBMS slot management is enabled
   - [MB-1168 ] - Queue name
   declarations with different data lengths seen in the scripts
   - [MB-1231 ] - Add the latest and
   correct jar files to client-lib folder
   - [MB-1245 ] -
   DurableTopicsSubscribers are not getting unsubscribed
   - [MB-1267 ] - Tenant Topic
   subscriptions are showing in Super tenant space
   - [MB-1271 ] -
   IllegalArgumentException: Underflow error logged when restarting the MB
   instance
   - [MB-1313 ] - When you subscribe
   to a topic that Subscriber is listed under durable topic subscribers
   - [MB-1323 ] - Topic can be
   deleted when there are subscribers in a subtopic
   - [MB-1326 ] - Deadlock when
   closing subscribers in Oracle
   - [MB-1333 ] - [MQTT] Messages are
   consumed from different topics if the topics are created by the same
   subscriber
   - [MB-1334 ] - [MQTT] Error when
   unsubscribing from broker
   - [MB-1366 ] - Messages remained
   in the DB eventhough subscriptions are active
   - [MB-1370 ] - Server went OOM
   when consuming messages from both nodes
   - [MB-1379 ] - Tenant users cannot
   publish messages to queues via MC
   - [MB-1386 ] - Queue/Topic names
   should be trimmed before saving
   - [MB-1387 ] - [Tenant] Allows to
   subscribe to a topic with " / "
   - [MB-1389 ] - Subscribers are
   removed from durable topics when they change the JMS selectors and
   subscribe again
   - [MB-1391 ] - If a message is
   published from UI to a topic with a name which has a space in-between the
   message is not routed to the subscribers
   - [MB-1404 ] - [MQTT] When
   subscribed with "+/+/+" the subscriber receives retained messages from
   multilevel topics
   - [MB-1415 ] - The full payload is
   not displyed in MC when the payload is huge
   - [MB-1416 ] - A user with a topic
   permission role only assigned to pub/sub to a specific subtopic can
   subscribe to immediate children
   - [MB-1419 ] - Message lost when
   unacked and no of redelivery attempts are exceeded
   - [MB-1422 ] - [MQTT] The retained
   flag is not set to true when client recieves a retained message
   - [MB-1423 ] - [MQTT] Cannot add
   multiple subscription with the same client ID
   - [MB-1424 ] - When unsubscribed
   from a subtopic with a wild card the subtopic can not be deleted
   - [MB-1427 ] - Prevent topic
   creation which has two full stops subsequently e.g - Sports..
   - [MB-1431 ] - [AMQP] Wild card
   characters shouldn't be allowed when publishing to topics
   - [MB-1433 ] - Publishers can
   publish messages to queues even though those queues do not exist
   - [MB-1437 ] - Observed a deadlock
   when adding multiple durable topics in clustered environment
   - [MB-1438

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

2015-10-25 Thread Thusitha Thilina Dayaratne

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)
>>
>> 
>>
>>
>> TID: [-1234] [] [2015-10-24 08:44:18,800] 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.CallerNotMemberException: Not Member!
>> caller:Address[172.18.1.228]:4000, partitionId: 30, operation:
>> com.hazelcast.map.impl.operation.GetOperation, service: hz:impl:mapService
>> at
>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureValidMember(OperationRunnerImpl.java:336)
>> at
>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:308)
>> at
>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142)
>> at
>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:115)
>>
>> 
>>
>>  ERROR {com.hazelcast.cluster.impl.operations.JoinCheckOperation} -
>> [172.18.1.229]:4000 [wso2.qa.das.domain] [3.5.2] Cannot send response:
>> JoinRequest{packetVersion=4, buildNumber=20150826,
>> address=Address[172.18.1.229]:4000,
>> uuid='6848559f-141d-47cd-9e75-53bb2de10d52', credentials=null,
>> memberCount=4, tryCount=0} to Address[172.18.1.228]:4000
>> {com.hazelcast.cluster.impl.operations.JoinCheckOperation}
>> com.ha

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

2015-10-25 Thread Niranda Perera

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)
>>>
>>> 
>>>
>>>
>>> TID: [-1234] [] [2015-10-24 08:44:18,800] 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.CallerNotMemberException: Not Member!
>>> caller:Address[172.18.1.228]:4000, partitionId: 30, operation:
>>> com.hazelcast.map.impl.operation.GetOperation, service: hz:impl:mapService
>>> at
>>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureValidMember(OperationRunnerImpl.java:336)
>>> at
>>> com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:308)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.processPacket(OperationThread.java:142)
>>> at
>>> com.hazelcast.spi.impl.operationexecutor.classic.OperationThread.process(OperationThread.java:115)
>>>
>>> 
>>>
>>>  ERROR {

Re: [Dev] [IS] Way to store user tokens when writing an Autheticator

2015-10-25 Thread Malaka Silva

Yes I guess we are referring to AuthiticationContext as caching here. I
also agree that it should be stored there.

On Sat, Oct 24, 2015 at 2:43 PM, Chamara Philips  wrote:

> Hi,
> Hope this token is generated by code and sent to the user's phone for him
> to input. Then you validate the user with WSO2 IS, matching the token.
> After he has used it once he can't use that again.
> Based on that assumption, I think the best option is to go with cache.
> Usually userstore is not used in scenarios like this.
> When you generate the new token for the same user you can update the cache
> and continue.
>
> Hope it helps.
>
> Thanks.
>
> On Sat, Oct 24, 2015 at 1:58 PM, Elilmatha Sivanesan 
> wrote:
>
>> Hi
>>
>> I'm writing SMSOTP Authenticator for IS, For that I'm generating a token
>> to be sent to the phone, I have the requirement to store that generated
>> tokens.
>>
>> For that what is the best option to go with.(user store/cache/...).
>>
>> Thanks.
>> --
>> *S.Elilmatha*
>> Associate  Software Engineer,
>>
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile 0779842221.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Hareendra Chamara Philips
> *Software  Engineer*
> Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
> chama...@wso2.com 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
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-25 Thread Afkham Azeez

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)

 TID: [-1234] [] [2015-10-24 08:44:18,800] 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.CallerNotMemberException: Not Member!
 caller:Address[172.18.1.228]:4000, partitionId: 30, operation:
 com.hazelcast.map.impl.operation.GetOperation, service: hz:impl:mapService
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.ensureValidMember(OperationRunnerImpl.java:336)
 at
 com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:308)
 at
 com.hazelcast.spi.impl.operationexecutor.classic.OperationThrea

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

2015-10-25 Thread Sachith Withana

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

[Dev] [ML] Identified Limitations - Pipeline PoC

2015-10-25 Thread Nethaji Chandrasiri

Hi,

As I'm currently working on spark pipeline poc (regex transformer) I've
discovered the following limitations when using data frames and defining
new stages in pipeline,

There's no way to add a csv file directly to a data frame, therefore we
have to use RDD to create a row type rdd and a schema to create a data
frame.

When implementing *Transformer* interface to define a new pipeline stage,
*transform* method is the one that returns a data frame yet it only accepts
a data frame, So if we consider a data frame as a table in a relational
database, in my case I have to convert the data frame into a rdd to replace
matching values with the given label but I couldn't find a way to convert
that rdd back to a data frame without using sql context.

There's another way to do it without using rdd inside a pipeline stage, (by
simply converting the data frame into a Row type array) but I'm still
working on converting that into a data frame.

Since *transformSchema *returns the schema as initial step we have to keep
a record of every change that we do to schema as a separate list, so that
we can pass it to next stage. If not next stage takes the original schema
instead of changed one.

As I'm still working on this task I'll update the details accordingly.

Appreciate any suggestions and comments.


Thanks
-- 
*Nethaji Chandrasiri*
*Software Engineering* *Intern; WSO2, Inc.; http://wso2.com
*
Mobile : +94 (0) 779171059 <%2B94%20%280%29%20778%20800570>
Email  : neth...@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

2015-10-25 Thread Anjana Fernando

Hi,

Please note that, earlier mail's distribution link's target wrong, it
actually points to the RC1 link (which is what you get when you click it,
you will have to copy and paste the link text to get the correct one),
anyways, the correct one again can be found below:-

https://svn.wso2.org/repos/wso2/scratch/DSS/3.5.0/RC2/wso2dss-3.5.0.zip

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

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

2015-10-25 Thread Anjana Fernando

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

[Dev] BAM Cluster. Need some guide.

2015-10-25 Thread Jorge

Hi all.
I setup the Hadoop and Cassandra clusters without problem, now I´m
configuring the BAM Cluster and I have some questions in:

http://stackoverflow.com/questions/33203792/wso2-bam-cluster

Any help?

Regards.
___
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-25 Thread Chanika Geeganage

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
___
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-25 Thread Nuwan Dias

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
___
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-25 Thread Rukshan Premathunga

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

Re: [Dev] Configurator does not give priority to env variables

2015-10-25 Thread Anuruddha Liyanarachchi

Hi,

By any chance if the values are commented out from the module.ini, only env
> values will get populated.


This is not the correct approach, the configurator should pick up the
variables from template itself and then search for environment variables
and module.ini.

Users don't have to comment variables in module.ini.

Please refer mail with subject *"PPaaS configurator doesn't pick all the
payload parameters"* for more info.

On Sat, Oct 24, 2015 at 11:43 PM, Pubudu Gunatilaka 
wrote:

> Hi Imesh,
>
> I just checked the configurator. It gives the priority to env variables
> before reading from module.ini. This should be the default approach.
>
> It would be more safe to define values within the template. By any chance
> if the values are commented out from the module.ini, only env values will
> get populated.
>
> Thank you!
>
> On Sat, Oct 24, 2015 at 10:33 PM, Gayan Gunarathne 
> wrote:
>
>> So what is the usage of the "module.ini"? We can live with only the
>> environment parameters.
>>
>> If the module.ini is for the default values, why are we having default
>> values in the template it self.We are checking whether that value is
>> defined. If that is not define we are setting the default value.
>>
>> [1]
>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.8.1/template-module/templates/repository/conf/datasources/master-datasources.xml.template#L8
>>
>> Thanks,
>> Gayan
>>
>> On Sat, Oct 24, 2015 at 10:00 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Devs,
>>>
>>> I noticed $subject if the same variable has been defined in module.ini.
>>>
>>> IMO this is not correct. We need to be able to configure any parameter
>>> using environment variables without touching the module.ini.
>>>
>>> Thanks
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Senior Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774079049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2EMM 2.0.0 Milestone 7 Released

2015-10-25 Thread Chamara Ariyarathne

Hi Prabath et al,

Any news on a new build that we can continue testing with?

Thanks.

On Fri, Oct 23, 2015 at 11:46 AM, Prabath Abeysekera 
wrote:

> Hi Chathurika,
>
> Yeah, the team is currently working on it. There was a few other issues
> too that have been uncovered in the M7 shared above. So, planning to host a
> new pack as M7 replacing what's already there, shortly. The initial plan
> was to be done with it yesterday itself, but couldn't get a proper build
> out of Jenkins due to some build issue that we ran into. Will keep you guys
> informed once this is all done.
>
> Cheers,
> Prabath
>
> On Fri, Oct 23, 2015 at 11:28 AM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi
>>
>> As per our understanding the starting point of EMM which is device
>> enrolment happens in two ways
>>
>> 1. User addition
>> 2. Through QA code
>>
>> But both seem to be not working in the M7 pack. Please find the reported
>> jiras below. Is there a chance to get a new pack?
>>
>> [1] https://wso2.org/jira/browse/EMM-846
>> 
>> [2] https://wso2.org/jira/browse/EMM-845
>>
>> Thanks
>> Erandi
>>
>> On Wed, Oct 21, 2015 at 11:04 AM, Prabath Abeysekera 
>> wrote:
>>
>>> Guys,
>>>
>>> Please do report doc JIRAs (blockers) upon any missing pieces in the
>>> product documentation. That will help us keep track of things properly and
>>> fix them ASAP.
>>>
>>> Cheers,
>>> Prabath
>>>
>>> On Wed, Oct 21, 2015 at 10:41 AM, Shavindri Dissanayake <
>>> shavin...@wso2.com> wrote:
>>>
 Hi Chamara and Sashika,

 We do have a guide to set up the database [1]. It has details on
 setting up H2 [2] and MySQL [3]. Please do let me know if any areas in this
 doc needs to updated accordingly.

 Thank you for the heads up!

 [1] https://docs.wso2.com/display/EMM200/Working+with+Databases
 [2] https://docs.wso2.com/display/EMM200/Setting+up+H2
 [3] https://docs.wso2.com/display/EMM200/Setting+up+MySQL

 Thanks & Regards
 Shavindri Dissanayake
 Technical Writer

 WSO2 Inc.
 lean.enterprise.middleware

 On Wed, Oct 21, 2015 at 10:18 AM, Chamara Ariyarathne <
 chama...@wso2.com> wrote:

> Since there are several datasources to be configured, we need to have
> a guide on setting up databases for the product documentation.
>
> On Wed, Oct 21, 2015 at 10:09 AM, Sashika Wijesinghe  > wrote:
>
>> Hi All,
>>
>> I observed FileNotFoundException when starting a fresh pack with
>> mysql database [1] . Further there is a naming issue in WSO2AM_DS
>> datasource, same jndi config name is used for WSO2AM_DB and WSO2AM_DS 
>> [2].
>>
>> I have reported JIRA for above issues.
>>
>> [1] https://wso2.org/jira/browse/EMM-822
>> [2] https://wso2.org/jira/browse/EMM-823
>>
>> Regards,
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> *Chamara Ariyarathne*
> Associate Technical Lead - QA
> WSO2 Inc; http://www.wso2.com/
> Mobile; *+94772786766 <%2B94772786766>*
>


>>>
>>>
>>> --
>>> Prabath Abeysekara
>>> Technical Lead
>>> WSO2 Inc.
>>> Email: praba...@wso2.com
>>> Mobile: +94774171471
>>>
>>
>>
>>
>> --
>> *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
>



-- 
*Chamara Ariyarathne*
Associate Technical Lead - QA
WSO2 Inc; http://www.wso2.com/
Mobile; *+94772786766*
___
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-25 Thread Nayomi Dayarathne

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 
>
___
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-25 Thread Aparna Karunarathna

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

Re: [Dev] Configurator does not give priority to env variables

2015-10-25 Thread Imesh Gunaratne

Correct, configurator is giving priority to the environment variables. I
misunderstood it earlier.
Sorry for the confusion.

Thanks

On Mon, Oct 26, 2015 at 9:10 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi,
>
> By any chance if the values are commented out from the module.ini, only
>> env values will get populated.
>
>
> This is not the correct approach, the configurator should pick up the
> variables from template itself and then search for environment variables
> and module.ini.
>
> Users don't have to comment variables in module.ini.
>
> Please refer mail with subject *"PPaaS configurator doesn't pick all the
> payload parameters"* for more info.
>
> On Sat, Oct 24, 2015 at 11:43 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Imesh,
>>
>> I just checked the configurator. It gives the priority to env variables
>> before reading from module.ini. This should be the default approach.
>>
>> It would be more safe to define values within the template. By any chance
>> if the values are commented out from the module.ini, only env values will
>> get populated.
>>
>> Thank you!
>>
>> On Sat, Oct 24, 2015 at 10:33 PM, Gayan Gunarathne 
>> wrote:
>>
>>> So what is the usage of the "module.ini"? We can live with only the
>>> environment parameters.
>>>
>>> If the module.ini is for the default values, why are we having default
>>> values in the template it self.We are checking whether that value is
>>> defined. If that is not define we are setting the default value.
>>>
>>> [1]
>>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.8.1/template-module/templates/repository/conf/datasources/master-datasources.xml.template#L8
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Sat, Oct 24, 2015 at 10:00 PM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Devs,

 I noticed $subject if the same variable has been defined in module.ini.

 IMO this is not correct. We need to be able to configure any parameter
 using environment variables without touching the module.ini.

 Thanks

 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware


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


>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>> Committer & PMC Member, Apache Stratos
>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774079049 <%2B94772207163>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
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-25 Thread Malith Dhanushka

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

Re: [Dev] [IS] Way to store user tokens when writing an Autheticator

2015-10-25 Thread Chamara Philips

Considering the simultaneous login attempt, explained by Darshana, for same
account by different devices, AuthenticationContext would be the best
place. Note that this attempt may be from the owner of the user or by some
other. The AuthenticatorContext will be created when the flow is
initialized for the request.

A simple authenticator to get an idea for you would be FIDOAuthenticator
and FacebookAuthenticator.

+1 for AuthenticationContext.

Thanks,
Chamara Philips.

On Mon, Oct 26, 2015 at 9:15 AM, Darshana Gunawardana 
wrote:

> There can be situations where the same user simultaneously try to login
> with two devices which leads to having two valid tokens for a one user. So
> this token cannot be treated as an user's attribute; It should have more
> finer scope.
>
> And I assume these tokens are generated at the time SMSOTP authenticator
> get invoked on *each* authentication request. Hence I assume the token is
> valid only for that particular authentication request. Ideally these tokens
> should stored in a context specific to the Authenticator or to a Step.
> Since the current version of the authentication framework doesn't have such
> context, the best place to store these token is in the
> AuthenticationContext since the AuthneticationContext have the scope as the
> the full authentication flow.
>
> Hence,
>
> On Sun, Oct 25, 2015 at 6:00 PM, Malaka Silva  wrote:
>
>> Yes I guess we are referring to AuthiticationContext as caching here. I
>> also agree that it should be stored there.
>>
>
> +1 for storing user tokens on AuthenticationContext.
>
> Thanks,
> Darshana.
>
>
>
>
>>
>> On Sat, Oct 24, 2015 at 2:43 PM, Chamara Philips 
>> wrote:
>>
>>> Hi,
>>> Hope this token is generated by code and sent to the user's phone for
>>> him to input. Then you validate the user with WSO2 IS, matching the token.
>>> After he has used it once he can't use that again.
>>> Based on that assumption, I think the best option is to go with cache.
>>> Usually userstore is not used in scenarios like this.
>>> When you generate the new token for the same user you can update the
>>> cache and continue.
>>>
>>> Hope it helps.
>>>
>>> Thanks.
>>>
>>> On Sat, Oct 24, 2015 at 1:58 PM, Elilmatha Sivanesan >> > wrote:
>>>
 Hi

 I'm writing SMSOTP Authenticator for IS, For that I'm generating a
 token to be sent to the phone, I have the requirement to store that
 generated tokens.

 For that what is the best option to go with.(user store/cache/...).

 Thanks.
 --
 *S.Elilmatha*
 Associate  Software Engineer,

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

 Mobile 0779842221.


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


>>>
>>>
>>> --
>>> Hareendra Chamara Philips
>>> *Software  Engineer*
>>> Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
>>> chama...@wso2.com 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Hareendra Chamara Philips
*Software  Engineer*
Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
chama...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Possible Code Improvement in IOStreamUtils

2015-10-25 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

[Dev] [Architecture] WSO2 Message Broker 3.0.0 Beta Released !

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

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

Re: [Dev] [IS] Way to store user tokens when writing an Autheticator

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

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

[Dev] [ML] Identified Limitations - Pipeline PoC

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

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

[Dev] BAM Cluster. Need some guide.

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

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

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

Re: [Dev] Configurator does not give priority to env variables

Re: [Dev] WSO2EMM 2.0.0 Milestone 7 Released

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

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

Re: [Dev] Configurator does not give priority to env variables

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

Re: [Dev] [IS] Way to store user tokens when writing an Autheticator

[Dev] Possible Code Improvement in IOStreamUtils

22 matches

Site Navigation

Mail list logo

Footer information