Skip to main content
M
mcaselle
Participating Frequently
November 4, 2010
Question

CF 9.01 Enterprise - multi-instance image problem

  • November 4, 2010
  • 1 reply
  • 1017 views

Have 9.01 enterprise running with 3 instances (sticky sessions) - the problem situation is as follows:  eg. CFchart created on instance1, writes .swf to cache1.  Print of chart writes .jpg to cache1, cfdocument shows that the image has expired - 1 to 3 refreshes of the page will ultimately show the image.  Apears that the cfdocument is looking for the image in other instances.  Removal of the cfdoucment tag and having the image go to a html page works.  Appreciate any assistance that will get us past this.

    This topic has been closed for replies.

    1 reply

    D
    Community Expert
    Dave WattsCommunity Expert
    Community Expert
    November 4, 2010

    It sounds like your sticky sessions aren't sticking. The user isn't being directed back to the same server that generated the image.

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

    Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on

    GSA Schedule, and provides the highest caliber vendor-authorized

    instruction at our training centers, online, or onsite.

    Read this before you post:

    http://forums.adobe.com/thread/607238

    Dave Watts, Eidolon LLC
    M
    mcaselleAuthor
    Participating Frequently
    November 5, 2010

    I guess my followup question is then, "how to make the sticky sessions sticky?" and why it's only a problem when using cfdocument, as the output to html works as expected.

    D
    Community Expert
    Dave WattsCommunity Expert
    Community Expert
    November 5, 2010

    Ah! I didn't realize the exact problem you were having until your followup.

    CFDOCUMENT is using HTTP to fetch the resources to build the page. That HTTP request isn't being stuck to the same server, as it's not really part of the session.

    There are a couple of ways you might fix this problem. One might be to use the local filesystem instead of HTTP using the LOCALURL attribute of CFDOCUMENT. Another might be to direct all requests that invoke CFDOCUMENT to a specific server within the cluster using that server's unique name, so that CFDOCUMENT also uses that unique name.

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

    Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on

    GSA Schedule, and provides the highest caliber vendor-authorized

    instruction at our training centers, online, or onsite.

    Read this before you post:

    http://forums.adobe.com/thread/607238

    Dave Watts, Eidolon LLC
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices