[
https://issues.apache.org/jira/browse/CAMEL-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044466#comment-13044466
]
Claus Ibsen commented on CAMEL-4042:
------------------------------------
Looking at the console output from Apache Hudson
https://builds.apache.org/job/Camel.trunk.fulltest/313/console
I can see it takes about 30+ sec. to archive a JAR file. So after the test it
archives the JAR and that takes a very long time
For example:
[JENKINS] Archiving
/home/hudson/hudson-slave/workspace/Camel.trunk.fulltest/camel-trunk/components/camel-jibx/target/camel-jibx-2.8-SNAPSHOT.jar
to
/home/hudson/hudson/jobs/Camel.trunk.fulltest/modules/org.apache.camel$camel-jibx/builds/2011-06-05_06-14-11/archive/org.apache.camel/camel-jibx/2.8-SNAPSHOT/camel-jibx-2.8-SNAPSHOT.jar
And since there is 100+ JAR files to archive then that takes about 1h.
Executing the unit tests seems to be about the same pace they take to run on my
laptop. Eg camel-core in about 20 min. camel-spring in about 6 min.
https://builds.apache.org/job/Camel.trunk.fulltest/313/
> Shutdown the thread pool when the test is over
> ----------------------------------------------
>
> Key: CAMEL-4042
> URL: https://issues.apache.org/jira/browse/CAMEL-4042
> Project: Camel
> Issue Type: Improvement
> Components: tests
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.8.0
>
>
> The thread size will keep increasing when we run the tests of camel.
> After digging the code for a while I found there are lots of thread pool are
> never shutdown when the test is over.
> We should release these resources after running test.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
