cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geissel, Adrian" <adrian.geis...@ecb.int>
Subject RE: Unusual behaviour with <xsp-uti:include-uri/>
Date Thu, 05 Jun 2003 15:09:18 GMT
Hi,
Firstly, I should have mentioned that we're running Cocoon 2.0.4

Now for some more information - and it's really bizarre!

The stylesheet "query-to-options.xsl" contains two comments before the first
element:
one for the copyright, and
one explaining its purpose.

*REMOVING* these comment sections causes the offending exception, and
associated spinning thread, to disappear! Very bizarre! To be sure, the
comments are well formed, and do not contain and wierd or unusual
constructs, other than two  comments placed before the root element (but
then again, never experienced any issues doing this upto now).

Any ideas?

To help with this, attached is a more detailed stack-trace.
Much appreciated.

/Adrian


> -----Original Message-----
> From: Geissel, Adrian 
> Sent: Thursday 05 June 2003 09:51
> To: cocoon-dev@xml.apache.org
> Subject: Unusual behaviour with <xsp-uti:include-uri/>
> 
> 
> Hi,
> 
> I wanted to check with the list before posting the following as a bug:
> 
> I'm using the following construct in an XSP to read the 
> select-list values from a database. 
> 
>   <select>
>     <xsp-util:include-uri href="cocoon:/query/all/id_lookup.options"/>
>   </select>
> 
> The sitemap fragment handling this does the following:
> 
>   <map:match pattern="query/**/*.options">
>     <map:generate type="query"/>
>     <map:transform type="xslt"
src="stylesheets/system/query-to-options.xsl"/>
>     <map:serialize type="xml"/>
>   </map:match>
> 
> where the query generator issues a query to the database 
> (Oracle 9i) and returns the results as XML.
> 
> 
> The observation is that the first time (after the server 
> [WebLogic 7] is started, an exception is thrown (attached) 
> and Xalan appears to keep a background thread running 
> consuming 100% CPU - obviously not good. The strange thing is 
> that if the query is accessed directly (issuing 
> http://.../id_lookup.options) directly in the browser, then 
> the results are returned immediately, and also accessing the 
> pages that contain <xsp-util:include-uri/> work as expected.
> 
> has anyone come across something similar (preferrably with a 
> solution) or is there anything else that I can do?
> 
> Thanks in advance,
> Adrian
> 
> 



Any e-mail message from the European Central Bank (ECB) is sent in good faith but shall neither
be binding nor construed as constituting a commitment by the ECB except where provided for
in a written agreement.
This e-mail is intended only for the use of the recipient(s) named above. Any unauthorised
disclosure, use or dissemination, either in whole or in part, is prohibited.
If you have received this e-mail in error, please notify the sender immediately via e-mail
and delete this e-mail from your system.

Mime
View raw message