Professional Web Applications Themes

Normal for COM objects to stay resident in IIS? - ASP Components

I am developing a COM object that is used by the server in an ASP page. I am not able to rebuild the COM object on the same server machine because once it is used once, IIS does not release it. I am forced to restart IIS in order to free the COM object. Is this normal? Is this just an operating symptom of IIS (keeping com objects active in memory)? Thanks! M...

  1. #1

    Default Normal for COM objects to stay resident in IIS?

    I am developing a COM object that is used by the server in an ASP page. I am
    not able to rebuild the COM object on the same server machine because once
    it is used once, IIS does not release it. I am forced to restart IIS in
    order to free the COM object.

    Is this normal? Is this just an operating symptom of IIS (keeping com
    objects active in memory)?

    Thanks!
    M


    Mark Findlay Guest

  2. #2

    Default Re: Normal for COM objects to stay resident in IIS?

    yes, IIS cache the COM object in memory.
    you can seperate it into another process,
    [url]http://support.microsoft.com/?scid=kb;EN-US;Q281335[/url]
    and kill dllhost.exe when you cant update the dll. I use this method, for
    kill dllhost is more convinient than restart IIS.


    "Mark Findlay" <mfindlayspeakeasy.org> wrote in message
    news:PVmdnd1qcLPjQuqiXTWc-gspeakeasy.net...
    > I am developing a COM object that is used by the server in an ASP page. I
    am
    > not able to rebuild the COM object on the same server machine because once
    > it is used once, IIS does not release it. I am forced to restart IIS in
    > order to free the COM object.
    >
    > Is this normal? Is this just an operating symptom of IIS (keeping com
    > objects active in memory)?
    >
    > Thanks!
    > M
    >
    >

    Onega Guest

  3. #3

    Default Re: Normal for COM objects to stay resident in IIS?

    "Onega" <Onegamvps.org> wrote in message
    news:ekIgz5lhDHA.3204TK2MSFTNGP11.phx.gbl...
    > yes, IIS cache the COM object in memory.
    > you can seperate it into another process,
    > [url]http://support.microsoft.com/?scid=kb;EN-US;Q281335[/url]
    > and kill dllhost.exe when you cant update the dll. I use this method, for
    > kill dllhost is more convinient than restart IIS.
    This is not a good practice. You could corrupt logfiles and the metabase
    (possibly).
    Better restart a COM+ project since IIS resides within COM+...
    Or use a script to 'unload' a specific IIS webapp.

    Egbert Nierop \(MVP for IIS\) Guest

Similar Threads

  1. meet your resident mvp ;-)
    By David Bartosik - MS MVP in forum Web Design
    Replies: 6
    Last Post: June 7th, 06:08 PM
  2. [OT] our resident troll
    By Mothra in forum PERL Miscellaneous
    Replies: 3
    Last Post: September 19th, 12:10 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139