You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2019/03/13 23:20:00 UTC

[jira] [Updated] (GEODE-6524) TestFunction.TEST_FUNCTION_ONSERVER_REEXECUTE_EXCEPTION will only work if executed repeatedly on the same server

     [ https://issues.apache.org/jira/browse/GEODE-6524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darrel Schneider updated GEODE-6524:
------------------------------------
    Priority: Minor  (was: Major)

> TestFunction.TEST_FUNCTION_ONSERVER_REEXECUTE_EXCEPTION will only work if executed repeatedly on the same server
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6524
>                 URL: https://issues.apache.org/jira/browse/GEODE-6524
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>            Reporter: Darrel Schneider
>            Priority: Minor
>
> TestFunction.TEST_FUNCTION_ONSERVER_REEXECUTE_EXCEPTION will only work if executed repeatedly on the same server.
> But the test that uses this function: org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException() has 3 servers in its pool that it uses to execute the function. The test would be fine if it had only one server in the pool. Currently it passes because our current pool implementation keeps returning the same connection when the retries happen. But if that retry logic was ever improved to not retry on the same connection then the test would fail. The function keeps some counts in statics but different servers will have their own copy of those static counters.
> I would suggest just rewriting this test to only have one server. That would prevent it from accidently doing the retries on other servers.
>  



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