fuse ESB choking on camel routes...

[e0richt]

hi,

i have components defined in osgi for activemq, processor, output1, output2...

I have defined 20 camel routes similar to the following:

.from("activemq:topic:topic1")

    .to("myBean")

    .failover(...)

          .to("output1:queue:queue1", "output2:queue:queue2");

activemq, output1 and output2 are activemq endpoints that are external to the ESB

myBean is used to parse the xml message and add properties based on certain fields in the message.

The only difference in the route definition is with the topic name goes from 1-20...

.from("activemq:topic:topic1")....

.from("activemq:topic:topic2")....

.from("activemq:topic:topic3")... etc...

I also have a separate route in a different context that takes messages off of output1 and output2 in order to "drain" the messages off the routes...

the ESB will "choke" due to lack of java heap space after about 200 meg bytes worth of messages have been processed...

possibilities:

    - a way to handle / prevent this condition from happening

    - a way to improve the route performance

any ideas?

[davsclaus]

Try without your custom bean, so the messages is passed straight through. It could be that your parsing logic have memory leaks etc.

[e0richt]

well, I havent done that but I have changed the output endpoints from "queues" to "toptics" and don't have a problem....

would that eliminate that as a possiblitiy or should I still take out my bean?

[e0richt]

ok, I have found an answer to my question... it deals with an option with ActiveMQ...

if I use the jms.useAsyncSend=true in the connection factory, the system will not choke on the messages being sent through...