[ebxmlms-general] "Missing start boundary" exception when processing lot of message

[Morin F. <fm...@ax...>]

Hi guys,

Here is a strange problem... An exception "Missing start boundary" =
always occurs in tomcat log (catalina.out) when Hermes process a lot of =
messages.

Let me explain the architecture :

I use 6 machines. 5 of them send messages to the last one. All messages =
sent from a same machine share the same cpaID and the same =
conversationID. So I have 5 different cpaID and 5 different =
conversationID. Service and action are the same for all messages on all =
machines. On the last machine, I use 5 contexts to get those messages.

To send messages, I use a little tool based on the monitor.
To receive message, I use another tool which polls every 30s the 5 =
contexts corresponding to the sender's context.

Each machine sends 100 messages to the last one (those messages are =
signed and sent reliably via HTTPS). I can send between 3 or 5 messages =
in a second. There are 2 ASCII payloads for each message, their sizes =
are between 1kb and 7kb).

After a few seconds, I get this error in the receiver tomcat log :

javax.mail.MessagingException: Missing start boundary
	at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
	at =
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:171)
	at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:118)
	at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)
	at =
hk.hku.cecid.phoenix.message.handler.MessageServiceHandler.processMessage=
(Unknown Source)
	at =
hk.hku.cecid.phoenix.message.handler.MessageServiceHandler.doPost(Unknown=
 Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at =
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat=
ionFilterChain.java:237)
	at =
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte=
rChain.java:157)
	at =
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve=
.java:214)
	at =
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve=
.java:178)
	at =
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:=
126)
	at =
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:=
105)
	at =
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.j=
ava:107)
	at =
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:14=
8)
	at =
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825=
)
	at =
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processCo=
nnection(Http11Protocol.java:731)
	at =
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.=
java:526)
	at =
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowe=
rWorkerThread.java:80)
	at =
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.=
java:684)
	at java.lang.Thread.run(Thread.java:534)=20

Of course everything works fine if I send less messages, more slowly...

Has anybody already had this kind of error ?


Regards,

Fabrice.