Hi all,
MultiplexingRequestor class used by lingo creates an instance of ScheduledThreadPoolExecutor and passes it to its DefaultTimeoutMap instance variable. This DefaultTimeoutMap's constructor creates a thread using the executor. This executor's shutdown() method is not called either by any method of DefaultTimeoutMap or those of MultiplexingRequestor.
We had to copy MultiplexingRequestor class and override close() method from its base class, added code to shutdown the executor given to DefaultTimeoutMap. Perhaps DefaultTimeoutMap itself should manage shutting down the executor?
The question is: Is this a bug or we are missing something here?
Environment: Lingo 1.3, ActiveMQ-4.0-RC2, Spring 2.0
-Madhav
