Skip to content

No lock protection around client conn during reconnect #2335

@dmcgowan

Description

@dmcgowan

After #2149 the client conn can be updated, however services are created using this client conn with no lock protection. We should protect this with a lock and document that these client instances of the services should not be kept around in scope for an extended period of time, since the connection may die.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions