Hi,
There are some serious problems when using Qpid JMS client with Service Bus (both Azure and on premise). For example:
1. When there is nothing on the queue and the client sends a Flow frame with "drain=true", Service Bus doesn't answer anything. That blocks the client and causes a timeout error later.
2. When prefetching messages without consuming them, Service Bus locks them for the "Lock Duration" interval. When closing the consumer, the client sends Detach and then explicitly releases all unconsumed messages. However, Service Bus seems to ignore the Disposition frames sent after Detach and therefore all those messages stay locked.
Can someone from Microsoft comment on these issues? Are there any workarounds?
Thanks!
There are some serious problems when using Qpid JMS client with Service Bus (both Azure and on premise). For example:
1. When there is nothing on the queue and the client sends a Flow frame with "drain=true", Service Bus doesn't answer anything. That blocks the client and causes a timeout error later.
2. When prefetching messages without consuming them, Service Bus locks them for the "Lock Duration" interval. When closing the consumer, the client sends Detach and then explicitly releases all unconsumed messages. However, Service Bus seems to ignore the Disposition frames sent after Detach and therefore all those messages stay locked.
Can someone from Microsoft comment on these issues? Are there any workarounds?
Thanks!