Phil,
I have not checked in any code as of yet. Joe Kesselman mentioned that he might
have a few cycles to look into the code/pattern's of the core DTM code and I was
waiting to see if we might come up with a better fix. I will send you a note once
I have something more concrete.
-JG
Phil Friedman wrote:
John,
After a fair amount of testing, these changes, built on top of 2.6.0 seem to have solved the memory problem. Thanks for your attention.
I will try to test new Xalan builds on a more proactive basis, so if you have changes in the works please let me know as out products depend heavily on the SQL extension.
-- Regards, Phil Friedman -- Terralink Software 1-207-772-6500 x101
John Gentilin wrote:
Phil,
One last thought... These code changes should work equally well with a 2.6 Release.
So if you feel more comfortable with 2.6 and a fixed SQL Extension, then you may
want to ride with that until 2.7 is released.
-JG
Phil Friedman wrote:
John, would you like me to build with these files against CVS or the 2.6.0 release?
Regards, Phil Friedman - Terralink Software - 1-207-772-6500 x101
John Gentilin wrote:
Phil,
If you have the time, can you give this code a try. The memory signature is much better if you use
your original _nsFanTest.xsl but it does not work all that great with my apply-templates version
The DTMManager.release code was always being called, it happened in the SQLDocument version
of close. With the new code, while Process is running, the SQLDocuments accumulate but they are
GC'ed at the end. With the apply-templates code, we fail to locate the original DTM document so
the close does nothing.
Thanks John G
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
