Re: Problem with Tomcat 6 cluster
] jk_ajp_common.c (2204): (worker1) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port [Mon Sep 14 14:15:42 2009][3604:2000] [info] jk_lb_worker.c (1168): service failed, worker worker1 is in error state [Mon Sep 14 14:15:43 2009]balancer LB-IP 3.421875 [Mon Sep 14 14:15:43 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:15:44 2009]balancer LB-IP 0.25 [Mon Sep 14 14:15:44 2009]balancer LB-IP 0.281250 [Mon Sep 14 14:15:44 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:15:44 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:16:03 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:16:03 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:16:12 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:16:12 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:26:55 2009]balancer LB-IP 0.00 [Mon Sep 14 14:26:55 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:10 2009][3604:3720] [info] jk_ajp_common.c (1347): (worker2) all endpoints are disconnected, detected by connect check (2), cping (0), send (0) [Mon Sep 14 14:27:11 2009][3604:3720] [info] jk_connect.c (566): connect to worker2Ip:8009 failed (errno=61) [Mon Sep 14 14:27:11 2009][3604:3720] [info] jk_ajp_common.c (869): Failed opening socket to (worker2Ip:8009) (errno=61) [Mon Sep 14 14:27:11 2009][3604:3720] [error] jk_ajp_common.c (1359): (worker2) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61) [Mon Sep 14 14:27:11 2009][3604:3720] [info] jk_ajp_common.c (2186): (worker2) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1) [Mon Sep 14 14:27:12 2009][3604:3720] [info] jk_connect.c (566): connect to 10.112.107.252:8009 failed (errno=61) [Mon Sep 14 14:27:12 2009][3604:3720] [info] jk_ajp_common.c (869): Failed opening socket to (worker2Ip:8009) (errno=61) [Mon Sep 14 14:27:12 2009][3604:3720] [error] jk_ajp_common.c (1359): (worker2) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61) [Mon Sep 14 14:27:12 2009][3604:3720] [info] jk_ajp_common.c (2186): (worker2) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2) [Mon Sep 14 14:27:12 2009][3604:3720] [error] jk_ajp_common.c (2204): (worker2) Connecting to tomcat failed. Tomcat is probably not started or is listening on the wrong port [Mon Sep 14 14:27:12 2009][3604:3720] [info] jk_lb_worker.c (1168): service failed, worker worker2 is in error state [Mon Sep 14 14:27:12 2009]balancer LB-IP 2.093750 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.00 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.046875 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:14 2009]balancer LB-IP 0.062500 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.062500 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.046875 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.046875 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.046875 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.046875 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.125000 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.031250 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.156250 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.015625 [Mon Sep 14 14:27:15 2009]balancer LB-IP 0.171875 Regards, Sumedh On Thu, Sep 17, 2009 at 10:56 PM, Jason Brittain jason.britt...@gmail.comwrote: Sumedh: We don't see any attachments on your emails. You might want to try attaching it again, but if it didn't come through on the first or second try then the size of the attachment might have been too large. Thanks. -- Jason Brittain On Wed, Sep 16, 2009 at 10:40 AM, Sumedh Sakdeo sumedhsak...@gmail.com wrote: Hi Filip, Did log files attached help? Thanks, Sumedh On Mon, Sep 14, 2009 at 2:38 PM, Sumedh Sakdeo sumedhsak...@gmail.com wrote: Hi Filip, Please find the logs in attached file. Thanks in advance, Sumedh On Wed, Sep 9, 2009 at 9:22 AM, Filip Hanik - Dev Lists devli...@hanik.com wrote: what do your logs tell you? Filip On 09/08/2009 02:33 AM, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per
Re: Problem with Tomcat 6 cluster
Hi Filip, Did log files attached help? Thanks, Sumedh On Mon, Sep 14, 2009 at 2:38 PM, Sumedh Sakdeo sumedhsak...@gmail.comwrote: Hi Filip, Please find the logs in attached file. Thanks in advance, Sumedh On Wed, Sep 9, 2009 at 9:22 AM, Filip Hanik - Dev Lists devli...@hanik.com wrote: what do your logs tell you? Filip On 09/08/2009 02:33 AM, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. Thanks in advance, Sumedh - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Container based authentication using LDAP and Active Directory
http://java.sun.com/j2se/1.5.0/docs/guide/security/jgss/single-signon.html might help you with secure authentication against AD. I use this for authentication purpose. Simple google landed me on these two wonderful pages maybe helpful... JAAS authentication http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/tutorials/GeneralAcnOnly.html http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/tutorials/GeneralAcnOnly.htmlJAAS authorization http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/tutorials/GeneralAcnAndAzn.html#WhatIsAzn let me know if this suffice your question. -Sumedh On Wed, Sep 16, 2009 at 2:14 AM, sharda k sktom...@gmail.com wrote: Thank you George. I think I need to elaborate my question further. I could bind user and fetch user roles using simple java class. But what I want to implement is JAAS. The problem is based on the information provided in different web sites I can use either LDAP or AD for both authentication and authorization. But I need to decouple authentication and authorization. How can I implement that? Any help would be appreciated. Sharda On Tue, Sep 15, 2009 at 3:19 PM, George Sexton geor...@mhsoftware.com wrote: AD servers run an LDAP connector. You use and LDAP API library and try to bind to the tree using the user's name and password for credentials. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 -Original Message- From: sharda k [mailto:sktom...@gmail.com] Sent: Tuesday, September 15, 2009 2:12 PM To: Tomcat Users List Subject: Re: Container based authentication using LDAP and Active Directory How can I implement LDAP to authenticate against AD? Can you please elaborate? I need AD for authentication and LDAP fro authorization. Thank you, Sharda On Tue, Sep 15, 2009 at 3:08 PM, George Sexton geor...@mhsoftware.comwrote: You can use LDAP to authenticate against AD. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 -Original Message- From: sharda k [mailto:sktom...@gmail.com] Sent: Tuesday, September 15, 2009 2:01 PM To: users@tomcat.apache.org Cc: sktom...@gmail.com Subject: Container based authentication using LDAP and Active Directory Hi, I want to implement Container based Authentication for a new web site I am working on. The scenario that I have is: - User ids are being stored in LDAP - User credentials(password) are being stored in Active Directory (AD). - User roles are gain being stored in LDAP In all examples that I could find in different websites write about LDAP authentication in Tomcat. Is there a way we can combine both LDAP and AD for authentication? Also I want to use custom login page for it. Any help on this would be appreciated. Thanks, Sharda - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Problem with Tomcat 6 cluster
Hi Filip, Please find the logs in attached file. Thanks in advance, Sumedh On Wed, Sep 9, 2009 at 9:22 AM, Filip Hanik - Dev Lists devli...@hanik.comwrote: what do your logs tell you? Filip On 09/08/2009 02:33 AM, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. Thanks in advance, Sumedh - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Problem with Tomcat 6 cluster
Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. Thanks in advance, Sumedh
Re: Tomcat 6 Clustering issue
Hi Darren, For our setup tomcat 6 is able to handle failover to healthy node with proper session replication. I assume you have loaded load balancer module, updated worker.properties, made cluster changes to server.xml of tomcat 6. My problem is next step of yours. http://www.mail-archive.com/users@tomcat.apache.org/msg66444.html In terms of monitoring you can use jkstatus of apache server. Use jkstatus Web page to monitor web server requests.For tomcat clustering visit http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html. Thanks, Sumedh On Tue, Sep 8, 2009 at 2:49 PM, Darren Kukulka darren.kuku...@connaught.plc.uk wrote: Hi All, I've come across some interesting scenarios with a clustered Tomcat6 environment and I'm wondering what the most common (or best) approach to configuration would be. Basically, in a 2 node cluster, with a front-end Apache Web Server using mod_jk balancer (on availability, with equal weighting) - when one node decides to stop servicing requests, it appears that the front end may still be trying to send requests to it and consequently timing out, or taking a very long time to resend the request to the healthy node. In situations like this, the failing node is not down. Nor is it low on resources or experiencing thread blocking. There's no immediate evidence of memory leaks but this will require further investigation. It just stops servicing requests. Indeed, even when we try and interrogate the JVM sometimes with JConsole, we cannot connect to the environment. Anyway, the crux of the issue is how can we configure our environment such that the healthy node will service all requests if the bad node is degraded, although it is up? There is also the question as to how we monitor for such scenarios. Cheers, Darren Connaught plc is a FTSE 250 company. We are the UK's leading provider of integrated services operating in the compliance, social housing and public sector markets. Please visit our website to see a full list of Connaught's Registered Companies www.connaught.plc.uk/group/aboutconnaught/registeredcompanies Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete this message. Connaught plc, Head Office 01392 444546
Re: Apache Server failover and session replication
Can anyone help in these regards? Thanks in advance, Sumedh On Thu, Sep 3, 2009 at 8:52 AM, Sumedh Sakdeo sumedhsak...@gmail.comwrote: http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html *How it Works * 1. TomcatA starts up 2. TomcatB starts up (Wait that TomcatA start is complete) 3. TomcatA receives a request, a session S1 is created. 4. TomcatA crashes 5. TomcatB receives a request for session S1 6. TomcatA starts up 7. TomcatA receives a request, invalidate is called on the session (S1) 8. TomcatB receives a request, for a new session (S2) 9. TomcatA The session S2 expires due to inactivity. section describes the steps.7-9 steps confusing. Does tomcat 6 even support such scenario? --Sumedh On Thu, Sep 3, 2009 at 6:29 AM, Shaun Senecal ssenecal.w...@gmail.comwrote: After re-reading your initial post, the problems might not be as related as I thought since at no point did replication stop for me. On Thu, Sep 3, 2009 at 9:56 AM, Shaun Senecal ssenecal.w...@gmail.com wrote: We had a similar problem with Tomcat 6 using clustering. It turns out that the SSO information is only propagated while all instances are running. If Instance-A fails, several users then log in to Instance-B, then Instance-A comes back up, all of the SSO information for the users that logged in during the downtime is not included in Instance-A so those users are forced to re-login once the load balancer sends them to that instance. I wrote a fix for it, which might be useful for you. However, it hasnt been fully tested and is designed to only share the SSO information at startup, not all Session information. If Tomcat doenst handle this case, then the fix I wrote should be easily extended to handle that. Basically, when an instance comes up it broadcasts a request for all known SSO information to the cluster. It then takes the first response it gets and continues processing as normal. Let me know if you dont find a proper solution to the problem and I will try to dig up that fix. My intention was to post it back to the group, but I got sidetracked once we (temporarily) stopped using clustering. Shaun On Thu, Sep 3, 2009 at 3:52 AM, Sumedh Sakdeo sumedhsak...@gmail.com wrote: Hi Rainer, I am using Tomcat session clustering and Apache Http Server for LB(using mod_jk module). Also, using Tomcat 6. I have made appropriate changes to worker.properties and httpd.conf. Also I have made appropriate changes to server.xml on each tomcat. Thanks, Sumedh On Thu, Sep 3, 2009 at 12:15 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 02.09.2009 19:57, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. How do you replicate? Are you using Tomcat session clustering? Tomcat 5.5 or Tomcat 6? Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Apache Server failover and session replication
Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. Thanks in advance, Sumedh
Re: Apache Server failover and session replication
Hi Rainer, I am using Tomcat session clustering and Apache Http Server for LB(using mod_jk module). Also, using Tomcat 6. I have made appropriate changes to worker.properties and httpd.conf. Also I have made appropriate changes to server.xml on each tomcat. Thanks, Sumedh On Thu, Sep 3, 2009 at 12:15 AM, Rainer Jung rainer.j...@kippdata.dewrote: On 02.09.2009 19:57, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. How do you replicate? Are you using Tomcat session clustering? Tomcat 5.5 or Tomcat 6? Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Server failover and session replication
Shaun, Yes we have a user session object created when user logs on with proper credentails. For ex: At startup of two servers lets say user A has logged in. As you are saying the SSO information is propagated while all instances are running. So when for first time when tomcat which was handling request goes down, this session object is successfully handled by other tomcat instance. But when first instance comes up, and due to some reason second instance which was processing sticky requests goes down this session object is lost. Our problem is that this failback should happen correctly, and we find this a general requirement, so do tomcat6 support such a scenario? I have been sratching my head from past few days to fix this. What kind of solution have you written for this? Could you please share? Thanks for your time, Ciao, Sumedh On Thu, Sep 3, 2009 at 6:26 AM, Shaun Senecal ssenecal.w...@gmail.comwrote: We had a similar problem with Tomcat 6 using clustering. It turns out that the SSO information is only propagated while all instances are running. If Instance-A fails, several users then log in to Instance-B, then Instance-A comes back up, all of the SSO information for the users that logged in during the downtime is not included in Instance-A so those users are forced to re-login once the load balancer sends them to that instance. I wrote a fix for it, which might be useful for you. However, it hasnt been fully tested and is designed to only share the SSO information at startup, not all Session information. If Tomcat doenst handle this case, then the fix I wrote should be easily extended to handle that. Basically, when an instance comes up it broadcasts a request for all known SSO information to the cluster. It then takes the first response it gets and continues processing as normal. Let me know if you dont find a proper solution to the problem and I will try to dig up that fix. My intention was to post it back to the group, but I got sidetracked once we (temporarily) stopped using clustering. Shaun On Thu, Sep 3, 2009 at 3:52 AM, Sumedh Sakdeo sumedhsak...@gmail.com wrote: Hi Rainer, I am using Tomcat session clustering and Apache Http Server for LB(using mod_jk module). Also, using Tomcat 6. I have made appropriate changes to worker.properties and httpd.conf. Also I have made appropriate changes to server.xml on each tomcat. Thanks, Sumedh On Thu, Sep 3, 2009 at 12:15 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 02.09.2009 19:57, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. How do you replicate? Are you using Tomcat session clustering? Tomcat 5.5 or Tomcat 6? Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Server failover and session replication
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html *How it Works * 1. TomcatA starts up 2. TomcatB starts up (Wait that TomcatA start is complete) 3. TomcatA receives a request, a session S1 is created. 4. TomcatA crashes 5. TomcatB receives a request for session S1 6. TomcatA starts up 7. TomcatA receives a request, invalidate is called on the session (S1) 8. TomcatB receives a request, for a new session (S2) 9. TomcatA The session S2 expires due to inactivity. section describes the steps.7-9 steps confusing. Does tomcat 6 even support such scenario? --Sumedh On Thu, Sep 3, 2009 at 6:29 AM, Shaun Senecal ssenecal.w...@gmail.comwrote: After re-reading your initial post, the problems might not be as related as I thought since at no point did replication stop for me. On Thu, Sep 3, 2009 at 9:56 AM, Shaun Senecal ssenecal.w...@gmail.com wrote: We had a similar problem with Tomcat 6 using clustering. It turns out that the SSO information is only propagated while all instances are running. If Instance-A fails, several users then log in to Instance-B, then Instance-A comes back up, all of the SSO information for the users that logged in during the downtime is not included in Instance-A so those users are forced to re-login once the load balancer sends them to that instance. I wrote a fix for it, which might be useful for you. However, it hasnt been fully tested and is designed to only share the SSO information at startup, not all Session information. If Tomcat doenst handle this case, then the fix I wrote should be easily extended to handle that. Basically, when an instance comes up it broadcasts a request for all known SSO information to the cluster. It then takes the first response it gets and continues processing as normal. Let me know if you dont find a proper solution to the problem and I will try to dig up that fix. My intention was to post it back to the group, but I got sidetracked once we (temporarily) stopped using clustering. Shaun On Thu, Sep 3, 2009 at 3:52 AM, Sumedh Sakdeo sumedhsak...@gmail.com wrote: Hi Rainer, I am using Tomcat session clustering and Apache Http Server for LB(using mod_jk module). Also, using Tomcat 6. I have made appropriate changes to worker.properties and httpd.conf. Also I have made appropriate changes to server.xml on each tomcat. Thanks, Sumedh On Thu, Sep 3, 2009 at 12:15 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 02.09.2009 19:57, Sumedh Sakdeo wrote: Hello All, I have a setup with two tomcat instances(AB). I have configured an apache web server 2.2 for load balancing and fail over. Setup looks fine as per the configurations suggested. Let tomcat A be handling some request at sometime. When tomcat instance(A) goes down, the session is replicated to another tomcat instance(B) successfully. Now tomcat instance B is handling those requests. Till this point everything goes fine, but when I bring up tomcat instance(A) and after that tomcat instance(B) goes down, the session is no longer replicated. What might be the issue? In status page of apache server I see even if node status is OK session is not replicated to fail over node for second time. How do you replicate? Are you using Tomcat session clustering? Tomcat 5.5 or Tomcat 6? Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
