Re: Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

I don't have personal experience running with that number of connected clients (I've only used ActiveMQ with a few dozen to a few hundred), but if it's a problem, the JVisualVM CPU sampling we talked about in that thread should make that clear pretty quickly. Tim On May 19, 2017 12:11 PM,

Re: JMX url in master/slave mode

I would recommend using a load balancer. You would put both up addresses in the load balancer. Thanks Sent from my iPhone > On May 19, 2017, at 3:17 PM, kpdude7 wrote: > > How would someone programmatically access the correct JMX server in this > master/slave

Re: AMQCPP -- Cannot publish to a delete Destination: temp-queue

I would use either a newer activemq or Artemis version. On Fri, May 19, 2017 at 8:09 PM bobeo wrote: > hi Tim, > > Maybe I wasn't clear enough. Let me make it clear again: > > First, I have a queue : sn.queue.settings. > > From Java, I send a message to that queue, and I

Re: AMQCPP -- Cannot publish to a delete Destination: temp-queue

hi Tim, Maybe I wasn't clear enough. Let me make it clear again: First, I have a queue : sn.queue.settings. >From Java, I send a message to that queue, and I can see from the log of activemq broker, I highlight important bits: INFO | Sending message: ActiveMQTextMessage {commandId = 24,

Re: Client compatibility of Artemis with AMQ and HQ

I'm not sure about 2.4.7 but it should work. The thing thought is the prefix on acceptors With 2.1.0 destinations won't have prefixes. So you may have to tweak the configuration. Maybe having a different port for newer clients. On Fri, May 19, 2017 at 9:46 AM Claudio Tagliola

JMX url in master/slave mode

How would someone programmatically access the correct JMX server in this master/slave configuration? For example, I have the JMX url: service:jmx:rmi:///jndi/rmi://${jmxTransferUrl}/jmxrmi My JMS is using a failover url: failover:(ssl://10.91.5.190:61616,ssl://10.91.5.115:61616) What value

Migrating storage from 5.10.0 to 5.14.5

Good Day, I've been working on migrating servers and upgrading from 5.10.0 to 5.14.5. We have a number of scheduled tasks and I want to preserve those along with other items in the queue. I tried moving the files in kahadb to the new server (after shutting down both servers), but have run into

Re: Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

Artemis has a new architecture and is more effective on keeping managing connections. Starting from the Journal where we do everything asynchronous using a lot less threads and more performant. It's the reason why Artemis merged ActiveMQ.. and it's been quite improved at 2.1.0.. It's worth to at

Re: Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

@clebertsuconic, ActiveMQ also supports NIO and we have already configured to use it. How is this different from that supported in Artemis? -- View this message in context:

Re: Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

Tim, each client process will open just one connection. There can be hundreds of thousands of different client processes (as many as no of users using our app) connected to the broker at the same time. In another thread

Random port listening on 0.0.0.0 for tcp transport

When I start up an activemq broker, besides listening on the configured ports of 61616 and 8161 it is also listening on a random port. My problem is that I can not find out how to configure the interface that it should listen on. It listens on 0.0.0.0 which is not acceptable for my company's

Re: ActiveMQ broker becomes unresponsive after sometime

Hi!!! In the last period I'm enjoying using this: http://gceasy.io/ You need to pass the following JVM arguments: -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:[file-path] With [file-path] as the location where garbage collection log should be saved. Then run your

Re: ActiveMQ broker becomes unresponsive after sometime

Hahah .. that's okay :-) I have never used JVisualVM; will understand how to use this tool and report my observations. Thanks for all inputs so far! -- View this message in context:

Client compatibility of Artemis with AMQ and HQ

We have two separate projects in development, one project running on HornetQ 2.4.7 and another on ActiveMQ 5.8.0. Currently we are investigating in upgrading at least the HQ one to Artemis, as HQ is no longer maintained. Next to this, we might also migrate the AMQ one, to simplify our software

Re: AMQCPP -- Cannot publish to a delete Destination: temp-queue

hi Tim, I'm facing the same problem of Cannot publish to a deleted Destination: temp-queue:// I've tried both Java server - C++ client and C++ server - C++ client , but both end up with the same error "Cannot publish to a deleted Destination: temp-queue://" I'm using Activemq 3.9.1 on Ubuntu.

Re: Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

Why don't you look at ActivMQ Artemis. It's using NIO/epoll so it won't use as much memory as you keep lots of active connections. On Fri, May 19, 2017 at 8:42 AM, Tim Bain wrote: > If you have many connections from a single client process, then yes, that's > an

Re: ActiveMQ broker becomes unresponsive after sometime

My brain swapped the units in your description, to an 8 minute GC with unresponsiveness 15 seconds later. Sorry for the confusion. 8 seconds is long, but not unheard of, especially if the heap is large. G1 aims to shorten the Old Gen GC pause time by doing multiple small GCs of Old Gen rather

Re: Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

If you have many connections from a single client process, then yes, that's an antipattern. Connection setup/teardown is somewhat expensive (and everyone will have to do it at the same time if the broker restarts), so you should be minimizing the number if possible by using a pooling connection

Re: Pure JMS management

Create a JIRA as well. Thanks. On Fri, May 19, 2017 at 2:21 AM Guillaume Nodet wrote: > It seems to work well for me. > I'll run a full build and will create a PR. > > 2017-05-19 8:03 GMT+02:00 Guillaume Nodet : > > > I'm enhancing a layer in OSGi to

Is creating thousands of connections to a single AMQ broker node and keeping them open an anti-pattern?

We use a single AMQ broker (using 5.14.1 version) node to exchange MQTT messages between our server and apps running on mobile devices (both Android and iOS). The app establishes a connection with AMQ broker using Eclipse Paho client lib. To be able to receive messages as soon as they are

Re: ActiveMQ broker becomes unresponsive after sometime

Tim, full GC takes 8 seconds, not 8 minutes. Also, after full GC, large amount of memory is reclaimed (13G to <2G) : 2017-05-17T14:01:46.179+0530: 34205.488: [Full GC2017-05-17T14:01:46.179+0530: 34205.488: [CMS: 13039360K->1895795K(26214400K), 8.5260340 secs] 13578056K->1895795K(27158144K),

Re: Pure JMS management

It seems to work well for me. I'll run a full build and will create a PR. 2017-05-19 8:03 GMT+02:00 Guillaume Nodet : > I'm enhancing a layer in OSGi to support Artemis, and I'd like to avoid > adding package dependencies. > That's why I'm using the connection's classloader to

Re: Pure JMS management

I'm enhancing a layer in OSGi to support Artemis, and I'd like to avoid adding package dependencies. That's why I'm using the connection's classloader to load the needed class, as it's not available from the class which defines this code. To refine my question further: could the reply be typed as