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 during stop.
So when the next time, the same context is started again, the routes gets added
to the list again thereby duplication.
I solved the issue by clea
I need to use a splitter expression to split a very large document with
rather complex splitting requirement. Based on the documentation provided on
the Apache Camel Splitter, I can a Bean or implement the Expression
interface and return java.util.Collection or java.util.Iterator. However,
it onl
Hi
I would suggest to use the JDK concurrency stuff for spawning threads.
See for instance the SedaConsumer
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/component/seda/SedaConsumer.java
On Wed, Apr 8, 2009 at 4:53 PM, wrote:
> I think you should "kill
Hi
Yeah I have tracked it down to a potential buffer stream not being
closed, that is used by the JMS consumer.
Converting the file content to String based beforehand should fix it
as Ade suggested.
However the bugfix is committed to 1.6.1 and 2.0 so hopefully it
should work out of the box in the
Hi Bruno, Marek,
Yeah, I encountered someting similar with Camel 1.5.4.0-fuse on
Windows: if you convertBodyTo(String.class) after the from("file:...")
then it should be ok.
/Ade
On 8 Apr 2009, at 15:50, bruno.bor...@gmail.com wrote:
Have you tried to put a direct:endpoint in the middle, b
I think you should "kill" your threads on method doStop() or stop() of your
consumer.
They are invoked when CamelContext is stopped.
Cheers,
Bruno Borges
On Apr 8, 2009 12:38am, Manish K Bafna wrote:
The same is visible in JMS component too.
Steps:
1. Create a route from JMS topic1 to
Have you tried to put a direct:endpoint in the middle, between file:* and
jms:* ?
Before routing to direct:, convert body to String. Then you route
from("direct:endpoint").to("jms:queue")
Maybe this works.
Cheers,
Bruno Borges
On Apr 8, 2009 11:39am, Marek2009 wrote:
Hello,
I have
Hey Claus!
Yes - I've seen it. This is the flag that allows you to do something I
already described - it allows you to turn transactions off for in-out
"jms:splited" so you are able to actually send anything. Without this option
it doesn't work at all. With this option requests are not transaction
Hello,
I have encountered an issue when combining file poller and JMS queue in one
route. If the poller is set to "noop=no" and tries to either delete or move
the files, it fails every now and then (say, every 5th to 10th file). For
instance, with "noop=no&delete=yes" on a Windows machine the exc
Hi,
I ran into a problem with a route that called a seda endpoint. For some
reason the unit of work within the seda route was completed before the
actual route processing finished. Here's a simplified test case:
public class SedaUnitOfWorkTest {
private String lastOne;
@Test
pub
Hi
Just a quick reply.
There is a trasactedInOut URI option for the JMS component. Have you
looked at it?
On Tue, Apr 7, 2009 at 6:29 PM, Roman Kalukiewicz
wrote:
> Hello Camel Riders!
>
> Let me show an example of a problem I'm working on:
>
> from("jms:in-queue").split(xpath("/foos/*"),
> my
11 matches
Mail list logo
