Re: Session replication will never happen after disabling session persistence across Tomcat restarts

Yes, I think if uncommented the The ClustedManage could be disabled even if is defined. 在 16/4/25 下午12:57, Keiichi Fujino 写道: 2016-04-23 15:29 GMT+09:00 sanigo : Hi! I have tested quite a few times to confirm that session replication will not happen after

Re: Session replication will never happen after disabling session persistence across Tomcat restarts

2016-04-23 15:29 GMT+09:00 sanigo : > Hi! >I have tested quite a few times to confirm that session replication > will not happen after uncommenting in > conf/context.xml. >If the line is commented out, the session replication will work > happily. > Is there a

Re: Session replication/fail-over for medium sized tomcat farm

On Fri, Jul 3, 2015 at 9:17 AM, Charles Richard charle...@thelearningbar.com wrote: On Fri, Jul 3, 2015 at 9:58 AM, Daniel Mikusa dmik...@pivotal.io wrote: On Fri, Jul 3, 2015 at 8:36 AM, Charles Richard charle...@thelearningbar.com wrote: Hi, We are currently using a product

Re: Session replication/fail-over for medium sized tomcat farm

On Fri, Jul 3, 2015 at 9:58 AM, Daniel Mikusa dmik...@pivotal.io wrote: On Fri, Jul 3, 2015 at 8:36 AM, Charles Richard charle...@thelearningbar.com wrote: Hi, We are currently using a product called Terracotta to do session fail-over/replication but are considering moving away from

Re: Session replication/fail-over for medium sized tomcat farm

On Fri, Jul 3, 2015 at 8:36 AM, Charles Richard charle...@thelearningbar.com wrote: Hi, We are currently using a product called Terracotta to do session fail-over/replication but are considering moving away from this product as it doesn't seem to support Java 7 and Tomcat 7. What products

Re: Session Replication across common base domain

Hi Guys, Any solution for this?? On 03-01-2014 02:31 PM, Sanket Paranjape wrote: Hi, I am using Tomcat 7.0.47 on windows 7 with JDK 1.7. I want to achieve session replications on multiple subdomains. If I have a domain as xyz.example.com and abc.example.com, then I would like to store

Re: Session replication configuration file question

Hi Daniel, At last we managed to solve the replication issue. (not exactly a solution but a workaround) : the problem was: The multicast tried to broadcast to local ip written in the hosts file 127.0.1.1 We had to write the actual ip adress in the hosts file instead : 127.0.1.1 - Tomcat1 we

Re: Session replication does not work - Continued

On Dec 29, 2013, at 10:11 AM, Nir A n...@netomedia.com wrote: Hi, So we have 3 tomcats in our cluster and we are failing to make them replicate our sessions still. Our IT guy said it might has something to do with the machines of the tomcats. He said that since the machines the tomcats

Re: Session replication configuration file question

On Dec 29, 2013, at 10:51 AM, Nir A n...@netomedia.com wrote: Hi, If i want to create a cluster of 2 tomcats: Tomcat1 - ip 111.111.111.111 Tomcat2 - ip 222.222.222.222 Where exactly the in the server.xml i should say that my cluster contains both of these ips? By default, you

Re: session replication issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dhaval, On 12/9/13, 3:04 PM, Dhaval Jaiswal wrote: setting of session replication worked well. However, we do have threading in some products. Like we are hitting the target API and getting response from there servers. If will not get the

Re: session-replication fails on restart or kill

On 27/08/2013 23:02, Tomcat Random wrote: NP, glad to contribute a little. The FAQ was helpful but it's a little confusing. I'd like to clean it up and add to the part that specifically addresses two boxes two nodes on Linux. Would that be alright? Sure. You'll need to create an account on the

Re: session-replication fails on restart or kill

In a great moment of DUH, I realized I had the expireSessionsOnShutdown to true. Manager className=org.apache.catalina.ha.session.DeltaManager expireSessionsOnShutdown=false notifyListenersOnReplication=true/ All working nicely now.

Re: session-replication fails on restart or kill

On 27/08/2013 22:41, Tomcat Random wrote: In a great moment of DUH, I realized I had the expireSessionsOnShutdown to true. Manager className=org.apache.catalina.ha.session.DeltaManager expireSessionsOnShutdown=false

Re: session-replication fails on restart or kill

NP, glad to contribute a little. The FAQ was helpful but it's a little confusing. I'd like to clean it up and add to the part that specifically addresses two boxes two nodes on Linux. Would that be alright? Thanks, Alec On Tue, Aug 27, 2013 at 5:52 PM, Mark Thomas ma...@apache.org wrote: On

Re: Session Replication

What do you need to know ? Un abrazo 2013/2/23 Technical Support techsupp...@brainstalk.com Hi, Im beginner in Linux. Can anyone help me develop my skills in Linux? Regards Chak Teylor On Sat, Feb 23, 2013 at 2:27 AM, Dhaval Jaiswal dhaval.jais...@via.com wrote: I am creating

Re: Session Replication

On Feb 22, 2013, at 1:27 PM, Dhaval Jaiswal wrote: I am creating cluster of 3 tomcats (Version 6) for session replication with the following changes in server.xml Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster channelSendOptions=6/ Manager

Re: Session Replication

Hi, Im beginner in Linux. Can anyone help me develop my skills in Linux? Regards Chak Teylor On Sat, Feb 23, 2013 at 2:27 AM, Dhaval Jaiswal dhaval.jais...@via.comwrote: I am creating cluster of 3 tomcats (Version 6) for session replication with the following changes in server.xml Cluster

Re: Session replication problem

On 22/03/2012 08:16, Andy Chapman wrote: Hi All, I'm using tribes session replication between two Tomcat 7 servers and getting errors as below. There are various possible causes: 1. The Tomcat versions are different (7.0.4 and 7.0.20) It is this one. Mark

Re: Session replication problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy, On 3/22/12 4:16 AM, Andy Chapman wrote: 1. The Tomcat versions are different (7.0.4 and 7.0.20) Note that Tomcat 7.0.6 was the first non-beta version of Tomcat 7. You should definitely upgrade the 7.0.4 version to 7.0.20 and I suspect things

Re: Session replication fails with Member send is failing

On 12/7/2011 9:04 AM, Jürgen Link wrote: Caused by: org.apache.catalina.tribes.RemoteProcessException: Received a failedack:org.apache.catalina.tribes.transport.Constants.FAIL_ACK_DATA sure thing, this is actually telling the sender that an exception happened on the receiver end. Take a look

Re: session replication question in 7.0.10

Hi Mark, This SessionExample http://bml0065.yalepath.org/tc/examples/servlets/servlet/SessionExample Sorry for the mistype I have a sticky keyboard and I try to live with it. Sorry for the comment.. Ultimately it was my fault because I left out the distributable tag from one the web.xml.

Re: session replication question in 7.0.10

On 21/03/2011 21:34, János Löbb wrote: Hi, I have two machines MachineA and MachineB with osx 10.6.6 on them. Both machines have one tomcat 7.0.10 running. On both machine the server.xml was modified minimally: - Uncommented the Cluster tag - added jvmRoute=tomcat(x) to the

Re: session replication question in 7.0.10

Sorry for the noise, one of the web.xml did not have the distributable/ tag :( Now it is working fine. János On Mar 21, 2011, at 5:34 PM, János Löbb wrote: Hi, I have two machines MachineA and MachineB with osx 10.6.6 on them. Both machines have one tomcat 7.0.10 running. On both

RE: Session replication fails on ReplicationValve invocation

undefined area? Thanks, Dave -- David Nillesen UNIX Systems Administrator Ph: + 61 2 6773 2112 -Original Message- From: Martin Gainty [mailto:mgai...@hotmail.com] Sent: Thursday, 18 June 2009 12:06 PM To: Tomcat Users List Subject: RE: Session replication fails

Re: Session replication question

make sure your clocks are synced across all machines, since session expiration is time based Filip On 12/23/2010 8:22 AM, Jorge Santiago Cruz Lambert wrote: Hi! I'm not an expert on Tomcat and we purchase a load balancer service with two tomcat 6.0.29 instances in separate Ubuntu servers

Re: Session replication question

Thanks for replying, I'm cheking the time in our machines and they are the same, but in different time zones: Machine 1: Thu Dec 23 17:18:40 CET 2010 Machine 2: Thu Dec 23 16:18:40 UTC 2010 Do I need to change the timezone in Machine 2? I think the time is the same and ntp is running as process.

Re: Session replication question

Thanks for replying, I'm cheking the time in our machines and they are the same, but in different time zones: Machine 1: Thu Dec 23 17:18:40 CET 2010 Machine 2: Thu Dec 23 16:18:40 UTC 2010 Do I need to change the timezone in Machine 2? I think the time is the same and ntp is running as

Re: Session replication with multicast

Actually, it works without it, just forgot to add distributable / in my web.xml. 2010/11/29 Filip Hanik - Dev Lists devli...@hanik.com: alternatively, try to add -Djava.net.preferIPv4Stack=true to your JVM args On 11/26/2010 06:36 AM, Guillaume HERAIL wrote: Hi, OS : Debian lenny

Re: Session replication with multicast

I found my mistake, i forgot to add distributable / in my web.xml. Anyway, i've updated tomcat on my boxes. Thanks, 2010/11/27 Christopher Schultz ch...@christopherschultz.net: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guillaume, (Apologies for the top-post, but these are general

Re: Session replication with multicast

On 11/26/2010 06:36 AM, Guillaume HERAIL wrote: Hi, OS : Debian lenny Tomcat : 7.0.2 JRE : 1.6.0_21 I have a problem trying to clusterize two tomcat on two different boxes. I want to use the MemberShip's argument bind to tell to tomcat wich interface to use but i get an exception :

Re: Session replication with multicast

alternatively, try to add -Djava.net.preferIPv4Stack=true to your JVM args On 11/26/2010 06:36 AM, Guillaume HERAIL wrote: Hi, OS : Debian lenny Tomcat : 7.0.2 JRE : 1.6.0_21 I have a problem trying to clusterize two tomcat on two different boxes. I want to use the MemberShip's argument

Re: Session replication with multicast

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guillaume, (Apologies for the top-post, but these are general comments) I don't know anything about Tomcat's clustering, but I do know that Tomcat 7 has had a few releases since 7.0.2. 7.0.5 was just recently tagged and might be released next week.

Re: Session replication: Channel.SEND_OPTIONS_SECURE

On 03/23/2010 09:46 AM, Tom wrote: On Tue, Mar 23, 2010 at 1:58 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Tom [mailto:808...@gmail.com] Subject: Session replication: Channel.SEND_OPTIONS_SECURE There is little documentation about Channel.SEND_OPTIONS_SECURE

RE: Session replication: Channel.SEND_OPTIONS_SECURE

From: Tom [mailto:808...@gmail.com] Subject: Session replication: Channel.SEND_OPTIONS_SECURE There is little documentation about Channel.SEND_OPTIONS_SECURE From a brief glance at the code, SEND_OPTIONS_SECURE appears to be defined, but not yet implemented - which would explain the

Re: Session replication: Channel.SEND_OPTIONS_SECURE

On Tue, Mar 23, 2010 at 1:58 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Tom [mailto:808...@gmail.com] Subject: Session replication: Channel.SEND_OPTIONS_SECURE There is little documentation about Channel.SEND_OPTIONS_SECURE From a brief glance at the code,

Re: Session replication using only PersistenceManager + JDBCStore

Thanks for your detailed answer, I will probably go with in-memory replication. Regading your last question, I have one database instance sitting on top of a 2 node DRBD. 2009/6/17 Christopher Schultz ch...@christopherschultz.net: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yves, On

Re: Session replication without Apache

Manu_SF wrote: Hi, I have a working prototype tomcat cluster with 2 worker nodes connected to Apache webserver as the Loadbalancer with mod_jk connectors. The session replication works like a charm with these 2 nodes. However, my ultimate goal is to deploy it over a system that does NOT have

Re: Session replication without Apache

On 06.07.2009 20:33, Manu_SF wrote: Hi, I have a working prototype tomcat cluster with 2 worker nodes connected to Apache webserver as the Loadbalancer with mod_jk connectors. The session replication works like a charm with these 2 nodes. However, my ultimate goal is to deploy it over a

Re: Session replication fails on ReplicationValve invocation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 6/18/2009 12:03 AM, David Nillesen wrote: I think I may have sorted the problem. Would that have occurred if I was asking for a webpage without a context? i.e. just hitting some undefined area? All requests are handled by /some/

Re: Session replication using only PersistenceManager + JDBCStore

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yves, On 6/17/2009 6:04 AM, Yves Glodt wrote: In my setup are 4 apaches with mod_proxy which connect to 4 tomcats. In front of the apaches is a hardware balancer which does round-robin, but with a kind of sticky TCP-sessions, so mostly the

RE: Session replication fails on ReplicationValve invocation

Hello Dave that line from ReplicationManager is getManager() Manager manager = request.getContext().getManager(); i would check to make sure the Manager node in /context.xml !-- The contents of this file will be loaded for each web application -- Context !-- Default set of

RE: Session replication fails on ReplicationValve invocation

...@hotmail.com] Sent: Thursday, 18 June 2009 12:06 PM To: Tomcat Users List Subject: RE: Session replication fails on ReplicationValve invocation Hello Dave that line from ReplicationManager is getManager() Manager manager = request.getContext().getManager(); i would check to make sure

Re: Session Replication problem

no all operating systems support a bind address for multicast sockets socket = new MulticastSocket(new InetSocketAddress(address,port)); Filip sudhakar p wrote: Hi I am trying to configure Clustering/Session Replication in Tomcat 6.0.18 and am getting this message when I start the tomcat

Re: Session Replication problem

Hi Filip, Thanks for your reply My server OS is Linux Red Hat Enterprise Linux Server release 5.3 which will be support MULTICAST. Please help to fix the problem Thanks in Advance Raju On Fri, May 8, 2009 at 8:50 AM, Filip Hanik - Dev Lists devli...@hanik.comwrote: no all operating

Re: Session Replication problem

I don't think Linux supports binding to an interface for multicast. Multicast still works, you just can't bind it, instead you setup your routing table to make sure you route it the way you want. the other way you can do is setup static memberships, where you define your tomcat instances

Re: Session Replication problems

we'd need the entire stacktrace, not just a snippet for it to be helpful to us. Filip Mohamedin wrote: Dear All, I use these configuration to enable session replication: Master server: Engine name=Catalina defaultHost=localhost jvmRoute=master Cluster

Re: Session Replication in Cluster

what you're seeing is correct. the server did fail over, and by changing the session id, it ensures that it does not do fail back Filip Roy McMorran wrote: Hello all, I've built a very simple 2-member Tomcat cluster for testing, but I am unable to get the session replication quite right.

Re: Session Replication in Cluster

To stick with the analogy: Your session's baby part is: FEBA6A8127A69079C79B7A641158CE20 and that remains the same if with daddy or mommy. Your session's daddy part is: itchy and Your session's mommy part is: scratchy Enjoy them :) János On Apr 3, 2009, at 5:32 PM, Roy McMorran wrote:

Re: Session Replication in Cluster

Hi Jorge, thanks for the reply. Actually no, these are the access logs from the Tomcat cluster members; you can view the corresponding AccessLogValve entries in the server.xml files referenced below. I included those logs for illustration, but I have confirmed that those are the actual

Re: Session Replication in Cluster

Roy McMorran wrote: Hi Jorge, thanks for the reply. Actually no, these are the access logs from the Tomcat cluster members; you can view the corresponding AccessLogValve entries in the server.xml files referenced below. I included those logs for illustration, but I have confirmed that

Re: Session Replication in Cluster

Mark Thomas wrote: Nope. The job of that valve is to change the route - exactly what you are seeing. Thanks Mark, Is it the expected behavior then, that the 2nd part of the session ID changes after a failover, and a new cookie is set? Thanks, Roy -- Roy McMorran Systems Administrator

Re: Session Replication in Cluster

Roy McMorran wrote: Mark Thomas wrote: Nope. The job of that valve is to change the route - exactly what you are seeing. Thanks Mark, Is it the expected behavior then, that the 2nd part of the session ID changes after a failover, and a new cookie is set? Yes Mark

Re: Session Replication in Cluster

Mark Thomas wrote: Roy McMorran wrote: Thanks Mark, Is it the expected behavior then, that the 2nd part of the session ID changes after a failover, and a new cookie is set? Yes Mark Interesting. I am certain I saw the other behavior (both parts of the session ID were

Re: Session Replication in Cluster

Mark Thomas wrote: Roy McMorran wrote: Is it the expected behavior then, that the 2nd part of the session ID changes after a failover, and a new cookie is set? Yes OK, please bear with me here, I may be just showing my ignorance with respect to Tomcat and web applications in

RE: Session Replication in Cluster

From: Roy McMorran [mailto:mcmor...@mdibl.org] Subject: Re: Session Replication in Cluster If the session ID changes from ABC123.node1 to ABC123.node2, then you will start a new session at the browser. No, you get a new *cookie* at the browser; the session is something only the server has

Re: Session Replication in Cluster

On Apr 3, 2009, at 3:31 PM, Roy McMorran wrote: Mark Thomas wrote: Roy McMorran wrote: Is it the expected behavior then, that the 2nd part of the session ID changes after a failover, and a new cookie is set? Yes OK, please bear with me here, I may be just showing my ignorance

Re: Session Replication in Cluster

Caldarale, Charles R wrote: From: Roy McMorran [mailto:mcmor...@mdibl.org] Subject: Re: Session Replication in Cluster If the session ID changes from ABC123.node1 to ABC123.node2, then you will start a new session at the browser. No, you get a new *cookie* at the browser; the session

Re: Session Replication in Cluster

János Löbb wrote: If You look the values created by the session earlier with ...node1, than You will see the same values after fail over with ...node2. A new session would not know about them. To verify it You can use the supplied SessionExmaple webapp. It is like passing a baby among

Re: Session Replication in Cluster

János Löbb wrote: If You look the values created by the session earlier with ...node1, than You will see the same values after fail over with ...node2. A new session would not know about them. To verify it You can use the supplied SessionExmaple webapp. OK, trying that. So, using an

Re: Session Replication in Cluster

Roy McMorran wrote: János Löbb wrote: If You look the values created by the session earlier with ...node1, than You will see the same values after fail over with ...node2. A new session would not know about them. To verify it You can use the supplied SessionExmaple webapp. OK, trying

RE: Session Replication in Cluster

Are your logs Apache logs? Mod_jk logs? If it is Apache, the question would probably better answer in the Apache mailing list. Anyway, What does your LogFormat string looks like? I bet what you see in the logs is the concatenation of the session ID and the worker name. I doubt two servers

Re: Session replication problem

, February 10, 2009 4:10 AM Subject: Re: Session replication problem Mohamedin wrote: I have a problem with Session replication. I am running multible tomcat instance on the same server. And I have 4 servers of the same configuration (Multible tomcat instances). I have enabled the session

Re: Session replication problem

devli...@hanik.com To: Tomcat Users List users@tomcat.apache.org Sent: Tuesday, February 10, 2009 4:10 AM Subject: Re: Session replication problem Mohamedin wrote: I have a problem with Session replication. I am running multible tomcat instance on the same server. And I have 4 servers of the same

Re: Session replication problem

Mohamedin wrote: I have a problem with Session replication. I am running multible tomcat instance on the same server. And I have 4 servers of the same configuration (Multible tomcat instances). I have enabled the session replication on these 4 servers (In each instance with different port).

RE: Session replication/sharing across WARs?

From: Robert Campbell [mailto:rrc...@gmail.com] Subject: Session replication/sharing across WARs? This means that I need single sign-on/share session between the two apps. Both WARs will be deployed on the same Tomcat 5.5 instance, It's in the docs:

Re: Session replication for JPetStore application in tomcat 6

Anupam I think this is probably your problem. You create and save information in one node and then look to see if it is in the other node. It will only be there if you are independently synchronizing the database state, because, as you said in your previous emails, they are independent. The

Re: Session replication for JPetStore application in tomcat 6

Thanks a lot Filip ! Well I tried to set up the log4j.properties at the server as well as the application level to include these categories but it dosent seem to work, i.e I couldnt see the traces specific to sessions . Is there any specific trace that could enable the sessionID to appear in

Re: Session replication for JPetStore application in tomcat 6

looks like its working, what is it that you don't think is working or would like help with? 6 nov. 2008 17:08:30 org.apache.catalina.ha.session.DeltaManager getAllClusterSessions ATTENTION: Manager [localhost#/jpetstore], requesting session state from

Re: Session replication for JPetStore application in tomcat 6

Hello Filip, Thanks a lot for your reply. From the logs , the session state send is evident .The scenario i tried is as follows I opened the application web page on the first node via my browser , logged in , did some operations like some additions and modifications. I displayed the

Re: Session replication for JPetStore application in tomcat 6

you could enable tracing for the two following categories org.apache.catalina.ha org.apache.catalina.tribes.MESSAGES Filip Anupam Beri wrote: Hello Filip, Thanks a lot for your reply. From the logs , the session state send is evident .The scenario i tried is as follows I opened the

Re: Session Replication question

useDirtyFlag is supposed to be the SimpleTcpManager, DeltaManager always only replicates deltas. so does the backup manager. The two managers that work best are DeltaManager and BackupManager, both of them replicate upon setAttribute/removeAttribute actions. DeltaManager replicates to all other

RE: session replication / cluster groups

I believe this segregation is typically done with instances of multiple load balancers. I'm not an expert on the mod_jk stuff, but you'd probably want to implement this with multiple load balancers regardless, when you're getting up to that many instances. Bear in mind that this piece of your

Re: session replication / cluster groups

you could use the BackupManager this only replicates data to one backup node http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-manager.html and you can fail over to any node, it will fetch the backup from the backup node Filip Kevin Phillips wrote: Hi, I have tomcat clustering working

Re: Session replication problem in tomcat 6.0.14 (loadbalancing with Apache)

the error should be fixed in 6.0.18 Filip Pavan Singaraju wrote: My question here was if the other node is not available anymore, will this exception come? If so how to avoid it. The fact is the session replication is happenning and everything is working inspite of the exception. But just in

Re: Session replication problem in tomcat 6.0.14 (loadbalancing with Apache)

this Jul 30, 2008 1:49:24 PM org.apache.catalina.ha.tcp.SimpleTcpCluster memberDisappeared INFO: Received member disappeared:org.apache.catalina.tribes.membership.MemberImpl[tcp://d5-4232.xius.ltd:4002,d5-4232.xius.ltd,4002, alive=46858,id={-38 -119 -88 -15 -57 -62 77 116 -98 -70 -92 -50 45 -83

Re: Session replication problem in tomcat 6.0.14 (loadbalancing with Apache)

My question here was if the other node is not available anymore, will this exception come? If so how to avoid it. The fact is the session replication is happenning and everything is working inspite of the exception. But just in case if we want to avoid this exception, is there a way or should the

Re: Session replication problem

The problem reported below was due to a misconfiguration. In the past I disabled the session persistence uncommenting the manager row in context.xml : Manager pathname= / After session persistance's activation (commenting the row above) session replication works as expected. Giancarlo Frison

Re: Session replication problem

excellent, yes, you are overriding the clustering manager if you define one yourself thanks for reporting back! Filip Giancarlo Frison wrote: The problem reported below was due to a misconfiguration. In the past I disabled the session persistence uncommenting the manager row in context.xml :

Re: Session replication problem

Hi all, This is the catalina.out. I read the post about session expiration during shutdown, so I tried to kill -9 the process to avoid any unexpected behavior but the outcome is the same, no session replication. What I may do? I appreciate any suggestion. Thanks! INFO: Starting Servlet Engine:

Re: Session replication problem

you can turn debug on and see the messages being sent back and forth. a previous user reported that sessions got expired during a normal shutdown, I yet have to investigate this Filip Giancarlo Frison wrote: Hi all, I have a cluster configured with 2 tomcat instaces in the same host and

Re: Session Replication

Andrew Hole wrote: Hello everyone! For using Tomcat session clustering I need to put the following component in all nodes? Yes, obviously. Any node without a cluster definition won't know that it's supposed to be in a cluster without it... I don't suppose you've read the docs on

Re: Session Replication

yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Filip Andrew Hole wrote: Hello everyone! For using Tomcat session clustering I need to put the following component in all nodes? Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster

Re: Session Replication

I only have one machine to test Session Replication. Every tomcat instances are in same machine. On 9/27/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you

Re: Session Replication

- Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat instances on the same box. What's that saying about eggs and baskets? - Chuck

Re: Session Replication

Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat instances on the same box. What's that saying about eggs and baskets? - Chuck

Re: Session Replication

. On 9/27/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat

RE: Session Replication in Tomcat5.5.17

- Van: Mark Thomas [mailto:[EMAIL PROTECTED] Verzonden: woensdag 20 juni 2007 14:12 Aan: Tomcat Users List Onderwerp: Re: Session Replication in Tomcat5.5.17 shiva sha wrote: Hai If i remove tomcats names (jvm route) in workers.properties means how Apache route the request? Pls clarify

Re: Session Replication in Tomcat5.5.17

-Oorspronkelijk bericht- Van: Mark Thomas [mailto:[EMAIL PROTECTED] Verzonden: woensdag 20 juni 2007 14:12 Aan: Tomcat Users List Onderwerp: Re: Session Replication in Tomcat5.5.17 shiva sha wrote: Hai If i remove tomcats names (jvm route) in workers.properties means how Apache route the request

Re: Session Replication in Tomcat5.5.17

Hi I follwoed ur given URLs... But no luck.. This is my configuraion Apache Version : 2.2.4 Tomcat Version : 5.5.17 JDK : 1.6.0_01 Win 2000 workers.properties worker.list=tomcat1,tomcat2,loadbalancer # First tomcat server worker.tomcat1.type=ajp13 worker.tomcat1.host=192.168.10.30

RE: Session Replication in Tomcat5.5.17

Try to remove tomcat1,tomcat2, from the workers.properties It should be something like worker.list=loadbalancer Thanks Guru -Original Message- From: shiva sha [mailto:[EMAIL PROTECTED] Sent: 20 June 2007 09:30 To: Tomcat Users List Subject: Re: Session Replication in Tomcat5.5.17

Re: Session Replication in Tomcat5.5.17

Thanks Guru -Original Message- From: shiva sha [mailto:[EMAIL PROTECTED] Sent: 20 June 2007 09:30 To: Tomcat Users List Subject: Re: Session Replication in Tomcat5.5.17 Hi I follwoed ur given URLs... But no luck.. This is my configuraion Apache Version : 2.2.4 Tomcat Version : 5.5.17 JDK

Re: Session replication in tomcat5.5

did you try to add the address attribute within connector tag ? something looks strange in your worker.properties i.e. worker.tomcat1.lbfactor=1 worker.tomcat2.lbfactor=100 this two directive mean something like you will use 100 times tomcat2 for 1 time tomcat1... if you want to use the two

Re: Session replication in tomcat5.5

I had paste the mod_jk.dll in conf/modules.. What i m trying is First i started the Apache and then Tomcat1,Tomcat2.. I run the html file in Tomcat1 and the given value is stored in session and displays the same. Then stop the Tomcat1.. If i run the same HTML i want to show the session value

Re: Session Replication in Tomcat5.5.17

shiva sha wrote: Hi At present I m trying Session replication only.. I think i need tomcat1 and tomcat2.. Am i correct? No - you need to remove these. Mark - To start a new topic, e-mail: users@tomcat.apache.org To

Re: Session replication in tomcat5.5

Thanks Guru.. Below is the log entry from mod_jk.log [Mon Jun 18 21:27:32 2007] [2292:2296] [debug] jk_ajp_common.c (1806): worker tomcat1 contact is '192.168.10.30:8009' [Mon Jun 18 21:27:32 2007] [2292:2296] [debug] jk_ajp_common.c (1895): setting socket keepalive to 1 [Mon Jun 18 21:27:32

RE: Session replication in tomcat5.5

[mailto:[EMAIL PROTECTED] Sent: 20 June 2007 12:46 To: Tomcat Users List; [EMAIL PROTECTED] Subject: Re: Session replication in tomcat5.5 Thanks Guru.. Below is the log entry from mod_jk.log [Mon Jun 18 21:27:32 2007] [2292:2296] [debug] jk_ajp_common.c (1806): worker tomcat1 contact

Re: Session replication in tomcat5.5

replication will have issues ... look at your application logs and confirm back Thanks Guru -Original Message- From: shiva sha [mailto:[EMAIL PROTECTED] Sent: 20 June 2007 12:46 To: Tomcat Users List; [EMAIL PROTECTED] Subject: Re: Session replication in tomcat5.5 Thanks Guru.. Below

Re: Session Replication in Tomcat5.5.17

Hai If i remove tomcats names (jvm route) in workers.properties means how Apache route the request? Pls clarify On 6/20/07, Mark Thomas [EMAIL PROTECTED] wrote: shiva sha wrote: Hi At present I m trying Session replication only.. I think i need tomcat1 and tomcat2.. Am i correct? No -

Re: Session Replication in Tomcat5.5.17

shiva sha wrote: Hai If i remove tomcats names (jvm route) in workers.properties means how Apache route the request? Pls clarify Remove the line: worker.list=tomcat1,tomcat2,loadbalancer Replace it with worker.list=loadbalancer Everythign else remains the same. mark

RE: Session Replication in Tomcat5.5.17

what this done with my problem -Oorspronkelijk bericht- Van: Mark Thomas [mailto:[EMAIL PROTECTED] Verzonden: woensdag 20 juni 2007 14:12 Aan: Tomcat Users List Onderwerp: Re: Session Replication in Tomcat5.5.17 shiva sha wrote: Hai If i remove tomcats names (jvm route

  1   2   >