You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2010/01/24 23:36:45 UTC

[jira] Updated: (SMXCOMP-704) smx-jms thread pool does not dynamically expand as expected

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

Ron Gavlin updated SMXCOMP-704:
-------------------------------

    Attachment: jmsEip3Test.zip

> smx-jms thread pool does not dynamically expand as expected
> -----------------------------------------------------------
>
>                 Key: SMXCOMP-704
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-704
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-jms
>    Affects Versions: servicemix-jms-2009.01
>         Environment: Windows XP SP2, JDK 6 update 10, servicemix.xml (jca & jms flows commented), servicemix.properties (servicemix.maximumPoolSize=256)
>            Reporter: Ron Gavlin
>            Priority: Critical
>         Attachments: jmsEip3Test.zip
>
>
> The smx-jms thread pool does not dynamically expand as expected.
> In order to reproduce the problem:
> 1. Edit servicemix.xml & servicemix.properties as described in the "Environment" section
> 2. Deploy my-sa-1.0-SNAPSHOT.zip from the attached test case to the hotdeploy directory
> 3. Execute jms-client.bat found in the attached test case
> The jms-client copies 100 messages to queue "queue/input". SA my-sa-1.0-SNAPSHOT.zip should take the messages of this input queue and eventually put them onto queue "queue/output". This does not happen. Instead, some messages get stuck on the servicemix-jms SedaQueue and the rest remain on queue "queue/input". 
> Next, edit servicemix.properties and change servicemix.corePoolSize from the default value of 16 to 256. Re-execute the steps above and notice that the SA puts all messages onto queue "queue/output" as expected.
> This bug results in extremely unexpected behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.