[
https://issues.apache.org/jira/browse/STORM-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809832#comment-17809832
]
Richard Zowalla commented on STORM-4019:
----------------------------------------
Yup - both use log4j2. I am wondering if it is an Storm issue or due to the
difference in log4j2 versions. They might be compatible, so can you test by
manually upgrading log4j2 on your 1.2.2 cluster and check if the log behaves as
expected with your config? If so, we can dig further.
Might also be good to get a small self containerdcode sample.
> Missing some parameters while logging external API calls
> ---------------------------------------------------------
>
> Key: STORM-4019
> URL: https://issues.apache.org/jira/browse/STORM-4019
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-client, storm-core
> Affects Versions: 2.4.0
> Reporter: Arth Gupta
> Priority: Critical
> Attachments: Screenshot 2024-01-16 at 4.37.20 PM.png, Screenshot
> 2024-01-16 at 4.38.26 PM.png, worker.xml
>
>
> Hi, I am upgrading the Apache Storm from version 1.2.2 to 2.4.0
> and while logging the external API calls, I am not getting the desired output
> format based on worker.xml mentioned in log4j2 directory
>
> Attaching screenshots
> # Screenshot 2024-01-16 at 4.37.20 PM.png -> apache storm 2.4.0 logs
> # Screenshot 2024-01-16 at 4.38.26 PM.png -> apache storm 1.2.2 logs
> # worker.xml -> log4j configuration file
>
> Problem -> I am passing cid and rid from the logger that is getting printed
> in the apache storm 1.2.2 logs but not in 2.4.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
