Description:
Activating debugging level to DEBUG does not log the inbound enpoint name, which make things difficult to trace. Please add that information to all debug logs.
Typical message:
Oct 8, 2019 @ 11:12:25.981 host.name:XXXXXXX source:/var/log/wso2ei/integrator/wso2carbon.log @timestamp:Oct 8, 2019 @ 11:12:25.981 client:wso2 offset:1,263,329 beat.name:XXXXXXX beat.hostname:XXXXXXX beat.version:6.8.3 tags:beats_input_codec_plain_applied @version:1 message:{org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} - Suspending polling as the pollingSuspensionLimit of 2 reached. Polling will be re-started after 120000 milliseconds log.file.path:/var/log/wso2ei/integrator/wso2carbon.log level:INFO _id:y47tq20BmFOqqeG3zpIq _type:_doc _index:rq-wso2-2019.10.08 _score: -
Description: Activating debugging level to DEBUG does not log the inbound enpoint name, which make things difficult to trace. Please add that information to all debug logs.
Typical message:
Oct 8, 2019 @ 11:12:25.981 host.name:XXXXXXX source:/var/log/wso2ei/integrator/wso2carbon.log @timestamp:Oct 8, 2019 @ 11:12:25.981 client:wso2 offset:1,263,329 beat.name:XXXXXXX beat.hostname:XXXXXXX beat.version:6.8.3 tags:beats_input_codec_plain_applied @version:1 message:{org.wso2.carbon.inbound.endpoint.protocol.jms.JMSPollingConsumer} - Suspending polling as the pollingSuspensionLimit of 2 reached. Polling will be re-started after 120000 milliseconds log.file.path:/var/log/wso2ei/integrator/wso2carbon.log level:INFO _id:y47tq20BmFOqqeG3zpIq _type:_doc _index:rq-wso2-2019.10.08 _score: -
Suggested Labels:
Suggested Assignees:
Affected Product Version: WSO2 Integrator 6.4.0 (Carbon-mediation)
OS, DB, other environment details and versions:
Windows 7, Oracle.
Steps to reproduce:
Related Issues: