Skip to content

Releases: JobService/job-service

v8.0.0

25 Oct 09:11
06b951f
Compare
Choose a tag to compare

Version Number

8.0.0-499

New Features

  • None.

Breaking Changes

  • 634058: CAF_WMP_ Environment variables and associated functionality has been removed.

Known Issues

  • None.

Release Artifacts

Maven
Read more

v7.2.0

26 Sep 14:52
2070f62
Compare
Choose a tag to compare

Version Number

7.2.0-490

New Features

  • US929026: Updated to run on Java 21.
  • US952036: Image is now built on Oracle Linux.
  • I948127: JVM arguments introduced for diagnosing OutOfMemoryError.

Known Issues

  • None

Release Artifacts

Maven
Read more

v7.1.0

17 Jun 10:59
a5c71a7
Compare
Choose a tag to compare

Version Number

7.1.0-426

Breaking Changes

  • US898110: Default queue type is set as quorum.
    • This change sets quorum as the default type of queues created by the jobservice. To maintain existing behavior the CAF_RABBITMQ_QUEUE_TYPE environment should be set to classic.

New Features

  • US915147: New liveness and readiness endpoints added to the Job Tracking Worker.

    • A new /health-check?name=all&type=ALIVE endpoint has been added on the default REST port (8080) to check if a worker is alive.
    • A new /health-check?name=all&type=READY endpoint has been added on the default REST port (8080) to check if a worker is ready.
    • See the Worker Framework Documentation
      for more details.
  • US914145: New liveness and readiness endpoints added to the Job Service.

    • A new /health-check?name=all&type=ALIVE endpoint has been added on the default REST port (8080) to return the result of the last
      liveness check.
    • A new /health-check?name=all&type=READY endpoint has been added on the default REST port (8080) to return the result of the last
      readiness check.
    • The liveness and readiness checks are run on a schedule, which can be configured by the environment variables described in the
      README.md.
  • US914157: New ports-alive and ports-ready liveness and readiness checks added to the Job Service.

    • ports-alive checks that the server's ports (application and admin) are started and open
    • ports-ready checks that the server's ports (application and admin) are accepting connections

Bug Fixes

  • US893094: Prevent creation of a job if any of its prerequisite jobs have failed.
  • I898110: Remove worker-message-prioritization dependencies.
  • I915151: Resolve a memory exhaustion issue in the service

Known Issues

  • None

Release Artifacts

Maven
Read more

v7.0.2

03 May 00:29
7ed6718
Compare
Choose a tag to compare

Version Number

7.0.2-1

New Features

  • None

Bug Fixes

  • I915151: Resolve a memory exhaustion issue in the service

Known Issues

  • None

Release Artifacts

Maven
Read more

v7.0.1

10 Apr 07:42
a064138
Compare
Choose a tag to compare

Version Number

7.0.1-381

Patch Fixes Included

  • This release includes dependency updates only.

New Features

  • None

Known Issues

  • None

Release Artifacts

Maven
Read more

v7.0.0

12 Feb 15:22
2f748a6
Compare
Choose a tag to compare

Version Number

7.0.0-334

New Features

  • US771133: Support bulk cancellation of multiple jobs through new API endpoint /partitions/{partitionId}/jobs:cancel.
  • US868107: Support bulk deletion of multiple jobs through new API endpoint /partitions/{partitionId}/jobs:delete.

Breaking Changes

  • US361030: SSL configuration environment variables changed
    The SSL_TOMCAT_* environment variables are no longer respected.
    The following environment variables are now used to configure SSL:

    • SSL_KEYSTORE_PATH
    • SSL_KEYSTORE
    • SSL_KEYSTORE_TYPE (Optional, defaults to JKS)
    • SSL_KEYSTORE_PASSWORD
    • SSL_CERT_ALIAS
    • SSL_VALIDATE_CERTS (Optional, defaults to false)
  • US361030: Dropped CORS headers
    The Access-Control-Allow-* headers are no longer returned by the Job Service.

  • D854021: Worker Framework V4 Format message support dropped
    The Job Tracking Worker has been updated to use a new version of the worker framework which no longer supports the V4 format message.


    The Job Service Scheduled Executor no longer respects the JOB_SERVICE_MESSAGE_OUTPUT_FORMAT environment variable. The V3 format message is always output regardless of the setting.

Known Issues

  • None.

Release Artifacts

Maven
Read more

v6.2.2

24 Nov 12:16
2f748a6
Compare
Choose a tag to compare

Version Number

6.2.2-266

New Features

  • None

Patch Fixes Included

  • This release includes OS package updates only.

Known Issues

  • None

Release Artifacts

Maven
Read more

v6.2.1

24 Aug 14:33
e4a9263
Compare
Choose a tag to compare

Version Number

6.2.1-176

New Features

  • None

Patch Fixes Included

  • This release includes OS package updates only.

Known Issues

  • None

Release Artifacts

Maven
Read more

v6.2.0

26 Apr 12:47
5ee28d5
Compare
Choose a tag to compare

Version Number

6.2.0-136

New Features

  • 627110: The Job Service Scheduled Executor now supports message prioritization, allowing it to reroute messages to staging queues.

It can be configured via the following environment variables:

CAF_WMP_ENABLED
description: Determines whether the Job Service Scheduled Executor should reroute a message to a worker's staging queue or not. If true, a message will attempt to be rerouted. If false, a message will not be rerouted and will be sent to the target queue rather than to a staging queue.
default: false

CAF_WMP_PARTITION_ID_PATTERN
description: Only applies when CAF_WMP_ENABLED is true. Used to specify the partition ID pattern. This pattern is used by the Job Service Scheduled Executor to extract the tenant ID from the partition ID. The tenant ID is then used to construct the staging queue name. The pattern must contain a named capturing group called tenantId, which is what is used to extract the tenant ID.
default: None
example: If the pattern is ^tenant-(?<tenantId>.+)# and the partition ID is tenant-acmecorp, the tenant ID extracted from this partition ID will be acmecorp.

CAF_WMP_TARGET_QUEUE_NAMES_PATTERN
description: Only applies when CAF_WMP_ENABLED is true. Used to specify the target queue names pattern. This pattern is used by the Job Service Scheduled Executor to check whether it should reroute a message to a staging queue or not. Only messages destined for target queues that match this pattern will be rerouted to staging queues.
default: None

  • US632159: The Job Service Scheduled Executor's healthcheck will now check the status of the Rabbit MQ Management API whenever the CAF_WMP_ENABLED environment variable is true.

  • D632168: Updated to use Tomcat version 9.0.73 This includes fixes for CVE-2023-24998.\n\n- US353672: Ping operation added to the Job Service's REST interface

Known Issues

  • None

Release Artifacts

Maven
Read more

v6.1.0

20 Dec 14:10
Compare
Choose a tag to compare

Version Number

6.1.0-72

New Features

  • US593021: Updated to run on Java 17.

Patch Fixes Included

  • US572082: Gson version upgraded to 2.9.1
  • US572083: Snakeyaml version upgraded to 1.32

Known Issues

  • None

Release Artifacts

Maven
Read more