Lingo

MultiplexingRequestor leaves lingering threads after close() called

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.3
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    ActiveMQ 4.1.1, Windows XP
  • Patch Submitted:
    Yes
  • Number of attachments :
    1

Description

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.

Activity

Hide
Jason Koch added a comment -

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

Show
Jason Koch added a comment - Blog entry related to this: http://bluedevel.com/blog/?p=3
Hide
Carlos Quiroz added a comment -

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

The attached patch works for me

Carlos

Show
Carlos Quiroz added a comment - I can confirm this issue and certainly creates problems while using Lingo inside Tomcat The attached patch works for me Carlos
Hide
elan added a comment -

Which release will have this critical bug fix?

Show
elan added a comment - Which release will have this critical bug fix?
Hide
Barry Lagerweij added a comment -

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

Show
Barry Lagerweij added a comment - I've encountered the same issue on Tomcat, when can we expect a bugfix release ?

People

Vote (3)
Watch (1)

Dates

  • Created:
    Updated:

Time Tracking

Estimated:
30m
Original Estimate - 30 minutes
Remaining:
30m
Remaining Estimate - 30 minutes
Logged:
Not Specified
Time Spent - Not Specified