configurator | Fatten your models with key/value pairs

The general guidance is that consuming services should be deployed/started before producing services. And a bus shouldn't be used until it has been started.

While some of the values can be specified as query parameters on the destination address, the only ones supported by Azure Service bus are autodelete and type (only one of those is useful to end users).

The queue description/settings aren't updated because they would change constantly if services aren't consistent.

UPDATE: The other reason is that some deploy their topics/queues with resource manager scripts (or something like Terraform) and if MassTransit changed them it would break those deployments by removing their custom settings.

It's not a bug in keytool or KeyStore. keytool in OpenJDK 16 has been improved to use more secure algorithms by default, which are not supported with Java 8 and Java 11 (see JDK-8228481).

2 options to solve the problem:

• Use JKS instead of PKCS12 for the key store
• Use the -J-Dkeystore.pkcs12.legacy option with keytool to set the keystore.pkcs12.legacy system property and force OpenJDK 16's keytool to use the older algorithms (which are supported by Java 8 and 11)

For the keytool-maven-plugin Maven plugin, use the below configuration:

You don't need to worry about the number of "consumers" that show up in RabbitMQ. MassTransit uses the PrefetchCount to have messages sent from RabbitMQ to the connected "RabbitMQ Consumer." The consumers in MassTransit are completely unrelated, and managed entirely by MassTransit. So you'll only see one "consumer" in RabbitMQ, but that only represents the connection/channel for the bus instance. Multiple concurrency messages are dispatched by MassTransit up to the PrefetchCount limit. As MassTransit consumers complete, new messages are pushed by RabbitMQ and dispatched by MassTransit.

For the ELK stack to work you need all three PersistentVolumeClaim's to be bound as I recall. Instead of creating 1 30 GB of PV create 3 of the same size with the claims and then re-install. Other nodes have unmet dependincies.

Also please do not handle the volumes by hand. There are guidelines to deploy dynamic volums. Use OpenEBS for example. That way you wont need to worry about the pvc's. After giving the pv's if anything happens write again with your cluster installation process.

I was wrong obviously, in this particular problem, filesystems and cgroups take role and the main problem of this is an old problem. From 5.2.1 to 8.0.0. Reinstall the chart by pulling the chart. Edit values file and definitely change the container version. It should be fine or create another error log stack.

In the case where you copied the message class from the publisher to the consumer, you need to make sure the message type is the same, including namespace. This is clearly highlighted in the documentation. If the types don't match, that would explain why it wasn't consumed by the service.

Either approach, copying the files or having a shared NuGet package with the contracts, is fine. Both are widely used. MassTransit has guidelines on evolving message contracts to ensure backwards compatibility as well.

Since you're in a container and using --master local, that would limit you to a local filesystem, which you can access from file:// URI.

--files takes relative paths to where the files are located from where you run the command, and adds to the driver/executor classpath, I think

Putting those two pieces of information together, you can specify

Add to RouteConfig after IgnoreRoutes

This is how the content is organized - highlighted the bucket name:

You can either use the https://forge.autodesk.com/en/docs/data/v2/reference/http/buckets-:bucketKey-objects-:objectName-details-GET/ endpoint to get the ObjectId of the file or construct it yourself based on the template: urn:adsk.objects:os.object:/ Note: make sure the file name is URL encoded if making the REST call directly instead of using the Forge SDK

You can see what ObjectId is provided for a given file e.g. using the Autodesk Forge Tools Extension in VS Code:

You need to base64 encode the ObjectId in order to get the urn of the file and then use that to kick off the translation: https://forge.autodesk.com/en/docs/model-derivative/v2/tutorials/translate-zip-to-stl/

In case of a zip file you also have to provide the rootFilename (it's pointed out in the sample referenced above) - in case of e.g. the Wheel assembly that's the WheelAssembly.iam file

MassTransit defaults to TimeSpan.Zero, so unless specified there is no heartbeat configured.