xi | specific language for live coding musical patterns | Audio Utils library

First create the grid mesh array (x,y,z) as 3-tuples using meshgrid then you can apply the function in sequence:

UserControl1 (added via the Designer) is showing but no data populated in ComboBox1. UserControl2 doesn't show (added at Form1 OnLoad event), and UserControl3 doesn't show via a Button event

The root issue is because you've wrapped the construction in using statements. For example:

ActiveMQ Artemis has no default connection limit. I just wrote a quick test based on this which uses the Paho 1.2.5 MQTT client. It spun up 500 concurrent connections using both normal TCP and WebSockets. The test finished in less than 20 seconds with no errors. I'm just running this test on my laptop.

I noticed that your journal-buffer-timeout is 700000 which seems quite high which means you have a very low write speed of 1.43 writes per millisecond (i.e. a slow disk). The journal-buffer-timeout that is calculated, for example, on my laptop is 4000 which translates into a write-speed of 250 which is significantly faster than yours. My laptop is nothing special, but it does have an SSD. That said, SSDs are pretty common. If this low write-speed is indicative of the overall performance of your VM it may simply be too weak to handle the load you want. To be clear, this value isn't related directly to MQTT connections. It's just something I noticed while reviewing your configuration that may be indirect evidence of your issue.

The journal-buffer-timeout value is calculated and configured automatically when the instance is created. You can re-calculate this value later and configure it manually using the bin/artemis perf-journal command.

Ultimately, your issue looks environmental to me. I recommend you inspect your VM and network. TCP dumps may be useful to see perhaps how/why the connection is being reset. Thread dumps from the server during the time of the trouble would also be worth inspecting.

I think I got the problem. First of all below is the way by which we can reproduce the error & the way you have proceed :

Here you have a good starting point. Not sure I understand your code, but this compiles:

Side notes:

• if you use C++, then it is not but
• single letter identifiers (variables and functions) is not recommended (except maybe for iterating ints), you should use significant names.

There are some issues with this implementation. start and end should remain iterators, they could be used directly without adding/subtracting nums.begin() all the time. We're talking about non-negative integers, so provided they fit into normal int first bit is 0 anyway, so we should start with int bit = 30 to skip one needless iteration. For integers right as for iterators as well, start <= end - 1 is better compared as start < end. The code consists of one single function, there's absolutely no need for a class then, so one should prefer a namespace. Applying these changes, the code would look like this:

I've taken your simplified configured with just 2 nodes using a non-wildcard queue with redistribution-delay of 0, and I reproduced the behavior you're seeing on my local machine (i.e. without Kubernetes). I believe I see why the behavior is such, but in order to understand the current behavior you first must understand how redistribution works in the first place.

In a cluster every time a consumer is created the node on which the consumer is created notifies every other node in the cluster about the consumer. If other nodes in the cluster have messages in their corresponding queue but don't have any consumers then those other nodes redistribute their messages to the node with the consumer (assuming the message-load-balancing is ON_DEMAND and the redistribution-delay is >= 0).

In your case however, the node with the messages is actually down when the consumer is created on the other node so it never actually receives the notification about the consumer. Therefore, once that node restarts it doesn't know about the other consumer and does not redistribute its messages.

I see you've opened ARTEMIS-3321 to enhance the broker to deal with this situation. However, that will take time to develop and release (assuming the change is approved). My recommendation to you in the mean-time would be to configure your client reconnection which is discussed in the documentation, e.g.:

Found the answer:

You can group the first geom_line with group and force the second geom_ribbon to take use as.numeric(xi) :