Re: Unsubscribing DurableSubscribers

Sorry for the poor copy paste. This the good one. Here is the problem I think and why close method not resolve your error : receiver1.receiveMessage(u2); receiver1.receiveMessage(u3); Calling receiveMessage many times on the same object as you designed will overwrite your consumer reference and t

Re: Unsubscribing DurableSubscribers

Unsubscribe durable subscribers with ActiveMQ up vote 0 down vote favorite I'm trying to UNSUBSCRIBE durable subscribers from TOPICS. My app is a kind of social network : each user is a topic for other users. So, each time a user is doing something, his friends are notified. Of course, a subscrib

Re: EmbeddedJMS doesn't register JMS topics or queues

Either use JNDI (see numerous examples shipped with Artemis) or don't use a lookup at all (i.e. just instantiate the destination programmatically). Justin - Original Message - From: "mcacker" To: users@activemq.apache.org Sent: Friday, September 16, 2016 1:18:07 PM Subject: EmbeddedJMS

Re: Unsubscribing DurableSubscribers

​​ Good evening Tim, thanx a lot for responding me. The response is YES. I've got 3 topics living and each has got 2 subscribers (it's my test case). Topics have been created. DurableSubscribers have registered. In case they disconnect, a listener is ON for each topic. Each subscriber has got

EmbeddedJMS doesn't register JMS topics or queues

Hi, I'm in the process of migrating from HornetQ to Artemis and have run into an issue with EmbeddedJMS. After processing the configuration file, i'm expecting the MapBindingRegistry (i'm not using JNDI) to have references to the configured queues and topics, like it did in HornetQ, but the regis

Re: Messages lost

Ravi, You appear to be doing request-response. In that paradigm, the message is delivered to your consumer, runs through your code, and your code eventually produces a response message that the broker accepts. The most likely reason that a response message would not be enqueued on the broker is

Re: Unsubscribing DurableSubscribers

At the time you try to unsubscribe, is a client with that ID connected? If so, you need to close the existing consumer before unsubscribing. Tim On Sep 16, 2016 8:01 AM, "Lovegiver" wrote: > Hello there,I'm trying to *UNSUBSCRIBE durable subscribers from TOPICS*.My > app is a kind of social ne

Re: [Artemis] Messages stuck in "Delivering" state infinitely

I assume you did this before you restarted the broker. Is that correct? If so, did the consumerCount ever reach 0? If so, did the deliveringCount stay > 0? Assuming each client is coming from a unique IP address you could invoke listConnectionsAsJSON() to get the IP address of every client a

Re: [Artemis] Messages stuck in "Delivering" state infinitely

There was a change on 1.4.0.. Whenever the TCP is closed, the connection will be released. (Unless you enable reconnect by setting confirmation-window-size) On Fri, Sep 16, 2016 at 10:38 AM, abhijith wrote: > Yes, we did see few dangling connections and I got the connection id's for > the same.

Re: [Artemis] Messages stuck in "Delivering" state infinitely

Yes, we did see few dangling connections and I got the connection id's for the same. Right now there is no JMX operation to close single connection based on connectionId. The only way I could do this was to close all existing connections for the given user. -- View this message in context: ht

Re: [Artemis] Messages stuck in "Delivering" state infinitely

Assuming that the messages that were "stuck" in a delivering state were actually being consumed by a stalled client then you should be able to return those messages to a non-delivering state by disconnecting the corresponding client. There are a handful of JMX operations to close client connect

Unsubscribing DurableSubscribers

Hello there,I'm trying to *UNSUBSCRIBE durable subscribers from TOPICS*.My app is a kind of social network : each user is a topic for other users. So, each time a user is doing something, his friends are notified.Of course, a subscriber may unsubscribe from a topic, wanting to receive notifications

[Artemis] Messages stuck in "Delivering" state infinitely

Hi, We found that few messages were not getting delivered by Artemis. When we ran count-messages using JMX it was returning correct number of messages on queue. But listMessages was returning empty. Then listDeliveringMessages showed all the messages. But messages were stuck in this state in

Can I Receive and Disconnect simultaneously

Hi Everyone, I would like to know if the following it thread-safe (in the sense of being data-race free). In my program one of the threads calls MessageConsumer::receive() and blocks until it receives a message. At the same time, in another thread, I get a signal from the user to shut the program

Re: Messages lost

Tim, I could see the same thing in My Console also. However REQ queue's En-queued and dequeued number should match with my Response queue's Enqueued also. Attaching the screenshot where I could see 9 messages were lost and I could not see those messages in anywhere.

Re: [Artemis] Error message in log file for cluster on v1.3

Can you provide a reproducible test-case? Have you tried with Artemis 1.4.0? Justin - Original Message - From: "abhijith" To: users@activemq.apache.org Sent: Thursday, September 15, 2016 8:13:09 PM Subject: Re: [Artemis] Error message in log file for cluster on v1.3 We are still facin