[ https://issues.apache.org/jira/browse/IGNITE-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186524#comment-17186524 ]
Stanilovsky Evgeny edited comment on IGNITE-13383 at 8/28/20, 1:11 PM: ----------------------------------------------------------------------- [~alex_pl] i recognize that transparent txId enumeration can`t be implemented such way, because of changing ClientListenerNioListener and as consequence - session, the only fix i want to store here is [1] possible race, what do you think ? [1] https://github.com/apache/ignite/pull/8184/files#diff-6f1053ded0ee927b46750b0260159bfcR154 was (Author: zstan): [~alex_pl] i recognize that transparent txId numeration can be implemented such way, because of changing ClientListenerNioListener and as consequence - session, the only fix i want to store here is [1] possible race, what do you think ? [1] https://github.com/apache/ignite/pull/8184/files#diff-6f1053ded0ee927b46750b0260159bfcR154 > Java thin client improvements: channel reconnect and redundant concurrency > structures replacement. > -------------------------------------------------------------------------------------------------- > > Key: IGNITE-13383 > URL: https://issues.apache.org/jira/browse/IGNITE-13383 > Project: Ignite > Issue Type: Improvement > Components: thin client > Affects Versions: 2.8.1 > Reporter: Stanilovsky Evgeny > Assignee: Stanilovsky Evgeny > Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > I found that {code:java}ConcurrentHashMap{code} and > {code:java}AtomicLong{code} are redundant in java thin client code, yes i fix > tests a bit but i can`t see any contradictions with thick client behavior > here. -- This message was sent by Atlassian Jira (v8.3.4#803005)