RE: Session Replication and CFCs = helpful?

[Stacy Young]

From my experience sticky sessions do not function properly by default on Windows. I don't know if this is specific to the Apache connector, but we had to add the mapCheck attribute in jrun.xml and set it to zero. For some reason the sticky sessions never 'stuck' unless we did this. (Jrun with cfmx on windows with apache webs out front)

  < service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService" >
    < attribute name="mapCheck">0</attribute >

What's odd is that on our production setup this attribute was magically there after the install (We use Solaris in prod)...It's also a good idea to verify it's there to cut down on useless chatter between the connector and the server instance. If the mapCheck is not set to zero, the connector does a remote lookup (sub process) after each call to get a bunch of info off one of the servers in the cluster (mappings etc)

Hope that helps,

Stace

________________________________________
From: Nathan Strutz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 07, 2004 3:23 PM
To: CF-Talk
Subject: RE: Session Replication and CFCs = helpful?

Dave, thanks for finding this post on bpurcell.org. I guess I skipped over
it earlier.

Now one question about it, my Jrun.xml file (or files, as there are many of
them) doesn't contain anything about sticky anything. I'm assuming I could
add this line in, does anyone know?

Also, It doesn't really seem like it's sticky by default. I can easily be
wrong, but I notice when one cfmx instance is broken, I can refresh the page
over and over and get a working page, then a broken page, working, broken,
etc. This seems to be the real default behavior.

thanks
-nathan strutz

��-----Original Message-----
��From: Dave Carabetta [mailto:[EMAIL PROTECTED]
��Sent: Wednesday, January 07, 2004 12:29 PM
��To: CF-Talk
��Subject: RE: Session Replication and CFCs = helpful?

��>I don't know of any way using JRun clustering to enforce "sticky"
sessions
��>-
��>that's typically done with web server clustering by having the cluster
��>manager issue a cookie at each initial request, and redirect future
��>requests
��>to each server depending on the cookie value.
��>

��Actually, unless I'm misinterpreting your statement, Brandon Purcell has
��just posted on his blog how JRun uses sticky sessions and where you can
��manipulate the setting:

��http://www.bpurcell.org/blog/index.cfm?mode=entry&entry=986

��Regards,
��Dave.
________________________________________

---

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

---