Re: [Dev] Getting Error "ServerWorker Error while building message for REST_URL request" for all API requests

[Chamila Adhikarinayake]

Hi Vijitha/Chanika,
Adding that formatter and builders resolved the issue. Would this be the
correct fix or is this a workaround?
Chamila.

On Sun, Mar 4, 2018 at 11:35 AM, Vijitha Ekanayake 
wrote:

> Hi Chamila,
>
> The reason that error doesn't print prior to the fix seems to be that the
> default content-type set as the application/x-www-form-urlencoded and
> product distribution ships with the axis2.xml enabling the
> relevant builder/formatter for that content-type. Could you try adding
> following builder/formatter to axis2.xml and check whether it resolves the
> issue?
>
>  class="org.wso2.carbon.relay.BinaryRelayBuilder"/>
>  class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>
>
> Thanks.
>
>
> On Sun, Mar 4, 2018 at 11:13 AM, Chamila Adhikarinayake  > wrote:
>
>> Hi Vijitha,
>>
>> Seems like the PR[1] is causing the issue. It sets content-type to
>> application/octet-stream for requests without a content-type header.
>> Seems like the logic is ok for POST request but not sure why that
>> validation related method is called for all other HTTP methods in [2].
>>
>> [1] https://github.com/wso2/wso2-synapse/pull/1015/files
>> [2] https://github.com/wso2/wso2-synapse/blob/master/modules
>> /transports/core/nhttp/src/main/java/org/apache/synapse/
>> transport/passthru/ServerWorker.java#L155
>>
>> On Fri, Mar 2, 2018 at 9:14 PM, Vijitha Ekanayake 
>> wrote:
>>
>>> ++Chanika
>>>
>>> On Fri, Mar 2, 2018 at 6:30 PM, Nuwan Dias  wrote:
>>>
 Is there a release of EI happening in Q1? Don't you notice this error
 on latest versions of EI?

 On Fri, Feb 23, 2018 at 3:46 PM, Vijitha Ekanayake 
 wrote:

> This error is generated within the handleRESTUrlPost(...) method in
> ServerWorker class. So I think we need to investigate the reason why these
> GET requests are landed in that method and fix if there is an issue in the
> logic.
>
> Thanks.
>
> On Fri, Feb 23, 2018 at 3:20 PM, Chaminda Jayawardena <
> chami...@wso2.com> wrote:
>
>> True, But I am trying with Jmeter and just tried since suggested
>> above and error is not appeared when it sends with Content-Type :)
>> Yes, have to fix it.
>>
>> Thanks,
>> Chaminda
>>
>> On Fri, Feb 23, 2018 at 3:12 PM, Nuwan Dias  wrote:
>>
>>> Well, for GET requests you aren't supposed to have a Content-Type
>>> header.
>>>
>>> On Fri, Feb 23, 2018 at 3:11 PM, Chaminda Jayawardena <
>>> chami...@wso2.com> wrote:
>>>
 Getting this continuously even for the GET requests in
 wso2apim-2.1.0-update12. Disappeared once put Content-Type(value as any
 format) on the header.

 Thanks,
 Chaminda

 On Fri, Feb 23, 2018 at 1:38 PM, Nuwan Dias 
 wrote:

> I'm just doing a GET. I also checked with a POST with the correct
> Content-Type header as well.
>
> On Fri, Feb 23, 2018 at 1:17 PM, Vijitha Ekanayake <
> vijit...@wso2.com> wrote:
>
>> Hi Nuwan,
>>
>> According to below code segment, it seems like this happens when
>> request Content-Type doesn't match with the payload.
>>
>> try {
>>
>>   soapEnvelope = TransportUtils.createSOAPMessage(msgContext, null, 
>> contentType);
>>} catch (Exception e) {
>>   log.error("Error while building message for REST_URL request");
>> }
>>
>> Also It might be a case that POST requests received without a 
>> Content-Type header. Is there any possibility to isolate one such 
>> request causes this error. So that we could identify extract root 
>> cause for this.
>>
>> Thanks.
>>
>>
>> On Thu, Feb 22, 2018 at 2:38 PM, Nuwan Dias 
>> wrote:
>>
>>> Hi,
>>>
>>> I'm seeing the error "*ServerWorker Error while building
>>> message for REST_URL request*" on the logs for all API requests
>>> on Synapse version 2.1.7.wso2v40. Any idea what could be causing 
>>> this?
>>> AFAIR this wasn't there on earlier versions.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Architect - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>>
>>
>>
>>
>> --
>> Vijitha Ekanayake
>> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
>> Mobile : +94 777 24 73 39 | +94 718 74 44 08
>> lean.enterprise.middleware
>>
>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <+94%2077%20777%205729>

[Dev] Reason for not supporting JMS Proprerties in AMQP STRICT mode

[Asanka Abeyweera]

Hi all,

Why have we restricted using JMS porperties in AMQP_STRICT mode? Please
refer [1] for implementation.

[1]
https://github.com/wso2/andes/blob/master/modules/andes-core/client/src/main/java/org/wso2/andes/client/message/AMQMessageDelegate_0_8.java#L59

-- 
Asanka Abeyweera
Associate Technical Lead
WSO2 Inc.

Phone: +94 712228648
Blog: a5anka.github.io


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

Re: [Dev] [Architecture] [VOTE] Release WSO2 IoT Server 3.2.0 RC4

[Rasika Perera]

Hi All,

Thanks for testing and voting. Since no blocking issues have been reported,
we’re hereby closing this vote with 8 +1s and no -1s and proceeding with
the IoT Server 3.2.0 release.

Best Regards,
~Rasika

On Sun, Mar 4, 2018 at 11:40 AM, Charitha Goonetilleke 
wrote:

> Hi All,
>
> I have tested following.
>
>- Device operation response publishing to Analytics.
>- Create API based device type and enroll device.
>- Publish operations and events via MQTT.
>- Update device properties dynamically for API based device types.
>- Configure FCM and Local Notification on top of Multi tenancy
>environment.
>
> [+] Stable - Go ahead and release
>
> Thanks & Regards,
> /charithag
>
> On Sat, Mar 3, 2018 at 10:34 PM, Lasantha Dharmakeerthi <
> lasant...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested following functionalities:
>>
>>1. Configured the server with the IP using the IP changing script
>>2. Installed the iOS feature on the server
>>3. Tenant Creation
>>4. Tested iOS and Android functionalities for the super tenant and
>>the tenant domain.
>>
>> *iOS *
>>
>>- Enrolled a device
>>- Unregister a device
>>- Tested operations (Device Lock, Ring, Notification, Location,
>>Applications)
>>- Enforced restriction policies and revoked
>>
>>  *Android*
>>
>>- Enrolled a device (BYOD)
>>- Unregister a device
>>- Tested operations (Device Lock, Ring, Notification, Location,
>>Applications)
>>- Enforced restriction policies and revoked
>>- Remote Control Feature
>>
>>  5. Device Locations mapping feature
>>
>>  6. App Manager
>>
>>- iOS and Android App publishing
>>- iOS and Android App Deletion
>>
>>
>> *[+] Stable - Go ahead and release*
>>
>> Thank You  and Best Regards,
>> Lasantha
>>
>> On Sat, Mar 3, 2018 at 9:55 PM, Madawa Soysa  wrote:
>>
>>> Hi All,
>>>
>>> I have tested the following,
>>>
>>>- Configure a distributed setup with Manager, Worker and Key Manager
>>>nodes in EC2 Instances.
>>>- Setup the servers against MySQL 5.6 with a shared registry.
>>>- API Publishing from worker nodes
>>>- Android Enrollment in BYOD mode.
>>>- Android Operations (RING, LOCATION, NOTIFICATION, CLEAR PASSCODE)
>>>- Unregister through the android agent.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> Best Regards,
>>> Madawa
>>>
>>> On Sat, Mar 3, 2018 at 9:25 PM, Madhawa Perera 
>>> wrote:
>>>
 Hi,

 I have tested following functionalities:

- Configured the server with the IP using change-ip.sh script
- Installed ios feature on the server
- Enrolled an iOS device using the admin user
- Tested operations, DEVICE_LOCK, RING, CLEAR_PASSCODE,
NOTIFICATION and WIPE_DATA
- Enforced restriction policies and revoked

 [+] Stable - Go ahead and release

 Thank you
 Best Regards,
 Madhawa






 On Sat, Mar 3, 2018 at 7:46 PM, Milan Perera  wrote:

> Hi all,
>
> I have tested the data archival feature in MySQL 5.5, 5.6, and 5.7.
>
> [+] Stable - Go ahead and release
>
> Regards,
>
>
> On Fri, Mar 2, 2018 at 7:22 PM, Shavindri Dissanayake <
> shavin...@wso2.com> wrote:
>
>> Hi,
>>
>> - Enrolled the virtual fire-alarm and sent a ring operation.
>> - Enrolled the AVD and sent a ring operation.
>> - Applied policies on a device and revoked a policy successfully.
>> - Tested the remote control screen view
>> - Grouped devices.
>>
>> [+] Stable - Go ahead and release
>>
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Senior Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>> On Fri, Mar 2, 2018 at 5:39 PM, Sumedha Rubasinghe 
>> wrote:
>>
>>> Installed on a remote machine against MySQL 5.5.
>>> Tested
>>> -Device type API
>>> -Message broker functionality
>>> -stream processing
>>>
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> On Mar 2, 2018 3:02 AM, "Rasika Perera"  wrote:
>>>
>>> Hi Devs,
>>>
>>> We are pleased to announce the release candidate of WSO2 IoT Server
>>>  3.2.0.
>>>
>>> This is the fourth release candidate (RC) of the WSO2 IoT Server 3.2.0
>>> release.
>>>
>>> This release carries 275+ issue fixes [1-12] over the last GA (3.1.0)
>>> release.
>>>
>>> Reported Issues:
>>>
>>>- https://github.com/wso2/product-iots/issues
>>>
>>> Source and distribution packages:
>>>
>>>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC4
>>>
>>> Tag to be voted upon:
>>>
>>>- https://github.com/wso2/product-iots/releases/tag/v3.2.0-RC4
>>>
>>> Please download, test, and vote. The README file under the
>>> distribution contains guide and instructions on how to try it 

Re: [Dev] [dev] please review and merge PR

[Hasunie Adikari]

I added some comments to elaborate how to fix the particular issue by
improving better performance as an additional outcome.

Regards
Hasunie

On Thu, Mar 1, 2018 at 10:54 AM, 김대경  wrote:

> Can you please review and merge PR.
>
> [1] https://github.com/wso2/wso2-synapse/pull/1054
>
> Best Regards.
> Daekyung Kim.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Hasunie Adikari*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
blog http://hasuniea.blogspot.com | https://medium.com/@Hasunie/
Mobile:+94713095876
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev