[ 
https://issues.apache.org/jira/browse/KARAF-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232603#comment-14232603
 ] 

Jean-Baptiste Onofré commented on KARAF-3339:
---------------------------------------------

After turning the log level to debug, it seems that we spend lot of time on 
things like:

{code}
2014-12-03 06:09:25,482 | INFO  | ion(3)-127.0.0.1 | ContainerTestRunner        
      | 69 - org.ops4j.pax.exam.invoker.junit - 4.3.0 | running headersCommand 
in reactor
2014-12-03 06:09:39,795 | DEBUG | RMI Scheduler(0) | tcp                        
      |  -  -  | RMI Scheduler(0): close connection
2014-12-03 06:09:39,796 | DEBUG | ion(2)-127.0.0.1 | tcp                        
      |  -  -  | RMI TCP Connection(2)-127.0.0.1: (port 44444) connection closed
2014-12-03 06:09:39,796 | DEBUG | RMI Scheduler(0) | tcp                        
      |  -  -  | RMI Scheduler(0): close connection
2014-12-03 06:09:39,796 | DEBUG | ion(2)-127.0.0.1 | tcp                        
      |  -  -  | RMI TCP Connection(2)-127.0.0.1: close connection
2014-12-03 06:09:39,796 | DEBUG | ion(1)-127.0.0.1 | tcp                        
      |  -  -  | RMI TCP Connection(1)-127.0.0.1: (port 1099) connection closed
2014-12-03 06:09:39,796 | DEBUG | ion(1)-127.0.0.1 | tcp                        
      |  -  -  | RMI TCP Connection(1)-127.0.0.1: close connection
2014-12-03 06:09:40,311 | DEBUG | RMI Scheduler(0) | tcp                        
      |  -  -  | RMI Scheduler(0): close connection
{code}

> itests execution is very long
> -----------------------------
>
>                 Key: KARAF-3339
>                 URL: https://issues.apache.org/jira/browse/KARAF-3339
>             Project: Karaf
>          Issue Type: Test
>          Components: karaf-test
>    Affects Versions: 2.4.0
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.4.1
>
>
> Even if the execution is succesful, it takes a long time to execute and move 
> forward.
> I suspect the artifacts resolution (resolving first on remote repositories 
> ending with timeout).



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

Reply via email to