|
From: Morin F. <fm...@ax...> - 2004-12-16 07:10:35
|
I updated javamail to the last version (1.3.2) but I always had the same problem... I'll try your suggestion to see what happen. Thanks. -----Message d'origine----- De : ebx...@li... [mailto:ebx...@li...]De la part de Ronald van Kuijk Envoye : mercredi 15 decembre 2004 17:57 A : ebx...@li... Objet : RE: [ebxmlms-general] "Missing start boundary" exception when processing lot of message I've seen this in three circumstances (not in hermes, but with jaxm) - once in a system under load where there was a threadsafety issue and one receiver started reading data after the headers were already read. - once where there was a wrong mail.jar which produced wrong headers, but that happened all the time, not specifically under load - an text/xml response was produced, but not multipart mime as expected. Otherwise I have no idea where it could come from. Can you turn on some low level debugging on http level? Ronald =20 > -----Oorspronkelijk bericht----- > Van: ebx...@li...=20 > [mailto:ebx...@li...] Namens=20 > Morin Fabrice > Verzonden: woensdag 15 december 2004 17:23 > Aan: ebx...@li... > Onderwerp: [ebxmlms-general] "Missing start boundary"=20 > exception when processing lot of message >=20 > Hi guys, >=20 > Here is a strange problem... An exception "Missing start=20 > boundary" always occurs in tomcat log (catalina.out) when=20 > Hermes process a lot of messages. >=20 > Let me explain the architecture : >=20 > I use 6 machines. 5 of them send messages to the last one.=20 > All messages sent from a same machine share the same cpaID=20 > and the same conversationID. So I have 5 different cpaID and=20 > 5 different conversationID. Service and action are the same=20 > for all messages on all machines. On the last machine, I use=20 > 5 contexts to get those messages. >=20 > To send messages, I use a little tool based on the monitor. > To receive message, I use another tool which polls every 30s=20 > the 5 contexts corresponding to the sender's context. >=20 > Each machine sends 100 messages to the last one (those=20 > messages are signed and sent reliably via HTTPS). I can send=20 > between 3 or 5 messages in a second. There are 2 ASCII=20 > payloads for each message, their sizes are between 1kb and 7kb). >=20 > After a few seconds, I get this error in the receiver tomcat log : >=20 > javax.mail.MessagingException: Missing start boundary > at=20 > javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284) > at=20 > javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:171) > at=20 > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl > .java:118) > at=20 > com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessa > ge(MessageFactoryImpl.java:32) > at=20 > hk.hku.cecid.phoenix.message.handler.MessageServiceHandler.pro > cessMessage(Unknown Source) > at=20 > hk.hku.cecid.phoenix.message.handler.MessageServiceHandler.doP > ost(Unknown Source) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at=20 > org.apache.catalina.core.ApplicationFilterChain.internalDoFilt > er(ApplicationFilterChain.java:237) > at=20 > org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli > cationFilterChain.java:157) > at=20 > org.apache.catalina.core.StandardWrapperValve.invoke(StandardW > rapperValve.java:214) > at=20 > org.apache.catalina.core.StandardContextValve.invoke(StandardC > ontextValve.java:178) > at=20 > org.apache.catalina.core.StandardHostValve.invoke(StandardHost > Valve.java:126) > at=20 > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport > Valve.java:105) > at=20 > org.apache.catalina.core.StandardEngineValve.invoke(StandardEn > gineValve.java:107) > at=20 > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdap > ter.java:148) > at=20 > org.apache.coyote.http11.Http11Processor.process(Http11Process > or.java:825) > at=20 > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandle > r.processConnection(Http11Protocol.java:731) > at=20 > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolT > cpEndpoint.java:526) > at=20 > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(Le > aderFollowerWorkerThread.java:80) > at=20 > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:534)=20 >=20 > Of course everything works fine if I send less messages, more=20 > slowly... >=20 > Has anybody already had this kind of error ? >=20 >=20 > Regards, >=20 > Fabrice. >=20 >=20 > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide Read honest &=20 > candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now.=20 > http://productguide.itmanagersjournal.com/ > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general >=20 |