Setup of JMS message listener invoker failed for destination 'queue-name' - trying to recover. Cause: Local transactions cannot span multiple top-level entities such as queue or topic. TrackingId:some_tracking_id, SystemTracker:gateway5, Timestamp:2024-02-29T21:57:11 [condition = amqp:not-allowed] about azure-sdk-for-java HOT 4 OPEN

Hi @Ahmetanakol , Thank you for reporting this issue. We have received your submission and will take a look. Could you help provide a minimal project and complete logs?
Please feel free to provide any additional information or context that you think may be helpful. We'll keep you updated on the progress of our review.

from azure-sdk-for-java.

Possibly related issue: #29881

from azure-sdk-for-java.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @chenrujun @moarychan @Netyyyy @saragluna.

from azure-sdk-for-java.

Hello @Netyyyy , I created a sample project in order to simulate the behaviour we are seeing in our production application. However I am not sure what triggers this behaviour. Meanwhile, I can share some of the logs that contains tracking ids I believe they can help you with the investigation.

Log level: WARN

Logger Class: org.apache.qpid.jms.provider.amqp.builders.AmqpResourceBuilder

Message: Open of resource:(JmsConsumerInfo: { ID:d7f8d045-3753-4eb3-b676-cce0b0f8cc71:14:12:63982, destination = fueling-process-initiated }) failed: Local transactions cannot span multiple top-level entities such as queue or topic. TrackingId:f2e784d0b104442092dfeed33a988b35_G5S2, SystemTracker:gateway5, Timestamp:2024-03-04T14:10:35 [condition = amqp:not-allowed]

I am attaching the sample project too. You can see how we send messages to the queues and consume those messages via JmsListeners.

demo.zip

from azure-sdk-for-java.