[
https://issues.apache.org/jira/browse/PHOENIX-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068957#comment-15068957
]
Hudson commented on PHOENIX-2528:
---------------------------------
FAILURE: Integrated in Phoenix-master #1034 (See
[https://builds.apache.org/job/Phoenix-master/1034/])
PHOENIX-2528 Pherf JVM doesn't exit due to un-closed ThreadPool (elserj)
(mujtaba: rev 69bd32f0def442bd1a660affcc2198acabda4793)
*
phoenix-pherf/src/main/java/org/apache/phoenix/pherf/workload/WriteWorkload.java
* phoenix-pherf/src/main/java/org/apache/phoenix/pherf/Pherf.java
* phoenix-pherf/src/main/java/org/apache/phoenix/pherf/util/ResourceList.java
> Pherf JVM doesn't exit due to un-closed ThreadPool
> --------------------------------------------------
>
> Key: PHOENIX-2528
> URL: https://issues.apache.org/jira/browse/PHOENIX-2528
> Project: Phoenix
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2528.1.patch, PHOENIX-2528.patch
>
>
> In trying to use the pherf tool in "cluster" mode, the invocation of
> {{Pherf}} never exited. I had removed a {{System.exit(0)}} already because it
> was suppressing an Exception.
> The JVM never exited because there were a number of threads (8) still running
> and not marked as daemon. After a while, I finally tracked down these threads
> to {{WriteWorkload}} which didn't bother to close the pool.
> I believe the System.exit was forcing the JVM to exit instead of letting it
> exit naturally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
