3356078 - JMS sender adapter fails to process message due to "Missing start boundary" error in Cloud Integration

JMS receiver adapter sends message into JMS queue. When a JMS sender adapter tries to process it from JMS queue, below error happens:

javax.mail.internet.ParseException: Missing start boundary

at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:691)

at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:350)

at org.apache.camel.dataformat.mime.multipart.MimeMultipartDataFormat.unmarshal(MimeMultipartDataFormat.java:247)

at org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)

at org.apache.camel.component.dataformat.DataFormatEndpoint$1.process(DataFormatEndpoint.java:91)

at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:110)

at com.sap.it.op.agent.collector.camel.MplInterceptor$MplAsyncProcessor.process(MplInterceptor.java:289)

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:110)

at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)

at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:203)

at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)

at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)

at org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:203)

at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)

at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:212)

at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:736)

at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:696)

at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:674)

at com.sap.esb.monitoring.mpl.access.jms.MessageListenerContainer.doExecuteListener(MessageListenerContainer.java:56)

at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:331)

at com.sap.esb.monitoring.mpl.access.jms.MessageListenerContainer.doReceiveAndExecute(MessageListenerContainer.java:76)

at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:270)

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1237)

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1127)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:838)

SAP BTP Neo, SAP BTP Cloud Foundry

JMS, receiver adapter, mismatch, content-type header, content-type, header, boundary, Missing start boundary, javax.mail.internet.ParseException, ParseException, , KBA , LOD-HCI-PI-CON-SOAP , SOAP Adapter , Problem