Hi Kohsuke,
Thanks for the info we are going to try using single context . We have about
10 message driven applications running within Websphere app server and each
will have 15 concurrent threads running. Since all these run within the
same JVM the websphere class loader loads these classes from each of the
application install directory. So there would be separate instance of each
object in these 10 application loaded by the class loader.
Thanks and Regards
kesavan
>From: Kohsuke Kawaguchi <Kohsuke.Kawaguchi_at_Sun.COM>
>Reply-To: users_at_jaxb.dev.java.net
>To: users_at_jaxb.dev.java.net
>Subject: Re: InterleaveExp object growth
>Date: Thu, 17 Feb 2005 14:34:31 -0800
>
>Kesavan T.S wrote:
>>Hi Kohsuke,
>>Thanks for your response. I am attaching the schema its not very large
>>however on peak day load we might parse upto 500000 XML per day. Our
>>application uses Message Driven bean in Websphere 5.1.1 on AIX using jdk
>>1.4.2. We are using jaxb 1.0 I think this the what is see in manifest in
>
>This is the whole schema and you see 4 million InterleaveExp!? How many
>threads do you have? Please definitely share the JAXBContext object across
>threads, and please tell me how many InterleaveExps you'll see after that
>change.
>
>If you still see this many, there might be something very wrong.
>
>
>--
>Kohsuke Kawaguchi
>Sun Microsystems kohsuke.kawaguchi_at_sun.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
>For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>