[jira] [Commented] (SLING-5718) Pipes size parameter is ignored

2016-05-10 Thread Jordan Shurmer (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278618#comment-15278618
 ] 

Jordan Shurmer commented on SLING-5718:
---

Hi [~npeltier]. Thanks for taking a look.

I was wanting to see all the results in the project I was working on, without 
knowing for sure how many would be affected ahead of time. That's why I added 
the <0 check. If you give size=-1 then all the results will be returned.


> Pipes size parameter is ignored
> ---
>
> Key: SLING-5718
> URL: https://issues.apache.org/jira/browse/SLING-5718
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jordan Shurmer
> Attachments: SLING-5718.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> The "size" parameter which can be passed in when executing a Pipe is ignored.
> line 92 of PlumbServlet.Java gets it
> {code}int size = request.getParameter(PARAM_SIZE) != null ? 
> Integer.parseInt(request.getParameter(PARAM_SIZE)) : NB_MAX;{code}
> but it is never used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5718) Pipes size parameter is ignored

2016-05-10 Thread Nicolas Peltier (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278525#comment-15278525
 ] 

Nicolas Peltier commented on SLING-5718:


Hi [~jshurmer] looks good to me, just maybe the <0 checks seems overkill to me.
(i don't have commit rights by the way, so you'll have to wait for a commiter 
to see this)

> Pipes size parameter is ignored
> ---
>
> Key: SLING-5718
> URL: https://issues.apache.org/jira/browse/SLING-5718
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jordan Shurmer
> Attachments: SLING-5718.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> The "size" parameter which can be passed in when executing a Pipe is ignored.
> line 92 of PlumbServlet.Java gets it
> {code}int size = request.getParameter(PARAM_SIZE) != null ? 
> Integer.parseInt(request.getParameter(PARAM_SIZE)) : NB_MAX;{code}
> but it is never used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: Pipes size parameter is ignored

2016-05-10 Thread Shurmer, Jordan 
Hey guys,

This is my first ticket/patch in the ASF!  Not 100% sure if I'm doing things 
the right way, but I've attached the patch to the ticket. 

Can someone take a look and see if I set up the ticket correct to get the patch 
patched in? 

Thanks!
Jordan Shurmer

-Original Message-
From: Jordan Shurmer (JIRA) [mailto:j...@apache.org] 
Sent: Tuesday, May 10, 2016 11:53 AM
To: dev@sling.apache.org
Subject: [jira] [Updated] (SLING-5718) Pipes size parameter is ignored


 [ 
https://issues.apache.org/jira/browse/SLING-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jordan Shurmer updated SLING-5718:
--
Attachment: SLING-5718.patch

Attached the Path to fix this. The documentation does not need updating as it 
already calls out this feature.

> Pipes size parameter is ignored
> ---
>
> Key: SLING-5718
> URL: https://issues.apache.org/jira/browse/SLING-5718
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jordan Shurmer
> Attachments: SLING-5718.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> The "size" parameter which can be passed in when executing a Pipe is ignored.
> line 92 of PlumbServlet.Java gets it
> {code}int size = request.getParameter(PARAM_SIZE) != null ? 
> Integer.parseInt(request.getParameter(PARAM_SIZE)) : NB_MAX;{code} but it is 
> never used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5718) Pipes size parameter is ignored

2016-05-10 Thread Jordan Shurmer (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jordan Shurmer updated SLING-5718:
--
Attachment: SLING-5718.patch

Attached the Path to fix this. The documentation does not need updating as it 
already calls out this feature.

> Pipes size parameter is ignored
> ---
>
> Key: SLING-5718
> URL: https://issues.apache.org/jira/browse/SLING-5718
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jordan Shurmer
> Attachments: SLING-5718.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> The "size" parameter which can be passed in when executing a Pipe is ignored.
> line 92 of PlumbServlet.Java gets it
> {code}int size = request.getParameter(PARAM_SIZE) != null ? 
> Integer.parseInt(request.getParameter(PARAM_SIZE)) : NB_MAX;{code}
> but it is never used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5718) Pipes size parameter is ignored

2016-05-10 Thread Jordan Shurmer (JIRA) 
Jordan Shurmer created SLING-5718:
-

 Summary: Pipes size parameter is ignored
 Key: SLING-5718
 URL: https://issues.apache.org/jira/browse/SLING-5718
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Reporter: Jordan Shurmer


The "size" parameter which can be passed in when executing a Pipe is ignored.

line 92 of PlumbServlet.Java gets it
{code}int size = request.getParameter(PARAM_SIZE) != null ? 
Integer.parseInt(request.getParameter(PARAM_SIZE)) : NB_MAX;{code}

but it is never used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5717) Add a unit test for PrivilegeDistributionRequestAuthorizationStrategy

2016-05-10 Thread Tommaso Teofili (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili resolved SLING-5717.

Resolution: Fixed
  Assignee: Tommaso Teofili

fixed in r1743213

> Add a unit test for PrivilegeDistributionRequestAuthorizationStrategy
> -
>
> Key: SLING-5717
> URL: https://issues.apache.org/jira/browse/SLING-5717
> Project: Sling
>  Issue Type: Test
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: Content Distribution 0.2.0
>
>
> {{PrivilegeDistributionRequestAuthorizationStrategy}} is missing a unit test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5717) Add a unit test for PrivilegeDistributionRequestAuthorizationStrategy

2016-05-10 Thread Tommaso Teofili (JIRA) 
Tommaso Teofili created SLING-5717:
--

 Summary: Add a unit test for 
PrivilegeDistributionRequestAuthorizationStrategy
 Key: SLING-5717
 URL: https://issues.apache.org/jira/browse/SLING-5717
 Project: Sling
  Issue Type: Test
  Components: Distribution
Reporter: Tommaso Teofili
 Fix For: Content Distribution 0.2.0


{{PrivilegeDistributionRequestAuthorizationStrategy}} is missing a unit test.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5716) Async building of packages

2016-05-10 Thread Tommaso Teofili (JIRA) 
Tommaso Teofili created SLING-5716:
--

 Summary: Async building of packages
 Key: SLING-5716
 URL: https://issues.apache.org/jira/browse/SLING-5716
 Project: Sling
  Issue Type: Improvement
  Components: Distribution
Reporter: Tommaso Teofili


Current SimpleAgent builds the DistributionPackage synchronously, in some cases 
it may be acceptable to do that asynchronously and improve the throughput of 
the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5695) Make it possible to build a reference package and send the actual package asynchronously

2016-05-10 Thread Tommaso Teofili (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili updated SLING-5695:
---
Description: 
It'd be good to see if it's possible to reach a higher throughput by 
parallelizing the process of transporting multiple packages with the process of 
installing them; so the idea is to build a package, but only put a reference to 
it in the ordered queue and send the actual package by putting it into a 
different queue that gets processed in parallel.
 

  was:Current SimpleAgent builds the DistributionPackage synchronously, in some 
cases it may be acceptable to do that asynchronously and improve the throughput 
of the agent.


> Make it possible to build a reference package and send the actual package 
> asynchronously
> 
>
> Key: SLING-5695
> URL: https://issues.apache.org/jira/browse/SLING-5695
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Attachments: SLING-5695.0.patch, SLING-5695.1.patch
>
>
> It'd be good to see if it's possible to reach a higher throughput by 
> parallelizing the process of transporting multiple packages with the process 
> of installing them; so the idea is to build a package, but only put a 
> reference to it in the ordered queue and send the actual package by putting 
> it into a different queue that gets processed in parallel.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5695) Make it possible to build a reference package and send the actual package asynchronously

2016-05-10 Thread Tommaso Teofili (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili updated SLING-5695:
---
Summary: Make it possible to build a reference package and send the actual 
package asynchronously  (was: Make it possible to build a package 
asynchronously)

> Make it possible to build a reference package and send the actual package 
> asynchronously
> 
>
> Key: SLING-5695
> URL: https://issues.apache.org/jira/browse/SLING-5695
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Attachments: SLING-5695.0.patch, SLING-5695.1.patch
>
>
> Current SimpleAgent builds the DistributionPackage synchronously, in some 
> cases it may be acceptable to do that asynchronously and improve the 
> throughput of the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5695) Make it possible to build a package asynchronously

2016-05-10 Thread Tommaso Teofili (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili updated SLING-5695:
---
Attachment: SLING-5695.1.patch

second iteration of the former patch, now async delivery works, but there're 
several points to optimize.

> Make it possible to build a package asynchronously
> --
>
> Key: SLING-5695
> URL: https://issues.apache.org/jira/browse/SLING-5695
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Attachments: SLING-5695.0.patch, SLING-5695.1.patch
>
>
> Current SimpleAgent builds the DistributionPackage synchronously, in some 
> cases it may be acceptable to do that asynchronously and improve the 
> throughput of the agent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: WebDav Polling Not Working

2016-05-10 Thread Bertrand Delacretaz 
Hi,

On Fri, May 6, 2016 at 5:49 PM, Andreas Schaefer Sr.  wrote:
> ...Did you ever use something like RMI, JCA to connect to a remote JCR 
> repository...

I've never used those mechanisms myself and my understanding is that
JCR over RMI is quite slow due to the fine granularity of JCR methods.

I think PHPCR is or at least was using remote Jackrabbit/Oak
repositories via DavEx [1] but activity about that has slowed down on
the jackrabbit list [2].

-Bertrand

[1] https://wiki.apache.org/jackrabbit/RemoteAccess
[2] 
http://jackrabbit.markmail.org/search/?q=phpcr#query:phpcr%20order%3Adate-backward+page:1+state:facets

[jira] [Commented] (SLING-5715) Random NoRouteToHostException in Teleporter Client MultipartAdapter method

2016-05-10 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277768#comment-15277768
 ] 

Konrad Windszus commented on SLING-5715:


To me it seems that 
https://github.com/apache/sling/blob/c9e59667d8f9cd698bc33a51f3e6a22e85d4a952/testing/junit/teleporter/src/main/java/org/apache/sling/testing/teleporter/client/TeleporterHttpClient.java#L142
 is not consuming the input stream and therefore might lead to the socket not 
being reused 
(http://docs.oracle.com/javase/6/docs/technotes/guides/net/http-keepalive.html).
 The response stream should always be consumed and then closed (then 
{{disconnect}} does not need to be called at all, 
http://stackoverflow.com/questions/4767553/safe-use-of-httpurlconnection).

> Random NoRouteToHostException in Teleporter Client MultipartAdapter method
> --
>
> Key: SLING-5715
> URL: https://issues.apache.org/jira/browse/SLING-5715
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: JUnit Tests Teleporter 1.0.4
>Reporter: Thierry Ygé
>Assignee: Bertrand Delacretaz
>
> We observe on jenkins jobs that randomly serverside tests are failing due to 
> "java.net.NoRouteToHostException: Cannot assign requested address"
> This is apparently always coming from 
> "org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)"
> It would be good to check if the implementation is not using "old" or 
> unstable API. maybe replacing it using http component API would help to make 
> it more stable.
> {noformat}
> 06:48:39 [INFO] java.net.NoRouteToHostException: Cannot assign requested 
> address
> 06:48:39 [INFO]   at java.net.PlainSocketImpl.socketConnect(Native Method)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> 06:48:39 [INFO]   at 
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:589)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:538)
> 06:48:39 [INFO]   at 
> sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.(HttpClient.java:211)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.TeleporterHttpClient.uninstallBundle(TeleporterHttpClient.java:92)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.ClientSideTeleporter$2.evaluate(ClientSideTeleporter.java:174)
> ...
> {noformat}
> It is same for uninstall and install bundle operation of Teleporter. Maybe it 
> could be related to SLING-5352, as the test class contains ~115 tests, and 
> maybe that produce issues when Teleporter install/uninstall quickly so many 
> test / bundle.
> cc [~bdelacretaz]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5715) Random NoRouteToHostException in Teleporter Client MultipartAdapter method

2016-05-10 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277757#comment-15277757
 ] 

Konrad Windszus commented on SLING-5715:


It would be good to check the TCP connections and their state once that 
happens. It may be related to http://stackoverflow.com/a/31877033.

> Random NoRouteToHostException in Teleporter Client MultipartAdapter method
> --
>
> Key: SLING-5715
> URL: https://issues.apache.org/jira/browse/SLING-5715
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: JUnit Tests Teleporter 1.0.4
>Reporter: Thierry Ygé
>Assignee: Bertrand Delacretaz
>
> We observe on jenkins jobs that randomly serverside tests are failing due to 
> "java.net.NoRouteToHostException: Cannot assign requested address"
> This is apparently always coming from 
> "org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)"
> It would be good to check if the implementation is not using "old" or 
> unstable API. maybe replacing it using http component API would help to make 
> it more stable.
> {noformat}
> 06:48:39 [INFO] java.net.NoRouteToHostException: Cannot assign requested 
> address
> 06:48:39 [INFO]   at java.net.PlainSocketImpl.socketConnect(Native Method)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> 06:48:39 [INFO]   at 
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:589)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:538)
> 06:48:39 [INFO]   at 
> sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.(HttpClient.java:211)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.TeleporterHttpClient.uninstallBundle(TeleporterHttpClient.java:92)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.ClientSideTeleporter$2.evaluate(ClientSideTeleporter.java:174)
> ...
> {noformat}
> It is same for uninstall and install bundle operation of Teleporter. Maybe it 
> could be related to SLING-5352, as the test class contains ~115 tests, and 
> maybe that produce issues when Teleporter install/uninstall quickly so many 
> test / bundle.
> cc [~bdelacretaz]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (SLING-5452) ClientSideTeleporter should check for web console readiness

2016-05-10 Thread Bertrand Delacretaz (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz reopened SLING-5452:


Good point, I'm reopening this issue to implement this. I'm not sure if it's 
related to SLING-5715 but makes sense anyway.

> ClientSideTeleporter should check for web console readiness
> ---
>
> Key: SLING-5452
> URL: https://issues.apache.org/jira/browse/SLING-5452
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: JUnit Tests Teleporter 1.0.6
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: JUnit Tests Teleporter 1.0.8
>
>
> Before installing its test bundle, the {{ClientSideTeleporter}} should 
> (optionally?) check, via HTTP, that the OSGi console is ready to accept it. 
> The customizer could optionally set a longer retry timeout for installing the 
> bundle.
> This is not a problem in our launchpad test suite as the Sling readiness is 
> checked extensively before starting tests, but in smaller test suites it's 
> useful for the teleporter to be self-contained in this respect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5715) Random NoRouteToHostException in Teleporter Client MultipartAdapter method

2016-05-10 Thread Bertrand Delacretaz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277747#comment-15277747
 ] 

Bertrand Delacretaz commented on SLING-5715:


I suspect it might be a connection or other network related resource that's not 
released properly, in which case running lots of tests quickly should make this 
more likely. Does that match your observations? Or do you have other hints on 
how to reproduce this issue?

> Random NoRouteToHostException in Teleporter Client MultipartAdapter method
> --
>
> Key: SLING-5715
> URL: https://issues.apache.org/jira/browse/SLING-5715
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: JUnit Tests Teleporter 1.0.4
>Reporter: Thierry Ygé
>
> We observe on jenkins jobs that randomly serverside tests are failing due to 
> "java.net.NoRouteToHostException: Cannot assign requested address"
> This is apparently always coming from 
> "org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)"
> It would be good to check if the implementation is not using "old" or 
> unstable API. maybe replacing it using http component API would help to make 
> it more stable.
> {noformat}
> 06:48:39 [INFO] java.net.NoRouteToHostException: Cannot assign requested 
> address
> 06:48:39 [INFO]   at java.net.PlainSocketImpl.socketConnect(Native Method)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> 06:48:39 [INFO]   at 
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:589)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:538)
> 06:48:39 [INFO]   at 
> sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.(HttpClient.java:211)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.TeleporterHttpClient.uninstallBundle(TeleporterHttpClient.java:92)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.ClientSideTeleporter$2.evaluate(ClientSideTeleporter.java:174)
> ...
> {noformat}
> It is same for uninstall and install bundle operation of Teleporter. Maybe it 
> could be related to SLING-5352, as the test class contains ~115 tests, and 
> maybe that produce issues when Teleporter install/uninstall quickly so many 
> test / bundle.
> cc [~bdelacretaz]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-5715) Random NoRouteToHostException in Teleporter Client MultipartAdapter method

2016-05-10 Thread Bertrand Delacretaz (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz reassigned SLING-5715:
--

Assignee: Bertrand Delacretaz

> Random NoRouteToHostException in Teleporter Client MultipartAdapter method
> --
>
> Key: SLING-5715
> URL: https://issues.apache.org/jira/browse/SLING-5715
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: JUnit Tests Teleporter 1.0.4
>Reporter: Thierry Ygé
>Assignee: Bertrand Delacretaz
>
> We observe on jenkins jobs that randomly serverside tests are failing due to 
> "java.net.NoRouteToHostException: Cannot assign requested address"
> This is apparently always coming from 
> "org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)"
> It would be good to check if the implementation is not using "old" or 
> unstable API. maybe replacing it using http component API would help to make 
> it more stable.
> {noformat}
> 06:48:39 [INFO] java.net.NoRouteToHostException: Cannot assign requested 
> address
> 06:48:39 [INFO]   at java.net.PlainSocketImpl.socketConnect(Native Method)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> 06:48:39 [INFO]   at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> 06:48:39 [INFO]   at 
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:589)
> 06:48:39 [INFO]   at java.net.Socket.connect(Socket.java:538)
> 06:48:39 [INFO]   at 
> sun.net.NetworkClient.doConnect(NetworkClient.java:180)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> 06:48:39 [INFO]   at 
> sun.net.www.http.HttpClient.(HttpClient.java:211)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> 06:48:39 [INFO]   at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)
> 06:48:39 [INFO]   at 
> sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.MultipartAdapter.(MultipartAdapter.java:42)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.TeleporterHttpClient.uninstallBundle(TeleporterHttpClient.java:92)
> 06:48:39 [INFO]   at 
> org.apache.sling.testing.teleporter.client.ClientSideTeleporter$2.evaluate(ClientSideTeleporter.java:174)
> ...
> {noformat}
> It is same for uninstall and install bundle operation of Teleporter. Maybe it 
> could be related to SLING-5352, as the test class contains ~115 tests, and 
> maybe that produce issues when Teleporter install/uninstall quickly so many 
> test / bundle.
> cc [~bdelacretaz]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)