Václav Haisman

You do not need atomic access there because you still have to cover its use with mutex when you are using the conditional variable.

We have debugged the issue further and we can now see that Liquibase computes the MD5 sums from different strings. In our case, it seems the issue is on `addForeignKeyConstraint`....

Further debugging reveals that the issue is that we specify both `deleteCascade="true"` and also `onDelete="CASCADE"`. There is an issue in the `AddForeignKeyConstraintChange.setDeleteCascade()` method: https://github.com/liquibase/liquibase/blob/cedd404bf159f1cb923cac7454ea1b2ea5673b31/liquibase-core/src/main/java/liquibase/change/core/AddForeignKeyConstraintChange.java#L205-L211 If both are set, it executes...

After removing the `deleteCascade="true"` from the change set, the checksum returns to the same value as it was before for us.

There is currently no such function at the moment. I am open to patches in this direction. It would probably require each appender and layout to have the ability to...

There is a [UDP appender](https://log4cplus.github.io/log4cplus/docs/log4cplus-2.1.0/doxygen/classlog4cplus_1_1Log4jUdpAppender.html) that sends XML formatted events for log4j 1.2. There is nothing for log4j2. It would certainly be possible to create similar appender for log4j2.

Is this happening around startup of your process or shutdown of your process? I have seen similar errors when people were trying to log before `main()` was entered or after...

I think this works as intended. The `filename` is constant, e.g., `app.log`. When schedule period ends, the `filename`, gets renamed to `scheduledFilename` and the new current period uses the `filename`...

Any released version should work.

The 1.1.3 version does not support C++17 explicitly. It supports C++11. It might work with C++17 but I have not tested that. If you are going to compile from sources...