Skip to content

Transaction ID generation is incorrect #18

@negentropicdev

Description

@negentropicdev

At least looking in the TCP master code. A feedback node is used in a shared reentrant VI to track the incrementing ID which means the clone instances can swap amongst master instance calls and transaction IDs may swap between connection instances. If this needs to be shared there should be a proper sharing mechanism that is composed into the class. Feedback nodes in shared reentrant VIs is a no-no.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions