[jira] [Updated] (GEODE-95) PartitionedRegionSingleHopDUnitTest.test_MetadataContents fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-95:
---
Fix Version/s: 1.0.0-alpha1
> PartitionedRegionSingleHopDUnitTest.test_MetadataContents fails intermittently
> --
>
> Key: GEODE-95
> URL: https://issues.apache.org/jira/browse/GEODE-95
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Dan Smith
>Assignee: Kishor Bachhav
> Fix For: 1.0.0-alpha1
>
>
> This test appears to have a race condition. It failed on of the nightly
> builds:
> https://builds.apache.org/view/All/job/Geode-nightly/lastBuild/testReport/junit/com.gemstone.gemfire.internal.cache/PartitionedRegionSingleHopDUnitTest/test_MetadataContents/
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest.verifyMetadata(PartitionedRegionSingleHopDUnitTest.java:2221)
> at
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest.test_MetadataContents(PartitionedRegionSingleHopDUnitTest.java:386)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-418) CI failure: AutoConnectionSourceWithUDPDUnitTest.testEmbeddedLocator
[ https://issues.apache.org/jira/browse/GEODE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-418: Fix Version/s: 1.0.0-alpha1 > CI failure: AutoConnectionSourceWithUDPDUnitTest.testEmbeddedLocator > > > Key: GEODE-418 > URL: https://issues.apache.org/jira/browse/GEODE-418 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Assignee: Sai Boorlagadda > Labels: CI > Fix For: 1.0.0-alpha1 > > > Failed 1 times in the last 30 runs. Stability: 96 % > Error Message > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 646 > com.gemstone.gemfire.cache.client.ServerConnectivityException: Pool > unexpected Connection reset connection=Pooled Connection to > cc8-rh64.gemstone.com:22199: Connection[DESTROYED]). Server unreachable: > could not connect after 1 attempts > Stacktrace > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 646 > com.gemstone.gemfire.cache.client.ServerConnectivityException: Pool > unexpected Connection reset connection=Pooled Connection to > cc8-rh64.gemstone.com:22199: Connection[DESTROYED]). Server unreachable: > could not connect after 1 attempts > at org.junit.Assert.fail(Assert.java:88) > at > dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307) > at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784) > at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759) > at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737) > at junit.framework.TestCase.runBare(TestCase.java:146) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at > org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64) > at >
[jira] [Updated] (GEODE-435) CI failure: ClientServerTransactionDUnitTest.testClientCommitFunction
[
https://issues.apache.org/jira/browse/GEODE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-435:
Fix Version/s: 1.0.0-alpha1
> CI failure: ClientServerTransactionDUnitTest.testClientCommitFunction
> -
>
> Key: GEODE-435
> URL: https://issues.apache.org/jira/browse/GEODE-435
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest$99.call
> in VM 2 running on Host cc1-rh6.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:360)
> at dunit.VM.invoke(VM.java:303)
> at dunit.VM.invoke(VM.java:271)
> at
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest.doFunctionWork(ClientServerTransactionDUnitTest.java:2678)
> at
> com.gemstone.gemfire.internal.cache.ClientServerTransactionDUnitTest.testClientCommitFunction(ClientServerTransactionDUnitTest.java:2649)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by:
> com.gemstone.gemfire.cache.TransactionDataNodeHasDepartedException: Could not
> connect to member:cc1-rh6(5725):21949
> at
> com.gemstone.gemfire.internal.cache.execute.TransactionFunctionService.onTransaction(TransactionFunctionService.java:82)
> at
>
[jira] [Updated] (GEODE-626) MemoryChunk methods getSize and copyBytes need unit test coverage
[ https://issues.apache.org/jira/browse/GEODE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-626: Fix Version/s: 1.0.0-alpha1 > MemoryChunk methods getSize and copyBytes need unit test coverage > - > > Key: GEODE-626 > URL: https://issues.apache.org/jira/browse/GEODE-626 > Project: Geode > Issue Type: Sub-task > Components: offheap >Reporter: Darrel Schneider >Assignee: Darrel Schneider > Fix For: 1.0.0-alpha1 > > > The MemoryChunk methods getSize and copyBytes have no unit test coverage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-375) A lot of suspect string in HAStartupAndFailoverDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-375: Fix Version/s: 1.0.0-alpha1 > A lot of suspect string in HAStartupAndFailoverDUnitTest > > > Key: GEODE-375 > URL: https://issues.apache.org/jira/browse/GEODE-375 > Project: Geode > Issue Type: Bug > Components: client/server > Environment: develop >Reporter: xiaojian zhou >Assignee: Sai Boorlagadda >Priority: Critical > Labels: CI > Fix For: 1.0.0-alpha1 > > > Run the dunit test: HAStartupAndFailoverDUnitTest, it failed with following > suspicous strings: > :gemfire-core:distributedTest > com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest > > > testCacheClientUpdaterInitiatesFailoverOnBothPrimaryAndSecondaryFailureWithServerMonitors > FAILED > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 3862 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3901 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3929 > java.net.ConnectException: Connection refused: connect > com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest > > testExceptionWhileMakingPrimary FAILED > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 3051 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3117 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3183 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3211 > java.net.ConnectException: Connection refused: connect > com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest > > testCacheClientUpdatersInitiatesFailoverOnPrimaryFailure FAILED > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 3101 > java.net.ConnectException: Connection refused: connect > com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest > > testPrimaryShouldBeNullAndEPListShouldBeEmptyWhenAllServersAreDead FAILED > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 3109 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3135 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3165 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3194 > java.net.ConnectException: Connection refused: connect > --- > Found suspect string in log4j at line 3220 > java.net.ConnectException: Connection refused: connect > com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest > > testTwoPrimaryFailedOneAfterTheAnother FAILED > java.lang.AssertionError: Suspicious strings were written to the log > during this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. >
[jira] [Updated] (GEODE-588) CI Failure: LocatorDUnitTest.testMultipleMcastLocators
[
https://issues.apache.org/jira/browse/GEODE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-588:
Fix Version/s: 1.0.0-alpha1
> CI Failure: LocatorDUnitTest.testMultipleMcastLocators
> --
>
> Key: GEODE-588
> URL: https://issues.apache.org/jira/browse/GEODE-588
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> After the GEODE-77 merge, we're seeing this test fail fairly frequently.
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 2999
> [fatal 2015/11/23 00:13:57.477 PST
> tid=0x12] Could not stop Distribution Locator on cc2-rh6[23827] in 60
> seconds
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:330)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:751)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:726)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:704)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-397) When the server-ssl-* properties are configured, the client subscription socket can fail to be created
[
https://issues.apache.org/jira/browse/GEODE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-397:
Fix Version/s: 1.0.0-alpha1
> When the server-ssl-* properties are configured, the client subscription
> socket can fail to be created
> --
>
> Key: GEODE-397
> URL: https://issues.apache.org/jira/browse/GEODE-397
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
> Fix For: 1.0.0-alpha1
>
>
> The {{{CacheClientUpdater}}} (which creates the client subscription socket)
> uses the default {{{SocketCreator}}} which is configured based on the
> {{{cluster-ssl-*}}} properties.
> If the {{{cluster-ssl-*}}} properties are configured in the client security
> properties, the client subscription socket is created correctly. If, instead,
> the {{{server-ssl-*}}} properties are configured, then the
> {{{CacheClientUpdater}}} will attempt to create the socket with value of
> {{{cluster-ssl-enabled}}} (which will be false) instead of
> {{{server-ssl-enabled}}} (which will be true) and fail.
> The messages logged in the client log are:
> {{{
> [warning 2015/10/05 18:41:46.487 PDT tid=0x1] Cache Client Updater
> Thread on boglesbymac(server1:85312):13499 port 49848
> (192.168.2.12:49848): Security exception when creating server-to-client
> communication socket.
> com.gemstone.gemfire.security.AuthenticationRequiredException: Server
> expecting SSL connection
> [error 2015/10/05 18:41:46.491 PDT tid=0x1] Could not find any server
> to create primary client queue on. Number of excluded servers is 1 and
> exception is no exception.
> [error 2015/10/05 18:41:46.491 PDT tid=0x1] Could not initialize a
> primary queue on startup. No queue servers available.
> }}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-279) Hang may be caused by repeatedly creating and destroying a Partiitioned Region
[ https://issues.apache.org/jira/browse/GEODE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-279: Fix Version/s: 1.0.0-alpha1 > Hang may be caused by repeatedly creating and destroying a Partiitioned Region > -- > > Key: GEODE-279 > URL: https://issues.apache.org/jira/browse/GEODE-279 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Minor > Fix For: 1.0.0-alpha1 > > Original Estimate: 3h > Remaining Estimate: 3h > > If a partitioned region is concurrently created and destroyed while > operations on it are in progress it may result in a hang. The hang will log > this severe message: [severe ...] While pulling a message > com.gemstone.gemfire.cache.RegionDestroyedException: Region ... is destroyed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-43) Integer overflow in PartitionedRegionLoadModel
[
https://issues.apache.org/jira/browse/GEODE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-43:
---
Fix Version/s: 1.0.0-alpha1
> Integer overflow in PartitionedRegionLoadModel
> --
>
> Key: GEODE-43
> URL: https://issues.apache.org/jira/browse/GEODE-43
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.0.0-incubating
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-alpha1
>
>
> PartitionRegionLoadModel.getAverageLoad() is casting a float to an integer
> and potentially overflowing. totalLoad here is size of a region in bytes,
> this code easily be bigger than Integer.MaxValue.
> {code}
> private float getAverageLoad() {
> if(this.averageLoad == -1) {
> float totalWeight = 0;
> int totalLoad = 0;
> for(Member member : this.members.values()) {
> totalLoad += member.getTotalLoad();
> totalWeight += member.getWeight();
> }
>
> this.averageLoad = totalLoad / totalWeight;
> }
>
> return this.averageLoad;
> }
> {code}
> member.getTotalLoad() returns a float.
> Interestingly, if this expression is written as below, the compiler will
> complain:
> {code}
> totalLoad = totalLoad + member.getTotalLoad()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-708) Need the stats for Geode membership health monitor
[ https://issues.apache.org/jira/browse/GEODE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-708: Fix Version/s: 1.0.0-alpha1 > Need the stats for Geode membership health monitor > -- > > Key: GEODE-708 > URL: https://issues.apache.org/jira/browse/GEODE-708 > Project: Geode > Issue Type: Task >Reporter: Jianxia Chen >Assignee: Jianxia Chen > Fix For: 1.0.0-alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-570) Fix generation of javadocs from build script
[
https://issues.apache.org/jira/browse/GEODE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-570:
Fix Version/s: 1.0.0-alpha1
> Fix generation of javadocs from build script
>
>
> Key: GEODE-570
> URL: https://issues.apache.org/jira/browse/GEODE-570
> Project: Geode
> Issue Type: Sub-task
> Components: build
>Reporter: Nitin Lamba
>Assignee: Nitin Lamba
> Fix For: 1.0.0-alpha1
>
> Attachments: GEODE-570.diff
>
>
> Currently, the build errors out when javadoc is run:
> {code}
> ./gradlew javadoc
> {code}
> With stricter checks in JDK 8, the error-checking need to be ignored
> initially.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-244) CI failure: RebalanceOperationDUnitTest testRecoverRedundancyParallelAsyncEventQueueSimulation failed an assertion
[
https://issues.apache.org/jira/browse/GEODE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-244:
Fix Version/s: 1.0.0-alpha1
> CI failure: RebalanceOperationDUnitTest
> testRecoverRedundancyParallelAsyncEventQueueSimulation failed an assertion
> --
>
> Key: GEODE-244
> URL: https://issues.apache.org/jira/browse/GEODE-244
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> RebalanceOperationDUnitTest
> testRecoverRedundancyParallelAsyncEventQueueSimulation failed an assertion in
> nightly build #190:
> {color:red}
> {noformat}
> com.gemstone.gemfire.internal.cache.control.RebalanceOperationDUnitTest >
> testRecoverRedundancyParallelAsyncEventQueueSimulation FAILED
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.control.RebalanceOperationDUnitTest$43.run
> in VM 0 running on Host jenkins-ubuntu-1404-4gb-f59 with 4 VMs
> at dunit.VM.invoke(VM.java:359)
> at dunit.VM.invoke(VM.java:303)
> at dunit.VM.invoke(VM.java:257)
> at
> com.gemstone.gemfire.internal.cache.control.RebalanceOperationDUnitTest.recoverRedundancyParallelAsyncEventQueue(RebalanceOperationDUnitTest.java:1148)
> at
> com.gemstone.gemfire.internal.cache.control.RebalanceOperationDUnitTest.testRecoverRedundancyParallelAsyncEventQueueSimulation(RebalanceOperationDUnitTest.java:1090)
> Caused by:
> junit.framework.AssertionFailedError: expected:<6> but was:<4>
> {noformat}
> {color}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-434) CI failure: Bug36995DUnitTest.testBug36526
[
https://issues.apache.org/jira/browse/GEODE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-434:
Fix Version/s: 1.0.0-alpha1
> CI failure: Bug36995DUnitTest.testBug36526
> --
>
> Key: GEODE-434
> URL: https://issues.apache.org/jira/browse/GEODE-434
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Sai Boorlagadda
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> See also GEODE-433
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 2934
> [warn 2015/10/17 18:51:39.980 PDT
> tid=0x1246] Server connection from
> [identity(zambia(25218:loner):34399:9723a578,connection=1; port=60915]:
> Unexpected IOException:
> ---
> Found suspect string in log4j at line 2935
> java.net.SocketException: Connection reset
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Previously run tests: [Bug40396DUnitTest, DestroyEntryPropagationDUnitTest,
> Bug36269DUnitTest, DurableRegistrationDUnitTest,
> RedundancyLevelPart2DUnitTest, ConflationDUnitTest,
> EventIDVerificationInP2PDUnitTest, ForceInvalidateOffHeapEvictionDUnitTest,
> DurableClientBug39997DUnitTest,
>
[jira] [Updated] (GEODE-709) CI failure: AnalyzeSerializablesJUnitTest error parsing class file
[ https://issues.apache.org/jira/browse/GEODE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-709: Fix Version/s: 1.0.0-alpha1 > CI failure: AnalyzeSerializablesJUnitTest error parsing class file > -- > > Key: GEODE-709 > URL: https://issues.apache.org/jira/browse/GEODE-709 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Assignee: Darrel Schneider > Labels: CI > Fix For: 1.0.0-alpha1 > > > The test failed in build 1081: > java.lang.Error: Unknown tag type in constant pool: 18 > at com.gemstone.gemfire.codeAnalysis.decode.cp.Cp.readCp(Cp.java:65) > at > com.gemstone.gemfire.codeAnalysis.decode.CompiledClass.(CompiledClass.java:101) > at > com.gemstone.gemfire.codeAnalysis.decode.CompiledClass.getInstance(CompiledClass.java:81) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:108) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.CompiledClassUtils.parseClassFilesInDir(CompiledClassUtils.java:104) > at > com.gemstone.gemfire.codeAnalysis.AnalyzeSerializablesJUnitTest.loadClassesFromBuild(AnalyzeSerializablesJUnitTest.java:257) > at > com.gemstone.gemfire.codeAnalysis.AnalyzeSerializablesJUnitTest.loadClasses(AnalyzeSerializablesJUnitTest.java:95) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-7) Off heap data storage
[ https://issues.apache.org/jira/browse/GEODE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-7: -- Fix Version/s: 1.0.0-alpha1 > Off heap data storage > - > > Key: GEODE-7 > URL: https://issues.apache.org/jira/browse/GEODE-7 > Project: Geode > Issue Type: Sub-task > Components: core >Reporter: Dan Smith >Assignee: Darrel Schneider > Labels: asf-migration > Fix For: 1.0.0-alpha1 > > Attachments: GemFire Off-Heap Functional Specification - 7th draft - > 05_11_2015.pdf > > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Geode stores a lot of data in the java heap. With very large heap sizes, this > can lead to performance impacts due to garbage collection time. > Rather than storing data in the java heap, store data in native memory > managed by Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-524) Misspelled method name: 'beforeEnque()' should be 'beforeEnqueue()'
[ https://issues.apache.org/jira/browse/GEODE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-524: Fix Version/s: 1.0.0-alpha1 > Misspelled method name: 'beforeEnque()' should be 'beforeEnqueue()' > --- > > Key: GEODE-524 > URL: https://issues.apache.org/jira/browse/GEODE-524 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Dave Barnes >Assignee: Ashvin > Fix For: 1.0.0-alpha1 > > > The method 'beforeEnqueue()' (correct spelling) appears in several places in > code related to Gateway Events. Unfortunately, so does 'beforeEnque()' > (incorrect spelling). To avoid confusion, occurrences of the > incorrectly-spelled method should be fixed in the Geode code base. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-216) Failure to process GetMessage due RegionDestroyedException
[
https://issues.apache.org/jira/browse/GEODE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-216:
Fix Version/s: 1.0.0-alpha1
> Failure to process GetMessage due RegionDestroyedException
> --
>
> Key: GEODE-216
> URL: https://issues.apache.org/jira/browse/GEODE-216
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Dan Smith
>Assignee: Darrel Schneider
> Fix For: 1.0.0-alpha1
>
>
> This failure showed up in a nightly build, the test
> RedisDistDUnitTest.testConcCreateDestroy timed out on a read.
> But to me it looks like the underlying issue is some missing exception
> handling code in GetMessage that caused a hang due to a
> RegionDestroyedException.
> https://builds.apache.org/job/Geode-nightly/183/testReport/junit/com.gemstone.gemfire.redis/RedisDistDUnitTest/testConcCreateDestroy/
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.redis.RedisDistDUnitTest$1ConcCreateDestroy.call in VM 3
> running on Host jenkins-ubuntu-1404-4gb-f9a 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.redis.RedisDistDUnitTest.testConcCreateDestroy(RedisDistDUnitTest.java:168)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: redis.clients.jedis.exceptions.JedisConnectionException:
> java.net.SocketTimeoutException: Read timed out
> at
>
[jira] [Updated] (GEODE-295) Failure from BridgeMembershipDUnitTest.testBridgeMembershipEventsInClient
[
https://issues.apache.org/jira/browse/GEODE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-295:
Fix Version/s: 1.0.0-alpha1
> Failure from BridgeMembershipDUnitTest.testBridgeMembershipEventsInClient
> -
>
> Key: GEODE-295
> URL: https://issues.apache.org/jira/browse/GEODE-295
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> This test failed in a nightly build. Looks to me like maybe it just needs to
> expect a suspect string?
> https://builds.apache.org/job/Geode-nightly/196/testReport/junit/com.gemstone.gemfire.cache30/BridgeMembershipDUnitTest/testBridgeMembershipEventsInClient/
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 1104
> java.io.IOException: Socket input is shutdown
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:764)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:739)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:717)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor212.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-105) Null value in Map causes NPE with Map Indexes
[ https://issues.apache.org/jira/browse/GEODE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-105: Fix Version/s: 1.0.0-alpha1 > Null value in Map causes NPE with Map Indexes > - > > Key: GEODE-105 > URL: https://issues.apache.org/jira/browse/GEODE-105 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > Fix For: 1.0.0-alpha1 > > > When a value of null is added into a map that is being indexed on, a NPE will > be thrown. This should not happen and instead should be handled correcty > with the NULL token. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-621) CI Failure: AnalyzeSerializablesJUnitTest.testDataSerializables
[ https://issues.apache.org/jira/browse/GEODE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-621: Fix Version/s: 1.0.0-alpha1 > CI Failure: AnalyzeSerializablesJUnitTest.testDataSerializables > --- > > Key: GEODE-621 > URL: https://issues.apache.org/jira/browse/GEODE-621 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Jason Huynh > Labels: CI > Fix For: 1.0.0-alpha1 > > > java.lang.AssertionError: Modified > classes > com/gemstone/gemfire/distributed/internal/StartupMessage,3 > fromDataProblem,38,2ab40039c7000e2abb006b59b7006cb500392ab400392bb6006d572ab40039126eb6006d57b1 > fromData,325,2a2bb7006f2bb80070b2004eb6004f9c000704a70004033d1c9900082bb80071572a2bb80072b500092a2bb900730100b5000c2a2bb900740100b5000d2a2bb900740100b500112bb9007301003e03360415041da2003e2bb800753a052bb90073010036061905c6000d19050301011506b80076a700183a072ab2007704bd00225903190753b60026b70078840401a7ffc22bb900730100360403360515051504a200492bb800753a062bb800753a072bb90073010036081906c600121907c6000d19061907150803b80079a700183a092ab2007a04bd00225903190953b60026b70078840501a7ffb62a2bb80071c0007bb500122a2bb900730100b500172a2bb80072b500182a2bb900740100b50019bb006459b700653a0519052bb6007c2a1905b6007db5000a2a1905b6007eb5000b2a1905b6007fb5000e2a1905b60080b5000fb1 > toData,366,2a2bb7004c2bb8004db2004eb6004f9c000704a70004033d1c99000ebb005059b700512bb800522ab400092bb800532b2ab4000cb9005402002b2ab4000db9005502002b2ab40011b900550200b800564e2b2dbeb90054020003360415042dbea200212d150432b600572bb800582b2d150432b60059b900540200840401a7ffdeb8005a3a042b1904beb90054020003360515051904bea2007f1904150532c1005b9900331904150532c0005bb6005cb6005d3a061904150532c0005bb6005eb6005d3a071904150532c0005bb6005f3608a7002a1904150532c00060b600613a061904150532c00060b600623a071904150532c00060b60063360819062bb8005819072bb800582b1508b900540200840501a7ff7f2ab400122bb800522b2ab40017b9005402002ab400182bb800532b2ab40019b900550200bb006459b700653a0519052ab4000ab6006619052ab4000bb6006719052ab4000eb6006819052ab4000fb6006919052bb6006ab1 > : toData (len=366,expected=399), and fromData (len=325,expected=354) > If the class is not persisted or sent over the wire add it to the > excludedClasses.txt file in the > com/gemstone/gemfire/codeAnalysis directory. Otherwise if this doesn't > break backward compatibility move the file actualDataSerializables.dat to the > codeAnalysis > test directory and rename to sanctionedDataSerializables.txt > at org.junit.Assert.fail(Assert.java:88) > at > com.gemstone.gemfire.codeAnalysis.AnalyzeSerializablesJUnitTest.testDataSerializables(AnalyzeSerializablesJUnitTest.java:193) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-186) ClientServerTransactionDUnitTest.testSuspendTimeout takes too long to run
[ https://issues.apache.org/jira/browse/GEODE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-186: Fix Version/s: 1.0.0-alpha1 > ClientServerTransactionDUnitTest.testSuspendTimeout takes too long to run > - > > Key: GEODE-186 > URL: https://issues.apache.org/jira/browse/GEODE-186 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Minor > Fix For: 1.0.0-alpha1 > > > ClientServerTransactionDUnitTest.testSuspendTimeout takes too long to run. It > takes 70 seconds. It has a 70 second sleep. It is waiting for a suspended tx > to expire. It should use a test hook to change the expiration units from > minutes to millis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-208) Developers can run unit tests
[ https://issues.apache.org/jira/browse/GEODE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-208: Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Developers can run unit tests > - > > Key: GEODE-208 > URL: https://issues.apache.org/jira/browse/GEODE-208 > Project: Geode > Issue Type: Sub-task >Reporter: Bruce Schuchardt > Fix For: 1.0.0-alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-207) Services and MemberFactory are available to the GMS components
[ https://issues.apache.org/jira/browse/GEODE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-207: Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Services and MemberFactory are available to the GMS components > -- > > Key: GEODE-207 > URL: https://issues.apache.org/jira/browse/GEODE-207 > Project: Geode > Issue Type: Sub-task >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.0.0-alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-209) FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is not stable
[
https://issues.apache.org/jira/browse/GEODE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-209:
Affects Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
> is not stable
> --
>
> Key: GEODE-209
> URL: https://issues.apache.org/jira/browse/GEODE-209
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-alpha1
>Reporter: Ashvin
>Assignee: Kirk Lund
>Priority: Minor
> Fix For: 1.0.0-alpha1
>
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
> failed 5 times in the last 30 runs. It is failing in the tearDown phase.
> {quote}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
> at
> com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {quote}
> {code}
> public void subTearDown() throws Exception {
> this.process.waitFor();
> assertFalse(this.process.isAlive());
> }
> {code}
> Fix to GEODE-127 may have caused this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-232) gfsh prints ERROR StatusLogger log4j2-cli.xml not found in file system or classpath
[ https://issues.apache.org/jira/browse/GEODE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-232: Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > gfsh prints ERROR StatusLogger log4j2-cli.xml not found in file system or > classpath > --- > > Key: GEODE-232 > URL: https://issues.apache.org/jira/browse/GEODE-232 > Project: Geode > Issue Type: Bug >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Critical > Labels: gfsh > Fix For: 1.0.0-alpha1 > > > ./open/gemfire-assembly/build/install/apache-geode/bin/gfsh > ERROR StatusLogger File not found in file system or classpath: > /com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml > ERROR StatusLogger No log4j2 configuration file found. Using default > configuration: logging only errors to the console. > _ __ >/ _/ __/ __/ // / > / / __/ /___ /_ / _ / > / /__/ / / _/ / // / > /__/_/ /__/_//_/v1.0.0-incubating-SNAPSHOT > Monitor and Manage GemFire > gfsh> -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-264) Fix varargs compiler warnings
[
https://issues.apache.org/jira/browse/GEODE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-264:
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> Fix varargs compiler warnings
> -
>
> Key: GEODE-264
> URL: https://issues.apache.org/jira/browse/GEODE-264
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.0.0-alpha1
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Trivial
> Fix For: 1.0.0-alpha1
>
>
> Several test classes generate warnings that should be cleaned up.
> {noformat}
> /Users/abaker/code/incubator-geode/gemfire-core/src/test/java/com/gemstone/gemfire/internal/compression/SnappyCompressorJUnitTest.java:57:
> warning: non-varargs call of varargs method with inexact argument type for
> last parameter;
> File nativeLibrary = (File) findNativeLibraryMethod.invoke(null, null);
> ^
> cast to Object for a varargs call
> cast to Object[] for a non-varargs call and to suppress this warning
> /Users/abaker/code/incubator-geode/gemfire-core/src/test/java/dunit/standalone/DUnitLauncher.java:107:
> warning: non-varargs call of varargs method with inexact argument type for
> last parameter;
> getInstance.invoke(null, null);
>^
> cast to Object for a varargs call
> cast to Object[] for a non-varargs call and to suppress this warning
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-213) JMX -http manager treats "start gateway-sender" as "start gateway-receiver"
[ https://issues.apache.org/jira/browse/GEODE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-213: Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > JMX -http manager treats "start gateway-sender" as "start gateway-receiver" > --- > > Key: GEODE-213 > URL: https://issues.apache.org/jira/browse/GEODE-213 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.0.0-alpha1 >Reporter: Vitaliy Gavrilov >Assignee: Kirk Lund > Fix For: 1.0.0-alpha1 > > > WanCommandsControlle in method startGatewaySender builds up a command using > the string constant for gateway receiver instead of sender -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-213) JMX -http manager treats "start gateway-sender" as "start gateway-receiver"
[ https://issues.apache.org/jira/browse/GEODE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-213: Affects Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > JMX -http manager treats "start gateway-sender" as "start gateway-receiver" > --- > > Key: GEODE-213 > URL: https://issues.apache.org/jira/browse/GEODE-213 > Project: Geode > Issue Type: Bug > Components: core >Affects Versions: 1.0.0-alpha1 >Reporter: Vitaliy Gavrilov >Assignee: Kirk Lund > Fix For: 1.0.0-alpha1 > > > WanCommandsControlle in method startGatewaySender builds up a command using > the string constant for gateway receiver instead of sender -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-246) Clean up WanCommandsControllerJUnitTest
[ https://issues.apache.org/jira/browse/GEODE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-246: Affects Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Clean up WanCommandsControllerJUnitTest > --- > > Key: GEODE-246 > URL: https://issues.apache.org/jira/browse/GEODE-246 > Project: Geode > Issue Type: Bug >Affects Versions: 1.0.0-alpha1 >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.0.0-alpha1 > > > Change parameters from comma-delimited to separate strings. Add assertions > for actual values of groups and members in the command. Simplify use of > JUnitParams -- only one list of parameters is really needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-246) Clean up WanCommandsControllerJUnitTest
[ https://issues.apache.org/jira/browse/GEODE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-246: Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Clean up WanCommandsControllerJUnitTest > --- > > Key: GEODE-246 > URL: https://issues.apache.org/jira/browse/GEODE-246 > Project: Geode > Issue Type: Bug >Affects Versions: 1.0.0-alpha1 >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.0.0-alpha1 > > > Change parameters from comma-delimited to separate strings. Add assertions > for actual values of groups and members in the command. Simplify use of > JUnitParams -- only one list of parameters is really needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-264) Fix varargs compiler warnings
[
https://issues.apache.org/jira/browse/GEODE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-264:
Affects Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> Fix varargs compiler warnings
> -
>
> Key: GEODE-264
> URL: https://issues.apache.org/jira/browse/GEODE-264
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.0.0-alpha1
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Trivial
> Fix For: 1.0.0-alpha1
>
>
> Several test classes generate warnings that should be cleaned up.
> {noformat}
> /Users/abaker/code/incubator-geode/gemfire-core/src/test/java/com/gemstone/gemfire/internal/compression/SnappyCompressorJUnitTest.java:57:
> warning: non-varargs call of varargs method with inexact argument type for
> last parameter;
> File nativeLibrary = (File) findNativeLibraryMethod.invoke(null, null);
> ^
> cast to Object for a varargs call
> cast to Object[] for a non-varargs call and to suppress this warning
> /Users/abaker/code/incubator-geode/gemfire-core/src/test/java/dunit/standalone/DUnitLauncher.java:107:
> warning: non-varargs call of varargs method with inexact argument type for
> last parameter;
> getInstance.invoke(null, null);
>^
> cast to Object for a varargs call
> cast to Object[] for a non-varargs call and to suppress this warning
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-209) FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is not stable
[
https://issues.apache.org/jira/browse/GEODE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-209:
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
> is not stable
> --
>
> Key: GEODE-209
> URL: https://issues.apache.org/jira/browse/GEODE-209
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-alpha1
>Reporter: Ashvin
>Assignee: Kirk Lund
>Priority: Minor
> Fix For: 1.0.0-alpha1
>
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
> failed 5 times in the last 30 runs. It is failing in the tearDown phase.
> {quote}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
> at
> com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {quote}
> {code}
> public void subTearDown() throws Exception {
> this.process.waitFor();
> assertFalse(this.process.isAlive());
> }
> {code}
> Fix to GEODE-127 may have caused this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-23) Generated POM missing JLine repo and needs to remove spring-data-gemfire
[ https://issues.apache.org/jira/browse/GEODE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-23: --- Affects Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Generated POM missing JLine repo and needs to remove spring-data-gemfire > > > Key: GEODE-23 > URL: https://issues.apache.org/jira/browse/GEODE-23 > Project: Geode > Issue Type: Bug > Components: build >Affects Versions: 1.0.0-alpha1 >Reporter: Anthony Baker >Assignee: Mark Bretl > Fix For: 1.0.0-alpha1 > > Attachments: GEODE-23.patch, gemfire-8.2.0.pom, > gemfire_dependencies.log, geode_dependencies.log, test.tgz > > > The POM file is missing the repository location for jline. In addition the > spring-data-gemfire dependency needs an exclusion so it does not pull in > gemfire-7.0.2. > See attached test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-38) Gfsh init script ignored
[ https://issues.apache.org/jira/browse/GEODE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-38: --- Affects Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Gfsh init script ignored > > > Key: GEODE-38 > URL: https://issues.apache.org/jira/browse/GEODE-38 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.0.0-alpha1 >Reporter: Neil Stevenson >Assignee: Kirk Lund >Priority: Trivial > Labels: gfsh > Fix For: 1.0.0-alpha1 > > Attachments: 0001-Initial-version.patch, > 0002-Review-board-changes.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > Gfsh launcher script implies an init file can be used. This was possible in > GF 6.6, but wasn't implemented in the transition to the new Gfsh in GF 7.0 > onwards. > From "gemfire-assembly/src/main/dist/bin/gfsh.bat " : > " > # > # Copy default .gfshrc to the home directory. Uncomment if needed. > # > #if [ ! -f $HOME/.gemfire/.gfsh2rc ]; then > # cp $GEMFIRE/defaultConfigs/.gemfire/.gfsh2rc $HOME > #fi > " > If this file is specified, it is currently ignored. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-21) Website updates from ProjectGeode.org git
[ https://issues.apache.org/jira/browse/GEODE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-21: --- Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Website updates from ProjectGeode.org git > - > > Key: GEODE-21 > URL: https://issues.apache.org/jira/browse/GEODE-21 > Project: Geode > Issue Type: Task > Components: general >Reporter: Gregory Chase >Assignee: Roman Shaposhnik > Labels: website > Fix For: 1.0.0-alpha1 > > Attachments: > 0001-GEODE-21.-Website-updates-from-ProjectGeode.org-git.patch > > > See pull requests on projectgeode.org site branch by myself and Chloe > updating various pages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-23) Generated POM missing JLine repo and needs to remove spring-data-gemfire
[ https://issues.apache.org/jira/browse/GEODE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-23: --- Fix Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Generated POM missing JLine repo and needs to remove spring-data-gemfire > > > Key: GEODE-23 > URL: https://issues.apache.org/jira/browse/GEODE-23 > Project: Geode > Issue Type: Bug > Components: build >Affects Versions: 1.0.0-alpha1 >Reporter: Anthony Baker >Assignee: Mark Bretl > Fix For: 1.0.0-alpha1 > > Attachments: GEODE-23.patch, gemfire-8.2.0.pom, > gemfire_dependencies.log, geode_dependencies.log, test.tgz > > > The POM file is missing the repository location for jline. In addition the > spring-data-gemfire dependency needs an exclusion so it does not pull in > gemfire-7.0.2. > See attached test case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2) Support JDK 8 on Geode
[ https://issues.apache.org/jira/browse/GEODE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-2: -- Affects Version/s: (was: 1.0.0-incubating) 1.0.0-alpha1 > Support JDK 8 on Geode > -- > > Key: GEODE-2 > URL: https://issues.apache.org/jira/browse/GEODE-2 > Project: Geode > Issue Type: Task > Components: general >Affects Versions: 1.0.0-alpha1 >Reporter: Pulkit Chandra >Assignee: William Markito Oliveira > Labels: JDK8SUPPORT > Fix For: 1.0.0-alpha1 > > Original Estimate: 504h > Remaining Estimate: 504h > > We have already reached EOL for JDK 7.0. We should be testing soon with JDK > 8.0. We can have sub tasks based on the issues reported on Geode with JDK 8.0. > EOL JDK 7: https://www.java.com/en/download/faq/java_7.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-496) CI failure: PRClientServerRegionFunctionExecutionNoSingleHopDUnitTest.testServerPutAllFunction
[
https://issues.apache.org/jira/browse/GEODE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-496:
Fix Version/s: 1.0.0-alpha1
> CI failure:
> PRClientServerRegionFunctionExecutionNoSingleHopDUnitTest.testServerPutAllFunction
> --
>
> Key: GEODE-496
> URL: https://issues.apache.org/jira/browse/GEODE-496
> Project: Geode
> Issue Type: Bug
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> Error Message
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3103
> java.net.SocketException: Connection reset by peer
> Stacktrace
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3103
> java.net.SocketException: Connection reset by peer
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Standard Output
> Previously run tests: [PRColocationDUnitTest,
> MultiRegionFunctionExecutionDUnitTest,
> PRClientServerRegionFunctionExecutionDUnitTest,
>
[jira] [Updated] (GEODE-15) Configure build machines on Jenkins to use JDK 8
[ https://issues.apache.org/jira/browse/GEODE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-15: --- Fix Version/s: 1.0.0-alpha1 > Configure build machines on Jenkins to use JDK 8 > > > Key: GEODE-15 > URL: https://issues.apache.org/jira/browse/GEODE-15 > Project: Geode > Issue Type: Task > Components: build >Affects Versions: 1.0.0-incubating >Reporter: William Markito Oliveira >Assignee: Mark Bretl > Fix For: 1.0.0-alpha1 > > > Given JDK 7 EOL, we need to update JDK version on build boxes under ASF > Jenkins in order to start using JDK 8+ for builds/tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-469) CI failure: PersistentColocatedPartitionedRegionDUnitTest.testReplaceOfflineMemberAndRestartTwoDiskStores
[
https://issues.apache.org/jira/browse/GEODE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-469:
Fix Version/s: 1.0.0-alpha1
> CI failure:
> PersistentColocatedPartitionedRegionDUnitTest.testReplaceOfflineMemberAndRestartTwoDiskStores
> -
>
> Key: GEODE-469
> URL: https://issues.apache.org/jira/browse/GEODE-469
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3982
> com.gemstone.gemfire.cache.RegionDestroyedException: The DiskRegion has been
> closed or destroyed
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Previously run tests: [RemoveAllDAckDUnitTest, RemoveDAckDUnitTest,
> RemoveGlobalDUnitTest, SizingFlagDUnitTest, SystemFailureDUnitTest,
> PersistentPartitionedRegionWithTransactionDUnitTest, Bug39356DUnitTest,
> Bug43684DUnitTest, Bug47388DUnitTest, Bug51400DUnitTest,
> ElidedPutAllDUnitTest, PartitionResolverDUnitTest,
> PartitionedRegionLoaderWriterDUnitTest,
> PartitionedRegionMetaDataCleanupDUnitTest, PersistPRKRFDUnitTest,
>
[jira] [Updated] (GEODE-75) Rebalance independent regions in parallel
[ https://issues.apache.org/jira/browse/GEODE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-75: --- Fix Version/s: 1.0.0-alpha1 > Rebalance independent regions in parallel > - > > Key: GEODE-75 > URL: https://issues.apache.org/jira/browse/GEODE-75 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Minor > Fix For: 1.0.0-alpha1 > > > Rebalancing a single region happens under a distributed lock by a single > coordinator. Multiple non-colocated regions should be able to be rebalanced > independently. > However, when rebalance is invoked through the API, a single thread goes > throw each region one by one and rebalances it. > We should provide the ability to parallelize a rebalance invoked through the > API, so that each region can be rebalanced in parallel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-463) CI failure: RegionWithHDFSBasicDUnitTest.testBasicPutsForWriteOnlyHDFSStore
[ https://issues.apache.org/jira/browse/GEODE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-463: Fix Version/s: 1.0.0-alpha1 > CI failure: RegionWithHDFSBasicDUnitTest.testBasicPutsForWriteOnlyHDFSStore > --- > > Key: GEODE-463 > URL: https://issues.apache.org/jira/browse/GEODE-463 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Sai Boorlagadda > Labels: HDFS > Fix For: 1.0.0-alpha1 > > > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 1046 > java.io.IOException: java.lang.InterruptedException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-350) PersistentColocatedPartitionedRegionDUnitTest.testReplaceOfflineMemberAndRestartCreateColocatedPRLate fails intermittently with suspect string
[ https://issues.apache.org/jira/browse/GEODE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-350: Fix Version/s: 1.0.0-alpha1 > PersistentColocatedPartitionedRegionDUnitTest.testReplaceOfflineMemberAndRestartCreateColocatedPRLate > fails intermittently with suspect string > -- > > Key: GEODE-350 > URL: https://issues.apache.org/jira/browse/GEODE-350 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Dan Smith >Priority: Minor > Labels: CI > Fix For: 1.0.0-alpha1 > > > Seen on a private build. Here is what was seen: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 4142 > com.gemstone.gemfire.cache.RegionDestroyedException: The DiskRegion has been > closed or destroyed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-162) testRegionIdleInvalidate entry invalidated prematurely
[ https://issues.apache.org/jira/browse/GEODE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-162: Fix Version/s: 1.0.0-alpha1 > testRegionIdleInvalidate entry invalidated prematurely > -- > > Key: GEODE-162 > URL: https://issues.apache.org/jira/browse/GEODE-162 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Minor > Fix For: 1.0.0-alpha1 > > > Test fails intermittently. > Failed in build #166: > https://builds.apache.org/view/All/job/Geode-nightly/166/testReport/com.gemstone.gemfire.cache30/DistributedAckPersistentRegionCCEOffHeapDUnitTest/testRegionIdleInvalidate/ > dunit.RMIException: While invoking > com.gemstone.gemfire.cache30.RegionTestCase$21.run in VM 0 running on Host > asf910.gq1.ygridcore.net with 4 VMs > at dunit.VM.invoke(VM.java:359) > at dunit.VM.invoke(VM.java:303) > at dunit.VM.invoke(VM.java:257) > at > com.gemstone.gemfire.cache30.RegionTestCase.testRegionIdleInvalidate(RegionTestCase.java:3798) > Caused by: junit.framework.AssertionFailedError: Entry invalidated 22 ms > prematurely (null) > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > com.gemstone.gemfire.cache30.RegionTestCase$21.run2(RegionTestCase.java:3888) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-50) Apache Geode Lab for OSCon 2015
[ https://issues.apache.org/jira/browse/GEODE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-50: --- Fix Version/s: 1.0.0-alpha1 > Apache Geode Lab for OSCon 2015 > > > Key: GEODE-50 > URL: https://issues.apache.org/jira/browse/GEODE-50 > Project: Geode > Issue Type: Task > Components: web-content >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira > Fix For: 1.0.0-alpha1 > > > During OSCon there will be an IoT lab and I'll be implementing and supporting > the Geode integration part of the lab. > The example code and content generated by this task will be then published to > the community in the Wiki or as blog post. > Given the focus on IoT the current proposals would be integration with a > Raspberry PI device or some sort of activity track band. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-107) Server failure
[ https://issues.apache.org/jira/browse/GEODE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-107: Fix Version/s: 1.0.0-alpha1 > Server failure > -- > > Key: GEODE-107 > URL: https://issues.apache.org/jira/browse/GEODE-107 > Project: Geode > Issue Type: Bug >Reporter: Haridarshan HS > Fix For: 1.0.0-alpha1 > > > Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" com.gemstone.gemfire.SystemConnectException: > Attempt to connect to distributed system timed out > at > Could not start the server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-76) Running ordered queries on PDX Instances.
[ https://issues.apache.org/jira/browse/GEODE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-76: --- Fix Version/s: 1.0.0-alpha1 > Running ordered queries on PDX Instances. > - > > Key: GEODE-76 > URL: https://issues.apache.org/jira/browse/GEODE-76 > Project: Geode > Issue Type: Bug > Components: querying, serialization >Reporter: Altan Gokcek >Assignee: Jason Huynh >Priority: Critical > Fix For: 1.0.0-alpha1 > > > When we create PDX instances by sending json to gemfire, if a filed is number > type gemfire decides in which datatype it will save it to region (<128 byte, > >128 short, >65536 Integer etc...) this is totally normal. > Problem is in order to run a ordered query. For example, > "select * from /myRegion ORDERY BY myNumberField" > We get such errors "byte and short cannot be compared or short and Integer > cannot be compared" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-83) Support AUTH for Redis protocol adaptor
[ https://issues.apache.org/jira/browse/GEODE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-83: --- Fix Version/s: 1.0.0-alpha1 > Support AUTH for Redis protocol adaptor > --- > > Key: GEODE-83 > URL: https://issues.apache.org/jira/browse/GEODE-83 > Project: Geode > Issue Type: Improvement > Components: extensions >Reporter: Swapnil Bawaskar > Fix For: 1.0.0-alpha1 > > > The Redis protocol supports basic authentication through the AUTH command: > http://redis.io/topics/security > Rather than storing the password in redis.conf, we should ask the users to > store it in gfsecurity.conf file as a "redis-password" property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-430) CI failure: UpdatePropagationDUnitTest.testVerifyUpdatesReceivedByOtherClients
[
https://issues.apache.org/jira/browse/GEODE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-430:
Fix Version/s: 1.0.0-alpha1
> CI failure: UpdatePropagationDUnitTest.testVerifyUpdatesReceivedByOtherClients
> --
>
> Key: GEODE-430
> URL: https://issues.apache.org/jira/browse/GEODE-430
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Bruce Schuchardt
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.tier.sockets.UpdatePropagationDUnitTest.acquireConnectionsAndPutonK1andK2
> in VM 2 running on Host angola.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:161)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.UpdatePropagationDUnitTest.testVerifyUpdatesReceivedByOtherClients(UpdatePropagationDUnitTest.java:369)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: while setting
> acquireConnections
> com.gemstone.gemfire.cache.client.ServerConnectivityException: Pool
> unexpected closed socket on server connection=Pooled Connection to
> angola.gemstone.com:24028: Connection[DESTROYED]). Server unreachable: could
> not connect after 1 attempts
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.UpdatePropagationDUnitTest.acquireConnectionsAndPutonK1andK2(UpdatePropagationDUnitTest.java:398)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Updated] (GEODE-352) PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_byInlineFunction fails intermittently with suspect string
[
https://issues.apache.org/jira/browse/GEODE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-352:
Fix Version/s: 1.0.0-alpha1
> PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_byInlineFunction
> fails intermittently with suspect string
> ---
>
> Key: GEODE-352
> URL: https://issues.apache.org/jira/browse/GEODE-352
> Project: Geode
> Issue Type: Bug
>Reporter: Darrel Schneider
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> Failure was on a private build.
> {code}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 2039
> java.net.SocketTimeoutException: Read timed out
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-525) Javadocs: addGatewayEventFilter() doc correction
[ https://issues.apache.org/jira/browse/GEODE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-525: Fix Version/s: 1.0.0-alpha1 > Javadocs: addGatewayEventFilter() doc correction > > > Key: GEODE-525 > URL: https://issues.apache.org/jira/browse/GEODE-525 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Dave Barnes > Fix For: 1.0.0-alpha1 > > > The Javadoc comment for addGatewayEventFilter() says 'Removes...', should say > 'Adds'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-337) CI failure: ClientHealthStatsDUnitTest.testStatsMatchWithSize
[ https://issues.apache.org/jira/browse/GEODE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-337: Fix Version/s: 1.0.0-alpha1 > CI failure: ClientHealthStatsDUnitTest.testStatsMatchWithSize > - > > Key: GEODE-337 > URL: https://issues.apache.org/jira/browse/GEODE-337 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Jason Huynh >Assignee: Anilkumar Gingade > Labels: CI > Fix For: 1.0.0-alpha1 > > > While running tests the following issue occurred for this test: > dunit.RMIException: While invoking > com.gemstone.gemfire.management.ClientHealthStatsDUnitTest.createClientCache > in VM 2 running on Host zambia.gemstone.com with 4 VMs > at dunit.VM.invoke(VM.java:161) > at > com.gemstone.gemfire.management.ClientHealthStatsDUnitTest.testStatsMatchWithSize(ClientHealthStatsDUnitTest.java:195) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at > org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: > com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException: > com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException: Could not > initialize a primary queue on startup. No queue servers available. > at > com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:190) > at > com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:522) > at >
[jira] [Updated] (GEODE-41) Dummy feature for gitflow validation
[ https://issues.apache.org/jira/browse/GEODE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-41: --- Fix Version/s: 1.0.0-alpha1 > Dummy feature for gitflow validation > > > Key: GEODE-41 > URL: https://issues.apache.org/jira/browse/GEODE-41 > Project: Geode > Issue Type: Improvement > Components: general >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira >Priority: Trivial > Fix For: 1.0.0-alpha1 > > > Dummy feature for gitflow validation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-311) pdx registry logging should be at info level
[ https://issues.apache.org/jira/browse/GEODE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-311: Fix Version/s: 1.0.0-alpha1 > pdx registry logging should be at info level > > > Key: GEODE-311 > URL: https://issues.apache.org/jira/browse/GEODE-311 > Project: Geode > Issue Type: Improvement >Reporter: Darrel Schneider >Assignee: Darrel Schneider > Fix For: 1.0.0-alpha1 > > Original Estimate: 4h > Remaining Estimate: 4h > > The logging of pdx type's should be done at the "info" level. It was > accidentally changed to "fine" level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-155) RegionWithHDFS*BasicDUnitTest.testWOTimeForRollOverParam failed due to incorrect number of files created.
[
https://issues.apache.org/jira/browse/GEODE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-155:
Fix Version/s: 1.0.0-alpha1
> RegionWithHDFS*BasicDUnitTest.testWOTimeForRollOverParam failed due to
> incorrect number of files created.
> -
>
> Key: GEODE-155
> URL: https://issues.apache.org/jira/browse/GEODE-155
> Project: Geode
> Issue Type: Bug
> Components: hdfs
>Affects Versions: 1.0.0-incubating
>Reporter: Amogh Shetkar
>Assignee: Amogh Shetkar
> Fix For: 1.0.0-alpha1
>
>
> The same test case in two distributed tests failed with the same error in
> Jenkins build #165.
> {code}
> com.gemstone.gemfire.cache.hdfs.internal.RegionWithHDFSOffHeapBasicDUnitTest
> > testWOTimeForRollOverParam FAILED
> junit.framework.AssertionFailedError: there should be exactly two files,
> but there are 1
> com.gemstone.gemfire.cache.hdfs.internal.RegionWithHDFSBasicDUnitTest >
> testWOTimeForRollOverParam FAILED
> junit.framework.AssertionFailedError: there should be exactly two files,
> but there are 1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> com.gemstone.gemfire.cache.hdfs.internal.RegionWithHDFSBasicDUnitTest.verifyTwoHDFSFiles(RegionWithHDFSBasicDUnitTest.java:1075)
> at
> com.gemstone.gemfire.cache.hdfs.internal.RegionWithHDFSBasicDUnitTest.testWOTimeForRollOverParam(RegionWithHDFSBasicDUnitTest.java:1023)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-505) HARQueueNewImplDUnitTest.testCMRNotReturnedByRootRegionsMethod failed
[
https://issues.apache.org/jira/browse/GEODE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-505:
Fix Version/s: 1.0.0-alpha1
> HARQueueNewImplDUnitTest.testCMRNotReturnedByRootRegionsMethod failed
> -
>
> Key: GEODE-505
> URL: https://issues.apache.org/jira/browse/GEODE-505
> Project: Geode
> Issue Type: Bug
>Reporter: xiaojian zhou
>Assignee: Sai Boorlagadda
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> revision d08e51d2eaa391fcda11cd18ee4413aa5fe6b80d
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3069
> [warn 2015/10/27 05:52:16.600 PDT
> tid=0x6827] Server connection from
> [identity(angola(10759:loner):56230:ef2d5ba9,connection=1; port=56230]:
> Unexpected IOException:
> ---
> Found suspect string in log4j at line 3070
> java.net.SocketException: Connection reset
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:316)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:793)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:768)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:746)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor122.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-196) Remove unneeded system out in RuntimeIterator
[
https://issues.apache.org/jira/browse/GEODE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-196:
Fix Version/s: 1.0.0-alpha1
> Remove unneeded system out in RuntimeIterator
> -
>
> Key: GEODE-196
> URL: https://issues.apache.org/jira/browse/GEODE-196
> Project: Geode
> Issue Type: Bug
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Minor
> Fix For: 1.0.0-alpha1
>
>
> Remove the system out and if block in RuntimeIterator. The lines are:
> if(current == UNINITIALIZED) {
> System.out.println("asif");
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-56) Put to partitioned region with overflow doesn't properly update numOverflowBytesOnDisk
[
https://issues.apache.org/jira/browse/GEODE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-56:
---
Fix Version/s: 1.0.0-alpha1
> Put to partitioned region with overflow doesn't properly update
> numOverflowBytesOnDisk
> --
>
> Key: GEODE-56
> URL: https://issues.apache.org/jira/browse/GEODE-56
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-alpha1
>
>
> For the purposes of rebalancing, geode keeps track of the amount of data
> stored on disk in a counter - BucketRegion.numOverflowBytesOnDisk.
> For regions that have overflow but not persistence, a put that replaces a
> value that was overflowed on disk does not correctly decrement the counter of
> bytes overflowed to disk.
> The issue is that that size of the entry on disk is read in an if block
> testing to see if the region is persistent (dr.isBackup())
> {code}
> if (dr.isBackup()) {
> dr.testIsRecoveredAndClear(did); // fixes bug 41409
> oldValueLength = getValueLength(did);
> {code}
> Later it is used to change the stat, but it oldValueLength may not be set
> {code}
> incrementBucketStats(region, 1/*InVM*/, -1/*OnDisk*/,
> -oldValueLength);
> {code}
> The net effect of this issue is that if a lot of puts happen to entries that
> are overflowed to disk, the size of the bucket will be inflated. This may
> then cause issues with rebalancing calculations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-539) Remove XD artifacts from off-heap feature
[ https://issues.apache.org/jira/browse/GEODE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-539: Fix Version/s: 1.0.0-alpha1 > Remove XD artifacts from off-heap feature > - > > Key: GEODE-539 > URL: https://issues.apache.org/jira/browse/GEODE-539 > Project: Geode > Issue Type: Improvement > Components: offheap >Reporter: Darrel Schneider >Assignee: Darrel Schneider > Fix For: 1.0.0-alpha1 > > > The off-heap feature has a number of implementation details that were added > for the XD product which is not part of Geode. > The interface OffHeapReference should be removed since it only exists because > of some XD build issues. > The following src types in are all for XD features: > SRC_TYPE_NO_LOB_NO_DELTA > SRC_TYPE_WITH_LOBS > SRC_TYPE_WITH_SINGLE_DELTA > SRC_TYPE_WITH_MULTIPLE_DELTAS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-149) gradle build does not rerun passed test
[ https://issues.apache.org/jira/browse/GEODE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-149: Fix Version/s: 1.0.0-alpha1 > gradle build does not rerun passed test > --- > > Key: GEODE-149 > URL: https://issues.apache.org/jira/browse/GEODE-149 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Minor > Fix For: 1.0.0-alpha1 > > > When running a test multiple times, gradle does not reexecute the test > because the output is considered "up to date". This makes it difficult to try > to reproduce a test that only fails intermittently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-13) Merge Hibernate L2 cache
[ https://issues.apache.org/jira/browse/GEODE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-13: --- Fix Version/s: 1.0.0-alpha1 > Merge Hibernate L2 cache > > > Key: GEODE-13 > URL: https://issues.apache.org/jira/browse/GEODE-13 > Project: Geode > Issue Type: Sub-task > Components: extensions >Reporter: Anthony Baker > Fix For: 1.0.0-alpha1 > > > GemFire includes support for Hibernate L2 cache. This task tracks the > donation of the code for Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-112) Geode Jenkins runs out of memory when archiving test reports
[
https://issues.apache.org/jira/browse/GEODE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-112:
Fix Version/s: 1.0.0-alpha1
> Geode Jenkins runs out of memory when archiving test reports
>
>
> Key: GEODE-112
> URL: https://issues.apache.org/jira/browse/GEODE-112
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Kirk Lund
>Assignee: Mark Bretl
> Labels: build
> Fix For: 1.0.0-alpha1
>
>
> Jenkins intermittently runs out of memory when archiving test reports for
> Geode:
> {code}
> BUILD FAILED
> Total time: 7 hrs 7 mins 57.659 secs
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Sending artifact delta relative to Geode-nightly #122
> Archived 2 artifacts
> Archive block size is 32768
> Received 1493 blocks and 128755578 bytes
> Compression is 27.5%
> Took 39 sec
> Recording test results
> ERROR: Failed to archive test reports
> java.io.IOException: remote file operation failed:
> /home/jenkins/jenkins-slave/workspace/Geode-nightly at
> hudson.remoting.Channel@18a56604:ubuntu-1
> at hudson.FilePath.act(FilePath.java:916)
> at hudson.FilePath.act(FilePath.java:893)
> at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
> at
> hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:117)
> at
> hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:129)
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
> at hudson.model.Build$BuildExecution.post2(Build.java:182)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
> at hudson.model.Run.execute(Run.java:1731)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:232)
> Caused by: java.io.IOException: Remote call on ubuntu-1 failed
> at hudson.remoting.Channel.call(Channel.java:751)
> at hudson.FilePath.act(FilePath.java:909)
> ... 13 more
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOfRange(Arrays.java:2694)
> at java.lang.String.(String.java:203)
> at org.dom4j.io.SAXContentHandler.characters(SAXContentHandler.java:293)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:546)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
> at org.dom4j.io.SAXReader.read(SAXReader.java:465)
> at org.dom4j.io.SAXReader.read(SAXReader.java:264)
> at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:273)
> at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:229)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:164)
> at hudson.tasks.junit.TestResult.parse(TestResult.java:147)
> at hudson.tasks.junit.TestResult.(TestResult.java:123)
> at
> hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117)
> at
> hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:328)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Sending e-mails
[jira] [Updated] (GEODE-362) TXExpiryJUnitTest.testEntryIdleExpiration intermittently fails because Cache listener detected a destroy
[
https://issues.apache.org/jira/browse/GEODE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-362:
Fix Version/s: 1.0.0-alpha1
> TXExpiryJUnitTest.testEntryIdleExpiration intermittently fails because Cache
> listener detected a destroy
>
>
> Key: GEODE-362
> URL: https://issues.apache.org/jira/browse/GEODE-362
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Minor
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> This was seen on a private build of git rev
> 4708d4e182f89c6a391fcad8bac854f929717685:
> {code}
> java.lang.AssertionError: Cache listener detected a destroy oh man that is
> bad!
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.TXExpiryJUnitTest.waitDance(TXExpiryJUnitTest.java:122)
> at
> com.gemstone.gemfire.TXExpiryJUnitTest.generalEntryExpirationTest(TXExpiryJUnitTest.java:186)
> at
> com.gemstone.gemfire.TXExpiryJUnitTest.testEntryIdleExpiration(TXExpiryJUnitTest.java:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-223) RedisDistDUnitTest.testConcCreateDestroy NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-223:
Fix Version/s: 1.0.0-alpha1
> RedisDistDUnitTest.testConcCreateDestroy NullPointerException
> -
>
> Key: GEODE-223
> URL: https://issues.apache.org/jira/browse/GEODE-223
> Project: Geode
> Issue Type: Bug
> Components: extensions
>Reporter: Darrel Schneider
>Assignee: Vitaliy Gavrilov
> Fix For: 1.0.0-alpha1
>
>
> com.gemstone.gemfire.redis.RedisDistDUnitTest.testConcCreateDestroy failed
> because of this suspect string:
> Found suspect string in log4j at line 1132
> [error 2015/08/11 11:39:31.020 PDT cc3-rh6(17559):13796 shared ordered uid=236 port=51035> tid=0x1506]
> Exception occurred in CacheListener
> java.lang.NullPointerException
> at
> java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1124)
> at
> com.gemstone.gemfire.internal.redis.RegionProvider.createRemoteRegionLocally(RegionProvider.java:222)
> at
> com.gemstone.gemfire.redis.GemFireRedisServer.afterKeyCreate(GemFireRedisServer.java:532)
> at
> com.gemstone.gemfire.redis.GemFireRedisServer.access$400(GemFireRedisServer.java:128)
> at
> com.gemstone.gemfire.redis.GemFireRedisServer$MetaCacheListener.afterCreate(GemFireRedisServer.java:559)
> at
> com.gemstone.gemfire.internal.cache.EnumListenerEvent$AFTER_CREATE.dispatchEvent(EnumListenerEvent.java:97)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:9251)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:7700)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.invokePutCallbacks(LocalRegion.java:6466)
> at
> com.gemstone.gemfire.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2623)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:157)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPutPart2(LocalRegion.java:6316)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:3214)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:6125)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:394)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:118)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicUpdate(LocalRegion.java:6100)
> at
> com.gemstone.gemfire.internal.cache.AbstractUpdateOperation.doPutOrCreate(AbstractUpdateOperation.java:142)
> at
> com.gemstone.gemfire.internal.cache.AbstractUpdateOperation$AbstractUpdateMessage.basicOperateOnRegion(AbstractUpdateOperation.java:280)
> I think the bug is in this code from RegionProvider:
> {code}
> r = cache.getRegion(key.toString());
> if (type == RedisDataType.REDIS_LIST)
> doInitializeList(key, r);
> else if (type == RedisDataType.REDIS_SORTEDSET)
> doInitializeSortedSet(key, r);
> this.regions.put(key, r);
> {code}
> The NPE happens on the last line (the put call) because r is null.
> I think this code just needs to handle the race in which cache.getRegion
> returns null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-684) CI failure: PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testServerGetAllFunction
[
https://issues.apache.org/jira/browse/GEODE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-684:
Fix Version/s: 1.0.0-alpha1
> CI failure:
> PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testServerGetAllFunction
> --
>
> Key: GEODE-684
> URL: https://issues.apache.org/jira/browse/GEODE-684
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-incubating
>Reporter: Jens Deppe
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> git rev fdec70bcd46c568637f0dad976f3778625858608 build #916
> {noformat}
> Error Message
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3240
> [fatal 2015/12/16 03:19:58.066 PST /0:0:0:0:0:0:0:0:27938 local port: 27938> tid=0x2d62] Failed to send message
> path='/_gfe_non_durable_client_with_id_cc4-rh6(21142:loner):58646:419a84aa_1_queue';
> sender=cc4-rh6(21124):1025; callbackArg=null; processorId=17795;
> op=REGION_LOCAL_DESTROY; applied=false; directAck=false; posdup=false;
> hasDelta=false; hasOldValue=false; eventID=null; serialNum=5515;
> subregionSerialNumbers={}; notifyOfRegionDeparture=false)> to member
> view =
> View[cc4-rh6(21119:locator):1024|1384] members:
> [cc4-rh6(21119:locator):1024, cc4-rh6(21124):1025{lead},
> cc4-rh6(21132):1026, cc4-rh6(21138):1027]
> com.gemstone.gemfire.distributed.internal.direct.ShunnedMemberException:
> Member is being shunned: {0}
> at
> com.gemstone.gemfire.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:599)
> at
> com.gemstone.gemfire.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:374)
> at
> com.gemstone.gemfire.distributed.internal.direct.DirectChannel.send(DirectChannel.java:667)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1730)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1924)
> at
> com.gemstone.gemfire.distributed.internal.DistributionChannel.send(DistributionChannel.java:88)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.sendOutgoing(DistributionManager.java:3474)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.sendMessage(DistributionManager.java:3515)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.putOutgoing(DistributionManager.java:1874)
> at
> com.gemstone.gemfire.internal.cache.DistributedCacheOperation.distribute(DistributedCacheOperation.java:529)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.distributeDestroyRegion(DistributedRegion.java:1957)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1932)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6825)
> at
> com.gemstone.gemfire.internal.cache.HARegion.destroyRegion(HARegion.java:347)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.destroyRegion(AbstractRegion.java:376)
> at
> com.gemstone.gemfire.internal.cache.ha.HARegionQueue.destroy(HARegionQueue.java:3733)
> at
> com.gemstone.gemfire.internal.cache.ha.HARegionQueue$BlockingHARegionQueue.destroy(HARegionQueue.java:2392)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.destroyRQ(CacheClientProxy.java:1065)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.terminateDispatching(CacheClientProxy.java:973)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.close(CacheClientProxy.java:850)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.closeDeadProxies(CacheClientNotifier.java:1977)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.unregisterClient(CacheClientNotifier.java:785)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ClientHealthMonitor.unregisterClient(ClientHealthMonitor.java:275)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.handleTermination(ServerConnection.java:906)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.handleTermination(ServerConnection.java:827)
> at
>
[jira] [Updated] (GEODE-637) Additional Tests for AsyncEventQueue
[ https://issues.apache.org/jira/browse/GEODE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-637: Fix Version/s: 1.0.0-alpha1 > Additional Tests for AsyncEventQueue > > > Key: GEODE-637 > URL: https://issues.apache.org/jira/browse/GEODE-637 > Project: Geode > Issue Type: Improvement >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-alpha1 > > > There were a few tests that pivotal missed in the initial code contribution > that cover AsyncEventQueues. This jira covers merging those tests into geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-504) Remove MaxPermSize references
[
https://issues.apache.org/jira/browse/GEODE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-504:
Fix Version/s: 1.0.0-alpha1
> Remove MaxPermSize references
> ---
>
> Key: GEODE-504
> URL: https://issues.apache.org/jira/browse/GEODE-504
> Project: Geode
> Issue Type: Improvement
>Reporter: William Markito Oliveira
>Assignee: William Markito Oliveira
> Fix For: 1.0.0-alpha1
>
>
> Clear these warnings in our build due to this property.
> {code}
> MaxPermSize=256M; support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M;
> support was removed in 8.0
> {code}
> A simple grep on the codebase return the following entries:
> {code}
> build.gradle:jvmArgs = ['-XX:+HeapDumpOnOutOfMemoryError',
> '-XX:MaxPermSize=256M', '-ea']
> gemfire-core/src/test/java/dunit/standalone/ProcessManager.java:
> "-XX:MaxPermSize=256M",
> gemfire-core/src/test/java/dunit/standalone/ProcessManager.java:
> "-XX:MaxPermSize=256M",
> gemfire-spark-connector/.idea/workspace.xml: name="VM_PARAMETERS" value="-Xmx512m -Xms256m -XX:MaxPermSize=250m -ea" />
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-157) Check for colocation not failing if non colocated comparison is first comparison made
[ https://issues.apache.org/jira/browse/GEODE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-157: Fix Version/s: 1.0.0-alpha1 > Check for colocation not failing if non colocated comparison is first > comparison made > - > > Key: GEODE-157 > URL: https://issues.apache.org/jira/browse/GEODE-157 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > Fix For: 1.0.0-alpha1 > > > There is a bug when checking for co located regions, if the first region > being checked happens to be not co located, the logic ignores this and > continues onward. This then causes the query to throw an unrelated > exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-179) DistributedNoAckRegionCCEOffHeapDUnitTest.testEntryTtlDestroyEvent intermittent assertion falure
[ https://issues.apache.org/jira/browse/GEODE-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-179: Fix Version/s: 1.0.0-alpha1 > DistributedNoAckRegionCCEOffHeapDUnitTest.testEntryTtlDestroyEvent > intermittent assertion falure > > > Key: GEODE-179 > URL: https://issues.apache.org/jira/browse/GEODE-179 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Minor > Fix For: 1.0.0-alpha1 > > > See: > https://builds.apache.org/view/All/job/Geode-nightly/172/testReport/com.gemstone.gemfire.cache30/DistributedNoAckRegionCCEOffHeapDUnitTest/testEntryTtlDestroyEvent/ > dunit.RMIException: While invoking > com.gemstone.gemfire.cache30.MultiVMRegionTestCase$183.run in VM 1 running on > Host asf903.gq1.ygridcore.net with 4 VMs > at dunit.VM.invoke(VM.java:359) > at dunit.VM.invoke(VM.java:303) > at dunit.VM.invoke(VM.java:257) > at > com.gemstone.gemfire.cache30.MultiVMRegionTestCase.testEntryTtlDestroyEvent(MultiVMRegionTestCase.java:3927) > Caused by: junit.framework.AssertionFailedError: Expected: but was: > NonTXEntry@655cb9ec VersionedThinRegionEntryOffHeapStringKey1@2ab268f1 > (key=KEY; >
[jira] [Updated] (GEODE-424) CI failure: DistTXPersistentDebugDUnitTest.testTXPRRR2_putall
[
https://issues.apache.org/jira/browse/GEODE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-424:
Fix Version/s: 1.0.0-alpha1
> CI failure: DistTXPersistentDebugDUnitTest.testTXPRRR2_putall
> -
>
> Key: GEODE-424
> URL: https://issues.apache.org/jira/browse/GEODE-424
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.createCacheInVm in VM 1
> running on Host cc6-co6.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:161)
> at dunit.VM.invoke(VM.java:86)
> at
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.createCacheInAllVms(DistTXDebugDUnitTest.java:83)
> at
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPRRR2_putall(DistTXDebugDUnitTest.java:615)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor131.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.gemstone.gemfire.cache.CacheExistsException: GemFireCache[id =
> 729430198; isClosing = false; isShutDownAll = false; created = Sat Oct 17
> 14:39:00 PDT 2015; server = false; copyOnRead = false; lockLease = 120;
> lockTimeout = 60]: An open cache already exists.
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:774)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:170)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:161)
> at
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.createCacheInVm(DistTXDebugDUnitTest.java:78)
> at
[jira] [Updated] (GEODE-412) CI failure: OnGroupsFunctionExecutionDUnitTest.testNoAckGroupsFunction
[ https://issues.apache.org/jira/browse/GEODE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-412: Fix Version/s: 1.0.0-alpha1 > CI failure: OnGroupsFunctionExecutionDUnitTest.testNoAckGroupsFunction > -- > > Key: GEODE-412 > URL: https://issues.apache.org/jira/browse/GEODE-412 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Assignee: Hitesh Khamesra > Labels: CI > Fix For: 1.0.0-alpha1 > > > Failed 1 times in the last 30 runs. Stability: 96 % > Error Message > junit.framework.AssertionFailedError: Event never occurred after 3 ms: > OnGroupsNoAck invocation count mismatch > Stacktrace > junit.framework.AssertionFailedError: Event never occurred after 3 ms: > OnGroupsNoAck invocation count mismatch > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.TestCase.fail(TestCase.java:227) > at > dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1162) > at > com.gemstone.gemfire.internal.cache.execute.OnGroupsFunctionExecutionDUnitTest.testNoAckGroupsFunction(OnGroupsFunctionExecutionDUnitTest.java:1184) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-678) DistributedLockService: reentrant lock calls with a small wait time can cause the lock to be lost
[ https://issues.apache.org/jira/browse/GEODE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-678: Fix Version/s: 1.0.0-alpha1 > DistributedLockService: reentrant lock calls with a small wait time can cause > the lock to be lost > - > > Key: GEODE-678 > URL: https://issues.apache.org/jira/browse/GEODE-678 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Darrel Schneider >Assignee: Darrel Schneider > Fix For: 1.0.0-alpha1 > > > If a thread already holds a lock from the DistributedLockService (this also > applies to global regions and using Region.getDistributedLock) then it can > reenter the lock by acquiring it again by calling lock. Since the thread > already holds the lock it does not need to wait to acquire it. But if a very > small waitTIme parameter is passed then the implementation may timeout the > reacquire call telling the caller that it could not acquire the lock. > In this case the thread also loses the original lock it held and future > attempts to release it will fail with LockNotHeldException. > The waitTime should only be considered in the initial lock request when you > might be waiting for some other thread to release the lock. If you already > hold the lock then waitTime should be ignored. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-398) CI failure: DistTXExpiryJUnitTest.testEntryTTLExpiration
[ https://issues.apache.org/jira/browse/GEODE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-398: Fix Version/s: 1.0.0-alpha1 > CI failure: DistTXExpiryJUnitTest.testEntryTTLExpiration > > > Key: GEODE-398 > URL: https://issues.apache.org/jira/browse/GEODE-398 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Assignee: Darrel Schneider > Labels: CI > Fix For: 1.0.0-alpha1 > > > Failed 1 times in the last 30 runs. Stability: 96 % > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > com.gemstone.gemfire.TXExpiryJUnitTest.generalEntryExpirationTest(TXExpiryJUnitTest.java:225) > at > com.gemstone.gemfire.TXExpiryJUnitTest.testEntryTTLExpiration(TXExpiryJUnitTest.java:96) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-176) Validating offheap orphan on bucket region in unit test may hit RegionDestroyedException
[ https://issues.apache.org/jira/browse/GEODE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-176: Fix Version/s: 1.0.0-alpha1 > Validating offheap orphan on bucket region in unit test may hit > RegionDestroyedException > > > Key: GEODE-176 > URL: https://issues.apache.org/jira/browse/GEODE-176 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Trivial > Fix For: 1.0.0-alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-6) Merge GemFire tests to Geode
[ https://issues.apache.org/jira/browse/GEODE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-6: -- Fix Version/s: 1.0.0-alpha1 > Merge GemFire tests to Geode > > > Key: GEODE-6 > URL: https://issues.apache.org/jira/browse/GEODE-6 > Project: Geode > Issue Type: Sub-task > Components: general >Reporter: Dan Smith >Assignee: Darrel Schneider > Labels: asf-migration > Fix For: 1.0.0-alpha1 > > > The initial drop of Geode received from pivotal contains only a few of the > tests from GemFire. > The GemFire team is working on getting the rest of the unit tests contributed > to the open source project. This bug tracks the status of that work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-191) region.size() operation sometimes returns incorrect results
[ https://issues.apache.org/jira/browse/GEODE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-191: Fix Version/s: 1.0.0-alpha1 > region.size() operation sometimes returns incorrect results > --- > > Key: GEODE-191 > URL: https://issues.apache.org/jira/browse/GEODE-191 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Swapnil Bawaskar > Fix For: 1.0.0-alpha1 > > Attachments: testForSize.txt > > > In case where a transaction is hosted on a remote member, doing a > region.size() operation on a partitioned region returns an incorrect size. > The operation returns 0 for size of all the buckets hosted locally. > This seems to have been introduced in the merge from sga2 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-175) ClientServerTransactionDUnitTest.testExpirySuspend_bug45984 fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-175:
Fix Version/s: 1.0.0-alpha1
> ClientServerTransactionDUnitTest.testExpirySuspend_bug45984 fails
> intermittently
>
>
> Key: GEODE-175
> URL: https://issues.apache.org/jira/browse/GEODE-175
> Project: Geode
> Issue Type: Bug
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Minor
> Fix For: 1.0.0-alpha1
>
>
> The assert that fails is that an entry should no longer exist after a 5
> second pause because of expiration:
> DistributedTestCase.pause(5000);
> TransactionId tx = getCache().getCacheTransactionManager().suspend();
> // A remote tx will allow expiration to happen on the side that
> // is not hosting the tx. But it will not allow an expiration
> // initiated on the hosting jvm.
> assertFalse(r.containsKey("key"));
> The test configures the region with 1 second expiration so it seems like
> giving it 4 extra seconds should be plenty. But the test should be rewritten
> to use a wait criteria and to use millisecond expiration.
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.RemoteTransactionDUnitTest$134.call in VM
> 0 running on Host cc4-rh6.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.RemoteTransactionDUnitTest.testExpirySuspend_bug45984(RemoteTransactionDUnitTest.java:4026)
> Caused by: junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at
> com.gemstone.gemfire.internal.cache.RemoteTransactionDUnitTest$134.call(RemoteTransactionDUnitTest.java:4040)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-680) Chunk class refactoring encountered while writing unit tests.
[ https://issues.apache.org/jira/browse/GEODE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-680: Fix Version/s: 1.0.0-alpha1 > Chunk class refactoring encountered while writing unit tests. > - > > Key: GEODE-680 > URL: https://issues.apache.org/jira/browse/GEODE-680 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda > Fix For: 1.0.0-alpha1 > > > Good to have Chunk refactoring encountered while writing unit tests > 1. Promote REF_COUNT_OFFSET to at-least protected access level and use it in > GemFireChunkJUnitTest - search by REF_COUNT_OFFSET in the comments. > 2. Promote MAX_REF_COUNT to at-least protected access level and use it in > GemFireChunkJUnitTest.retainShouldThrowExceptionAfterMaxNumberOfTimesRetained > 3. Promote IS_SERIALIZED_BIT & IS_COMPRESSED_BIT to at-least protected level > and use it in GemFireChunkJUnitTest - search by IS_SERIALIZED_BIT in the > comments > 4. Chunk.getAddressForReading - can delete to Chunk.getUnsafeAddress, as both > the methods are similar and `getUnsafeAddress` has more assert checks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-436) CI failure: DistributedAckRegionCompressionDUnitTest.testEntryTtlLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-436:
Fix Version/s: 1.0.0-alpha1
> CI failure: DistributedAckRegionCompressionDUnitTest.testEntryTtlLocalDestroy
> -
>
> Key: GEODE-436
> URL: https://issues.apache.org/jira/browse/GEODE-436
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$189.run in VM 0 running on
> Host latvia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:360)
> at dunit.VM.invoke(VM.java:303)
> at dunit.VM.invoke(VM.java:257)
> at
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.testEntryTtlLocalDestroy(MultiVMRegionTestCase.java:4060)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor212.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: Expected: but was:
> NonTXEntry@32512087 VMStatsRegionEntryHeapStringKey1@45593df3 (key=KEY;
> rawValue=[B@4407676e)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNull(Assert.java:277)
> at junit.framework.Assert.assertNull(Assert.java:268)
> at junit.framework.TestCase.assertNull(TestCase.java:438)
> at
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$189.run2(MultiVMRegionTestCase.java:4090)
> at
> com.gemstone.gemfire.cache30.CacheSerializableRunnable.run(CacheSerializableRunnable.java:46)
> at
[jira] [Updated] (GEODE-439) CI failure: PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException
[
https://issues.apache.org/jira/browse/GEODE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-439:
Fix Version/s: 1.0.0-alpha1
> CI failure:
> PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException
> -
>
> Key: GEODE-439
> URL: https://issues.apache.org/jira/browse/GEODE-439
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Sai Boorlagadda
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3043
> [warn 2015/10/19 08:04:12.058 PDT
> tid=0x2815] Server connection from
> [identity(venezuela(8655:loner):53577:a415a180,connection=1; port=53579]:
> Unexpected IOException:
> ---
> Found suspect string in log4j at line 3044
> java.net.SocketException: Connection reset
> at org.junit.Assert.fail(Assert.java:88)
> at
> dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307)
> at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784)
> at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759)
> at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737)
> at junit.framework.TestCase.runBare(TestCase.java:146)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Previously run tests:
> [PRClientServerRegionFunctionExecutionNoSingleHopDUnitTest,
> PRClientServerRegionFunctionExecutionSingleHopDUnitTest,
> PRClientServerRegionFunctionExecutionFailoverDUnitTest,
> ColocationFailoverDUnitTest,
[jira] [Updated] (GEODE-668) Improve logs for GMSHealthMonitor to help debugging
[ https://issues.apache.org/jira/browse/GEODE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-668: Fix Version/s: 1.0.0-alpha1 > Improve logs for GMSHealthMonitor to help debugging > --- > > Key: GEODE-668 > URL: https://issues.apache.org/jira/browse/GEODE-668 > Project: Geode > Issue Type: Improvement >Reporter: Jianxia Chen >Assignee: Jianxia Chen > Fix For: 1.0.0-alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-146) Queries are not thread safe due to scopeId variable
[
https://issues.apache.org/jira/browse/GEODE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-146:
Fix Version/s: 1.0.0-alpha1
> Queries are not thread safe due to scopeId variable
> ---
>
> Key: GEODE-146
> URL: https://issues.apache.org/jira/browse/GEODE-146
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
> Fix For: 1.0.0-alpha1
>
>
> Currently queries are not thread safe although they should be. This is due
> to the way the scopeId is stored in the CompiledSelect. The fix consists of
> storing the scopeId in the execution context.
> public void testThreadSafetyOfCompiledSelectScopeId() throws Exception {
> Cache cache = CacheUtils.getCache();
> RegionFactory rf = cache
> .createRegionFactory(RegionShortcut.PARTITION);
> Region r = rf.create("keyzset");
> for (int i = 0; i < 100; i++) {
> r.put(i, new Portfolio(i));
> }
> ScopeThreadingTestHook scopeIDTestHook = new ScopeThreadingTestHook(3);
> DefaultQuery.testHook = scopeIDTestHook;
> QueryService qs = cache.getQueryService();
> Query q = qs
> .newQuery("SELECT DISTINCT * FROM /keyzset.keySet key WHERE key.id >
> 0 AND key.id <= 0 ORDER BY key asc LIMIT $3");
> Thread q1 = new Thread(new QueryRunnable(q, new Object[] { 10, 20, 10 }));
> Thread q2 = new Thread(new QueryRunnable(q, new Object[] { 5, 10, 5 }));
> Thread q3 = new Thread(new QueryRunnable(q, new Object[] { 2, 10, 8 }));
> q1.start();
> q2.start();
> q3.start();
> q1.join();
> q2.join();
> q3.join();
> assertEquals("Exceptions were thrown due to DefaultQuery not being
> thread-safe", true, scopeIDTestHook.isOk());
> }
> private class QueryRunnable implements Runnable {
> private Query q;
> private Object[] params;
> public QueryRunnable(Query q, Object[] params) {
> this.q = q;
> this.params = params;
> }
> public void run() {
> try {
> q.execute(params);
> } catch (Exception e) {
> throw new TestException("exception occured while executing query", e);
> }
> }
> }
> public class ScopeThreadingTestHook implements DefaultQuery.TestHook {
> private CyclicBarrier barrier;
> private List exceptionsThrown = new LinkedList();
> public ScopeThreadingTestHook(int numThreads) {
> barrier = new CyclicBarrier(numThreads);
> }
> @Override
> public void doTestHook(int spot) {
> this.doTestHook(spot + "");
> }
> @Override
> public void doTestHook(String spot) {
> if (spot.equals("1")) {
> try {
> barrier.await(8, TimeUnit.SECONDS);
> } catch (InterruptedException e) {
> exceptionsThrown.add(e);
> Thread.currentThread().interrupt();
> } catch (Exception e) {
> exceptionsThrown.add(e);
> }
> }
> }
> public boolean isOk() {
> return exceptionsThrown.size() == 0;
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-542) Race in FunctionService.onMembers can result in hang during member startup
[
https://issues.apache.org/jira/browse/GEODE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-542:
Fix Version/s: 1.0.0-alpha1
> Race in FunctionService.onMembers can result in hang during member startup
> --
>
> Key: GEODE-542
> URL: https://issues.apache.org/jira/browse/GEODE-542
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-alpha1
>
>
> I hit this while doing some internal tests of FunctionService. I have a
> function that calls CacheFactory.getAnyInstance(). I was seeing that
> occasionally, my function would never see a reply while a member was starting
> up.
> Turning on debug logging, I found this is the logs
> {noformat}
> [fine 2015/10/28 17:15:41.903 PDT clientgemfire2_gluon_2055 Execution Processor2> tid=0x37] shutdown caught, abandoning message: A cache
> has not yet been created.
> com.gemstone.gemfire.cache.CacheClosedException: A cache has not yet been
> created.
> at
> com.gemstone.gemfire.cache.CacheFactory.getAnyInstance(CacheFactory.java:292)
> at
> com.gemstone.gemfire.internal.cache.execute.util.RollbackFunction.execute(RollbackFunction.java:82)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:701)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1158)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This seems wrong, because by not replying to the function the caller then can
> hang. I think this code was intended for use during shutdown, but it also
> gets hit during startup because members are available to process functions
> before the cache is created. That in itself is perhaps problematic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-90) IN SET Query using Index throws IllegalArgumentException
[
https://issues.apache.org/jira/browse/GEODE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-90:
---
Fix Version/s: 1.0.0-alpha1
> IN SET Query using Index throws IllegalArgumentException
>
>
> Key: GEODE-90
> URL: https://issues.apache.org/jira/browse/GEODE-90
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
> Fix For: 1.0.0-alpha1
>
>
> The following test will fail:
> public void testQueryRVMapMultipleEntries() throws Exception {
> Cache cache = CacheUtils.getCache();
> QueryService queryService = CacheUtils.getCache().getQueryService();
> CacheUtils.createRegion("TEST_REGION", null);
> queryService.createIndex("tr.nested.id.index", "nested.id",
> "/TEST_REGION, nested IN nested_values");
> Query queryInSet = queryService.newQuery("SELECT DISTINCT tr.id FROM
> /TEST_REGION tr, tr.nested_values nested WHERE nested.id IN SET ('1')");
> Query queryEquals = queryService.newQuery("SELECT DISTINCT tr.id FROM
> /TEST_REGION tr, nested IN nested_values WHERE nested.id='1'");
> Object[] nested = new Object[] {
> cache.createPdxInstanceFactory("nested_1").writeString("id",
> "1").create(),
> cache.createPdxInstanceFactory("nested_2").writeString("id",
> "1").create(),
> cache.createPdxInstanceFactory("nested_3").writeString("id",
> "1").create(),
> cache.createPdxInstanceFactory("nested_4").writeString("id",
> "4").create()
> };
> PdxInstance record =
> cache.createPdxInstanceFactory("root").writeString("id",
> "2").writeObjectArray("nested_values", nested).create();
> cache.getRegion("TEST_REGION").put("100", record);
> Index index =
> cache.getQueryService().getIndex(cache.getRegion("TEST_REGION"),
> "mdf.testRegion.nested.id");
> SelectResults queryResults = (SelectResults) queryEquals.execute();
> SelectResults inSetQueryResults = (SelectResults) queryInSet.execute();
> assertEquals(queryResults.size(), inSetQueryResults.size());
> assertTrue(inSetQueryResults.size() > 0);
> }
> AbstractIndex is adding the whole collection as an object into the result set
> instead of the individual object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-411) CI failure: ConnectDisconnectDUnitTest.testManyConnectsAndDisconnects
[ https://issues.apache.org/jira/browse/GEODE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-411: Fix Version/s: 1.0.0-alpha1 > CI failure: ConnectDisconnectDUnitTest.testManyConnectsAndDisconnects > - > > Key: GEODE-411 > URL: https://issues.apache.org/jira/browse/GEODE-411 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Assignee: Darrel Schneider > Labels: CI > Fix For: 1.0.0-alpha1 > > > Failed 4 times in the last 30 runs. Stability: 86 % > Error Message > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 14 > com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected. > --- > Found suspect string in log4j at line 27 > com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected. > Stacktrace > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 14 > com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected. > --- > Found suspect string in log4j at line 27 > com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected. > at org.junit.Assert.fail(Assert.java:88) > at > dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:307) > at dunit.DistributedTestCase.cleanupAllVms(DistributedTestCase.java:784) > at dunit.DistributedTestCase.realTearDown(DistributedTestCase.java:759) > at dunit.DistributedTestCase.tearDown(DistributedTestCase.java:737) > at > com.gemstone.gemfire.internal.cache.ConnectDisconnectDUnitTest.testManyConnectsAndDisconnects(ConnectDisconnectDUnitTest.java:75) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-598) CI Failure: ReconnectDUnitTest.testReconnectALocator
[
https://issues.apache.org/jira/browse/GEODE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-598:
Fix Version/s: 1.0.0-alpha1
> CI Failure: ReconnectDUnitTest.testReconnectALocator
>
>
> Key: GEODE-598
> URL: https://issues.apache.org/jira/browse/GEODE-598
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> Revision 25c8f0cc48e831d6afb459767a42c1c98fb47996
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.ReconnectDUnitTest$23.call in VM 0 running on
> Host cc2-rh6.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM.invoke(VM.java:312)
> at dunit.VM.invoke(VM.java:280)
> at
> com.gemstone.gemfire.cache30.ReconnectDUnitTest.forceDisconnect(ReconnectDUnitTest.java:1090)
> at
> com.gemstone.gemfire.cache30.ReconnectDUnitTest.testReconnectALocator(ReconnectDUnitTest.java:510)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: Event never occurred after
> 1 ms: waiting for locator to stop: Distribution Locator on cc2-rh6[22868]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1127)
> at
> com.gemstone.gemfire.cache30.ReconnectDUnitTest$23.call(ReconnectDUnitTest.java:1108)
> at
[jira] [Updated] (GEODE-87) ServerLauncherWithSpringJUnitTest fails checkMissedTests due to missing junit category
[ https://issues.apache.org/jira/browse/GEODE-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-87: --- Fix Version/s: 1.0.0-alpha1 > ServerLauncherWithSpringJUnitTest fails checkMissedTests due to missing junit > category > -- > > Key: GEODE-87 > URL: https://issues.apache.org/jira/browse/GEODE-87 > Project: Geode > Issue Type: Bug >Reporter: Kirk Lund >Assignee: Kirk Lund > Fix For: 1.0.0-alpha1 > > > The build targets rely on a junit category being specified. This test needs > to be annotated with "@Category(IntegrationTest.class)". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-40) Update Jenkins Nightly Build To Build From Develop
[ https://issues.apache.org/jira/browse/GEODE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-40: --- Fix Version/s: 1.0.0-alpha1 > Update Jenkins Nightly Build To Build From Develop > --- > > Key: GEODE-40 > URL: https://issues.apache.org/jira/browse/GEODE-40 > Project: Geode > Issue Type: Task > Environment: Jenkins, builds.apache.org >Reporter: Mark Bretl >Assignee: Mark Bretl > Fix For: 1.0.0-alpha1 > > Original Estimate: 1h > Remaining Estimate: 1h > > Currently, the nightly build uses the master branch to build from. The > community would like to use develop as that is where new development will be > done. Task is to change the job to build from develop, instead of master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-148) Many expiration unit tests take too long to run
[ https://issues.apache.org/jira/browse/GEODE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-148: Fix Version/s: 1.0.0-alpha1 > Many expiration unit tests take too long to run > --- > > Key: GEODE-148 > URL: https://issues.apache.org/jira/browse/GEODE-148 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Minor > Fix For: 1.0.0-alpha1 > > > Some examples are: > - MultiVMRegionTestCase.testUpdateResetsIdleTime > - RegionTestCase.testEntryIdleReset -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-307) Failure from SnapshotDUnitTest due to listener installed in a previous test
[
https://issues.apache.org/jira/browse/GEODE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-307:
Fix Version/s: 1.0.0-alpha1
> Failure from SnapshotDUnitTest due to listener installed in a previous test
> ---
>
> Key: GEODE-307
> URL: https://issues.apache.org/jira/browse/GEODE-307
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.testCacheExportFilterException
> {noformat}
> Stacktrace
> com.gemstone.gemfire.cache.DiskAccessException
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRVVRecoveryDUnitTest$3.afterWriteGCRVV(PersistentRVVRecoveryDUnitTest.java:206)
> at
> com.gemstone.gemfire.internal.cache.DiskStoreObserver.endWriteGCRVV(DiskStoreObserver.java:51)
> at com.gemstone.gemfire.internal.cache.Oplog.writeGCRVV(Oplog.java:4982)
> at
> com.gemstone.gemfire.internal.cache.DiskStoreImpl.writeRVVGC(DiskStoreImpl.java:4798)
> at
> com.gemstone.gemfire.internal.cache.DiskRegion.writeRVVGC(DiskRegion.java:841)
> at
> com.gemstone.gemfire.internal.cache.InitialImageOperation.saveReceivedRVV(InitialImageOperation.java:1140)
> at
> com.gemstone.gemfire.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:465)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1429)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1215)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3111)
> at
> com.gemstone.gemfire.pdx.internal.PeerTypeRegistration.initialize(PeerTypeRegistration.java:179)
> at
> com.gemstone.gemfire.pdx.internal.TypeRegistry.initialize(TypeRegistry.java:103)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initializePdxRegistry(GemFireCacheImpl.java:1354)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1292)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1131)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:758)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:778)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:170)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:217)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.createCache(CacheTestCase.java:105)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:315)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:290)
> at
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest$4.call(SnapshotDUnitTest.java:183)
> at
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.forEachVm(SnapshotDUnitTest.java:212)
> at
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.loadCache(SnapshotDUnitTest.java:200)
> at
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.setUp(SnapshotDUnitTest.java:156)
> at junit.framework.TestCase.runBare(TestCase.java:139)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor173.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
>
[jira] [Updated] (GEODE-97) Unit tests using jmock fail due to cglib/asm incompatibility with JDK 8
[
https://issues.apache.org/jira/browse/GEODE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-97:
---
Fix Version/s: 1.0.0-alpha1
> Unit tests using jmock fail due to cglib/asm incompatibility with JDK 8
> ---
>
> Key: GEODE-97
> URL: https://issues.apache.org/jira/browse/GEODE-97
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Assignee: Kirk Lund
> Fix For: 1.0.0-alpha1
>
>
> Several unit tests using jmock/cglib/asm fail when run using JDK 8:
> {code}
> com.gemstone.gemfire.internal.cache.DiskInitFileJUnitTest > testCanonicalIds
> FAILED
> java.lang.IllegalArgumentException
> at net.sf.cglib.asm.ClassReader.(Unknown Source)
> at net.sf.cglib.asm.ClassReader.(Unknown Source)
> at net.sf.cglib.asm.ClassReader.(Unknown Source)
> at
> net.sf.cglib.proxy.BridgeMethodResolver.resolveAll(BridgeMethodResolver.java:61)
> at net.sf.cglib.proxy.Enhancer.emitMethods(Enhancer.java:911)
> at net.sf.cglib.proxy.Enhancer.generateClass(Enhancer.java:498)
> at
> net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25)
> at
> net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:216)
> at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377)
> at net.sf.cglib.proxy.Enhancer.createClass(Enhancer.java:317)
> at
> org.jmock.lib.legacy.ClassImposteriser.proxyClass(ClassImposteriser.java:121)
> at
> org.jmock.lib.legacy.ClassImposteriser.imposterise(ClassImposteriser.java:66)
> at
> org.jmock.internal.ReturnDefaultValueAction.invoke(ReturnDefaultValueAction.java:82)
> at
> org.jmock.internal.InvocationExpectation.invoke(InvocationExpectation.java:165)
> at
> org.jmock.internal.InvocationDispatcher.dispatch(InvocationDispatcher.java:81)
> at org.jmock.Mockery.dispatch(Mockery.java:244)
> at org.jmock.Mockery.access$100(Mockery.java:29)
> at org.jmock.Mockery$MockObject.invoke(Mockery.java:284)
> at
> org.jmock.internal.InvocationDiverter.invoke(InvocationDiverter.java:27)
> at
> org.jmock.internal.FakeObjectMethods.invoke(FakeObjectMethods.java:38)
> at
> org.jmock.internal.SingleThreadedPolicy$1.invoke(SingleThreadedPolicy.java:21)
> at
> org.jmock.lib.legacy.ClassImposteriser$4.invoke(ClassImposteriser.java:136)
> at
> com.gemstone.gemfire.internal.cache.persistence.DiskRegionView$$EnhancerByCGLIB$$dc027cdd.getFlags()
> at
> com.gemstone.gemfire.internal.cache.DiskInitFile.writeRegionConfig(DiskInitFile.java:1796)
> at
> com.gemstone.gemfire.internal.cache.DiskInitFile.createRegion(DiskInitFile.java:2081)
> at
> com.gemstone.gemfire.internal.cache.DiskInitFileJUnitTest.testCanonicalIds(DiskInitFileJUnitTest.java:81)
> {code}
> The following dependencies change in gradle seems to fix the problem:
> {code}
> -testRuntime 'cglib:cglib-nodep:3.1'
> +testRuntime 'cglib:cglib:3.1'
> {code}
> The cglib-nodep jar has an "asm" package while the cglib jar does not. This
> causes the build to use asm 5.0.3 as defined in the dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-683) CI failure: PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecutionOnASingleBucket_byName
[
https://issues.apache.org/jira/browse/GEODE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-683:
Fix Version/s: 1.0.0-alpha1
> CI failure:
> PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecutionOnASingleBucket_byName
> ---
>
> Key: GEODE-683
> URL: https://issues.apache.org/jira/browse/GEODE-683
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-incubating
>Reporter: Jens Deppe
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> git rev fdec70bcd46c568637f0dad976f3778625858608 build #924
> {noformat}
> Error Message
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3356
> [fatal 2015/12/16 18:38:40.374 PST /0:0:0:0:0:0:0:0:25581 local port: 25581> tid=0x239a] Failed to send message
> path='/_gfe_non_durable_client_with_id_cc8-rh64(4402:loner):40609:b5bbcdad_1_queue';
> sender=cc8-rh64(4365):1025; callbackArg=null; processorId=35400;
> op=REGION_LOCAL_DESTROY; applied=false; directAck=false; posdup=false;
> hasDelta=false; hasOldValue=false; eventID=null; serialNum=4064;
> subregionSerialNumbers={}; notifyOfRegionDeparture=false)> to member
> view =
> View[cc8-rh64(4360:locator):1024|1047] members:
> [cc8-rh64(4360:locator):1024, cc8-rh64(4365):1025{lead},
> cc8-rh64(4384):1026, cc8-rh64(4389):1027]
> com.gemstone.gemfire.distributed.internal.direct.ShunnedMemberException:
> Member is being shunned: {0}
> at
> com.gemstone.gemfire.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:599)
> at
> com.gemstone.gemfire.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:374)
> at
> com.gemstone.gemfire.distributed.internal.direct.DirectChannel.send(DirectChannel.java:667)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1730)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1924)
> at
> com.gemstone.gemfire.distributed.internal.DistributionChannel.send(DistributionChannel.java:88)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.sendOutgoing(DistributionManager.java:3474)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.sendMessage(DistributionManager.java:3515)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.putOutgoing(DistributionManager.java:1874)
> at
> com.gemstone.gemfire.internal.cache.DistributedCacheOperation.distribute(DistributedCacheOperation.java:529)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.distributeDestroyRegion(DistributedRegion.java:1957)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.basicDestroyRegion(DistributedRegion.java:1932)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicDestroyRegion(LocalRegion.java:6825)
> at
> com.gemstone.gemfire.internal.cache.HARegion.destroyRegion(HARegion.java:347)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.destroyRegion(AbstractRegion.java:376)
> at
> com.gemstone.gemfire.internal.cache.ha.HARegionQueue.destroy(HARegionQueue.java:3733)
> at
> com.gemstone.gemfire.internal.cache.ha.HARegionQueue$BlockingHARegionQueue.destroy(HARegionQueue.java:2392)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.destroyRQ(CacheClientProxy.java:1065)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.terminateDispatching(CacheClientProxy.java:973)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.close(CacheClientProxy.java:850)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.closeDeadProxies(CacheClientNotifier.java:1977)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.unregisterClient(CacheClientNotifier.java:785)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ClientHealthMonitor.unregisterClient(ClientHealthMonitor.java:275)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.handleTermination(ServerConnection.java:906)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.handleTermination(ServerConnection.java:827)
> at
>
[jira] [Updated] (GEODE-358) ClientServerFunctionExecutionDUnitTest.testOnServerFailoverWithTwoServerDownHA fails intermittently with suspect string
[
https://issues.apache.org/jira/browse/GEODE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-358:
Fix Version/s: 1.0.0-alpha1
> ClientServerFunctionExecutionDUnitTest.testOnServerFailoverWithTwoServerDownHA
> fails intermittently with suspect string
> ---
>
> Key: GEODE-358
> URL: https://issues.apache.org/jira/browse/GEODE-358
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Darrel Schneider
>Assignee: Sai Boorlagadda
>Priority: Minor
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> Seen on a private build using git rev:
> 4708d4e182f89c6a391fcad8bac854f929717685
> {code}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 3063
> java.net.SocketException: Connection reset by peer
> {code}
> The logs containing the suspect string:
> {code}
> [vm_0][info 2015/09/21 00:24:53.238 PDT Connection(30)-10.118.33.102> tid=0x3988] Bridge server on port 26,030 is
> shutting down.
> [vm_0]
> [vm_3][info 2015/09/21 00:24:53.240 PDT doomtwo(989):4546 port 26030> tid=0x1268] Cache client updater for
> Queue on endpoint doomtwo.gemstone.com:26030 exiting. Scheduling recovery.
> [vm_3]
> [vm_3][warn 2015/09/21 00:24:53.240 PDT
> tid=0x1261] Pool unexpected
> closed socket on server
> connection=SubscriptionConnectionImpl[doomtwo.gemstone.com:26030:closed]).
> Server unreachable: could not connect after 1 attempts
> [vm_3]
> [vm_3][warn 2015/09/21 00:24:53.240 PDT
> tid=0x1269] Could not
> connect to: doomtwo.gemstone.com:26030
> [vm_3]java.net.SocketException: Connection reset by peer
> [vm_3]at java.net.PlainSocketImpl.socketConnect(Native Method)
> [vm_3]at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
> [vm_3]at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> [vm_3]at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> [vm_3]at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> [vm_3]at java.net.Socket.connect(Socket.java:589)
> [vm_3]at
> com.gemstone.gemfire.internal.SocketUtils.connect(SocketUtils.java:85)
> [vm_3]at
> com.gemstone.gemfire.internal.SocketUtils.connect(SocketUtils.java:57)
> [vm_3]at
> com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:1013)
> [vm_3]at
> com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:948)
> [vm_3]at
> com.gemstone.gemfire.internal.SocketCreator.connectForClient(SocketCreator.java:917)
> [vm_3]at
> com.gemstone.gemfire.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:113)
> [vm_3]at
> com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:117)
> [vm_3]at
> com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.createNewPrimary(QueueManagerImpl.java:785)
> [vm_3]at
> com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.recoverPrimary(QueueManagerImpl.java:903)
> [vm_3]at
> com.gemstone.gemfire.cache.client.internal.QueueManagerImpl$RedundancySatisfierTask.run2(QueueManagerImpl.java:1428)
> [vm_3]at
> com.gemstone.gemfire.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1250)
> [vm_3]at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [vm_3]at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [vm_3]at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [vm_3]at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [vm_3]at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [vm_3]at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [vm_3]at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-617) Change lucene xsd namespace to geode.apache.org
[ https://issues.apache.org/jira/browse/GEODE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-617: Fix Version/s: 1.0.0-alpha1 > Change lucene xsd namespace to geode.apache.org > --- > > Key: GEODE-617 > URL: https://issues.apache.org/jira/browse/GEODE-617 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-alpha1 > > > The current namespace for the geode lucene integration is > geode.incubator.apache.org. Based on discussions on GEODE-386, this should be > geode.apache.org. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-329) Failure from ShutdownAllDUnitTest.testShutdownAllWithEncounterIGE2
[ https://issues.apache.org/jira/browse/GEODE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-329: Fix Version/s: 1.0.0-alpha1 > Failure from ShutdownAllDUnitTest.testShutdownAllWithEncounterIGE2 > -- > > Key: GEODE-329 > URL: https://issues.apache.org/jira/browse/GEODE-329 > Project: Geode > Issue Type: Bug >Reporter: Jason Huynh >Assignee: xiaojian zhou > Labels: CI > Fix For: 1.0.0-alpha1 > > > dunit.RMIException: While invoking > com.gemstone.gemfire.cache30.CacheTestCase$4.run in VM 0 running on Host > asf905.gq1.ygridcore.net with 4 VMs > at dunit.VM.invoke(VM.java:359) > at dunit.VM.invoke(VM.java:303) > at dunit.VM.invoke(VM.java:257) > at > com.gemstone.gemfire.internal.cache.partitioned.ShutdownAllDUnitTest.testShutdownAllWithEncounterIGE2(ShutdownAllDUnitTest.java:191) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106) > at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at > org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.gemstone.gemfire.InternalGemFireError > at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:84) > at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:48) > at > com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1588) > at dunit.DistributedTestCase.getSystem(DistributedTestCase.java:481) > at dunit.DistributedTestCase.getSystem(DistributedTestCase.java:594) > at > com.gemstone.gemfire.cache30.CacheTestCase.createCache(CacheTestCase.java:99) > at > com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:315) > at >
[jira] [Updated] (GEODE-581) Load probe that only considers the size of buckets
[ https://issues.apache.org/jira/browse/GEODE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-581: Fix Version/s: 1.0.0-alpha1 > Load probe that only considers the size of buckets > -- > > Key: GEODE-581 > URL: https://issues.apache.org/jira/browse/GEODE-581 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-alpha1 > > > The default implementation of LoadProbe used for rebalancing returns the size > in bytes of each bucket. > For some use cases, there is a need to ignore the size is bytes of the bucket > and balance based on the number of buckets on each server instead. > Geode should provide a load probe that returns only the number of buckets on > each server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-452) CI failure: Bug37210DUnitTest.testHAStatsCleanup
[ https://issues.apache.org/jira/browse/GEODE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-452: Fix Version/s: 1.0.0-alpha1 > CI failure: Bug37210DUnitTest.testHAStatsCleanup > > > Key: GEODE-452 > URL: https://issues.apache.org/jira/browse/GEODE-452 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Hitesh Khamesra > Labels: CI > Fix For: 1.0.0-alpha1 > > > at > com.gemstone.gemfire.internal.cache.tier.sockets.Bug37210DUnitTest.testHAStatsCleanup(Bug37210DUnitTest.java:145) > Caused by: junit.framework.AssertionFailedError: > HARegionQueue.dispatchedMessagesMap contains entry for the region even after > proxy.close() > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertFalse(Assert.java:39) > at junit.framework.TestCase.assertFalse(TestCase.java:210) > at > com.gemstone.gemfire.internal.cache.tier.sockets.Bug37210DUnitTest.closeCacheClientProxyAndVerifyStats(Bug37210DUnitTest.java:244) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-138) MemoryThresholdsOffHeapDUnitTest.testEventDelivery failed
[
https://issues.apache.org/jira/browse/GEODE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-138:
Fix Version/s: 1.0.0-alpha1
> MemoryThresholdsOffHeapDUnitTest.testEventDelivery failed
> --
>
> Key: GEODE-138
> URL: https://issues.apache.org/jira/browse/GEODE-138
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Minor
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> This end-to-end test failed in Jenkins in build #159. Need to tighten up any
> race conditions and make this test more reliable.
> {code}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest$46.call
> in VM 1 running on Host asf911.gq1.ygridcore.net 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.cache.management.MemoryThresholdsOffHeapDUnitTest.verifyListenerValue(MemoryThresholdsOffHeapDUnitTest.java:1568)
> at
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.testEventDelivery(MemoryThresholdsOffHeapDUnitTest.java:149)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:49)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: expected:<1> but was:<0>
> at junit.framework.Assert.fail(Assert.java:57)
> at
[jira] [Updated] (GEODE-144) Try-with-resources for Geode cache
[
https://issues.apache.org/jira/browse/GEODE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-144:
Fix Version/s: 1.0.0-alpha1
> Try-with-resources for Geode cache
> --
>
> Key: GEODE-144
> URL: https://issues.apache.org/jira/browse/GEODE-144
> Project: Geode
> Issue Type: Improvement
> Components: core
>Reporter: William Markito Oliveira
>Assignee: William Markito Oliveira
>Priority: Minor
> Fix For: 1.0.0-alpha1
>
>
> I'd like to propose implementing AutoClosable interface in order to allow
> Geode users to treat Cache as an AutoClosable resource.
> Most of old GemFire examples and Geode docs[1] as well include a very common
> practice as follows:
> {code}
> Cache cache = new CacheFactory().set("name", "nodeName")
> .set("log-level", "fine")
> .set("statistic-sampling-enabled", "true")...
> .create();
> // application code
> // Close the cache and disconnect
> System.out.println("Closing the cache and disconnecting.");
> cache.close();
> {code}
> The idea would be to avoid such closing calls when user think it's
> appropriate by using try-with-resources syntax:
> {code}
> try ( Cache cache = new CacheFactory().set("name", "nodeName").create() ) {
> // application code
> }
> {code}
> There would be no need to call cache.close() or use try/finally blocks.
> Please find in the link below more examples [3] of try-with-resources.
> [1]
> http://gemfire.docs.pivotal.io/latest/userguide/index.html#basic_config/the_cache/managing_a_client_cache.html
> [2] http://docs.oracle.com/javase/7/docs/api/java/lang/AutoCloseable.html
> [3]
> http://docs.oracle.com/javase/7/docs/technotes/guides/language/try-with-resources.html
> [4]
> http://gemfire.docs.pivotal.io/latest/javadocs/japi/com/gemstone/gemfire/cache/RegionService.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-320) Snapshot tests failing due to a cache left by a previous test
[
https://issues.apache.org/jira/browse/GEODE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-320:
Fix Version/s: 1.0.0-alpha1
> Snapshot tests failing due to a cache left by a previous test
> -
>
> Key: GEODE-320
> URL: https://issues.apache.org/jira/browse/GEODE-320
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-alpha1
>
>
> Several of the snapshot tests failed in the last nightly build. It looks like
> a previous test case left a cache running in some VMs. CacheTestCase would
> have cleaned this up, so it looks like this may be caused by a previous test
> that doesn't extend CacheTestCase and doesn't clean up after itself.
> {noformat}
> com.gemstone.gemfire.cache.snapshot.SnapshotByteArrayDUnitTest.testImportByteArray
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.testCacheExportFilterException
>
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.testCacheImportFilterException
> com.gemstone.gemfire.cache.snapshot.SnapshotDUnitTest.testExportAndImport
> com.gemstone.gemfire.cache.snapshot.SnapshotPerformanceDUnitTest.testPerformance
> {noformat}
> Sample failure:
> {noformat}
> java.lang.IllegalStateException: Cannot create region /PdxTypes DataPolicy
> withPersistence=true because another cache (asf903(25185):55958) has
> the same region DataPolicy withPersistence=false. Persistent members must be
> started before non-persistent members
> at
> com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.handleCacheDistributionAdvisee(CreateRegionProcessor.java:483)
> at
> com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.process(CreateRegionProcessor.java:378)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:371)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:442)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:692)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$5$1.run(DistributionManager.java:1000)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
