Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-1.8.2.GA_P03
-
Fix Version/s: EE-1.8.2.GA_P04
-
Component/s: Framework
-
Labels:None
-
Environment:Apache Tomcat 6.0.32
Description
As of some 6.0.x version of Tomcat it complains about hanging threads upon shutdown or undeploy:
Jun 16, 2011 10:52:43 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/timezone-failover-push] appears to have started a thread named [Render Thread - 1] but has failed to stop it. This is very likely to create a memory leak.
Though JStack shows that even though the complaint is made that the threads do get cleaned up (probably forcibly by Tomcat). This seems to affect multiple parts of ICEfaces, namely the Core, MSC and Push Server. Each issue can be addressed in a separate JIRA linking to this one.
Jun 16, 2011 10:52:43 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/timezone-failover-push] appears to have started a thread named [Render Thread - 1] but has failed to stop it. This is very likely to create a memory leak.
Though JStack shows that even though the complaint is made that the threads do get cleaned up (probably forcibly by Tomcat). This seems to affect multiple parts of ICEfaces, namely the Core, MSC and Push Server. Each issue can be addressed in a separate JIRA linking to this one.
Issue Links
- depends on
-
ICE-6974
Hanging Core threads upon shutdown or undeploy
-
- Closed
-
-
ICE-6975
Hanging Push Server threads upon shutdown or undeploy
-
- Closed
-
-
ICE-6990
Hanging Message Service Client threads upon shutdown or undeploy
-
- Closed
-
-
ICE-7988
Hanging Monitor Runner thread upon shutdown or redeploy
-
- Closed
-
-
ICE-7989
Hanging Session Monitor thread upon shutdown or redeploy
-
- Closed
-
-
ICE-8002
Hanging Render threads upon shutdown or undeploy
-
- Closed
-
Show 1 more links (1 depends on)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Jack van Ooststroom [ jack.van.ooststroom ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Comment |
[ Sending core/src/com/icesoft/net/messaging/MessagePipeline.java Sending core/src/com/icesoft/net/messaging/MessageServiceClient.java Transmitting file data .. Committed revision 28657. ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Comment | [ MessagePipelines can now be closed as well. Causing any outstanding PublishTask to get cancelled. However, it could still happen that between server shutdown and the invocations of the Servlet's destroy() methods, another UpdatedViews message will be attempted to send to Push Server using HTTP. At this point the invocation of HttpURLConnection.getInputStream() seems to hang presumably because the ports or the listeners of the servers don't allow any more incoming requests. This causes warnings to be logged for Core Threads and MSC Threads. Please refer to the main JIRA for more specifics. Marking this one as FIXED. ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |