As a follow-up question...If we're load balancing across two machines *and* have some CFCs in session scope. We're still ok if the connector is set to "sticky" sessions and replication is not turned off in JRun?
I would definitely recommend sticky session to avoid having request bounce from server to server (and then also having to deal with the CFC session replication issue).
I would only turn session replication on if it is critical to your application that losing a server does not cause loss of session. I don't believe many systems really require that.
As for handling the CFC session replication issue, no error is thrown but you can detect that you got a failed replication:
<cfif structKeyExists(session,"myObject") and
not isObject(session.myObject)>
<!---
need to recreate session.myObject because
we lost a server and the replication failed
for this CFC
--->
</cfif>Hope that helps?
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
