Apache mod_rewrite + Tomcat clustering/ load balancing.

[Sunkersett, Jeevan \(Cognizant\)]

Hi,



I hv clustered 2 Tomcat (version 5.0.18) instances on 2 physically
different machines A and B.

Individually accessible as

http://machineA:8080   and
http://machineB:8080 



I have Apache 2.0.54 installed on machine A and following the tomcat doc


http://jakarta.apache.org/tomcat/tomcat-5.0-doc/balancer-howto.html



I am trying to use Apache mod_rewrite to load balance/
failover between my 2 tomcat instances.



As per the doc modified the  element in server.xml
to include the jvmRoute attribute

Configuring Apache was a headache.

The documentation assumes the reader is an expert with Apache.

It is not completely accurate. The reader cannot use it as is.

For instance it talks of creating balancer.conf but uses servers.conf in
http.



Anyways I discovered it and created a balancing.conf for
mod_rewrite as explained.

   

Edited apache's httpd.conf as given in the tomcat doc.

And with both tomcat instances working browsed
to


http://localhost/servlets-examples/servlet/RequestInfoExample

But it did not work. Error log gave:

File does not exist:
proxy:http://machineA:8080/servlets-examples/servlet/RequestInfoExample



   But I could get the expected page when I replaced [P, L]
in the RewriteRule for  with only [L]

   

The funny thing however is I browse to


http://localhost/servlets-examples/servlet/RequestInfoExample

but that later automatically changes to either


http://machineA:8080/servlets-examples/servlet/RequestInfoExample or


http://machineB:8080/servlets-examples/servlet/RequestInfoExample

depending upon which Tomcat instance served my request.



Any clues as to why the URL in the browser changes?



PS: My entries in httpd.conf

   RewriteMap SERVERS rnd:<>

RewriteEngine On
RewriteCond "%{HTTP_COOKIE}"
"(^|;\s*)jsessionid=\w*\.(\w+)($|;)"
RewriteRule "(.*)"
"http://${SERVERS:%2}%{REQUEST_URI}";  [P,L]
RewriteRule "^.*;jsessionid=\w*\.(\w+)($|;)"
"http://${SERVERS:$1}%{REQUEST_URI}";  [P,L]
RewriteRule "(.*)"
"http://${SERVERS:ALL}%{REQUEST_URI}"; [P,L]




<< I had to replace [P,L] with [L] to make it work>>

   

rgds,

G1







This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply 
e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing 
or copying of this email or any action taken in reliance on this e-mail is 
strictly
prohibited and may be unlawful.

  Visit us at http://www.cognizant.com

Re: Tomcat clustering & load balancing

[Lintang JP]

Hi Jeevan,

> 1. Am I missing something? Load balancing?
Lot of ways to do load balancing : 
a. U can use balancer apps, it's bundled on tomcat sample
b. U can use apache with mod_jk

So, yes, you browse to some other URL. For example, if U run the balancer 
apps from tomcat, U should be redirected to some URL.

Clustering and load balancing is two separated different things. A request, 
usually goes into the load balancer first, and after that, the load balancer 
redirect it to the "real" tomcat, it can be within the same machine but 
different port, or it can be to another machine.
The "Real" tomcat, it can be clustered, or stand alone. If it's clustered, 
then those tomcat's are sharing their "sesion state", means that if your 
request is handled by tomcatA and then suddenly tomcatA is dead, then the 
load balancer will redirect your request to tomcatB, tomcatB knows, what has 
been done with your request by tomcatA, and will continue to process your 
request.

> 2. But how to configure load balancing?

Google ? :D 
I have written my documentation with load balancing and clustering,but in 
Indonesian language, hehehe :D sorry

On 8/3/05, Sunkersett, Jeevan (Cognizant) <[EMAIL PROTECTED]> 
wrote:
> 
> 
> Hi,
> 
> 
> 
> I am experimenting with Tomcat clustering
> 
> I easily implemented a tomcat cluster un-commenting the 
> element in server.xml
> 
> 
> 
> I now have 2 tomcat instances (on 2 physically different boxes) machineA
> and machineB
> 
> I noted they can keep track of each other and get notified the other is
> down - for e.g. when I pull out the network cord.
> 
> 
> 
> With clustering enabled I expect my request sent to say machineA
> (http://machineA:8080 <http://machinea:8080/> ) to be served by the
> other tomcat instance.
> 
> 
> 
> But this does not happen.
> 
> 
> 
> 1. Am I missing something? Load balancing?
> 
> 2. But how to configure load balancing?
> 
> In non-clustered environment I would browse to
> http://machineA:8080 <http://machinea:8080/> or http://machineB:8080
> <http://machineb:8080/> (The machine name is specified in the url
> EXPLICITLY.)
> 
> With load balancing app should I browse to some other URL?
> 
> 
> 
> 3. How and who will route the request?
> 
> 4. Do I need to run my own specialized version of the load balancing app
> on a third tomcat instance?
> 
> 5. What if the third tomcat instance on which the load balancing app is
> running comes down?
> 
> 
> 
> rgds,
> 
> G1
> 
> 
> 
> 
> 
> This e-mail and any files transmitted with it are for the sole use of the 
> intended recipient(s) and may contain confidential and privileged 
> information.
> If you are not the intended recipient, please contact the sender by reply 
> e-mail and destroy all copies of the original message.
> Any unauthorised review, use, disclosure, dissemination, forwarding, 
> printing or copying of this email or any action taken in reliance on this 
> e-mail is strictly
> prohibited and may be unlawful.
> 
> Visit us at http://www.cognizant.com
> 



-- 
---
http://www.psychotazkia.or.id

Tomcat clustering & load balancing

[Sunkersett, Jeevan \(Cognizant\)]

Hi,



I am experimenting with Tomcat clustering

I easily implemented a tomcat cluster un-commenting the 
element in server.xml



I now have 2 tomcat instances (on 2 physically different boxes) machineA
and machineB

I noted they can keep track of each other and get notified the other is
down - for e.g. when I pull out the network cord.



With clustering enabled I expect my request sent to say machineA
(http://machineA:8080 <http://machinea:8080/> ) to be served by the
other tomcat instance.



But this does not happen.



1. Am I missing something? Load balancing?

2. But how to configure load balancing?

In non-clustered environment I would browse to
http://machineA:8080 <http://machinea:8080/>  or http://machineB:8080
<http://machineb:8080/>  (The machine name is specified in the url
EXPLICITLY.)

With load balancing app should I browse to some other URL?



3. How and who will route the request?

4. Do I need to run my own specialized version of the load balancing app
on a third tomcat instance?

5. What if the third tomcat instance on which the load balancing app is
running comes down?



rgds,

G1





This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply 
e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing 
or copying of this email or any action taken in reliance on this e-mail is 
strictly
prohibited and may be unlawful.

  Visit us at http://www.cognizant.com

Re: Tomcat Clustering - Replicated Sessions

[Peter Rossbach]

Hey,
you have install my cluster patch for 5.5.9?
http://issues.apache.org/bugzilla/show_bug.cgi?id=34389
I  used very heavy  the new fastasyncqueue mode without memory problems
Every minute the sessions controlled for timeout. Look with an JMX 
Console that the manager active session count is reduced.
Every expire message are transfered to all backup nodes.

Peter
Laura Haverkamp schrieb:
According to the Tomcat (5.5.9) documentation after a sessions has
reached a certian period of inactivity it expires.  However my
question is when is this expired session marked by the JVM for garbage
collection.
The reason I ask is that our application has an interesting problem. 
If we start up a single server (configured for a cluster) and have the
application run memory looks good, CPU is good, response time is good.

However when we start up the 2nd clustered instance after a day or two
both servers start showing up with OutOfMemory errors.  The only new
item introduced is that we are now replicating sessions between the
applications.  We changed the replication mode to asynchronous after
having performance problems using pooled.
Thanks.
-
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]

Tomcat Clustering - Replicated Sessions

[Laura Haverkamp]

According to the Tomcat (5.5.9) documentation after a sessions has
reached a certian period of inactivity it expires.  However my
question is when is this expired session marked by the JVM for garbage
collection.

The reason I ask is that our application has an interesting problem. 
If we start up a single server (configured for a cluster) and have the
application run memory looks good, CPU is good, response time is good.

However when we start up the 2nd clustered instance after a day or two
both servers start showing up with OutOfMemory errors.  The only new
item introduced is that we are now replicating sessions between the
applications.  We changed the replication mode to asynchronous after
having performance problems using pooled.

Thanks.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: tomcat clustering

[Joshua Szmajda]

Awesome!
I think though since I need this functionality now, I might go with
JGroups' DistributedHashtable system. It's basically what I need right
out of the box.

Thanks, and good luck! I'll be looking forward to that functionality.

-Josh

Peter Rossbach wrote:

> With the next release I hope we support those handlings context
> attribute replication handling.
> We start a discussion at this list ( last three days).
>
> Topic:
> http://marc.theaimsgroup.com/?t=11141745513&r=1&w=2
>
> Peter
>
>
>
>
> Joshua Szmajda schrieb:
>
>> Hey all,
>>
>> Is there a way to get the cluster system to replicate ServletContext
>> scope variables between cluster members? If not, is there a good guide
>> to writing Multicast sockets somewhere?
>>
>> Thanks alot!
>> -Josh
>>
>> -
>> 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]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: tomcat clustering

[Peter Rossbach]

With the next release I hope we support those handlings context 
attribute replication handling.
We start a discussion at this list ( last three days).

Topic:
http://marc.theaimsgroup.com/?t=11141745513&r=1&w=2
Peter

Joshua Szmajda schrieb:
Hey all,
Is there a way to get the cluster system to replicate ServletContext
scope variables between cluster members? If not, is there a good guide
to writing Multicast sockets somewhere?
Thanks alot!
-Josh
-
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]

tomcat clustering

[Joshua Szmajda]

Hey all,

Is there a way to get the cluster system to replicate ServletContext
scope variables between cluster members? If not, is there a good guide
to writing Multicast sockets somewhere?

Thanks alot!
-Josh

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to use Database persistence for tomcat clustering?

[Filip Hanik - Dev Lists]

Configure the PersistenceManager as your session manager
hang zhao wrote:
Hi, everyone
I am trying some configuration with my small tomcat
cluster (2 tomcats, 1 apache, connected with mod_jk2
as load balancer).
The problem is that I want to use a shared database
(Mysql) to do session replication instead of in-memory
session replication. 

But to the best of my knowledge, you seems can not
make session level fail over to work with shared
database  session replication. The changed session
data is not sent to database immediately.
In another word, how can I configure so that when I
change session data, it is sent to database
immediately. And so when some nodes dies, the other
node can pick up the unfinished request silently
without session data loss.
Thanks in advance
Hang 

		
__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

-
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]

How to use Database persistence for tomcat clustering?

[hang zhao]

Hi, everyone

I am trying some configuration with my small tomcat
cluster (2 tomcats, 1 apache, connected with mod_jk2
as load balancer).

The problem is that I want to use a shared database
(Mysql) to do session replication instead of in-memory
session replication. 

But to the best of my knowledge, you seems can not
make session level fail over to work with shared
database  session replication. The changed session
data is not sent to database immediately.

In another word, how can I configure so that when I
change session data, it is sent to database
immediately. And so when some nodes dies, the other
node can pick up the unfinished request silently
without session data loss.


Thanks in advance

Hang 



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Authentication problems with tomcat clustering.

[David Owens]

That was exactly it!  Thank you.  I had changed the configs, but had not
commented in that section.  All is well now.  Thank you very much!

|)ave

-Original Message-
From: David Rees [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 05, 2005 6:51 PM
To: Tomcat Users List
Subject: Re: Authentication problems with tomcat clustering.

On Apr 5, 2005 3:13 PM, David Owens <[EMAIL PROTECTED]> wrote:
> After further debug, I see this is happening because mod_jk is
> "ignoring" the sticky sessions, and continuing to lb back and forth.
> After looking at the mod_jk code, I see it is looking for something
> after the '.' character in the JSESSIONID to tell it where the session
> should stick.
> 
> How do I setup tomcat (or is it httpd) to provide this piece of
> information?

The name of your worker in the mod_jk config must match the value in
each Tomcat instance's server.xml.

For example (abbreviated configs) in tomcat-workers.properties:

worker.list=tomcat1,tomcat2

And in tomcat1's server.xml:


And in tomcat2's server.xml:


Hope this helps...

-Dave

-
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]

Re: Authentication problems with tomcat clustering.

[David Rees]

On Apr 5, 2005 3:13 PM, David Owens <[EMAIL PROTECTED]> wrote:
> After further debug, I see this is happening because mod_jk is
> "ignoring" the sticky sessions, and continuing to lb back and forth.
> After looking at the mod_jk code, I see it is looking for something
> after the '.' character in the JSESSIONID to tell it where the session
> should stick.
> 
> How do I setup tomcat (or is it httpd) to provide this piece of
> information?

The name of your worker in the mod_jk config must match the value in
each Tomcat instance's server.xml.

For example (abbreviated configs) in tomcat-workers.properties:

worker.list=tomcat1,tomcat2

And in tomcat1's server.xml:


And in tomcat2's server.xml:


Hope this helps...

-Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Authentication problems with tomcat clustering.

[David Owens]

After further debug, I see this is happening because mod_jk is
"ignoring" the sticky sessions, and continuing to lb back and forth.
After looking at the mod_jk code, I see it is looking for something
after the '.' character in the JSESSIONID to tell it where the session
should stick.  

How do I setup tomcat (or is it httpd) to provide this piece of
information?

Thanks!

|)ave

-Original Message-
From: David Owens 
Sent: Tuesday, April 05, 2005 7:11 AM
To: tomcat-user@jakarta.apache.org
Subject: RE: Authentication problems with tomcat clustering.

I have done some further testing and have found what I think the problem
is, but I still do not know the solution. What is happening is that the
first time I access the webapp through httpd, I am getting the first
tomcat server.  I then type in my username and password and hit submit.
I see in the logs of the first tomcat server log the authentication
happening successfully, however, I am then redirected to the second
tomcat server where my session is not available.

 

I am using a 'lb' type load balancer, and by default it has sticky
sessions, so I wonder why I am being balanced over to the other tomcat.
Is this, perhaps, a question for the mod_jk team?  Is there such a
mailing list?

 

|)ave

 

-Original Message-
From: David Owens 
Sent: Monday, April 04, 2005 10:04 AM
To: 'tomcat-user@jakarta.apache.org'
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
yet?

 

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

 

Thanks in advance!

 

|)ave


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Authentication problems with tomcat clustering.

[Vaneet Sharma]

I suggest u do step by step again
You will find the bug.

Start from basic . First run one ... And then try loadbalancer.. Later
on

Vaneet

-Original Message-
From: David Owens [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 05, 2005 3:11 PM
To: tomcat-user@jakarta.apache.org
Subject: RE: Authentication problems with tomcat clustering.


I have done some further testing and have found what I think the problem
is, but I still do not know the solution. What is happening is that the
first time I access the webapp through httpd, I am getting the first
tomcat server.  I then type in my username and password and hit submit.
I see in the logs of the first tomcat server log the authentication
happening successfully, however, I am then redirected to the second
tomcat server where my session is not available.

 

I am using a 'lb' type load balancer, and by default it has sticky
sessions, so I wonder why I am being balanced over to the other tomcat.
Is this, perhaps, a question for the mod_jk team?  Is there such a
mailing list?

 

|)ave

 

-Original Message-
From: David Owens 
Sent: Monday, April 04, 2005 10:04 AM
To: 'tomcat-user@jakarta.apache.org'
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
yet?

 

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

 

Thanks in advance!

 

|)ave



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

[EMAIL PROTECTED]
call me on www.skype.com - my ID is CALLVANEET

Want a signature like this? - www.plaxo.com\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.

www.iWG.info
www.countryprofiler.com/iWG
www.visitmalta.com
www.mfc.com.mt


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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Authentication problems with tomcat clustering.

[David Owens]

Okay, not quite right...

I first hit tomcat1 though httpd.  When I submit I see successful
authentication in the log for tomcat2.  I then get the "Invalid direct
reference..." message.

I am now using mod_jk 1.2.10.

Still no idea why this is happening...

|)ave

-Original Message-
From: David Owens 
Sent: Tuesday, April 05, 2005 7:11 AM
To: tomcat-user@jakarta.apache.org
Subject: RE: Authentication problems with tomcat clustering.

I have done some further testing and have found what I think the problem
is, but I still do not know the solution. What is happening is that the
first time I access the webapp through httpd, I am getting the first
tomcat server.  I then type in my username and password and hit submit.
I see in the logs of the first tomcat server log the authentication
happening successfully, however, I am then redirected to the second
tomcat server where my session is not available.

 

I am using a 'lb' type load balancer, and by default it has sticky
sessions, so I wonder why I am being balanced over to the other tomcat.
Is this, perhaps, a question for the mod_jk team?  Is there such a
mailing list?

 

|)ave

 

-Original Message-
From: David Owens 
Sent: Monday, April 04, 2005 10:04 AM
To: 'tomcat-user@jakarta.apache.org'
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
yet?

 

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

 

Thanks in advance!

 

|)ave


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Authentication problems with tomcat clustering.

[David Owens]

I have done some further testing and have found what I think the problem
is, but I still do not know the solution. What is happening is that the
first time I access the webapp through httpd, I am getting the first
tomcat server.  I then type in my username and password and hit submit.
I see in the logs of the first tomcat server log the authentication
happening successfully, however, I am then redirected to the second
tomcat server where my session is not available.

 

I am using a 'lb' type load balancer, and by default it has sticky
sessions, so I wonder why I am being balanced over to the other tomcat.
Is this, perhaps, a question for the mod_jk team?  Is there such a
mailing list?

 

|)ave

 

-Original Message-
From: David Owens 
Sent: Monday, April 04, 2005 10:04 AM
To: 'tomcat-user@jakarta.apache.org'
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
yet?

 

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

 

Thanks in advance!

 

|)ave

RE: Authentication problems with tomcat clustering.

[Vaneet Sharma]

You can find jakarta tomcat connector 1.2.10 
Apache website

http://jakarta.apache.org/tomcat/connectors-doc/

Have fun. 
Im still struggling with mod_jk :)

Need to change, restart and la la la

Vaneet

-Original Message-
From: David Owens [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 7:25 PM
To: Tomcat Users List
Subject: RE: Authentication problems with tomcat clustering.


Are your servlets in the /servlet/ directory?  Or some other name? You
have only redirected /servet/*, /*.vm and
/therestaurant/servlet/ControllerServlet/*

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 [mailto:[EMAIL PROTECTED] 
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
page. Pls have a look below to see the configuration

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

Httpd.conf
LoadModule jk_module modules/mod_jk.so


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


NameVirtualHost xxx.xxx.xxx.xxx:80


ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/jakarta-tomcat-x.x.x/webapps/therestaurant
ServerName www.therestaurant.name



And below is workers.properties file worker.ajp13Worker.port=8009
worker.ajp13Worker.host=xxx.xxx.xxx.xxx
worker.ajp13Worker.type=ajp13
worker.ajp13Worker.lbfactor=50
worker.ajp13Worker.cachesize=10 worker.ajp13Worker.cache_timeout=600


-Original Message-
From: David Owens [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 6:04 PM
To: tomcat-user@jakarta.apache.org
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
yet?

 

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

 

Thanks in advance!

 

|)ave



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

[EMAIL PROTECTED]
call me on www.skype.com - my ID is CALLVANEET

Want a signature like this? - www.plaxo.com\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.

www.iWG.info
www.countryprofiler.com/iWG
www.visitmalta.com
www.mfc.com.mt


Privileged/Confidential Information may be contained 

RE: Authentication problems with tomcat clustering.

[David Owens]

Are your servlets in the /servlet/ directory?  Or some other name?
You have only redirected /servet/*, /*.vm and
/therestaurant/servlet/ControllerServlet/*

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 [mailto:[EMAIL PROTECTED] 
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
page.
Pls have a look below to see the configuration

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

Httpd.conf
LoadModule jk_module modules/mod_jk.so


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


NameVirtualHost xxx.xxx.xxx.xxx:80


ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/jakarta-tomcat-x.x.x/webapps/therestaurant
ServerName www.therestaurant.name



And below is workers.properties file worker.ajp13Worker.port=8009
worker.ajp13Worker.host=xxx.xxx.xxx.xxx
worker.ajp13Worker.type=ajp13
worker.ajp13Worker.lbfactor=50
worker.ajp13Worker.cachesize=10 worker.ajp13Worker.cache_timeout=600


-Original Message-
From: David Owens [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 6:04 PM
To: tomcat-user@jakarta.apache.org
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
yet?

 

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

 

Thanks in advance!

 

|)ave



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

[EMAIL PROTECTED]
call me on www.skype.com - my ID is CALLVANEET

Want a signature like this? - www.plaxo.com\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.

www.iWG.info
www.countryprofiler.com/iWG
www.visitmalta.com
www.mfc.com.mt


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: [EMAIL PROTECTED]
For additional

RE: Authentication problems with tomcat clustering.

[Vaneet Sharma]

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
page.
Pls have a look below to see the configuration

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

Httpd.conf
LoadModule jk_module modules/mod_jk.so


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


NameVirtualHost xxx.xxx.xxx.xxx:80


ServerAdmin [EMAIL PROTECTED]
DocumentRoot /usr/local/jakarta-tomcat-x.x.x/webapps/therestaurant
ServerName www.therestaurant.name



And below is workers.properties file worker.ajp13Worker.port=8009
worker.ajp13Worker.host=xxx.xxx.xxx.xxx
worker.ajp13Worker.type=ajp13
worker.ajp13Worker.lbfactor=50
worker.ajp13Worker.cachesize=10 worker.ajp13Worker.cache_timeout=600


-Original Message-
From: David Owens [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 6:04 PM
To: tomcat-user@jakarta.apache.org
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
yet?

 

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

 

Thanks in advance!

 

|)ave



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

[EMAIL PROTECTED]
call me on www.skype.com - my ID is CALLVANEET

Want a signature like this? - www.plaxo.com\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.

www.iWG.info
www.countryprofiler.com/iWG
www.visitmalta.com
www.mfc.com.mt


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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Authentication problems with tomcat clustering.

[David Owens]

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
yet?

 

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

 

Thanks in advance!

 

|)ave

RE: Tomcat clustering and NotSerializableException

[Sng Wee Jim]

This will be a problem if the requests from the frames use the same Struts form.
Else it should be fine, since the framework will set the request into the 
Struts form for each request, so transient will still work.

- Jim



From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Wed 3/2/2005 12:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException



> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat clustering and NotSerializableException
>
> Indeed a reference to the HttpServletRequest is held in my Struts form
> (session-scope). The problem went away once I added transient to the
> attribute.

How do you handle the situation of having multiple concurrent requests on the 
same session?  This can easily happen with frames, users clicking refresh, etc.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.






The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorized. If you are not
an intended recipient, please notify the sender of this email
immediately. You should not copy, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.

http://www.capco.com/

RE: Tomcat clustering and NotSerializableException

[Caldarale, Charles R]

> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat clustering and NotSerializableException
> 
> Indeed a reference to the HttpServletRequest is held in my Struts form
> (session-scope). The problem went away once I added transient to the
> attribute.

How do you handle the situation of having multiple concurrent requests on the 
same session?  This can easily happen with frames, users clicking refresh, etc.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering and NotSerializableException

[Richard Mixon (qwest)]

If you specify "transient" on the HttpServletRequest property in your
form bean (this does not seem like "good" design) you must make
provisions when the form bean is "de-serialized" on the other end to
initialize the property.

See my post on this list for the subject titled "RE: SOLVED -
commons-logging logger instances - how to initialize in replicated
session objects"r fo the details of one way to do this.

HTH - Richard

-Original Message-
From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 01, 2005 7:47 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException



Thanks to all that replied.
Indeed a reference to the HttpServletRequest is held in my Struts form
(session-scope). The problem went away once I added transient to the
attribute.

My concern is when the session is replicated to other tomcat instances,
will a call to getRequest() always return null?


- Jim

-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Tuesday,
March 01, 2005 11:47 PM
To: Tomcat Users List
Subject: Re: Tomcat clustering and NotSerializableException

As Richard says, don't store your request in the session, not a good
idea.

Richard Mixon (qwest) wrote:

>CoyoteRequestFacade is the first element in the stack trace - it is not
>the session stored object that is causing the NotSerializableException.
>
>As I said in my prior posting, to resolve this issue you need to:
>
>1) Identify each object that you are explicitly storing in the session
>and make sure it directly or indirectly (through inheritance) specified
>that it implements Serializable.
>
>2) Follow the chain from each session object to other objects that it
>references and make sure they are ALL marked as serializable (again -
>either directly or indirectly)>
>
>That will fix your problem. These issues often do not come up until
>either you:
>1. Try and use session replication.
>2. Try to persist sessions to a datastore and access from a cluster.
>3. Try to persist sessions across a restart of Tomcat.
>
>Also, please just reply to the list - not to the list and to the
poster.
>
>HTH - Richard
>
>Sng Wee Jim wrote:
>  >
>>But the stacktrace says
>>
>>java.io.NotSerializableException:
>>org.apache.coyote.tomcat5.CoyoteRequestFacade
>>  at
>>java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>>  at
>>
>>>>
>java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1
3
>  >
>>32)
>>  at
>>
>>Since CoyoteRequestFacade is a tomcat class, I assume it has to be
>>fixed
>>by the tomcat team. Unless the actual object that is not Serializable
>>not CoyoteRequestFacade is available somewhere else...
>>
>>- Jim
>>
>>
>>
>>-Original Message-
>>From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Monday,
>>February 28, 2005 11:13 PM
>>To: Tomcat Users List
>>Subject: RE: Tomcat clustering and NotSerializableException
>>
>>As Matt said its probably your applications objects. When we switched
>>to
>>clustering I was surprised at how many of my session objects I needed
>>to
>>add serializable to. But it was easy work and quickl done.
>>
>>HTH - Richard
>>
>>Dale, Matt wrote:
>>>>
>>>I would guess that this means you have an object in your session that
>>>does not implement the serializable interface.
>>>
>>>Ta
>>>Matt
>>>
>>>-Original Message-
>>>From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
>>>Sent: 28 February 2005 09:21
>>>To: tomcat-user@jakarta.apache.org
>>>Subject: Tomcat clustering and NotSerializableException
>>>
>>>
>>>
>>>Hi,
>>>
>>>
>>>
>>>
>>>
>>>I am using Tomcat 5.0.28 on MS Win2k server.
>>>
>>>
>>>
>>>
>>>After I have uncommented the "Cluster" element in server.xml, I get
>>>the following exceptions on the tomcat console for some actions that
>>>are using displaytag.
>>>
>>>
>>>
>>>
>>>Is it a tomcat bug, since
>>>org.apache.coyote.tomcat5.CoyoteRequestFacade
>>>is involved?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>(DeltaManager.java:813)- Unable to serialize delta request
>>>
>>>java.io.NotSerializableException:
>>>org.apache.coyote.tomcat5.CoyoteRequestFacade
>>>
>>>at
>>>jav

RE: Tomcat clustering and NotSerializableException

[Sng Wee Jim]

Thanks to all that replied.

Indeed a reference to the HttpServletRequest is held in my Struts form
(session-scope). The problem went away once I added transient to the
attribute.

My concern is when the session is replicated to other tomcat instances,
will a call to getRequest() always return null?


- Jim

-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 01, 2005 11:47 PM
To: Tomcat Users List
Subject: Re: Tomcat clustering and NotSerializableException

As Richard says, don't store your request in the session, not a good
idea.

Richard Mixon (qwest) wrote:

>CoyoteRequestFacade is the first element in the stack trace - it is not
>the session stored object that is causing the NotSerializableException.
>
>As I said in my prior posting, to resolve this issue you need to:
>
>1) Identify each object that you are explicitly storing in the session
>and make sure it directly or indirectly (through inheritance) specified
>that it implements Serializable.
>
>2) Follow the chain from each session object to other objects that it
>references and make sure they are ALL marked as serializable (again -
>either directly or indirectly)>
>
>That will fix your problem. These issues often do not come up until
>either you:
>1. Try and use session replication.
>2. Try to persist sessions to a datastore and access from a cluster.
>3. Try to persist sessions across a restart of Tomcat.
>
>Also, please just reply to the list - not to the list and to the
poster.
>
>HTH - Richard
>
>Sng Wee Jim wrote:
> 
>
>>But the stacktrace says
>>
>>java.io.NotSerializableException:
>>org.apache.coyote.tomcat5.CoyoteRequestFacade
>>  at
>>java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>>  at
>>
>>   
>>
>java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1
3
> 
>
>>32)
>>  at
>>
>>Since CoyoteRequestFacade is a tomcat class, I assume it has to be
>>fixed
>>by the tomcat team. Unless the actual object that is not Serializable
>>not CoyoteRequestFacade is available somewhere else...
>>
>>- Jim
>>
>>
>>
>>-Original Message-
>>From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Monday,
>>February 28, 2005 11:13 PM
>>To: Tomcat Users List
>>Subject: RE: Tomcat clustering and NotSerializableException
>>
>>As Matt said its probably your applications objects. When we switched
>>to
>>clustering I was surprised at how many of my session objects I needed
>>to
>>add serializable to. But it was easy work and quickl done.
>>
>>HTH - Richard
>>
>>Dale, Matt wrote:
>>   
>>
>>>I would guess that this means you have an object in your session that
>>>does not implement the serializable interface.
>>>
>>>Ta
>>>Matt
>>>
>>>-Original Message-
>>>From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
>>>Sent: 28 February 2005 09:21
>>>To: tomcat-user@jakarta.apache.org
>>>Subject: Tomcat clustering and NotSerializableException
>>>
>>>
>>>
>>>Hi,
>>>
>>>
>>>
>>>
>>>
>>>I am using Tomcat 5.0.28 on MS Win2k server.
>>>
>>>
>>>
>>>
>>>After I have uncommented the "Cluster" element in server.xml, I get
>>>the following exceptions on the tomcat console for some actions that
>>>are using displaytag.
>>>
>>>
>>>
>>>
>>>Is it a tomcat bug, since
>>>org.apache.coyote.tomcat5.CoyoteRequestFacade
>>>is involved?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>(DeltaManager.java:813)- Unable to serialize delta request
>>>
>>>java.io.NotSerializableException:
>>>org.apache.coyote.tomcat5.CoyoteRequestFacade
>>>
>>>at
>>>java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>>>
>>>
>>>
>>>
>>>at
>>>java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>>>
>>> 
>>>
>>>>1332)
>>>>   
>>>>
>>>at
>>>java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>>>
>>>04)
>>>
>>>at
>>>java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>>>
>>>a:1247)
>>>
>>>at
>

Re: Tomcat clustering and NotSerializableException

[Filip Hanik - Dev Lists]

As Richard says, don't store your request in the session, not a good idea.
Richard Mixon (qwest) wrote:
CoyoteRequestFacade is the first element in the stack trace - it is not
the session stored object that is causing the NotSerializableException.
As I said in my prior posting, to resolve this issue you need to:
1) Identify each object that you are explicitly storing in the session
and make sure it directly or indirectly (through inheritance) specified
that it implements Serializable.
2) Follow the chain from each session object to other objects that it
references and make sure they are ALL marked as serializable (again -
either directly or indirectly)>
That will fix your problem. These issues often do not come up until
either you:
1. Try and use session replication.
2. Try to persist sessions to a datastore and access from a cluster.
3. Try to persist sessions across a restart of Tomcat.
Also, please just reply to the list - not to the list and to the poster.
HTH - Richard
Sng Wee Jim wrote:
 

But the stacktrace says
java.io.NotSerializableException:
org.apache.coyote.tomcat5.CoyoteRequestFacade
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
   

java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:13
 

32)
at
Since CoyoteRequestFacade is a tomcat class, I assume it has to be
fixed
by the tomcat team. Unless the actual object that is not Serializable
not CoyoteRequestFacade is available somewhere else...
- Jim

-Original Message-
From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Monday,
February 28, 2005 11:13 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException
As Matt said its probably your applications objects. When we switched
to
clustering I was surprised at how many of my session objects I needed
to
add serializable to. But it was easy work and quickl done.
HTH - Richard
Dale, Matt wrote:
   

I would guess that this means you have an object in your session that
does not implement the serializable interface.
Ta
Matt
-Original Message-
From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
Sent: 28 February 2005 09:21
To: tomcat-user@jakarta.apache.org
Subject: Tomcat clustering and NotSerializableException

Hi,


I am using Tomcat 5.0.28 on MS Win2k server.

After I have uncommented the "Cluster" element in server.xml, I get
the following exceptions on the tomcat console for some actions that
are using displaytag.

Is it a tomcat bug, since
org.apache.coyote.tomcat5.CoyoteRequestFacade
is involved?



(DeltaManager.java:813)- Unable to serialize delta request
java.io.NotSerializableException:
org.apache.coyote.tomcat5.CoyoteRequestFacade
   at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)

   at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
 

1332)
   

   at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
04)
   at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
a:1247)
   at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)

   at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
   at
org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
xternal(DeltaRequest.java:300)
   at
org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
equest.java:217)
   at
org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
eltaManager.java:393)
   at
org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
taManager.java:782)
   at
org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
lve.java:203)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
   at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:118)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:102)
   at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
   at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
   at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:104)
   at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:520)
   at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)

   at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
0)
   at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)

   at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
   at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
   at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:675)
   at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
   at
org.apache.tomcat.util.

RE: Tomcat clustering and NotSerializableException

[Caldarale, Charles R]

> From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat clustering and NotSerializableException
> 
> CoyoteRequestFacade is the first element in the stack trace - 
> it is not the session stored object that is causing the 
> NotSerializableException.

Actually, the CoyoteRequestFacade _is_ the object being serialized.  That class 
name is the explanatory text added to the exception being thrown by 
ObjectOutputStream at line 1054 (look at the JRE source), not the origin of the 
exception.  Nonetheless, your points are still valid.  Whatever code is 
sneaking a direct or indirect reference to the request into the session object 
needs to be changed.  As you indicated, it must be an indirect reference from 
an attribute added to the session, since a direct one wouldn't pass the 
serializability check.

> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException: 
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>   at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>   at 
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeExternal(DeltaRequest.java:300)
>   at 
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaRequest.java:217)
>   at 
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(DeltaManager.java:393)
>   at 
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(DeltaManager.java:782)
>   at 
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationValve.java:203)
>   at 
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
>   at 
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>   at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>   at 
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>   at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>   at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>   at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
>   at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
>   at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
>   at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
>   at 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
>   at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
>   at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
>   at java.lang.Thread.run(Thread.java:534)

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering and NotSerializableException

[Richard Mixon (qwest)]

CoyoteRequestFacade is the first element in the stack trace - it is not
the session stored object that is causing the NotSerializableException.

As I said in my prior posting, to resolve this issue you need to:

1) Identify each object that you are explicitly storing in the session
and make sure it directly or indirectly (through inheritance) specified
that it implements Serializable.

2) Follow the chain from each session object to other objects that it
references and make sure they are ALL marked as serializable (again -
either directly or indirectly)>

That will fix your problem. These issues often do not come up until
either you:
1. Try and use session replication.
2. Try to persist sessions to a datastore and access from a cluster.
3. Try to persist sessions across a restart of Tomcat.

Also, please just reply to the list - not to the list and to the poster.

HTH - Richard

Sng Wee Jim wrote:
> But the stacktrace says
>
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>   at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>   at
>
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:13
> 32)
>   at
>
> Since CoyoteRequestFacade is a tomcat class, I assume it has to be
> fixed
> by the tomcat team. Unless the actual object that is not Serializable
> not CoyoteRequestFacade is available somewhere else...
>
> - Jim
>
>
>
> -Original Message-
> From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Monday,
> February 28, 2005 11:13 PM
> To: Tomcat Users List
> Subject: RE: Tomcat clustering and NotSerializableException
>
> As Matt said its probably your applications objects. When we switched
> to
> clustering I was surprised at how many of my session objects I needed
> to
> add serializable to. But it was easy work and quickl done.
>
> HTH - Richard
>
> Dale, Matt wrote:
>> I would guess that this means you have an object in your session that
>> does not implement the serializable interface.
>>
>> Ta
>> Matt
>>
>> -Original Message-----
>> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
>> Sent: 28 February 2005 09:21
>> To: tomcat-user@jakarta.apache.org
>> Subject: Tomcat clustering and NotSerializableException
>>
>>
>>
>> Hi,
>>
>>
>>
>>
>>
>> I am using Tomcat 5.0.28 on MS Win2k server.
>>
>>
>>
>>
>> After I have uncommented the "Cluster" element in server.xml, I get
>> the following exceptions on the tomcat console for some actions that
>> are using displaytag.
>>
>>
>>
>>
>> Is it a tomcat bug, since
>> org.apache.coyote.tomcat5.CoyoteRequestFacade
>> is involved?
>>
>>
>>
>>
>>
>>
>>
>>
>> (DeltaManager.java:813)- Unable to serialize delta request
>>
>> java.io.NotSerializableException:
>> org.apache.coyote.tomcat5.CoyoteRequestFacade
>>
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>>
>>
>>
>>
>> at
>> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>>
>>> 1332)
>>
>> at
>> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>>
>> 04)
>>
>> at
>> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>>
>> a:1247)
>>
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>>
>>
>>
>>
>> at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>>
>> xternal(DeltaRequest.java:300)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>>
>> equest.java:217)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>>
>> eltaManager.java:393)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>>
>> taManager.java:782)
>>
>> at
>> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>>
>> lve.java:203)
>>
>> at
>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>>
>> eContext.java:102)
>>
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>>
>> ava:118)
>>
>

RE: Tomcat clustering and NotSerializableException

[Caldarale, Charles R]

> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat clustering and NotSerializableException
> 
> But the stacktrace says
> 
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
> 
> Since CoyoteRequestFacade is a tomcat class, I assume it has 
> to be fixed by the tomcat team.

I'm confused.  How did a reference to a request facade object get stored in the 
session object?  I couldn't find any request-related fields in a DeltaSession, 
and if it was set as an attribute, there's a check in DeltaSession to insure 
serializability before the value is accepted.  (Actually, there are two checks 
in the 5.0.28 version; it appears that the second one is redundant.)  Also, it 
wouldn't make sense to have  any request-related data in a session object, 
since there can be multiple concurrent requests associated with any session.  
What am I missing?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException: 
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>   at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>   at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
>   at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>   at 
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeExternal(DeltaRequest.java:300)
>   at 
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaRequest.java:217)
>   at 
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(DeltaManager.java:393)
>   at 
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(DeltaManager.java:782)
>   at 
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationValve.java:203)
>   at 
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
>   at 
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>   at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>   at 
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>   at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>   at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>   at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
>   at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
>   at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
>   at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
>   at 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
>   at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
>   at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
>   at java.lang.Thread.run(Thread.java:534)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering and NotSerializableException

[Sng Wee Jim]

But the stacktrace says

java.io.NotSerializableException:
org.apache.coyote.tomcat5.CoyoteRequestFacade
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:13
32)
at


Since CoyoteRequestFacade is a tomcat class, I assume it has to be fixed
by the tomcat team. Unless the actual object that is not Serializable
not CoyoteRequestFacade is available somewhere else...

- Jim



-Original Message-
From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 11:13 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException

As Matt said its probably your applications objects. When we switched to
clustering I was surprised at how many of my session objects I needed to
add serializable to. But it was easy work and quickl done.

HTH - Richard

Dale, Matt wrote:
> I would guess that this means you have an object in your session that
> does not implement the serializable interface.
>
> Ta
> Matt
>
> -Original Message-
> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 09:21
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat clustering and NotSerializableException
>
>
>
> Hi,
>
>
>
>
>
> I am using Tomcat 5.0.28 on MS Win2k server.
>
>
>
>
> After I have uncommented the "Cluster" element in server.xml, I get
> the
> following exceptions on the tomcat console for some actions that are
> using displaytag.
>
>
>
>
> Is it a tomcat bug, since
> org.apache.coyote.tomcat5.CoyoteRequestFacade
> is involved?
>
>
>
>
>
>
>
>
> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>
>
>
>
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>
>> 1332)
>
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>
> 04)
>
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>
> a:1247)
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>
>
>
>
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>
> xternal(DeltaRequest.java:300)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>
> equest.java:217)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>
> eltaManager.java:393)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>
> taManager.java:782)
>
> at
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>
> lve.java:203)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>
> ava:118)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>
> ve.java:109)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:104)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>
>
>
>
> at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
>
> 0)
>
> at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
>
>
>
>
> at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
>
> at
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
>
> at
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
>
> va:675)
>
> at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
>
> ool.java:683)
>
> at java.lang.Thread.run(Thread.java:534)
>
>
>
>
>
>

RE: Tomcat clustering and NotSerializableException

[Randall Svancara]

well apparently my problem is that my cluster is not working properly.
I can see the multicast broadcast messages on my network, however the
objects do not seem to be replicating.  The only thing I have in my logs
is:

INFO: Manager[/testapp], skipping state transfer. No members active in
cluster group.

This displays after the delta manager starts in the catalina.out file.
If anyone has any good ideas on why this is happening for me, I would be
willing to try anything at this point.  My NIC supports multicast.  I
have set the distributable element in the web.xml.

Thanks,

Randall 

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 28, 2005 11:04 AM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException


These objects will replicate to other instances when ALL objects in the
session are serializable. I suspect that nothing will be replicated if
there is non serializable objects in there.

Ta
Matt

-Original Message-
From: Randall Svancara [mailto:[EMAIL PROTECTED]
Sent: 28 February 2005 15:14
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException


But do those session objects replicate to the other tomcat instances???
I have been testing session objects that implement java.io.serializable
and I have not yet been able to see these objects when fail over occurs
to another instance??

Thanks,

Randall 

-Original Message-
From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 8:13 AM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException

As Matt said its probably your applications objects. When we switched to
clustering I was surprised at how many of my session objects I needed to
add serializable to. But it was easy work and quickl done.

HTH - Richard

Dale, Matt wrote:
> I would guess that this means you have an object in your session that 
> does not implement the serializable interface.
>
> Ta
> Matt
>
> -Original Message-
> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 09:21
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat clustering and NotSerializableException
>
>
>
> Hi,
>
>
>
>
>
> I am using Tomcat 5.0.28 on MS Win2k server.
>
>
>
>
> After I have uncommented the "Cluster" element in server.xml, I get 
> the following exceptions on the tomcat console for some actions that 
> are using displaytag.
>
>
>
>
> Is it a tomcat bug, since
> org.apache.coyote.tomcat5.CoyoteRequestFacade
> is involved?
>
>
>
>
>
>
>
>
> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>
>
>
>
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>
>> 1332)
>
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>
> 04)
>
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>
> a:1247)
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>
>
>
>
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>
> xternal(DeltaRequest.java:300)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>
> equest.java:217)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>
> eltaManager.java:393)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>
> taManager.java:782)
>
> at
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>
> lve.java:203)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>
> ava:118)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>
> ve.java:109)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:104)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)

RE: Tomcat clustering and NotSerializableException

[Dale, Matt]

These objects will replicate to other instances when ALL objects in the session 
are serializable. I suspect that nothing will be replicated if there is non 
serializable objects in there.

Ta
Matt

-Original Message-
From: Randall Svancara [mailto:[EMAIL PROTECTED]
Sent: 28 February 2005 15:14
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException


But do those session objects replicate to the other tomcat instances???
I have been testing session objects that implement java.io.serializable
and I have not yet been able to see these objects when fail over occurs
to another instance??

Thanks,

Randall 

-Original Message-
From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 28, 2005 8:13 AM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException

As Matt said its probably your applications objects. When we switched to
clustering I was surprised at how many of my session objects I needed to
add serializable to. But it was easy work and quickl done.

HTH - Richard

Dale, Matt wrote:
> I would guess that this means you have an object in your session that 
> does not implement the serializable interface.
>
> Ta
> Matt
>
> -Original Message-
> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 09:21
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat clustering and NotSerializableException
>
>
>
> Hi,
>
>
>
>
>
> I am using Tomcat 5.0.28 on MS Win2k server.
>
>
>
>
> After I have uncommented the "Cluster" element in server.xml, I get 
> the following exceptions on the tomcat console for some actions that 
> are using displaytag.
>
>
>
>
> Is it a tomcat bug, since
> org.apache.coyote.tomcat5.CoyoteRequestFacade
> is involved?
>
>
>
>
>
>
>
>
> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>
>
>
>
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>
>> 1332)
>
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>
> 04)
>
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>
> a:1247)
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>
>
>
>
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>
> xternal(DeltaRequest.java:300)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>
> equest.java:217)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>
> eltaManager.java:393)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>
> taManager.java:782)
>
> at
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>
> lve.java:203)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>
> ava:118)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>
> ve.java:109)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:104)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>
>
>
>
> at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
>
> 0)
>
> at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
>
>
>
>
> at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
>
> at
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
>
> at
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
>
> va:675)
>
> at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
>
> at
> org.apache.tomcat.util.threads.

RE: Tomcat clustering and NotSerializableException

[Randall Svancara]

ThanksI will look at 5.5.8.  I know it is in alpha status right now,
but I am just testing and by the time I deploy my application, 5.5.8
will probably be stable.

Thanks

Randall 

-Original Message-
From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 28, 2005 8:55 AM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException

Randall,
I know that session replication works in Tomcat 5.5.7 and it may also
works in 5.0.x (no experience). But to get failover restart to work
properly (i.e. restarting a failed node) I had to use Tomcat 5.5.7 with
a developer-supplied patch. This patch will be available with Tomcat
5.5.8.
HTH- Richard

Randall Svancara wrote:
> But do those session objects replicate to the other tomcat 
> instances??? I have been testing session objects that implement 
> java.io.serializable and I have not yet been able to see these objects

> when fail over occurs to another instance??
>
> Thanks,
>
> Randall
>
> -Original Message-
> From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 8:13 AM
> To: Tomcat Users List
> Subject: RE: Tomcat clustering and NotSerializableException
>
> As Matt said its probably your applications objects. When we switched 
> to clustering I was surprised at how many of my session objects I 
> needed to add serializable to. But it was easy work and quickl done.
>
> HTH - Richard
>
> Dale, Matt wrote:
>> I would guess that this means you have an object in your session that

>> does not implement the serializable interface.
>>
>> Ta
>> Matt
>>
>> -Original Message-
>> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
>> Sent: 28 February 2005 09:21
>> To: tomcat-user@jakarta.apache.org
>> Subject: Tomcat clustering and NotSerializableException
>>
>>
>>
>> Hi,
>>
>>
>>
>>
>>
>> I am using Tomcat 5.0.28 on MS Win2k server.
>>
>>
>>
>>
>> After I have uncommented the "Cluster" element in server.xml, I get 
>> the following exceptions on the tomcat console for some actions that 
>> are using displaytag.
>>
>>
>>
>>
>> Is it a tomcat bug, since
>> org.apache.coyote.tomcat5.CoyoteRequestFacade
>> is involved?
>>
>>
>>
>>
>>
>>
>>
>>
>> (DeltaManager.java:813)- Unable to serialize delta request
>>
>> java.io.NotSerializableException:
>> org.apache.coyote.tomcat5.CoyoteRequestFacade
>>
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>>
>>
>>
>>
>> at
>> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>>
>>> 1332)
>>
>> at
>> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>>
>> 04)
>>
>> at
>> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>>
>> a:1247)
>>
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>>
>>
>>
>>
>> at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>>
>> xternal(DeltaRequest.java:300)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>>
>> equest.java:217)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>>
>> eltaManager.java:393)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>>
>> taManager.java:782)
>>
>> at
>> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>>
>> lve.java:203)
>>
>> at
>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>>
>> eContext.java:102)
>>
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>>
>> ava:118)
>>
>> at
>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>>
>> eContext.java:102)
>>
>> at
>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>>
>> a:520)
>>
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>>
>> ve.java:109)
>>
>> at
>> org.apache.catalin

RE: Tomcat clustering and NotSerializableException

[Richard Mixon (qwest)]

Randall,
I know that session replication works in Tomcat 5.5.7 and it may also
works in 5.0.x (no experience). But to get failover restart to work
properly (i.e. restarting a failed node) I had to use Tomcat 5.5.7 with
a developer-supplied patch. This patch will be available with Tomcat
5.5.8.
HTH- Richard

Randall Svancara wrote:
> But do those session objects replicate to the other tomcat
> instances??? I have been testing session objects that implement
> java.io.serializable and I have not yet been able to see these
> objects when fail over occurs to another instance??
>
> Thanks,
>
> Randall
>
> -Original Message-
> From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 8:13 AM
> To: Tomcat Users List
> Subject: RE: Tomcat clustering and NotSerializableException
>
> As Matt said its probably your applications objects. When we switched
> to clustering I was surprised at how many of my session objects I
> needed to add serializable to. But it was easy work and quickl done.
>
> HTH - Richard
>
> Dale, Matt wrote:
>> I would guess that this means you have an object in your session that
>> does not implement the serializable interface.
>>
>> Ta
>> Matt
>>
>> -Original Message-
>> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
>> Sent: 28 February 2005 09:21
>> To: tomcat-user@jakarta.apache.org
>> Subject: Tomcat clustering and NotSerializableException
>>
>>
>>
>> Hi,
>>
>>
>>
>>
>>
>> I am using Tomcat 5.0.28 on MS Win2k server.
>>
>>
>>
>>
>> After I have uncommented the "Cluster" element in server.xml, I get
>> the following exceptions on the tomcat console for some actions that
>> are using displaytag.
>>
>>
>>
>>
>> Is it a tomcat bug, since
>> org.apache.coyote.tomcat5.CoyoteRequestFacade
>> is involved?
>>
>>
>>
>>
>>
>>
>>
>>
>> (DeltaManager.java:813)- Unable to serialize delta request
>>
>> java.io.NotSerializableException:
>> org.apache.coyote.tomcat5.CoyoteRequestFacade
>>
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>>
>>
>>
>>
>> at
>> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>>
>>> 1332)
>>
>> at
>> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>>
>> 04)
>>
>> at
>> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>>
>> a:1247)
>>
>> at
>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>>
>>
>>
>>
>> at
>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>>
>> xternal(DeltaRequest.java:300)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>>
>> equest.java:217)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>>
>> eltaManager.java:393)
>>
>> at
>> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>>
>> taManager.java:782)
>>
>> at
>> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>>
>> lve.java:203)
>>
>> at
>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>>
>> eContext.java:102)
>>
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>>
>> ava:118)
>>
>> at
>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>>
>> eContext.java:102)
>>
>> at
>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>>
>> a:520)
>>
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>>
>> ve.java:109)
>>
>> at
>> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>>
>> eContext.java:104)
>>
>> at
>> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>>
>> a:520)
>>
>> at
>> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>>
>>
>>
>>
>> at
>> org.apache.coyo

RE: Tomcat clustering and NotSerializableException

[Randall Svancara]

But do those session objects replicate to the other tomcat instances???
I have been testing session objects that implement java.io.serializable
and I have not yet been able to see these objects when fail over occurs
to another instance??

Thanks,

Randall 

-Original Message-
From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 28, 2005 8:13 AM
To: Tomcat Users List
Subject: RE: Tomcat clustering and NotSerializableException

As Matt said its probably your applications objects. When we switched to
clustering I was surprised at how many of my session objects I needed to
add serializable to. But it was easy work and quickl done.

HTH - Richard

Dale, Matt wrote:
> I would guess that this means you have an object in your session that 
> does not implement the serializable interface.
>
> Ta
> Matt
>
> -Original Message-
> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 09:21
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat clustering and NotSerializableException
>
>
>
> Hi,
>
>
>
>
>
> I am using Tomcat 5.0.28 on MS Win2k server.
>
>
>
>
> After I have uncommented the "Cluster" element in server.xml, I get 
> the following exceptions on the tomcat console for some actions that 
> are using displaytag.
>
>
>
>
> Is it a tomcat bug, since
> org.apache.coyote.tomcat5.CoyoteRequestFacade
> is involved?
>
>
>
>
>
>
>
>
> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>
>
>
>
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>
>> 1332)
>
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>
> 04)
>
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>
> a:1247)
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>
>
>
>
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>
> xternal(DeltaRequest.java:300)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>
> equest.java:217)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>
> eltaManager.java:393)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>
> taManager.java:782)
>
> at
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>
> lve.java:203)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>
> ava:118)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>
> ve.java:109)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:104)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>
>
>
>
> at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
>
> 0)
>
> at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
>
>
>
>
> at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
>
> at
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
>
> at
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
>
> va:675)
>
> at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
>
> ool.java:683)
>
> at java.lang.Thread.run(Thread.java:534)
>
>
>
>
>
>
>
>
>
>
> - Jim
>
>
>
>

> The information in this email is confidential and is intended solely 
> for the addressee(s).
> Ac

RE: Tomcat clustering and NotSerializableException

[Richard Mixon (qwest)]

As Matt said its probably your applications objects. When we switched to
clustering I was surprised at how many of my session objects I needed to
add serializable to. But it was easy work and quickl done.

HTH - Richard

Dale, Matt wrote:
> I would guess that this means you have an object in your session that
> does not implement the serializable interface.
>
> Ta
> Matt
>
> -Original Message-
> From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 09:21
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat clustering and NotSerializableException
>
>
>
> Hi,
>
>
>
>
>
> I am using Tomcat 5.0.28 on MS Win2k server.
>
>
>
>
> After I have uncommented the "Cluster" element in server.xml, I get
> the
> following exceptions on the tomcat console for some actions that are
> using displaytag.
>
>
>
>
> Is it a tomcat bug, since
> org.apache.coyote.tomcat5.CoyoteRequestFacade
> is involved?
>
>
>
>
>
>
>
>
> (DeltaManager.java:813)- Unable to serialize delta request
>
> java.io.NotSerializableException:
> org.apache.coyote.tomcat5.CoyoteRequestFacade
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>
>
>
>
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
>
>> 1332)
>
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
>
> 04)
>
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
>
> a:1247)
>
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>
>
>
>
> at
> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE
>
> xternal(DeltaRequest.java:300)
>
> at
> org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR
>
> equest.java:217)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D
>
> eltaManager.java:393)
>
> at
> org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del
>
> taManager.java:782)
>
> at
> org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa
>
> lve.java:203)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>
> ava:118)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:102)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>
> ve.java:109)
>
> at
> org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
>
> eContext.java:104)
>
> at
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
>
> a:520)
>
> at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>
>
>
>
> at
> org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16
>
> 0)
>
> at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
>
>
>
>
> at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
>
> at
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
>
> at
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
>
> va:675)
>
> at
> org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
>
> ool.java:683)
>
> at java.lang.Thread.run(Thread.java:534)
>
>
>
>
>
>
>
>
>
>
> - Jim
>
>
>
>

> The information in this email is confidential and is intended solely
> for the addressee(s).
> Access to this email by anyone else is unauthorized. If you are not
> an intended recipient, please notify the sender of this email
>
> immediately. You should not copy, use or disseminate the
>
> information contained in the email.
> Any views expressed in this message are those of the individual
> sender, except where the sender specifically states them to be
> the views of Capco.
>
> http://www.capco.com/
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering and NotSerializableException

[Dale, Matt]

I would guess that this means you have an object in your session that does not 
implement the serializable interface.

Ta
Matt

-Original Message-
From: Sng Wee Jim [mailto:[EMAIL PROTECTED]
Sent: 28 February 2005 09:21
To: tomcat-user@jakarta.apache.org
Subject: Tomcat clustering and NotSerializableException



Hi,





I am using Tomcat 5.0.28 on MS Win2k server.




After I have uncommented the "Cluster" element in server.xml, I get the
following exceptions on the tomcat console for some actions that are
using displaytag.




Is it a tomcat bug, since org.apache.coyote.tomcat5.CoyoteRequestFacade
is involved?








(DeltaManager.java:813)- Unable to serialize delta request

java.io.NotSerializableException:
org.apache.coyote.tomcat5.CoyoteRequestFacade

at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)




at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java

:1332)

at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13

04)

at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav

a:1247)

at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)




at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at
org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE

xternal(DeltaRequest.java:300)

at
org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR

equest.java:217)

at
org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D

eltaManager.java:393)

at
org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del

taManager.java:782)

at
org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa

lve.java:203)

at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv

eContext.java:102)

at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j

ava:118)

at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv

eContext.java:102)

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav

a:520)

at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal

ve.java:109)

at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv

eContext.java:104)

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav

a:520)

at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)




at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16

0)

at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)




at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)

at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)

at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja

va:675)

at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)

at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP

ool.java:683)

at java.lang.Thread.run(Thread.java:534)










- Jim




The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorized. If you are not
an intended recipient, please notify the sender of this email

immediately. You should not copy, use or disseminate the

information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.

http://www.capco.com/


Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not 
the intended recipient or the person responsible for delivering to the intended 
recipient, be advised that you have received this E-mail in error and that any 
use or copying is strictly prohibited. If you have received this E-mail in 
error please notify the beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual 
sender and not beCogent Ltd. You must take full responsibility for virus 
checking this email and any attachments.
Please note that the content of this email or any of its attachments may 
contain data that falls within the scope of the Data Protection Acts and that 
you must ensure that any handling or processing of such data by you is fully 
compliant with the terms and provisions of the Data Protection Act 1984 and 
1998.


--

Tomcat clustering and NotSerializableException

[Sng Wee Jim]

Hi,



I am using Tomcat 5.0.28 on MS Win2k server.



After I have uncommented the "Cluster" element in server.xml, I get the
following exceptions on the tomcat console for some actions that are
using displaytag.



Is it a tomcat bug, since org.apache.coyote.tomcat5.CoyoteRequestFacade
is involved?





(DeltaManager.java:813)- Unable to serialize delta request

java.io.NotSerializableException:
org.apache.coyote.tomcat5.CoyoteRequestFacade

at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)



at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java

:1332)

at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13

04)

at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav

a:1247)

at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)



at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at
org.apache.catalina.cluster.session.DeltaRequest$AttributeInfo.writeE

xternal(DeltaRequest.java:300)

at
org.apache.catalina.cluster.session.DeltaRequest.writeExternal(DeltaR

equest.java:217)

at
org.apache.catalina.cluster.session.DeltaManager.unloadDeltaRequest(D

eltaManager.java:393)

at
org.apache.catalina.cluster.session.DeltaManager.requestCompleted(Del

taManager.java:782)

at
org.apache.catalina.cluster.tcp.ReplicationValve.invoke(ReplicationVa

lve.java:203)

at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv

eContext.java:102)

at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j

ava:118)

at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv

eContext.java:102)

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav

a:520)

at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal

ve.java:109)

at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv

eContext.java:104)

at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav

a:520)

at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)



at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:16

0)

at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)



at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)

at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)

at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja

va:675)

at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)

at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP

ool.java:683)

at java.lang.Thread.run(Thread.java:534)







- Jim




The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorized. If you are not
an intended recipient, please notify the sender of this email
immediately. You should not copy, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.

http://www.capco.com/

Re: tomcat clustering / jwsdp soap / serializable

[peter maas]

O.k. I just found out that I can force wscompile to add the 
implementation of Serializable to all datatypes 
(xSerializable="true")... however the part about older apps is still 
relevant.

peter maas wrote:
Hi list,
I have been experimenting with the clustering options for a while. The 
main issue I seem to encounter over and over again is synchronizing 
objects which do not implement the serializable interface. Since we 
are using the jwsdp wscompile tool to generate source code based on a 
wsdl we have tons of beans generated which do not implement the 
Serializable interface (allthough, since they are sent over SOAP the 
can be serialized). If we want to connect suchs a bean to a session, I 
would have to modify the auto generated code or write adapter beans.
Also it would mean that if I want to use older applications (for which 
we are not sure if they implement the Serializable interface) in a 
cluster setup, I would have to modify and recompile them!

Is there a way to enable replication based on introspection if the 
Serialization interface is not implemented? Any other ideas?


--
Peter Maas
Application Architect / Streaming
Noterik Multimedia BV
Prins Hendrikkade 120
1011 AM Amsterdam
The Netherlands
Tel: +31 (0)205929966
Fax: +31 (0)204688405
Gsm: +31 (0)624687952
Web: www.noterik.nl
--
Take a look at our streaming solutions: 
http://www.streamedit.com/demo.html

Get firefox: 
http://www.mozilla.org/products/firefox/
---

:wq!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

tomcat clustering / jwsdp soap / serializable

[peter maas]

Hi list,
I have been experimenting with the clustering options for a while. The 
main issue I seem to encounter over and over again is synchronizing 
objects which do not implement the serializable interface. Since we are 
using the jwsdp wscompile tool to generate source code based on a wsdl 
we have tons of beans generated which do not implement the Serializable 
interface (allthough, since they are sent over SOAP the can be 
serialized). If we want to connect suchs a bean to a session, I would 
have to modify the auto generated code or write adapter beans.
Also it would mean that if I want to use older applications (for which 
we are not sure if they implement the Serializable interface) in a 
cluster setup, I would have to modify and recompile them!

Is there a way to enable replication based on introspection if the 
Serialization interface is not implemented? Any other ideas?

--
Peter Maas
Application Architect / Streaming
Noterik Multimedia BV
Prins Hendrikkade 120
1011 AM Amsterdam
The Netherlands
Tel: +31 (0)205929966
Fax: +31 (0)204688405
Gsm: +31 (0)624687952
Web: www.noterik.nl
--
Take a look at our streaming solutions: 
http://www.streamedit.com/demo.html

Get firefox: 
http://www.mozilla.org/products/firefox/
---

:wq!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat clustering

[Michael Echerer]

Srinivas Rao Ch wrote:
I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".
Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.
I remember that on WindowsXP the integrated Firewall, if enabled, is a 
show stopper.
Try to - temporarily - disable it on all network interfaces and start 
your Tomcats again.

Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat clustering without Apache

[Cott Lang]

> That's also what I referred to when mentioning "SSL Session" - see, the
> SSL layer in effect creates a session with the client, and one can thus
> use this to do sessioning/sticking with - AT LEAST this works when you use
> client certificates, but I'm not totally sure how this goes when there is
> no client certificate. Still the browser and server has to do some
> negotiation of what session key they'll use - and this is what I believed
> was the key to session-keeping-aspect of SSL.

It works fine without client keys. Usually. :)  Some browers don't reuse
ssl session IDs. Also, you will still have the possibility of hopping
servers when you switch from http to https, since you can't map from a
cookie to an SSL session ID.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat clustering without Apache

[Cott Lang]

On Tue, 2004-08-17 at 06:26, QM wrote:
> On Tue, Aug 17, 2004 at 05:33:00AM -0700, Cott Lang wrote:
> : One problem with that is you can still have the session hop servers
> : since the Local Director can't match up cookie based mappings to SSL
> : session mappings, since it can't read the cookies from SSL connections,
> : and can't read non-existant SSL session IDs from non-SSL sessions.
> 
> I may have dreamt this =) but I thought you could have the
> LocalDirector/F5/whatever handle SSL for you, then send plaintext
> traffic back to the Tomcat containers.   (This is effectively what
> people do when they put a web server in front of Tomcat using jk/jk2.)

You did not dream it. :)  However, many load balancers do not support
offloading SSL - I didn't think any Local Director models did, mine
don't.

I've fallen out of touch with load balancing hardware lately. I'm not
sure what (if anything) is "affordable" out there that supports SSL
offload anymore. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Filip Hanik \(lists\)]

mcastAddr is a multicast IP address, range from 224.0.0.0 - 
google it
Filip

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 7:01 AM
To: Tomcat Users List
Subject: RE: Tomcat clustering


Can you please tell me what is "mCastAddr" theoritically, Do I need to run
any service there(Or something like Multicast server) to be a valid
multicast address? Can you please eloberate on this, or point me to some
useful link on this.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 5:19 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



Your first problem is the mCastAddr, firstly it should be an IP address as
no dns lookups are done, secondly it shouldnt be a machine name, it should
be a valid multicast address, the default is 228.0.0.4.

I would suggest setting your tcpListenAddreess back to auto as per the
default as 127.0.0.1 will not hear the multicast ping.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:25
To: Tomcat Users List
Subject: RE: Tomcat clustering


Hi Matt,

Here's my cluster part of server.xml. And, "srao" is my machine name.












Thanks for the interest.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:56 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering


I didnt mean mcastAddr, I meant tcpListenAddress, you have this set to
127.0.0.1 (Loopback) which is not available for external access so the
mulitcast will never get to it.

I'm not sure what's causing your exception though, you'd need to post the
cluster part of your server.xml for a better guess at the problem.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:05
To: Tomcat Users List
Subject: RE: Tomcat clustering


Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]


-
To unsubscr

Re: Tomcat clustering without Apache

[Endre Stølsvik]

On Tue, 17 Aug 2004, QM wrote:

| On Tue, Aug 17, 2004 at 05:33:00AM -0700, Cott Lang wrote:
| : One problem with that is you can still have the session hop servers
| : since the Local Director can't match up cookie based mappings to SSL
| : session mappings, since it can't read the cookies from SSL connections,
| : and can't read non-existant SSL session IDs from non-SSL sessions.
|
| I may have dreamt this =) but I thought you could have the
| LocalDirector/F5/whatever handle SSL for you, then send plaintext
| traffic back to the Tomcat containers.   (This is effectively what
| people do when they put a web server in front of Tomcat using jk/jk2.)

That's exactly what I meant.

Have a good read on the LD and BigIP (or whatever it was) and the
Linux-based approach, I think you might find something in there that
magically solve those problems.

|
| That would grant the LD/F5/etc access to plant their own cookies and
| otherwise determine which client was bound to that Tomcat.

Yes.

That's also what I referred to when mentioning "SSL Session" - see, the
SSL layer in effect creates a session with the client, and one can thus
use this to do sessioning/sticking with - AT LEAST this works when you use
client certificates, but I'm not totally sure how this goes when there is
no client certificate. Still the browser and server has to do some
negotiation of what session key they'll use - and this is what I believed
was the key to session-keeping-aspect of SSL.

|
| -but again, this is all hazy in my memory, so I fear I may have dreamt
| it all...

I'm pretty sure of this. This is supposed to be one of the nice things
with these dedicated clustering boxes: "HW" SSL..

Endre


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat clustering without Apache

[QM]

On Tue, Aug 17, 2004 at 05:33:00AM -0700, Cott Lang wrote:
: One problem with that is you can still have the session hop servers
: since the Local Director can't match up cookie based mappings to SSL
: session mappings, since it can't read the cookies from SSL connections,
: and can't read non-existant SSL session IDs from non-SSL sessions.

I may have dreamt this =) but I thought you could have the
LocalDirector/F5/whatever handle SSL for you, then send plaintext
traffic back to the Tomcat containers.   (This is effectively what
people do when they put a web server in front of Tomcat using jk/jk2.)

That would grant the LD/F5/etc access to plant their own cookies and
otherwise determine which client was bound to that Tomcat.

-but again, this is all hazy in my memory, so I fear I may have dreamt
it all...

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Cott Lang]

On Tue, 2004-08-17 at 02:59, Endre StÃlsvik wrote:

> No, I can't seem to imagine! ;) You should let LocalDirector do the
> SLL'ing - and then you can use the "SSL Session" as stickyness too.

One problem with that is you can still have the session hop servers
since the Local Director can't match up cookie based mappings to SSL
session mappings, since it can't read the cookies from SSL connections,
and can't read non-existant SSL session IDs from non-SSL sessions.

Correct me if I'm wrong, it's always been a problem, so I've always had
to use some sort of session-distribution mechanism. :)




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Srinivas Rao Ch]

Can you please tell me what is "mCastAddr" theoritically, Do I need to run
any service there(Or something like Multicast server) to be a valid
multicast address? Can you please eloberate on this, or point me to some
useful link on this.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 5:19 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



Your first problem is the mCastAddr, firstly it should be an IP address as
no dns lookups are done, secondly it shouldnt be a machine name, it should
be a valid multicast address, the default is 228.0.0.4.

I would suggest setting your tcpListenAddreess back to auto as per the
default as 127.0.0.1 will not hear the multicast ping.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:25
To: Tomcat Users List
Subject: RE: Tomcat clustering


Hi Matt,

Here's my cluster part of server.xml. And, "srao" is my machine name.












Thanks for the interest.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:56 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering


I didnt mean mcastAddr, I meant tcpListenAddress, you have this set to
127.0.0.1 (Loopback) which is not available for external access so the
mulitcast will never get to it.

I'm not sure what's causing your exception though, you'd need to post the
cluster part of your server.xml for a better guess at the problem.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:05
To: Tomcat Users List
Subject: RE: Tomcat clustering


Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]


-
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]

RE: Tomcat clustering

[Dale, Matt]

Your first problem is the mCastAddr, firstly it should be an IP address as no dns 
lookups are done, secondly it shouldnt be a machine name, it should be a valid 
multicast address, the default is 228.0.0.4.

I would suggest setting your tcpListenAddreess back to auto as per the default as 
127.0.0.1 will not hear the multicast ping.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:25
To: Tomcat Users List
Subject: RE: Tomcat clustering


Hi Matt,

Here's my cluster part of server.xml. And, "srao" is my machine name.












Thanks for the interest.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:56 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering


I didnt mean mcastAddr, I meant tcpListenAddress, you have this set to
127.0.0.1 (Loopback) which is not available for external access so the
mulitcast will never get to it.

I'm not sure what's causing your exception though, you'd need to post the
cluster part of your server.xml for a better guess at the problem.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:05
To: Tomcat Users List
Subject: RE: Tomcat clustering


Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the

AW: Tomcat clustering

[Bjoern . Andersen]

Hmm,

not sure, but hasn't mcastAddr="srao" got to be an IP-Address? Or at least I
hope that srao resolves well on all HOSTS-Files/DNS to a valid MCast-Adress
which is configured on the tomcat-servers.
Say, if you got one tomcat on each server and each server got one NIC, you
need 2 ip-adresses on this NIC, maybe even 3 (Normal IP, multicast-addr,
loadbalancing-addr). And the mcast-addr needs to be identical on all nic's
and in the range of 224.0.0.0 - 239.255.255.255 if you want to stay in the
conventions.

--
Björn Andersen
www.premiere.de

-Ursprüngliche Nachricht-
Von: Srinivas Rao Ch [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 17. August 2004 13:25
An: Tomcat Users List
Betreff: RE: Tomcat clustering

Hi Matt,

Here's my cluster part of server.xml. And, "srao" is my machine name.












Thanks for the interest.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:56 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering


I didnt mean mcastAddr, I meant tcpListenAddress, you have this set to
127.0.0.1 (Loopback) which is not available for external access so the
mulitcast will never get to it.

I'm not sure what's causing your exception though, you'd need to post the
cluster part of your server.xml for a better guess at the problem.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:05
To: Tomcat Users List
Subject: RE: Tomcat clustering


Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]


-
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]

RE: Tomcat clustering

[Srinivas Rao Ch]

Hi Matt,

Here's my cluster part of server.xml. And, "srao" is my machine name.












Thanks for the interest.

Regards,
Srinivas

-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:56 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering


I didnt mean mcastAddr, I meant tcpListenAddress, you have this set to
127.0.0.1 (Loopback) which is not available for external access so the
mulitcast will never get to it.

I'm not sure what's causing your exception though, you'd need to post the
cluster part of your server.xml for a better guess at the problem.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:05
To: Tomcat Users List
Subject: RE: Tomcat clustering


Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Dale, Matt]

I didnt mean mcastAddr, I meant tcpListenAddress, you have this set to 127.0.0.1 
(Loopback) which is not available for external access so the mulitcast will never get 
to it.

I'm not sure what's causing your exception though, you'd need to post the cluster part 
of your server.xml for a better guess at the problem.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 12:05
To: Tomcat Users List
Subject: RE: Tomcat clustering


Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Srinivas Rao Ch]

Matt,

Thanks for the reply. Do you mean "mcastAddr" the loopback address? If yes,
I am not using the root machine(Load Balancer, or the machine which takes
request from clients) for clustering.

And before that, seems that the cluster-nodes are not starting the cluster
service. I am getting the following exception at the console.

SEVERE: Unable to start cluster.
java.lang.NullPointerException
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:804)
at
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader
.java:756)
at
org.apache.catalina.cluster.MembershipFactory.getMembershipService(Membershi
pFactory.java:93)
at
org.apache.catalina.cluster.tcp.SimpleTcpCluster.start(SimpleTcpCluster.java
:491)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1115)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:816)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1125)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:518)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:234

Can you please tell me where I was wrong.

Regards,
Srinivas


-Original Message-
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 17, 2004 4:17 PM
To: Tomcat Users List
Subject: RE: Tomcat clustering



I think you may have 2 problems here, firstly the port has to be the same
accross all the tomcats and secondly (I could be wrong about this one) but I
think by specifying the loopback address as the listen address means that it
wont listen on the external interface, therefore the multicast will never be
heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
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]

RE: Tomcat clustering

[Dale, Matt]

I think you may have 2 problems here, firstly the port has to be the same accross all 
the tomcats and secondly (I could be wrong about this one) but I think by specifying 
the loopback address as the listen address means that it wont listen on the external 
interface, therefore the multicast will never be heard.

Ta
Matt

-Original Message-
From: Srinivas Rao Ch [mailto:[EMAIL PROTECTED]
Sent: 17 August 2004 11:26
To: Tomcat Users List
Subject: Tomcat clustering


I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat clustering

[Srinivas Rao Ch]

I am getting problems in configuring my tomcat for clustering. Nodes are not
recognizing each other. "mcastAddr" has the same IP for all the nodes. Can
someone tell what this property is for. My tcpListenAddress is 127.0.0.1 for
all the nodes but port is different. In my rules.xml in the Load Balancer, I
am giving the machine names for "tcpListenAddress".

Still it is not working. Is there anything to be done. Why my nodes are not
recognizing each other. I appreciate any help.

Regards,
Srinivas

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Endre Stølsvik]

On Mon, 16 Aug 2004, Mitchell Teixeira wrote:

| Thanks for the responses so far on this topic.  Seems like I need to
| elaborate a little
|
| We are looking towards Tomcat clustering to solve a problem caused by
| so-called Megaproxy ISPs such as AOL, etc. These ISPs make it look as if
| the same client is coming from multiple IP addresses.

How nice of them..! ;)

| This breaks our app, quite simply.

I can't understand this, though. Do you sort/stick your sessions on ip??
  What about simple, commonday problems like NAT-LANs? Where 50 PCs from
the same office, company, houshold, office, whatever, seems to come from
the same IP?

You need cookies. And you need a loadbalancer that "sticks the sessions"
based on cookie. I know that "Cisco LocalDirectory" can do this, and
something called "BigIP" - both of which are cluster-boxes that uses
different style of "stickyness", the cookie-based stickyness being the
most commonly used for things with sessions.
  (Note that the LocalDirector does not need to know of the
session-semantics, timeout or anything, of the app server (Tomcat) behind.
It just needs -anything- that is unique coming from the client every time
it connects - so to keep the stickyness. Whether Tomcat chooses to drop
the cookie, doesn't really matter, as LocalDirectory simply still would
route that client to this specific box - and your app would understand it
as a new client coming in).

| We're hoping that clustering, with its replicated session data will
| resolve the problem where a customer hitting one physical server and
| adding items to the cart (and therefore session data) then goes to
| checkout and at that moment they appear to be coming from a different IP
| address and end up on the other physical server and an empty cart!

Hmm - I can't seem to imagine that solving your problem in a nice way..
Remember that replicating the session data is rather expensive - and if
your problem is performance (why would you have multiple servers in the
first place?) - then you'll now have to replicate session data between
servers on every client access in addition to your earlier bottlenecks.

|
| Load balancing with "stickiness" helps some, but not completely. Add SSL
| requirements to the mix and you can imagine the headache.

No, I can't seem to imagine! ;) You should let LocalDirector do the
SLL'ing - and then you can use the "SSL Session" as stickyness too.

Note that there are some open source solutions to this problem, using a
specially configured Linux box as an imitation of the LocalDirector.

Note (2) that to achieve no-single-point-of-failure, you'd need -two-
LocalDirectors - they're then linked using some super-proprietary bridge,
and all state are replicated between the two - if one fails, the other
takes over immediately, incl. the TCP connections.
  This is also copied in the open source solution - but I haven't tested
it at all.

| There are lots of load balancing and hardware accellerator vendors
| professing to have a solution, but none of these are really addressing
| the root problem.

I must be missing something - what is the root problem, exactly?

|
| So, with all this said, is it possible to make two or more physical
| servers talk as a Tomcat cluster without Apache or IIS, etc.?  All
| references seem to rely on Apache to make clustering happen.  (just like
| some texts on JSP rely too much on using Struts to teach JSP! ).

Just out of curiousity, why can't you use Apache in front?

Endre


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Dale, Matt]

You would still need some kind of single entry point to your application though as the 
cookie would not reference the same session if the URL changes.

Apache is one way to achieve this but any kind of load balancer should do the trick.

Ta
Matt

-Original Message-
From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
Sent: 16 August 2004 17:31
To: Tomcat Users List
Subject: RE: Tomcat clustering without Apache


session replication is supported in tomcat without apache

in tomcat 5, just uncomment the cluster section in server.xml, also, there
are online docs
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cluster-howto.html

Filip

-Original Message-
From: Mitchell Teixeira [mailto:[EMAIL PROTECTED]
Sent: Monday, August 16, 2004 11:23 AM
To: [EMAIL PROTECTED]
Subject: RE: Tomcat clustering without Apache


Thanks for the responses so far on this topic.  Seems like I need to
elaborate a little

We are looking towards Tomcat clustering to solve a problem caused by
so-called Megaproxy ISPs such as AOL, etc. These ISPs make it look as if
the same client is coming from multiple IP addresses.  This breaks our
app, quite simply. We're hoping that clustering, with its replicated
session data will resolve the problem where a customer hitting one
physical server and adding items to the cart (and therefore session data)
then goes to checkout and at that moment they appear to be coming from a
different IP address and end up on the other physical server and an empty
cart!

Load balancing with "stickiness" helps some, but not completely. Add SSL
requirements to the mix and you can imagine the headache. There are lots
of load balancing and hardware accellerator vendors professing to have a
solution, but none of these are really addressing the root problem.

So, with all this said, is it possible to make two or more physical
servers talk as a Tomcat cluster without Apache or IIS, etc.?  All
references seem to rely on Apache to make clustering happen.  (just like
some texts on JSP rely too much on using Struts to teach JSP! ).

Thanks for any help/ideas.
MitchellT

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Filip Hanik \(lists\)]

session replication is supported in tomcat without apache

in tomcat 5, just uncomment the cluster section in server.xml, also, there
are online docs
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cluster-howto.html

Filip

-Original Message-
From: Mitchell Teixeira [mailto:[EMAIL PROTECTED]
Sent: Monday, August 16, 2004 11:23 AM
To: [EMAIL PROTECTED]
Subject: RE: Tomcat clustering without Apache


Thanks for the responses so far on this topic.  Seems like I need to
elaborate a little

We are looking towards Tomcat clustering to solve a problem caused by
so-called Megaproxy ISPs such as AOL, etc. These ISPs make it look as if
the same client is coming from multiple IP addresses.  This breaks our
app, quite simply. We're hoping that clustering, with its replicated
session data will resolve the problem where a customer hitting one
physical server and adding items to the cart (and therefore session data)
then goes to checkout and at that moment they appear to be coming from a
different IP address and end up on the other physical server and an empty
cart!

Load balancing with "stickiness" helps some, but not completely. Add SSL
requirements to the mix and you can imagine the headache. There are lots
of load balancing and hardware accellerator vendors professing to have a
solution, but none of these are really addressing the root problem.

So, with all this said, is it possible to make two or more physical
servers talk as a Tomcat cluster without Apache or IIS, etc.?  All
references seem to rely on Apache to make clustering happen.  (just like
some texts on JSP rely too much on using Struts to teach JSP! ).

Thanks for any help/ideas.
MitchellT

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Mitchell Teixeira]

Thanks for the responses so far on this topic.  Seems like I need to
elaborate a little

We are looking towards Tomcat clustering to solve a problem caused by
so-called Megaproxy ISPs such as AOL, etc. These ISPs make it look as if
the same client is coming from multiple IP addresses.  This breaks our
app, quite simply. We're hoping that clustering, with its replicated
session data will resolve the problem where a customer hitting one
physical server and adding items to the cart (and therefore session data)
then goes to checkout and at that moment they appear to be coming from a
different IP address and end up on the other physical server and an empty
cart!

Load balancing with "stickiness" helps some, but not completely. Add SSL
requirements to the mix and you can imagine the headache. There are lots
of load balancing and hardware accellerator vendors professing to have a
solution, but none of these are really addressing the root problem. 

So, with all this said, is it possible to make two or more physical
servers talk as a Tomcat cluster without Apache or IIS, etc.?  All
references seem to rely on Apache to make clustering happen.  (just like
some texts on JSP rely too much on using Struts to teach JSP! ).

Thanks for any help/ideas.
MitchellT

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Dale, Matt]

You can also use any kind of hardware or software load balancer or DNS round robin.

Ta
Matt

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 16 August 2004 14:12
To: Tomcat Users List
Subject: RE: Tomcat clustering without Apache


Hi,
The Balancer webapp is meant to function is a pure-Java, low-tech
clustering approach.  It doesn't support some of the features that
advanced clustering configurations do, but it lets you distribute
traffic according to whatever rules or heuristics you want, and easily
define fallbacks for when a server goes down.

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Mitchell Teixeira [mailto:[EMAIL PROTECTED]
>Sent: Monday, August 16, 2004 9:05 AM
>To: [EMAIL PROTECTED]
>Subject: Tomcat clustering without Apache
>
>Hello - I am still fairly new to Tomcat but I have the need to put up a
>Tomcat cluster. Most of the reading I've done about Tomcat clusters
shows
>using Apache someplace in the environment. Is it possible to cluster
two
>Tomcat servers without Apache, IIS, etc. in the picture?
>
>Any ideas, links, etc. are welcome. Thanks for any help. I'm using
Tomcat
>5.0.19 on Windows2000.
>
>Regards,
>MitchellT
>
>
>-
>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]

Any opinions expressed in this E-mail may be those of the individual and not 
necessarily the company. This E-mail and any files transmitted with it are 
confidential and solely for the use of the intended recipient. If you are not the 
intended recipient or the person responsible for delivering to the intended recipient, 
be advised that you have received this E-mail in error and that any use or copying is 
strictly prohibited. If you have received this E-mail in error please notify the 
beCogent postmaster at [EMAIL PROTECTED]
Unless expressly stated, opinions in this email are those of the individual sender and 
not beCogent Ltd. You must take full responsibility for virus checking this email and 
any attachments.
Please note that the content of this email or any of its attachments may contain data 
that falls within the scope of the Data Protection Acts and that you must ensure that 
any handling or processing of such data by you is fully compliant with the terms and 
provisions of the Data Protection Act 1984 and 1998.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering without Apache

[Shapira, Yoav]

Hi,
The Balancer webapp is meant to function is a pure-Java, low-tech
clustering approach.  It doesn't support some of the features that
advanced clustering configurations do, but it lets you distribute
traffic according to whatever rules or heuristics you want, and easily
define fallbacks for when a server goes down.

Yoav Shapira
Millennium Research Informatics


>-Original Message-
>From: Mitchell Teixeira [mailto:[EMAIL PROTECTED]
>Sent: Monday, August 16, 2004 9:05 AM
>To: [EMAIL PROTECTED]
>Subject: Tomcat clustering without Apache
>
>Hello - I am still fairly new to Tomcat but I have the need to put up a
>Tomcat cluster. Most of the reading I've done about Tomcat clusters
shows
>using Apache someplace in the environment. Is it possible to cluster
two
>Tomcat servers without Apache, IIS, etc. in the picture?
>
>Any ideas, links, etc. are welcome. Thanks for any help. I'm using
Tomcat
>5.0.19 on Windows2000.
>
>Regards,
>MitchellT
>
>
>-
>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]

Tomcat clustering without Apache

[Mitchell Teixeira]

Hello - I am still fairly new to Tomcat but I have the need to put up a
Tomcat cluster. Most of the reading I've done about Tomcat clusters shows
using Apache someplace in the environment. Is it possible to cluster two
Tomcat servers without Apache, IIS, etc. in the picture?

Any ideas, links, etc. are welcome. Thanks for any help. I'm using Tomcat
5.0.19 on Windows2000.

Regards, 
MitchellT


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Applet in tomcat clustering

[Filip Hanik - Dev]

no idea until you gives us some more info. like what do your server log files tell you,
how does the URL you are constructing to open the connection look like? etc

Filip

- Original Message - 
From: "Simon Zeng" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 2004 11:43 AM
Subject: RE: Applet in tomcat clustering


> I thought it would work too. But unfortunately it did not.:(
> 
> In both applet and servlet code, I have the trace log. From time to time,
> while in
> applet log the jsessionid is the correct one, but in servlet, it is a
> different one.
> 
> Any idea?
> 
> -Simon
> 
> -Original Message-
> From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 12, 2004 4:42 PM
> To: Tomcat Users List
> Subject: Re: Applet in tomcat clustering
> 
> 
> yes, that should work. print out some debug statements on the server to make
> sure that your request indeed gets the session Id you
> want it to.
> Assuming you have clustering turned on and working properly, you should be
> good to go
> 
> Filip
> - Original Message -
> From: "Simon Zeng" <[EMAIL PROTECTED]>
> To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> Sent: Monday, July 12, 2004 2:40 PM
> Subject: RE: Applet in tomcat clustering
> 
> 
> > I thought I did it. Here are my steps
> > 1. first get jsessionid from servlet
> > 2. pass the jsessionid to applet (through htm page)
> > 3. inside applet, create a new HTTPUrlConnection, and set cookie property
> > with jsessionid.
> > 4. connect to server.
> > 5. In server, the request was sent to a different tomcat instance (this is
> > against the sticky session as stated in tomcat cluster).
> >
> > I might have missed out something, please point them out if so.
> >
> > Thanks,
> > -Simon
> >
> > -Original Message-
> > From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 12, 2004 2:56 PM
> > To: Tomcat Users List
> > Subject: Re: Applet in tomcat clustering
> >
> >
> > you will need to send up cookies just like the HTTP protocol says in order
> > to keep state
> >
> > Filip
> > - Original Message -
> > From: "Simon Zeng" <[EMAIL PROTECTED]>
> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> > Sent: Monday, July 12, 2004 1:39 PM
> > Subject: RE: Applet in tomcat clustering
> >
> >
> > > My mistake. I am using HttpURLConnection (not HttpTunnel) to communicate
> > > between applet and server.
> > >
> > > Thanks,
> > > -Simon
> > >
> > > -Original Message-
> > > From: Simon Zeng [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, July 12, 2004 1:51 PM
> > > To: 'Tomcat Users List'
> > > Subject: Applet in tomcat clustering
> > >
> > >
> > >
> > > Hi,
> > >
> > > Does any use applet in tomcat clustering?I have an question and need
> some
> > > help.
> > >
> > > I have set up two tomcat instances in cluster/load balance. My
> > > webapplication has one feature using applet. As I understand, tomcat
> > > cluster/load balance has sticky session which means subseqent requests
> > being
> > > sent to the same tomcat once the browser/server connection is setup.
> This
> > is
> > > true in my application except while using applet, the request is sent to
> > > different tomcat randomly. I use HTTPTunnel to communicate between
> applet
> > > and server.
> > >
> > > Thanks,
> > >
> > > -Simon
> > >
> > > -
> > > 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]
> >
> >
> > -
> > 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]
> 
> 
> -
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Applet in tomcat clustering

[Simon Zeng]

I thought it would work too. But unfortunately it did not.:(

In both applet and servlet code, I have the trace log. From time to time,
while in
applet log the jsessionid is the correct one, but in servlet, it is a
different one.

Any idea?

-Simon

-Original Message-
From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED]
Sent: Monday, July 12, 2004 4:42 PM
To: Tomcat Users List
Subject: Re: Applet in tomcat clustering


yes, that should work. print out some debug statements on the server to make
sure that your request indeed gets the session Id you
want it to.
Assuming you have clustering turned on and working properly, you should be
good to go

Filip
- Original Message -
From: "Simon Zeng" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Monday, July 12, 2004 2:40 PM
Subject: RE: Applet in tomcat clustering


> I thought I did it. Here are my steps
> 1. first get jsessionid from servlet
> 2. pass the jsessionid to applet (through htm page)
> 3. inside applet, create a new HTTPUrlConnection, and set cookie property
> with jsessionid.
> 4. connect to server.
> 5. In server, the request was sent to a different tomcat instance (this is
> against the sticky session as stated in tomcat cluster).
>
> I might have missed out something, please point them out if so.
>
> Thanks,
> -Simon
>
> -Original Message-
> From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 12, 2004 2:56 PM
> To: Tomcat Users List
> Subject: Re: Applet in tomcat clustering
>
>
> you will need to send up cookies just like the HTTP protocol says in order
> to keep state
>
> Filip
> - Original Message -
> From: "Simon Zeng" <[EMAIL PROTECTED]>
> To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> Sent: Monday, July 12, 2004 1:39 PM
> Subject: RE: Applet in tomcat clustering
>
>
> > My mistake. I am using HttpURLConnection (not HttpTunnel) to communicate
> > between applet and server.
> >
> > Thanks,
> > -Simon
> >
> > -Original Message-
> > From: Simon Zeng [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 12, 2004 1:51 PM
> > To: 'Tomcat Users List'
> > Subject: Applet in tomcat clustering
> >
> >
> >
> > Hi,
> >
> > Does any use applet in tomcat clustering?I have an question and need
some
> > help.
> >
> > I have set up two tomcat instances in cluster/load balance. My
> > webapplication has one feature using applet. As I understand, tomcat
> > cluster/load balance has sticky session which means subseqent requests
> being
> > sent to the same tomcat once the browser/server connection is setup.
This
> is
> > true in my application except while using applet, the request is sent to
> > different tomcat randomly. I use HTTPTunnel to communicate between
applet
> > and server.
> >
> > Thanks,
> >
> > -Simon
> >
> > -
> > 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]
>
>
> -
> 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]


-
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]

Re: Applet in tomcat clustering

[Filip Hanik - Dev]

yes, that should work. print out some debug statements on the server to make sure that 
your request indeed gets the session Id you
want it to.
Assuming you have clustering turned on and working properly, you should be good to go

Filip
- Original Message -
From: "Simon Zeng" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Monday, July 12, 2004 2:40 PM
Subject: RE: Applet in tomcat clustering


> I thought I did it. Here are my steps
> 1. first get jsessionid from servlet
> 2. pass the jsessionid to applet (through htm page)
> 3. inside applet, create a new HTTPUrlConnection, and set cookie property
> with jsessionid.
> 4. connect to server.
> 5. In server, the request was sent to a different tomcat instance (this is
> against the sticky session as stated in tomcat cluster).
>
> I might have missed out something, please point them out if so.
>
> Thanks,
> -Simon
>
> -Original Message-
> From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 12, 2004 2:56 PM
> To: Tomcat Users List
> Subject: Re: Applet in tomcat clustering
>
>
> you will need to send up cookies just like the HTTP protocol says in order
> to keep state
>
> Filip
> - Original Message -
> From: "Simon Zeng" <[EMAIL PROTECTED]>
> To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
> Sent: Monday, July 12, 2004 1:39 PM
> Subject: RE: Applet in tomcat clustering
>
>
> > My mistake. I am using HttpURLConnection (not HttpTunnel) to communicate
> > between applet and server.
> >
> > Thanks,
> > -Simon
> >
> > -Original Message-
> > From: Simon Zeng [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 12, 2004 1:51 PM
> > To: 'Tomcat Users List'
> > Subject: Applet in tomcat clustering
> >
> >
> >
> > Hi,
> >
> > Does any use applet in tomcat clustering?I have an question and need some
> > help.
> >
> > I have set up two tomcat instances in cluster/load balance. My
> > webapplication has one feature using applet. As I understand, tomcat
> > cluster/load balance has sticky session which means subseqent requests
> being
> > sent to the same tomcat once the browser/server connection is setup. This
> is
> > true in my application except while using applet, the request is sent to
> > different tomcat randomly. I use HTTPTunnel to communicate between applet
> > and server.
> >
> > Thanks,
> >
> > -Simon
> >
> > -
> > 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]
>
>
> -
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Applet in tomcat clustering

[Simon Zeng]

I thought I did it. Here are my steps
1. first get jsessionid from servlet
2. pass the jsessionid to applet (through htm page)
3. inside applet, create a new HTTPUrlConnection, and set cookie property
with jsessionid.
4. connect to server.
5. In server, the request was sent to a different tomcat instance (this is
against the sticky session as stated in tomcat cluster).

I might have missed out something, please point them out if so.

Thanks,
-Simon

-Original Message-
From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED]
Sent: Monday, July 12, 2004 2:56 PM
To: Tomcat Users List
Subject: Re: Applet in tomcat clustering


you will need to send up cookies just like the HTTP protocol says in order
to keep state

Filip
- Original Message - 
From: "Simon Zeng" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Monday, July 12, 2004 1:39 PM
Subject: RE: Applet in tomcat clustering


> My mistake. I am using HttpURLConnection (not HttpTunnel) to communicate
> between applet and server.
> 
> Thanks,
> -Simon
> 
> -Original Message-
> From: Simon Zeng [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 12, 2004 1:51 PM
> To: 'Tomcat Users List'
> Subject: Applet in tomcat clustering
> 
> 
> 
> Hi,
> 
> Does any use applet in tomcat clustering?I have an question and need some
> help.
> 
> I have set up two tomcat instances in cluster/load balance. My
> webapplication has one feature using applet. As I understand, tomcat
> cluster/load balance has sticky session which means subseqent requests
being
> sent to the same tomcat once the browser/server connection is setup. This
is
> true in my application except while using applet, the request is sent to
> different tomcat randomly. I use HTTPTunnel to communicate between applet
> and server.
> 
> Thanks,
> 
> -Simon
> 
> -
> 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]


-
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]

Re: Applet in tomcat clustering

[Filip Hanik - Dev]

you will need to send up cookies just like the HTTP protocol says in order to keep 
state

Filip
- Original Message - 
From: "Simon Zeng" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <[EMAIL PROTECTED]>
Sent: Monday, July 12, 2004 1:39 PM
Subject: RE: Applet in tomcat clustering


> My mistake. I am using HttpURLConnection (not HttpTunnel) to communicate
> between applet and server.
> 
> Thanks,
> -Simon
> 
> -Original Message-
> From: Simon Zeng [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 12, 2004 1:51 PM
> To: 'Tomcat Users List'
> Subject: Applet in tomcat clustering
> 
> 
> 
> Hi,
> 
> Does any use applet in tomcat clustering?I have an question and need some
> help.
> 
> I have set up two tomcat instances in cluster/load balance. My
> webapplication has one feature using applet. As I understand, tomcat
> cluster/load balance has sticky session which means subseqent requests being
> sent to the same tomcat once the browser/server connection is setup. This is
> true in my application except while using applet, the request is sent to
> different tomcat randomly. I use HTTPTunnel to communicate between applet
> and server.
> 
> Thanks,
> 
> -Simon
> 
> -
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Applet in tomcat clustering

[Simon Zeng]

My mistake. I am using HttpURLConnection (not HttpTunnel) to communicate
between applet and server.

Thanks,
-Simon

-Original Message-
From: Simon Zeng [mailto:[EMAIL PROTECTED]
Sent: Monday, July 12, 2004 1:51 PM
To: 'Tomcat Users List'
Subject: Applet in tomcat clustering



Hi,

Does any use applet in tomcat clustering?I have an question and need some
help.

I have set up two tomcat instances in cluster/load balance. My
webapplication has one feature using applet. As I understand, tomcat
cluster/load balance has sticky session which means subseqent requests being
sent to the same tomcat once the browser/server connection is setup. This is
true in my application except while using applet, the request is sent to
different tomcat randomly. I use HTTPTunnel to communicate between applet
and server.

Thanks,

-Simon

-
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]

Applet in tomcat clustering

[Simon Zeng]

Hi,

Does any use applet in tomcat clustering?I have an question and need some
help.

I have set up two tomcat instances in cluster/load balance. My
webapplication has one feature using applet. As I understand, tomcat
cluster/load balance has sticky session which means subseqent requests being
sent to the same tomcat once the browser/server connection is setup. This is
true in my application except while using applet, the request is sent to
different tomcat randomly. I use HTTPTunnel to communicate between applet
and server.

Thanks,

-Simon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Fw: Urgent: Issue with Tomcat Clustering

[Filip Hanik - Dev]

try without mod_jk with another load balancer first,
pen (http://siag.nu/pen) or balance (http://balance.sourceforge.net)


- Original Message - 
From: "Vikas Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Sunday, May 23, 2004 12:07 PM
Subject: Urgent: Issue with Tomcat Clustering



Hi All,
I am trying to do tomcat clustering using tomcat 5.0.19 using mod_jk
connector for Apache 2.
I am stuck up in a problem for quite some time.
I am able to run the sample application in my setup and the clustering and
session replication works fine.

But when I run my application in the cluster it bombs. The test scenarios is
like this,
We hvve tried using "poolable" and "synchronous" mode.

The session object in is not getting replicated and is
request.getSession(false) gives null value. The same scenario is working
fine on the sample application. 
I think Cluster setup is fine because sample application

Can you please tell us the reason of exception 

Is there any adverse impact of the following on session replication in
clustering scenario: 

1. usage of encodeURL (URL rewriting)
2. usage of large objects in session
3. usage of cookies

I have attached the server.xml, web.xml and workers.properties.

Please advise
Regards
Vikas

May 23, 2004 8:51:11 PM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:580)
at
org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:518)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:638)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:536)
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:55:53 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberD










-
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]

Re: Urgent: Issue with Tomcat Clustering

[Filip Hanik - Dev]

try without mod_jk with another load balancer first,
pen (http://siag.nu/pen) or balance (http://balance.sourceforge.net)


- Original Message - 
From: "Vikas Gupta" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Sunday, May 23, 2004 12:07 PM
Subject: Urgent: Issue with Tomcat Clustering



Hi All,
I am trying to do tomcat clustering using tomcat 5.0.19 using mod_jk
connector for Apache 2.
I am stuck up in a problem for quite some time.
I am able to run the sample application in my setup and the clustering and
session replication works fine.

But when I run my application in the cluster it bombs. The test scenarios is
like this,
We hvve tried using "poolable" and "synchronous" mode.

The session object in is not getting replicated and is
request.getSession(false) gives null value. The same scenario is working
fine on the sample application. 
I think Cluster setup is fine because sample application

Can you please tell us the reason of exception 

Is there any adverse impact of the following on session replication in
clustering scenario: 

1. usage of encodeURL (URL rewriting)
2. usage of large objects in session
3. usage of cookies

I have attached the server.xml, web.xml and workers.properties.

Please advise
Regards
Vikas

May 23, 2004 8:51:11 PM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:580)
at
org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:518)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:638)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:536)
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:55:53 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberD










-
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]

RE: Urgent: Issue with Tomcat Clustering

[Filip Hanik \(lists\)]

not an issue with clustering, the stack trace is in the mod_jk code,
Filip


-Original Message-
From: Vikas Gupta [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 23, 2004 12:08 PM
To: Tomcat Users List
Subject: Urgent: Issue with Tomcat Clustering



Hi All,
I am trying to do tomcat clustering using tomcat 5.0.19 using mod_jk
connector for Apache 2.
I am stuck up in a problem for quite some time.
I am able to run the sample application in my setup and the clustering and
session replication works fine.

But when I run my application in the cluster it bombs. The test scenarios is
like this,
We hvve tried using "poolable" and "synchronous" mode.

The session object in is not getting replicated and is
request.getSession(false) gives null value. The same scenario is working
fine on the sample application. 
I think Cluster setup is fine because sample application

Can you please tell us the reason of exception 

Is there any adverse impact of the following on session replication in
clustering scenario: 

1. usage of encodeURL (URL rewriting)
2. usage of large objects in session
3. usage of cookies

I have attached the server.xml, web.xml and workers.properties.

Please advise
Regards
Vikas

May 23, 2004 8:51:11 PM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:580)
at
org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:518)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:638)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:536)
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:55:53 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberD





---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.676 / Virus Database: 438 - Release Date: 5/3/2004
 
  

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.676 / Virus Database: 438 - Release Date: 5/3/2004
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Urgent: Issue with Tomcat Clustering

[Vikas Gupta]

Hi All,
I am trying to do tomcat clustering using tomcat 5.0.19 using mod_jk
connector for Apache 2.
I am stuck up in a problem for quite some time.
I am able to run the sample application in my setup and the clustering and
session replication works fine.

But when I run my application in the cluster it bombs. The test scenarios is
like this,
We hvve tried using "poolable" and "synchronous" mode.

The session object in is not getting replicated and is
request.getSession(false) gives null value. The same scenario is working
fine on the sample application. 
I think Cluster setup is fine because sample application

Can you please tell us the reason of exception 

Is there any adverse impact of the following on session replication in
clustering scenario: 

1. usage of encodeURL (URL rewriting)
2. usage of large objects in session
3. usage of cookies

I have attached the server.xml, web.xml and workers.properties.

Please advise
Regards
Vikas

May 23, 2004 8:51:11 PM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:580)
at
org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:518)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:638)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:536)
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:55:53 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberD




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Urgent: Issue with Tomcat Clustering

[Vikas Gupta]

Hi All,
I am trying to do tomcat clustering using tomcat 5.0.19 using mod_jk
connector for Apache 2.
I am stuck up in a problem for quite some time.
I am able to run the sample application in my setup and the clustering and
session replication works fine.

But when I run my application in the cluster it bombs. The test scenarios is
like this,
We hvve tried using "poolable" and "synchronous" mode.

The session object in is not getting replicated and is
request.getSession(false) gives null value. The same scenario is working
fine on the sample application. 
I think Cluster setup is fine because sample application

Can you please tell us the reason of trace that is seeen on tomcat console
when cluster nodes try to communicate to each other.

Is there any adverse impact of the following on session replication in
clustering scenario: 

1. usage of encodeURL (URL rewriting)
2. usage of large objects in session
3. usage of cookies

I have attached the server.xml, web.xml and workers.properties.

Please advise
Regards
Vikas

May 23, 2004 8:51:11 PM org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, processing connection
java.net.SocketException: Software caused connection abort: recv failed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:580)
at
org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:518)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:638)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:536)
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:51:11 PM org.apache.jk.common.HandlerRequest invoke
INFO: Unknown message 0
May 23, 2004 8:55:53 PM org.apache.catalina.cluster.tcp.SimpleTcpCluster
memberD




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: tomcat clustering

[keita elhadji]

Hi,

Thank you for your answer it's working now
thank you.. 

 --- Filip Hanik - Dev <[EMAIL PROTECTED]> a écrit :
> I don't think you have even enabled clustering,
> did you put  in the web.xml file?
> 
> also, all session attributes must be serializable
> 
> Filip
> - Original Message -
> From: "keita elhadji" <[EMAIL PROTECTED]>
> To: "Tomcat Users List"
> <[EMAIL PROTECTED]>
> Sent: Tuesday, May 11, 2004 3:57 AM
> Subject: Re: tomcat clustering
> 
> 
> 
> Hi,
> 
> Thank you for your answer now it's working in my log
> i
> have now :
> 
> 2004-05-11 10:04:21
> StandardContext[/jsp-examples]ContextListener:
> contextInitialized()
> 2004-05-11 10:04:21
> StandardContext[/jsp-examples]SessionListener:
> contextInitialized()
> 2004-05-11 10:04:24
> StandardContext[/servlets-examples]ContextListener:
> contextInitialized()
> 2004-05-11 10:04:25
> StandardContext[/servlets-examples]SessionListener:
> contextInitialized()
> 2004-05-11 10:06:42
> StandardContext[/jsp-examples]SessionListener:
>
sessionCreated('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat')
> 2004-05-11 10:07:07
> StandardContext[/jsp-examples]SessionListener:
>
attributeAdded('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat',
> 'ja
> vax.servlet.jsp.jstl.fmt.request.charset', 'null')
> 2004-05-11 10:07:40
> StandardContext[/jsp-examples]SessionListener:
>
attributeReplaced('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat',
> 'javax.servlet.jsp.jstl.fmt.request.charset',
> 'UTF-8')
> 
> that's mean it's working or not ?
> thank you for answer.
> 
> 
> --- Filip Hanik - Dev <[EMAIL PROTECTED]> a écrit :
> >
> Caused by: java.io.NotSerializableException:
> >
> >
> > - Original Message -
> > From: "keita elhadji" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, May 10, 2004 4:52 AM
> > Subject: tomcat clustering
> >
> >
> > Hi,
> >
> > i have a problem with mod_jk2 .
> > I have two PC  with tomcat5.019
> > 1st PC name is : www.avisdunet.biz
> > 2nd PC name is : www1.avisdunet.biz
> >
> > mod_jk2 and apache2 in the first when i start
> tomcat
> > my clustering didn't work and i don't know why and
> > in
> > my logs catalina.out :
> >
> > 10 mai 2004 11:30:15
> > org.apache.coyote.http11.Http11Protocol init
> > INFO: Initialisation de Coyote HTTP/1.1 sur le
> port
> > 8080
> > 10 mai 2004 11:30:17
> > org.apache.catalina.startup.Catalina load
> > INFO: Initialization processed in 48211 ms
> > 10 mai 2004 11:30:22
> > org.apache.catalina.core.StandardService start
> > INFO: Démarrage du service Catalina
> > 10 mai 2004 11:30:22
> > org.apache.catalina.core.StandardEngine start
> > INFO: Starting Servlet Engine: Apache
> Tomcat/5.0.19
> > 10 mai 2004 11:30:23
> > org.apache.catalina.core.StandardHost start
> > INFO: XML validation disabled
> > 10 mai 2004 11:30:23
> > org.apache.catalina.cluster.tcp.SimpleTcpCluster
> > start
> > INFO: Cluster is about to start
> > 10 mai 2004 11:30:24
> > org.apache.catalina.cluster.mcast.McastService
> start
> > INFO: Sleeping for 2000 secs to establish cluster
> > membership
> > 10 mai 2004 11:30:26
> > org.apache.catalina.core.StandardHost getDeployer
> > INFO: Create Host deployer for direct deployment (
> > non-jmx )
> > 10 mai 2004 11:30:27
> > org.apache.catalina.core.StandardHostDeployer
> > install
> > INFO: Installation d'une application pour le
> chemin
> > de
> > contexte /pro depuis l'URL
> > file:/usr/local/java/tomcat/webapps/pro
> > 10 mai 2004 11:30:43
> > org.apache.catalina.session.StandardManager doLoad
> > GRAVE: "IOException" lors du chargement des
> sessions
> > persistantes: java.io.WriteAbortedException:
> writing
> > aborted; java.io.No$
> > java.io.WriteAbortedException: writing aborted;
> > java.io.NotSerializableException:
> > com.avisdunet.ServeurFond
> > at
> >
>
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
> > at
> >
>
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
> > at
> >
>
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
> > 
> >
> > Caused by: java.io.NotSerializableException:
> > com.avisdunet.ServeurFond
> > a

Re: tomcat clustering

[Filip Hanik - Dev]

I don't think you have even enabled clustering,
did you put  in the web.xml file?

also, all session attributes must be serializable

Filip
- Original Message -
From: "keita elhadji" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, May 11, 2004 3:57 AM
Subject: Re: tomcat clustering



Hi,

Thank you for your answer now it's working in my log i
have now :

2004-05-11 10:04:21
StandardContext[/jsp-examples]ContextListener:
contextInitialized()
2004-05-11 10:04:21
StandardContext[/jsp-examples]SessionListener:
contextInitialized()
2004-05-11 10:04:24
StandardContext[/servlets-examples]ContextListener:
contextInitialized()
2004-05-11 10:04:25
StandardContext[/servlets-examples]SessionListener:
contextInitialized()
2004-05-11 10:06:42
StandardContext[/jsp-examples]SessionListener:
sessionCreated('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat')
2004-05-11 10:07:07
StandardContext[/jsp-examples]SessionListener:
attributeAdded('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat',
'ja
vax.servlet.jsp.jstl.fmt.request.charset', 'null')
2004-05-11 10:07:40
StandardContext[/jsp-examples]SessionListener:
attributeReplaced('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat',
'javax.servlet.jsp.jstl.fmt.request.charset', 'UTF-8')

that's mean it's working or not ?
thank you for answer.


--- Filip Hanik - Dev <[EMAIL PROTECTED]> a écrit : >
Caused by: java.io.NotSerializableException:
>
>
> - Original Message -
> From: "keita elhadji" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, May 10, 2004 4:52 AM
> Subject: tomcat clustering
>
>
> Hi,
>
> i have a problem with mod_jk2 .
> I have two PC  with tomcat5.019
> 1st PC name is : www.avisdunet.biz
> 2nd PC name is : www1.avisdunet.biz
>
> mod_jk2 and apache2 in the first when i start tomcat
> my clustering didn't work and i don't know why and
> in
> my logs catalina.out :
>
> 10 mai 2004 11:30:15
> org.apache.coyote.http11.Http11Protocol init
> INFO: Initialisation de Coyote HTTP/1.1 sur le port
> 8080
> 10 mai 2004 11:30:17
> org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 48211 ms
> 10 mai 2004 11:30:22
> org.apache.catalina.core.StandardService start
> INFO: Démarrage du service Catalina
> 10 mai 2004 11:30:22
> org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
> 10 mai 2004 11:30:23
> org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 10 mai 2004 11:30:23
> org.apache.catalina.cluster.tcp.SimpleTcpCluster
> start
> INFO: Cluster is about to start
> 10 mai 2004 11:30:24
> org.apache.catalina.cluster.mcast.McastService start
> INFO: Sleeping for 2000 secs to establish cluster
> membership
> 10 mai 2004 11:30:26
> org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment (
> non-jmx )
> 10 mai 2004 11:30:27
> org.apache.catalina.core.StandardHostDeployer
> install
> INFO: Installation d'une application pour le chemin
> de
> contexte /pro depuis l'URL
> file:/usr/local/java/tomcat/webapps/pro
> 10 mai 2004 11:30:43
> org.apache.catalina.session.StandardManager doLoad
> GRAVE: "IOException" lors du chargement des sessions
> persistantes: java.io.WriteAbortedException: writing
> aborted; java.io.No$
> java.io.WriteAbortedException: writing aborted;
> java.io.NotSerializableException:
> com.avisdunet.ServeurFond
> at
>
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
> at
>
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
> at
>
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
> 
>
> Caused by: java.io.NotSerializableException:
> com.avisdunet.ServeurFond
> at
>
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
> at
>
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
> at
>
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
> at
>
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
> at
>
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
> at
>
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
> at
>
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
> at
>
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>
> Resolving to alternate DTD
>
'file:/usr/local/java/jakarta-

Re: tomcat clustering

[keita elhadji]

 
Hi,

Thank you for your answer now it's working in my log i
have now :

2004-05-11 10:04:21
StandardContext[/jsp-examples]ContextListener:
contextInitialized()
2004-05-11 10:04:21
StandardContext[/jsp-examples]SessionListener:
contextInitialized()
2004-05-11 10:04:24
StandardContext[/servlets-examples]ContextListener:
contextInitialized()
2004-05-11 10:04:25
StandardContext[/servlets-examples]SessionListener:
contextInitialized()
2004-05-11 10:06:42
StandardContext[/jsp-examples]SessionListener:
sessionCreated('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat')
2004-05-11 10:07:07
StandardContext[/jsp-examples]SessionListener:
attributeAdded('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat',
'ja
vax.servlet.jsp.jstl.fmt.request.charset', 'null')
2004-05-11 10:07:40
StandardContext[/jsp-examples]SessionListener:
attributeReplaced('9BC1CA057DB6D0ADAB176D1D1B266CC2.tomcat',
'javax.servlet.jsp.jstl.fmt.request.charset', 'UTF-8')
 
that's mean it's working or not ?
thank you for answer.


--- Filip Hanik - Dev <[EMAIL PROTECTED]> a écrit : >
Caused by: java.io.NotSerializableException:
> 
> 
> - Original Message -
> From: "keita elhadji" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, May 10, 2004 4:52 AM
> Subject: tomcat clustering
> 
> 
> Hi,
> 
> i have a problem with mod_jk2 .
> I have two PC  with tomcat5.019
> 1st PC name is : www.avisdunet.biz
> 2nd PC name is : www1.avisdunet.biz
> 
> mod_jk2 and apache2 in the first when i start tomcat
> my clustering didn't work and i don't know why and
> in
> my logs catalina.out :
> 
> 10 mai 2004 11:30:15
> org.apache.coyote.http11.Http11Protocol init
> INFO: Initialisation de Coyote HTTP/1.1 sur le port
> 8080
> 10 mai 2004 11:30:17
> org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 48211 ms
> 10 mai 2004 11:30:22
> org.apache.catalina.core.StandardService start
> INFO: Démarrage du service Catalina
> 10 mai 2004 11:30:22
> org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
> 10 mai 2004 11:30:23
> org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 10 mai 2004 11:30:23
> org.apache.catalina.cluster.tcp.SimpleTcpCluster
> start
> INFO: Cluster is about to start
> 10 mai 2004 11:30:24
> org.apache.catalina.cluster.mcast.McastService start
> INFO: Sleeping for 2000 secs to establish cluster
> membership
> 10 mai 2004 11:30:26
> org.apache.catalina.core.StandardHost getDeployer
> INFO: Create Host deployer for direct deployment (
> non-jmx )
> 10 mai 2004 11:30:27
> org.apache.catalina.core.StandardHostDeployer
> install
> INFO: Installation d'une application pour le chemin
> de
> contexte /pro depuis l'URL
> file:/usr/local/java/tomcat/webapps/pro
> 10 mai 2004 11:30:43
> org.apache.catalina.session.StandardManager doLoad
> GRAVE: "IOException" lors du chargement des sessions
> persistantes: java.io.WriteAbortedException: writing
> aborted; java.io.No$
> java.io.WriteAbortedException: writing aborted;
> java.io.NotSerializableException:
> com.avisdunet.ServeurFond
> at
>
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
> at
>
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
> at
>
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
> 
> 
> Caused by: java.io.NotSerializableException:
> com.avisdunet.ServeurFond
> at
>
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
> at
>
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
> at
>
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
> at
>
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
> at
>
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
> at
>
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
> at
>
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
> at
>
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
> 
> Resolving to alternate DTD
>
'file:/usr/local/java/jakarta-tomcat-5.0.19/work/Standalone/localhost/pro/loader/org/apache/strut$
> Call
>
org.apache.struts.action.ActionServlet.addServletMapping(monActionServlet/java.lang.String,*.action/java.lang.String)
> Call
>
org.apache.struts.action.ActionServlet.addServletMapping(action/java.lang.String,*.do/java.lang.String)
> 10 mai 

Re: tomcat clustering

[Filip Hanik - Dev]

Caused by: java.io.NotSerializableException:


- Original Message -
From: "keita elhadji" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 10, 2004 4:52 AM
Subject: tomcat clustering


Hi,

i have a problem with mod_jk2 .
I have two PC  with tomcat5.019
1st PC name is : www.avisdunet.biz
2nd PC name is : www1.avisdunet.biz

mod_jk2 and apache2 in the first when i start tomcat
my clustering didn't work and i don't know why and in
my logs catalina.out :

10 mai 2004 11:30:15
org.apache.coyote.http11.Http11Protocol init
INFO: Initialisation de Coyote HTTP/1.1 sur le port
8080
10 mai 2004 11:30:17
org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 48211 ms
10 mai 2004 11:30:22
org.apache.catalina.core.StandardService start
INFO: Démarrage du service Catalina
10 mai 2004 11:30:22
org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
10 mai 2004 11:30:23
org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
10 mai 2004 11:30:23
org.apache.catalina.cluster.tcp.SimpleTcpCluster start
INFO: Cluster is about to start
10 mai 2004 11:30:24
org.apache.catalina.cluster.mcast.McastService start
INFO: Sleeping for 2000 secs to establish cluster
membership
10 mai 2004 11:30:26
org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment (
non-jmx )
10 mai 2004 11:30:27
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /pro depuis l'URL
file:/usr/local/java/tomcat/webapps/pro
10 mai 2004 11:30:43
org.apache.catalina.session.StandardManager doLoad
GRAVE: "IOException" lors du chargement des sessions
persistantes: java.io.WriteAbortedException: writing
aborted; java.io.No$
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
com.avisdunet.ServeurFond
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)


Caused by: java.io.NotSerializableException:
com.avisdunet.ServeurFond
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

Resolving to alternate DTD
'file:/usr/local/java/jakarta-tomcat-5.0.19/work/Standalone/localhost/pro/loader/org/apache/strut$
Call
org.apache.struts.action.ActionServlet.addServletMapping(monActionServlet/java.lang.String,*.action/java.lang.String)
Call
org.apache.struts.action.ActionServlet.addServletMapping(action/java.lang.String,*.do/java.lang.String)
10 mai 2004 11:30:56
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte  depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.0.19/weba$
10 mai 2004 11:30:59
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /balancer depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.$
10 mai 2004 11:31:02
org.apache.catalina.core.StandardContext start
GRAVE: Error filterStart
10 mai 2004 11:31:02
org.apache.catalina.core.StandardContext start
GRAVE: Erreur de démarrage du contexte suite aux
erreurs précédentes
10 mai 2004 11:31:02
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /jsp-examples depuis l'URL
file:/usr/local/java/jakarta-tomca$
10 mai 2004 11:31:09
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /servlets-examples depuis l'URL
file:/usr/local/java/jakarta-$
10 mai 2004 11:31:13
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /tomcat-docs depuis l'URL
file:/usr/local/java/jakarta-tomcat$
10 mai 2004 11:31:15
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /webdav depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.0.$
10 mai 2004 11:31:20
org.apache.coyote.http11.Http11Protocol start
INFO: Démarrage de Coyote HTTP/1.1 sur le port 8080
10 mai 2

tomcat clustering

[keita elhadji]

Hi,

i have a problem with mod_jk2 .
I have two PC  with tomcat5.019
1st PC name is : www.avisdunet.biz
2nd PC name is : www1.avisdunet.biz

mod_jk2 and apache2 in the first when i start tomcat
my clustering didn't work and i don't know why and in
my logs catalina.out :

10 mai 2004 11:30:15
org.apache.coyote.http11.Http11Protocol init
INFO: Initialisation de Coyote HTTP/1.1 sur le port
8080
10 mai 2004 11:30:17
org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 48211 ms
10 mai 2004 11:30:22
org.apache.catalina.core.StandardService start
INFO: Démarrage du service Catalina
10 mai 2004 11:30:22
org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
10 mai 2004 11:30:23
org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
10 mai 2004 11:30:23
org.apache.catalina.cluster.tcp.SimpleTcpCluster start
INFO: Cluster is about to start
10 mai 2004 11:30:24
org.apache.catalina.cluster.mcast.McastService start
INFO: Sleeping for 2000 secs to establish cluster
membership
10 mai 2004 11:30:26
org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment (
non-jmx )
10 mai 2004 11:30:27
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /pro depuis l'URL
file:/usr/local/java/tomcat/webapps/pro
10 mai 2004 11:30:43
org.apache.catalina.session.StandardManager doLoad
GRAVE: "IOException" lors du chargement des sessions
persistantes: java.io.WriteAbortedException: writing
aborted; java.io.No$
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
com.avisdunet.ServeurFond
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)


Caused by: java.io.NotSerializableException:
com.avisdunet.ServeurFond
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

Resolving to alternate DTD
'file:/usr/local/java/jakarta-tomcat-5.0.19/work/Standalone/localhost/pro/loader/org/apache/strut$
Call
org.apache.struts.action.ActionServlet.addServletMapping(monActionServlet/java.lang.String,*.action/java.lang.String)
Call
org.apache.struts.action.ActionServlet.addServletMapping(action/java.lang.String,*.do/java.lang.String)
10 mai 2004 11:30:56
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte  depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.0.19/weba$
10 mai 2004 11:30:59
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /balancer depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.$
10 mai 2004 11:31:02
org.apache.catalina.core.StandardContext start
GRAVE: Error filterStart
10 mai 2004 11:31:02
org.apache.catalina.core.StandardContext start
GRAVE: Erreur de démarrage du contexte suite aux
erreurs précédentes
10 mai 2004 11:31:02
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /jsp-examples depuis l'URL
file:/usr/local/java/jakarta-tomca$
10 mai 2004 11:31:09
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /servlets-examples depuis l'URL
file:/usr/local/java/jakarta-$
10 mai 2004 11:31:13
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /tomcat-docs depuis l'URL
file:/usr/local/java/jakarta-tomcat$
10 mai 2004 11:31:15
org.apache.catalina.core.StandardHostDeployer install
INFO: Installation d'une application pour le chemin de
contexte /webdav depuis l'URL
file:/usr/local/java/jakarta-tomcat-5.0.$
10 mai 2004 11:31:20
org.apache.coyote.http11.Http11Protocol start
INFO: Démarrage de Coyote HTTP/1.1 sur le port 8080
10 mai 2004 11:31:25
org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
10 mai 2004 11:31:25 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=85/1005 
config=/usr/local/java/tomcat/conf/jk2.properties
10 mai 2004 11:31:26
org.apache.catalina.startup.Catalina start
INFO: Server startup in 68992 ms
Lectur

tomcat clustering

[shyam]

Hi all,
I am trying to do the clustering . I have tomcat set up on two different
machines. Both these tomcats are joining the cluster. I have checked the
logs and everything looks fine. I tried load balancing with apache2. I
have apache set up on one machine. I have followed the instructions
posted on Jakarta site. The problem is I don't see any session
replication happening. I have checked the tomcat logs and apache logs.
Tomcat logs has a warning. ERROR IN REGISTERING REQUEST. And apache logs
has a error 
[error] ajp13.connect() failed ajp13:localhost:8009
[error] ajp13.service() failed to connect endpoint errno=61 Unknown
error
[error] ajp13.service() Error  forwarding ajp13:localhost:8009 1 1
[error] lb.service() worker failed ajp13:localhost:8009
[error] lb_worker.service() all workers in error or disabled state

Can somebody help me out in this. 
Thanks in advance
shyam

Software Engineer
Adamshand Inc
www.interviewexchange.com






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Shapira, Yoav]

Howdy,

>if 1 server is very powerful, then 1 instance of tomcat would not
utilize
>the full resources available right?

Not necessarily right: depends on the application.  We have apps of
tomcat that efficiently and highly utilize many concurrent threads and
up to 2GB of RAM.

>are there any good IIS -> Tomcat 5 clustering notes anywhere? Or would
the
>built in balancer webapp be useful for single server clustering?

I'm not aware of specific IIS -> Tomcat 5 clustering documentation, but
it might be out there.

The balancer webapp is useful for single server clustering, sure.  As
long as you keep in mind that it's a traffic controller which does not
replicate sessions or data across the instances it controls.  On a
single server, the setup would be:
- Balancer webapp on tomcat installed at the main port, e.g. port 80,
that users use.  The balancer filter is probably mapped to /*.  So this
is a tiny installation with only balancer using a tiny amount of
memory/CPU.

- Other tomcat instances installed on other ports on the same physical
server.  Balancer is configured to forward requests to the appropriate
tomcat instance on the same server according to whatever business rules
make sense.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Allistair Crossley]

hey,

if 1 server is very powerful, then 1 instance of tomcat would not utilize the full 
resources available right? so does a cluster also make sense in this situation so that 
multiple tomcat instances on the same server can benefit an application's performance. 
I appreciate that multiple server clusters allow failover for when a server goes 
under, but i am interested to know if clustering on one server can also be useful to 
utilize more resource. 

are there any good IIS -> Tomcat 5 clustering notes anywhere? Or would the built in 
balancer webapp be useful for single server clustering?

cheers, ADC

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 26 January 2004 14:07
To: Tomcat Users List
Subject: RE: Tomcat clustering



Howdy,
Note that if you simply wish to divide up traffic among servers, not
"cluster" in the purest sense of the word that includes session
replication and failover, then you can easily use the balancer webapp
that ships with tomcat 5.

Yoav Shapira
Millennium ChemInformatics


>-Original Message-
>From: Salvador Santander Gutierrez
>[mailto:[EMAIL PROTECTED]
>Sent: Monday, January 26, 2004 7:49 AM
>To: Tomcat List
>Subject: Tomcat clustering
>
>How can I get some tomcat servers working like a cluster? I means, how
to
>put some tomcat to get load balancing and increment the site
performance.
>Thanks.
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



 
---
QAS Ltd.
Developers of QuickAddress Software
http://www.qas.com";>www.qas.com
Registered in England: No 2582055
Registered in Australia: No 082 851 474
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Shapira, Yoav]

Howdy,
Note that if you simply wish to divide up traffic among servers, not
"cluster" in the purest sense of the word that includes session
replication and failover, then you can easily use the balancer webapp
that ships with tomcat 5.

Yoav Shapira
Millennium ChemInformatics


>-Original Message-
>From: Salvador Santander Gutierrez
>[mailto:[EMAIL PROTECTED]
>Sent: Monday, January 26, 2004 7:49 AM
>To: Tomcat List
>Subject: Tomcat clustering
>
>How can I get some tomcat servers working like a cluster? I means, how
to
>put some tomcat to get load balancing and increment the site
performance.
>Thanks.
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Robert J. Williams Jr.]

Buy the Apache Tomcat Bible by Jon Eaves and published by Wiley.

It has chapters devoted to clustering Tomcat. 

I was able to cluster tomcat with in a few hours 

Bob W. 


-Original Message-
From: Salvador Santander Gutierrez
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 26, 2004 4:49 AM
To: Tomcat List
Subject: Tomcat clustering


How can I get some tomcat servers working like a cluster? I means, how to
put some tomcat to get load balancing and increment the site performance.
Thanks.


-
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]

Re: Tomcat clustering

[jean-philippe . belanger]

For the basic on loadbalancing and architecture check out this article 
from Filip:
http://www.theserverside.com/articles/article.jsp?l=Tomcat

It's nicely done. A little out of date as for the tomcat configuration. 
Since tc 5.x has a whole new clustering engine.

But it should be good enough for you to understand the balancing 
fundamentals.

Jean-Philippe Bélanger
CGI


Salvador Santander Gutierrez wrote:

How can I get some tomcat servers working like a cluster? I means, how to
put some tomcat to get load balancing and increment the site performance.
Thanks.
-
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]

Tomcat clustering

[Salvador Santander Gutierrez]

How can I get some tomcat servers working like a cluster? I means, how to
put some tomcat to get load balancing and increment the site performance.
Thanks.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat clustering and servletContext.

[Antony Paul]

I found your reply in the archives.

Antony Paul

- Original Message -
From: "Shapira, Yoav" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 04, 2003 7:09 PM
Subject: RE: Tomcat clustering and servletContext.



Howdy,
And I did reply yesterday saying the same thing...

Yoav Shapira
Millennium ChemInformatics


>-Original Message-
>From: Antony Paul [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 03, 2003 11:23 PM
>To: Tomcat Users List
>Subject: Tomcat clustering and servletContext.
>
>Hi,
>I asked this question yesterday no one replied.
>Suppose Tomcat is running in a cluster with load balancer. If I put a
>JavaBean in ServletContext is it possible to access this bean in all
>machines ?.
>
>Antony Paul
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


-
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]

Re: Formerly: Tomcat clustering and servletContext.

[Tim Funk]

Neither. All permissions are of the OS user running the process.

-Tim

Hart, Justin wrote:

Ahh, you seem to know a bit about this.

Given that I've authenticated someone, using JNDIRealm, can I then operate with their permissions on the server?  IE, if they authenticate to Tomcat in JNDIRealm, do I get access to files that carry their NT permissions?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Formerly: Tomcat clustering and servletContext.

[Hart, Justin]

Works for me.  Thanks.

Justin

-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 2:23 PM
To: Tomcat Users List
Subject: Re: Formerly: Tomcat clustering and servletContext.


Justin,

> Given that I've authenticated someone, using JNDIRealm, can I then
> operate with their permissions on the server?  IE, if they
> authenticate to Tomcat in JNDIRealm, do I get access to files that
> carry their NT permissions?

Uhh, I'm not entirely sure, but I'd eat my proverbial hat if a user 
logged-in to your web application (using J2EE-style j_security_check, 
right?) and then could access any of their files on the server.

Tomcat should run with a particular user's privs. If you run it as 
Administrator, then you'll open your whole system up to file theft (is 
that your concern?).

You should run Tomcat as a user with very little access. On UNIX 
systems, it's common to either use the "nobody" user or create a user 
under which Tomcat will run.

Tomcat doesn't assume the privs of a user that has successfully 
logged-in to your application. So, you can't use Tomcat as a file-server 
unless it actually is running as Administrator or the user whose files 
you want to read.

There may be a way to authenticate directly with NT and then request 
files through some other mechanism, but you can't just open up a 
FileInputStream to anything you want :)

-chris


-
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]

Re: Formerly: Tomcat clustering and servletContext.

[Christopher Schultz]

Justin,

Given that I've authenticated someone, using JNDIRealm, can I then
operate with their permissions on the server?  IE, if they
authenticate to Tomcat in JNDIRealm, do I get access to files that
carry their NT permissions?
Uhh, I'm not entirely sure, but I'd eat my proverbial hat if a user 
logged-in to your web application (using J2EE-style j_security_check, 
right?) and then could access any of their files on the server.

Tomcat should run with a particular user's privs. If you run it as 
Administrator, then you'll open your whole system up to file theft (is 
that your concern?).

You should run Tomcat as a user with very little access. On UNIX 
systems, it's common to either use the "nobody" user or create a user 
under which Tomcat will run.

Tomcat doesn't assume the privs of a user that has successfully 
logged-in to your application. So, you can't use Tomcat as a file-server 
unless it actually is running as Administrator or the user whose files 
you want to read.

There may be a way to authenticate directly with NT and then request 
files through some other mechanism, but you can't just open up a 
FileInputStream to anything you want :)

-chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Formerly: Tomcat clustering and servletContext.

[Hart, Justin]

Ahh, you seem to know a bit about this.

Given that I've authenticated someone, using JNDIRealm, can I then operate with their 
permissions on the server?  IE, if they authenticate to Tomcat in JNDIRealm, do I get 
access to files that carry their NT permissions?

Justin

-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 1:52 PM
To: Tomcat Users List
Subject: Re: Tomcat clustering and servletContext.


Antony,

> I asked this question yesterday no one replied.
> Suppose Tomcat is running in a cluster with load balancer. If I put a
> JavaBean in ServletContext is it possible to access this bean in all
> machines ?.

No, the ServletContext does not get propagated to other machines. 
Consider using a shared JNDI scope to share this information.

-chris


-
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]

Re: Tomcat clustering and servletContext.

[Christopher Schultz]

Antony,

I asked this question yesterday no one replied.
Suppose Tomcat is running in a cluster with load balancer. If I put a
JavaBean in ServletContext is it possible to access this bean in all
machines ?.
No, the ServletContext does not get propagated to other machines. 
Consider using a shared JNDI scope to share this information.

-chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering and servletContext.

[Shapira, Yoav]

Howdy,
And I did reply yesterday saying the same thing...

Yoav Shapira
Millennium ChemInformatics


>-Original Message-
>From: Antony Paul [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 03, 2003 11:23 PM
>To: Tomcat Users List
>Subject: Tomcat clustering and servletContext.
>
>Hi,
>I asked this question yesterday no one replied.
>Suppose Tomcat is running in a cluster with load balancer. If I put a
>JavaBean in ServletContext is it possible to access this bean in all
>machines ?.
>
>Antony Paul
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat clustering and servletContext.

[Antony Paul]

Thanks
- Original Message -
From: "Tim Funk" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 04, 2003 5:45 PM
Subject: Re: Tomcat clustering and servletContext.


> AFAIK, only sessions are replicated. Attributes in the Servlet Context are
> not replicated.
>
> -Tim
>
> Antony Paul wrote:
> > Hi,
> > I asked this question yesterday no one replied.
> > Suppose Tomcat is running in a cluster with load balancer. If I put a
> > JavaBean in ServletContext is it possible to access this bean in all
> > machines ?.
>
>
> -
> 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]

Re: Tomcat clustering and servletContext.

[Tim Funk]

AFAIK, only sessions are replicated. Attributes in the Servlet Context are 
not replicated.

-Tim

Antony Paul wrote:
Hi,
I asked this question yesterday no one replied.
Suppose Tomcat is running in a cluster with load balancer. If I put a
JavaBean in ServletContext is it possible to access this bean in all
machines ?.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat clustering and servletContext.

[Antony Paul]

Hi,
I asked this question yesterday no one replied.
Suppose Tomcat is running in a cluster with load balancer. If I put a
JavaBean in ServletContext is it possible to access this bean in all
machines ?.

Antony Paul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat clustering

[Neil Aggarwal]

Bern:

We are using clustering on Tomcat 4.

Actually, at the current time, we are working with Filip Hanik
to track down a performance problem with the clustering code.

Let me know what I can do to help you.

Thanks,
Neil

--
Neil Aggarwal, JAMM Consulting, (972)612-6056, www.JAMMConsulting.com
FREE! Valuable info on how your business can reduce operating costs by 
17% or more in 6 months or less! => http://newsletter.JAMMConsulting.com

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, September 27, 2003 10:03 AM
> To: Tomcat Users List
> Subject: Tomcat clustering
> 
> 
> Hi,   has anybody tried clustering Tomcat?  I have read this 
> article 
> http://www.onjava.com/pub/a/onjava/2002/07/17/tomcluster.html 
>  but has been able to successfully configure this.
> 
> Thanks for any help.
> 
> Bern
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat clustering

[[EMAIL PROTECTED]]

Hi,   has anybody tried clustering Tomcat?  I have read this article 
http://www.onjava.com/pub/a/onjava/2002/07/17/tomcluster.html  but has been able to 
successfully configure this.

Thanks for any help.

Bern

RE: Session Problems in Tomcat Clustering

[Filip Hanik]

is this class in all your webapps?
can you send me a test case webapp and I will try it out

> -Original Message-
> From: Mandeep Jossan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 11, 2003 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: Session Problems in Tomcat Clustering
>
>
> Iam using the Tomcat 4.1.24 clustering with apache 2.0.43.
> everything seems to work fine, many many thanks to Filip for the
> fine work. But I have a problem when I try to save a session
> notifier called 'SessionTimeoutNotifier' which extends
> 'HttpSessionBindingListener' in the session. First it said it is
> not serializable so I implemented java.io.Serializable and it
> accepted it. But now when the session is replicated to the other
> Tomcat server in the cluster then it says cannot unserialize
> because the file SessionTimeoutNotifier is missing. But the file
> is right there but I don't know why the Replication manager
> cannot load it. I think it has some class loading problems.
> I am pretty sure that I have the SessionTimeoutNotifier.class
> file under both the Tomcat under the same directory.
> Iam getting the following exception
> --
> [InMemoryReplicationManager] Failed to
> deserialize the session!
> java.lang.ClassNotFoundException:
> com.checkfree.login.SessionTimeoutNotifier
> at
> org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClas
> sLoader.java:992)
> at
> org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClas
> sLoader.java:857)
> at
> org.apache.catalina.session.ReplicationStream.resolveClass(Replicatio
> nStream.java:124)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:150
> 3)
> at
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1425)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
> 616)
> at
> java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264)
> at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)
> at
> org.apache.catalina.session.StandardSession.readObject(StandardSessio
> n.java:1369)
> at
> org.apache.catalina.session.StandardSession.readObjectData(StandardSe
> ssion.java:864)
> at
> org.apache.catalina.session.ReplicatedSession.readObjectData(Replicat
> edSession.java:336)
> at
> org.apache.catalina.session.InMemoryReplicationManager.readSession(In
> MemoryReplicationManager.java:555)
> at
> org.apache.catalina.session.InMemoryReplicationManager.messageReceive
> d(InMemoryReplicationManager.java:859)
> at
> org.apache.catalina.session.InMemoryReplicationManager.messageDataRec
> eived(InMemoryReplicationManager.java:943)
> at
> org.apache.catalina.cluster.ObjectReader.append(ObjectReader.java:45)
> at
> org.apache.catalina.cluster.WorkerThread.drainChannel(WorkerThread.ja
> va:121)
> at
> org.apache.catalina.cluster.WorkerThread.run(WorkerThread.java:60)
> [InMemoryReplicationManager] Unable to receive message through TCP channel
> java.lang.NullPointerException
> at
> org.apache.catalina.session.InMemoryReplicationManager.messageReceive
> d(InMemoryReplicationManager.java:860)
> at
> org.apache.catalina.session.InMemoryReplicationManager.messageDataRec
> eived(InMemoryReplicationManager.java:943)
> at
> org.apache.catalina.cluster.ObjectReader.append(ObjectReader.java:45)
> at
> org.apache.catalina.cluster.WorkerThread.drainChannel(WorkerThread.ja
> va:121)
> at
> org.apache.catalina.cluster.WorkerThread.run(WorkerThread.java:60)
> Sep 11, 2003 11:42:26 AM org.apache.jk.common.ChannelSocket
> processConnection
> INFO: connection timeout reached
> Sep 11, 2003 11:42:45 AM org.apache.jk.common.ChannelSocket
> processConnection
> INFO: connection timeout reached
> --
> ---
>
>
>
> -
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Session Problems in Tomcat Clustering

[Mandeep Jossan]

Iam using the Tomcat 4.1.24 clustering with apache 2.0.43. everything seems to work 
fine, many many thanks to Filip for the fine work. But I have a problem when I try to 
save a session notifier called 'SessionTimeoutNotifier' which extends 
'HttpSessionBindingListener' in the session. First it said it is not serializable so I 
implemented java.io.Serializable and it accepted it. But now when the session is 
replicated to the other Tomcat server in the cluster then it says cannot unserialize 
because the file SessionTimeoutNotifier is missing. But the file is right there but I 
don't know why the Replication manager cannot load it. I think it has some class 
loading problems.
I am pretty sure that I have the SessionTimeoutNotifier.class file under both the 
Tomcat under the same directory.
Iam getting the following exception
--[InMemoryReplicationManager]
 Failed to deserialize the session!
java.lang.ClassNotFoundException: com.checkfree.login.SessionTimeoutNotifier
at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClas
sLoader.java:992)
at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClas
sLoader.java:857)
at org.apache.catalina.session.ReplicationStream.resolveClass(Replicatio
nStream.java:124)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:150
3)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1425)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
616)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322)
at org.apache.catalina.session.StandardSession.readObject(StandardSessio
n.java:1369)
at org.apache.catalina.session.StandardSession.readObjectData(StandardSe
ssion.java:864)
at org.apache.catalina.session.ReplicatedSession.readObjectData(Replicat
edSession.java:336)
at org.apache.catalina.session.InMemoryReplicationManager.readSession(In
MemoryReplicationManager.java:555)
at org.apache.catalina.session.InMemoryReplicationManager.messageReceive
d(InMemoryReplicationManager.java:859)
at org.apache.catalina.session.InMemoryReplicationManager.messageDataRec
eived(InMemoryReplicationManager.java:943)
at org.apache.catalina.cluster.ObjectReader.append(ObjectReader.java:45)
at org.apache.catalina.cluster.WorkerThread.drainChannel(WorkerThread.ja
va:121)
at org.apache.catalina.cluster.WorkerThread.run(WorkerThread.java:60)
[InMemoryReplicationManager] Unable to receive message through TCP channel
java.lang.NullPointerException
at org.apache.catalina.session.InMemoryReplicationManager.messageReceive
d(InMemoryReplicationManager.java:860)
at org.apache.catalina.session.InMemoryReplicationManager.messageDataRec
eived(InMemoryReplicationManager.java:943)
at org.apache.catalina.cluster.ObjectReader.append(ObjectReader.java:45)
at org.apache.catalina.cluster.WorkerThread.drainChannel(WorkerThread.ja
va:121)
at org.apache.catalina.cluster.WorkerThread.run(WorkerThread.java:60)
Sep 11, 2003 11:42:26 AM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Sep 11, 2003 11:42:45 AM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
-
 


-
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

RE: Tomcat clustering

[Filip Hanik]

sent to tomcat-user for archiving purposes.

> the Tomcat
> 5.x source code and judicious use of a decompiler we've managed to build

why did you need to decompile it only to compile it again? I've already give
you a compiled version for tomcat-replication.jar. interested to hear the
reply on this one.
I have the source code at home, can send it to you next week if you are
interested.

> From looking at the code I can see that things have changed somewhat since
> your original article on the TheServerSide and you've abandoned using

Several reasons:
- TCP is faster than UDP, and reliability is built in.
- The JavaGroups license is not accepted into Tomcat source (main reason)
- Different replication schema, replicates at the end of the request, not on
every attribute change.
- Synchronous replication, don't let the user go until the replication is
done ( in the future this might change) and hence reduce the risk of the
stuff that can happen when you don't have distributed locking in place.

> I wondered what your thoughts were on the sending of deltas rather than
> replicating the entire session. I see that you've allowed for

interesting idea, might be a future feature. For now there is a "isDirty"
flag that if set only replicates when attributes actually change.
If isDirty=false the following code would also work

HashMap map = session.getAttribute("map");
map.put("data",data);

hence allows developers to instantly have session replication without
finding the traps.
only replicating deltas, won't work in this scenario.

> How about session locking, that is when a session is accessed on
> one server

the only locking we do is synchronous replication, but other than that, you
are talking about a wormhole for performance problems. I rather not do that
right now, maybe in the future.

> Also we're interested in only replicating those attributes at the
> end of the

tomcat-replication.jar does this already, except it replicates the entire
session. see above for reasoning on deltas.

Filip



> -Original Message-
> From: Yao Ng [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 9:37 AM
> To: 'Filip Hanik'
> Cc: Sam Wilson
> Subject: RE: Tomcat clustering
>
>
> Hi Filip,
>
> Thanks for your prompt reply. Through a combination of looking at
> the Tomcat
> 5.x source code and judicious use of a decompiler we've managed to build
> from source a version of your tomcat-replication.jar and got it
> working very
> nicely with two instances of Tomcat 4.1.24. Great work!
>
> From looking at the code I can see that things have changed somewhat since
> your original article on the TheServerSide and you've abandoned using
> JavaGroups in favour of writing your own custom multicast and TCP/IP
> transports. What was the motivation for doing this? Haven't you lost the
> ability to configure the protocol stack depending on your network's
> requirements? Admittedly, the codebase is now much smaller and I daresay
> leaner. Also it benefits from not having dependencies on
> JavaGroups and it's
> parents.
>
> I wondered what your thoughts were on the sending of deltas rather than
> replicating the entire session. I see that you've allowed for
> SessionMessage
> types SESSION-ATTRIBUTE-ADDED and
> SESSION-ATTRIBUTE-REMOVED-WITH-NOTIFY but
> you only send SESSION-CREATED and SESSION-GET-ALL message types
> at present.
> The reason I ask is that in our applications the sessions could get fairly
> large (not ideal I know) and we'd rather just broadcast the session
> attributes that are modified.
>
> Also we're interested in only replicating those attributes at the
> end of the
> request rather than sending messages every time the servlet code
> needlessly
> modifies the session during the request (we might not have
> control over what
> other developers do in their servlet code).
>
> How about session locking, that is when a session is accessed on
> one server
> it broadcasts a lock message to prevent the same session being accessed on
> the other cluster nodes until the request has been serviced? This might be
> useful in safeguarding against situations when the user
> double-clicks on his
> browser and makes the same request twice. Clearly the expiring of session
> locks and how you wait for a lock to become released are important
> considerations.
>
> I'd be very interested in your thoughts on these matters and if you can
> think of any obvious pitfalls in implementing such features.
>
> Thanks for your input.
>
> Yao
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]