activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jlindwall <>
Subject Forcing daemon threads when using discovery transport
Date Fri, 05 Dec 2014 01:12:21 GMT
I see that I can add a "daemon=true" parameter to tcp broker urls to force
the ActiveMQ Transport threads to be created as daemon threads.  I've tested
this and it works fine, e.g.

However I am not using failover or tcp transports directly: I am using
discovery transport in my broker urls, like this: 

Is it possible to force the "daemon=true" parameter to always be in effect
for this style of transport?  Or perhaps there is some other mechanism?

I tried adding daemon=true, transport.daemon=true, tcp.daemon=true to the
discovery urls to no avail.

Perhaps this can be handled in my server configuration?  My
transportConnector and networkConnector appear as follows:


View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message