Issue Details (XML | Word | Printable)

Key: LINGO-44
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Jason Koch
Votes: 3
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Lingo

MultiplexingRequestor leaves lingering threads after close() called

Created: 04/Sep/07 08:30 PM   Updated: 18/Dec/08 05:08 PM
Component/s: None
Affects Version/s: 1.3
Fix Version/s: None

Time Tracking:
Original Estimate: 30 minutes
Original Estimate - 30 minutes
Remaining Estimate: 30 minutes
Remaining Estimate - 30 minutes
Time Spent: Not Specified
Time Spent - Not Specified

File Attachments: 1. Java Source File MultiplexingRequestor.java (9 kB)

Environment: ActiveMQ 4.1.1, Windows XP

Patch Submitted: Yes


 Description  « Hide

The MultiplexingRequestor class does not have a close() method to close the ScheduledThreadPoolExecutor. This leaves non-daemon threads hanging around and thus applications will not quit until System.exit() is called (causing Tomcat applications exporting Lingo services and standard Java apps calling Lingo services to hang forever on shutdown).

Attached is an updated MultiplexingRequestor class that fixes the issue.



Jason Koch added a comment - 13/Sep/07 08:02 PM

Blog entry related to this: http://bluedevel.com/blog/?p=3


Carlos Quiroz added a comment - 08/Oct/07 06:37 AM

I can confirm this issue and certainly creates problems while using Lingo inside Tomcat

The attached patch works for me

Carlos


elan added a comment - 07/Dec/07 12:55 PM

Which release will have this critical bug fix?


Barry Lagerweij added a comment - 18/Dec/08 05:08 PM

I've encountered the same issue on Tomcat, when can we expect a bugfix release ?