mq | MQ is a simple distributed in-memory message broker

If you refer to the Provided Sinks list and examine the source code for some of them, you'll notice that the pattern is usually:

1. Construct the sink configuration (usually taking values from IConfiguration, inline or a combination of both)
2. Pass the configuration to the sink registration.

Then the sink implementation instantiates the required services to push logs to.

An alternate approach I could suggest is registering Serilog without any arguments (UseSerilog()) and then configure the static Serilog.Log class using the built IServiceProvider:

You can define on custom retry strategy on implementing the interface IExecutionStrategy. If you want reuse the default SQL Server retry strategy, you can derive from SqlServerRetryingExecutionStrategy on override the method ShouldRetryOn :

Even though your configured persistent messages on the payments queue, this just means messages will survive a broker restart - once a message has been consumed and acknowledged it would be removed.

If you know you're going to need the payment_analyze queue at some point in the future, is it viable to just create this queue/binding upfront and route messages to both payment_analyze and payments? Messages on the payment_analyze will bank up until you're ready to start consuming them. Note: If you're producing a large number of messages this approach might result in storage issues...

As an alternative, you could write the messages to BLOB storage (or some other data store) as part of your payments queue consumer (or a different queue/consumer altogether) and then when you're ready to introduce the payment_analyze queue, you could write a script to read all the old messages from BLOB storage and send them to the RabbitMQ exchange. With 'topic' exchanges - see here - you can probably be clever with wildcards and routing keys in your queue bindings to ensure both old messages (from BLOB storage) as well as new messages are both routed to the payment_analyze queue, but only new messages are routed to the payments queue (so that your payments queue consumer is not reprocessing old messages).

Another option (assuming you're not overly invested in RabbitMQ) could be to consider Apache Kafka instead which deals with this scenario quite nicely as messages aren't automatically removed from a partition once they've been processed by a subscriber.

Anyways, just a few options to consider...

JSON CCDT support was not added to IBM MQ until 9.2 LTS. You won't be able to use it with a 9.1.0.7 RA.

Your only options are to use a binary CCDT or add/installed the 9.2 RA (rar) for WAS to use instead of the builtin 9.1.0.7 RA.

9.2.0.4 is the latest and you can download the java-all package to obtain the rar file.

I dont see any requirement for the input queue. It sounds as if your real requirement is

• Read an input file using a FileInput node
• Use JavaCompute to construct the output message tree
• Put the output message to the output queue

As pointed out by, @cigien this is indeed a clang bug. It works fine with gcc.

Check the log. Check if xdebug connects, if it tries to connect to correct ip. In my case it was trying to to connect to wrong ip. So needed to change this config to this value:

xdebug.remote_host=192.168.31.26

Next thing - PhpStorm started writing

Cannot parse server name for external Xdebug connection. To fix it create environment variable PHP_IDE_CONFIG on the remote server. Windows: set PHP_IDE_CONFIG="serverName=SomeName" Linux / Mac OS X: export PHP_IDE_CONFIG="serverName=SomeName".

So got in docker container and run the export. ServerName has to be same as Name field in PhpStorm config

Yes there was a change in behaviour.

In C you are supposed to only define a global variable in one translation unit, other translation unit that want to access the variable should declare it as "extern".

In your code, a.h is included in both a.c and main.c so the variable is defined twice. To fix this you should change the "int test" in a.h to "extern int test", then add "int test" to a.c to define the variable exactly once.

In C a definition of a global variable that does not initialise the variable is considered "tentative". You can have multiple tentative definitions of a variable in the same compilation unit. Multiple tentative defintions in different compilation units are not allowed in standard C, but were historically allowed by C compilers on unix systems.

Older versions of gcc would allow multiple tenative definitions (but not multiple non-tentative definitions) of a global variable in different compilation units by default. gcc-10 does not. You can restore the old behavior with the command line option "-fcommon" but this is discouraged.

seperator should be \n instead of \t while writing to the file. Also opening file in w mode inside the for loop overrides the previous contents of the file.