Have you tried translets? Jacob Hookom Comprehensive Computer Science University of Wisconsin, Eau Claire
-----Original Message----- From: Will Hartung [mailto:[EMAIL PROTECTED]] Sent: Monday, July 22, 2002 12:21 PM To: Tomcat Users List Subject: Re: Xalan performance within Tomcat From: "Mario Felarca" <[EMAIL PROTECTED]> Sent: Sunday, July 21, 2002 3:50 PM Subject: Re: Xalan performance within Tomcat > At 09:57 PM 7/17/2002 +0000, you wrote: > > I am bumping my thread in the hopes that some people may not have seen it > before, or that others may have come across some new ideas. > > Also, for informational purposes, the time that I am actually measuring is > the actual time that the transform call takes. In both cases, the Source is > a StreamSource that has a ByteArrayInputStream at its base, and the Result > is a StreamResult that is going to a ByteArrayOutputStream. > > Can anyone think of anything, either java related, Tomcat related, xalan > related, etc. that would cause the time for the same transform to be much > much slower from within a servlet running in Tomcat as opposed to a test > program run from command line. This probably won't help, but it's fuel for the fire. If you think about it, once code is running, the only real difference between a command line program and a Servlet running in Tomcat will be its environment. Then, you can think of what in the environment may be affecting your program. The key distinctions that come to mind is that in Tomcat you have a completely different ClassLoader environment and, probably, a much more complex threading environment. Now, I'm assuming that your 6-8 minute servlet is simple a single request with "nothing else" going on. But the only thing I can think of is that your servlet is stuck waiting on something, though I can't imagine what. I would like to think that the XLST engine is distinct from any other, potential, engines within the same JVM (perhaps something that Tomcat is using internally). I can't fathom why the ClassLoaders would be dramatically different. You may simply need to try some profiling tool to see where your code is all hung up, or perhaps start making some stack dumps to see if anything comes to the top. Even the basic tools that come with Java should be more that adequate to point out the culprits. But, all in all, it just sounds to me that there is some kind of contention issue fighting within the code. Somebody is waiting for something. If you find out what the issue is, be sure to report back so we all can learn something. Sorry I couldn't be much more help. Best Regards, Will Hartung ([EMAIL PROTECTED]) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.375 / Virus Database: 210 - Release Date: 7/10/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.375 / Virus Database: 210 - Release Date: 7/10/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
