Hi Yes. I do see the problem.
The simple answer would again be to raise the timeut periode. Other workarounds could be. - Users work in a frameset (portal) where both the Domino and the Tomcat applications a reached from. A very tiny frame could refresh a page on the Domino or Tomcat servers and keep the sessions alive. - Don't use Domino session based authentication (less secure) - use lotus.domino.Session.getSessionToken() to update the Domino session cookie in the browser regards Jesper B. Ki�r http://www.jezzper.dk [EMAIL PROTECTED] wrote on 11-06-2003 12:34:22: > Consider the following scenario: > > The user logs in our web application (which runs on both Tomcat and > Domino) using the Domino authentication services. Then a Domino > HttpSession is created. Then the user clicks a link which redirects the > user to the Tomcat application. Then the user clicks around in the > 'tomcat-part' of the application for about an hour. (The Domino session > then is timed out). The he clicks a link which redirects him back to the > 'domino-part' of the application. > The user is presented a login-screen. > > This seems a bit odd, because he wasn't inactive for the past hour. (He > was actively using the 'tomcat-part' of the application. The user doesn't > know he is on a different server). So why should he log in again? > > See my problem? > > Many thanks, > > Harm de Laat > Informatiefabriek > The Netherlands > > > > > > "Jesper B. Ki�r" <[EMAIL PROTECTED]> > 06/11/2003 12:22 PM > Please respond to > "Tomcat Users List" <[EMAIL PROTECTED]> > > > To > "Tomcat Users List" <[EMAIL PROTECTED]> > cc > > Subject > Re: tomcat & domino server > > > > > > > Hi > > I was wonderring why is this a big problem? > > When your session is timed out in Domino you are redirected to the login > page and thereafter to the page originaly requested. > > You could rise the the default time out periode from 30 minuttes on the > Domino server. This would help the users, but of course lower the security > > level. > > regards > Jesper B. Ki�r > > > Jezzper Consulting > http://www.jezzper.dk > > > > [EMAIL PROTECTED] wrote on 11-06-2003 11:04:56: > > > Hi all, > > > > In our production environment we are (slowly) switching from the Lotus > > Domino Webserver to Tomcat (and JBoss). > > But for now we have to use both because we can't switch all applications > > > > at once. > > > > Therefore some of our webpages (applications) use both the Domino > > webserver and the Tomcat server. > > Unfortunatly we have some problems with session time-outs. > > > > For instance, when a user logs in our webapplication (we use Domino > > authentication) a Lotus Domino HttpSession is created. > > Then when a user clicks a link in the application the user is sent to a > > Tomcat application. > > The user then stays in the tomcat application for more than a hour. Then > > > > he cliks another link which sends the user back to the Domino server. > > But then, Ooops... The session of the Domino server is timed-out! > > > > This ofcourse goes both ways.... (The tomcat session could time out, > while > > the user is busy in the Domino web-application). > > > > We have absolutely no idea on how to fix this problem. > > > > We have searched the net for days and tried a lot, but nothing seems to > > work. > > > > Maybe some of you guys encountered the same problem? > > > > Can you help? > > > > Thanks, > > > > Harm de Laat > > Informatiefabriek > > The Netherlands > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
