[ 
https://issues.apache.org/jira/browse/QPID-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lorenz Quack updated QPID-7474:
-------------------------------
    Description: 
Currently when statistics gathering is enabled on the broker it iterates over 
all virtual hosts and accesses their EventLogger. Some VirtualHosts (e.g., 
BDBHAReplicaVirtualHost or RedirectingVirtualHost) do not have an EventLogger 
and will return null causing a NullPointerException in the 
StatisticsReportingTask that will be logged with a stacktrace and prevents 
other VHs from reporting their statistics.


  was:
Currently when statistics gathering is enabled on the broker it iterates over 
all virtual hosts and accesses their EventLogger. Some VirtualHosts (e.g., 
RedirectingVirtualHost) do not have an EventLogger and will return null causing 
a NullPointerException in the StatisticsReportingTask that will be logged with 
a stacktrace and prevents other VHs from reporting their statistics.



> [Java Broker] Guard against NPE in StatisticsReportingTask
> ----------------------------------------------------------
>
>                 Key: QPID-7474
>                 URL: https://issues.apache.org/jira/browse/QPID-7474
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: qpid-java-6.0, qpid-java-6.0.4, qpid-java-6.1
>            Reporter: Lorenz Quack
>
> Currently when statistics gathering is enabled on the broker it iterates over 
> all virtual hosts and accesses their EventLogger. Some VirtualHosts (e.g., 
> BDBHAReplicaVirtualHost or RedirectingVirtualHost) do not have an EventLogger 
> and will return null causing a NullPointerException in the 
> StatisticsReportingTask that will be logged with a stacktrace and prevents 
> other VHs from reporting their statistics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to