NoOp operations can fail with an ObjectDisposedException on MultiplexingConnection

Description

https://forums.couchbase.com/t/getasync-failures-due-to-cannot-access-a-disposed-object-sdk-3-0-1/26397/3

Executing op NoOp on 3.225.106.106:11210 with key and opaque 3876. dbug: Couchbase.Core.ClusterNode[0] Op failed: Couchbase.Core.IO.Operations.Noop System.ObjectDisposedException: Cannot access a disposed object. Object name: 'MultiplexingConnection'.

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

Jeffry Morris December 18, 2021 at 3:22 AM

Fixed by removing the log noise; the actual reason for the socket being closed it what should be investigated.

Matt Ingenthron July 9, 2021 at 8:27 PM

and I reviewed this and we believe it's just log noise, the actual op probably retries. Moving to 3.2.1 where we'll verify. If anyone has other info, by all means, please comment!

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Components

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created February 28, 2021 at 6:30 PM
Updated December 18, 2021 at 3:22 AM
Resolved December 18, 2021 at 3:16 AM
Instabug