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 service keep a process open

web service keep a process open

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

    I am trying to determine where a C# 2008 application that communicates with a web service is having a process problem. The C# 2008 app is communicating to the web service using a *.wsdl file by accessing a proxy. The problem is when the C# app has finished executing there are still processes that are active when looking at the task manager on the production server. Thus the proxy still has a process executinng and/or the connection to the web service has some process that is not releasing some process. Thus my questions are: 1. What do I look for in the connection to the web service that may not be releasing the appropriate resources? Can you tell me what I can do to try to resolve the problem? 2. If the proxy is not releasing some resource, can you tell me what to look for and let me know how to reolve the problem? 3. To at least try to solve the problem, would using the system.exit(1) at the end of the code at least resolve the problem? if system.exit(1) does not work, can you tell me what you suggest I do stop the unwanted process from executing in the code?

    N 1 Reply Last reply
    0
    • D dcof

      I am trying to determine where a C# 2008 application that communicates with a web service is having a process problem. The C# 2008 app is communicating to the web service using a *.wsdl file by accessing a proxy. The problem is when the C# app has finished executing there are still processes that are active when looking at the task manager on the production server. Thus the proxy still has a process executinng and/or the connection to the web service has some process that is not releasing some process. Thus my questions are: 1. What do I look for in the connection to the web service that may not be releasing the appropriate resources? Can you tell me what I can do to try to resolve the problem? 2. If the proxy is not releasing some resource, can you tell me what to look for and let me know how to reolve the problem? 3. To at least try to solve the problem, would using the system.exit(1) at the end of the code at least resolve the problem? if system.exit(1) does not work, can you tell me what you suggest I do stop the unwanted process from executing in the code?

      N Offline
      N Offline
      N a v a n e e t h
      wrote on last edited by
      #2

      What process is active?

      Best wishes, Navaneeth

      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