Hi
Have you tried with 2.0? Would be interresting to know if this issue
exists in 2.0 as well?
On Thu, Apr 9, 2009 at 6:21 AM, Manish K Bafna
wrote:
> I guess there was an issue with Camel 1.5.
> When starting the context, the routes are added in the list.
> This route list is not cleared durin
Hi Manish,
Please feel free to create a JIRA[1] ticket for it.
I just went through the code and can confirm your finding.
BTW there are some changes in the Camel 2.0 about starting and stoping
the RouteDefinintions. Not sure if it is resolved by Camel 2.0.
[1]https://issues.apache.org/activemq/b
Hi
Camel will convert whatever your expression returns to something that
it iterates.
For non streams it will walk the list before they are processed, so it
will know the total size.
If you have a very large document you can use streaming to split it on-the-fly.
However then the total size is not
Hi Jens
Thanks for reporting this. I have looked into it.
Yes the seda is async by nature and should not spin off a copy of the
exchange that shares the same unit of work as the original.
I have a fix at hand and will commit it later today.
BTW The same issue applies for the wire tap. It should
On Thu, Apr 9, 2009 at 11:07 AM, Claus Ibsen wrote:
> Hi Jens
>
> Thanks for reporting this. I have looked into it.
>
> Yes the seda is async by nature and should not spin off a copy of the
> exchange that shares the same unit of work as the original.
> I have a fix at hand and will commit it late
Clause,
This is what my route looks like
from("file:C:/work/esb/filetestpoller/")//large file
exceeding 800M
.convertBodyTo(InputStream.class)
.splitter(customsplitter)//custom splitter(injected by spring)
that
returns a java.util.Collection
java.util.Scanner is good for splitting big files.
In fact I think that is what the .streaming() is for.
But returning an iterator should be fine as well. Can you show the error?
Maybe there is a bug we can fix.
On Thu, Apr 9, 2009 at 3:52 PM, javadevel wrote:
>
> Clause,
>
> This is what my ro
Hello All,
My router is becoming blocked by sending messages to a queue on which no one
is taking messages from the queue, when the queue becomes full, the router
is blocked waiting for more space in the queue to become free, any ideas
about how I could get around this? In my application it is po