You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "David Ingham (JIRA)" <ji...@apache.org> on 2013/09/24 12:53:05 UTC
[jira] [Updated] (QPID-5166) Lazily create dispatcher thread in JMS
Session implementation
[ https://issues.apache.org/jira/browse/QPID-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Ingham updated QPID-5166:
-------------------------------
Attachment: QPID-5166.patch
This patch updates SessionImpl to create the dispatcher thread when required rather than at instantiation.
> Lazily create dispatcher thread in JMS Session implementation
> -------------------------------------------------------------
>
> Key: QPID-5166
> URL: https://issues.apache.org/jira/browse/QPID-5166
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.24
> Environment: Qpid JMS AMQP 1.0 client library (v0.24)
> Reporter: David Ingham
> Priority: Minor
> Attachments: QPID-5166.patch
>
>
> The implementation of JMS Session uses a thread to dispatch messages to message listeners. This thread is created on instantiation of the Session even though it is only required if the application goes on to create a MessageConsumer with a MessageListener from the Session. For environments that create lots of Sessions with only MessageProducers then this is an unnecessary overhead. The recommendation is to change the Session implementation to only create these dispatcher threads when required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org