addTemporaryDestination() not called on the client side when advisorySupport="False"

In my effort to debug why I keep getting the "Cannot publish to a delete queue", I ran my example with activemqcpp code. I found that that on the consumer side when I call MessageProducer->send(replyTodestination, message) ultimately it ends up calling ActiveMQSessionKernel::send() in which

Re: ActiveMQCPP--Cannot publish to a deleted destinatination: temp-queue:

On 09/18/2018 09:38 PM, dpatel wrote: I did try to connect with the ?jms.watchTopicAdvisories=false in the uri. connection.watchTopicAdvisories=false -- Tim Bish

Re: ActiveMQCPP--Cannot publish to a deleted destinatination: temp-queue:

I did try to connect with the ?jms.watchTopicAdvisories=false in the uri. That didn't fix it. I ran my example with activemqcpp code. I found that that on the consumer side when I call MessageProducer->send(replyTodestination, message) ultimately it ends up calling ActiveMQSessionKernel::send()

Re: ActiveMQCPP--Cannot publish to a deleted destinatination: temp-queue:

I suspect you may be running into the problem that the client keeps track of known temporary destinations on the broker, and immediately rejects attempts to produce to temporary destinations that the client doesn't know about, even if they exist on the broker (although that's not the intent). This

Re: REST API - multiple users and authorizations

Hi Tim, Thanks for your response. For the HTTP REST queries with a Basic Auth, I only managed to use usernames and passwords defined in the file "jetty-realm.properties". As per my understanding, these queries then use the credential defined in the file "credentials.properties". I never managed

Re: no consumers for the queue by a duplex network connector

I found a bug in 5.14.0 as below: https://issues.apache.org/jira/browse/AMQ-6640 and when the problem happened,I collected the jstacek log as below which is the same as the log in the bug's description. and in my env, Broke A had more than 3 million pendding messages, but after I clean up most of

Re: jolokia cors and 0.0.0.0

Couple of things: - The "addresses" command-line parameter has nothing to do with network addresses. It's for specifying broker-level addresses (i.e. a place to send messages). - You can work-around the issue by using a real address rather than 0.0.0.0. Also, there is no way for t

Re: REST API - multiple users and authorizations

The Security section of http://activemq.apache.org/rest.html says "The API uses basic authentication header format to get username and password information." Have you tried that? Of so, what was the result? Tim On Wed, Sep 12, 2018, 1:15 PM ncasaux wrote: > Hello, > > I'm trying to configure Ac

jolokia cors and 0.0.0.0

Hi, found very strange issue while configuring artemis, which blocks web access. When i try to create instance with option --addresses=0.0.0.0 --http-host=0.0.0.0 cli correctly configures bootstrap.xml and broker.xml. it also adds http-host to jolokia-access.xml as 0.0.0.0 due to cli implemenati

Should the page-size-bytes be less than max-size-bytes for paging?

Hello folks, I'm quite new to artemis and trying to understand the paging configuration. Looking at the doc, I couldn't find the info whether page-size-bytes should be less than max-size-bytes. In all the examples they provide it is lesser by 5-10 times. Below is a sample config from them.