Hi,
You didn't say what version of Castor you are trying to use. There have
been a few patches around release 1.3 that fixed minor concurrency
issues and/or memory usage in the XML descriptor cache area.
But before we are going into details, let's first see your answer.
Cheers
Werner
eaidevpc32 wrote:
> We have a high volume messaging system where we unmarshall an incoming xml to
> java objects, set various values etc, then marshall back to xml and send on.
>
> This all worked fine until we did some performance testing, where memory
> usage just grew and grew until we hit an out of memory issue.
>
> our processing goes something like this:
>
> //setup
> -create XMLContext only once
> -load mapping xml
>
> //on incomming xml
> -create unmarshaller from cached XMLContext
> -unmarshall the incoming xml to java objects
> -perform various operations on the java objects and set values
> -create marshaller from cached XMLContext
> -marshall java objects back to xml and send on
>
>
> So I cant see why the memory usage would just grow and grow. we have checked
> for any obvious memory leaks elsewhere but it seems to be coming from the
> XMLContext. we have tried to create a new XMLContext for each incoming xml,
> and this did put a stop to the memory growth but at the cost of performance.
>
> Does anyone have any ideas?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
