On Thu, Oct 8, 2009 at 9:11 AM, parasmk para...@gmail.com wrote:
Thank you very much! I'll try this and update the thread with my findings.
I created a FAQ about it
http://cwiki.apache.org/confluence/display/CAMEL/How+do+I+handle+failures+when+consumimg+for+example+from+a+FTP+server
Please
On Thu, Oct 8, 2009 at 9:44 AM, Charles Moulliard cmoulli...@gmail.com wrote:
Forget my post. The maximum redeliveries was not setted to ZERO but 1.
Great that you found the issue. And glad it seems to work. As we do
got a ton of testing in this area so I was a bit surprised if there
was an
Hi
On Thu, Oct 8, 2009 at 8:54 AM, _Jens jens.riemschnei...@icw.de wrote:
Hi,
I just checked out the new example for the JMX management in Camel 2.1. When
I run the example and browse the MBeans with JConsole, I can see all the
processors of the route being instrumented. I then added a
I was also very surprised myself. This is a good idea to have modular
architecture where the application is deployed as separate bundles but
when you have to redeploy or update part of a project, sometimes you
forget to check / verify this kind of configuration defined in a xml
file embedded in a
On Thu, Oct 8, 2009 at 9:57 AM, _Jens jens.riemschnei...@icw.de wrote:
Just debugged this a bit and it seems that processors have to implement
Service to be instrumented. The processor for setHeader only implements
Processor, whereas TransformProcessor extends ServiceSupport.
Ah well
Hi Claus,
I simply changed the last route of the example:
route errorHandlerRef=dlc
from uri=activemq:queue:stock/
delayconstant100/constant/delay
bean ref=stock method=transform/
setHeader headerName=foo
Yes, this is true. In theory it is possible to use some custom expression
that does significant work, but most setHeader steps are probably very
light-weight.
However, this means that a custom processor used with process() needs to
implement Service if I want to simply have some performance
I knew you were going to say that :) I will!
Claus Ibsen-2 wrote:
On Mon, Oct 5, 2009 at 5:01 PM, jpcook jonathan.c...@erars.plus.com
wrote:
Hi,
I was also wondering why you can't specify that you want all the entries
sorted? It appears that sortEntries only works when splitEntries is
Hi
Why do you have mixed message on that JMS queue?
Can you not have 1 queue for XML files
And another queue for CSV files?
If not I suggest to use 3 routes
1st route will consume from that JMS queue and check the message
content if its XML or CSV.
And then route to either A or B depending on
Hi
I have backed out on add all processors as its too much work and
brings little value.
A processor must implement Service to be managementable.
And those we would like to be managed such as the bigger EIPs do this already.
On Thu, Oct 8, 2009 at 10:21 AM, Claus Ibsen claus.ib...@gmail.com
my incoming queue, receives messages of bytes type.
the message content in bytes may be an XML or CSV or PDF file that I
converted a file in the end.
In the header of the message,there's on properties(Action), that allows me
to place this file to the proper directory.
From where I
On Thu, Oct 8, 2009 at 11:22 AM, titexe abdellatifbouch...@eurofins.com wrote:
my incoming queue, receives messages of bytes type.
the message content in bytes may be an XML or CSV or PDF file that I
converted a file in the end.
In the header of the message,there's on properties(Action),
Thank you for your reply,
now I get no errors for CSV files.
cons by my filter does not work with the simple language, it puts all files
received in the same directory
to uri=file:///c:/CAMEL/IN/AAE/
below my configuration:
route errorHandlerRef=myDeadLetterChannel
from
Hi
Is there a Action header at all?
You can use the tracer to look?
http://camel.apache.org/tracer
I suspect this is the problem.
On Thu, Oct 8, 2009 at 12:49 PM, titexe abdellatifbouch...@eurofins.com wrote:
Thank you for your reply,
now I get no errors for CSV files.
cons by my filter
Hi
I created an unit test that simulates your problem.
I works for me
http://svn.apache.org/viewvc?rev=823137view=rev
On Thu, Oct 8, 2009 at 1:52 PM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
Is there a Action header at all?
You can use the tracer to look?
Is really a big problem, there's no place for logic:)
I enabled the trace mode, the Action field is in the header of the message,
I tried another solution, by changing the file name by adding at the end
${header.Action}
The result: I get all the files in the directory c:/CAMEL/IN/AAE with a
sorry the other configuration is deformed, here is the setup I used
to remember (camel version : 1.6.1, jvm version: 1.6,activemq :
fuse message broker 5.3.0.3 )
and my config camel in activemq.xml
route errorHandlerRef=myDeadLetterChannel
from uri=activemq:queue:AX.IN/
On Thu, Oct 8, 2009 at 9:48 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Wed, Oct 7, 2009 at 7:37 PM, erh ehas...@transunion.com wrote:
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
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 or not using transacted=true |
Hi
I'm observing quite a strange behavior at the moment. In my app, I have
several routes which all start by reading files in the same directory,
deleting them after processing. Obviously, each rule uses its own include
pattern to process separate subset of files.
Now, the problem is that if
Hi
Always state which version of Camel you are using.
And post how you route is configured.
On Thu, Oct 8, 2009 at 4:57 PM, Vladimir Okhotnikov
vokhotni...@gmail.com wrote:
Hi
I'm observing quite a strange behavior at the moment. In my app, I have
several routes which all start by reading
On Thu, Oct 8, 2009 at 5:51 PM, erh ehas...@transunion.com wrote:
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
Hello,
My route is simple, I have a incoming queue (IN), All messages received in
this queue is routed to XML Queue or CSV Queue according to the following
condition:
If the Action field located in the header of the message as field properties
(Message Properties) is equal to XML or CSV
This
Hi
The simple language does NOT support operators in Camel 1.x.
This feature requires to use Camel 2.0.
You have to use something else such as mvel, ognl, groovy or a regular
bean for the testing.
Or upgrade to Camel 2.0 and use Simple.
On Thu, Oct 8, 2009 at 6:41 PM, titexe
Sorry,
Camel 2.0 release
3 routes like:
file:///home/javadev/workspace/camelroutes/testdir/testdata/testimport?delete=trueinclude=%5E.%2Bmapping_warnings%5C.txt%24readLock=rename
the only difference between all 3 is the include pattern.
Claus Ibsen-2 wrote:
Hi
Always state which version
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
On Fri, Oct 9, 2009 at 12:41 AM, erh ehas...@transunion.com wrote:
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
29 matches
Mail list logo
