Qorus Integration Engine® Enterprise Edition 6.0.27_prod
|
Latest version: Qorus 6.0.27
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4116 | High | worked around a platform bug related to openssl where the full certificate chain was not available from the server despite all required certificates being present in the certificate file |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
GitHub 108 | Normal | Fixed a bug in the UI where it was not possible to use workflow order links generated from a search query containing % characters |
4113 | High | fixed a dynamic memory leak in service calls related to the service call performance optimization introduced in 6.0.25 |
4111 | Normal | fixed a bug where the WORKFLOW-ORDER-CONTROL did not allow users to skip workflow steps as documented |
4110 | High | fixed a deadlock when recovering the active master and a recovered process dies before the notification messages can be ackknowledged |
4109 | High | fixed a deadlock in Qorus cluster recoveries when running in Kubernetes |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
GitHub 105 | Normal | It was not possible to scroll to the bottom in the export CSV modal |
GitHub 101 | Normal | The sort workflow instances modal could not be closed |
4107 | High | improved performance with Qorus service calls |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4087 | High | improved Qorus workflow execution performance and scalability |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4106 | High | Fixed a bug on Oracle where a deadlock can occur when loading jobs due to missing indices on child tables with foreign constraints on the JOBS table |
4103 | High | Fixed a bug where qorus could fail to recover a cluster instance due to internal bugs |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4102 | High | Fixed a bug where async array backend functions or methods could not be executed |
4101 | Normal | Fixed a bug where DB server communication errors when recovering a qorus-master process cause transactions to hang indefintiely; in these cases the process is terminated and can recover normally on restart |
4100 | Normal | Fixed a bug in the system.info service where the UI would not find workflow orders in the archiving schema when searching |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4098 | Normal | Fixed a bug archiving workflow orders in large Qorus instances with complex hierarchies and a large number of orders to be archived |
4095 | Normal | Fixed a bug archiving on Oracle DBs with space management enabled |
4094 | Normal | Fixed a bug archiving objects with loggers |
GitHub 101 | Normal | fixed a bug where the workflow order status dialog could not be closed |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4091 | Normal | Respect qorus.use-functional-indices in the call to info.getWorkflowInstances() |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4090 | High | fixed a bug in schema archiving as well as setting up an archiving schema with schema-tool while Qorus is running |
4089 | High | fixed a potential deadlock recovering Qorus clusters running in Kubernetes |
4087 | High | improved Qorus workflow execution performance and scalability |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4088 | High | fixed a race condition shutting down Qorus and stopping workflows |
4087 | High | improved Qorus workflow execution performance and scalability |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4086 | High | fixed returning incorrect workflow order and job instance counts due to a bug in combining data from snapshot queries and the live DB |
4085 | High | fixed monitoring of Qorus remote connections hased on HTTP |
4085 | High | fixed monitoring of Qorus remote connections hased on HTTP |
4084 | Normal | reduced the contention on global connection lock when acquiring connections to increase performance and scalability for large Qorus instances |
4083 | Normal | fixed an error recovering Qorus cluster failover events that could cause a deadlock |
4082 | Normal | fixed a bug where it was not possible to update the monitor attribute of connections with the REST API |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4080 | Normal | implemented the qorus.use-functional-indices option for Oracle to enable the usage of functional indices in workflow status queries |
4079 | Normal | greatly reduced contention on an internal connection lock to increase scalability in large Qorus instances perfoming a large amount of parallel SQL I/O |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4078 | Normal | fixed upgrading the Qorus schema from 3.* to 5.1 or greater |
4077 | Normal | fixed packaging of tar releases for EL8 |
4076 | Normal | added the qorus.http-idle-disconnect option to allow the HTTP idle disconnect period to be changed |
4074 | Normal | fixed slow ostart performance with a workflow execution instance file |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4073 | High | fixed a bug where Qorus would not run under podman |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4072 | High | fixed a bug where workflow orders with incomplete processing were incorrectly read into the queue for new orders |
4071 | High | fixed a crashing bug handling workflow order priorities |
4070 | High | raised the maximum thread limit to 8192 to allow for additional scalability for very large Qorus instances |
4069 | High | fixed scalability issues with the internal table cache by dramatically reducing contention on the cache |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4068 | High | fixed a bug where Qorus did not start or work correctly when any datasource had the "coord-mode" option set; implemented qorus.disable-qdsp |
4067 | High | fixed a bug where qdsp processes were not updated when datasource options were updated with the API |
4066 | High | fixed a bug where Qorus would not start when the qorus.default-datasource-coordinated option was enabled |
4065 | Normal | fixed a bug where Qorus could throw a spurious exception when restarting stateless services under Kubernetes |
4064 | Normal | fixed a bug where Qorus could throw a spurious exception loading external users when serving connection APIs |
4063 | High | fixed a bug where Qorus would not start in a container environment where PID 1 could not be accessed |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4062 | High | fixed a bug where ping failures in monitored connections were not treated as failures |
4061 | High | fixed a race condition that could cause Qorus remote process starts to fail |
4059 | High | Fixed a bug where one or more qorus master process(es) would not restart after terminating or being killed and a deadlock resulted when the new active master could not reach the process |
4058 | High | Fixed a bug where a failed audit calls could cause a deadlock due to the system DB transaction status being silently lost |
4057 | Normal | Added missing audit codes to schema allowing all supported audit records to be saved |
4053 | Normal | Fixed a bug in oload where updating mapper code objects did not reset affected mapper(s) |
4047 | Normal | Fixed a bug loading value maps with descriptions with oload |
4046 | Normal | Fixed the trunc flag in mappers with DB table output fields |
4054 | High | Fixed a bug in oload where config item values migrated to new versions of objects were deleted after validation |
4041 | High | Fixed a rare deadlock that can occur under Kubernetes when an active master and qorus-core happen at the same time |
4040 | Normal | Fixed a bug where Qorus connections could not be edited with the UI without manually correcting the URL scheme to qorus or qoruss |
4038 | Normal | OAuth2 error redirects were issued with the wrong status causing an error in the UI when the OAuth2 auth code flow fails |
4036 | Normal | Fixed a bug where Qorus would ignore REST API calls to remove all roles from a user |
4035 | Normal | Fixed a bug handling abort messages for the system qdsp datasource process that could result in spurious error messages in the system log |
4033 | Normal | Fixed a race condition managing the workflow order cache that could cause spurious failures retrieving order information from REST APIs |
4032 | Normal | Fixed a type error in QorusClient::createRole() in the client library |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4032 | Normal | Fixed a bug where Qorus would not shut down properly if qorus-core could not be started due to schema version errors or similar issues |
4030 | High | Fixed a bug where Qorus was unable to start processes in remote master nodes |
4029 | High | Fixed a bug where HTTP connections with authorization from an OAuth2 client were processed as if they had no permissions |
4028 | High | Fixed a bug where HTTP connections with OAuth2 authorization did not work with users provided by external RBAC providers such as LDAP / AD |
4027 | High | The Authorization header was not respected by the Qorus HTTP server |
4025 | Normal | fixed a bug where the REST API would report non-existent permissions in requests |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
GitHub 81 | Normal | fixed a bug where the SLA event page in the UI did not scroll or support paging |
GitHub 80 | Normal | fixed a bug where the web UI rendered modal dialogs for service actions behind the service pane |
GitHub 77 | Normal | fixed a bug where the web UI did not show any descriptions for connection options |
GitHub 76 | Normal | fixed a bug where the web UI did not render narrow pages properly in several locations |
GitHub 68 | Normal | fixed a bug where the "More ..." control on service panes was inoperable |
4021 | High | fixed a bug where oload created yaml-based workflows without an autostart key with a default value of 1 |
4019 | Normal | fixed a bug where invalid connections were reported with an invalid url attribute in the REST API |
4018 | Normal | fixed a bug where the web UI would not recognize supported connection schemes until they were used at least once |
4017 | High | fixed a bug where a lost connection error with PostgreSQL DBs would sometimes not be handled as a cluster failover error |
4015 | Normal | fixed a bug in oload where the -P,–add-prefix option did not work |
4014 | High | fixed a bug where Qorus would not start under Kubernetes with in some cases due to an issue accessing the Kubernetes API server |
4013 | High | fixed a bug where the OAuth2 authentication grant flow failed unless the client provided the client secret when retrieving the token based on the granted code |
4012 | High | fixed a bug where updating an OAuth2 client with the REST API to remove all permissions would result in adding all available permissions to the client |
4011 | Normal | fixed a bug where alert events for connections did not contain the connectionid, so the UI could not update them |
Latest version: Qorus 6.0.27
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
4010 | Normal | fixed a bug in the REST API for message and event types in data providers where the information could not be used properly in the IDE or in the web UI |
4009 | Critical | fixed a bug where Qorus did not run on Kubernetes v1.26 or later |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
GitHub 57 | Normal | fixed a bug where the web UI did not work when served from an HTTP (as opposed to an HTTPS) listener |
GitHub 47 | Normal | fixed a bug in the web UI where new and updated connection info was missing or displayed incorrectly |
GitHub 44 | Normal | fixed a bug in the web UI where it was not possible to create, read, or update connection options with complex values |
4008 | Normal | fixed a bug where disabled connections were still monitored |
4006 | Normal | fixed a bug where the Qore connection scheme cache was not used consistently to provide connections and scheme information |
4004 | High | fixed a bug where it was not possible to use the Qore Datasource, DatasourcePool, or related classes from native Java reliably with jdbc connections |
4003 | Normal | fixed a bug where Qorus did not handle file paths in connection options correctly in some cases in the remote deployment API |
4002 | Normal | fixed a bug where CONNECTION_UP events were issued for disabled connections when connections were reloaded |
4000 | Normal | fixed a bug deploying connections with complex option values with the remote deployment API |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
3999 | Normal | fixed a bug handling imports of abstract methods from Qore classes into Java; implemented the qorus.compat-broken-varargs option to handle any issues with backwards-compatibility |
3998 | Normal | fixed a bug recovering Qorus application sessions when Prometheus or Grafana processes are enabled |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
3997 | High | fixed an error recovering Qorus application sessions introduced in the fix for issue #3993 |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
3994 | Normal | fixed an error starting workflows with language data |
3993 | Normal | fixed a deadlock in system shutdown when the system clock of the node where qorus-core is running is corrected to a future time after interfaces have been started |
3992 | Normal | fixed a deadlock in system shutdown related to an in-progress connection reset |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
3991 | Normal | fixed a delay in shutting down Qorus in Kubernetes after the qorus-core process stops |
3988 | Normal | fixed the REST API to return global config item values with the config item description |
3987 | Normal | fixed issues in the web UI displaying integer and floating-point values |
3986 | Normal | fixed bugs the web UI handling global config item values |
3985 | Normal | fixed bugs in REST APIs related to data provider event and message type handling |
3984 | Normal | fixed bugs parsing the qorus.node option |
3983 | Normal | suppressed node warnings in Docker images |
3982 | Normal | fixed retrieving data provider record types when search options are required |
3980 | High | fixed handling automatic variables in FSMs |
jdbc:user/pass@{url=sqlserver://hostname;integratedSecurity=false;encrypt=false;classpath=$OMQ_DIR/user/jar/mssql-jdbc-12.2.0.jre11.jar}
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
3981 | Normal | fixed a bug where Qorus would send invalid API responses with JDBC datasource errors in some cases |
This is a bugfix release; see below for more information
Issue ID | Severity | Description |
3979 | Normal | fixed bugs handling transaction block states in FSMs |
3978 | Normal | fixed bugs handling variable declarations and variable action states in FSMs |
3977 | Normal | fixed a bug where the REST DataProvider browse API was not showing message types as children |
3975 | High | fixed a bug where data provider factory options were ignored in FSM states |
3974 | High | fixed bugs in handling FSM send message states |
3973 | High | fixed bugs in UserApi::getTypeFromPath() parsing factory options with slashes |
3972 | High | fixed bugs in UserApi::getTypeFromPath() retrieving the types of events and messages from supported data providers |
Qorus 6.0 is a major release of Qorus focusing on improved integration into external applications, improved security, and a better user experience.
schema-tool -mmanually when upgrading to ensure that log rotation and schema archiving jobs are active. This step is not necessary for new installations.
/schema
with HTTP/S and the Qorus host and portqorus-archiver
job) and log rotation (the qorus-log-rotator
job) are automatically configured and enabledQORE_FILE_LOCATION_HANDLERS
environment variable needs to be set to "QorusResourceFileLocationHandler"
to use the resource://
scheme for service file resources in command-line programs such as qdp
ldap.bindn
and ldap.bindpassword
are supported; see LDAP Authentication and RBAC Integration for more inforesource://
locations for service file resources are now supported in client contexts as well as server contexts; see File Locations for more informationQorusEE
is defined in all Qorus interface contextsworkflow-params
option, which has been non-functional since Qorus 4.0, was removedauto-recover
option has been removed and will be ignored if present in the System Options File. Qorus will always try to recover the application DB session on start if the previous instance is not contactableIssue ID | Severity | Description |
3971 | High | fixed a bug setting the mapper input or output type when a subtype key is present in the data provider definition |
3970 | Normal | fixed recovering terminating dependent processes when qorus-core aborts while dependent processes are starting |
3969 | Normal | fixed running qbugreport with no qorus.node option set |
3968 | High | Fixed a bug where a job's active status was always overridden when loaded with oload even if it had been manually set by the API |
3961 | Normal | Fixed displaying long descriptions with oload list object options |
3955 | Normal | Improved Qorus's ability to handle situations with low available I/O descriptors |
3856 | Normal | Fixed a bug where DataProvider search APIs required hash arguments but only support GET requests, making them impossible to use with standards-conforming HTTP requests |