You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Alec Bickerton <al...@net-m.ch> on 2011/09/14 10:58:53 UTC
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Transformer parameters are intermittently not set.
Posted by "Nathaniel, Alfred" <Al...@six-group.com>.
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:alec.bickerton@net-m.ch]
Sent: Mittwoch, 14. September 2011 10:59
To: users@cocoon.apache.org
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Transformer parameters are intermittently not set.
Posted by Javier Puerto <ja...@apache.org>.
2011/9/14 Alec Bickerton <al...@net-m.ch>
> On 14/09/11 11:48, Thorsten Scherler wrote:
> > On Wed, 2011-09-14 at 10:58 +0200, Alec Bickerton wrote:
> >> 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>
>
I think that the above three parameters are to control the caching key. If
it's set to true, the parameters are included to build the caching key.
> >> <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?
> >
> > Hmm, try with <use-request-parameters>true</use-request-parameters>
> > however calling localhost:8888/general?bi_show=true should work
> >
> > salu2
> >
>
> Thanks for the suggestion, unfortunately I already tried setting
> <use-request-parameters>true</use-request-parameters>
> and using
> <map:parameter name="use-request-parameters" value="true" />.
>
> Neither of which solves the problem.
>
IMO it should be true for "use-request-parameters" due you use this
parameters on the transformation. But I didn't experienced this kind of
problems on Cocoon 2.2, I didn't tested 2.1.9.
>
> Alec,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
Re: Transformer parameters are intermittently not set.
Posted by Alec Bickerton <al...@net-m.ch>.
On 14/09/11 11:48, Thorsten Scherler wrote:
> On Wed, 2011-09-14 at 10:58 +0200, Alec Bickerton wrote:
>> 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?
>
> Hmm, try with <use-request-parameters>true</use-request-parameters>
> however calling localhost:8888/general?bi_show=true should work
>
> salu2
>
Thanks for the suggestion, unfortunately I already tried setting <use-request-parameters>true</use-request-parameters>
and using
<map:parameter name="use-request-parameters" value="true" />.
Neither of which solves the problem.
Alec,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Transformer parameters are intermittently not set.
Posted by Thorsten Scherler <sc...@gmail.com>.
On Wed, 2011-09-14 at 10:58 +0200, Alec Bickerton wrote:
> 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?
Hmm, try with <use-request-parameters>true</use-request-parameters>
however calling localhost:8888/general?bi_show=true should work
salu2
--
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org