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
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 thus
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
Claus Ibsen-2 wrote:
On Tue, Dec 1, 2009 at 5:04 PM, erh ehas...@transunion.com 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.scheduledpollconsumer(ScheduledPollConsumer
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:
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 transacted mode
erh wrote:
I got rid of *all* JMS options. The DLC queue is seda:errorQ. The
from endpoints are directories (from uri=file:data/input/) (which
causes OverlappingFileLockException and Can not rename file... errors,
but that's probably a different problem).
I tried with and without
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. I looked at the jms page again
Claus Ibsen-2 wrote:
On Mon, Oct 5, 2009 at 9:10 PM, erh ehas...@transunion.com 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 property there either
Claus Ibsen-2 wrote:
On Mon, Oct 5, 2009 at 7:32 PM, erh ehas...@transunion.com 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 from
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 bit odd.
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:
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:
el${in.body.replaceAll('id','orderId')}/el
However, when I try to use something like
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
deferred
14 matches
Mail list logo
