COPPER 5.0 has just been released and is ready for Java 11. It is available on GitHub and in Maven Central.

COPPER has been upgraded to ASM 6.1, so Java 9, 10 and 11 are now supported in addition to Java 8. This release no longer supports Java 7 or older versions.

COPPER 5.0 adds support for the Java Platform Module System in order to let you build modular applications. However, if you don’t need this feature, you can use COPPER the same way as before.

We are also proud to announce the first release of our new Monitoring UI for COPPER, which is written as a modern single page application with Vue.js as JavaScript framework and communicating with the COPPER engine(s) via a JMX-REST Bridge (Jolokia). Note that for the UI to work, your engine needs to be on that 5 release.

Another addition to this release is a demo project showing how to build a modular application with Java 11 and COPPER 5. It provides a Gradle script for creating a custom runtime image of this application.

We are proud to announce that COPPER 5.0.0-alpha1 has just been released. It is available on GitHub and in Maven Central.

COPPER has been upgraded to ASM 6.1, so Java 9 and 10 are now supported in addition to Java 8. This release no longer supports Java 7 or older versions.

We also added support for the Java Platform Module System in order to let you build modular applications. However, if you don’t need this feature, you can use COPPER the same way as before.

In addition to the Java version upgrade, we are happy to share the alpha state of our new monitoring UI for COPPER, which is written as a modern single page application with Vue.js as JavaScript framework and communicating with the COPPER engine(s) via a JMX-REST Bridge (Jolokia). You can find the sources aon GitHub. Note that for the UI to work, your engine needs to be on that 5 release.

We are proud to anounce, that COPPER 4.2.0 has just been released. See https://github.com/copper-engine/copper-engine/blob/4.2.0/WHATSNEW.txt for changes.

You can get it here: https://github.com/copper-engine/copper-engine/releases/tag/4.2.0

Our new COPPER ‘Performance Test’ is now available. Check our performance test.

We are proud to anounce, that COPPER 4.1.1 has just been released. Besides a bugfix, this release contains a nice little performance enhancement which speeds up resubmit/savepoint and wait/notify in an idle system. In an idle copper engine, the database queue creator and readers sleep for a while before trying again. When a response arrives in copper (using ProcessingEngine.notify) the engine wakes up the queue creator to check for workflow instances that are ready to be resumed. If the creator has found at least one workflow instance to resume, it will wake up the database readers. Doing so, the latency times are as small as possible, unless the “notify” arrives AFTER the corresponding “wait” in the workflow is invoked.

If the “notify” occurs BEFORE the “wait”, the mechanism described above did not work, leading to long latency times because the queue processes are sleeping until their sleep interval is finished. In this release, we optimized this issuse. So even if the “notify” occurs before the “wait” there will be no unnecessary long latency times. On my local notebook with an Oracle 11g database the execution time of a resubmit/savepoint in an otherwise idle system melt down from 800ms to round about 10 to 20 ms.

You can get it here: https://github.com/copper-engine/copper-engine/releases/tag/4.1.1