You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "john lilley (Jira)" <ji...@apache.org> on 2022/12/03 00:46:00 UTC

[jira] [Updated] (ARTEMIS-4105) useGlobalPools=false or ActiveMQConnectionFactory.setUseGlobalPools(false) makes for dead services

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

john lilley updated ARTEMIS-4105:
---------------------------------
    Attachment: amqtest.zip

> useGlobalPools=false or ActiveMQConnectionFactory.setUseGlobalPools(false) makes for dead services
> --------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4105
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4105
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: ActiveMQ-Artemis-Native
>    Affects Versions: 2.27.1
>            Reporter: john lilley
>            Assignee: Clebert Suconic
>            Priority: Major
>         Attachments: amqtest.zip
>
>
> We have an application, which mostly interfaces with the vanilla JMS driver for Artemis, except for the connection factory.
> In an attempt to work around ARTEMIS-4104, I investigated using per-connection thread pools, in the hope that I could divide services in categories, and have each category use an independent thread pool.  Instead, I find that the application is completely dead.  Nothing is ever delivered to services.
> To validate, build the attached project using maven 3.8 and JDK 17.  Run the Main, and ... nothing will happen after the requests are posted to the queue.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)