Bart Koelman
Bart Koelman
Superseded by #1459.
[QUESTION] Usage of Steeltoe in OCF .Net6 Application to establish a connection with Onprem RabbitMQ
Can you clarify what OCF means? Also, did you set `SslEnabled` as described at https://docs.steeltoe.io/api/v3/connectors/rabbitmq.html? Is this an existing or new application you're developing? Furthermore, it would help if you...
[QUESTION] Usage of Steeltoe in OCF .Net6 Application to establish a connection with Onprem RabbitMQ
Thanks for providing the additional info. Can you also share the contents of the `VCAP_SERVICES` environment variable?
[QUESTION] Usage of Steeltoe in OCF .Net6 Application to establish a connection with Onprem RabbitMQ
For reference, here's the same `VCAP_SERVICES` from above, but with fixed quoting, reformatted, and other corrections: ```json { "label": "rabbitmq", "provider": null, "plan": "three-node", "name": "RabbitMQ-Instance", "tags": [ "blacksmith", "dedicated",...
[QUESTION] Usage of Steeltoe in OCF .Net6 Application to establish a connection with Onprem RabbitMQ
I believe the reason this `VCAP_SERVICES` binds to `amqps` is because of the following line, at JSON path `/credentials/uri`: ``` "uri": "amqps://testuser:testpwd@7487363f-b5dd-4c61-bb59-8ba56615b2af.node.ocf-namespace.rabbitmq-three-node-1234563f-b5dd-4c61-bb59-8ba56615b2af.bosh:5671", ``` From looking at the Steeltoe source code,...
[QUESTION] Usage of Steeltoe in OCF .Net6 Application to establish a connection with Onprem RabbitMQ
That sounds like the source of the problem then. If the OCF broker advertises to use `amqps`, then Steeltoe uses that. Please check if you're actually able to connect using...
I don't see the point of adding this, am I missing something? ASP.NET already provides built-in tracing for HttpClient usage.
I don't understand why a periodic background request to eureka should be correlated to an incoming request. There's no relationship between those execution flows. For example: 18:43:01 Incoming HTTP request...
Thanks, it would be nice to have built-in support for EasyNetQ, or at least have a sample demonstrating how it can be used. It shouldn't be hard to use already...
I tried this from a unit test, seems to work: ```c# builder.Services.RegisterEasyNetQ(serviceResolver => { var optionsMonitor = serviceResolver.Resolve(); RabbitMQOptions options = optionsMonitor.Get(null); var parser = serviceResolver.Resolve(); return parser.Parse(options.ConnectionString); }); await...