[
https://issues.apache.org/jira/browse/IGNITE-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186341#comment-17186341
]
Stanilovsky Evgeny commented on IGNITE-13383:
---------------------------------------------
1. My position - no need to defense from users buggy code on server side,
performance - possible i agree here, but without bench this still unclear.
2. All thin clients need to implement the same.
> Moreover, you introduce memory leak again on the server-side (current
> connection context has reference to the ses - I nullify it, thanks for point.
> and next started transaction will intersect old transactions by id - tests
> are green, i double check them.
> 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)
