September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-432) One connection per unique JMS server leak

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Ovidiu Feodorov closed JBMESSAGING-432. --------------------------------------- Resolution: Won't Fix > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-432) One connection per unique JMS server leak

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Ovidiu Feodorov updated JBMESSAGING-432: ---------------------------------------- Fix Version/s: 1.0.1.CR5 (was: 1.2.1) > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3345) Synch up with tomcat6 based jbossweb as the bundled web container

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3345?page=all ] Remy Maucherat resolved JBAS-3345. ---------------------------------- Resolution: Done > Synch up with tomcat6 based jbossweb as the bundled web container > ----------------------------------------------------------------- > > Key: JBAS-3345 > URL: http://jira.jboss.com/jira/browse/JBAS-3345 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Scott M Stark > Assigned To: Remy Maucherat > Priority: Blocker > Fix For: JBossAS-5.0.0.Beta > > > We need a tomcat6 based version of jbosseb as the bundled web container for the jboss5 release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-432) One connection per unique JMS server leak

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-432: --------------------------------------------- Can we just mark won't fix? A proper fix here would require changes on the API anyway. > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.2.1 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-529) Install TCK5 locally and fix all errors that prevent Messaging from passing

by Ovidiu Feodorov (JIRA)

Install TCK5 locally and fix all errors that prevent Messaging from passing --------------------------------------------------------------------------- Key: JBMESSAGING-529 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-529 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-432) One connection per unique JMS server leak

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Ovidiu Feodorov updated JBMESSAGING-432: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.1.CR5) > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.2.1 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-432) One connection per unique JMS server leak

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-432: --------------------------------------------- Disconnecting the client will make TIME_WAIT state TCP/IP connections accumulate again, so this is not the right fix. Minor issue anyway, pushed for later, when we'll have time for it. > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-432) One connection per unique JMS server leak

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Clebert Suconic reopened JBMESSAGING-432: ----------------------------------------- > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-432) One connection per unique JMS server leak

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Clebert Suconic closed JBMESSAGING-432. --------------------------------------- Resolution: Done > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-432) One connection per unique JMS server leak

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-432: --------------------------------------------- Tim, I'm just changing ClientConnectionFactoryDeleage to change that client. If you could please verify if this is correct. I have executed testcases and this didn't change any behavior. > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006