From j.hoffman at onehippo.com  Tue Jun 16 14:07:47 2009
From: j.hoffman at onehippo.com (Jeroen Hoffman)
Date: Tue Jun 16 14:07:53 2009
Subject: [Hippoportal-dev] Getting Started: Demo contains errors
In-Reply-To: <6CDBDA86-C92E-4455-B491-AFAB3B9F4167@finalist.com>
References: <6CDBDA86-C92E-4455-B491-AFAB3B9F4167@finalist.com>
Message-ID: <4A378B13.9060306@onehippo.com>

Hi Martin,

I just had a look at this (finally) and have the following comments:

- you're right about the https/http

- Maven-1 goal 'all' does exist in the latest trunk, see line 60 of 
http://svn.hippocms.org/repos/hippo/hippo-portal/trunk/demo-portal/maven.xml.
This goal will build the demo-pa and the demo-portal. Maybe you were in the 
demo-pa dir instead of the demo-portal?

- I used a fresh Tomcat 5.5.27 downloaded from 
http://tomcat.apache.org/download-55.cgi that requires a different setting 
compared to 5.5.23 and before. In the context file 
<tomcat>/conf/Catalina/localhost/demo-portal.xml, the Realm attribute 
useContextClassLoader has to be set to "true". This is not documented yet.

I agree that the documentation needs an update!

Jeroen Hoffman

Martin Sturm schreef:
> Hi all,
> 
> I'm testing Hippo Portal and experienced some troubles while trying to 
> follow the 'Getting Started: Demo' guide 
> (http://www.hippoportal.org/demo/index.html).
> First of all, the documentation is outdated on some aspects. It says you 
> have to check out demo-pa and demo-portal from 
> https://svn.hippocms.org/repos/hippo/hippo-portal/trunk/demo-pa (and 
> demo-portal), but these url's require authentication (probably the 
> non-secured http://svn.hippocms.org should be manted, which doesn'r 
> require authentication).
> 
> Secontly, if you use the trunk, you get a version which is much newer 
> than the version used in the tutorial (at least, that is my guess), 
> since the build target 'all' is not know. I solved this issue by 
> explicitly getting the 1.07.01 version using the SVN url 
> http://svn.hippocms.org/repos/hippo/hippo-portal/tags/Release-PORTAL-v1_07_01 
> 
> That version will compile using the 'maven all' command.
> 
> Unfortunately, it sitll doesn't work as expected when I follow the 
> guidelines in that document (with my personal modifcations). When 
> running demo-portal using Tomcat 5.5.27 and the recommended repository, 
> I get the error HTTP Status 404 - No page matched / request in site 
> view.  Accompanied by the following stack trace in de jetspeed.log file:
> 2009-05-18 14:32:00,009 [http-8080-Processor24] ERROR 
> org.apache.jetspeed.profiler.impl.ProfilerValveImpl - No page matched / 
> request in site view.
> org.apache.jetspeed.page.document.NodeNotFoundException: No page matched 
> / request in site view.
>    at 
> org.apache.jetspeed.portalsite.impl.PortalSiteSessionContextImpl.selectRequestPage(PortalSiteSessionContextImpl.java:645) 
> 
>    at 
> org.apache.jetspeed.portalsite.impl.PortalSiteSessionContextImpl.selectRequestPage(PortalSiteSessionContextImpl.java:228) 
> 
>     [...]
> 
> I'm accessing the page using http://preview.localhost:8080/demo-portal 
> (and preview.localhost is mapped to localhost). I'm not able to get 
> something meaningful on the screen using the current guide, and my 
> knowledge of Hippo Portal/Jetspeed is currently unsufficient to get it 
> working.
> 
> Everything runs on Mac OS X 10.5 us ing a MySQL database.
> 
> Hopefully, someone can help me with the latter problem, and can update 
> the documentation in order to avoid new users to suffer from similar  
> problems.
> 
> Regards,
> -- 
> Martin Sturm
> 
> Finalist IT Group - never stop developing!
> http://www.finalist.com
> E: martin.sturm@finalist.com
> T: +31882170882
> M: +31615529147
> 
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
From martin.sturm at finalist.com  Tue Jun 16 14:11:41 2009
From: martin.sturm at finalist.com (Martin Sturm)
Date: Tue Jun 16 14:11:52 2009
Subject: [Hippoportal-dev] Getting Started: Demo contains errors
In-Reply-To: <4A378B13.9060306@onehippo.com>
References: <6CDBDA86-C92E-4455-B491-AFAB3B9F4167@finalist.com>
	<4A378B13.9060306@onehippo.com>
Message-ID: <5E744248-678E-4FC9-9D06-7A1D5B0A6692@finalist.com>

Hi,

Thanks for the reply. I didn't look anymore into this issue, since  
we're upgraded tot Jetspeed 2.2.0 with the latest HST2, which is  
working pretty well I must say.

Related to this: are there any plans to provide additional  
documentation on the latter combination? Because at the moment, it is  
pretty hard to find information about this combination.

Regards,
--
Martin Sturm

Finalist IT Group - never stop developing!
http://www.finalist.com
E: martin.sturm@finalist.com
T: +31882170882
M: +31615529147

Op 16 jun 2009, om 14:07 heeft Jeroen Hoffman het volgende geschreven:

> Hi Martin,
>
> I just had a look at this (finally) and have the following comments:
>
> - you're right about the https/http
>
> - Maven-1 goal 'all' does exist in the latest trunk, see line 60 of http://svn.hippocms.org/repos/hippo/hippo-portal/trunk/demo-portal/maven.xml 
> .
> This goal will build the demo-pa and the demo-portal. Maybe you were  
> in the demo-pa dir instead of the demo-portal?
>
> - I used a fresh Tomcat 5.5.27 downloaded from http://tomcat.apache.org/download-55.cgi 
>  that requires a different setting compared to 5.5.23 and before. In  
> the context file <tomcat>/conf/Catalina/localhost/demo-portal.xml,  
> the Realm attribute useContextClassLoader has to be set to "true".  
> This is not documented yet.
>
> I agree that the documentation needs an update!
>
> Jeroen Hoffman
>
> Martin Sturm schreef:
>> Hi all,
>> I'm testing Hippo Portal and experienced some troubles while trying  
>> to follow the 'Getting Started: Demo' guide (http://www.hippoportal.org/demo/index.html 
>> ).
>> First of all, the documentation is outdated on some aspects. It  
>> says you have to check out demo-pa and demo-portal from https://svn.hippocms.org/repos/hippo/hippo-portal/trunk/demo-pa 
>>  (and demo-portal), but these url's require authentication  
>> (probably the non-secured http://svn.hippocms.org should be manted,  
>> which doesn'r require authentication).
>> Secontly, if you use the trunk, you get a version which is much  
>> newer than the version used in the tutorial (at least, that is my  
>> guess), since the build target 'all' is not know. I solved this  
>> issue by explicitly getting the 1.07.01 version using the SVN url http://svn.hippocms.org/repos/hippo/hippo-portal/tags/Release-PORTAL-v1_07_01 
>>  That version will compile using the 'maven all' command.
>> Unfortunately, it sitll doesn't work as expected when I follow the  
>> guidelines in that document (with my personal modifcations). When  
>> running demo-portal using Tomcat 5.5.27 and the recommended  
>> repository, I get the error HTTP Status 404 - No page matched /  
>> request in site view.  Accompanied by the following stack trace in  
>> de jetspeed.log file:
>> 2009-05-18 14:32:00,009 [http-8080-Processor24] ERROR  
>> org.apache.jetspeed.profiler.impl.ProfilerValveImpl - No page  
>> matched / request in site view.
>> org.apache.jetspeed.page.document.NodeNotFoundException: No page  
>> matched / request in site view.
>>   at  
>> org 
>> .apache 
>> .jetspeed 
>> .portalsite 
>> .impl 
>> .PortalSiteSessionContextImpl 
>> .selectRequestPage(PortalSiteSessionContextImpl.java:645)    at  
>> org 
>> .apache 
>> .jetspeed 
>> .portalsite 
>> .impl 
>> .PortalSiteSessionContextImpl 
>> .selectRequestPage(PortalSiteSessionContextImpl.java:228)     [...]
>> I'm accessing the page using http://preview.localhost:8080/demo-portal 
>>  (and preview.localhost is mapped to localhost). I'm not able to  
>> get something meaningful on the screen using the current guide, and  
>> my knowledge of Hippo Portal/Jetspeed is currently unsufficient to  
>> get it working.
>> Everything runs on Mac OS X 10.5 us ing a MySQL database.
>> Hopefully, someone can help me with the latter problem, and can  
>> update the documentation in order to avoid new users to suffer from  
>> similar  problems.
>> Regards,
>> -- 
>> Martin Sturm
>> Finalist IT Group - never stop developing!
>> http://www.finalist.com
>> E: martin.sturm@finalist.com
>> T: +31882170882
>> M: +31615529147
>> _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev

From mduijvelaar at anwb.nl  Fri Jun 26 10:23:30 2009
From: mduijvelaar at anwb.nl (Mike Duijvelaar)
Date: Fri Jun 26 10:23:33 2009
Subject: [Hippoportal-dev] portal issue
Message-ID: <4A44A1A3.84E8.0098.1@anwb.nl>

Hello,

Has anyone seen the next problem:

If you run a high loadtest in portal, that sometimes porlets are mingled. The titel of the page is e.g. portlet A(psml), but content is from portlet B(psml).

Met vriendelijke groet,
Mike Duijvelaar
 
ANWB Online Beheer
 
Gebouw B midden; B330
Wassenaarseweg 220
Den Haag
 
Tel: (intern) toestel 7325/7301
Mob: 06-50233023
**********************************************************************************************
Disclaimer

E-mail wordt door ANWB niet gebruikt voor het aangaan van externe verplichtingen.
Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze e-mail
onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact op te
nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail mag niet
worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
toestemming van de afzender.
ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB kan
echter niet garanderen dat deze e-mail juist, volledig, tijdig en virusvrij wordt
overgebracht. In een dergelijk geval is ANWB op geen enkele wijze aansprakelijk
voor enige schade, direct dan wel indirect, in welke vorm dan ook.

ANWB B.V.
**********************************************************************************************

From nick.stolwijk at gmail.com  Mon Jun 29 11:17:33 2009
From: nick.stolwijk at gmail.com (Nick Stolwijk)
Date: Mon Jun 29 11:17:34 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <4A44A1A3.84E8.0098.1@anwb.nl>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
Message-ID: <3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>

A little clarification about what we are seeing.

We have psml A with some portlets and psml B with some portlets. It
seems that, under load, sometimes a request which retrieves page A
gets the content page A with one portlet not on page A but on page B
and the portlet that is supposed to be there, isn't there. It even
seems that this content is from another request.

This is just a wild guess, but it seems that the portlet handling
intermingles outputstreams between requests.

Is this a known issue?

Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl



2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
> Hello,
>
> Has anyone seen the next problem:
>
> If you run a high loadtest in portal, that sometimes porlets are mingled. The titel of the page is e.g. portlet A(psml), but content is from portlet B(psml).
>
> Met vriendelijke groet,
> Mike Duijvelaar
>
> ANWB Online Beheer
>
> Gebouw B midden; B330
> Wassenaarseweg 220
> Den Haag
>
> Tel: (intern) toestel 7325/7301
> Mob: 06-50233023
> **********************************************************************************************
> Disclaimer
>
> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe verplichtingen.
> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze e-mail
> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact op te
> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail mag niet
> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
> toestemming van de afzender.
> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB kan
> echter niet garanderen dat deze e-mail juist, volledig, tijdig en virusvrij wordt
> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze aansprakelijk
> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>
> ANWB B.V.
> **********************************************************************************************
>
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>
From a.douma at onehippo.com  Mon Jun 29 11:45:40 2009
From: a.douma at onehippo.com (Ate Douma)
Date: Mon Jun 29 11:45:49 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
Message-ID: <4A488D44.4070009@onehippo.com>

Nick Stolwijk wrote:
> A little clarification about what we are seeing.
> 
> We have psml A with some portlets and psml B with some portlets. It
> seems that, under load, sometimes a request which retrieves page A
> gets the content page A with one portlet not on page A but on page B
> and the portlet that is supposed to be there, isn't there. It even
> seems that this content is from another request.
> 
> This is just a wild guess, but it seems that the portlet handling
> intermingles outputstreams between requests.
> 
> Is this a known issue?

No, not really, except possibly when the following (incorrect) configuration is used:
- if portletA (on Page A) has the same fragment id as portlet B (on Page B)
- portlet caching is enabled for one or both these portlets (e.g. content cache managed by the *portal*)

If the above is the case, the portal might deliver the content for the portlet directly from its internal cache which is keyed off the 
fragment id.
Thus: if you have enabled portlet caching you should *not* reuse its fragment id across psml pages.

Regards,

Ate

> 
> Nick Stolwijk
> ~Java Developer~
> 
> Iprofs BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> www.iprofs.nl
> 
> 
> 
> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>> Hello,
>>
>> Has anyone seen the next problem:
>>
>> If you run a high loadtest in portal, that sometimes porlets are mingled. The titel of the page is e.g. portlet A(psml), but content is from portlet B(psml).
>>
>> Met vriendelijke groet,
>> Mike Duijvelaar
>>
>> ANWB Online Beheer
>>
>> Gebouw B midden; B330
>> Wassenaarseweg 220
>> Den Haag
>>
>> Tel: (intern) toestel 7325/7301
>> Mob: 06-50233023
>> **********************************************************************************************
>> Disclaimer
>>
>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe verplichtingen.
>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze e-mail
>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact op te
>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail mag niet
>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>> toestemming van de afzender.
>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB kan
>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en virusvrij wordt
>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze aansprakelijk
>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>
>> ANWB B.V.
>> **********************************************************************************************
>>
>> _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev


-- 
a.douma@onehippo.com  www.onehippo.com

Amsterdam     - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100 +1(877) 41-HIPPO

From wouter.zelle at gmail.com  Mon Jun 29 11:55:30 2009
From: wouter.zelle at gmail.com (Wouter Zelle)
Date: Mon Jun 29 11:55:31 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <4A488D44.4070009@onehippo.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
	<4A488D44.4070009@onehippo.com>
Message-ID: <52cb4dc10906290255r366a20fna16b4a6326b2be98@mail.gmail.com>

Hi Ate,

Portlet caching is off for all of these portlets
(<expiration-cache>0</expiration-cache>).

Regards,

Wouter


On Mon, Jun 29, 2009 at 11:45, Ate Douma <a.douma@onehippo.com> wrote:

> Nick Stolwijk wrote:
>
>> A little clarification about what we are seeing.
>>
>> We have psml A with some portlets and psml B with some portlets. It
>> seems that, under load, sometimes a request which retrieves page A
>> gets the content page A with one portlet not on page A but on page B
>> and the portlet that is supposed to be there, isn't there. It even
>> seems that this content is from another request.
>>
>> This is just a wild guess, but it seems that the portlet handling
>> intermingles outputstreams between requests.
>>
>> Is this a known issue?
>>
>
> No, not really, except possibly when the following (incorrect)
> configuration is used:
> - if portletA (on Page A) has the same fragment id as portlet B (on Page B)
> - portlet caching is enabled for one or both these portlets (e.g. content
> cache managed by the *portal*)
>
> If the above is the case, the portal might deliver the content for the
> portlet directly from its internal cache which is keyed off the fragment id.
> Thus: if you have enabled portlet caching you should *not* reuse its
> fragment id across psml pages.
>
> Regards,
>
> Ate
>
>
>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> Iprofs BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> www.iprofs.nl
>>
>>
>>
>> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>>
>>> Hello,
>>>
>>> Has anyone seen the next problem:
>>>
>>> If you run a high loadtest in portal, that sometimes porlets are mingled.
>>> The titel of the page is e.g. portlet A(psml), but content is from portlet
>>> B(psml).
>>>
>>> Met vriendelijke groet,
>>> Mike Duijvelaar
>>>
>>> ANWB Online Beheer
>>>
>>> Gebouw B midden; B330
>>> Wassenaarseweg 220
>>> Den Haag
>>>
>>> Tel: (intern) toestel 7325/7301
>>> Mob: 06-50233023
>>>
>>> **********************************************************************************************
>>> Disclaimer
>>>
>>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe
>>> verplichtingen.
>>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze
>>> e-mail
>>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact
>>> op te
>>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail
>>> mag niet
>>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>>> toestemming van de afzender.
>>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB
>>> kan
>>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en
>>> virusvrij wordt
>>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze
>>> aansprakelijk
>>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>>
>>> ANWB B.V.
>>>
>>> **********************************************************************************************
>>>
>>> _______________________________________________
>>> Hippoportal-dev mailing list
>>> Hippoportal-dev@lists.hippo.nl
>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>
>>>  _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>
>
>
> --
> a.douma@onehippo.com  www.onehippo.com
>
> Amsterdam     - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100
> +1(877) 41-HIPPO
>
>
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20090629/2852c7b0/attachment.htm
From nick.stolwijk at gmail.com  Mon Jun 29 11:56:43 2009
From: nick.stolwijk at gmail.com (Nick Stolwijk)
Date: Mon Jun 29 11:56:45 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <4A488D44.4070009@onehippo.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
	<4A488D44.4070009@onehippo.com>
Message-ID: <3a15f5ad0906290256g2d8011e1y1284854de1e9f2c7@mail.gmail.com>

We have the convention for fragment id's like
<projectname>-<page-name>-<page-part> so no double fragment id's (I
have just double checked them). Also the portlet cache is disabled,
afaik.

We'll keep investigating the issue. If someone has any additional
tips, they're welcome.

With regards,

Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl



On Mon, Jun 29, 2009 at 11:45 AM, Ate Douma<a.douma@onehippo.com> wrote:
> Nick Stolwijk wrote:
>>
>> A little clarification about what we are seeing.
>>
>> We have psml A with some portlets and psml B with some portlets. It
>> seems that, under load, sometimes a request which retrieves page A
>> gets the content page A with one portlet not on page A but on page B
>> and the portlet that is supposed to be there, isn't there. It even
>> seems that this content is from another request.
>>
>> This is just a wild guess, but it seems that the portlet handling
>> intermingles outputstreams between requests.
>>
>> Is this a known issue?
>
> No, not really, except possibly when the following (incorrect) configuration
> is used:
> - if portletA (on Page A) has the same fragment id as portlet B (on Page B)
> - portlet caching is enabled for one or both these portlets (e.g. content
> cache managed by the *portal*)
>
> If the above is the case, the portal might deliver the content for the
> portlet directly from its internal cache which is keyed off the fragment id.
> Thus: if you have enabled portlet caching you should *not* reuse its
> fragment id across psml pages.
>
> Regards,
>
> Ate
>
>>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> Iprofs BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> www.iprofs.nl
>>
>>
>>
>> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>>>
>>> Hello,
>>>
>>> Has anyone seen the next problem:
>>>
>>> If you run a high loadtest in portal, that sometimes porlets are mingled.
>>> The titel of the page is e.g. portlet A(psml), but content is from portlet
>>> B(psml).
>>>
>>> Met vriendelijke groet,
>>> Mike Duijvelaar
>>>
>>> ANWB Online Beheer
>>>
>>> Gebouw B midden; B330
>>> Wassenaarseweg 220
>>> Den Haag
>>>
>>> Tel: (intern) toestel 7325/7301
>>> Mob: 06-50233023
>>>
>>> **********************************************************************************************
>>> Disclaimer
>>>
>>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe
>>> verplichtingen.
>>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze
>>> e-mail
>>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact
>>> op te
>>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail
>>> mag niet
>>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>>> toestemming van de afzender.
>>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB
>>> kan
>>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en
>>> virusvrij wordt
>>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze
>>> aansprakelijk
>>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>>
>>> ANWB B.V.
>>>
>>> **********************************************************************************************
>>>
>>> _______________________________________________
>>> Hippoportal-dev mailing list
>>> Hippoportal-dev@lists.hippo.nl
>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>
>> _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>
>
> --
> a.douma@onehippo.com ?www.onehippo.com
>
> Amsterdam ? ? - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100
> +1(877) 41-HIPPO
>
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>
From w.ko at onehippo.com  Mon Jun 29 12:16:46 2009
From: w.ko at onehippo.com (Woonsan Ko)
Date: Mon Jun 29 12:16:49 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <3a15f5ad0906290256g2d8011e1y1284854de1e9f2c7@mail.gmail.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
	<4A488D44.4070009@onehippo.com>
	<3a15f5ad0906290256g2d8011e1y1284854de1e9f2c7@mail.gmail.com>
Message-ID: <1e122f750906290316i127dae85j8b513880135c7bb7@mail.gmail.com>

Hi Nick,

If a portlet class or its ancestor class has member variables to store
some states and the member variables are set on requests, it would
cause a thread-safety problem.

Just two cents,

Woonsan


On Mon, Jun 29, 2009 at 11:56 AM, Nick Stolwijk<nick.stolwijk@gmail.com> wrote:
> We have the convention for fragment id's like
> <projectname>-<page-name>-<page-part> so no double fragment id's (I
> have just double checked them). Also the portlet cache is disabled,
> afaik.
>
> We'll keep investigating the issue. If someone has any additional
> tips, they're welcome.
>
> With regards,
>
> Nick Stolwijk
> ~Java Developer~
>
> Iprofs BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> www.iprofs.nl
>
>
>
> On Mon, Jun 29, 2009 at 11:45 AM, Ate Douma<a.douma@onehippo.com> wrote:
>> Nick Stolwijk wrote:
>>>
>>> A little clarification about what we are seeing.
>>>
>>> We have psml A with some portlets and psml B with some portlets. It
>>> seems that, under load, sometimes a request which retrieves page A
>>> gets the content page A with one portlet not on page A but on page B
>>> and the portlet that is supposed to be there, isn't there. It even
>>> seems that this content is from another request.
>>>
>>> This is just a wild guess, but it seems that the portlet handling
>>> intermingles outputstreams between requests.
>>>
>>> Is this a known issue?
>>
>> No, not really, except possibly when the following (incorrect) configuration
>> is used:
>> - if portletA (on Page A) has the same fragment id as portlet B (on Page B)
>> - portlet caching is enabled for one or both these portlets (e.g. content
>> cache managed by the *portal*)
>>
>> If the above is the case, the portal might deliver the content for the
>> portlet directly from its internal cache which is keyed off the fragment id.
>> Thus: if you have enabled portlet caching you should *not* reuse its
>> fragment id across psml pages.
>>
>> Regards,
>>
>> Ate
>>
>>>
>>> Nick Stolwijk
>>> ~Java Developer~
>>>
>>> Iprofs BV.
>>> Claus Sluterweg 125
>>> 2012 WS Haarlem
>>> www.iprofs.nl
>>>
>>>
>>>
>>> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>>>>
>>>> Hello,
>>>>
>>>> Has anyone seen the next problem:
>>>>
>>>> If you run a high loadtest in portal, that sometimes porlets are mingled.
>>>> The titel of the page is e.g. portlet A(psml), but content is from portlet
>>>> B(psml).
>>>>
>>>> Met vriendelijke groet,
>>>> Mike Duijvelaar
>>>>
>>>> ANWB Online Beheer
>>>>
>>>> Gebouw B midden; B330
>>>> Wassenaarseweg 220
>>>> Den Haag
>>>>
>>>> Tel: (intern) toestel 7325/7301
>>>> Mob: 06-50233023
>>>>
>>>> **********************************************************************************************
>>>> Disclaimer
>>>>
>>>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe
>>>> verplichtingen.
>>>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze
>>>> e-mail
>>>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact
>>>> op te
>>>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail
>>>> mag niet
>>>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>>>> toestemming van de afzender.
>>>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB
>>>> kan
>>>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en
>>>> virusvrij wordt
>>>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze
>>>> aansprakelijk
>>>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>>>
>>>> ANWB B.V.
>>>>
>>>> **********************************************************************************************
>>>>
>>>> _______________________________________________
>>>> Hippoportal-dev mailing list
>>>> Hippoportal-dev@lists.hippo.nl
>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>
>>> _______________________________________________
>>> Hippoportal-dev mailing list
>>> Hippoportal-dev@lists.hippo.nl
>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>
>>
>> --
>> a.douma@onehippo.com ?www.onehippo.com
>>
>> Amsterdam ? ? - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100
>> +1(877) 41-HIPPO
>>
>> _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>



-- 
w.ko@onehippo.com     www.onehippo.com
EUROPE ? AMSTERDAM - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
NORTH AMERICA ? SAN FRANCISCO - Hippo USA Inc. 185 H Street, Suite B
Petaluma CA 94952 +1 (877) 414-4776
From nick.stolwijk at gmail.com  Mon Jun 29 12:46:19 2009
From: nick.stolwijk at gmail.com (Nick Stolwijk)
Date: Mon Jun 29 12:46:20 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <1e122f750906290316i127dae85j8b513880135c7bb7@mail.gmail.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
	<4A488D44.4070009@onehippo.com>
	<3a15f5ad0906290256g2d8011e1y1284854de1e9f2c7@mail.gmail.com>
	<1e122f750906290316i127dae85j8b513880135c7bb7@mail.gmail.com>
Message-ID: <3a15f5ad0906290346o13ca7f8cvedf8607699a2f88@mail.gmail.com>

That is correct, but our problem is with two completely different
portlets, which normally only exists on two different psml's. But once
in a while, the content of portlet B is shown on page A, instead of
portlet A.

With regards,

Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl



On Mon, Jun 29, 2009 at 12:16 PM, Woonsan Ko<w.ko@onehippo.com> wrote:
> Hi Nick,
>
> If a portlet class or its ancestor class has member variables to store
> some states and the member variables are set on requests, it would
> cause a thread-safety problem.
>
> Just two cents,
>
> Woonsan
>
>
> On Mon, Jun 29, 2009 at 11:56 AM, Nick Stolwijk<nick.stolwijk@gmail.com> wrote:
>> We have the convention for fragment id's like
>> <projectname>-<page-name>-<page-part> so no double fragment id's (I
>> have just double checked them). Also the portlet cache is disabled,
>> afaik.
>>
>> We'll keep investigating the issue. If someone has any additional
>> tips, they're welcome.
>>
>> With regards,
>>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> Iprofs BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> www.iprofs.nl
>>
>>
>>
>> On Mon, Jun 29, 2009 at 11:45 AM, Ate Douma<a.douma@onehippo.com> wrote:
>>> Nick Stolwijk wrote:
>>>>
>>>> A little clarification about what we are seeing.
>>>>
>>>> We have psml A with some portlets and psml B with some portlets. It
>>>> seems that, under load, sometimes a request which retrieves page A
>>>> gets the content page A with one portlet not on page A but on page B
>>>> and the portlet that is supposed to be there, isn't there. It even
>>>> seems that this content is from another request.
>>>>
>>>> This is just a wild guess, but it seems that the portlet handling
>>>> intermingles outputstreams between requests.
>>>>
>>>> Is this a known issue?
>>>
>>> No, not really, except possibly when the following (incorrect) configuration
>>> is used:
>>> - if portletA (on Page A) has the same fragment id as portlet B (on Page B)
>>> - portlet caching is enabled for one or both these portlets (e.g. content
>>> cache managed by the *portal*)
>>>
>>> If the above is the case, the portal might deliver the content for the
>>> portlet directly from its internal cache which is keyed off the fragment id.
>>> Thus: if you have enabled portlet caching you should *not* reuse its
>>> fragment id across psml pages.
>>>
>>> Regards,
>>>
>>> Ate
>>>
>>>>
>>>> Nick Stolwijk
>>>> ~Java Developer~
>>>>
>>>> Iprofs BV.
>>>> Claus Sluterweg 125
>>>> 2012 WS Haarlem
>>>> www.iprofs.nl
>>>>
>>>>
>>>>
>>>> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>>>>>
>>>>> Hello,
>>>>>
>>>>> Has anyone seen the next problem:
>>>>>
>>>>> If you run a high loadtest in portal, that sometimes porlets are mingled.
>>>>> The titel of the page is e.g. portlet A(psml), but content is from portlet
>>>>> B(psml).
>>>>>
>>>>> Met vriendelijke groet,
>>>>> Mike Duijvelaar
>>>>>
>>>>> ANWB Online Beheer
>>>>>
>>>>> Gebouw B midden; B330
>>>>> Wassenaarseweg 220
>>>>> Den Haag
>>>>>
>>>>> Tel: (intern) toestel 7325/7301
>>>>> Mob: 06-50233023
>>>>>
>>>>> **********************************************************************************************
>>>>> Disclaimer
>>>>>
>>>>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe
>>>>> verplichtingen.
>>>>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze
>>>>> e-mail
>>>>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact
>>>>> op te
>>>>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail
>>>>> mag niet
>>>>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>>>>> toestemming van de afzender.
>>>>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB
>>>>> kan
>>>>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en
>>>>> virusvrij wordt
>>>>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze
>>>>> aansprakelijk
>>>>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>>>>
>>>>> ANWB B.V.
>>>>>
>>>>> **********************************************************************************************
>>>>>
>>>>> _______________________________________________
>>>>> Hippoportal-dev mailing list
>>>>> Hippoportal-dev@lists.hippo.nl
>>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>>
>>>> _______________________________________________
>>>> Hippoportal-dev mailing list
>>>> Hippoportal-dev@lists.hippo.nl
>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>
>>>
>>> --
>>> a.douma@onehippo.com ?www.onehippo.com
>>>
>>> Amsterdam ? ? - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>>> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100
>>> +1(877) 41-HIPPO
>>>
>>> _______________________________________________
>>> Hippoportal-dev mailing list
>>> Hippoportal-dev@lists.hippo.nl
>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>
>> _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>
>
>
>
> --
> w.ko@onehippo.com ? ? www.onehippo.com
> EUROPE ? AMSTERDAM - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> NORTH AMERICA ? SAN FRANCISCO - Hippo USA Inc. 185 H Street, Suite B
> Petaluma CA 94952 +1 (877) 414-4776
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>
From nick.stolwijk at gmail.com  Tue Jun 30 09:10:33 2009
From: nick.stolwijk at gmail.com (Nick Stolwijk)
Date: Tue Jun 30 09:10:35 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <3a15f5ad0906290346o13ca7f8cvedf8607699a2f88@mail.gmail.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>
	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>
	<4A488D44.4070009@onehippo.com>
	<3a15f5ad0906290256g2d8011e1y1284854de1e9f2c7@mail.gmail.com>
	<1e122f750906290316i127dae85j8b513880135c7bb7@mail.gmail.com>
	<3a15f5ad0906290346o13ca7f8cvedf8607699a2f88@mail.gmail.com>
Message-ID: <3a15f5ad0906300010kf4c10b9o6b42edfac14401ba@mail.gmail.com>

It looks like we have found our problem. It was in one of our
extensions to the hippo portal, which saved the request context in a
member variable. And this caused the wrong PSML to be loaded and thus
the wrong portlets being rendered.

With regards,

Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl



On Mon, Jun 29, 2009 at 12:46 PM, Nick Stolwijk<nick.stolwijk@gmail.com> wrote:
> That is correct, but our problem is with two completely different
> portlets, which normally only exists on two different psml's. But once
> in a while, the content of portlet B is shown on page A, instead of
> portlet A.
>
> With regards,
>
> Nick Stolwijk
> ~Java Developer~
>
> Iprofs BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> www.iprofs.nl
>
>
>
> On Mon, Jun 29, 2009 at 12:16 PM, Woonsan Ko<w.ko@onehippo.com> wrote:
>> Hi Nick,
>>
>> If a portlet class or its ancestor class has member variables to store
>> some states and the member variables are set on requests, it would
>> cause a thread-safety problem.
>>
>> Just two cents,
>>
>> Woonsan
>>
>>
>> On Mon, Jun 29, 2009 at 11:56 AM, Nick Stolwijk<nick.stolwijk@gmail.com> wrote:
>>> We have the convention for fragment id's like
>>> <projectname>-<page-name>-<page-part> so no double fragment id's (I
>>> have just double checked them). Also the portlet cache is disabled,
>>> afaik.
>>>
>>> We'll keep investigating the issue. If someone has any additional
>>> tips, they're welcome.
>>>
>>> With regards,
>>>
>>> Nick Stolwijk
>>> ~Java Developer~
>>>
>>> Iprofs BV.
>>> Claus Sluterweg 125
>>> 2012 WS Haarlem
>>> www.iprofs.nl
>>>
>>>
>>>
>>> On Mon, Jun 29, 2009 at 11:45 AM, Ate Douma<a.douma@onehippo.com> wrote:
>>>> Nick Stolwijk wrote:
>>>>>
>>>>> A little clarification about what we are seeing.
>>>>>
>>>>> We have psml A with some portlets and psml B with some portlets. It
>>>>> seems that, under load, sometimes a request which retrieves page A
>>>>> gets the content page A with one portlet not on page A but on page B
>>>>> and the portlet that is supposed to be there, isn't there. It even
>>>>> seems that this content is from another request.
>>>>>
>>>>> This is just a wild guess, but it seems that the portlet handling
>>>>> intermingles outputstreams between requests.
>>>>>
>>>>> Is this a known issue?
>>>>
>>>> No, not really, except possibly when the following (incorrect) configuration
>>>> is used:
>>>> - if portletA (on Page A) has the same fragment id as portlet B (on Page B)
>>>> - portlet caching is enabled for one or both these portlets (e.g. content
>>>> cache managed by the *portal*)
>>>>
>>>> If the above is the case, the portal might deliver the content for the
>>>> portlet directly from its internal cache which is keyed off the fragment id.
>>>> Thus: if you have enabled portlet caching you should *not* reuse its
>>>> fragment id across psml pages.
>>>>
>>>> Regards,
>>>>
>>>> Ate
>>>>
>>>>>
>>>>> Nick Stolwijk
>>>>> ~Java Developer~
>>>>>
>>>>> Iprofs BV.
>>>>> Claus Sluterweg 125
>>>>> 2012 WS Haarlem
>>>>> www.iprofs.nl
>>>>>
>>>>>
>>>>>
>>>>> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Has anyone seen the next problem:
>>>>>>
>>>>>> If you run a high loadtest in portal, that sometimes porlets are mingled.
>>>>>> The titel of the page is e.g. portlet A(psml), but content is from portlet
>>>>>> B(psml).
>>>>>>
>>>>>> Met vriendelijke groet,
>>>>>> Mike Duijvelaar
>>>>>>
>>>>>> ANWB Online Beheer
>>>>>>
>>>>>> Gebouw B midden; B330
>>>>>> Wassenaarseweg 220
>>>>>> Den Haag
>>>>>>
>>>>>> Tel: (intern) toestel 7325/7301
>>>>>> Mob: 06-50233023
>>>>>>
>>>>>> **********************************************************************************************
>>>>>> Disclaimer
>>>>>>
>>>>>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe
>>>>>> verplichtingen.
>>>>>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze
>>>>>> e-mail
>>>>>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact
>>>>>> op te
>>>>>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail
>>>>>> mag niet
>>>>>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>>>>>> toestemming van de afzender.
>>>>>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB
>>>>>> kan
>>>>>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en
>>>>>> virusvrij wordt
>>>>>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze
>>>>>> aansprakelijk
>>>>>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>>>>>
>>>>>> ANWB B.V.
>>>>>>
>>>>>> **********************************************************************************************
>>>>>>
>>>>>> _______________________________________________
>>>>>> Hippoportal-dev mailing list
>>>>>> Hippoportal-dev@lists.hippo.nl
>>>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>>>
>>>>> _______________________________________________
>>>>> Hippoportal-dev mailing list
>>>>> Hippoportal-dev@lists.hippo.nl
>>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>
>>>>
>>>> --
>>>> a.douma@onehippo.com ?www.onehippo.com
>>>>
>>>> Amsterdam ? ? - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>>>> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100
>>>> +1(877) 41-HIPPO
>>>>
>>>> _______________________________________________
>>>> Hippoportal-dev mailing list
>>>> Hippoportal-dev@lists.hippo.nl
>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>
>>> _______________________________________________
>>> Hippoportal-dev mailing list
>>> Hippoportal-dev@lists.hippo.nl
>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>
>>
>>
>>
>> --
>> w.ko@onehippo.com ? ? www.onehippo.com
>> EUROPE ? AMSTERDAM - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>> NORTH AMERICA ? SAN FRANCISCO - Hippo USA Inc. 185 H Street, Suite B
>> Petaluma CA 94952 +1 (877) 414-4776
>> _______________________________________________
>> Hippoportal-dev mailing list
>> Hippoportal-dev@lists.hippo.nl
>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>
>
From a.douma at onehippo.com  Tue Jun 30 14:07:00 2009
From: a.douma at onehippo.com (Ate Douma)
Date: Tue Jun 30 14:07:07 2009
Subject: [Hippoportal-dev] portal issue
In-Reply-To: <3a15f5ad0906300010kf4c10b9o6b42edfac14401ba@mail.gmail.com>
References: <4A44A1A3.84E8.0098.1@anwb.nl>	<3a15f5ad0906290217g68c13784lcc10068f06962bf2@mail.gmail.com>	<4A488D44.4070009@onehippo.com>	<3a15f5ad0906290256g2d8011e1y1284854de1e9f2c7@mail.gmail.com>	<1e122f750906290316i127dae85j8b513880135c7bb7@mail.gmail.com>	<3a15f5ad0906290346o13ca7f8cvedf8607699a2f88@mail.gmail.com>
	<3a15f5ad0906300010kf4c10b9o6b42edfac14401ba@mail.gmail.com>
Message-ID: <4A49FFE4.3020402@onehippo.com>

Nick Stolwijk wrote:
> It looks like we have found our problem. It was in one of our
> extensions to the hippo portal, which saved the request context in a
> member variable. And this caused the wrong PSML to be loaded and thus
> the wrong portlets being rendered.
Ok, thanks for reporting back Nick.

We'll regard this issue then as resolved and out-of-scope/unrelated to Hippo Portal.

Regards,

Ate

> 
> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> Iprofs BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> www.iprofs.nl
> 
> 
> 
> On Mon, Jun 29, 2009 at 12:46 PM, Nick Stolwijk<nick.stolwijk@gmail.com> wrote:
>> That is correct, but our problem is with two completely different
>> portlets, which normally only exists on two different psml's. But once
>> in a while, the content of portlet B is shown on page A, instead of
>> portlet A.
>>
>> With regards,
>>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> Iprofs BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> www.iprofs.nl
>>
>>
>>
>> On Mon, Jun 29, 2009 at 12:16 PM, Woonsan Ko<w.ko@onehippo.com> wrote:
>>> Hi Nick,
>>>
>>> If a portlet class or its ancestor class has member variables to store
>>> some states and the member variables are set on requests, it would
>>> cause a thread-safety problem.
>>>
>>> Just two cents,
>>>
>>> Woonsan
>>>
>>>
>>> On Mon, Jun 29, 2009 at 11:56 AM, Nick Stolwijk<nick.stolwijk@gmail.com> wrote:
>>>> We have the convention for fragment id's like
>>>> <projectname>-<page-name>-<page-part> so no double fragment id's (I
>>>> have just double checked them). Also the portlet cache is disabled,
>>>> afaik.
>>>>
>>>> We'll keep investigating the issue. If someone has any additional
>>>> tips, they're welcome.
>>>>
>>>> With regards,
>>>>
>>>> Nick Stolwijk
>>>> ~Java Developer~
>>>>
>>>> Iprofs BV.
>>>> Claus Sluterweg 125
>>>> 2012 WS Haarlem
>>>> www.iprofs.nl
>>>>
>>>>
>>>>
>>>> On Mon, Jun 29, 2009 at 11:45 AM, Ate Douma<a.douma@onehippo.com> wrote:
>>>>> Nick Stolwijk wrote:
>>>>>> A little clarification about what we are seeing.
>>>>>>
>>>>>> We have psml A with some portlets and psml B with some portlets. It
>>>>>> seems that, under load, sometimes a request which retrieves page A
>>>>>> gets the content page A with one portlet not on page A but on page B
>>>>>> and the portlet that is supposed to be there, isn't there. It even
>>>>>> seems that this content is from another request.
>>>>>>
>>>>>> This is just a wild guess, but it seems that the portlet handling
>>>>>> intermingles outputstreams between requests.
>>>>>>
>>>>>> Is this a known issue?
>>>>> No, not really, except possibly when the following (incorrect) configuration
>>>>> is used:
>>>>> - if portletA (on Page A) has the same fragment id as portlet B (on Page B)
>>>>> - portlet caching is enabled for one or both these portlets (e.g. content
>>>>> cache managed by the *portal*)
>>>>>
>>>>> If the above is the case, the portal might deliver the content for the
>>>>> portlet directly from its internal cache which is keyed off the fragment id.
>>>>> Thus: if you have enabled portlet caching you should *not* reuse its
>>>>> fragment id across psml pages.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Ate
>>>>>
>>>>>> Nick Stolwijk
>>>>>> ~Java Developer~
>>>>>>
>>>>>> Iprofs BV.
>>>>>> Claus Sluterweg 125
>>>>>> 2012 WS Haarlem
>>>>>> www.iprofs.nl
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2009/6/26 Mike Duijvelaar <mduijvelaar@anwb.nl>:
>>>>>>> Hello,
>>>>>>>
>>>>>>> Has anyone seen the next problem:
>>>>>>>
>>>>>>> If you run a high loadtest in portal, that sometimes porlets are mingled.
>>>>>>> The titel of the page is e.g. portlet A(psml), but content is from portlet
>>>>>>> B(psml).
>>>>>>>
>>>>>>> Met vriendelijke groet,
>>>>>>> Mike Duijvelaar
>>>>>>>
>>>>>>> ANWB Online Beheer
>>>>>>>
>>>>>>> Gebouw B midden; B330
>>>>>>> Wassenaarseweg 220
>>>>>>> Den Haag
>>>>>>>
>>>>>>> Tel: (intern) toestel 7325/7301
>>>>>>> Mob: 06-50233023
>>>>>>>
>>>>>>> **********************************************************************************************
>>>>>>> Disclaimer
>>>>>>>
>>>>>>> E-mail wordt door ANWB niet gebruikt voor het aangaan van externe
>>>>>>> verplichtingen.
>>>>>>> Deze e-mail is uitsluitend bestemd voor geadresseerde(n). Indien deze
>>>>>>> e-mail
>>>>>>> onverhoopt niet voor u is bestemd dan verzoeken wij u vriendelijk contact
>>>>>>> op te
>>>>>>> nemen met de afzender en daarna het bericht te vernietigen. Deze e-mail
>>>>>>> mag niet
>>>>>>> worden doorgestuurd, openbaar gemaakt of verveelvoudigd worden zonder de
>>>>>>> toestemming van de afzender.
>>>>>>> ANWB betracht grote zorgvuldigheid bij het verzenden van e-mails. ANWB
>>>>>>> kan
>>>>>>> echter niet garanderen dat deze e-mail juist, volledig, tijdig en
>>>>>>> virusvrij wordt
>>>>>>> overgebracht. In een dergelijk geval is ANWB op geen enkele wijze
>>>>>>> aansprakelijk
>>>>>>> voor enige schade, direct dan wel indirect, in welke vorm dan ook.
>>>>>>>
>>>>>>> ANWB B.V.
>>>>>>>
>>>>>>> **********************************************************************************************
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Hippoportal-dev mailing list
>>>>>>> Hippoportal-dev@lists.hippo.nl
>>>>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Hippoportal-dev mailing list
>>>>>> Hippoportal-dev@lists.hippo.nl
>>>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>>
>>>>> --
>>>>> a.douma@onehippo.com  www.onehippo.com
>>>>>
>>>>> Amsterdam     - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>>>>> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100
>>>>> +1(877) 41-HIPPO
>>>>>
>>>>> _______________________________________________
>>>>> Hippoportal-dev mailing list
>>>>> Hippoportal-dev@lists.hippo.nl
>>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>>
>>>> _______________________________________________
>>>> Hippoportal-dev mailing list
>>>> Hippoportal-dev@lists.hippo.nl
>>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>>
>>>
>>>
>>> --
>>> w.ko@onehippo.com     www.onehippo.com
>>> EUROPE ? AMSTERDAM - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
>>> NORTH AMERICA ? SAN FRANCISCO - Hippo USA Inc. 185 H Street, Suite B
>>> Petaluma CA 94952 +1 (877) 414-4776
>>> _______________________________________________
>>> Hippoportal-dev mailing list
>>> Hippoportal-dev@lists.hippo.nl
>>> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev
>>>
> _______________________________________________
> Hippoportal-dev mailing list
> Hippoportal-dev@lists.hippo.nl
> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev


-- 
a.douma@onehippo.com  www.onehippo.com

Amsterdam     - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-5100 +1(877) 41-HIPPO