[ 
https://issues.apache.org/jira/browse/GEODE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539293#comment-16539293
 ] 

ASF subversion and git services commented on GEODE-5379:
--------------------------------------------------------

Commit d7a698851e369e12cfeb0065a1bb938eccc8f7ae in geode's branch 
refs/heads/feature/GEODE-5379 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d7a6988 ]

GEODE-5379: reset affinityRetryCount to zero only when initial retry count is 
zero


> affinityRetryCount should not be reseted after executeOnServer successfully 
> ----------------------------------------------------------------------------
>
>                 Key: GEODE-5379
>                 URL: https://issues.apache.org/jira/browse/GEODE-5379
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently affinityRetryCount is reseted after executeOnServer successfully in 
> executeWithServerAffinity. This is wrong, as TXFailoverOp executed after 
> server connection failure can succeed and reset the affinityRetryCount. This 
> could leads to StackOverflowError.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to