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
I'm not sure if this is the right place, but Microsoft support pointed me here. Feel free to direct me to the right place.
First thing: we don't use azure-service-bus-java, but the qpid-jms library to communicate with the Service Bus (premium tier).
Occasionally we get (a few messages out of tens of thousands a day) that a message transaction cannot be acked. The following errors can be found in Insights:
Caused by: org.apache.qpid.jms.provider.ProviderException: Transaction is not declared Reference:5a340f1b-d7ae-41de-be7d-51b974ada1ba, TrackingId:de27835d-7c58-455b-83d4-0a6c6de8c3e0_G2S1, SystemTracker:gtm, Timestamp:2023-01-19T09:41:23 [condition = amqp:transaction:unknown-id]
Caused by: org.apache.qpid.jms.provider.ProviderException: Transaction hasn't been declared yet, or has already been discharged [condition = amqp:transaction:unknown-id]
Caused by: org.apache.qpid.jms.provider.ProviderException: Unknown error from remote peer
Potential causes, which turned out not to be the case:
qpid-jms version (tried newer version, still same errors)
2 minutes transaction timeout (processing can take only few seconds and the error occurs)
Environment:
Java 17
Springboot + Spring JMS + qpid-jms
Service Bus premium tier
AKS, container image based on openjdk:17-jdk-slim
Could this problem be caused by a wrong consumer/producer configuration? Here is a link to a sample consumer/producer project whose JMS configuration corresponds to our production services.
I'm not sure if this is the right place, but Microsoft support pointed me here. Feel free to direct me to the right place.
First thing: we don't use azure-service-bus-java, but the qpid-jms library to communicate with the Service Bus (premium tier).
Occasionally we get (a few messages out of tens of thousands a day) that a message transaction cannot be acked. The following errors can be found in Insights:
Caused by: org.apache.qpid.jms.provider.ProviderException: Transaction is not declared Reference:5a340f1b-d7ae-41de-be7d-51b974ada1ba, TrackingId:de27835d-7c58-455b-83d4-0a6c6de8c3e0_G2S1, SystemTracker:gtm, Timestamp:2023-01-19T09:41:23 [condition = amqp:transaction:unknown-id]
Caused by: org.apache.qpid.jms.provider.ProviderException: Transaction hasn't been declared yet, or has already been discharged [condition = amqp:transaction:unknown-id]
Caused by: org.apache.qpid.jms.provider.ProviderException: Unknown error from remote peer
Potential causes, which turned out not to be the case:
Environment:
Could this problem be caused by a wrong consumer/producer configuration? Here is a link to a sample consumer/producer project whose JMS configuration corresponds to our production services.
Again, if this repository is not the right place, please direct me somewhere more suited for solving this issue.
Tagging @miroslav-staffa for updates.
The text was updated successfully, but these errors were encountered: