[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393289#comment-16393289 ] Claus Ibsen commented on CAMEL-11370: - I dont think anyone going to work on this that hybrid stuff is added in 2010 > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.21.0 > > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393220#comment-16393220 ] Sascha Dirbach commented on CAMEL-11370: [~davsclaus] my comment was only related to the memory consumption. I suspect that the original issue still persists... > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.21.0 > > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393087#comment-16393087 ] Claus Ibsen commented on CAMEL-11370: - Thanks Sascha for your feedback. > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > Fix For: 2.21.0 > > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392033#comment-16392033 ] Sascha Dirbach commented on CAMEL-11370: [~Peter Keller] I had a look into your reproducer. The problem with the high memory consumption is not related to MTOM, but to the involved marshalling. MTOM is just relevant when it comes to sending the data over the wire. When you marshal the object to XML, internally a DOM tree will be created with the actual data from the DataHandler and not only with a reference. I analyzed some heap dumps while processing and found quite large DefaultExchange (70m) and (cxf) Message (>100m) objects. I changed your sample project to: * Use POJO (default) instead of PAYLOAD dataFormat * Set the mtom-enabled message property (required for POJO dataFormat) * Remove the unmarshalling and marshalling By these changes the memory consumption stays below 100m at any time (not including the startup of the application). You can find the required changes here: https://github.com/peterkeller/camel-cxf-memory/pull/1/files > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358539#comment-16358539 ] Peter Keller commented on CAMEL-11370: -- I tried v2.20.2 with the same effect. I implemented a small sample project which can be found on https://github.com/peterkeller/camel-cxf-memory.git > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348206#comment-16348206 ] Claus Ibsen commented on CAMEL-11370: - Try with newer version. Also if you can build a small sample project / unit test that reproduces the issue will help. And then there is also commercial support http://camel.apache.org/commercial-camel-offerings.html > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346464#comment-16346464 ] Peter Keller commented on CAMEL-11370: -- Requesting a SOAP response of about 50 MB with JAXB/MTOM results in an excessive memory heap usage (> 500 MB) which is not acceptable (Camel v2.19.2). It would be highly appreciated if anyone could fix this. > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > Attachments: MTOM-conversion.patch, > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125522#comment-16125522 ] Joerg Kessler commented on CAMEL-11370: --- I did some further analysis. I am at the moment only referring to Camel 2.17.4 and CXF 3.1.9. I changed CXF so that it also accepts HybridSourceDataBinding and not just JAXBDataBinding (patch attached). I extended HybridSourceDataBinding so that createWriter() so that it also returns a writer for OutputStream (same as JAXBDataBinding). The only problem left is that the MTOM conversion seems to only work for DOMs So I added in DefaultCxfBinding a payload conversion to Document. I have added a patch for Camel-CXF. I also added a test that checks whether the incoming message contains an attachment. Without the modifications the test fails. Existing tests in Camel-CXF add this attachment as part of the test. But the problem is that HybridSourceDataBinding affects the MTOM conversion and therefore the complete processing must be tested. All existing tests are executed sucessfully with the above modifications. All in all it seems that the intrduction of HybridSourceDataBinding destroyed the ability to convert to MTOM format. What I implemented here is only a kind of repair. I am not sure whether this will have no side effects. My knowledge on this complex topic of payload conversion is rather limited. If you agree to this modification I can provide 'real' patches for the actual releases. > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > Attachments: > accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, > MTOM-conversion.patch, mtom.test.zip > > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031058#comment-16031058 ] Joerg Kessler commented on CAMEL-11370: --- Please have a look at the ticket I posted on CXF. It contains a unit test that fails. I did some analysis and proposed a solution. But the solution leads to the next problem when I implemented it. It seems that the this Hybrid Data Binding class that is set by Camel CXF completely prevents the usage of MTOM. > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Reporter: Joerg Kessler >Priority: Minor > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF
[ https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031030#comment-16031030 ] Claus Ibsen commented on CAMEL-11370: - What version of Camel do you use? > Problem with MTOM in Camel-CXF > -- > > Key: CAMEL-11370 > URL: https://issues.apache.org/jira/browse/CAMEL-11370 > Project: Camel > Issue Type: Bug >Reporter: Joerg Kessler > > I originally opened the issue on CXF: > https://issues.apache.org/jira/browse/CXF-7388 > but ther CXF guys think the problem is in camel-cxf. Please have a look at > this ticket. Basically the MTOM conversion seems not to work anymore when > using CXF in Camel. I provided a unit test that demonstrates the observed > behaviour. -- This message was sent by Atlassian JIRA (v6.3.15#6346)