[
https://issues.apache.org/jira/browse/BATIK-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350485#comment-17350485
]
Gruust commented on BATIK-939:
------------------------------
h1. shutdown() function for CleanerThread #27
Opened pull request at https://github.com/apache/xmlgraphics-batik/pull/27
Instead of using or suppressing interrupts, a simple CountDownLatch is used to
check whether the thread should shut down or not.
Would be nice if I could at least run Batik in my maven build process without
spawning external Java processes (maven complains about the Daemon thread not
shutting down).
> [PATCH] CleanerThread never terminates, causes leaks in webapp
> --------------------------------------------------------------
>
> Key: BATIK-939
> URL: https://issues.apache.org/jira/browse/BATIK-939
> Project: Batik
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 1.7
> Environment: Operating System: Windows XP
> Platform: PC
> URL:
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-batik-users/201002.mbox/%[email protected]%3E
> Reporter: Joel Carranza
> Assignee: Batik Developer's Mailing list
> Labels: PatchAvailable
> Attachments: CleanerThread.java.patch, CleanerThread.java.patch
>
>
> org.apache.batik.util.CleanerThread does not self-terminate, nor is there a
> way to dispose of it programatically. When using Batik within a webapp, this
> prevents the webapp's classloader from being garbage collected, eventually
> causing PermGen: Out of Memory errors after several webapp redeploys.
> CleanerThread should expose some method that allows for it to be terminated.
> Patch attached which follows the same solution used in geotools package
> [https://fisheye.codehaus.org/browse/GEOT-2742]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
