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

Dan Smith resolved GEODE-192.
-----------------------------
    Resolution: Fixed

> ClientServerTransactionCCEDUnitTest.testClientCommitFunction fails 
> intermittently
> ---------------------------------------------------------------------------------
>
>                 Key: GEODE-192
>                 URL: https://issues.apache.org/jira/browse/GEODE-192
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Darrel Schneider
>            Assignee: Dan Smith
>            Priority: Minor
>              Labels: CI
>         Attachments: 
> 0001-GEODE-192-Patch-to-cause-this-test-to-fail-every-tim.patch
>
>
> ClientServerTransactionCCEDUnitTest.testClientCommitFunction failed recently 
> on a private build. The only changes on that branch (feature/GEODE-185) had 
> to do with an expiration unit test and some minor expiration changes.
> This failure is intermittent even on that branch.
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest$99.call 
> in VM 2 running on Host watson.gemstone.com with 4 VMs
>       at dunit.VM.invoke(VM.java:359)
>       at dunit.VM.invoke(VM.java:303)
>       at dunit.VM.invoke(VM.java:271)
>       at 
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest.doFunctionWork(ClientServerTransactionDUnitTest.java:2709)
>       at 
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest.testClientCommitFunction(ClientServerTransactionDUnitTest.java:2680)
> Caused by: 
> com.gemstone.gemfire.cache.TransactionDataNodeHasDepartedException: Could not 
> connect to member:watson(12644)<v169>:44703
>       at 
> com.gemstone.gemfire.internal.cache.execute.TransactionFunctionService.onTransaction(TransactionFunctionService.java:82)
>       at 
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest$99.call(ClientServerTransactionDUnitTest.java:2756)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to