Hello, problem is solved. It was due to an incompatibility between servicemix and camel from trunk. Not same release of camel in servicemix. Recompiling servicemix with Camel trunk solves the issue.
As a result pop3s works fine. It's just necessary to convert pop3s message in XML and DomSource before injecting it into ServiceMix. Thank for your help Christophe James.Strachan wrote: > > What code are you running? It looks like the error is caused trying to > turn a non-XML document into XML > > On 01/12/2007, xtof <[EMAIL PROTECTED]> wrote: >> >> Thank for the pop3s, it's better >> In can retreive the mail but I've got now the following error. Any idea? >> Thank >> Christophe >> >> DEBUG - ScheduledPollConsumer - Starting to poll >> DEBUG - ScheduledPollConsumer - Starting to poll >> [Fatal Error] :1:1: Content is not allowed in prolog. >> ERROR - DeadLetterChannel - On delivery attempt: 0 caught: >> org.apache.camel.RuntimeCamelException: org.xml. >> sax.SAXParseException: Content is not allowed in prolog. >> org.apache.camel.RuntimeCamelException: org.xml.sax.SAXParseException: >> Content is not allowed in prolog. >> at >> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:291) >> at >> org.apache.camel.impl.converter.InstanceMethodTypeConverter.convertTo(InstanceMethodTypeConverter.java:51) >> at >> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(DefaultTypeConverter.java:64) >> at >> org.apache.camel.builder.ExpressionBuilder$16.evaluate(ExpressionBuilder.java:339) >> at >> org.apache.camel.builder.ValueBuilder.evaluate(ValueBuilder.java:36) >> at >> org.apache.camel.builder.ProcessorBuilder$1.process(ProcessorBuilder.java:42) >> at >> org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsynProcessorBridge.process(AsyncProce >> ssorTypeConverter.java:44) >> at >> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:136) >> at >> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:86) >> at org.apache.camel.processor.Pipeline.process(Pipeline.java:103) >> at org.apache.camel.processor.Pipeline.process(Pipeline.java:87) >> at >> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:40) >> at >> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:44) >> at >> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:68) >> at >> org.apache.camel.component.mail.MailConsumer.processMessage(MailConsumer.java:108) >> at >> org.apache.camel.component.mail.MailConsumer.messagesAdded(MailConsumer.java:67) >> at >> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:97) >> at >> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:63) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) >> at >> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) >> at >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.j >> ava:65) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor. >> java:142) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166 >> ) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) >> at java.lang.Thread.run(Thread.java:595) >> Caused by: org.xml.sax.SAXParseException: Content is not allowed in >> prolog. >> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) >> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown >> Source) >> at >> org.apache.camel.converter.jaxp.XmlConverter.toDOMSourceFromStream(XmlConverter.java:355) >> at >> org.apache.camel.converter.jaxp.XmlConverter.toDOMSource(XmlConverter.java:206) >> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:585) >> at >> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:287) >> ... 26 more >> DEBUG - DeadLetterChannel - Sleeping for: 1000 until >> attempting >> redelivery >> [Fatal Error] :1:1: Content is not allowed in prolog. >> >> >> >> James.Strachan wrote: >> > >> > On 29/11/2007, Jason Anderson <[EMAIL PROTECTED]> wrote: >> >> from the stack trace it looks like its just a simple connection >> >> refused while trying to connect to the pop3 server, try to telnet >> >> pop.mail.yahoo.fr 995 from the commandline to see if you have a >> >> firewall or something similar blocking the connection >> >> >> >> SSL support in the would be a matter of getting camel to recognize a >> >> pop3s uri if it doesnt already and making sure the protocol is set to >> >> pop3s in the endpoints mail configuration rather than pop3 >> > >> > I've just added native support for pop3s to trunk; so using pop3s in a >> > URI should just work >> > >> > -- >> > James >> > ------- >> > http://macstrac.blogspot.com/ >> > >> > Open Source Integration >> > http://open.iona.com >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/mail-pop3-and-ssl---how-to-do--tf4896801s22882.html#a14105936 >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/mail-pop3-and-ssl---how-to-do--tp14024595s22882p14238021.html Sent from the Camel - Users mailing list archive at Nabble.com.
