Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IMap's lock operations use constant thread id [API-1225] #696

Open
puzpuzpuz opened this issue Nov 30, 2020 · 1 comment
Open

IMap's lock operations use constant thread id [API-1225] #696

puzpuzpuz opened this issue Nov 30, 2020 · 1 comment
Labels
to-jira Type: Enhancement

Comments

@puzpuzpuz
Copy link
Contributor

puzpuzpuz commented Nov 30, 2020 •
edited
Loading

All IMap's lock operations use a hard-coded thread id. We describe this behavior in the ref manual, but it may lead to user confusion as server-side assumes lock reentrancy.

Corresponding TDD: https://hazelcast.atlassian.net/wiki/spaces/PM/pages/3032121505/Node.js+Client+IMap+Lock+Ownership+Contexts+-+TDD
@puzpuzpuz puzpuzpuz added this to the 4.1 milestone Nov 30, 2020
@puzpuzpuz puzpuzpuz modified the milestones: 4.1, Backlog Dec 24, 2020
@yuce yuce added the to-jira label Feb 18, 2022
@github-actions github-actions bot changed the title IMap's lock operations use constant thread id IMap's lock operations use constant thread id [API-1225] Feb 18, 2022
@github-actions
Copy link

Internal Jira issue: API-1225

@degerhz degerhz modified the milestones: Backlog, 5.2.0 May 16, 2022
@harunalpak harunalpak modified the milestones: 5.2.0, 5.3.0 Dec 14, 2022
@degerhz degerhz removed this from the 5.3.0 milestone Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
to-jira Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@yuce @degerhz @harunalpak @srknzl @puzpuzpuz