You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2007/02/10 01:56:06 UTC

[jira] Created: (PLUTO-310) Session Timeout Test (Testsuite test # 10) fails, for Test Portlet 2 only

Session Timeout Test (Testsuite test # 10) fails, for Test Portlet 2 only
-------------------------------------------------------------------------

                 Key: PLUTO-310
                 URL: https://issues.apache.org/jira/browse/PLUTO-310
             Project: Pluto
          Issue Type: Bug
    Affects Versions: 1.1.0-beta2, Current CVS
         Environment: RC candidate 504324 https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0
            Reporter: Elliot Metsger
            Priority: Minor


SessionTimeoutTest fails - 15.6 in test portlet 2 only.
  	 PLT 15.6 - checkSessionInvalidated
	Ensure portlet session is invalidated after the max inactive interval.
PortletSession should have expired and have been invalidated, but is still available. Make sure that other portlets did not create a new portlet session.


The session timeout test in portlet 1 always works.  The session timeout test in portlet 2 never works.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (PLUTO-310) Session Timeout Test (Testsuite test # 10) fails, for Test Portlet 2 only

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David DeWolf updated PLUTO-310:
-------------------------------

    Fix Version/s: 1.1.1

Since this seems to be an issue with the test instead of with the feature, we'll postpone until 1.1.1.

> Session Timeout Test (Testsuite test # 10) fails, for Test Portlet 2 only
> -------------------------------------------------------------------------
>
>                 Key: PLUTO-310
>                 URL: https://issues.apache.org/jira/browse/PLUTO-310
>             Project: Pluto
>          Issue Type: Bug
>    Affects Versions: Current CVS, 1.1.0-beta2
>         Environment: RC candidate 504324 https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0
>            Reporter: Elliot Metsger
>            Priority: Minor
>             Fix For: 1.1.1
>
>
> SessionTimeoutTest fails - 15.6 in test portlet 2 only.
>   	 PLT 15.6 - checkSessionInvalidated
> 	Ensure portlet session is invalidated after the max inactive interval.
> PortletSession should have expired and have been invalidated, but is still available. Make sure that other portlets did not create a new portlet session.
> The session timeout test in portlet 1 always works.  The session timeout test in portlet 2 never works.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (PLUTO-310) Session Timeout Test (Testsuite test # 10) fails, for Test Portlet 2 only

Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PLUTO-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David DeWolf resolved PLUTO-310.
--------------------------------

    Resolution: Fixed
      Assignee: David DeWolf

forcing it to maximize on test.

> Session Timeout Test (Testsuite test # 10) fails, for Test Portlet 2 only
> -------------------------------------------------------------------------
>
>                 Key: PLUTO-310
>                 URL: https://issues.apache.org/jira/browse/PLUTO-310
>             Project: Pluto
>          Issue Type: Bug
>    Affects Versions: Current CVS, 1.1.0-beta2
>         Environment: RC candidate 504324 https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0
>            Reporter: Elliot Metsger
>         Assigned To: David DeWolf
>            Priority: Minor
>             Fix For: 1.1.1
>
>
> SessionTimeoutTest fails - 15.6 in test portlet 2 only.
>   	 PLT 15.6 - checkSessionInvalidated
> 	Ensure portlet session is invalidated after the max inactive interval.
> PortletSession should have expired and have been invalidated, but is still available. Make sure that other portlets did not create a new portlet session.
> The session timeout test in portlet 1 always works.  The session timeout test in portlet 2 never works.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.