You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jon Yeargers <jo...@bme.ogi.edu> on 2006/08/18 18:03:58 UTC

Firefox / cookies / sessions - tomcat problem

Issue: Im running into problems with a tomcat based application that 
uses the JNDI connection pooling mechanism that ships with tomcat. It 
appears that my session bits are being kept 'alive' by any running 
instances of firefox even after the browser running my app is closed.

Situation: I have a session bean that handles the connection pool. Im 
handling several DBs in it so there are corresponding 'getConnection' 
for each. There are several web-apps in this installation that use this 
session bean (compiled into a .jar with some other common functions).

What happens: I run the app (in firefox) ('A'). All is well. I open 
another instance of firefox ('B'). I close the instance of firefox with 
the app. Browse a bit in the remaining instance. Then I run the app 
again('C'). I get exceptions from any attempt to get DB connection(s). 
Debugging information shows that the constructor in the .jar isn't being 
called as the second process is getting the session object (now 'stale') 
from Firefox ('B').

Question: is there some way to force the app to create a 'fresh' 
instance of a session object? Or am I highly confused on this issue?

Installation ver: tomcat 5.5.9 on Redhat Enterprise. Firefox 1.5


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Firefox / cookies / sessions - tomcat problem

Posted by David Smith <dn...@cornell.edu>.
Firefox 'B' is a new window on the original Firefox 'A' (same 
application instance).  As such they share the same session on your 
webapp.  Your code should check to be sure the session is still valid 
(request.isRequestedSessionIdValid()).

On a design note, you should not be maintaining open connections in 
session.  Open, do your business, and close them immediately within the 
life cycle of a single request.  Pooling will take care of maintaining 
the connections for you.

--David

Jon Yeargers wrote:

> Issue: Im running into problems with a tomcat based application that 
> uses the JNDI connection pooling mechanism that ships with tomcat. It 
> appears that my session bits are being kept 'alive' by any running 
> instances of firefox even after the browser running my app is closed.
>
> Situation: I have a session bean that handles the connection pool. Im 
> handling several DBs in it so there are corresponding 'getConnection' 
> for each. There are several web-apps in this installation that use 
> this session bean (compiled into a .jar with some other common 
> functions).
>
> What happens: I run the app (in firefox) ('A'). All is well. I open 
> another instance of firefox ('B'). I close the instance of firefox 
> with the app. Browse a bit in the remaining instance. Then I run the 
> app again('C'). I get exceptions from any attempt to get DB 
> connection(s). Debugging information shows that the constructor in the 
> .jar isn't being called as the second process is getting the session 
> object (now 'stale') from Firefox ('B').
>
> Question: is there some way to force the app to create a 'fresh' 
> instance of a session object? Or am I highly confused on this issue?
>
> Installation ver: tomcat 5.5.9 on Redhat Enterprise. Firefox 1.5
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: NSIS Error during Installation

Posted by Mark Thomas <ma...@apache.org>.
Shyamal Mitra wrote:
> 
> Hi,
> 
> I am trying to install Tomcat 5.5.17 on my PC running Windows XP.
> I have downloaded the executable file from at least two sites. But
> I get the following error while trying to install:
> 
> NSIS Error

When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this  makes your new message appear as part
of the old thread. This makes it harder for other users to find
relevant information when searching the lists.

This is known as thread hijacking and is behaviour that is frowned
upon on this list. Frequent offenders will be removed from the list.
It should also be noted that many list subscribers automatically
ignore any messages that hijack another thread.

The correct procedure is to create a new message with a new subject.
This will start a new thread.

Mark
tomcat-user-owner
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


NSIS Error during Installation

Posted by Shyamal Mitra <mi...@cs.utexas.edu>.
Hi,

I am trying to install Tomcat 5.5.17 on my PC running Windows XP.
I have downloaded the executable file from at least two sites. But
I get the following error while trying to install:

NSIS Error

The installer you are trying to use is corrupted or incomplete.
This could be the result of a damaged disk, a failed download or a
virus.

You may want to contact the author of this installer to obtain a new copy.



Do let me know how I can resolve this problem? I have added JAVA_HOME
to the environment variables and I have JDK 1.5 installed on my machine.

Thanks for your help.

Regards,

Shyamal




---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org