Thansk for the reply, scott.
Hopefully 2.2.0 will solve this problem. I still don't understand why
there's such a big performance difference between command-line and
Tomcat? BTW, I tried XT executable on NT from command line, it only took
3 seconds!
I would be very appreciated if you could tell me more about this switch
of incremental mode. Thanks very much!
-Li
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 28, 2001 9:06 AM
To: [EMAIL PROTECTED]
Subject: Re: Help: Xalan runs toooo slow on Tomcat
The join thread is just waiting for the transformation to finish... not
all
other threads.
We should be releasing a developer's release of 2.2.0 today. Unless you
turn incremental mode on, you should not be having these problems with
that
version if the issue is directly related to threads.
-scott
"Li Liang"
<lliang@first To:
<[EMAIL PROTECTED]>
rain.com> cc: (bcc: Scott
Boag/CAM/Lotus)
Subject: Help: Xalan runs
toooo slow on Tomcat
06/28/01
10:06 AM
Please
respond to
xalan-dev
Environment:
Tomcat 3.2.1
Xalan 2.0 (also tried 2.1.0)
Xerces 1.2.3
I applied a self-composed XSL from command line, it took 17 seconds. But
running it in a servlet on Tomcat, it took 80 seconds! After profiling,
I could identify that Thread.join() in endDocument() took up more than
90% of the time. I guess this is because it needs to wait all other
threads to finish to complete the work. I am using a SAX source to feed
into Xalan.
I read somewhere in this mailing list that Xalan has some threading
issues with servlet container. Is this the issue? If so, what's my
alternative?
Many thanks in advance.
Sincerely,
Li Liang
