[
https://issues.apache.org/activemq/browse/SM-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49047#action_49047
]
Gert Vanthienen commented on SM-1754:
-------------------------------------
Ron,
I have updated the test to use the same values (16 core threads, 32 max threads
and a queue size of 256) as the distribution to avoid any further confusion,
but it really doesn't make any difference for these tests. In fact, with the
default setup we'll probably end up using even more threads for running the
unit tests.
My setup had 4 core threads, 16 max threads and a queue size of 0, effectively
causing the ExecutorFactory to create 4 core threads of the first 4 tasks and
only create the additional 12 threads (up to 16) if all core threads are busy
and more work arrives. Using the default settings with these unit tests will
create the 16 core threads on the first 16 tasks that arrive, but we'll
probably never write a unit tests that is using all 16 core threads and queues
over 256 tasks to trigger the creation of additional threads anyway.
Regards,
Gert
> running servicemix-eip unit tests stalls intermittently
> -------------------------------------------------------
>
> Key: SM-1754
> URL: https://issues.apache.org/activemq/browse/SM-1754
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-eip
> Affects Versions: servicemix-eip-2008.01
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: servicemix-eip-2008.02
>
>
> The servicemix-eip unit tests sometimes stall while running them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
