You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/10/31 20:33:59 UTC
[jira] Created: (GERONIMO-1121) ConnectionManager leaves several timer tasks running even after gbeans are shutdown -- causes memory leak
ConnectionManager leaves several timer tasks running even after gbeans are shutdown -- causes memory leak
---------------------------------------------------------------------------------------------------------
Key: GERONIMO-1121
URL: http://issues.apache.org/jira/browse/GERONIMO-1121
Project: Geronimo
Type: Bug
Components: connector
Versions: 1.0
Reporter: David Jencks
Fix For: 1.0
The AbsractSinglePoolConnectionInterceptor has a IdleRemoverTask and a FillTask that are added to a timer and never removed. Among other possible problems, this results in a memory leak (thanks to Kevan Miller) :
java.util.TaskQueue [Stack Local, Monitor Used]
queue --> java.util.TimerTask[128]
[5] --> org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor$IdleReleaser
this$0 --> org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
next --> org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor
next --> org.apache.geronimo.connector.outbound.MCFConnectionInterceptor
stack --> org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor
next --> org.apache.geronimo.connector.outbound.TCCLInterceptor
classLoader --> org.apache.geronimo.kernel.config.MultiParentClassLoader
We need to figure out how to shut down the pool cleanly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-1121) ConnectionManager leaves several timer tasks running even after gbeans are shutdown -- causes memory leak
Posted by "Kevan Miller (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1121?page=all ]
Kevan Miller resolved GERONIMO-1121:
------------------------------------
Resolution: Duplicate
Assign To: Kevan Miller
This problem was fixed under GERONIMO-1125. My mistake for forgetting/not noticing this issue.
> ConnectionManager leaves several timer tasks running even after gbeans are shutdown -- causes memory leak
> ---------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-1121
> URL: http://issues.apache.org/jira/browse/GERONIMO-1121
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0
> Reporter: David Jencks
> Assignee: Kevan Miller
> Fix For: 1.0
>
> The AbsractSinglePoolConnectionInterceptor has a IdleRemoverTask and a FillTask that are added to a timer and never removed. Among other possible problems, this results in a memory leak (thanks to Kevan Miller) :
> java.util.TaskQueue [Stack Local, Monitor Used]
> queue --> java.util.TimerTask[128]
> [5] --> org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor$IdleReleaser
> this$0 --> org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
> next --> org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor
> next --> org.apache.geronimo.connector.outbound.MCFConnectionInterceptor
> stack --> org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor
> next --> org.apache.geronimo.connector.outbound.TCCLInterceptor
> classLoader --> org.apache.geronimo.kernel.config.MultiParentClassLoader
> We need to figure out how to shut down the pool cleanly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1121) ConnectionManager leaves several timer tasks running even after gbeans are shutdown -- causes memory leak
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1121?page=all ]
Matt Hogstrom closed GERONIMO-1121:
-----------------------------------
> ConnectionManager leaves several timer tasks running even after gbeans are shutdown -- causes memory leak
> ---------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-1121
> URL: http://issues.apache.org/jira/browse/GERONIMO-1121
> Project: Geronimo
> Type: Bug
> Components: connector
> Versions: 1.0
> Reporter: David Jencks
> Assignee: Kevan Miller
> Fix For: 1.0
>
> The AbsractSinglePoolConnectionInterceptor has a IdleRemoverTask and a FillTask that are added to a timer and never removed. Among other possible problems, this results in a memory leak (thanks to Kevan Miller) :
> java.util.TaskQueue [Stack Local, Monitor Used]
> queue --> java.util.TimerTask[128]
> [5] --> org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor$IdleReleaser
> this$0 --> org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
> next --> org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor
> next --> org.apache.geronimo.connector.outbound.MCFConnectionInterceptor
> stack --> org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor
> next --> org.apache.geronimo.connector.outbound.TCCLInterceptor
> classLoader --> org.apache.geronimo.kernel.config.MultiParentClassLoader
> We need to figure out how to shut down the pool cleanly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira