This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 94%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECH%3C/text%3E%3C/svg%3E)
After working without issue for a few months, we are now receiving the following error messages on all messages in the azure PubSub live trace tool.
Failed to send message: Send event to event handler failed...
Failed to send message: Upstream invocation error: Error while copying content to a stream...
It seems requests are hitting our API and a 200 response is being returned with a valid body, but the PubSub service is then throwing this error and not sending messages out to other clients in the group.
I cannot find this error message documented anywhere. What exactly does this error indicate? Is there any way we can see what response PubSub is receiving to determine if there is an issue with something between our API and PubSub?
Hi @Courtney Henderson I've reached out to the product group, and nothing sticks out. It would be helpful if you could provide the resource name, logs when this issue started occurring and if there were any recent deployments. Feel free to email this information to AzCommunity[at]microsoft[dot]com ATTN: Ryan. Include a link to this post and comment down below once you've sent it.
Hi @Courtney Henderson this is Liangying Wei from Web PubSub product team, the error message indicates that the message response stream was closed during reading. Could you share with me more about the message response in your event handler? What is the message type? How large is one message response? How long would one message event take to return a response? Could you email me lianwei[at]microsoft[dot]com your resource name for me to take a further look?
Thank you @Liangying Wei , I have emailed you with further details.
Thank you for posting you question @Courtney Henderson .
To benefit the broader community, the product group has discovered a bug in the service that caused this problem. They have a fix that will be applied for all the affected resources.