RabbitMQ unexpected disconnect when a process is started by console app

[nps]

Hi All, 

New to RabbitMQ, and experiencing an issue that I haven't been able to figure out yet.

Have an asp.net 4.0\c# web application and rabbitMQ being used.  It works fine except for one scenario.  In the code when calling a win32 console app that does a Process.Start to write some data to the console:

            process32.Start();

            byte[] stuff;

            using (Stream stdout = process32.StandardOutput.BaseStream)

            {

                var size = 250000;

                stuff = ReadFully(stdout, size);

            }

            process32.WaitForExit(300000);

            int returnValue = process32.ExitCode;

as soon as it gets to the ExitCode line above, it causes RabbitMQ to think it was disconnected when it was not. 

The error is:

{AMQP close-reason, initiated by Application, code=541, text="Domain Unload", classId=0, methodId=0, cause=}

Guessing that this console app call is causing an app domain unload, but not sure why.

Anyone ever run into this or have any suggestions?

[Michael Klishin]

On 25 July 2014 at 19:06:17, nps (noree...@gmail.com) wrote:
> > The error is:
> {AMQP close-reason, initiated by Application, code=541, text="Domain
> Unload", classId=0, methodId=0, cause=}
>
> Guessing that this console app call is causing an app domain unload,
> but not sure why.
>
> Anyone ever run into this or have any suggestions?

This is an ASP.NET question I'm afraid. I can't think of why a process
started can lead to an AppDomain being unloaded. 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ