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

Quinn Stevenson resolved CAMEL-12659.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.23.0
                   2.22.1
                   2.21.2
                   2.20.4

Correct on master w/commit 130a42223171a39cbe3d77021b2ecf15a21036f8.

Back-ported to 2.22.x w/commit fc069058dbf283e5b72e58d6c3e3f438c8c34ec0
Back-ported to 2.21.x w/commit 9d8f7c662562f17ad9d0282fbfae7fb585fd4d11
Back-ported to 2.20.x w/commit b7281f1eda9c5a4dd7328c3e4d55142f45737a22

> MllpTcpServerConsumer logging failure to set HL7 headers even when setting 
> HL7 headers is disabled
> --------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12659
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12659
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-mllp
>    Affects Versions: 2.20.3, 2.21.1, 2.22.0
>            Reporter: Quinn Stevenson
>            Assignee: Quinn Stevenson
>            Priority: Minor
>             Fix For: 2.20.4, 2.21.2, 2.22.1, 2.23.0
>
>
> In the process of setting Camel message headers from the payload, the 
> MllpTcpServerConsumer is logging an error when it fails to identify the MSH 
> segment of the message.  This error is logged before the hl7Headers 
> configuration option is checked, so the error is always logged - even if 
> setting the HL7 headers is disabled (i.e. hl7Headers=false).
> This is a minor issue, but it effects edge cases where non-HL7 payloads are 
> sent with the MLLP protocol.
> The logic should be changed such that if the hl7Headers option is false, 
> don't do anything (i.e. no log statement).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to