You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: