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. Threads in ASP .NET

Threads in ASP .NET

Scheduled Pinned Locked Moved ASP.NET
csharpsysadminhelpquestion
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.
  • M Offline
    M Offline
    mikeyhardingboyo
    wrote on last edited by
    #1

    Hi, I have a asp .net application. In the application I attempt to start a thread from globals "Application_start" method. My problem is that the start page never fully loads and the secondary thread fails on a specific line but it gives me no indication as to which one. Thus I get the message "Server Unavailable". Is this a case of deadlock? or do you need to apply threads differently in asp .net. cheers Mike

    M 1 Reply Last reply
    0
    • M mikeyhardingboyo

      Hi, I have a asp .net application. In the application I attempt to start a thread from globals "Application_start" method. My problem is that the start page never fully loads and the secondary thread fails on a specific line but it gives me no indication as to which one. Thus I get the message "Server Unavailable". Is this a case of deadlock? or do you need to apply threads differently in asp .net. cheers Mike

      M Offline
      M Offline
      Mike Ellison
      wrote on last edited by
      #2

      Well, I'm not sure of the specific problem, but here are a couple of links to some excellent articles on threading in ASP.NET. Perhaps you've already read them, but if not, they're good reads: http://msdn.microsoft.com/msdnmag/issues/05/10/WickedCode/ http://msdn.microsoft.com/msdnmag/issues/03/06/Threading/ You might consider turning on tracing just calling the failing code synchronously until you can determine which line is causing the error.

      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