date:20151218

[Dev] App Manager 1.1.0 latest build pack - 18-12-2015

2015-12-18 Thread Dinusha Senanayaka

Hi,

Please find $subject in [1].

[1].
http://builder1.us1.wso2.org/~appm/release-1.1.0/18-12-2015/wso2appm-1.1.0-SNAPSHOT-18-12-2015.zip

Regards,
Dinusha.

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

Re: [Dev] UUF/Jaggery - unformatted error

2015-12-18 Thread Sumedha Rubasinghe

Malithi,
Can we fix this? If not errors from Jaggery are not readable.

On Fri, Dec 18, 2015 at 2:37 PM, Sajith Ariyarathna 
wrote:

> Hi Sumedha,
>
> This happens due to a security fix done for Carbon 4.4.2. Please refer Dev
> mail thread [1].
>
>
> [1] [Dev] Issue in carbon logs after changing carbon.kernel.version from
> 4.4.1 to 4.4.2
>
> Thanks.
>
>
> On Fri, Dec 18, 2015 at 1:12 PM, Sumedha Rubasinghe 
> wrote:
>
>> Sajith,
>> What is the reason for following exception to be printed in an
>> unformatted manner?
>>
>> >
>>
>> [2015-12-18 13:01:35,127] ERROR {JAGGERY.config.app:js} -
>>  org.mozilla.javascript.WrappedException: Wrapped
>> java.lang.ArrayIndexOutOfBoundsException: 1
>> (/publisher/modules/data/driver.js#40)_ at
>> org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)_ at
>> org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)_ at
>> org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)_ at
>> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)_ at
>> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c4._c_anonymous_4(/publisher/modules/data/driver.js:40)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c4.call(/publisher/modules/data/driver.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_10(/publisher/modules/data/model.manager.js:104)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)_ at
>> org.jaggeryjs.rhino..scripts.c0._c_anonymous_17(/scripts/server.js:266)_
>>  at
>> org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)_ at
>> org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)_ at
>> org.jaggeryjs.rhino..scripts.c0._c_anonymous_16(/scripts/server.js:246)_
>>  at
>> org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)_ at
>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_9(/publisher/modules/data/model.manager.js:103)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_17(/publisher/modules/data/model.manager.js:151)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_5(/publisher/modules/data/model.manager.js:76)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_4(/publisher/modules/data/model.manager.js:42)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>> org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_3(/publisher/modules/data/model.manager.js:40)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_ModelManager_2(/publisher/modules/data/model.manager.js:24)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>  at
>> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:338)_ at
>> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c0._c_anonymous_3(/publisher/modules/data/storage.js:74)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c0.call(/publisher/modules/data/storage.js)_
>>  at
>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
>> org.jaggeryjs.rhino.publisher.modules.data.c0._c_StorageManager_2(/publisher/modules/data/storage.js:54)_
>>  at
>> org.jaggeryjs.rhino.publisher.modules.data.c0.call(/publisher/modules/data/storage.js)_
>>  at
>> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:338)_ at
>>

[Dev] "No bam.xml" - Is this required to be present when embedding DAS?

2015-12-18 Thread Sumedha Rubasinghe

Getting following error.

[2015-12-18 15:33:57,538]  WARN
{org.wso2.carbon.bam.service.data.publisher.internal.StatisticsServiceComponent}
-  No bam.xml found in
/Volumes/data/projects/wso2/iot-server/src/product-iot-server/modules/distribution/target/wso2iot-1.0.0-SNAPSHOT/repository/conf/etc/bam.xml
[2015-12-18 15:33:57,538]  WARN
{org.wso2.carbon.bam.service.data.publisher.internal.StatisticsServiceComponent}
-  Invalid bam.xml. Disabling service publishing.


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

Re: [Dev] UUF/Jaggery - unformatted error

2015-12-18 Thread Sajith Ariyarathna

Hi Sumedha,

This happens due to a security fix done for Carbon 4.4.2. Please refer Dev
mail thread [1].


[1] [Dev] Issue in carbon logs after changing carbon.kernel.version from
4.4.1 to 4.4.2

Thanks.


On Fri, Dec 18, 2015 at 1:12 PM, Sumedha Rubasinghe 
wrote:

> Sajith,
> What is the reason for following exception to be printed in an unformatted
> manner?
>
> >
>
> [2015-12-18 13:01:35,127] ERROR {JAGGERY.config.app:js} -
>  org.mozilla.javascript.WrappedException: Wrapped
> java.lang.ArrayIndexOutOfBoundsException: 1
> (/publisher/modules/data/driver.js#40)_ at
> org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)_ at
> org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)_ at
> org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)_ at
> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)_ at
> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c4._c_anonymous_4(/publisher/modules/data/driver.js:40)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c4.call(/publisher/modules/data/driver.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_10(/publisher/modules/data/model.manager.js:104)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)_ at
> org.jaggeryjs.rhino..scripts.c0._c_anonymous_17(/scripts/server.js:266)_
>  at
> org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)_ at
> org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)_ at
> org.jaggeryjs.rhino..scripts.c0._c_anonymous_16(/scripts/server.js:246)_
>  at
> org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)_ at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_9(/publisher/modules/data/model.manager.js:103)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_17(/publisher/modules/data/model.manager.js:151)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_5(/publisher/modules/data/model.manager.js:76)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_4(/publisher/modules/data/model.manager.js:42)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
> org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)_
>  at
> org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)_ 
> at
> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_3(/publisher/modules/data/model.manager.js:40)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c1._c_ModelManager_2(/publisher/modules/data/model.manager.js:24)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>  at
> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:338)_ at
> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c0._c_anonymous_3(/publisher/modules/data/storage.js:74)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c0.call(/publisher/modules/data/storage.js)_
>  at
> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ at
> org.jaggeryjs.rhino.publisher.modules.data.c0._c_StorageManager_2(/publisher/modules/data/storage.js:54)_
>  at
> org.jaggeryjs.rhino.publisher.modules.data.c0.call(/publisher/modules/data/storage.js)_
>  at
> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:338)_ at
> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
> org.jaggeryjs.rhino.publisher.modules.c7._c_Deployer_2(/publisher/modules/asset.deployment.js:50)_
>  at
> org.jaggeryjs.rhino.publisher.modules.c7.call(/publisher/modules/asset.deployment.js)_
>  at
>

Re: [Dev] [DS][DAS] Sample for DashboardServer - How to get back-end url, username, password for DAS to invoke DAS rest API from jaggery file

2015-12-18 Thread Isuru Wijesinghe

Hi Rajeenthini,

Can't you hold a configuration file at the back-end side for this ?? Here
what I mean is something similar to below example. In the url tag you
should have to keep the base url of the DAS. The rest of the part of the
url u can append from the code. (Please note that if you keep a property
file like below, you should have to add secure vault also. It  is used to
secure plain text password which is contains in configuration  files of
WSO2 products).  And then you can read it from your jaggery code . (see
http://jaggeryjs.org/documentation.jag?api=file)
eg:

http://wso2.org/pc/config;>

https://localhost:9445/
admin
admin




On Fri, Dec 18, 2015 at 12:33 PM, Supun Sethunga  wrote:

> Hi Rajeenthini,
>
> Instead of the DAS REST API, you can use the "Analytics javascript API"
> [1]. This should eliminate the requirement of needing user-credentials. (or
> doesn't need to send an Authorization header)
>
> [1] https://docs.wso2.com/display/DAS300/Analytics+JavaScript+(JS)+API
>
> Regards,
> Supun
>
> On Fri, Dec 18, 2015 at 10:41 AM, Rajeenthini Satkunam <
> rajeenth...@wso2.com> wrote:
>
>> Hi all,
>>
>> Currently I am working on creating sample for dashboard server with DAS
>> integration.I need to invoke DAS rest API from Jaggery file(sample.jag) to
>> get some data.As per documentation[1] of DAS rest API we need to send
>> authorization header along with request to fetch data from DAS. So for
>> workaround I have hard-coded the username password values to variable and
>> concatenate them as username + ":" + password and encoded them then send as
>> a authorization header.Here I need to get server username and
>> password(credentials).IMHO it is not good practice that hard-coding
>> credentials of server.
>> I have shared my Jaggery code below
>>
>> try {
>> var username = "admin";//hard-coded value of username
>> var password = "admin";//hard-coded value of password
>> var tableName = request.getParameter("tableName");
>> var query = request.getParameter("query");
>> var url = "https://localhost:9465/analytics/search;;
>> var encoderJavaPkg = Packages.javax.xml.bind.DatatypeConverter;
>> var bytes = [];
>> var encodeString = username + ":" + password;
>> for (var i = 0; i < encodeString.length; ++i) {
>> bytes.push(encodeString.charCodeAt(i));
>> }
>> var authHeader = "Basic " + encoderJavaPkg.printBase64Binary(bytes);
>> var result = post(url, stringify({
>> "tableName": tableName,
>> "start": 0,
>> "count": 100,
>> "query": query
>> }), {"Authorization": authHeader, "Content-Type": "application/json"}, 
>> "application/json");
>> print(result.data);
>> } catch (e) {
>> log.info(e);
>> }
>>
>> [1] - 
>> https://docs.wso2.com/display/DAS300/Retrieving+All+Records+Matching+the+Given+Search+Query+via+REST+API
>>
>> As for now to start both server (DAS and DS) I have changed offset value for 
>> DAS as "2" in carbon.xml.I can successfully start both server 
>> simultaneously.It will be very useful if I can get the back-end URL and 
>> server credentials of DAS and get rid of hard-coding those values.Can anyone 
>> please help me and your suggestions mostly appreciate?
>>
>>
>>
>>
>> --
>>
>> *Thank You.*
>>
>> *Rajeenthini Satkunam*
>>
>> *Associate Software Engineer | WSO2*
>>
>>
>> *E:rajeenth...@wso2.com *
>>
>> *M :+94770832823 <%2B94770832823>   *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Supun Sethunga*
> Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC2

2015-12-18 Thread Maheshakya Wijewardena

Hi Devs,

This is the 2nd Release Candidate of WSO2 Machine Learner 1.1.0.

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

Please download, test and vote. Vote will be open for 72 hours or as longer
as needed.

*Binary distribution files:*
https://github.com/wso2/product-ml/releases/download/v1.1.0-rc2/wso2ml-1.1.0.zip

*P2 repository*:
https://github.com/wso2/product-ml/releases/download/v1.1.0-rc2/p2-repo.zip


*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2ml-208/


*The tag to be voted upon:*
https://github.com/wso2/product-ml/tree/v1.1.0-rc2


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

Thank you,
Machine Learner Team

-- 
Pruthuvi Maheshakya Wijewardena
mahesha...@wso2.com
+94711228855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can we suppress DAS message for schedule task execution?

2015-12-18 Thread Niranda Perera

Hi Sumedha,

Yes, this was reported here and will be fixed in the coming patch release.
[1]

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

On Fri, Dec 18, 2015 at 1:18 PM, Sumedha Rubasinghe 
wrote:

> It can fill up the logs quite easily when there are lot of scheduled
> scripts running @ low intervals.
>
> As an alternative,
> Make it a DEBUG & have an UI option to see when was the script last ran.
>
>
> eg:
>
> [2015-12-18 13:05:34,067]  INFO
> {org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -
>  Subscribed with client id: f9560:virtual_firealarm
> [2015-12-18 13:05:34,067]  INFO
> {org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -
>  Subscribed to topic: WSO2IoTServer/+/virtual_firealarm/+/publisher
> [2015-12-18 13:06:00,002]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Accelerometer_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,002]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Battery_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,003]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: GPS_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,004]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Gravity_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,004]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Gyroscope_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,005]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Light_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,006]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Magnetic_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,006]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Pressure_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,007]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Proximity_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,008]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Rotation_Sensor_Script for tenant id: -1234
> [2015-12-18 13:06:00,008]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Temperature_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,001]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Accelerometer_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,001]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Battery_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,002]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: GPS_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,002]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Gravity_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,003]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Gyroscope_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,004]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Light_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,004]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Magnetic_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,004]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Pressure_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,005]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Proximity_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,005]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Rotation_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:00,006]  INFO
> {org.wso2.carbon.analytics.spark.core.AnalyticsTask} -  Executing the
> schedule task for: Temperature_Sensor_Script for tenant id: -1234
> [2015-12-18 13:07:28,405] ERROR
> {org.eclipse.paho.client.mqttv3.internal.ClientState} -  b942b:raspberrypi:
> Timed out as no activity, keepAlive=60,000
> lastOutboundActivity=1,450,424,128,407 lastInboundActivity=1,450,424,068,623
> [2015-12-18 13:07:28,406]  WARN
> {org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -  Lost
> Connection for client: b942b:raspberrypi to tcp://204.232.188.214:1883._This
> was due to - Timed out waiting for a response

[Dev] [Architecture] WSO2 Message Broker 3.1.0 Milestone 2 Released !

2015-12-18 Thread Akalanka Pagoda Arachchi

Hi All,

The WSO2 Message Broker team is pleased to announce the 2nd milestone
release of WSO2 Message Broker (MB)  3.1.0.

You can download this distribution from [1].
All the known issues identified are listed in JIRA.[2].

Following are the bug fixes, improvements and the new features included in
this milestone release.

Bug

   - [MB-1089 ] - [Cluster] Hazelcast
   issue in server startup
   - [MB-1374 ] - Data in
   MB_QUEUE_MAPPING table not removed when deleting a Queue
   - [MB-1433 ] - Publishers can
   publish messages to queues even though those queues do not exist
   - [MB-1577 ] - Node ID becomes
   null if the network link between two nodes fails and comes again

Improvement

   - [MB-1584 ] - Change
   slotRetainTimeInMemory property in broker.xml in to a meaningful name

Task

   - [MB-1594 ] - Upgrade MB Carbon
   Kernel Version to 4.4.3


[1] - https://github.com/wso2/product-mb/releases/tag/v3.1.0-M2
[2] - https://wso2.org/jira/browse/MB-424?filter=12509

Regards,
MB Team.

-- 
*Darshana Akalanka Pagoda Arachchi,*
*Software Engineer*
*078-4721791*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][BRS][Release] WSO2 Business Rule Server (WSO2 BRS) 2.2.0 - Beta2 Released!

2015-12-18 Thread Milinda Perera

*WSO2 Business Rule Server (WSO2 BRS) 2.2.0 - Beta2 Released*

Date :  18th December 2015

The WSO2 BPS/BRS team is pleased to announce the Beta2 release of WSO2 BRS
v2.2.0.

The WSO2 Business Rules Server brings the agility of business rules to your
SOA toolkit. Based on a solid platform for hosting business rules, our
Business Rules Server excels at extending the capabilities of your SOA.
Allowing business rules to be encapsulated in a simpler, more direct
dialect and language closer to business analysts, ensures that the
technology directly meets the enterprise’s business needs.

Interested in playing with an early release? Download the latest beta2 release
! : WSO2 BRS 2.2.0-Beta2

[1].

Source of WSO2 BRS v2.2.0-Beta2 can be found in [2]
 and latest
development updates can be found in our product development Git
Repositories [3]  [4]
.

Release Notes - WSO2 Business Rule Server - Version 2.2.0 Beta2


*Issues Fixed for this release*

   *Improvements*

   - [BRS-130 ] - [Rule Serivice
   Deployment][Rule Wizard] rule service creation with inline rule script for
   decision tables
   - [BRS-131 ] - [Rule Service
   Deployment] Provide support to create decision table based rule service
   using .csv files


*Known Issues*

Jira:issues:brs


*How To Contribute*


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

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

*Reporting Problems*

Issues can be reported using the BRS public JIRA available at :
https://wso2.org/jira/browse/BRS

*Contact us*

WSO2 developers can be contacted via the mailing list: Carbon developer
mailing list 
For details on subscriptions see http://wso2.org/mail




*- The WSO2 BPS/BRS Team -*
[1]
https://github.com/wso2/product-brs/releases/download/v2.2.0-BETA2/wso2brs-2.2.0-beta2.zip
[2] https://github.com/wso2/product-brs/archive/v2.2.0-BETA2.zip
[3] https://github.com/wso2/carbon-rules
[4] https://github.com/wso2/product-brs
[5] https://docs.wso2.com/display/BRS220/Get+Involved


-- 
Milinda Perera
Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue while using the special characters in url-template with legacy encoding.

2015-12-18 Thread Kathees Rajendram

Hi,

I created uri.var.status property and used the property in url-template with
legacy encoding. Remaining part of URL is removed with the special
character.







*Request* - sample #test

*Output*

[2015-12-18 16:45:47,269] DEBUG - wire << "POST
/1.1/statuses/update.json?status=sample%20 HTTP/1.1[\r][\n]"
[2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
en-US,en;q=0.8[\r][\n]"

*Expected output*

[2015-12-18 16:45:47,269] DEBUG - wire << "POST
/1.1/statuses/update.json?status=sample%20%23test HTTP/1.1[\r][\n]"
[2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
en-US,en;q=0.8[\r][\n]"

What could be the reason?

Thanks,
Kathees

-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Carbon Kernel 5.0.0 RC2

2015-12-18 Thread Kishanthan Thangarajah

Hi Devs,

This is the 2nd Release Candidate of WSO2 Carbon Kernel 5.0.0.

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

Please download and test your products with kernel 5.0.0 RC2 and vote.

*Source and binary distribution files:*
https://github.com/wso2/carbon-kernel/releases/download/v5.0.0-RC2/wso2carbon-kernel-5.0.0-rc2.zip

*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-210/

*The tag to be voted upon:*
https://github.com/wso2/carbon-kernel/releases/tag/v5.0.0-RC2


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

Thank you,
Carbon Team

-- 
*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] Clarification on OUT_ONLY ESB proxy service scenario

2015-12-18 Thread Anupama Pathirage

Hi team,

I get the following exception when I run the Sample 150 (Introduction to
Proxy Services) in the WSO2 ESB 4.9.0 as mentioned in the [1
]
with the client mode "placeorder" even though the order is placed correctly
in the back end service.

*Client Command used:*
ant stockquote -Daddurl=http://localhost:8280/services/StockQuoteProxy
-Dmode=placeorder -Dsymbol=MSFT

*ESB Exception:*
[2015-12-18 17:00:04,072] ERROR - NativeWorkerPool Uncaught exception
java.lang.UnsupportedOperationException: An access occurred that is not
valid.
at
org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:117)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:299)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Since “PlaceOrder” is a method which does not return anything as a response
for a request, it was possible to avoid this exception by setting the
property OUT_ONLY for the in sequence as follows [2
].





But this make the other client modes such as "quote" not working because it
is trying to send a request which expects a response through an OUT_ONLY
proxy which must be wrong in theoretically. So can you please let me know
the proper way of handling above ESB exception while providing the support
for both types of operations.


[1]
https://docs.wso2.com/display/ESB490/Sample+150%3A+Introduction+to+Proxy+Services
[2] https://docs.wso2.com/display/ESB403/Generic+Properties

Thanks and Regards,
-- 
Anupama Pathirage
Associate Technical Lead
WSO2, Inc.  http://wso2.com/
Email: anup...@wso2.com
Mobile:+94 71 8273 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Transports can't be stopped and start in MSS

2015-12-18 Thread Aruna Karunarathna

Hi,

I tried to stop the jaxrs-http transport in MSS and tried to start and
ended up with the following exception. Seems like a bug in MSS?

osgi> listTransports
Transport Name: jaxrs-http State: STARTED
osgi>
osgi>
osgi> stopTransport jaxrs-http
[2015-12-18 18:18:54,729]  INFO
{org.wso2.carbon.transport.http.netty.listener.NettyListener} - Stopping
Netty transport jaxrs-http on port 8080
osgi>
osgi>
osgi> [2015-12-18 18:18:59,155]  INFO
{org.wso2.carbon.transport.http.netty.listener.NettyListener} - Netty
transport jaxrs-http on port 8080 stopped successfully
osgi>
osgi> listTransports
Transport Name: jaxrs-http State: STOPPED
osgi>
osgi>
osgi> startTransport jaxrs-http
[2015-12-18 18:19:17,378]  INFO
{org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
Netty Http Transport Listener
[2015-12-18 18:19:17,380]  WARN {io.netty.channel.AbstractChannel} -
Force-closing a channel whose registration task was not accepted by an
event loop: [id: 0xafe9e0b1]
java.util.concurrent.RejectedExecutionException: event executor terminated
at
io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:706)
at
io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:298)
at
io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:689)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.register(AbstractChannel.java:421)
at
io.netty.channel.SingleThreadEventLoop.register(SingleThreadEventLoop.java:60)
at
io.netty.channel.SingleThreadEventLoop.register(SingleThreadEventLoop.java:48)
at
io.netty.channel.MultithreadEventLoopGroup.register(MultithreadEventLoopGroup.java:64)
at
io.netty.bootstrap.AbstractBootstrap.initAndRegister(AbstractBootstrap.java:315)
at io.netty.bootstrap.AbstractBootstrap.doBind(AbstractBootstrap.java:271)
at io.netty.bootstrap.AbstractBootstrap.bind(AbstractBootstrap.java:267)
at
org.wso2.carbon.transport.http.netty.listener.NettyListener.startTransport(NettyListener.java:81)
at
org.wso2.carbon.transport.http.netty.listener.NettyListener.start(NettyListener.java:61)
at
org.wso2.carbon.kernel.transports.CarbonTransport.startTransport(CarbonTransport.java:47)
at
org.wso2.carbon.kernel.transports.TransportManager.startTransport(TransportManager.java:46)
at
org.wso2.carbon.kernel.internal.transports.TransportMgtCommandProvider._startTransport(TransportMgtCommandProvider.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
org.eclipse.equinox.console.command.adapter.CommandProviderAdapter.main(CommandProviderAdapter.java:47)
at
org.eclipse.equinox.console.command.adapter.CommandProviderAdapter._main(CommandProviderAdapter.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
at org.apache.felix.gogo.shell.Console.run(Console.java:62)
at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
at
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
at java.lang.Thread.run(Thread.java:745)

gogo: RejectedExecutionException: event executor terminated
osgi>

Re: [Dev] UUF/Jaggery - unformatted error

2015-12-18 Thread Malithi Edirisinghe

Hi Sumedha,

We are sanitizing only the logging message. In Jaggery, stack traces are
sanitized since log.error(e); is used rather than log.error(message, e);.
This is also discussed at [1]. I think this should be fixed from jaggery
code.

[1] [Dev] Issue in carbon logs after changing carbon.kernel.version from 4.4
.1 to 4.4.2

Thanks,
Malithi.

On Fri, Dec 18, 2015 at 3:59 AM, Sumedha Rubasinghe 
wrote:

> Malithi,
> Can we fix this? If not errors from Jaggery are not readable.
>
> On Fri, Dec 18, 2015 at 2:37 PM, Sajith Ariyarathna 
> wrote:
>
>> Hi Sumedha,
>>
>> This happens due to a security fix done for Carbon 4.4.2. Please refer
>> Dev mail thread [1].
>>
>>
>> [1] [Dev] Issue in carbon logs after changing carbon.kernel.version from
>> 4.4.1 to 4.4.2
>>
>> Thanks.
>>
>>
>> On Fri, Dec 18, 2015 at 1:12 PM, Sumedha Rubasinghe 
>> wrote:
>>
>>> Sajith,
>>> What is the reason for following exception to be printed in an
>>> unformatted manner?
>>>
>>> >
>>>
>>> [2015-12-18 13:01:35,127] ERROR {JAGGERY.config.app:js} -
>>>  org.mozilla.javascript.WrappedException: Wrapped
>>> java.lang.ArrayIndexOutOfBoundsException: 1
>>> (/publisher/modules/data/driver.js#40)_ at
>>> org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)_ at
>>> org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)_ at
>>> org.mozilla.javascript.FunctionObject.call(FunctionObject.java:392)_ at
>>> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:343)_ at
>>> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
>>> org.jaggeryjs.rhino.publisher.modules.data.c4._c_anonymous_4(/publisher/modules/data/driver.js:40)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c4.call(/publisher/modules/data/driver.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_10(/publisher/modules/data/model.manager.js:104)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)_ at
>>> org.jaggeryjs.rhino..scripts.c0._c_anonymous_17(/scripts/server.js:266)_
>>>  at
>>> org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)_ at
>>> org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)_ at
>>> org.jaggeryjs.rhino..scripts.c0._c_anonymous_16(/scripts/server.js:246)_
>>>  at
>>> org.jaggeryjs.rhino..scripts.c0.call(/scripts/server.js)_ at
>>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_9(/publisher/modules/data/model.manager.js:103)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ 
>>> at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_17(/publisher/modules/data/model.manager.js:151)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ 
>>> at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_5(/publisher/modules/data/model.manager.js:76)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_4(/publisher/modules/data/model.manager.js:42)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>>> org.jaggeryjs.rhino.publisher.modules.c8._c_anonymous_13(/publisher/modules/bundler.js:168)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.c8.call(/publisher/modules/bundler.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)_ at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_anonymous_3(/publisher/modules/data/model.manager.js:40)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:85)_ 
>>> at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1._c_ModelManager_2(/publisher/modules/data/model.manager.js:24)_
>>>  at
>>> org.jaggeryjs.rhino.publisher.modules.data.c1.call(/publisher/modules/data/model.manager.js)_
>>>  at
>>> org.mozilla.javascript.BaseFunction.construct(BaseFunction.java:338)_ at
>>> org.mozilla.javascript.ScriptRuntime.newObject(ScriptRuntime.java:2349)_ at
>>> org.jaggeryjs.rhino.publisher.modules.data.c0._c_anonymous_3(/publisher/modules/data/storage.js:74)_
>>>  at

Re: [Dev] Transports can't be stopped and start in MSS

2015-12-18 Thread Samiyuru Senarathne

This issue occurs because in carbon-transport when restarting a
transport bossGroup
and workerGroup is attempted to reuse after they were stopped.
Reinitializing them when transport is again started will fix the issue.

Following pull request was sent to fix the issue:
https://github.com/wso2/carbon-transports/pull/15
Best Regards,
Samiyuru

On Fri, Dec 18, 2015 at 6:26 PM, Aruna Karunarathna  wrote:

> Hi,
>
> I tried to stop the jaxrs-http transport in MSS and tried to start and
> ended up with the following exception. Seems like a bug in MSS?
>
> osgi> listTransports
> Transport Name: jaxrs-http State: STARTED
> osgi>
> osgi>
> osgi> stopTransport jaxrs-http
> [2015-12-18 18:18:54,729]  INFO
> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Stopping
> Netty transport jaxrs-http on port 8080
> osgi>
> osgi>
> osgi> [2015-12-18 18:18:59,155]  INFO
> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Netty
> transport jaxrs-http on port 8080 stopped successfully
> osgi>
> osgi> listTransports
> Transport Name: jaxrs-http State: STOPPED
> osgi>
> osgi>
> osgi> startTransport jaxrs-http
> [2015-12-18 18:19:17,378]  INFO
> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
> Netty Http Transport Listener
> [2015-12-18 18:19:17,380]  WARN {io.netty.channel.AbstractChannel} -
> Force-closing a channel whose registration task was not accepted by an
> event loop: [id: 0xafe9e0b1]
> java.util.concurrent.RejectedExecutionException: event executor terminated
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:706)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:298)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:689)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.register(AbstractChannel.java:421)
> at
> io.netty.channel.SingleThreadEventLoop.register(SingleThreadEventLoop.java:60)
> at
> io.netty.channel.SingleThreadEventLoop.register(SingleThreadEventLoop.java:48)
> at
> io.netty.channel.MultithreadEventLoopGroup.register(MultithreadEventLoopGroup.java:64)
> at
> io.netty.bootstrap.AbstractBootstrap.initAndRegister(AbstractBootstrap.java:315)
> at io.netty.bootstrap.AbstractBootstrap.doBind(AbstractBootstrap.java:271)
> at io.netty.bootstrap.AbstractBootstrap.bind(AbstractBootstrap.java:267)
> at
> org.wso2.carbon.transport.http.netty.listener.NettyListener.startTransport(NettyListener.java:81)
> at
> org.wso2.carbon.transport.http.netty.listener.NettyListener.start(NettyListener.java:61)
> at
> org.wso2.carbon.kernel.transports.CarbonTransport.startTransport(CarbonTransport.java:47)
> at
> org.wso2.carbon.kernel.transports.TransportManager.startTransport(TransportManager.java:46)
> at
> org.wso2.carbon.kernel.internal.transports.TransportMgtCommandProvider._startTransport(TransportMgtCommandProvider.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at
> org.eclipse.equinox.console.command.adapter.CommandProviderAdapter.main(CommandProviderAdapter.java:47)
> at
> org.eclipse.equinox.console.command.adapter.CommandProviderAdapter._main(CommandProviderAdapter.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at org.apache.felix.gogo.shell.Console.run(Console.java:62)
> at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
> at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> at

Re: [Dev] Issue while using the special characters in url-template with legacy encoding.

2015-12-18 Thread Malaka Silva

Hi Kathees,

Can you try debugging [1] and try to figure out the issues?

May be the issues it in  'String decodedString =
URLDecoder.decode(template.expand(), "UTF-8");'

[1]
https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/endpoints/HTTPEndpoint.java

On Fri, Dec 18, 2015 at 4:59 PM, Kathees Rajendram  wrote:

> Hi,
>
> I created uri.var.status property and used the property in url-template with
> legacy encoding. Remaining part of URL is removed with the special
> character.
>
> 
> 
> 
> uri-template="legacy-encoding:{uri.var.apiUrl}/1.1/statuses/update.json?{uri.var.status}"/>
> 
> 
>
> *Request* - sample #test
>
> *Output*
>
> [2015-12-18 16:45:47,269] DEBUG - wire << "POST
> /1.1/statuses/update.json?status=sample%20 HTTP/1.1[\r][\n]"
> [2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
> en-US,en;q=0.8[\r][\n]"
>
> *Expected output*
>
> [2015-12-18 16:45:47,269] DEBUG - wire << "POST
> /1.1/statuses/update.json?status=sample%20%23test HTTP/1.1[\r][\n]"
> [2015-12-18 16:45:47,269] DEBUG - wire << "Accept-Language:
> en-US,en;q=0.8[\r][\n]"
>
> What could be the reason?
>
> Thanks,
> Kathees
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>



-- 

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

[Dev] WSO2 Private PaaS Cartridges v4.1.3 released

2015-12-18 Thread Gayan Gunarathne

Hi All,

The WSO2 Private PaaS community is pleased to announce the release of the
WSO2 Private PaaS Cartridges 4.1.3. This release includes cartridges for
the following WSO2 products.

 - WSO2 API Manager 1.9.1 cartridge
 - WSO2 Enterprise Service Bus 4.8.1 cartridge
 - WSO2 Enterprise Service Bus 4.9.0 cartridge
 - WSO2 Identity Server 5.0.0 cartridge
 - WSO2 Application Server 5.2.1 cartridge
 - WSO2 Application Server 5.3.0 cartridge
 - WSO2 Govenence Registry 5.0.0 cartridge
 - WSO2 Business Process Server 3.5.0 cartridge
 - WSO2 Business Rules Server 2.1.0 cartridge
 - WSO2 Governance Registry 5.0.0 cartridge
 - WSO2 Governance Registry 5.1.0 cartridge
 - WSO2 Data Services Server 3.2.2 cartridge
 - WSO2 Message Broker 3.0.0 cartridge
 - WSO2 Complex Event Processor 4.0.0 cartridge

Following are the newly added cartridges for this release
 - WSO2 Complex Event Processor 4.0.0 cartridge

Please note that above cartridges and Docker files are compatible with WSO2
Private PaaS 4.1.0 or higher releases.

Your feedback is most welcome. The distributions are available at [1]. Any
issues can be reported in [2].


[1]
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-cartridges-4.1.3/
[2] https://wso2.org/jira/browse/PPC

Thanks,
WSO2 Private PaaS Team

-- 

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

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

2015-12-18 Thread Gayan Gunarathne

This vote has been cancelled due to CEP 3.0.0 artifacts issue and will
start a RC2 release with those fixes.

Thanks,
Gayan

On Fri, Dec 18, 2015 at 11:05 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> Private PaaS distribution pack is missing cep artifacts because in ppaas
> distribution assembly [1] we are referring those artifacts from ppaas cep
> extension which has been removed from ppaas repo. Ideally we should refer
> these cep artifacts in [1] from Stratos [2].
>
> [1].
> https://github.com/wso2/product-private-paas/blob/release-4.1.1/products/ppaas/modules/distribution/src/assembly/bin.xml#L430-L463
>
> [2].
> https://github.com/apache/stratos/tree/stratos-4.1.x/extensions/cep/modules/artifacts/wso2cep-3.0.0
>
> Thanks.
>
> On Wed, Dec 16, 2015 at 11:32 AM, Gayan Gunarathne 
> wrote:
>
>>  Hi All,
>>
>> This is the first release candidate of WSO2 Private PaaS 4.1.1.
>>
>> This release fixes the following issues:
>> *https://wso2.org/jira/browse/PAAS-305?filter=12582
>> *
>>
>> Please download, test and vote. The vote will be open for 72 hours or as
>> needed.
>>
>> *Source and binary distribution files:*
>> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc1/
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-181/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thanks,
>> The WSO2 Private PaaS Team
>>
>> --
>>
>> 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
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 

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

[Dev] APIM 1.10.0 latest pack - 18-12-2015

2015-12-18 Thread Chamila Adhikarinayake

Hi,
Please find the latest pack and p2 repo from [1]
[1] https://svn.wso2.org/repos/wso2/scratch/apim/builds/18-12-2015/

Thanks,
Chamila

-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification on OUT_ONLY ESB proxy service scenario

2015-12-18 Thread Vijitha Ekanayake

Hi Anupama,

We set *OUT_ONLY *property to "true" on a message to indicate that no
response message is expected for it once it is forwarded from the ESB. This
prevents  the ESB from registering unnecessary callbacks for response
handling.

One possible option to get sample working for client modes, We can check
the header value and change synapse configuration accordingly. We can
support for both types of operations by using config[1].


[1].

http://ws.apache.org/ns/synapse; name="StockQuoteProxy"
transports="https,http" statistics="disable" trace="disable"
startOnLoad="true">
   
  
 http://www.w3.org/2005/08/addressing;
source="$header/wsa:Action" regex="urn:placeOrder">

   

 
  
  
 
  
  
 http://localhost:9000/services/SimpleStockQuoteService; />
  
   
   
   


Thanks,

Vijitha.


On Fri, Dec 18, 2015 at 6:00 PM, Anupama Pathirage  wrote:

>
> Hi team,
>
> I get the following exception when I run the Sample 150 (Introduction to
> Proxy Services) in the WSO2 ESB 4.9.0 as mentioned in the [1
> ]
> with the client mode "placeorder" even though the order is placed correctly
> in the back end service.
>
> *Client Command used:*
> ant stockquote -Daddurl=http://localhost:8280/services/StockQuoteProxy
> -Dmode=placeorder -Dsymbol=MSFT
>
> *ESB Exception:*
> [2015-12-18 17:00:04,072] ERROR - NativeWorkerPool Uncaught exception
> java.lang.UnsupportedOperationException: An access occurred that is not
> valid.
> at
> org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:117)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:299)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> Since “PlaceOrder” is a method which does not return anything as a
> response for a request, it was possible to avoid this exception by setting
> the property OUT_ONLY for the in sequence as follows [2
> ].
>
> 
> 
> 
>
> But this make the other client modes such as "quote" not working because
> it is trying to send a request which expects a response through an OUT_ONLY
> proxy which must be wrong in theoretically. So can you please let me know
> the proper way of handling above ESB exception while providing the support
> for both types of operations.
>
>
> [1]
> https://docs.wso2.com/display/ESB490/Sample+150%3A+Introduction+to+Proxy+Services
> [2] https://docs.wso2.com/display/ESB403/Generic+Properties
>
> Thanks and Regards,
> --
> Anupama Pathirage
> Associate Technical Lead
> WSO2, Inc.  http://wso2.com/
> Email: anup...@wso2.com
> Mobile:+94 71 8273 979
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vijitha Ekanayake
Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

2015-12-18 Thread Thanuja Uruththirakodeeswaran

Hi All,

Private PaaS distribution pack is missing cep artifacts because in ppaas
distribution assembly [1] we are referring those artifacts from ppaas cep
extension which has been removed from ppaas repo. Ideally we should refer
these cep artifacts in [1] from Stratos [2].

[1].
https://github.com/wso2/product-private-paas/blob/release-4.1.1/products/ppaas/modules/distribution/src/assembly/bin.xml#L430-L463

[2].
https://github.com/apache/stratos/tree/stratos-4.1.x/extensions/cep/modules/artifacts/wso2cep-3.0.0

Thanks.

On Wed, Dec 16, 2015 at 11:32 AM, Gayan Gunarathne  wrote:

>  Hi All,
>
> This is the first release candidate of WSO2 Private PaaS 4.1.1.
>
> This release fixes the following issues:
> *https://wso2.org/jira/browse/PAAS-305?filter=12582
> *
>
> Please download, test and vote. The vote will be open for 72 hours or as
> needed.
>
> *Source and binary distribution files:*
> https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc1/
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-181/
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-private-paas/tree/v4.1.1-rc1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thanks,
> The WSO2 Private PaaS Team
>
> --
>
> 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
>
>


-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC2

2015-12-18 Thread Nirmal Fernando

We have to cancel this vote due to an issue in the README.

On Fri, Dec 18, 2015 at 4:10 PM, Maheshakya Wijewardena  wrote:

> Hi Devs,
>
> This is the 2nd Release Candidate of WSO2 Machine Learner 1.1.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12594
>
> Please download, test and vote. Vote will be open for 72 hours or as
> longer as needed.
>
> *Binary distribution files:*
>
> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc2/wso2ml-1.1.0.zip
>
> *P2 repository*:
> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc2/p2-repo.zip
>
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2ml-208/
> 
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-ml/tree/v1.1.0-rc2
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you,
> Machine Learner Team
>
> --
> Pruthuvi Maheshakya Wijewardena
> mahesha...@wso2.com
> +94711228855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC3

2015-12-18 Thread Maheshakya Wijewardena

Hi Devs,

This is the 3rd Release Candidate of WSO2 Machine Learner 1.1.0.

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

Please download, test and vote. Vote will be open for 72 hours or as longer
as needed.

*Binary distribution files:*
https://github.com/wso2/product-ml/releases/download/v1.1.0-rc3/wso2ml-1.1.0.zip

*P2 repository*:
https://github.com/wso2/product-ml/releases/download/v1.1.0-rc3/p2-repo.zip


*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2ml-211/


*The tag to be voted upon:*
https://github.com/wso2/product-ml/tree/v1.1.0-rc3


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

Thank you,
Machine Learner Team

-- 
Pruthuvi Maheshakya Wijewardena
mahesha...@wso2.com
+94711228855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Blog post on WSO2 MSS - Pet Store Sample

2015-12-18 Thread Nanduni Nimalsiri

Hi,

Here[1] is the blog post that I wrote describing how WSO2 MSS - Pet Store
Sample works in Linux OS. Happy to hear your comments.

[1] http://nanduni.blogspot.com/2015/10/wso2-mss-pet-store-sample.html



Thank you,
Nanduni.


*Nanduni Nimalsiri*
Software Engineering Intern, WSO2 Inc. (http://wso2.com)
email : nand...@wso2.com
blog : http://nanduni.blogspot.com/
mobile : +94714114256
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [dev] DS test fixes after UI changes.

2015-12-18 Thread Nipuna Chandradasa

Thank you Ayesha,

Test fixes still going on. Delayed due to the conflicts with two PR. I'm
looking in to this.

On Fri, Dec 18, 2015 at 12:08 PM, Ayesha Dissanayaka 
wrote:

> Created ui-test-fixes branch in carbon-dashboards as well.
>
> [2] https://github.com/wso2/carbon-dashboards/tree/ui-test-fixes
>
> Thanks!
> -Ayesha
>
> On Fri, Dec 18, 2015 at 10:41 AM, Ayesha Dissanayaka 
> wrote:
>
>> Hi all,
>>
>> I have created new branch *ui-test-fixes* in product-ds repo in-order to
>> perform test fixes. All the PRs related to these test fixes, please send
>> them to this branch. As discussed once all the test related changes are
>> done, we'll merge this branch to the master.
>>
>> [1] https://github.com/wso2/product-ds/tree/ui-test-fixes
>>
>> Thanks!
>> -Ayesha
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>
>
>
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>



-- 
Nipuna Marcus
*Software Engineer*
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"
Mobile : +94 (0) 713 667906
nipu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] App Manager 1.1.0 latest build pack - 18-12-2015

Re: [Dev] UUF/Jaggery - unformatted error

[Dev] "No bam.xml" - Is this required to be present when embedding DAS?

Re: [Dev] UUF/Jaggery - unformatted error

Re: [Dev] [DS][DAS] Sample for DashboardServer - How to get back-end url, username, password for DAS to invoke DAS rest API from jaggery file

[Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC2

Re: [Dev] Can we suppress DAS message for schedule task execution?

[Dev] [Architecture] WSO2 Message Broker 3.1.0 Milestone 2 Released !

[Dev] [DEV][BRS][Release] WSO2 Business Rule Server (WSO2 BRS) 2.2.0 - Beta2 Released!

[Dev] Issue while using the special characters in url-template with legacy encoding.

[Dev] [VOTE] Release WSO2 Carbon Kernel 5.0.0 RC2

[Dev] Clarification on OUT_ONLY ESB proxy service scenario

[Dev] Transports can't be stopped and start in MSS

Re: [Dev] UUF/Jaggery - unformatted error

Re: [Dev] Transports can't be stopped and start in MSS

Re: [Dev] Issue while using the special characters in url-template with legacy encoding.

[Dev] WSO2 Private PaaS Cartridges v4.1.3 released

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

[Dev] APIM 1.10.0 latest pack - 18-12-2015

Re: [Dev] Clarification on OUT_ONLY ESB proxy service scenario

Re: [Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC2

[Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC3

[Dev] Blog post on WSO2 MSS - Pet Store Sample

Re: [Dev] [dev] DS test fixes after UI changes.

25 matches

Site Navigation

Mail list logo

Footer information