Camel mime-multipart marshal data formatter is not writing the complete body part

Hi We are using blueprint XML for camel route and using mime-multipart:marshal data formatter. On very rare cases, this data formatted is failing to write the comple body. It simply adds few Mime headers and sends the message to next step of the route. I have documented the issue in Stack over flow

Re: Upgrade to Mina 2.0.19 broke camel-xmpp tests

Should have been "properly fix this". Sorry, Pascal Am 19.06.2018 um 19:27 schrieb Pascal Schumacher: Hi everybody, after the recent updated to Mina 2.0.19 four camel-xmpp tests are broken: https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/411/testReport/junit/org.apac

Upgrade to Mina 2.0.19 broke camel-xmpp tests

Hi everybody, after the recent updated to Mina 2.0.19 four camel-xmpp tests are broken: https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/411/testReport/junit/org.apache.camel.component.xmpp/ I can replicated this locally. Reverting commit 2b16d9b1c224e0d4b131f70017cf80

Re: Getting ready for Camel 2.22 Release with SB2 support

Hi, I am done with CAMEL-6840. This will possibly resolve CAMEL-5599. I think lately Willem has had one comment. I think it is addressed already. If you have more, please let me know and we can have it merged soon. Thanks, Önder On Mon, Jun 18, 2018 at 11:02 AM Onder SEZGIN wrote: > Hi, > > I

[GitHub] camel pull request #2386: CAMEL-12588 Fix Improvement

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2386 ---

[GitHub] camel pull request #2386: CAMEL-12588 Fix Improvement

GitHub user gsudharsan opened a pull request: https://github.com/apache/camel/pull/2386 CAMEL-12588 Fix Improvement AggregateProcessor doStop() method changed to call shutdown() instead of shutdownNow() You can merge this pull request into a Git repository by running: $ git

[GitHub] camel pull request #2385: CAMEL-12588 - Improving the fix

Github user gsudharsan closed the pull request at: https://github.com/apache/camel/pull/2385 ---

[GitHub] camel pull request #2385: CAMEL-12588 - Improving the fix

GitHub user gsudharsan opened a pull request: https://github.com/apache/camel/pull/2385 CAMEL-12588 - Improving the fix doStop() method now shuts down the timeoutCheckerExecutorService pool too Improvment - used shutdown instead of shutdownNow You can merge this pull request i

[GitHub] camel pull request #2384: Cleanup TimeOutChecker threads

Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/2384 ---

[GitHub] camel pull request #2384: Cleanup TimeOutChecker threads

GitHub user gsudharsan opened a pull request: https://github.com/apache/camel/pull/2384 Cleanup TimeOutChecker threads When a Aggregator route is stopped, only the AggregateRecoveryChecker threads are stopped and not the AggregateTimeoutChecker threads. They keep lingering around.

R: Re: Teiid Camel component

Not necessary. We can eventually wrap non OSGi-fied dependencies. Inviato da Yahoo Mail su Android Il mar, 19 giu, 2018 alle 12:42, Rafal Korytkowski ha scritto: Hi Claus, Thanks a lot for your guidance! I've got one follow up question. Is it a strict requirement for component's dependen

Re: Teiid Camel component

Hi Claus, Thanks a lot for your guidance! I've got one follow up question. Is it a strict requirement for component's dependencies to be OSGI-fied? On Mon, Jun 18, 2018 at 9:01 AM Claus Ibsen wrote: > Hi Rafal > > Welcome to the Camel community. > It sounds great with a camel-teiid component.