On Thu, Jan 24, 2013 at 8:13 AM, Thibault Cassan <thibault.cas...@gmail.com> wrote: > Christian, > > I am using Oracle's JDK. >
And have you tried restarting the Karaf container after installing all these features. Sometimes this can fix weird issues. > Regards, > Thibault > 2013/1/24 Christian Müller <christian.muel...@gmail.com> > >> Which JDK do you use (Oracle, IBM, OpenJDK, ...)? >> >> Best, >> Christian >> >> Sent from a mobile device >> Am 24.01.2013 07:37 schrieb "Thibault Cassan" <thibault.cas...@gmail.com>: >> >> > Hi all, >> > >> > I am using Camel 2.10.2 on Karaf 2.2.9 (JDK 1.7.0_09 or 1.6.0_37, I tried >> > with both), and i am facing a curious behavior. >> > Here is how to reproduce it, from a fresh downloaded Apache Karaf 2.2.9: >> > - Start karaf >> > - Add some features URL: 'features:addurl >> > mvn:org.apache.camel.karaf/apache-camel/2.10.2/xml/features >> > mvn:org.apache.activemq/activemq-karaf/5.7.0/xml/features' >> > - Add some features: 'features:install activemq activemq-spring camel >> > camel-jms camel-mail camel-cxf camel-jaxb camel-mina camel-jmx >> camel-saxon >> > activemq-camel' >> > - Create adefault Broker: 'activemq:create-broker' >> > >> > Until this point, everything seems to work fine. Now let's create a route >> > involving the mail component: >> > <beans xmlns="http://www.springframework.org/schema/beans"; >> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> > xsi:schemaLocation=" >> > http://www.springframework.org/schema/beans >> > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd >> > http://camel.apache.org/schema/spring >> > http://camel.apache.org/schema/spring/camel-spring.xsd >> > "> >> > <camelContext id="test.mail" xmlns=" >> > http://camel.apache.org/schema/spring";> >> > >> > <route id="test.inbound.mail"> >> > <from uri="imap:// >> > b...@example.com?host=localhost&password=test"/> >> > <log message="Read ok"/> >> > </route> >> > >> > </camelContext> >> > </beans> >> > >> > I write this in a XML file, a copy it in the deploy directory of Karaf. >> The >> > route seems ok. >> > >> > Now, the problem. If I stop Karaf (using logout from the karaf command >> > prompt), and restart it, I am facing a new exception: >> > 2013-01-24 07:30:18,861 | WARN | /b...@example.com | >> > MailConsumer | 255 - org.apache.camel.camel-core - >> > 2.10.2 | Consumer Consumer[imap://b...@example.com?host=localh >> > ost&password=******] failed polling endpoint: Endpoint[imap:// >> > b...@example.com?host=localhost&password=******]. Will try again at next >> > poll. Caused by: [javax.mail.NoSuchProviderExceptio >> > n - imap] >> > javax.mail.NoSuchProviderException: imap >> > at >> > javax.mail.Session.getService(Session.java:798)[130:javax.mail:1.4.4] >> > at >> > javax.mail.Session.getStore(Session.java:578)[130:javax.mail:1.4.4] >> > at >> > javax.mail.Session.getStore(Session.java:540)[130:javax.mail:1.4.4] >> > at >> > javax.mail.Session.getStore(Session.java:519)[130:javax.mail:1.4.4] >> > at >> > >> > >> org.apache.camel.component.mail.MailConsumer.ensureIsConnected(MailConsumer.java:375)[262:org.apache.camel.camel-mail:2.10.2] >> > at >> > >> > >> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:82)[262:org.apache.camel.camel-mail:2.10.2] >> > at >> > >> > >> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:142)[255:org.apache.camel.camel-core:2.10.2] >> > at >> > >> > >> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:92)[255:org.apache.camel.camel-core:2.10.2] >> > at >> > >> > >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)[:1.6.0_37] >> > at >> > >> > >> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)[:1.6.0_37] >> > at >> > >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)[:1.6.0_37] >> > at >> > >> > >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)[:1.6.0_37] >> > at >> > >> > >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)[:1.6.0_37] >> > at >> > >> > >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)[:1.6.0_37] >> > at >> > >> > >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_37] >> > at >> > >> > >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_37] >> > at java.lang.Thread.run(Thread.java:662)[:1.6.0_37] >> > >> > This one is more curious. I made a search with my friend Google, but >> wasn't >> > able to find a way to make it work correctly. Does anyone have already >> > faced this and have an idea how to configure it ? >> > >> > Best regards, >> > Thibault Cassan >> > >> -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
