[jira] Created: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called
by JIRA jira@codehaus.org
::
Rate this Message:
MultiplexingRequestor leaves lingering threads after close() called
------------------------------------------------------------------- Key: LINGO-44 URL: http://jira.codehaus.org/browse/LINGO-44 Project: Lingo Issue Type: Bug Affects Versions: 1.3 Environment: ActiveMQ 4.1.1, Windows XP Reporter: Jason Koch Priority: Critical Attachments: MultiplexingRequestor.java 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107331 ] Jason Koch commented on LINGO-44: --------------------------------- Blog entry related to this: http://bluedevel.com/blog/?p=3 > MultiplexingRequestor leaves lingering threads after close() called > ------------------------------------------------------------------- > > Key: LINGO-44 > URL: http://jira.codehaus.org/browse/LINGO-44 > Project: Lingo > Issue Type: Bug > Affects Versions: 1.3 > Environment: ActiveMQ 4.1.1, Windows XP > Reporter: Jason Koch > Priority: Critical > Attachments: MultiplexingRequestor.java > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109278 ] Carlos Quiroz commented on LINGO-44: ------------------------------------ I can confirm this issue and certainly creates problems while using Lingo inside Tomcat The attached patch works for me Carlos > MultiplexingRequestor leaves lingering threads after close() called > ------------------------------------------------------------------- > > Key: LINGO-44 > URL: http://jira.codehaus.org/browse/LINGO-44 > Project: Lingo > Issue Type: Bug > Affects Versions: 1.3 > Environment: ActiveMQ 4.1.1, Windows XP > Reporter: Jason Koch > Priority: Critical > Attachments: MultiplexingRequestor.java > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called
by JIRA jira@codehaus.org
::
Rate this Message:
[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116196 ] elan commented on LINGO-44: --------------------------- Which release will have this critical bug fix? > MultiplexingRequestor leaves lingering threads after close() called > ------------------------------------------------------------------- > > Key: LINGO-44 > URL: http://jira.codehaus.org/browse/LINGO-44 > Project: Lingo > Issue Type: Bug > Affects Versions: 1.3 > Environment: ActiveMQ 4.1.1, Windows XP > Reporter: Jason Koch > Priority: Critical > Attachments: MultiplexingRequestor.java > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email |
| Free Forum Powered by Nabble | Forum Help |