qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3784) Add special JVM environment variable to run dispatcher thread as daemon/non deamon depending from its value.
Date Wed, 01 Feb 2012 12:32:58 GMT

    [ https://issues.apache.org/jira/browse/QPID-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197785#comment-13197785
] 

Robbie Gemmell commented on QPID-3784:
--------------------------------------

The change itself looks reasonable, but I agree with keith we should document the property
in the guide. Also, there have been various code updates since the patch was created (my bad)
including some to field accesses that mean the patch needs updated. Finally,  QpidTestCase
provides system property setting/unsetting utilities, I think the test would look cleaner
if it was updated to use those.
                
> Add special JVM environment variable to run dispatcher thread as daemon/non deamon depending
from its value.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-3784
>                 URL: https://issues.apache.org/jira/browse/QPID-3784
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: 0.15
>            Reporter: Alex Rudyy
>            Assignee: Robbie Gemmell
>             Fix For: 0.15
>
>         Attachments: 0001-QPID-3784-Introduce-JVM-env-variable-to-run-a-dispat.patch
>
>
> Dispatcher thread needs be set daemon/non-daemon depending of new configuration option
to allow manipulating this behaviour.
> Historically, for the 0-8/0-9/0-9-1 client the use of Mina kept the
> JVM alive when a MessageListener was set, allowing asynchronous
> delivery to continue without the user having taken any explicit action
> to keep the JVM alive. Since we removed Mina this is no longer the
> case, and if there are no non-daemon threads then the JVM will now
> exit even though the user has set a MessageListener set. Investigating
> other providers suggests the typical behaviour is to make use of
> non-daemon threads by default, preventing this happening, but allowing
> users who desire that behaviour to configure it as such.
> For example, tibco seem to do exactly what I am proposing with their
> Dispatcher threads:
> https://docs.tibco.com/pub/enterprise_message_service/6.1.0-august-2011/doc/html/tib_ems_api_reference/api/javadoc/com/tibco/tibjms/Tibjms.html#PROP_DAEMON_DISPATCHER
> ActiveMQ seems to control this through transport options, defaulting
> to non-daemon threads with an option to reconfigure it:
> http://activemq.apache.org/tcp-transport-reference.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message