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

"Channel has already been signaled to stop" when sending many messages #650

Open
tiwari-abhishek opened this issue Mar 16, 2016 · 0 comments

Comments

@tiwari-abhishek
Copy link

What version of PushSharp are you using?

V2

Describe your issue:

Locally all messages are sent successfully, when deployed to staging environment, every now and then we see "channel has already been signaled to stop".

What are the steps required to reproduce this issue?

Please provide any Exception Stack Traces

System.ObjectDisposedException: Channel has already been signaled to stop
Object name: 'Channel'.

I know v2 is dead and wont be fixed, but I want to know the why this is happening so that I can fix it myself. Why does it work locally? Is there some RACE condition causing the channel to be stopped before all messages are sent?

I would really appreciate any information on how to fix this. I did apply the code change of doing a RaiseChannelException instead of throw new ChannelException but this shouldn't be happening at all.

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