ipv6 | My project for IPv6 -

The address is truncated. Try using netstat with -l

I think what's happening here is that you've put the container name before the environment argument list to the docker run command.

So instead of setting the PACT_BROKER_DATABASE_NAME and other environment variables for the running container with your custom values, they are simply being discarded by the runtime.

Try this instead:

Search your code for where the @interface for ESPTaskParameter is defined, that will be in some .h file. Then, make sure the .m file #imports that header file. If it doesn’t the there would indeed be no visible interface defining the selector you want to call to the .m file that is trying to call it

And check that the interface .h does indeed declare a public setter for broadcast.

You just have another instance of Mosquitto already running.

Use ps ax | grep mosq to see if Mosquitto is still running outside of a container. If you find it, use sudo kill -9 PID where you replace PID with its process ID. Or you can try sudo killall -9 mosquitto.

If that doesn't solve the problem, check Docker.

Use docker ps to list all the Docker containers currently running.

Use docker stop ID where you replace the ID for each container that's running.

If you fail to find an instance of Mosquitto, reboot your computer and try again.

Non-logged in users got the error but logged in users didn't.

Codecov has some heisenberg issues. If you don't have a token, please add one otherwise try to:

• Force-push to retrigger Codecov
• Rotate your token.

Some parts of your question have been asked before.

Establishing an IPv6 connection using sockets in python

However, it is not the entire reason why it is not working correctly. If you look at your IPv6 address. fe80::cbdd:d3da:5194:99be%eth1 You can see the %eth1 at the end. That is not part of the internet address. Change HOST to HOST = 'fe80::cbdd:d3da:5194:99be'. And it should work.

I would also like to point out another error in your code. You are attempting to send a string (received from input) over the socket. However, this method only accepts byte like objects. You can add data = data.encode('utf-8') to fix this.

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.

Changing the command doesn't work because the /docker-entrypoint.sh contains: