Re: ActiveMQ REST Api with HTTP

Hello, Excellent advice: You should be able to publish your messages and then look at them in the web console to confirm that the right values are getting set. I see all my messages in the wed admin console. I see the property test=2 associated with the message.

Re: ActiveMQ REST Api with HTTP

Is what you're doing (setting them via request parameters on the URL) the right way to set message header properties (e.g. test=2)? The page doesn't say explicitly, but I had assumed that you'd need to use the --header approach. You should be able to publish your messages and then look at them in

Re: ActiveMQ REST Api with HTTP

Hello, Point 1: I insert the the 4 following messages curl -u admin:admin -d "hello world 1" -H "Content-Type: text/plain" -XPOST "http://localhost:8161/api/message?destination=queue://Test_Kovac&&clientId=KovacIP1"; curl -u admin:admin -d "test selector" -H "selector test" -H "Content-Type: te

Re: ActiveMQ REST Api with HTTP

Hello Tim, First of all, thank you very much for replying. Concerning point 1: I have read your answer and I believe you are right. The clientID is not a filter. My Question: What is the function of the clientID, since I can asssign any value to it and it will work? Bottom line, I don't underst

Re: ActiveMQ REST Api with HTTP

As I understand it, the clientId parameter isn't a selector; rather, it ensures that your consumer gets messages consistent with what has already been delivered to it even if the session has expired, but it is not meant to specify that you only consume messages produced by yourself. So the delivery