tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Owens" <>
Subject RE: Authentication problems with tomcat clustering.
Date Mon, 04 Apr 2005 17:25:12 GMT
Are your servlets in the /servlet/ directory?  Or some other name?
You have only redirected /servet/*, /*.vm and

You may want to try just /therestaurant/*

And you may want to do this

JkMount / therestaurant /* loadbalancer

On my problem:
So I did some more investigation, and have found that I am
authenticating against one tomcat, and then being balanced over to the
other tomcat.  This is presumably happening before the session is
replicated... still looking for a solution... perhaps synchronous
replication...  I am also trying to find the 1.2.10 mod_jk for my
system. (linux)

-----Original Message-----
From: Vaneet Sharma [] 
Sent: Monday, April 04, 2005 10:09 AM
To: Tomcat Users List
Subject: RE: Authentication problems with tomcat clustering.

Your Apache and Tomcat configuration is exactly like me..
However today I installed connector mod_jk.. Connector 1.2.10...

And ... Though apache and tomcat are talking .. I cannot run my servlet
Pls have a look below to see the configuration

The connector is not loading my servlets?
I am writing down my httpd.conf and

LoadModule jk_module modules/

<ifModule mod_jk.c>
JkWorkersFile /usr/local/jakarta-tomcat-5.5.4/conf/
JkLogFile /etc/httpd/logs/mod_jk.log
JkLogLevel info
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" JkAutoAlias
JkShmFile /etc/httpd/logs/mod_jk.shm 
JkMount /servlet/* ajp13Worker
JkMount /*.vm ajp13Worker
JkMount /therestaurant/servlet/ControllerServlet/* ajp13Worker


    DocumentRoot /usr/local/jakarta-tomcat-x.x.x/webapps/therestaurant

And below is file worker.ajp13Worker.port=8009
worker.ajp13Worker.cachesize=10 worker.ajp13Worker.cache_timeout=600

-----Original Message-----
From: David Owens [] 
Sent: Monday, April 04, 2005 6:04 PM
Subject: Authentication problems with tomcat clustering.

I have setup load balancing and clustering between two Tomcat 5.5.7
instances and Apache 2.0.50 with mod_jk.  Almost everything works great.
I can fail back and forth between the 2 tomcat instances with no
trouble.  However, I am having problems with the form based
authentication.  I have an index.html file which redirects the user to a
secured resource.  When the user hits this file through Apache, it works
like normal, directing them to the login page.  However, when I attempt
to login I get "Invalid direct reference to form login page".  When I
look in the logs, I see the user is being authenticated, and the correct
roles are being found. If I continually try logging in, and hitting the
secure page, eventually I get in.  Then, if I bounce apache, the problem
starts again. If I login in the exact same manner directly against one
of the tomcat instances, everything works, and I continue to the secure
resource.  In addition, I have found that if I stop one tomcat instance,
I can login on the first try even when going through apache.  


It's worth noting, once I get successfully logged in once through apache
(after many tries), I can logout/in repeatedly with no problem.  Once I
bounce apache,

the problem starts again.


I think something strange is happening with the login stuff when tomcat
is clustered...  Maybe I'm logging into 1 tomcat successfully, but being
load balanced over

to the other one, and the session has not been completely replicated


Any one else out there have this issue, or have any ideas?


Thanks in advance!



Vaneet Sharma
executive manager	
iDeasTank Limited	
an iwg business
dolphins' court po 388
valletta, m-malta/europe
mobile:	 +356 9943 8263
fax:	 +356 9952 8888
phone:	 +356 9942 8888
call me on - my ID is CALLVANEET

Want a signature like this? -\signature

iwg is a global e-mobile company creating, building and growing new
businesses.  iwg founders are pioneers in creating multi-billion dollar
mobile and Internet businesses in Europe, Asia and the US.

Privileged/Confidential Information may be contained in this message.
If you are not the addressee indicated in this message (or responsible
for delivery of the message to such person), you may not copy or deliver
this message to anyone. In such case, you should destroy this message
and kindly notify the sender by reply email.

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message