[
https://issues.jboss.org/browse/JGRP-541?page=com.atlassian.jira.plugin.s...
]
Peter Novak commented on JGRP-541:
----------------------------------
In our environment we have similar problem like
https://issues.jboss.org/browse/ISPN-1444.
It is testing environment where we execute some testing scripts that are using Infinispan
as a Cache provider. For this environment we have special configuration, where Infinispan
Threads are created as DAEMON threads, because we need to stop the JVM instance, when the
executed scripts finished. We donĀ“t want to put the System.exit(0) into scripts, because
it avoids the re-usability. We already have configured the Infinispan to support
non-daemon threads for this environment, but it does not stop, because it is using the
JGroups and there is no possibility to configure the ThreadPools to create Daemons threads
for this situation.
I understand your motivation for "non daemon threads", and I agree, that by
default it should be "non daemon", but In my opinion, there are some situations,
where this config parameter could be very helpful. We use the jgroups-2.12.1.3.Final.
Please, add some configuration parameter to provide choice for your users, like it is in
Infinispan. Thank you.
Thread pools in transport protocols not using daemon threads
------------------------------------------------------------
Key: JGRP-541
URL:
https://issues.jboss.org/browse/JGRP-541
Project: JGroups
Issue Type: Bug
Affects Versions: 2.5
Reporter: Paul Ferraro
Assignee: Bela Ban
Priority: Minor
Fix For: 2.5
The ThreadFactory used by the ThreadPoolExecutors (for both regular and OOB messages) in
org.jgroups.protocols.TP does not create daemon threads. During runtime the JVM will
resist exiting unless the channel is explicitly shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira