Gentics CMS EE 6.0.9
Bugfix SUP-15945 Link to this entry
Execution of external tasks in the scheduler has been improved: stdout and stderr of the executed command (script)
will now not be buffered, but will be redirected to log files. This fixes problems with commands that create lots of output (e.g. curl, if the request runs for a long time),
which could cause some executions to hang forever.
Additionally, the display of scheduler executions has been improved:
- Running scheduler tasks will now be shown as “Running“ (instead of “Failed”)
- Running scheduler tasks will now show the current duration instead of 0
Gentics Aloha Editor 1.5.0
No changesGentics Mesh 2.0.8
Bugfix SUP-15948 Link to this entry
GraphQL: Performance optimizations of the Elasticsearch-based requests.
Bugfix SUP-15895 Link to this entry
GraphQL: Some more multithreading issues with initialization of GraphQL have been fixed.
Bugfix SUP-15949 Link to this entry
Core: Requests to branches failed with an internal error, if monitoring was disabled. This has been fixed.
Bugfix SUP-15949 Link to this entry
Core: The new configuration option `vertxOptions.orderedBlockingHandlers` allows to change the behaviour of concurrent handling of “long running” requests
(requests that modify data or GraphQL requests). If the option is set to `true` (default value) such requests will be run in order (per http verticle) and never concurrently.
As a consequence, it may happen that e.g. GraphQL requests are queued for some time if some other requests are currently handled.
If the option is set to `false`, blocking requests will only be queued, if all threads of the worker pool are currently busy.
Gentics Mesh SQL 2.0.9
Bugfix SUP-15948 Link to this entry
GraphQL: Performance optimizations of the Elasticsearch-based requests.
Bugfix SUP-15948 Link to this entry
GraphQL: Performance optimizations of the Elasticsearch-based requests.
Bugfix SUP-15949 Link to this entry
Core: The new configuration option `vertxOptions.orderedBlockingHandlers` allows to change the behaviour of concurrent handling of “long running” requests
(requests that modify data or GraphQL requests). If the option is set to `true` (default value) such requests will be run in order (per http verticle) and never concurrently.
As a consequence, it may happen that e.g. GraphQL requests are queued for some time if some other requests are currently handled.
If the option is set to `false`, blocking requests will only be queued, if all threads of the worker pool are currently busy.
Bugfix SUP-15949 Link to this entry
Core: Requests to branches failed with an internal error, if monitoring was disabled. This has been fixed.
Bugfix SUP-15895 Link to this entry
GraphQL: Some more multithreading issues with initialization of GraphQL have been fixed.
Bugfix SUP-15949 Link to this entry
SQL: Due to incorrect SQL statements, deleting of nodes could be very slow. The SQL statements have been fixed.
Bugfix SUP-15949 Link to this entry
SQL: Some more possible `Too many SQL parameters` occurrences have been fixed.
Gentics Mesh Commercial Plugins 2.0.3
Bugfix SUP-15964 Link to this entry
Forms: Adds new configuration options security.injectionPreventionMode and security.sanitationRules to either mark unsafe posted values as validation errors or sanitize the values before storing them.