[jira] [Assigned] (GEODE-1934) Failure from RDDJoinRegionIntegrationTest

2016-09-23 Thread Dan Smith (JIRA)

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

Dan Smith reassigned GEODE-1934:


Assignee: Dan Smith

> Failure from RDDJoinRegionIntegrationTest
> -
>
> Key: GEODE-1934
> URL: https://issues.apache.org/jira/browse/GEODE-1934
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> This test is failing in the nightly build for the spark integration.
> It looks like the issue is that it's missing the StringUtils class, which is 
> part of spring core:
> {noformat}
> sbt.ForkMain$ForkError: org/springframework/util/StringUtils
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactory.configureSSLPropertiesFromSystemProperties(SSLConfigurationFactory.java:274)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactory.configureSSLPropertiesFromSystemProperties(SSLConfigurationFactory.java:270)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactory.createSSLConfigForComponent(SSLConfigurationFactory.java:138)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactory.getSSLConfigForComponent(SSLConfigurationFactory.java:67)
>   at 
> org.apache.geode.internal.net.SocketCreatorFactory.getSocketCreatorForComponent(SocketCreatorFactory.java:67)
>   at 
> org.apache.geode.distributed.internal.tcpserver.TcpClient.(TcpClient.java:69)
>   at 
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.(AutoConnectionSourceImpl.java:114)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.getSourceImpl(PoolImpl.java:579)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.(PoolImpl.java:219)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:132)
>   at 
> org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:319)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.determineDefaultPool(GemFireCacheImpl.java:2943)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1293)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1124)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:765)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createClient(GemFireCacheImpl.java:740)
>   at 
> org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:235)
>   at 
> org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:189)
>   at 
> org.apache.geode.spark.connector.internal.DefaultGeodeConnection.initClientCache(DefaultGeodeConnection.scala:52)
>   at 
> org.apache.geode.spark.connector.internal.DefaultGeodeConnection.(DefaultGeodeConnection.scala:43)
>   at 
> org.apache.geode.spark.connector.internal.DefaultGeodeConnectionFactory.newConnection(DefaultGeodeConnection.scala:162)
>   at 
> org.apache.geode.spark.connector.internal.DefaultGeodeConnectionManager$.getConnection(DefaultGeodeConnectionManager.scala:59)
>   at 
> org.apache.geode.spark.connector.internal.DefaultGeodeConnectionManager.getConnection(DefaultGeodeConnectionManager.scala:29)
>   at 
> org.apache.geode.spark.connector.GeodeConnectionConf.getConnection(GeodeConnectionConf.scala:39)
>   at 
> ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest.verifyPairRDDJoinRegionWithSameKeyType(RDDJoinRegionIntegrationTest.scala:89)
>   at 
> ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest$$anonfun$1.apply$mcV$sp(RDDJoinRegionIntegrationTest.scala:73)
>   at 
> ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest$$anonfun$1.apply(RDDJoinRegionIntegrationTest.scala:73)
>   at 
> ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest$$anonfun$1.apply(RDDJoinRegionIntegrationTest.scal
> {noformat}
> Looking at our pom.xml file for geode-core, this is not suprising because 
> spring-core is marked as an optional dependency. I think the dependencies of 
> geode-core are messed, either spring-core should not be marked optional or we 
> should not be depending on it. These are the places that are using 
> spring-core in geode-core:
> {noformat}
> ./gradlew geode-core:findUsage -Djar.name=spring-core
> Matches
> 
> org/apache/geode/management/internal/cli/shell/GfshExecutionStrategy.java
> org/apache/geode/management/internal/cli/converters/DirConverter.java
> org/apache/geode/management/internal/cli/util/CommentSkipHelper.java
> org/apache/geode/management/internal/cli/multistep/CLIMultiStepHelper.java
> org/apache/geode/management/internal/cli/remote/RemoteExecutionStrategy.java
> 

[jira] [Created] (GEODE-1934) Failure from RDDJoinRegionIntegrationTest

2016-09-23 Thread Dan Smith (JIRA)
Dan Smith created GEODE-1934:


 Summary: Failure from RDDJoinRegionIntegrationTest
 Key: GEODE-1934
 URL: https://issues.apache.org/jira/browse/GEODE-1934
 Project: Geode
  Issue Type: Bug
  Components: tests
Reporter: Dan Smith


This test is failing in the nightly build for the spark integration.

It looks like the issue is that it's missing the StringUtils class, which is 
part of spring core:
{noformat}
sbt.ForkMain$ForkError: org/springframework/util/StringUtils
at 
org.apache.geode.internal.net.SSLConfigurationFactory.configureSSLPropertiesFromSystemProperties(SSLConfigurationFactory.java:274)
at 
org.apache.geode.internal.net.SSLConfigurationFactory.configureSSLPropertiesFromSystemProperties(SSLConfigurationFactory.java:270)
at 
org.apache.geode.internal.net.SSLConfigurationFactory.createSSLConfigForComponent(SSLConfigurationFactory.java:138)
at 
org.apache.geode.internal.net.SSLConfigurationFactory.getSSLConfigForComponent(SSLConfigurationFactory.java:67)
at 
org.apache.geode.internal.net.SocketCreatorFactory.getSocketCreatorForComponent(SocketCreatorFactory.java:67)
at 
org.apache.geode.distributed.internal.tcpserver.TcpClient.(TcpClient.java:69)
at 
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.(AutoConnectionSourceImpl.java:114)
at 
org.apache.geode.cache.client.internal.PoolImpl.getSourceImpl(PoolImpl.java:579)
at 
org.apache.geode.cache.client.internal.PoolImpl.(PoolImpl.java:219)
at 
org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:132)
at 
org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:319)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.determineDefaultPool(GemFireCacheImpl.java:2943)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1293)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1124)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:765)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.createClient(GemFireCacheImpl.java:740)
at 
org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:235)
at 
org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:189)
at 
org.apache.geode.spark.connector.internal.DefaultGeodeConnection.initClientCache(DefaultGeodeConnection.scala:52)
at 
org.apache.geode.spark.connector.internal.DefaultGeodeConnection.(DefaultGeodeConnection.scala:43)
at 
org.apache.geode.spark.connector.internal.DefaultGeodeConnectionFactory.newConnection(DefaultGeodeConnection.scala:162)
at 
org.apache.geode.spark.connector.internal.DefaultGeodeConnectionManager$.getConnection(DefaultGeodeConnectionManager.scala:59)
at 
org.apache.geode.spark.connector.internal.DefaultGeodeConnectionManager.getConnection(DefaultGeodeConnectionManager.scala:29)
at 
org.apache.geode.spark.connector.GeodeConnectionConf.getConnection(GeodeConnectionConf.scala:39)
at 
ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest.verifyPairRDDJoinRegionWithSameKeyType(RDDJoinRegionIntegrationTest.scala:89)
at 
ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest$$anonfun$1.apply$mcV$sp(RDDJoinRegionIntegrationTest.scala:73)
at 
ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest$$anonfun$1.apply(RDDJoinRegionIntegrationTest.scala:73)
at 
ittest.org.apache.geode.spark.connector.RDDJoinRegionIntegrationTest$$anonfun$1.apply(RDDJoinRegionIntegrationTest.scal
{noformat}

Looking at our pom.xml file for geode-core, this is not suprising because 
spring-core is marked as an optional dependency. I think the dependencies of 
geode-core are messed, either spring-core should not be marked optional or we 
should not be depending on it. These are the places that are using spring-core 
in geode-core:

{noformat}
./gradlew geode-core:findUsage -Djar.name=spring-core

Matches

org/apache/geode/management/internal/cli/shell/GfshExecutionStrategy.java
org/apache/geode/management/internal/cli/converters/DirConverter.java
org/apache/geode/management/internal/cli/util/CommentSkipHelper.java
org/apache/geode/management/internal/cli/multistep/CLIMultiStepHelper.java
org/apache/geode/management/internal/cli/remote/RemoteExecutionStrategy.java
org/apache/geode/management/internal/cli/parser/GfshMethodTarget.java
org/apache/geode/management/internal/configuration/domain/XmlEntity.java
org/apache/geode/management/internal/web/util/ConvertUtils.java
org/apache/geode/management/internal/web/io/MultipartFileResourceAdapter.java

[jira] [Commented] (GEODE-1922) CI Failure: RegionCreateDestroyDUnitTest.testCreateDestroyValidRegion

2016-09-23 Thread Eric Shu (JIRA)

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

Eric Shu commented on GEODE-1922:
-

Following tests also fail with the same issue:
org.apache.geode.management.RegionCreateDestroyDUnitTest.testCreateInvalidRegion
and
org.apache.geode.management.internal.configuration.SharedConfigurationDUnitTest.testGetHostedLocatorsWithSharedConfiguration

> CI Failure: RegionCreateDestroyDUnitTest.testCreateDestroyValidRegion
> -
>
> Key: GEODE-1922
> URL: https://issues.apache.org/jira/browse/GEODE-1922
> Project: Geode
>  Issue Type: Bug
>  Components: jmx
>Reporter: Eric Shu
>  Labels: ci
>
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 84
> [fatal 2016/09/16 04:18:58.969 PDT  tid=0x191] 
> (tid=401 msgId=44) No longer connected to cc6-co6.gemstone.com[24253].
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.geode.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:358)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:545)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:493)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDown(JUnit4DistributedTestCase.java:482)
>   at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.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:109)
>   at sun.reflect.GeneratedMethodAccessor176.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> 

[jira] [Updated] (GEODE-1931) CI Failure: LocatorUDPSecurityDUnitTest.testStartTwoLocators

2016-09-23 Thread Eric Shu (JIRA)

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

Eric Shu updated GEODE-1931:

Labels: ci  (was: )

> CI Failure: LocatorUDPSecurityDUnitTest.testStartTwoLocators
> 
>
> Key: GEODE-1931
> URL: https://issues.apache.org/jira/browse/GEODE-1931
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Eric Shu
>  Labels: ci
>
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedCallable.call in VM 2 running on Host 
> cc2-rh6.gemstone.com with 5 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
>   at 
> org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:307)
>   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.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:109)
>   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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
>   at 
> 

[jira] [Updated] (GEODE-1932) CI Failure: ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException

2016-09-23 Thread Eric Shu (JIRA)

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

Eric Shu updated GEODE-1932:

Labels: ci  (was: )

> CI Failure: 
> ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException
> --
>
> Key: GEODE-1932
> URL: https://issues.apache.org/jira/browse/GEODE-1932
> Project: Geode
>  Issue Type: Bug
>  Components: functions
>Reporter: Eric Shu
>  Labels: ci
>
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest$$Lambda$310/689837786.run
>  in VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
>   at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException(ClientServerFunctionExecutionDUnitTest.java:393)
>   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.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:109)
>   at sun.reflect.GeneratedMethodAccessor386.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> 

[jira] [Updated] (GEODE-1933) CI Failure: ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy

2016-09-23 Thread Eric Shu (JIRA)

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

Eric Shu updated GEODE-1933:

Labels: ci  (was: )

> CI Failure: 
> ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy
> 
>
> Key: GEODE-1933
> URL: https://issues.apache.org/jira/browse/GEODE-1933
> Project: Geode
>  Issue Type: Bug
>  Components: transactions
>Reporter: Eric Shu
>  Labels: ci
>
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.ClientServerTransactionDUnitTest$70.call in 
> VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
>   at 
> org.apache.geode.internal.cache.ClientServerTransactionDUnitTest.doFailoverWork(ClientServerTransactionDUnitTest.java:1910)
>   at 
> org.apache.geode.internal.cache.ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy(ClientServerTransactionDUnitTest.java:1835)
>   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.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:109)
>   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 
> 

[jira] [Created] (GEODE-1933) CI Failure: ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy

2016-09-23 Thread Eric Shu (JIRA)
Eric Shu created GEODE-1933:
---

 Summary: CI Failure: 
ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy
 Key: GEODE-1933
 URL: https://issues.apache.org/jira/browse/GEODE-1933
 Project: Geode
  Issue Type: Bug
  Components: transactions
Reporter: Eric Shu


org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.internal.cache.ClientServerTransactionDUnitTest$70.call in VM 
3 running on Host cc4-rh6.gemstone.com with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
at 
org.apache.geode.internal.cache.ClientServerTransactionDUnitTest.doFailoverWork(ClientServerTransactionDUnitTest.java:1910)
at 
org.apache.geode.internal.cache.ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy(ClientServerTransactionDUnitTest.java:1835)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.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:109)
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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
at 

[jira] [Created] (GEODE-1932) CI Failure: ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException

2016-09-23 Thread Eric Shu (JIRA)
Eric Shu created GEODE-1932:
---

 Summary: CI Failure: 
ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException
 Key: GEODE-1932
 URL: https://issues.apache.org/jira/browse/GEODE-1932
 Project: Geode
  Issue Type: Bug
  Components: functions
Reporter: Eric Shu


org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest$$Lambda$310/689837786.run
 in VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
at 
org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.testOnServerExecution_FunctionInvocationTargetException(ClientServerFunctionExecutionDUnitTest.java:393)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.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:109)
at sun.reflect.GeneratedMethodAccessor386.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
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)

[jira] [Created] (GEODE-1931) CI Failure: LocatorUDPSecurityDUnitTest.testStartTwoLocators

2016-09-23 Thread Eric Shu (JIRA)
Eric Shu created GEODE-1931:
---

 Summary: CI Failure: 
LocatorUDPSecurityDUnitTest.testStartTwoLocators
 Key: GEODE-1931
 URL: https://issues.apache.org/jira/browse/GEODE-1931
 Project: Geode
  Issue Type: Bug
  Components: membership
Reporter: Eric Shu


org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.test.dunit.NamedCallable.call in VM 2 running on Host 
cc2-rh6.gemstone.com with 5 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
at 
org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:307)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.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:109)
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.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
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 

[jira] [Created] (GEODE-1930) JMX DistributedTests are in need of overhauling

2016-09-23 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-1930:


 Summary: JMX DistributedTests are in need of overhauling
 Key: GEODE-1930
 URL: https://issues.apache.org/jira/browse/GEODE-1930
 Project: Geode
  Issue Type: Improvement
  Components: management
Reporter: Kirk Lund


In particular the DistributedTests that extend ManagementTestBase are really 
lacking. Most of these have system outs instead of assertions, broken 
AsyncInvocations and a host of other problems.

Before working on anything in JMX or GFSH, these tests should be fixed up so 
that keeping them green actually means something.




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


[jira] [Assigned] (GEODE-1930) JMX DistributedTests are in need of overhauling

2016-09-23 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-1930:


Assignee: Kirk Lund

> JMX DistributedTests are in need of overhauling
> ---
>
> Key: GEODE-1930
> URL: https://issues.apache.org/jira/browse/GEODE-1930
> Project: Geode
>  Issue Type: Improvement
>  Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> In particular the DistributedTests that extend ManagementTestBase are really 
> lacking. Most of these have system outs instead of assertions, broken 
> AsyncInvocations and a host of other problems.
> Before working on anything in JMX or GFSH, these tests should be fixed up so 
> that keeping them green actually means something.



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


[jira] [Updated] (GEODE-1929) Specifying ORDER BY in a OQL Query should not require the SELECT to be DISTINCT

2016-09-23 Thread John Blum (JIRA)

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

John Blum updated GEODE-1929:
-
Description: 
Currently, when a user writes a sorted OQL query, the user would specify an 
{{ORDER BY}} clause indicating which object properties to sort on along with 
the direction of the sort.  Additionally, for some non-apparent reason, Geode 
also requires the result of the query to be unique (a.k.a. {{DISTINCT}}).

Therefore, the following query would be considered invalid by Geode...

{code:sql}
SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
p.birthDate DESC
{code}

To correct this query, a user much specify the {{DISTINCT}} OQL keyword...

{code:sql}
SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
ASC, p.birthDate DESC
{code}

However, sorting has nothing to do with uniqueness as it is still possible to 
sort results even when they contain duplicates.

This seems to be a technical limitation in Geode rather than an apparent 
limitation of data grid technology, which has be inappropriately exposed to the 
end user.

  was:
Currently, when a user writes a sorted OQL query, the user would specify an 
{{ORDER BY}} clause indicating which object properties to sort on along with 
the direction of the sort.  Additionally, for some non-apparent reason, Geode 
also requires the result of the query to be unique (a.k.a. {{DISTINCT}}).

Therefore, the following query would considered to be invalid by Geode...

{code:sql}
SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
p.birthDate DESC
{code}

To correct this query, a user much specify the {{DISTINCT}} OQL keyword...

{code:sql}
SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
ASC, p.birthDate DESC
{code}

However, sorting has nothing to do with uniqueness as it is still possible to 
sort results even when they contain duplicates.

This seems to be a technical limitation in Geode rather than an apparent 
limitation of data grid technology, which has be inappropriately exposed to the 
end user.


> Specifying ORDER BY in a OQL Query should not require the SELECT to be 
> DISTINCT
> ---
>
> Key: GEODE-1929
> URL: https://issues.apache.org/jira/browse/GEODE-1929
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: John Blum
>
> Currently, when a user writes a sorted OQL query, the user would specify an 
> {{ORDER BY}} clause indicating which object properties to sort on along with 
> the direction of the sort.  Additionally, for some non-apparent reason, Geode 
> also requires the result of the query to be unique (a.k.a. {{DISTINCT}}).
> Therefore, the following query would be considered invalid by Geode...
> {code:sql}
> SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
> p.birthDate DESC
> {code}
> To correct this query, a user much specify the {{DISTINCT}} OQL keyword...
> {code:sql}
> SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
> ASC, p.birthDate DESC
> {code}
> However, sorting has nothing to do with uniqueness as it is still possible to 
> sort results even when they contain duplicates.
> This seems to be a technical limitation in Geode rather than an apparent 
> limitation of data grid technology, which has be inappropriately exposed to 
> the end user.



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


[jira] [Updated] (GEODE-1929) Specifying ORDER BY in a OQL Query should not require the SELECT to be DISTINCT

2016-09-23 Thread John Blum (JIRA)

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

John Blum updated GEODE-1929:
-
Description: 
Currently, when a user writes a sorted OQL query, the user would specify an 
{{ORDER BY}} clause indicating which object properties to sort on along with 
the direction of the sort.  Additionally, for some non-apparent reason, Geode 
also requires the result of the query to be unique (a.k.a. {{DISTINCT}}).

Therefore, the following query would considered to be invalid by Geode...

{code:sql}
SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
p.birthDate DESC
{code}

To correct this query, a user much specify the {{DISTINCT}} OQL keyword...

{code:sql}
SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
ASC, p.birthDate DESC
{code}

However, sorting has nothing to do with uniqueness as it is still possible to 
sort results even when they contain duplicates.

This seems to be a technical limitation in Geode rather than an apparent 
limitation of data grid technology, which has be inappropriately exposed to the 
end user.

  was:
Currently, when a user writes a sorted OQL query, the user would specify an 
{{ORDER BY}} clause indicating which object properties to sort on along with 
the direction of the sort.  Additionally, for some non-apparent reason, Geode 
also requires the result of the query to be unique (a.k.a. DISTINCT).

Therefore, the following query would considered to be invalid by Geode...

{code:sql}
SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
p.birthDate DESC
{code}

To correct this query, a user much specify the {{DISTINCT}} OQL keyword...

{code:sql}
SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
ASC, p.birthDate DESC
{code}

However, sorting has nothing to do with uniqueness as it is still possible to 
sort results even when they contain duplicates.

This seems to be a technical limitation in Geode rather than an apparent 
limitation of data grid technology, which has be inappropriately exposed to the 
end user.


> Specifying ORDER BY in a OQL Query should not require the SELECT to be 
> DISTINCT
> ---
>
> Key: GEODE-1929
> URL: https://issues.apache.org/jira/browse/GEODE-1929
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: John Blum
>
> Currently, when a user writes a sorted OQL query, the user would specify an 
> {{ORDER BY}} clause indicating which object properties to sort on along with 
> the direction of the sort.  Additionally, for some non-apparent reason, Geode 
> also requires the result of the query to be unique (a.k.a. {{DISTINCT}}).
> Therefore, the following query would considered to be invalid by Geode...
> {code:sql}
> SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
> p.birthDate DESC
> {code}
> To correct this query, a user much specify the {{DISTINCT}} OQL keyword...
> {code:sql}
> SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
> ASC, p.birthDate DESC
> {code}
> However, sorting has nothing to do with uniqueness as it is still possible to 
> sort results even when they contain duplicates.
> This seems to be a technical limitation in Geode rather than an apparent 
> limitation of data grid technology, which has be inappropriately exposed to 
> the end user.



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


[jira] [Created] (GEODE-1929) Specifying ORDER BY in a OQL Query should not require the SELECT to be DISTINCT

2016-09-23 Thread John Blum (JIRA)
John Blum created GEODE-1929:


 Summary: Specifying ORDER BY in a OQL Query should not require the 
SELECT to be DISTINCT
 Key: GEODE-1929
 URL: https://issues.apache.org/jira/browse/GEODE-1929
 Project: Geode
  Issue Type: Bug
  Components: querying
Reporter: John Blum


Currently, when a user writes a sorted OQL query, the user would specify an 
{{ORDER BY}} clause indicating which object properties to sort on along with 
the direction of the sort.  Additionally, for some non-apparent reason, Geode 
also requires the result of the query to be unique (a.k.a. DISTINCT).

Therefore, the following query would considered to be invalid by Geode...

{code:sql}
SELECT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname ASC, 
p.birthDate DESC
{code}

To correct this query, a user much specify the {{DISTINCT}} OQL keyword...

{code:sql}
SELECT DISTINCT * FROM /People p WHERE p.lastname = 'Doe' ORDER BY p.lastname 
ASC, p.birthDate DESC
{code}

However, sorting has nothing to do with uniqueness as it is still possible to 
sort results even when they contain duplicates.

This seems to be a technical limitation in Geode rather than an apparent 
limitation of data grid technology, which has be inappropriately exposed to the 
end user.



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


[jira] [Commented] (GEODE-1894) SerialGatewaySenderOperationsDUnitTest test hangs

2016-09-23 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-1894:


Commit a1938b386f1ed9064529df7f4206af913d4461c2 in incubator-geode's branch 
refs/heads/develop from zhouxh
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=a1938b3 ]

GEODE-1894: there's a race that AckReader thred is reading for ack
(hold the read lock), while stopping sender thread tried to hold the
write lock.


> SerialGatewaySenderOperationsDUnitTest test hangs
> -
>
> Key: GEODE-1894
> URL: https://issues.apache.org/jira/browse/GEODE-1894
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Hitesh Khamesra
> Attachments: threaddump.txt
>
>
> test tries to stop Serial Gateway Sender and that thread just hangs. Event 
> processors are waiting to become primary. One AckReader thread waiting for 
> ack. Seems like need to interrupt these threads. Attached thread dump 



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


[jira] [Assigned] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility

2016-09-23 Thread Kevin Duling (JIRA)

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

Kevin Duling reassigned GEODE-1902:
---

Assignee: Kevin Duling

> Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards 
> compatibility
> ---
>
> Key: GEODE-1902
> URL: https://issues.apache.org/jira/browse/GEODE-1902
> Project: Geode
>  Issue Type: Improvement
>  Components: logging
>Reporter: Kirk Lund
>Assignee: Kevin Duling
>
> If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they 
> either need to change this to GEODE_VERBOSE or we need to add some sort of 
> alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE.



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