tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joel <j...@physics.tamu.edu>
Subject Re: tomcat session mixing
Date Mon, 17 Jun 2013 22:14:31 GMT
 

Hi Chris, 

First, my apologies. Much of the terminology is
unfamiliar to me here. I hope that I've managed to fully answer your
questions. 

The "server calls" are all rmi calls on java-based servers
on the same machine. There are no separate threads directly in the .jsp
pages. 

The userToken has a few variables (userID, userName, etc) and a
bunch of rmi interface methods. It doesn't directly use a tomcat
request,response, etc. Another way of putting it is that all of these
methods could be called equally well from the command line. Here's a
typical method: 

 public UserToken getUserToken(String userName) 

I
think a few of the server calls do have
System.out.println/System.err.println commands that do end up in the
catalina.out file. 

Joel 

On 2013-06-17 16:59, Christopher Schultz
wrote: 

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
>
Joel,
> 
> On 6/17/13 5:12 PM, joel wrote:
> 
>> Thanks for the help.
I'm not an expert with tomcat management, There are no servlets. I don't
know what Threadlocal, doGet/doPost/etc are, so presumably haven't used
them.
> 
> Eventually, everything is a servlet (or maybe a Filter in
certain
> cases). Even if your code does not include doGet/doPost, they
are
> likely being used under the covers.
> 
>> No references are kept
to request,response, session, or stream objects. At login, a user
session token is stored: session.setAttribute("userToken", userToken);
This token also contains wrapper methods to make server calls.
> 
> What
does that mean "make server calls"? Do you make those calls in
>
separate threads or anything like that?

 

Links:
------
[1]
http://gpgtools.org
[2] http://www.enigmail.net/
[3]
mailto:users-unsubscribe@tomcat.apache.org
[4]
mailto:users-help@tomcat.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message