decider | Apply CSS to React components | Frontend Framework library

Increase memory, for example with VM option -Xmx4g

Also note that parallelBenchmarkCount AUTO currently doesn't take into account that moveThreadCount is not NONE. So your benchmarks will not be accurate, because if you have 16 cores, parallelBenchmarkCount AUTO will resolve to 8. With moveThreadCount 4 (+ 1 solver thread), you'll be using 32+ cores but only have 16 cores. This probably should be reported as an issue in optaplanner's jira for parallelBenchmarkCount AUTO.

Generally speaking, if your constraint compiles and the code still throws ClassCastException at runtime, you should expect the bug to be on the OptaPlanner side. Unless you are willing to look at the Drools executable model, there is nothing for you to debug there.

I recommend refactoring the constraint to look like this:

a few things

• high cpu or memory use will not be due to not setting those gateway settings, and as a single node cluster they are somewhat irrelevant
• we recommend keeping heap <32GB, see https://www.elastic.co/guide/en/elasticsearch/reference/current/advanced-configuration.html#set-jvm-heap-size
• you can never allocate replica shards on the same node as the primary. thus for a single node cluster you either need to remove replicas (risky), or add another (ideally) 2 nodes to the cluster
• setting up a multiple node cluster on the same host is a little pointless. sure your replicas will be allocated, but if you lose the host you lose all of the data anyway

I'd suggest looking at https://www.elastic.co/guide/en/elasticsearch/reference/7.14/bootstrap-checks.html and applying the settings it talks about, because even if you are running a single node those are what we refer to as production-ready settings

that aside, do you have Monitoring enabled? what do your Elasticsearch logs show? what about hot threads? or slow logs?

(and to be pendantic, it's Elasticsearch, the s is not camelcase ;))

Spring Batch does not allow alternative branches in the flow to be implicit. In other words, you need an on(...) for each case.

Assuming decider() yields a proxied bean, it should work fine with

testQ & testA are not initialized. Initialize them with an empty list.

To fail a workflow using the Flow Framework throw an Exception or its subclass from the workflow code.

Don't throw an Error from the workflow code. This indeed is going to fail a decision task which will lead to the workflow getting blocked in a retry loop.

(Just repeating/extending @hornisgrinde's comment here so this question has a clear answer.)

Run mvn dependency:tree (or the equivalent gradle command), make sure that all optaplanner-* and drools-* versions are in sync.

In this case, the classpath contained both optaplanner-test 8.3.0 and optaplanner-core 8.7.0, which got shadowed by optaplanner-tests transitive dependency on optaplanner-core I believe. To avoid this issue altogether, use optaplanner-bom.

All the answers you're looking for are in the users guide (and manpage)

Firstly, assuming you don't want to scan the input files to add included files specified in the input files, you can use Commmand() (See info here: https://scons.org/doc/production/HTML/scons-user.html#chap-builders-commands)

Then you'll want an alias to specify an a non file command line target (See here:https://scons.org/doc/production/HTML/scons-user.html#chap-alias)

Putting those two together yields

Not sure if xhr.send sends in JSON format, but in any case, try catching the post with: