cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nadathur, Srivathsan" <snadat...@bell-labs.com>
Subject Anybody aware of threading problems with jserv/cocoon
Date Mon, 14 Feb 2000 21:52:15 GMT

> Hi,
> 
Thanks in advance for any responses...


> I have cocoon successfully working on Redhat 6.1
> The following are the version numbers of the various
> components.
> 
> IBM JDK 1.1.8
> Apache Webserver 1.3.9
> Apache Jserv 1.1
> Cocoon 1.6
> 
> 
> The problem shows up if cocoon serves a HTML frameset
> to the browser and the browser attempts to retrieve the URL's
> pointed to by the FRAME statements.  Here is the XSL
> file that generated the frameset.
> 
> <?xml version="1.0"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> 
> <xsl:template match="/">
> <xsl:processing-instruction
> name="cocoon-format">type="text/html"</xsl:processing-instruction>
> <html>
> <head>
>  <title>
>  </title>
> </head>
> <frameset framespacing="0" border="false" frameborder="0" rows="20%,80%">
>  <frame name="devices" src="http://<IPADDR>/weldev.xml"
> scrolling="no"></frame>
>  <frameset framespacing="0" border="false" frameborder="0" cols="20%,80%">
>   <frame name="menu" src="http://<IPADDR>/welmenu.xml" scrolling="no" />
>   <frame name="main" src="http://<IPADDR>/welmain.xml" scrolling="yes" />
>  </frameset>
> </frameset>
> </html>
> </xsl:template>
> 
> </xsl:stylesheet>
> 
> 60-70 % of the time the correct xml files are transfromed and returned for
> the respective frames
> and everything works as expected (the three frames in the page have their
> respective output)
> 
> However during the remaining attempts, the same content appears on two
> frames, 
> and the  page source as viewed by the HTML browser, indicates that two of
> the
> frames got the same HTML source.
>  
> The producer seems to be returning the correct XML file  (based on logs).
> It looks as though the output of a xsl transformation overwrote the output
> for 
> a previous request. This happens only when there are simultaneous HTTP
> requests
> from the client, as would be the case with a FRAMESET.
> 
> Is there a multi-threading problem here, which any of you have experienced
> before.
> 
> -Srivathsan Nadathur

Mime
View raw message