Hi Alan, I don't have any explanation for your problem but a few hints to look at.
I would think that the transformer parameters are passed all right but that the request-param input module resolves all parameters to the empty string. Either the parameter map gets modified or the whole request object is replaced. A 1 in 5 failure rate is too large to be explained by memory-model related concurrency problem. You should check whether the generic-common pipeline or possible a high-level pipeline which calls general, messes with the request object. Other experiments to try: 1.) <use-request-parameters>true</use-request-parameters> instead of individual map:parameter 2.) <map:generate src="http://localhost/.../generic-common"; HTH, Alfred. -----Original Message----- From: Alec Bickerton [mailto:[email protected]] Sent: Mittwoch, 14. September 2011 10:59 To: [email protected] Subject: Transformer parameters are intermittently not set. Hi, I'm seeing some unusual behaviour in Cocoon 2.1.9. It appears that it possible for the xalan transformer parameters to not be set in a pipeline. Is this a known issue? Relevant part of the sitemap.xmap <map:match pattern="general"> <map:generate src="cocoon://projects/pe/templatetrafo/generic-common" /> <!-- No failure of the generator ever detected --> <map:transform src="transformer_one.xsl"> <map:parameter name="hostname" value="myhost.example.com"/> <map:parameter name="jsessionid" value="{request-param:jsessionid}"/> <map:parameter name="bi_show" value="{request-param:bi_show}"/> <map:parameter name="basehosttest" value="{request-param:basehosttest}"/> <map:parameter name="portalnumber" value="{request-param:portalnumber}"/> </map:transform> <map:transform src="transformer_two.xsl"> <map:parameter name="jsessionid" value="{request-param:jsessionid}"/> </map:transform> <map:serialize type="xml"/> </map:match> Using the above sitemap 1 in 5 requests fails to set the parameters triggering the pipeline to fail. I see this by setting a breakpoint in the extension method called from transformer_one. The transformer is configure as shown. <map:transformer logger="sitemap.transformer.xslt" name="xslt" pool-max="2048" pool-min="32" pool-grow="8" src="org.apache.cocoon.transformation.TraxTransformer" > <use-request-parameters>false</use-request-parameters> <use-session-parameters>false</use-session-parameters> <use-cookie-parameters>false</use-cookie-parameters> <xslt-processor-role>xalan</xslt-processor-role> <check-includes>true</check-includes> <use-deli>false</use-deli> <encoding>UTF-8</encoding> </map:transformer> Has anyone seen this behaviour in the past, or suggest a place to look for a misconfiguration? Alec, --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] The content of this e-mail is intended only for the confidential use of the person addressed. If you are not the intended recipient, please notify the sender and delete this e-mail immediately. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
