Skip to content

[Bug] Heap Dump failure due to long operation execution time #1131

@andrewazores

Description

@andrewazores

Current Behavior

See #1130

targetConnectionManager.executeConnectedTask(

public <T> T executeConnectedTask(Target target, ConnectedTask<T> task) {

The heap dump operation calls into the TargetConnectionManager using the default "failed connection" timeout duration, which is 30 seconds. This is not enough time for realistic heap dumps to be taken, since dumping the heap itself within the target JVM will take some time, and then the dumped file needs to be sent over the network to Cryostat and from there piped into storage. Completing all of these slow tasks within 30 seconds is unlikely in a real scenario.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions