[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster

[Prabhat Jha (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1879?page=comments#action_12417888 ] 
            
Prabhat Jha commented on JBPORTAL-1879:
---------------------------------------

Details at the forum. Resolution is to update cache version. jboss cache version 1.4.1.SP8 (http://repository.jboss.com/jboss/cache/1.4.1.SP8.patch02-brew

> problem accessing a portlet deployed in a cluster
> -------------------------------------------------
>
>                 Key: JBPORTAL-1879
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.4 Final
>         Environment: Hibernate Version:  3.2.4.sp1
> JBoss Cache Version:  1.4.1.SP5
> JBoss AS: 4.2.2.GA
>            Reporter: Prabhat Jha
>         Assigned To: Prabhat Jha
>             Fix For: 2.7 Final
>
>         Attachments: cluster-jam.zip
>
>
> This is something I had noticed in my scalability test but at that time I thought I may have done something stupid and later, I saw a similar note in support case.
> I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is predeployed before servers are started. If I start both servers simultaneously and access http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with "The requested resource () is not available". I am able to access the page if I hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) .
> What is more interesting is that when I start servers one by one and access portal page as server comes online i.e. start second server when first one has already started and page has been accessed, then I can access the NullPortletPage in both servers. Since there is a work around, let's fix this by 2.6.5 release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira