Claus Ibsen-2 wrote:
>
> Yeah in Camel 2.1 you now have full control of these situations where
> you can dictate the order
> http://camel.apache.org/configuring-route-startup-ordering-and-autostartup.html
>
> And all the routes are pre started, before at the end the consumers is
> started and t
I'm having trouble with what seems to be a race condition during Camel
startup, which is causing "No getConsumers() available on Producer" errors
to happen:
[2009-12-10
05:05:03,026][WARN][DefaultMessageListenerContainer-1][component.direct.DirectProducer(DirectProducer)-process(44)]:
No getConsu
--
View this message in context:
http://old.nabble.com/Getting-%22No-getConsumers%28%29-available-on-Producer-tp26731552p26731552.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Claus Ibsen-2 wrote:
>
> And you are sure your bean does not throw a NPE exception?
>
> But yeah without a stacktrace or any more detailed logging its hard to
> work out.
>
I actually got a stack trace this time:
[2009-12-04 01:46:53,105][WARN][Thread: 1
org.apache.camel.component.file.filec
Claus Ibsen-2 wrote:
>
> On Tue, Dec 1, 2009 at 5:04 PM, erh wrote:
>>
>> I'm getting errors like this in my application:
>>
>> [2009-12-01 05:53:21,813][WARN][Thread: 2
>> org.apache.camel.component.file.filecompon...@62681b][camel.impl.scheduledp
I'm getting errors like this in my application:
[2009-12-01 05:53:21,813][WARN][Thread: 2
org.apache.camel.component.file.filecompon...@62681b][camel.impl.scheduledpollconsumer(ScheduledPollConsumer)-run(68)]:
An exception occured while polling:
Endpoint[file:data/input?consumer.recursive=false&l
erh wrote:
>
> Well, I guess I actually *didn't* try w/o transferExchange param present
> at all before. oops. If I remove that, things work ok, at least with a
> seda queue. I'm trying it with an activemq queue now.
>
yep, it works fine with an activemq too.
erh wrote:
>
> I got rid of *all* JMS options. The DLC queue is "seda:errorQ". The
> "from" endpoints are directories () (which
> causes OverlappingFileLockException and "Can not rename file..." errors,
> but that's probably a different pro
Claus Ibsen-2 wrote:
>
> Hi
>
> Can you try without using JMS as the DLC queue. For example a seda
> endpoint instead.
> To ensure that this works.
>
> Also try without transferExchange=true|false as well.
>
> And it can also matter whether your JMS component have been configured
> in transac
Claus Ibsen-2 wrote:
>
> Thanks I can see its the new OSGi blueprint support that causes some
> maven issues.
> Will disable this until blueprint works completely.
>
Well, the build worked, but some tests failed, and I guess that means the
tarball didn't get over to repository.apache.org. :(
Claus Ibsen-2 wrote:
>
> On Mon, Oct 5, 2009 at 7:32 PM, erh wrote:
>> Do the snapshots get built automatically? The dates on the files in the
>> 1.6.2-SNAPSHOT directory are a bit odd. The md5 and sha1 files have a
>> timestamp from October 4th, but the tarballs are
Claus Ibsen-2 wrote:
>
> On Mon, Oct 5, 2009 at 9:10 PM, erh wrote:
>> huh? I'm looking at the javadocs for 2.0
>> (http://camel.apache.org/maven/camel-core/apidocs/org/apache/camel/builder/DeadLetterChannelBuilder.html)
>> and I don't see a deadLetterUri
I'm having trouble getting the dead letter channel to actually deliver to a
dead letter queue. It retries correctly, but after all the retries all I
get that refers to the final queue is a log message saying "Handled by the
failure processor:
RecipientList[activemq:queue:bulk_ErrorQ?transferExcha
Claus Ibsen-2 wrote:
>
> You are using Camel 1.x which have some properties which are not the
> same as 2.0.
>
> If you use a good IDE you get code completion in the XML editor and
> thus can see which properties you can use.
>
> I recall its called: defaultDeadLetterEndpointUri in Camel 1.x i
Claus Ibsen-2 wrote:
>
> Hi
>
> I have just backported a fix for CAMEL-1878 to 1.x as well.
> You are welcome to try with a new 1.6.2-SNAPSHOT whether it fixes your
> bean problem.
>
>
Do the snapshots get built automatically? The dates on the files in the
1.6.2-SNAPSHOT directory are a bi
Claus Ibsen-2 wrote:
>
> Hi
>
> I have just backported a fix for CAMEL-1878 to 1.x as well.
> You are welcome to try with a new 1.6.2-SNAPSHOT whether it fixes your
> bean problem.
>
>
Thanks! I'll give it a shot.
eric
--
View this message in context:
http://www.nabble.com/using-methodN
I'm having trouble getting the methodName to work when routing to a bean
using a route like this:
foo is a bean that implements Processor [*2], and in some routes I want it
to use the process() method, but in this case I need to use a different
entry point. According to http://camel.a
Claus Ibsen-2 wrote:
>
> Hi
>
> I have fixed the sample page and removed the replaceAll.
>
>
oh, ok. I guess that'll be a little better.
I figured out a bit more about being able to call methods. Apparently the
"MethodExpression" in the unified EL is meant to be used by JSF to define a
de
Claus Ibsen-2 wrote:
>
> On Mon, Aug 31, 2009 at 8:28 PM, erh wrote:
>>
>> I'm trying to use the JSP EL according to the example listed on
>> http://camel.apache.org/el.html
>> It claims that you can call arbitrary functions with camel's version of
&g
I'm trying to use the JSP EL according to the example listed on
http://camel.apache.org/el.html
It claims that you can call arbitrary functions with camel's version of the
EL, with the example shown being:
${in.body.replaceAll('id','orderId')}
However, when I try to use something like that, I
20 matches
Mail list logo
