[ 
https://issues.apache.org/jira/browse/CAMEL-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755466#comment-15755466
 ] 

ASF GitHub Bot commented on CAMEL-10511:
----------------------------------------

GitHub user hqstevenson opened a pull request:

    https://github.com/apache/camel/pull/1356

    CAMEL-10511: Backport to 2.17

    Updated MllpTcpClientProducer and MllpTcpServerConsumer to consume all 
available data on socket

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hqstevenson/camel CAMEL-10511-2.17

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1356.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1356
    
----
commit a53540da1e5b7550355c68dc9e98c5e6e77c109a
Author: Quinn Stevenson <[email protected]>
Date:   2016-12-16T20:41:12Z

    CAMEL-10511:  Updated MllpTcpClientProducer and MllpTcpServerConsumer to 
consume all available data on socket - backport to 2.17

----


> 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.18.2, 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)

Reply via email to