Skip to content

unused-umwl gets EOF on API call after around 2500 umwls processed #128

@tobinbxnz-spec

Description

@tobinbxnz-spec

For a large set of UMWLs the unused-umwl function of workloader will fail with an EOF while doing a GET API call

This can happen anywhere from 5 hours to 10 hours into a set of processing, usually between 2100 and 2600 UMWLs processed.

Normal sequence for the API calls is PUT / GET / GET / GET with download

The failure happens after the first GET which completes successfully. The second GET does not reach the PCE.

This happens with either direct calls to the PCE or when there is Zscaler in the middle.

One possibility is the connection pool either exhausting or attempting to reuse a now closed connection.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions