> From: Abel Braaksma [mailto:[EMAIL PROTECTED]
> Sent: 27 March 2008 11:49
> To: [email protected]
> Subject: Re: FOP 0.20 Memory Leak?
Hi Abel,
Thanks for the information.
> Jason Timmins wrote:
> > amounts of XML documents through them, I'd gladly give it a try.
>
> You are making things way too complicated for yourself. FOP is a Java
> app, Saxon is a Java app (it is available as .NET but that's an
> automated port, not a .NET optimized version). Having two
> Java apps and
> calling them from IKVM makes things both slow and complicated at the
> same time. Unless there's a compelling need for you to use
> .NET for your
> transformations (you mention using IIS) why not call both
> Saxon and FOP
> by code?
I don't know how to do that but, if you're telling me I can call Java
methods straight from .NET without the delays associated with starting-up
the Java VM, then I'd gladly try that.
The only reason I have to use Saxon is that Microsoft don't have an XSLT v2
implementation. They seem focused on their LINQ technology at the moment so
the word is 'no XSLT v2 for now.'
> It's plain and simple, even when you have limited
> knowledge of
> Java. And you don't need to exit the JVM anymore. This has two main
> benefits: you gain speed (perhaps a lot!) and your
> application becomes easier.
No doubt but I have to stay with .NET as the rest of the site is .NET-based.
> And while your at it, you might as well upgrade to a newer version of
> FOP, since yours is really ancient.
Ahh, well, I've been holding-off upgrading because my XSL design tool,
XSLFastm uses FOP 0.20.5 to render to PDF as a preview. I thought it only
logical to stick with 0.20.5 until XSLFast switches to using the latest
version of FOP. I can't have my development tool showing one thing and what
gets printed being something different. That's one headache I can live
without.
Also, in my current environment I'd have to translate FOP 0.9X into a .NET
assembly and I'm not looking forward to that.
> > Which is why I'm asking. It might be Saxon or something in
> > IKVM that leaks.
>
> Or you just do not destroy your objects.... IIS + .NET is
> known for its
> late garbage collection, but when references stay open, it
> won't garbage
> collect at all.
Oh man, if only it were that simple. I've never written code the cleans
itself up so well as this app! I 'dispose' of every object and data
structure I use. I can say with reasonable certainty, it's not crappy code
in my .NET world. :-)
> > in IIS. It's the IIS worker process that grows until it
> > get's too big and is recycled.
>
> There are a zillion tools to track down memory leaks (try
> google, both
> free and commercial). But why trying the hard way when you can solve
> things easily by switching gears?
I will look around for some tools.
Thanks again for your comments.
Bye for now
Jason.
Jason Timmins (Technical Director) InterLinx Ltd.
Geo: West Mids, UK. Tele: +44 8707 430999. Fax: +44 8707 460999.
Beyond here there be dragons.
________________________________________________________________________
This email has been scanned for all viruses by the InterLinx Anti-Virus
Email service. For more information on a proactive anti-virus service
working around the clock, around the globe, visit
http://www.interlinx.co.uk/anti-virus-anti-spam.htm
________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
