Re: [Dev] Socket connection closed while trying ESB connector operation.

[Shakila Sivagnanarajah]

Thanks Kathees,

It is fixed by adding the following properties.





Thanks

On Thu, Jun 16, 2016 at 4:46 PM, Kathees Rajendram  wrote:

> Hi Shakila,
>
> Since you are using PUT operation without body, Can you try the following
> property to remove the entry body from HTTP request.
>
> 
>
>
> Thanks,
> Kathees
>
> On Thu, Jun 16, 2016 at 4:41 PM, Shakila Sivagnanarajah 
> wrote:
>
>> Hi,
>>
>> I sent the request without setting the payload entity using a proxy
>> service [1], It works fine. But in my template, I remove the previous
>> payload using 'FORCE_POST_PUT_NOBODY'. It seems the problem is the payload.
>>
>> [1]
>> 
>> 
>> 
>> 
>> > value="256"/>
>> > value="xx"/>
>> > scope="transport" value="bytes=0-9"/>
>> > value="application/xml; charset=UTF-8"/>
>> 
>> > value="/bucketName/testFile.jpg"/>
>> > value="256"/>
>> 
>> 
>> http://1466064852454testconbkt2.s3-us-west-2.amazonaws.com/testFile1.txt?partNumber=2uploadId=wdU0iM8SaNaGzHyFiUEHEk4WTqkL2jC_LHTeLZ3EjTLjsB8WVELvbH.XHcCrToRQQRtDAjr_kWv0JPk_7vacLVevdCjje11_pYuEjes2Ev1erXifpt.gdKmgtXU0VLP1
>> "/>
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> Thanks
>>
>> On Thu, Jun 16, 2016 at 9:46 AM, Senduran Balasubramaniyam <
>> sendu...@wso2.com> wrote:
>>
>>> Hi Shakila,
>>>
>>> Can you compare the request sending from ESB(using wirelog) and sending
>>> directly.
>>>
>>> Regards
>>> Senduran
>>>
>>> On Wed, Jun 15, 2016 at 6:56 PM, Shakila Sivagnanarajah <
>>> shak...@wso2.com> wrote:
>>>
 Hi all,

 I am experiencing socket connection closed exception while trying
 'upload part operation' [1] of Amazon s3 connector. In direct call, the
 response comes within 5 seconds. I increased the the timeout values as
 below.

 synapse.global_timeout_interval - 180 seconds in synapse.properties
 http.socket.timeout - 180 seconds in passthru-http.properties
 http.socket.timeout.receiver - 180 seconds in nhttp.properties

 After this tuning also, no improvement. It waits for nearly 21 seconds.
 But not receiving the response from API. [2] is the message I get.

 Finally I set the endpoint timeout [3] also. But the result is same.

 [1]
 http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html


 
 [2]
 
 RequestTimeout
 Your socket connection to the server was not read from or
 written to within the timeout period. Idle connections will be
 closed.
 7223E45B22E88E80

 cH2RE4IG7QhmiN1Bpqw6/bweEKowmtXS+jFwJkzay/3u3MovuutgtzAXM37tpXuzCl23HxAYuZIF1rLGLuJxvh4GRAu6891c
 

 [3]
 
 
 >>> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}">
 
 18
 fault
 
 
 
 

 [4] Template:

 http://ws.apache.org/ns/synapse;>
 
 
 
 
 
 >>> expression="$func:bucketUrl"/>
 >>> expression="$func:objectName"/>
 
 >>> expression="$func:partNumber"/>
 
 >>> scope="axis2"/>
 >>> scope="axis2"/>
 
 
 >>>
 uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}"/>
 
 
 
 
 >>> action="remove"/>
 
 >>> action="remove"/>
 
 


 Thank you
 --
 Shakila Sivagnanarajah
 Software Engineer
 Mobile :+94 (0) 768 856837
 shak...@wso2.com
 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/

>>>
>>>
>>>
>>> --
>>> *Senduran *
>>> Software Engineer,
>>> WSO2, Inc.;  http://wso2.com/ 
>>> Mobile: +94 77 952 6548
>>>
>>
>>
>>
>> --
>> Shakila Sivagnanarajah
>> Software Engineer
>> Mobile :+94 (0) 768 856837
>> shak...@wso2.com
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>



-- 
Shakila Sivagnanarajah
Software Engineer
Mobile :+94 (0) 768 856837
shak...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
___
Dev mailing list

Re: [Dev] Socket connection closed while trying ESB connector operation.

[Kathees Rajendram]

Hi Shakila,

Since you are using PUT operation without body, Can you try the following
property to remove the entry body from HTTP request.




Thanks,
Kathees

On Thu, Jun 16, 2016 at 4:41 PM, Shakila Sivagnanarajah 
wrote:

> Hi,
>
> I sent the request without setting the payload entity using a proxy
> service [1], It works fine. But in my template, I remove the previous
> payload using 'FORCE_POST_PUT_NOBODY'. It seems the problem is the payload.
>
> [1]
> 
> 
> 
> 
>  value="256"/>
>  value="xx"/>
>  scope="transport" value="bytes=0-9"/>
>  value="application/xml; charset=UTF-8"/>
> 
>  value="/bucketName/testFile.jpg"/>
>  value="256"/>
> 
> 
> http://1466064852454testconbkt2.s3-us-west-2.amazonaws.com/testFile1.txt?partNumber=2uploadId=wdU0iM8SaNaGzHyFiUEHEk4WTqkL2jC_LHTeLZ3EjTLjsB8WVELvbH.XHcCrToRQQRtDAjr_kWv0JPk_7vacLVevdCjje11_pYuEjes2Ev1erXifpt.gdKmgtXU0VLP1
> "/>
> 
> 
> 
> 
> 
> 
>
> Thanks
>
> On Thu, Jun 16, 2016 at 9:46 AM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Hi Shakila,
>>
>> Can you compare the request sending from ESB(using wirelog) and sending
>> directly.
>>
>> Regards
>> Senduran
>>
>> On Wed, Jun 15, 2016 at 6:56 PM, Shakila Sivagnanarajah > > wrote:
>>
>>> Hi all,
>>>
>>> I am experiencing socket connection closed exception while trying
>>> 'upload part operation' [1] of Amazon s3 connector. In direct call, the
>>> response comes within 5 seconds. I increased the the timeout values as
>>> below.
>>>
>>> synapse.global_timeout_interval - 180 seconds in synapse.properties
>>> http.socket.timeout - 180 seconds in passthru-http.properties
>>> http.socket.timeout.receiver - 180 seconds in nhttp.properties
>>>
>>> After this tuning also, no improvement. It waits for nearly 21 seconds.
>>> But not receiving the response from API. [2] is the message I get.
>>>
>>> Finally I set the endpoint timeout [3] also. But the result is same.
>>>
>>> [1]
>>> http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html
>>>
>>>
>>> 
>>> [2]
>>> 
>>> RequestTimeout
>>> Your socket connection to the server was not read from or
>>> written to within the timeout period. Idle connections will be
>>> closed.
>>> 7223E45B22E88E80
>>>
>>> cH2RE4IG7QhmiN1Bpqw6/bweEKowmtXS+jFwJkzay/3u3MovuutgtzAXM37tpXuzCl23HxAYuZIF1rLGLuJxvh4GRAu6891c
>>> 
>>>
>>> [3]
>>> 
>>> 
>>> >> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}">
>>> 
>>> 18
>>> fault
>>> 
>>> 
>>> 
>>> 
>>>
>>> [4] Template:
>>>
>>> http://ws.apache.org/ns/synapse;>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> expression="$func:objectName"/>
>>> 
>>> >> expression="$func:partNumber"/>
>>> 
>>> >> scope="axis2"/>
>>> >> scope="axis2"/>
>>> 
>>> 
>>> >>
>>> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}"/>
>>> 
>>> 
>>> 
>>> 
>>> >> action="remove"/>
>>> 
>>> >> action="remove"/>
>>> 
>>> 
>>>
>>>
>>> Thank you
>>> --
>>> Shakila Sivagnanarajah
>>> Software Engineer
>>> Mobile :+94 (0) 768 856837
>>> shak...@wso2.com
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>>
>>
>>
>>
>> --
>> *Senduran *
>> Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ 
>> Mobile: +94 77 952 6548
>>
>
>
>
> --
> Shakila Sivagnanarajah
> Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Socket connection closed while trying ESB connector operation.

[Shakila Sivagnanarajah]

Hi,

I sent the request without setting the payload entity using a proxy service
[1], It works fine. But in my template, I remove the previous payload using
'FORCE_POST_PUT_NOBODY'. It seems the problem is the payload.

[1]













http://1466064852454testconbkt2.s3-us-west-2.amazonaws.com/testFile1.txt?partNumber=2uploadId=wdU0iM8SaNaGzHyFiUEHEk4WTqkL2jC_LHTeLZ3EjTLjsB8WVELvbH.XHcCrToRQQRtDAjr_kWv0JPk_7vacLVevdCjje11_pYuEjes2Ev1erXifpt.gdKmgtXU0VLP1
"/>







Thanks

On Thu, Jun 16, 2016 at 9:46 AM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:

> Hi Shakila,
>
> Can you compare the request sending from ESB(using wirelog) and sending
> directly.
>
> Regards
> Senduran
>
> On Wed, Jun 15, 2016 at 6:56 PM, Shakila Sivagnanarajah 
> wrote:
>
>> Hi all,
>>
>> I am experiencing socket connection closed exception while trying 'upload
>> part operation' [1] of Amazon s3 connector. In direct call, the response
>> comes within 5 seconds. I increased the the timeout values as below.
>>
>> synapse.global_timeout_interval - 180 seconds in synapse.properties
>> http.socket.timeout - 180 seconds in passthru-http.properties
>> http.socket.timeout.receiver - 180 seconds in nhttp.properties
>>
>> After this tuning also, no improvement. It waits for nearly 21 seconds.
>> But not receiving the response from API. [2] is the message I get.
>>
>> Finally I set the endpoint timeout [3] also. But the result is same.
>>
>> [1]
>> http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html
>>
>>
>> 
>> [2]
>> 
>> RequestTimeout
>> Your socket connection to the server was not read from or
>> written to within the timeout period. Idle connections will be
>> closed.
>> 7223E45B22E88E80
>>
>> cH2RE4IG7QhmiN1Bpqw6/bweEKowmtXS+jFwJkzay/3u3MovuutgtzAXM37tpXuzCl23HxAYuZIF1rLGLuJxvh4GRAu6891c
>> 
>>
>> [3]
>> 
>> 
>> > uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}">
>> 
>> 18
>> fault
>> 
>> 
>> 
>> 
>>
>> [4] Template:
>>
>> http://ws.apache.org/ns/synapse;>
>> 
>> 
>> 
>> 
>> 
>> 
>> > expression="$func:objectName"/>
>> 
>> > expression="$func:partNumber"/>
>> 
>> > scope="axis2"/>
>> > scope="axis2"/>
>> 
>> 
>> >
>> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}"/>
>> 
>> 
>> 
>> 
>> > action="remove"/>
>> 
>> > action="remove"/>
>> 
>> 
>>
>>
>> Thank you
>> --
>> Shakila Sivagnanarajah
>> Software Engineer
>> Mobile :+94 (0) 768 856837
>> shak...@wso2.com
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>>
>
>
>
> --
> *Senduran *
> Software Engineer,
> WSO2, Inc.;  http://wso2.com/ 
> Mobile: +94 77 952 6548
>



-- 
Shakila Sivagnanarajah
Software Engineer
Mobile :+94 (0) 768 856837
shak...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Socket connection closed while trying ESB connector operation.

[Senduran Balasubramaniyam]

Hi Shakila,

Can you compare the request sending from ESB(using wirelog) and sending
directly.

Regards
Senduran

On Wed, Jun 15, 2016 at 6:56 PM, Shakila Sivagnanarajah 
wrote:

> Hi all,
>
> I am experiencing socket connection closed exception while trying 'upload
> part operation' [1] of Amazon s3 connector. In direct call, the response
> comes within 5 seconds. I increased the the timeout values as below.
>
> synapse.global_timeout_interval - 180 seconds in synapse.properties
> http.socket.timeout - 180 seconds in passthru-http.properties
> http.socket.timeout.receiver - 180 seconds in nhttp.properties
>
> After this tuning also, no improvement. It waits for nearly 21 seconds.
> But not receiving the response from API. [2] is the message I get.
>
> Finally I set the endpoint timeout [3] also. But the result is same.
>
> [1]
> http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html
>
>
> 
> [2]
> 
> RequestTimeout
> Your socket connection to the server was not read from or
> written to within the timeout period. Idle connections will be
> closed.
> 7223E45B22E88E80
>
> cH2RE4IG7QhmiN1Bpqw6/bweEKowmtXS+jFwJkzay/3u3MovuutgtzAXM37tpXuzCl23HxAYuZIF1rLGLuJxvh4GRAu6891c
> 
>
> [3]
> 
> 
>  uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}">
> 
> 18
> fault
> 
> 
> 
> 
>
> [4] Template:
>
> http://ws.apache.org/ns/synapse;>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  scope="axis2"/>
>  scope="axis2"/>
> 
> 
> 
> uri-template="{uri.var.bucketUrl}/{+uri.var.objectName}?partNumber={+uri.var.partNumber}uploadId={+uri.var.uploadId}"/>
> 
> 
> 
> 
> 
> 
>  action="remove"/>
> 
> 
>
>
> Thank you
> --
> Shakila Sivagnanarajah
> Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
>



-- 
*Senduran *
Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Socket connection closed while trying ESB connector operation.

[Shakila Sivagnanarajah]

Hi all,

I am experiencing socket connection closed exception while trying 'upload
part operation' [1] of Amazon s3 connector. In direct call, the response
comes within 5 seconds. I increased the the timeout values as below.

synapse.global_timeout_interval - 180 seconds in synapse.properties
http.socket.timeout - 180 seconds in passthru-http.properties
http.socket.timeout.receiver - 180 seconds in nhttp.properties

After this tuning also, no improvement. It waits for nearly 21 seconds. But
not receiving the response from API. [2] is the message I get.

Finally I set the endpoint timeout [3] also. But the result is same.

[1]
http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadUploadPartCopy.html


[2]

RequestTimeout
Your socket connection to the server was not read from or
written to within the timeout period. Idle connections will be
closed.
7223E45B22E88E80

cH2RE4IG7QhmiN1Bpqw6/bweEKowmtXS+jFwJkzay/3u3MovuutgtzAXM37tpXuzCl23HxAYuZIF1rLGLuJxvh4GRAu6891c


[3]




18
fault





[4] Template:

http://ws.apache.org/ns/synapse;>


























Thank you
-- 
Shakila Sivagnanarajah
Software Engineer
Mobile :+94 (0) 768 856837
shak...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev