ConfigManager | A configuration file manager for C # / .NET / Mono | Runtime Evironment library

The ArtemisCloud container image for ActiveMQ Artemis is designed to run inside a container so the container IP address should be used to access to the console or to other resources.

The container IP address can be obtained by using the command docker inspect or by reading the container log, ie:

The PayPal-NET-SDK mention in comments is deprecated and should not be used. If you are going to make API calls for anything other than the Checkout-NET-SDK or Payouts-NET-SDK use cases, use direct REST API calls.

The best method to obtain a list of transactions is to download an activity log report in CSV format from www.paypal.com

However, if for some reason you require an API for this accounting task, the only publicly available one is the Transaction Search API: https://developer.paypal.com/docs/api/transaction-search/v1 -- which you must enable for the client ID you are using, and wait up to 9 hours (or terminate the token) if you have already requested an access token with it.

Assuming this is the SQL Server JDBC driver, try using a newer version (e.g. current latest is 9.2.1), and see if that resolves the problem.

Alternatively, given your application server already provides JAXB, you could also try excluding the JAXB dependency from being pulled in again through the driver.

Looks like that issue is fixed and a new JAR is available.

See: https://forum.primefaces.org/viewtopic.php?f=68&t=66604

For some reason, mpg123 outputs its data on stderr, not stdout. Making the switch works like a charm, go figure.

This kind of behavior is expected when sending non-durable messages because non-durable messages are sent in a non-blocking manner. It's not clear whether or not you're sending non-durable messages, but you've also set blockOnDurableSend=false on your client's URL so even durable messages will be sent non-blocking.

From the broker's perspective the messages haven't actually arrived so there's no way to see the number of messages that have been sent but are not yet in the queue.

If you want to ensure that when the Camel route terminates all messages are written to the queue then you should send durable messages and set blockOnDurableSend=true (which is the default value).

Keep in mind that blocking will reduce performance (potentially substantially) based on the speed of you hard disk. This is because the client will have to wait for a response from the broker for every message it sends, and for every message the broker receives it will have to persist that message to disk and wait for the hard disk to sync before it sends a response back to the client. Therefore, if your hard disk can't sync quickly the client will have to wait a long time relatively speaking.

One of the configuration parameters that influences this behavior is journal-buffer-timeout. This value is calculated automatically and set when the broker instance is first created. You'll see evidence of this logged, e.g.:

Arguments to functions are either passed by-value or by-reference. Any variable passed by-value will be local to the function and any changes made to it is local to the function too. This means that when to assign a new value to the pointer (file = mConfigFile) you only change the pointer in the function. The pointer you passed as an argument is unaffected.

When taking arguments by-reference, the variable inside the function references the variable used to call the function. Any changes made to that variable will be directly made to the variable used in the call to the function.

In your case, that means that you need to change the ConfigManager::getConfigFile function:

Obtaining a token for the AAD B2C tenant without UI is possible in two ways and you should probably pick one depending on what exactly you want to achieve:

1. user token - by using Resource Owner Password Credentials flow - https://docs.microsoft.com/en-us/azure/active-directory-b2c/add-ropc-policy. This flow is deprecated though and mentioned usually in legacy application context
2. server-side application token - by using Client Cretendial flow - this on the other hand requires using requests specific for AAD but with AAD B2C tenant - https://docs.microsoft.com/en-us/azure/active-directory-b2c/application-types#daemonsserver-side-applications

I'm also not quite sure why should you use id_token for that. If the application needs to authorize the request to the function with the token then it should be an access token regardless of how the token is retrieved (interactive UI or not).

Validating a Token from the Graph API is a bit different than a standard OIDC Token.

See the following for more information: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/609