Hi James,
This message (and the following one) are marked as sent 5/9, but were only received by my mail server last night. Just want to make sure that's not a surprise to you...
Comments inline...
James Black wrote:
Sure, I was just suggesting the 1-minute timeout for whoever verifies this bug, so that they could reproduce it quickly. I should have made that clear.Rich Feit (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/BEEHIVE-623?page=comments#action_64788 ]
>Rich Feit commented on BEEHIVE-623: >-----------------------------------
>OK, I'm able to reproduce this in the following manner:
> - Hit a page flow.
> - Hit a nested page flow (so that now the original page flow is on the nesting stack).
> - Redeploy the webapp, or start/stop Tomcat.
> - Wait for the session to expire.
>To make the session expire quickly, add this entry in web.xml, after the last servlet-mapping:
> <session-config> > <session-timeout>1</session-timeout> > </session-config>
This would be a problem, as the end-user would need to log in much more often than they should. I am thinking that 30-45 mins will be the time for timeouts.
I actually resolved this bug a few days ago -- hopefully you can't reproduce it anymore, as long as you've updated beehive-netui-*.jar in WEB-INF/lib? Let me know...If they log in and get out of the nested page flow section, then would that solve my problem?
It may just mean that I have to design without using nested page flows.
Rich
-- Corruptisima republica plurimae leges. [The more corrupt a republic, the more laws.] Tacitus from Annals III, 116AD Blogs: http://jamesruminations.blogspot.com
