You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/26 14:54:43 UTC
[jira] [Assigned] (QPID-3784) Add special JVM environment variable
to run dispatcher thread as daemon/non deamon depending from its value.
[ https://issues.apache.org/jira/browse/QPID-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-3784:
--------------------------------
Assignee: Alex Rudyy
> 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: Alex Rudyy
> Fix For: 0.15
>
>
> 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