[
https://issues.apache.org/jira/browse/CAMEL-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752286#comment-15752286
]
Claus Ibsen commented on CAMEL-10511:
-------------------------------------
Okay then we need for 2.18.x also. Yeah you just switch branch
First checkout the branch which you need to do once
git co -b camel-2.18.x origin/camel-2.18.x
git co camel-2.18.x
create new branch because you want to do a PR to ASF Camel
git branch some-name
git co some-name
And then cherry pick the master commit using its sha
git cherry-pick 91121843801aed6411b7c91da3b1e502e2d35009
And fix any merge conflicts or whatever its there
git status
shows a status, and you can then use
git cherry-pick --continue
And then its the usual git push some-name to push it to github for a new PR
And then do the same again for 2.17.x. However you can pick the commit from the
2.18.x branch
> MllpTcpClientProducer should read all available bytes in TCP buffer for
> acknowledgment
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-10511
> URL: https://issues.apache.org/jira/browse/CAMEL-10511
> Project: Camel
> Issue Type: Bug
> Components: camel-mllp
> Affects Versions: 2.17.0
> Reporter: Quinn Stevenson
> Assignee: Quinn Stevenson
> Priority: Minor
> Fix For: 2.19.0
>
>
> The MllpClientProducer currently reads the TCP buffer until it receives the
> proper closing frame characters for the MLLP envelope.
> This turned out to be a problem with a certain MLLP Server, which under
> certain circumstances would send double MLLP acknowledgments. As currently
> written, the MllpClientProducer will use the old/double/second acknowledgment
> for the next message - which may cause erroneous results, but in any case is
> clearly wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
