Hi, Thanks for your replies! I would also support making the default configuration production ready and simple. In my opinion, it is better to have the examples in Wiki or similar, instead of the default configuration.
-Aleksi rajdavies wrote: > > Hi Aleksi, > > creating lots of temporary topics is definately ok. > +1 to change useDedicatedTaskRunner back to false > > cheers, > > Rob > > Rob Davies > http://fusesource.com > http://rajdavies.blogspot.com/ > > On 26 May 2009, at 14:38, Aleksi Kallio wrote: > >> >> Hi, >> >> >> Aleksi Kallio wrote: >>> >>> Because of the excessive thread creation, using dedicated >>> TaskRunners was >>> also slower. If they are preferred, shouldn't temporary topics (and >>> queues) be handled in a more lighweight manner? >>> >> >> My question did not arouse much interest, so I'll have a second go: Is >> creating a lot of temporary topics (resulting in a lots of threads >> at the >> broker) against the general design philosophy of JMS or ActiveMQ? In >> other >> words, are we doing something stupid or is it just that the default >> value of >> UseDedicatedTaskRunner is a bit counterintuitive? >> >> Cheers, >> Aleksi >> >> -- >> View this message in context: >> http://www.nabble.com/Why-UseDedicatedTaskRunner-is-true-by-default--tp23631976p23723071.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> > > > > -- View this message in context: http://www.nabble.com/Why-UseDedicatedTaskRunner-is-true-by-default--tp23631976p23738535.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
