It is slightly more complicated that that. We are creating a session but not an HttpSession, a C++ session. The Tomcat web app essentially has a servlet that delegates to the C++ component using JNI.
Should we create an HttpSession before delegating? Is that the missing link? Thanks Sidd -----Original Message----- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Friday, June 16, 2006 10:59 AM To: Tomcat Users List Subject: Re: Apache with Tomcat and session affinity problem is your webapplication creating a session? if not, then there wont be a cookie, and mod_jk uses this cookie to determine server affinity. and if you dont have sessions, you don't need session affinity Filip Sharma, Siddharth wrote: > I have an http packet sniffer and it is reporting that there are no cookies > returned by apache. > > Just to recap what I have done: > 1. IBM HttpServer 2.0 with mod_jk on redhat linux > 2. worker.properties has a load-balancer worker fronting two tomcat workers > over ajp13. it's sticky session property is set to True. > 3. In the server.xml, the jvMRoute attribute of Engine (in both tomcat > instances) have their respective worker names (no case difference or silly > spelling mistakes). > > There is no cookie. Is there another step that I am missing to enable > session affinity? > > > > > -----Original Message----- > From: Sanjeev Kumar Bhat, Noida [mailto:[EMAIL PROTECTED] > Sent: Friday, June 16, 2006 10:15 AM > To: Tomcat Users List; Tomcat Users List > Subject: RE: Apache with Tomcat and session affinity problem > > > JSESSIONID is a non-persistent cookie and you can check its presence easily > using a Netscape Navigator or FireFox. > In Firefox go to Tools->Options, Options Popup appears. > Select Privacy in the left section, to get the privacy options on the right > side of the popup > Expand the Node "Cookies" and click on button View Cookies. > You can see the cookie JSESSIONID with its value. > > If you don't see the cookie, then definitely there is some issue. > > > ________________________________ > > From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] > Sent: Fri 6/16/2006 7:21 PM > To: Tomcat Users List > Subject: Re: Apache with Tomcat and session affinity problem > > > > how do you verify that you don't have a cookie? > > I suggest using LiveHttpHeaders (firefox/mozilla) or TCPMonitor > > Filip > > > Sharma, Siddharth wrote: > >> Yes I did >> jvmRoute is set to the worker name. >> still, no jsessionid cookie. >> >> >> >> >> >> -----Original Message----- >> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] >> Sent: Friday, June 16, 2006 7:18 AM >> To: Tomcat Users List >> Subject: Re: Apache with Tomcat and session affinity problem >> >> have you set jvmRoute in your engine element (server.xml)? >> this is how mod_jk does session affinity >> >> filipp >> >> >> >> Sharma, Siddharth wrote: >> >> >>> I have IBM HttpServer 2.0 (it is an apache essentially) fronting two >>> tomcat instances (version 5.5.16) using mod_jk over ajp13. >>> I have configured a load balancer worker to spray load across two workers >>> representing these two tomcat instances. >>> And it works. >>> The problem is I do not see a session id cookie in the response, so I am >>> >>> >> not >> >> >>> sure if it is maintaining session affinity. >>> I have configured the load balancer worker for session affinity with this >>> directive in worker.properties: >>> worker.lb_worker.sticky_session=True >>> >>> What am I missing? >>> What is the exact name of the cookie that mod_jk injects? >>> >>> I apologize if this is not the right mailing list for connector questions >>> and will appreciate if someone could point me to it. >>> >>> Thanks in advance >>> -Sidd >>> >>> >>> >>> --------------------------------------------------------------------- >>> To start a new topic, e-mail: users@tomcat.apache.org >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >>> >> >> > > > -- > > > Filip Hanik > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > DISCLAIMER: > ---------------------------------------------------------------------------- > ------------------------------------------- > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect > the opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail > is strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. Before opening any mail and > attachments please check them for viruses and defect. > ---------------------------------------------------------------------------- > ------------------------------------------- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Filip Hanik --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
