question

RazeenHendricks-7065 avatar image
0 Votes"
RazeenHendricks-7065 asked MayankBargali-MSFT edited

Service Bus Communication Error

Good day,

I have a logic app that reads from a session-enabled queue. At most, there may be 2 instances of this running in parallel.
However, each instance would never use the same session ID when reading from queue as they represent different categories of data upon which the session ID is based.

On an ad-hoc basis (happens now and then), the following error is being experienced when trying to complete the message after having read it:


Communication with the Service Bus namespace '<service-bus-name>.servicebus.windows.net' and '<service-bus-queue>' entity failed.


I then attempted to introduce a retry loop, but the subsequent attempt then yielded the following error:

This messaging entity has already been closed, aborted, or disposed.

Any further attempts presents the following error (due to eventual token timeout I suppose):

No session available to complete the message with the lock token '<token>'.


Could you please explain why the communication error occurs, and how this may be resolved?

azure-logic-appsazure-service-bus
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Helllllllloooooooooooooooo????? @tbgangav-MSFT @MayankBargali-MSFT @SatishBoddu-MSFT @nasreen-akter Is there any idea on the service bus communication error?

0 Votes 0 ·

1 Answer

MayankBargali-MSFT avatar image
1 Vote"
MayankBargali-MSFT answered MayankBargali-MSFT edited

@RazeenHendricks-7065 Apology for the delay. Communication expection is the Transient error and logic app does handle these type of errors.
As you are using the session enabled queue so all the messages are send to the same partition for the same sessions. In case if there is any service updates/issue for that partition then there would be some expection/error during that time. As logic app service bus connector does have retry in place but if it failes till the max retry then the exception is throw and your workflow failed. But the next runs (once the upgrade completes) should eventuately suceeded and it should not effect your workflow but you should few runs getting failed during that time.

If you are observing these error for every run then I will suggest you to open as support ticket with us. If you don't have the support plan then please let me know so we can connect offline and assist you further.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@MayankBargali-MSFT It's very disappointing that this type of problem does not have a proper built-in handling mechanism in place. I've just experienced this error again today, so happens now and then.

The retry policy on the logic app states that it only comes into effect for HTTP status codes 408, 429 and 5xx
The HTTP status code I'm seeing on this service bus communication error is 400 (Bad request), and so means that logic app needs a custom solution to handle this, which then means that every logic app customer needs to build their own workaround. Makes no sense at all! Microsoft should be dealing with this as its a known environmental issue.

0 Votes 0 ·

@RazeenHendricks-7065 Apologies for any inconvenience with this issue. Manually retry the error such as: No session available to complete the message with the lock token '<token>'. will not help as the the lock token already expired and retring it will yield the same result. This would need to looked at from the backend logs to know the root cause of the issue. Please refer to my private comment for more details. Only operation that could suceeds in the further retry are handled in the logic app.

0 Votes 0 ·