Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. web farm problem

web farm problem

Scheduled Pinned Locked Moved ASP.NET
helpcsharpjavascriptasp-netsysadmin
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gus_br
    wrote on last edited by
    #1

    Hi everybody... I`m having some problems with a web farm cenario. The issue is: the ASP.NET create a couple of js files in one server, but when a requisition goes to another server in the web farm the file with the js function doesn`t exist. To be more especific, I have a LinkButton on my page, and when this link is clicked it fires the 'WebForm_PostBackOptions' (which is 'undefined'sometimes). Any hints about this problem? A web.config element configuration? Thans you buddies

    D 1 Reply Last reply
    0
    • G gus_br

      Hi everybody... I`m having some problems with a web farm cenario. The issue is: the ASP.NET create a couple of js files in one server, but when a requisition goes to another server in the web farm the file with the js function doesn`t exist. To be more especific, I have a LinkButton on my page, and when this link is clicked it fires the 'WebForm_PostBackOptions' (which is 'undefined'sometimes). Any hints about this problem? A web.config element configuration? Thans you buddies

      D Offline
      D Offline
      doWhileSomething
      wrote on last edited by
      #2

      One thing you can do is put a value in each web.config for each server like a machine key or some other unique key then set a cookie with this key information to tie each user to that server. At the very least this will keep the user locked to one server for that visit. This will largely depend on how your server(s) are configured though.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups