Re: XMLC 2.1 compatibility with JDK 1.3

Hi Jim,

I have ran into similar problem with XMLC 2.2 alpha 3 in Tomcat 
environment and that has caused me several sleepless nights. Our final 
solution is to use the parallel GC (-XX:+UseParallelGC ) with 1.4.1 and 
that fixed it. I still don't have a clue about the cause. I'd 
appreciate if you could send me the Purify report. This would help my 
debugging process of the memory leak.

As for alpha 4, it still doesn't use latest release of Xerces, it just 
avoid conflict while XMLC is used in the environment with JDK 1.4, 
Xerces 1 or Xerces 2 by using the copy of Xerces existing in XMLC's 
namespace. This probably sound a bit confusing but this is the hack to 
get around the problem with XMLC in "modern" environment.

Also, it would be great if you could send me a note on how to configure 
WSAD with XMLC. I am trying to collect information about deploying XMLC 
in different container.

Thanks.

David Li

On Saturday, Mar 15, 2003, at 04:33 Asia/Shanghai, Cakalic, James wrote:

> Thanks for your quick response Richard. I had trouble getting out to 
> the CVS repository but I grabbed the 2.2 Alpha 4 that David Li posted. 
> After some amount of gyrations with my environment (WSAD 5.0) I was 
> able to get that release in and working along with the latest releases 
> of Xerces and Xalan (2.3.0 and 2.5.D1 respectively).
>
> It's good to be free of the Xerces restriction although, 
> unfortunately, it hasn't been the panacea that I hoped. I'm trying to 
> track down a memory leak in our web app which uses XMLC for page 
> presentation but uses Xerces, Xalan, and FOP to produce PDF reports. 
> Since we brought the report generation inside the app server we've 
> seen a gradual memory leak that has required a nightly restart 
> procedure. Purify has identified the (most) offending leak location to 
> be XMLSerializer.endElement(String) although for the life of me I 
> can't figure out why. I was hoping the latest release of Xerces would 
> fix the problem -- but no.
>
> I haven't tried out the new document reloading yet but I will real 
> soon.
>
> Anyway, thanks again for your quick response. It was really 
> appreciated.
> Jim
>
> -----Original Message-----
> From: Richard Kunze [mailto:[email protected]]
> Sent: Wednesday, March 12, 2003 8:06 AM
> To: [email protected]
> Subject: Re: Xmlc: XMLC 2.1 compatibility with JDK 1.3
>
>
> On Wednesday 12 March 2003 14:27, Cakalic, James wrote:
>> Hi, all. I'm currently using a version of XMLC somewhere between 
>> 2.0.1 and
>> 2.1 that was "lifted" from the Enhydra Application Server release 
>> 4.1. It's
>> been working fine but, because of external drivers, I'm trying to 
>> migrate
>> to the real 2.1 release.
>>
>> Here's my question: Is it possible that the XMLC 2.1 release was 
>> compiled
>> using JDK 1.4? I ask because I'm getting in some circumstances -- not
>> directly related to XMLC but using the xerces XMLSerializer -- I'm 
>> getting
>
> I don't recall the details (it's been a while since I compiled and 
> released XMLC 2.1 :-) but it's quite possible that I did compile with 
> 1.4. The error
> you're getting certainly indicates that I did...
>
> Now, XMLC doesn't use any 1.4 specific features and compiles with JDK 
> 1.3 without any problems. If you can access CVS repositories, I'd 
> recommend that
> you check out the latest sources from XMLC's anonymous CVS 
> (Instructions are
> at http://debian-sf.objectweb.org/cvs/?group_id=49) and compile it 
> yourself.
> The build is pretty much self-contained, the only external 
> dependencies are a
> JDK and ant.
>
> By using the latest CVS, you get some additional benefits over the 2.1
> version, namely
> - On-the-fly document reloading
> - XMLC coexists with newer Xerces versions
>
> Hope this helps,
>
> Richard
>
> -- 
> Richard Kunze
>
> [ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
> Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
> http://www.tivano.de, [email protected]
>
>
> Confidentiality Warning:  This e-mail contains information intended 
> only for the use of the individual or entity named above.  If the 
> reader of this e-mail is not the intended recipient or the employee or 
> agent responsible for delivering it to the intended recipient, any 
> dissemination, publication or copying of this e-mail is strictly 
> prohibited. The sender does not accept any responsibility for any 
> loss, disruption or damage to your data or computer system that may 
> occur while using data contained in, or transmitted with, this e-mail. 
>   If you have received this e-mail in error, please immediately notify 
> us by return e-mail.  Thank you.
>
>
> _______________________________________________
> XMLC mailing list
> [email protected]
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc