SilverStream delays

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

SilverStream delays

SilverStream delays

2003-09-10 - By Tom Eastmond

Reply: 1 2

I am testing SimpleXSLTServlet on a SilverStream 3.75 application
server. The first time the servlet is run it takes nearly 18 minutes
(not seconds). After the first run, execution times are less then half a
second. I don't see this delay running the same servlet in Tomcat 4.1.
Below I've included the code I'm using - does anyone know why this could
be taking so long?

TIA,

Tom

long start = System.currentTimeMillis();

// The servlet returns HTML.

res.setContentType("text/html; charset=UTF-8");

// Output goes in the response stream.

PrintWriter out = res.getWriter();

try

{

TransformerFactory tFactory =
TransformerFactory.newInstance();

// Get the XML input document and the
stylesheet.

Source xmlSource = new StreamSource(new
URL("file", "", "..//Resources//StyleSheets//birds.xml").openStream());

Source xslSource = new StreamSource(new
URL("file", "", "..//Resources//StyleSheets//birds.xsl").openStream());

// Generate the transformer.

Transformer transformer =
tFactory.newTransformer(xslSource);

// Perform the transformation, sending the
output to the response.

transformer.transform(xmlSource, new
StreamResult(out));

}

catch (Exception e)

{

out.write(e.getMessage());

e.printStackTrace(out);

}

out.close();

System.out.println("Time elapsed: " +
(System.currentTimeMillis() - start)); //typical output on first run -
1118617

return;
//afterwards - 400-500

<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

I am testing SimpleXSLTServlet on a SilverStream 3.75
application
server. The first time the servlet is run it takes nearly 18 minutes (not
seconds). After the first run, execution times are less then half a second. I
don’t see this delay running the same servlet in Tomcat 4.1. Below I&
#8217;ve
included the code I’m using – does anyone know why this could be
taking so long?

 

TIA,

Tom

 

          
  long
start = System.currentTimeMillis();

// The servlet returns HTML.

          
  res.setContentType("text/html;
charset=UTF-8");    

          
  //
Output goes in the response stream.

          
  PrintWriter
out = res.getWriter();

          
  try

          
  {           

          
             
TransformerFactory
tFactory = TransformerFactory.newInstance();

          
              /
/
Get the XML input document and the stylesheet.

          
             
Source
xmlSource = new StreamSource(new URL("file", "",
"..//Resources//StyleSheets//birds.xml").openStream());


          
             
Source
xslSource = new StreamSource(new URL("file", "",
"..//Resources//StyleSheets//birds.xsl").openStream());


          
              /
/
Generate the transformer.

          
             
Transformer
transformer = tFactory.newTransformer(xslSource);

          
              /
/
Perform the transformation, sending the output to the response.

          
             
transformer.transform(xmlSource,
new StreamResult(out));

          
     
}

          
     
catch (Exception e)

          
     
{

          
     
        out.write(e.getMessage());

          
     
        e.printStackTrace(out);  
 


          
     
}

          
     
out.close();

          
     
System.out.println("Time elapsed: " + (System.currentTimeMillis() -
start));  //typical output on first run - 1118617

          
     
return;            
             
             
             
             
             
             
          
//afterwards - 400-500

</div>

</body>

</html>