OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Phil Fuhlman (pfuhlmanDEXMA.COM)
Date: Thu Jan 24 2002 - 14:44:40 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    I think for each one of those 3rd pty DLLs I'd launch a wrapper process,
    then start a worker thread in your 'task runner' process that camps on
    the wrapper process via the event mechanism. Then if / when the 3rd pty
    DLL process dies, your worker thread continues execution because the
    event lets go. Works pretty cool.

    </pff>

    -----Original Message-----
    From: Kevin Palmer [mailto:kevin.palmerINTELLIWARE-SYSTEMS.COM]
    Sent: Thursday, January 24, 2002 3:54 AM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: COM Server Exceptions

    The $100 answer! We write 0 to address 100 hex (int *a = 0x100; *a=0)
    !!!

    Actually, we are developing a product which runs background jobs and
    each
    job can be different, each can load different 3rd party DLL's etc. The
    problem with this is, if a 3rd party DLL causes a application crash, we
    don't want the server and scheduler to be taken down with it.

    So to create a reliable server, we launch our Task Runnner COM EXE which
    in
    turn loads the DLL's and run's the job. And the idea is that if it
    crashes,
    we let the user know in the UI.

    So, to test this we have the above bit of code, which will reliably
    crash a
    process !!!!

    Cheers !

    Kevin

    -----Original Message-----
    From: Brian Muth [mailto:bmuthSTRAIGHTTHROUGH.COM]
    Sent: 24 January 2002 05:17
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: COM Server Exceptions

    The $100 question: why is the server crashing?

    >
    > When a local server crashes, the exception is handled and COM
    > returns a
    > RPC_E_SERVERFAULT.
    >
    > The local server doesn't terminate though. Is there anyway to
    > get it to
    > terminate after returning the error, or show we do it in the server ?
    >
    > I was thinking of returning the Process ID at the beginning
    > and then later
    > on the server can Open the process handle and terminate it.
    > Is there any
    > other way of terminating a crashed COM server process ? or getting the
    > process handle ?
    >

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM