8000 there is potential deadLock for lock order is different for StorageConnection.store and BinaryStorer$Default.storeAll · Issue #414 · eclipse-store/store · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
there is potential deadLock for lock order is different for StorageConnection.store and BinaryStorer$Default.storeAll #414
Open
@useryq8

Description

@useryq8

Environment Details

  • EclipseStore Version:1.2.0, 2.1.3 still has this bug
  • JDK version:OpenJDK Runtime Environment Zulu21.32+17-CA (build 21.0.2+13-LTS)
  • OS: os.arch=amd64
    os.name=Linux
    os.version=3.10.0-1160.105.1.el7.x86_64
  • Used frameworks: Spingboot 3.2.2

Describe the bug

We write ourself Map class to store object to eclipse. it is running multi-thread, but it block for deadlock,
I get the jstack ,it has dead-lock for org.eclipse.store.storage.types.StorageConnection.store and BinaryStorer$Default.storeAll has different lock order.

at org.eclipse.store.storage.types.StorageConnection.store(StorageConnection.java:401)
at org.eclipse.serializer.persistence.binary.types.BinaryStorer$Default.storeAll(BinaryStorer.java:460)

you can see the screenshot。 our code both use the BinaryStorer sotreAlll and the persister.storeAll method

To Reproduce

Step by step instructions to reproduce the problem.

Expected behavior

StorageConnection.store and BinaryStorer$Default.storeAll has the same lock order, then there is no deadlock happen

Screenshots

Image

Image

Additional context

I checked the eclipse-store and org.eclipse.serializer project 1.2.0 and 2.1.3, this bug exists in these two version

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

      0