Skip to content

Worker never gives up requeuing work items that are being rejected by the remote server #14644

@antoinemzs

Description

@antoinemzs

Description

OpenAEV might reject a STIX bundle based on certain criterias, such as the modified attribute, which is a permanent error and OAEV return HTTP 400 to signify this.

However, the OCTI worker will insist in requeuing the already rejected message, only to be rejected again.

if response.status_code != 200 and response.status_code != 202:
raise RequestException(response.status_code, response.text)
return "ack"
except (RequestException, Timeout):
self.logger.error(
"Error executing listen handling, a connection error or timeout occurred"
)
# Platform is under heavy load: wait for unlock & retry almost indefinitely.
sleep_jitter = round(random.uniform(10, 30), 2)
time.sleep(sleep_jitter)
return "requeue"

Environment

OCTI master branch

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Setup OCTIxOAEV interconnection (OAEV Coverage connector)
  2. Create a report in OCTI and add a Security Coverage (automated, connector)
  3. The scenario is created in OAEV and simulation might start
  4. Open the Enrichement menu (three dot menu next to the upper-right Update button)
  5. Trigger the connector a second time, which will resend the identical STIX bundle to OAEV

Expected Output

OAEV rejects the identical bundle (it's a guard in OAEV to not reprocess a Security Coverage base don the modified attribute, or md5 digest) and the worker acknowledges it, setting the work item as errored with reason.

Actual Output

Work item is permanently in the queue, and is also clogging the queue, preventing the normal course of operations in OCTI.
OAEV is constantly called with the rejected STIX bundle and keeps rejecting it.

2026-02-26T12:10:30.145+01:00 ERROR 2267235 --- [OpenAEV API] [0.0-8080-exec-6] io.openaev.api.stix_process.StixApi      : Parsing error while processing STIX bundle 
Error: The STIX package is obsolete because a newer version has already been computed.
Image

Metadata

Metadata

Labels

buguse for describing something not working as expectedopenaev integrationLinked to the integration with OpenAEVsolveduse to identify issue that has been solved (must be linked to the solving PR)

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions