Quantcast
Channel: Service Bus forum
Viewing all articles
Browse latest Browse all 1916

JMS message listener invoker failed, Cause: Identifier contains invalid JMS identifier character '-': 'x-request-id'

$
0
0

I'm working with JMS and queues (Azure Queues) for the first time. I'm required to make a queue where Rubi server would write some data and Java would read it from queue and will do further executions. This process is working fine locally on my machine, I've created a REST endpoint which is writing data in the queue and once data is written in the queue, the listener would take over and read the data and execute. When we deploy it to Azure. The error I can see in logs which is not letting the Queues start is

Setup of JMS message listener invoker failed for destination 'queue-name' - trying to recover. Cause: Identifier contains invalid JMS identifier character '-': 'x-request-id'

Zipkin is also present on azure server as a distributed tracing system and I guess this x-request-id is related to zipkin which is creating problem. I've searched google for the issue but couldn't understand it why its happening. Any help would be highly appreciated as I'm stuck on this issue for two days. many thanks.


Viewing all articles
Browse latest Browse all 1916

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>