[
https://issues.apache.org/jira/browse/QPID-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-6608:
-----------------------------
Description:
If VH housekeeping thread experiences an unexpected exception, the current
implementation (uses a ScheduledThreadPoolExecutor) neither reports the
exception nor causes the Broker to shutdown.
Note that ScheduledThreadPoolExecutor do not use the uncaught exception
handlers, we need to intercept #afterExecute.
http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html#afterExecute(java.lang.Runnable,%20java.lang.Throwable)
(This came to light during the investigation of QPID-6607. QueueRunner
threading is now performed by the housekeeper and its exceptions were being
swallowed silently).
was:
If VH housekeeping thread experiences an unexpected exception, the current
implementation (uses a ScheduledThreadPoolExecutor) neither reports the
exception nor causes the Broker to shutdown the Broker.
Note that ScheduledThreadPoolExecutor do not use the uncaught exception
handlers, we need to intercept #afterExecute.
http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html#afterExecute(java.lang.Runnable,%20java.lang.Throwable)
(This came to light during the investigation of QPID-6607. QueueRunner
threading is now performed by the housekeeper and its exceptions were being
swallowed silently).
> Unexpected exceptions occurring within virtualhost housekeeping thread are
> not logged and do not cause the Broker to fail
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6608
> URL: https://issues.apache.org/jira/browse/QPID-6608
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Lorenz Quack
> Fix For: qpid-java-6.0
>
> Attachments:
> 0001-QPID-6608-Java-Broker-Uncaught-exceptions-in-the-vho.patch
>
>
> If VH housekeeping thread experiences an unexpected exception, the current
> implementation (uses a ScheduledThreadPoolExecutor) neither reports the
> exception nor causes the Broker to shutdown.
> Note that ScheduledThreadPoolExecutor do not use the uncaught exception
> handlers, we need to intercept #afterExecute.
> http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html#afterExecute(java.lang.Runnable,%20java.lang.Throwable)
> (This came to light during the investigation of QPID-6607. QueueRunner
> threading is now performed by the housekeeper and its exceptions were being
> swallowed silently).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
