Out Of Memory error on using xpath for content based router

[gedda_mallik]

Hi All,

We are trying to route documents generated from multiple external sources using content based router.

Everything works fine as long as the documents are small, but once the documents reach the size of 100mb

or so, the component throws out of memory exception(we will use much larger documents in prod).

Is there a way to address this or an alternative approach I can use to route documents based on content?

Much Thanks.

Sorry for the duplicate post as this has been incorrectly posted in fuse mediation router forum. Here is the link to the issue

http://fusesource.com/forums/thread.jspa?threadID=1517&tstart=0

[gedda_mallik]

The current flow of our process is

FilePoller --> eip(content based router) --> bean

An external system generates a large xml document which is polled and picked

up by the File Poller and hands it over to content based router(which runs some

xpath queries) and hands it over to the correct end point based on the routing

rules.

We can control the process to use sax parser at the bean end point

but unfortunately the process fails even before reaching the bean end point.

To rule out which component is causing the issue we have removed the eip

component and now the process is

FilePoller --> bean

Even now the process fails with out of memory exception even before

reaching the bean end point.

We have increased the memory to the jvm (1536M)

So we are not sure if the process is failing trying to

build the message exchange or due to some other reason

We are using jdk 1.6 , Red Hat 4.7 and running on 1536M of memory

and fuse-esb-3.4.0.4

Any help is greatly appreciated.

[gedda_mallik]

I was assuming someone in the community would have come across a

scenario where they have to route a large xml document.

Any help is greatly appreciated.