[pulsar] 02/03: Fix the wrong parameter in the log. (#14309)

[mm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mmarshall pushed a commit to branch branch-2.8
in repository https://gitbox.apache.org/repos/asf/pulsar.git

commit 5748d8dbb7637ac653b34a0a4d34a15d8a715339
Author: Qiang Zhao <74...@users.noreply.github.com>
AuthorDate: Wed Feb 16 14:05:53 2022 +0800

    Fix the wrong parameter in the log. (#14309)
    
    ### Motivation
    
    Bad parameters in the log will always print "null", which can confuse users.
    
    ### Modifications
    
    - Correct exception parameter.
    
    (cherry picked from commit 9b003f96f1deb8e02a1654e30fbddd211d787e8e)
---
 .../pulsar/broker/service/SystemTopicBasedTopicPoliciesService.java     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/SystemTopicBasedTopicPoliciesService.java b/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/SystemTopicBasedTopicPoliciesService.java
index c91f66a..ca274b6 100644
--- a/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/SystemTopicBasedTopicPoliciesService.java
+++ b/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/SystemTopicBasedTopicPoliciesService.java
@@ -316,7 +316,7 @@ public class SystemTopicBasedTopicPoliciesService implements TopicPoliciesServic
                 reader.readNextAsync().whenComplete((msg, e) -> {
                     if (e != null) {
                         log.error("[{}] Failed to read event from the system topic.",
-                                reader.getSystemTopic().getTopicName(), ex);
+                                reader.getSystemTopic().getTopicName(), e);
                         future.completeExceptionally(e);
                         readerCaches.remove(reader.getSystemTopic().getTopicName().getNamespaceObject());
                         policyCacheInitMap.remove(reader.getSystemTopic().getTopicName().getNamespaceObject());