Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RabbitAdvancedPublishChannel.Dispose #65

Closed
ghost opened this issue Jan 28, 2013 · 7 comments
Closed

RabbitAdvancedPublishChannel.Dispose #65

ghost opened this issue Jan 28, 2013 · 7 comments

Comments

@ghost
Copy link

ghost commented Jan 28, 2013

Hi,

thanks for your great libary.
I have a Problem with the Class RabbitAdvancedPublishChannel.

I don't know where i came from, all other calls work perfect.

If i debug the code, the system hangs at Dispose()

public virtual void Dispose() { if (disposed) return; channel.Abort(); //Here hangs the app channel.Dispose(); disposed = true; }

the calling name is in a contructor with MEF Injection
using (var x = m_bus.OpenPublishChannel()) { x.Publish<TapiRefreshCommand>(new TapiRefreshCommand()); }

@ghost
Copy link
Author

ghost commented Jan 28, 2013

Thanks for reporting this Andreas. I can't see any reason why this should happen. My tests do publishing inside a using statement just like yours without any issues. Do you have any other context? Are you publishing in a tight loop or on lots of different threads for example?

@ghost
Copy link
Author

ghost commented Jan 31, 2013

I compiled everything againt the current sources an the problem is in
RabbitMQ.Client.Impl.ModelBase.Close(ShutdownEventArgs reason, bool abort)
stopped at k.Wait();

this happed at a Hyper-V virtualized machine with Windows 2008R2

@ghost
Copy link
Author

ghost commented Jan 31, 2013

Hmm, so it's in the RabbitMQ.Client. I wonder what it's waiting on?

@ghost
Copy link
Author

ghost commented Jan 31, 2013

I don't know. On my machine it works, on the server not. :(

@ghost
Copy link
Author

ghost commented Jan 31, 2013

So now it works. :-)
Seems there was an update in the background on the Server from the dot net framework.

Hours wasted :(

Thank you, for helping

@ghost ghost closed this as completed Jan 31, 2013
@ghost
Copy link
Author

ghost commented Jan 31, 2013

Hard for me to progress it if I can't reproduce it I'm afraid :(

@mikehadlow
Copy link
Contributor

Cool, glad to hear that :)

On Thu, Jan 31, 2013 at 9:57 AM, Mike Hadlow notifications@github.comwrote:

Hard for me to progress it if I can't reproduce it I'm afraid :(


Reply to this email directly or view it on GitHubhttps://github.com/mikehadlow/EasyNetQ/issues/65#issuecomment-12935201.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant