You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Clay <cl...@emc.com> on 2013/08/16 01:08:25 UTC
MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
A .Net WCF client is throwing a parsing error on the MTOM message returned
from our Camel endpoint.
Looking at the message sent by Camel in WireShark, we see the header part is
preceded by ”CRLFLF”, ”--”, ”boundary”, instead of ”CRLF”, ”--”, ”boundary”,
which is not according to the RFC 1341 specification:
- http://www.w3.org/Protocols/rfc1341/0_TableOfContents.html
- http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
Is this a known issue in Apache Camel or is there another explanation?
Thanks,
Clay
--
View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Christian Müller <ch...@gmail.com>.
Thanks for sharing!
Because this CXF issue is fixed in CXF 2.5.7, 2.6.4 and 2.7.1, the
following Camel versions should work too for you:
Camel 2.9.6+
Camel 2.10.4+
Camel 2.11.0+
Best,
Christian
-----------------
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Tue, Aug 20, 2013 at 6:18 PM, Clay <cl...@emc.com> wrote:
> This bug is fixed in CXF-4482!+
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737610.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Clay <cl...@emc.com>.
This bug is fixed in CXF-4482!+
--
View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737610.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Christian Müller <ch...@gmail.com>.
I don't have one concrete in mind, but it's not worth to try the lates
version. It also use a newer version of CXF...
Best,
Christian
Am 17.08.2013 00:21 schrieb "Clay" <cl...@emc.com>:
> Is there a fix for this in Camel 2.11.1?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737441.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Christian Müller <ch...@gmail.com>.
And as you may know, camel 2.9.x is not supported any more at Apache Camel.
You have definitely to upgrade to a newer version to get this fixed...
Best,
Christian
Am 17.08.2013 00:21 schrieb "Clay" <cl...@emc.com>:
> Is there a fix for this in Camel 2.11.1?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737441.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Clay <cl...@emc.com>.
Is there a fix for this in Camel 2.11.1?
--
View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737441.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Christian Müller <ch...@gmail.com>.
Can you give Camel 2.11.1 a try?
Best,
Christian
Christian Müller
-----------------
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Aug 16, 2013 at 7:22 PM, Clay <cl...@emc.com> wrote:
> Hi Claus,
>
> We are using:
> - Camel 2.9.2
> - CXF 2.6.3
> - Java 1.6
> - Suse Linux
>
> From the logs, it looks like they are using the Apache Coyote 1.1 connector
> with their Tomcat server.
>
> Clay
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737429.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Clay <cl...@emc.com>.
Hi Claus,
We are using:
- Camel 2.9.2
- CXF 2.6.3
- Java 1.6
- Suse Linux
>From the logs, it looks like they are using the Apache Coyote 1.1 connector
with their Tomcat server.
Clay
--
View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366p5737429.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: MTOM message part not formatted correctly according to RFC 1341
using CRLFLF instead of CRLFCRLF
Posted by Claus Ibsen <cl...@gmail.com>.
What version of Camel and CXF do you use?
And what is your JDK and OS you use?
On Fri, Aug 16, 2013 at 1:08 AM, Clay <cl...@emc.com> wrote:
> A .Net WCF client is throwing a parsing error on the MTOM message returned
> from our Camel endpoint.
>
> Looking at the message sent by Camel in WireShark, we see the header part is
> preceded by ”CRLFLF”, ”--”, ”boundary”, instead of ”CRLF”, ”--”, ”boundary”,
> which is not according to the RFC 1341 specification:
> - http://www.w3.org/Protocols/rfc1341/0_TableOfContents.html
> - http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
>
> Is this a known issue in Apache Camel or is there another explanation?
>
> Thanks,
>
> Clay
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/MTOM-message-part-not-formatted-correctly-according-to-RFC-1341-using-CRLFLF-instead-of-CRLFCRLF-tp5737366.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen