[jira] [Updated] (GEODE-919) Remove checksums from .asc files (asc.md5, asc.sha1)
[ https://issues.apache.org/jira/browse/GEODE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-919: Fix Version/s: (was: 1.0.0-incubating.M2) 1.0.0-incubating.M3 > Remove checksums from .asc files (asc.md5, asc.sha1) > > > Key: GEODE-919 > URL: https://issues.apache.org/jira/browse/GEODE-919 > Project: Geode > Issue Type: Sub-task > Components: build >Reporter: Dan Smith > Fix For: 1.0.0-incubating.M3 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-823) RC Feedback: Fix build artifacts
[
https://issues.apache.org/jira/browse/GEODE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-823:
Fix Version/s: (was: 1.0.0-incubating.M2)
1.0.0-incubating.M3
> RC Feedback: Fix build artifacts
>
>
> Key: GEODE-823
> URL: https://issues.apache.org/jira/browse/GEODE-823
> Project: Geode
> Issue Type: Task
> Components: build
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
> Fix For: 1.0.0-incubating.M3
>
>
> From [~niall.pember...@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR
> SEPARATE ISSUES:
> * The ASF frowns upon distributing other open source projects without their
> consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns
> * Also not re-packaging it means users could face a dependency issue if they
> also use joptsimple
> * Lastly, "gemfire-joptsimple" could violate someone elses mark
> More specific feedback:
> * pom dependencies look like an issue - see GEODE-818
> * It would be better if the maven artifacts were named "geode" rather than
> "gemfire"
> * pom files don't have the license header
> * The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to
> not create this maven artifact
> * The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1072) Move HDFS code to it's own subproject and get rid of HDFS dependencies in gemfire-core
[ https://issues.apache.org/jira/browse/GEODE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1072: - Description: Based on these discussions on the mailing list, we should remove the HDFS code from the core, as well has setCustomEvictionAttributes and EvictionCriteria from the public API: http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201603.mbox/%3CCAFh%2B7k0bryRbXpCZKmk5PYn4GaqrYgE-wrEQoc36OO5NaAczvA%40mail.gmail.com%3E http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201603.mbox/%3CCAFh%2B7k2mDmKPHCoWyTqOCR3RvZv8F0MLjQgdx_j3FNn8y5yAOg%40mail.gmail.com%3E That code should added back on a feature branch. In addition the public API for HDFS which was removed as part of GEODE-429 will be added back to that feature branch. That's probably just a matter of reverting the commits listed in GEODE-429. was:SequenceFile pulls in commons-logging, there may be other. > Move HDFS code to it's own subproject and get rid of HDFS dependencies in > gemfire-core > -- > > Key: GEODE-1072 > URL: https://issues.apache.org/jira/browse/GEODE-1072 > Project: Geode > Issue Type: Sub-task > Components: hdfs >Reporter: Dan Smith >Assignee: Dan Smith > > Based on these discussions on the mailing list, we should remove the HDFS > code from the core, as well has setCustomEvictionAttributes and > EvictionCriteria from the public API: > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201603.mbox/%3CCAFh%2B7k0bryRbXpCZKmk5PYn4GaqrYgE-wrEQoc36OO5NaAczvA%40mail.gmail.com%3E > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201603.mbox/%3CCAFh%2B7k2mDmKPHCoWyTqOCR3RvZv8F0MLjQgdx_j3FNn8y5yAOg%40mail.gmail.com%3E > That code should added back on a feature branch. In addition the public API > for HDFS which was removed as part of GEODE-429 will be added back to that > feature branch. That's probably just a matter of reverting the commits listed > in GEODE-429. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-96) CI failure: MemoryThresholdsOffHeapDUnitTest.testDistributedRegionClientPutRejection
[
https://issues.apache.org/jira/browse/GEODE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-96:
---
Fix Version/s: (was: 1.0.0-incubating.M1)
1.0.0-incubating.M2
> CI failure:
> MemoryThresholdsOffHeapDUnitTest.testDistributedRegionClientPutRejection
>
>
> Key: GEODE-96
> URL: https://issues.apache.org/jira/browse/GEODE-96
> Project: Geode
> Issue Type: Bug
> Components: client/server, core
>Reporter: Dan Smith
>Assignee: Darrel Schneider
>Priority: Minor
> Labels: CI
> Fix For: 1.0.0-incubating.M2
>
>
> This test failed in one of the nightly builds, but it passed in others and
> passed when I ran it by itself. This test may have a race condition.
> https://builds.apache.org/view/All/job/Geode-nightly/123/testReport/junit/com.gemstone.gemfire.cache.management/MemoryThresholdsOffHeapDUnitTest/testDistributedRegionClientPutRejection/
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest$39.call
> in VM 1 running on Host hemera.apache.org 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.doPuts(MemoryThresholdsOffHeapDUnitTest.java:1311)
> at
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.doClientServerTest(MemoryThresholdsOffHeapDUnitTest.java:1423)
> at
> com.gemstone.gemfire.cache.management.MemoryThresholdsOffHeapDUnitTest.testDistributedRegionClientPutRejection(MemoryThresholdsOffHeapDUnitTest.java:1305)
> 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$Stopp
[jira] [Resolved] (GEODE-943) CI failure: SharedConfigurationEndToEndDUnitTest.testStartServerAndExecuteCommands
[
https://issues.apache.org/jira/browse/GEODE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-943.
-
Resolution: Fixed
I broke this test when changed the dependencies as part of GEODE-27. The
locator was having problems starting up. I fixed it with this revision:
4b9f6b4971078115f2de0735afd1661e36ea48a7.
> CI failure:
> SharedConfigurationEndToEndDUnitTest.testStartServerAndExecuteCommands
> --
>
> Key: GEODE-943
> URL: https://issues.apache.org/jira/browse/GEODE-943
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Sai Boorlagadda
>Assignee: Jens Deppe
> Labels: CI
>
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: expected: but was:
> Stacktrace
> junit.framework.AssertionFailedError: expected: but was:
> 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:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at
> com.gemstone.gemfire.management.internal.configuration.SharedConfigurationEndToEndDUnitTest.startServers(SharedConfigurationEndToEndDUnitTest.java:85)
> at
> com.gemstone.gemfire.management.internal.configuration.SharedConfigurationEndToEndDUnitTest.testStartServerAndExecuteCommands(SharedConfigurationEndToEndDUnitTest.java:103)
> 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.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(ThreadPoolExe
[jira] [Assigned] (GEODE-1079) Unavailable maven repositories listed in build.gradle
[ https://issues.apache.org/jira/browse/GEODE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1079: Assignee: Dan Smith > Unavailable maven repositories listed in build.gradle > - > > Key: GEODE-1079 > URL: https://issues.apache.org/jira/browse/GEODE-1079 > Project: Geode > Issue Type: Bug > Components: build >Reporter: nabarun >Assignee: Dan Smith > > In the build.gradle script the following repositories are unreachable > 1. https://plugins.gradle.org/m2/ > 2. http://dist.gemstone.com/maven/release > PS: These warning messages are shown when IntelliJ imports the project from > the gradle file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1079) Unavailable maven repositories listed in build.gradle
[ https://issues.apache.org/jira/browse/GEODE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207607#comment-15207607 ] Dan Smith commented on GEODE-1079: -- We should remove mavenLocal as well. -Dan > Unavailable maven repositories listed in build.gradle > - > > Key: GEODE-1079 > URL: https://issues.apache.org/jira/browse/GEODE-1079 > Project: Geode > Issue Type: Bug > Components: build >Reporter: nabarun >Assignee: Dan Smith > > In the build.gradle script the following repositories are unreachable > 1. https://plugins.gradle.org/m2/ > 2. http://dist.gemstone.com/maven/release > PS: These warning messages are shown when IntelliJ imports the project from > the gradle file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1108) CI failure: ParallelWANPropagationDUnitTest.testParallelPropagationWihtOverflow
[
https://issues.apache.org/jira/browse/GEODE-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207627#comment-15207627
]
Dan Smith commented on GEODE-1108:
--
I see this in the log messages. I think some previous test changed the maximum
message size and is now breaking other tests.
{noformat}
[vm_4][warn 2016/03/22 04:29:03.235 PDT tid=0xcd3] The following exception occurred attempting
to send a batch of 10 events. The batch will be tried again after reducing the
batch size to 5 events.
[vm_4]com.gemstone.gemfire.GemFireIOException: message is too large to transmit
[vm_4] at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:668)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:634)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:598)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:766)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.GatewaySenderBatchOp.executeOn(GatewaySenderBatchOp.java:64)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.SenderProxy.dispatchBatch_NewWAN(SenderProxy.java:36)
[vm_4] at
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventRemoteDispatcher._dispatchBatch(GatewaySenderEventRemoteDispatcher.java:220)
[vm_4] at
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventRemoteDispatcher.dispatchBatch(GatewaySenderEventRemoteDispatcher.java:154)
[vm_4] at
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:633)
[vm_4] at
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1078)
[vm_4]Caused by:
com.gemstone.gemfire.internal.cache.tier.sockets.MessageTooLargeException:
Message size (10487553) exceeds gemfire.client.max-message-size setting
(1048576)
[vm_4] at
com.gemstone.gemfire.internal.cache.tier.sockets.Message.sendBytes(Message.java:567)
[vm_4] at
com.gemstone.gemfire.internal.cache.tier.sockets.Message.send(Message.java:1089)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.GatewaySenderBatchOp$GatewaySenderGFEBatchOpImpl.sendMessage(GatewaySenderBatchOp.java:245)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.AbstractOp.attemptSend(AbstractOp.java:93)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.GatewaySenderBatchOp$GatewaySenderGFEBatchOpImpl.attempt(GatewaySenderBatchOp.java:158)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:329)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:951)
[vm_4] at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:593)
[vm_4] ... 7 more
{noformat}
> CI failure:
> ParallelWANPropagationDUnitTest.testParallelPropagationWihtOverflow
> ---
>
> Key: GEODE-1108
> URL: https://issues.apache.org/jira/browse/GEODE-1108
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Bruce Schuchardt
> Labels: CI
>
> revision 67f0e2ca8dd384100a111e56aba052bc825ba103
> om.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.wan.parallel.ParallelWANPropagationDUnitTest$$Lambda$557/2058588163.run
> in VM 4 running on Host timor.gemstone.com with 8 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:440)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:382)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:318)
> at
> com.gemstone.gemfire.internal.cache.wan.parallel.ParallelWANPropagationDUnitTest.testParallelPropagationWihtOverflow(ParallelWANPropagationDUnitTest.java:617)
> 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.
[jira] [Reopened] (GEODE-478) Message class length field overflows if size is > 2GB
[
https://issues.apache.org/jira/browse/GEODE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reopened GEODE-478:
-
I'm reopening this issue because the test for these changes,
ParallelGatewaySenderOperationsDUnitTest.testParallelGatewaySenderMessageTooLargeException,
passes even if the maximum message size is not set.
We need to add a stat to track when we shrink and retry a batch due to this
failure and change the test to check the stat.
> Message class length field overflows if size is > 2GB
> -
>
> Key: GEODE-478
> URL: https://issues.apache.org/jira/browse/GEODE-478
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
> Fix For: 1.0.0-incubating.M2
>
>
> This bug is described in the context of a {{GatewaySender}} batch, but I
> think it could also happen with a client putAll.
> If the batch size is sufficiently large, and the data size as well, it is
> possible that we attempt to send a message greater than 2GB, which blows up
> the receiver with an exception like this one:
> {noformat}
> [warning 2015/10/07 21:06:29.213 UTC gemfire-data-node-cer-lx-gfirep03-49002
> tid=0xc3af9] Server connection from
> [identity(10.92.5.233(gemfire-data-node-ldc-lx-gfirep08-49002:23053):51883,connection=13;
> port=18172]: Unexpected IOException:
> java.io.IOException: Part length ( -2,000,248,199 ) and number of parts (
> 18,001 ) inconsistent
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.readPayloadFields(Message.java:793)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.readHeaderAndPayload(Message.java:742)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.read(Message.java:587)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.recv(Message.java:1087)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.recv(Message.java:1101)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.readRequest(BaseCommand.java:996)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:770)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:952)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1206)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:532)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
> Nothing on the sender side keeps track of the total size of the message that
> will be sent. We need to send earlier than satisfying the batch size if the
> buffer gets too large. I would suggest 1GB as being the largest we should
> allow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1108) CI failure: ParallelWANPropagationDUnitTest.testParallelPropagationWihtOverflow
[ https://issues.apache.org/jira/browse/GEODE-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1108. -- Resolution: Fixed Assignee: Dan Smith > CI failure: > ParallelWANPropagationDUnitTest.testParallelPropagationWihtOverflow > --- > > Key: GEODE-1108 > URL: https://issues.apache.org/jira/browse/GEODE-1108 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Bruce Schuchardt >Assignee: Dan Smith > Labels: CI > > revision 67f0e2ca8dd384100a111e56aba052bc825ba103 > om.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.wan.parallel.ParallelWANPropagationDUnitTest$$Lambda$557/2058588163.run > in VM 4 running on Host timor.gemstone.com with 8 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:440) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:382) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:318) > at > com.gemstone.gemfire.internal.cache.wan.parallel.ParallelWANPropagationDUnitTest.testParallelPropagationWihtOverflow(ParallelWANPropagationDUnitTest.java:617) > 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.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) > Caused by: java.lang.AssertionError: Event never occurred after 18 ms: > Expected bucket entries for bucket: 45 is: 0 but actual entries: 2 This > bucket isPrimary: true KEYSET: [2
[jira] [Commented] (GEODE-1117) Gateway sender manual-start=true causes region data not to be recovered from disk until gateway sender is started
[ https://issues.apache.org/jira/browse/GEODE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210715#comment-15210715 ] Dan Smith commented on GEODE-1117: -- The issue is that the gateway sender does not actually create the queue region until start is called. Persistent recovery does not happen until all colocated regions are created - this includes the gateway queue region if it is persistent. This is to avoid moving data in some of the colocated regions before all of the colocated regions have actually been recovered - otherwise we would break the colocation and bad things would happen. We should look into why the gateway sender doesn't create the queue region until start is called and see if it can create the queue region earlier. > Gateway sender manual-start=true causes region data not to be recovered from > disk until gateway sender is started > - > > Key: GEODE-1117 > URL: https://issues.apache.org/jira/browse/GEODE-1117 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: William Markito Oliveira > > Gateway sender manual-start=true causes region data not to be recovered from > disk until gateway sender is started which results in a cluster with no data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1128) Add log messages and enhance the output of list-missing-disk-stores to report missing colocated regions
Dan Smith created GEODE-1128: Summary: Add log messages and enhance the output of list-missing-disk-stores to report missing colocated regions Key: GEODE-1128 URL: https://issues.apache.org/jira/browse/GEODE-1128 Project: Geode Issue Type: Bug Components: persistence Reporter: Dan Smith Persistent recovery waits until all colocated regions are created. This is necessary in order to maintain colocation. However, it can result in surprising behavior if a user doesn't create a region or, in the case of GEODE-1117, geode doesn't create an internal region. We need a warning level log message indicating that some colocated regions are missing. We do have a log message after 15 seconds if other members have not created persistent regions - see the code in RedundancyLogger.logWaitingForMembers. We should enhance the logger to report any missing colocated regions as well. The list-missing-disk-stores command should also be enhanced to report missing colocated regions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1128) Add log messages and enhance the output of list-missing-disk-stores to report missing colocated regions
[ https://issues.apache.org/jira/browse/GEODE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210749#comment-15210749 ] Dan Smith commented on GEODE-1128: -- The general goal here is that if there are any issues with persistent recovery, they should show up in the log and should also be displayed in list-missing-disk-stores. We might also want to consider logging if there are any unrecovered persistent regions. > Add log messages and enhance the output of list-missing-disk-stores to report > missing colocated regions > --- > > Key: GEODE-1128 > URL: https://issues.apache.org/jira/browse/GEODE-1128 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Dan Smith > > Persistent recovery waits until all colocated regions are created. This is > necessary in order to maintain colocation. However, it can result in > surprising behavior if a user doesn't create a region or, in the case of > GEODE-1117, geode doesn't create an internal region. > We need a warning level log message indicating that some colocated regions > are missing. We do have a log message after 15 seconds if other members have > not created persistent regions - see the code in > RedundancyLogger.logWaitingForMembers. > We should enhance the logger to report any missing colocated regions as well. > The list-missing-disk-stores command should also be enhanced to report > missing colocated regions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-874) v1.0.0-incubating.M1.RC2: Text file errors in the source distribution
[ https://issues.apache.org/jira/browse/GEODE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-874. - Resolution: Fixed Merged pull request from Karen. > v1.0.0-incubating.M1.RC2: Text file errors in the source distribution > - > > Key: GEODE-874 > URL: https://issues.apache.org/jira/browse/GEODE-874 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Kenneth Howe >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating.M2 > > > gradlew script is not included in the Geode release packages, but it is > called out in command examples in the following text files in the release > source distribution: > COMPILING.txt > RUNNING.txt > docker/Dockerfile > gemfire-spark-connector/doc/1_building.md > The easy fix is to change "gradlew" to "gradle" in affected files and include > a requirement for the user to install gradle from gradle.org. > There was a similar issue with README.md that was fixed for RC2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-478) Message class length field overflows if size is > 2GB
[
https://issues.apache.org/jira/browse/GEODE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-478.
-
Resolution: Fixed
> Message class length field overflows if size is > 2GB
> -
>
> Key: GEODE-478
> URL: https://issues.apache.org/jira/browse/GEODE-478
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
> Fix For: 1.0.0-incubating.M2
>
>
> This bug is described in the context of a {{GatewaySender}} batch, but I
> think it could also happen with a client putAll.
> If the batch size is sufficiently large, and the data size as well, it is
> possible that we attempt to send a message greater than 2GB, which blows up
> the receiver with an exception like this one:
> {noformat}
> [warning 2015/10/07 21:06:29.213 UTC gemfire-data-node-cer-lx-gfirep03-49002
> tid=0xc3af9] Server connection from
> [identity(10.92.5.233(gemfire-data-node-ldc-lx-gfirep08-49002:23053):51883,connection=13;
> port=18172]: Unexpected IOException:
> java.io.IOException: Part length ( -2,000,248,199 ) and number of parts (
> 18,001 ) inconsistent
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.readPayloadFields(Message.java:793)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.readHeaderAndPayload(Message.java:742)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.read(Message.java:587)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.recv(Message.java:1087)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.recv(Message.java:1101)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.readRequest(BaseCommand.java:996)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:770)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:952)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1206)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:532)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
> Nothing on the sender side keeps track of the total size of the message that
> will be sent. We need to send earlier than satisfying the batch size if the
> buffer gets too large. I would suggest 1GB as being the largest we should
> allow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1123: - Component/s: (was: functions) messaging > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: messaging >Reporter: Bruce Schuchardt > Labels: CI > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1123: - Assignee: Bruce Schuchardt > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: messaging >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Labels: CI > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1079) Unavailable maven repositories listed in build.gradle
[ https://issues.apache.org/jira/browse/GEODE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1079. -- Resolution: Fixed > Unavailable maven repositories listed in build.gradle > - > > Key: GEODE-1079 > URL: https://issues.apache.org/jira/browse/GEODE-1079 > Project: Geode > Issue Type: Bug > Components: build >Reporter: nabarun >Assignee: Dan Smith > > In the build.gradle script the following repositories are unreachable > 1. https://plugins.gradle.org/m2/ > 2. http://dist.gemstone.com/maven/release > PS: These warning messages are shown when IntelliJ imports the project from > the gradle file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1079) Unavailable maven repositories listed in build.gradle
[ https://issues.apache.org/jira/browse/GEODE-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219087#comment-15219087 ] Dan Smith commented on GEODE-1079: -- I removed dist.gemstone.com. However, https://plugins.gradle.org/m2/ is needed for the rat gradle task, it doesn't seem to be available from anywhere else, such as mavenCentral. If we switch to the new plugins DSL with gradle, this problem will go away because intellij won't see the repository at all and the plugins DSL already looks at plugins.gradle.org. Unfortunately, there are some limitations with the plugins DSL, specifically in the section on limitations in https://docs.gradle.org/current/userguide/plugins.html it mentions that the plugins section must be in the top level buildscript. Once gradle fixes those limitations, we can switch and that error will go away. Until then, it's a harmless warning seen only on import. > Unavailable maven repositories listed in build.gradle > - > > Key: GEODE-1079 > URL: https://issues.apache.org/jira/browse/GEODE-1079 > Project: Geode > Issue Type: Bug > Components: build >Reporter: nabarun >Assignee: Dan Smith > > In the build.gradle script the following repositories are unreachable > 1. https://plugins.gradle.org/m2/ > 2. http://dist.gemstone.com/maven/release > PS: These warning messages are shown when IntelliJ imports the project from > the gradle file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219145#comment-15219145 ] Dan Smith commented on GEODE-1123: -- If I add a sleep to the test before the assertion, it fails with this error every time. It looks like what is happening is that the locator is also included in the list returned by DistributionManager.getOtherDistributionManagerIds(). I'm not sure if something changed recently to include the locator, or if this race always existed. > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Bruce Schuchardt > Labels: CI > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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)
[jira] [Resolved] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1123. -- Resolution: Fixed > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Bruce Schuchardt > Labels: CI > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1123. -- Resolution: Fixed You're way to fast :) I just checked a fix in 5 minutes ago, the CI hasn't picked it up yet. > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Bruce Schuchardt > Labels: CI > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1168) geode-dependencies manifest is missing jars that are present in the lib directory
Dan Smith created GEODE-1168:
Summary: geode-dependencies manifest is missing jars that are
present in the lib directory
Key: GEODE-1168
URL: https://issues.apache.org/jira/browse/GEODE-1168
Project: Geode
Issue Type: Bug
Components: build
Reporter: Dan Smith
While looking into GEODE-1025, I discovered that we have a number of jars in
the geode-assembly/build/install/apache-geode/lib directory that do not appear
in geode-dependencies.jar or gfsh-dependencies.jar.
I believe that means that these are not actually on the classpath for any geode
process, which means they either shouldn't be shipped with geode at all, or
they are supposed to be on the classpath but I getting skipped for some reason.
These are the jars present in the lib directory, but not on the classpath,
excluding the spring jars (I'm cleaning those up as part of GEODE-1025)
{noformat}
activation-1.1.jar
commons-modeler-2.0.jar
findbugs-annotations-1.3.9-1.jar
geode-jca-1.0.0-incubating.M2-SNAPSHOT.rar
geode-web-1.0.0-incubating.M2-SNAPSHOT.jar
geode-web-api-1.0.0-incubating.M2-SNAPSHOT.jar
guava-15.0.jar
javax.mail-api-1.4.5.jar
mx4j-3.0.1.jar
mx4j-remote-3.0.1.jar
mx4j-tools-3.0.1.jar
ra.jar
{noformat}
Most of these jars appear to be coming from compile dependencies of geode-core.
The jars in the lib directory are controlled by the distributions section of
geode-assembly/build.gradle. The jars in the geode-dependencies.jar manifest
are coming from the cp() method in geode-assembly/build.gradle.
It seems like these two lists ought to be unified - we should only ship jars
that appear in one of the two manifests, and what goes into the manifest should
probably be controlled by the configurations of the other projects - In other
words, if it's part of the runtime configuration of geode-core it should be
part of the geode-dependencies.jar; it shouldn't be filtered by this cp()
method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1168) geode-dependencies manifest is missing jars that are present in the lib directory
[
https://issues.apache.org/jira/browse/GEODE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1168:
-
Fix Version/s: 1.0.0-incubating.M3
> geode-dependencies manifest is missing jars that are present in the lib
> directory
> -
>
> Key: GEODE-1168
> URL: https://issues.apache.org/jira/browse/GEODE-1168
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> While looking into GEODE-1025, I discovered that we have a number of jars in
> the geode-assembly/build/install/apache-geode/lib directory that do not
> appear in geode-dependencies.jar or gfsh-dependencies.jar.
> I believe that means that these are not actually on the classpath for any
> geode process, which means they either shouldn't be shipped with geode at
> all, or they are supposed to be on the classpath but I getting skipped for
> some reason.
> These are the jars present in the lib directory, but not on the classpath,
> excluding the spring jars (I'm cleaning those up as part of GEODE-1025)
> {noformat}
> activation-1.1.jar
> commons-modeler-2.0.jar
> findbugs-annotations-1.3.9-1.jar
> geode-jca-1.0.0-incubating.M2-SNAPSHOT.rar
> geode-web-1.0.0-incubating.M2-SNAPSHOT.jar
> geode-web-api-1.0.0-incubating.M2-SNAPSHOT.jar
> guava-15.0.jar
> javax.mail-api-1.4.5.jar
> mx4j-3.0.1.jar
> mx4j-remote-3.0.1.jar
> mx4j-tools-3.0.1.jar
> ra.jar
> {noformat}
> Most of these jars appear to be coming from compile dependencies of
> geode-core.
> The jars in the lib directory are controlled by the distributions section of
> geode-assembly/build.gradle. The jars in the geode-dependencies.jar manifest
> are coming from the cp() method in geode-assembly/build.gradle.
> It seems like these two lists ought to be unified - we should only ship jars
> that appear in one of the two manifests, and what goes into the manifest
> should probably be controlled by the configurations of the other projects -
> In other words, if it's part of the runtime configuration of geode-core it
> should be part of the geode-dependencies.jar; it shouldn't be filtered by
> this cp() method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1168) geode-dependencies manifest is missing jars that are present in the lib directory
[
https://issues.apache.org/jira/browse/GEODE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225348#comment-15225348
]
Dan Smith commented on GEODE-1168:
--
It sounds like these jars are used by the old admin API, which is slated to be
removed as part of GEODE-288
{noformat}
activation-1.1.jar (dependency of commons-modeler)
commons-modeler-2.0.jar
javax.mail-api-1.4.5.jar
mx4j-3.0.1.jar
mx4j-remote-3.0.1.jar
mx4j-tools-3.0.1.jar
{noformat}
> geode-dependencies manifest is missing jars that are present in the lib
> directory
> -
>
> Key: GEODE-1168
> URL: https://issues.apache.org/jira/browse/GEODE-1168
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> While looking into GEODE-1025, I discovered that we have a number of jars in
> the geode-assembly/build/install/apache-geode/lib directory that do not
> appear in geode-dependencies.jar or gfsh-dependencies.jar.
> I believe that means that these are not actually on the classpath for any
> geode process, which means they either shouldn't be shipped with geode at
> all, or they are supposed to be on the classpath but I getting skipped for
> some reason.
> These are the jars present in the lib directory, but not on the classpath,
> excluding the spring jars (I'm cleaning those up as part of GEODE-1025)
> {noformat}
> activation-1.1.jar
> commons-modeler-2.0.jar
> findbugs-annotations-1.3.9-1.jar
> geode-jca-1.0.0-incubating.M2-SNAPSHOT.rar
> geode-web-1.0.0-incubating.M2-SNAPSHOT.jar
> geode-web-api-1.0.0-incubating.M2-SNAPSHOT.jar
> guava-15.0.jar
> javax.mail-api-1.4.5.jar
> mx4j-3.0.1.jar
> mx4j-remote-3.0.1.jar
> mx4j-tools-3.0.1.jar
> ra.jar
> {noformat}
> Most of these jars appear to be coming from compile dependencies of
> geode-core.
> The jars in the lib directory are controlled by the distributions section of
> geode-assembly/build.gradle. The jars in the geode-dependencies.jar manifest
> are coming from the cp() method in geode-assembly/build.gradle.
> It seems like these two lists ought to be unified - we should only ship jars
> that appear in one of the two manifests, and what goes into the manifest
> should probably be controlled by the configurations of the other projects -
> In other words, if it's part of the runtime configuration of geode-core it
> should be part of the geode-dependencies.jar; it shouldn't be filtered by
> this cp() method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-288) Remove deprecated Admin API
[ https://issues.apache.org/jira/browse/GEODE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225357#comment-15225357 ] Dan Smith commented on GEODE-288: - I'm not sure this old admin API while even work now, at least when running as part of a geode server. Some of the dependencies are not even on the server classpath - see GEODE-1168. > Remove deprecated Admin API > --- > > Key: GEODE-288 > URL: https://issues.apache.org/jira/browse/GEODE-288 > Project: Geode > Issue Type: Sub-task > Components: docs, jmx >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund > > The Admin API (com.gemstone.gemfire.admin) and old JMX Agent have been > deprecated since GemFire 7.0. The Admin API was retired in favor of using the > new Management JMX API (com.gemstone.gemfire.management) and GFSH. > #1) move some Admin classes used internally by non-Admin code: > move com.gemstone.gemfire.admin.BackupStatus > move com.gemstone.gemfire.admin.OperationCancelledException > move com.gemstone.gemfire.admin.RegionNotFoundException > move > com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.backupAllMembers > move > com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.compactAllDiskStores > move com.gemstone.gemfire.admin.internal.FinishBackupRequest > move com.gemstone.gemfire.admin.internal.FlushToDiskRequest > move com.gemstone.gemfire.admin.internal.InetAddressUtil > move com.gemstone.gemfire.admin.internal.PrepareBackupRequest > #2) move com.gemstone.gemfire.admin to > com.gemstone.gemfire.internal.admin.api (temporarily) > #3) remove com.gemstone.gemfire.cache.* usage of admin > #4) remove com.gemstone.gemfire.distributed.* usage of admin > #5) remove com.gemstone.gemfire.internal.* usage of admin (except for > internal.admin.*) > #6) remove com.gemstone.gemfire.management.* usage of admin > #7) remove com.gemstone.gemfire.internal.admin.api if possible > #8) remove unused classes from com.gemstone.gemfire.internal.admin.* > Breakdown by package and class: > com.gemstone.gemfire > --change DataSerializer to use moved RegionNotFoundException > com.gemstone.gemfire.cache > com.gemstone.gemfire.cache.persistence > com.gemstone.gemfire.cache.util > --remove com.gemstone.gemfire.cache.util.UniversalMembershipListenerAdapter > com.gemstone.gemfire.distributed > --remove Admin API from javadocs in Locator and DistributedSystem > com.gemstone.gemfire.distributed.internal > --remove > com.gemstone.gemfire.distributed.internal.DistributionManager.createHealthMonitor > --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitor > --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitorImpl > --change > com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.hasAlertListenerFor > to not use AlertLevel > com.gemstone.gemfire.internal > --remove DSFIDFactory support for admin messages > --remove com.gemstone.gemfire.admin.jmx.internal.AgentLauncher from > GemFireUtilLauncher > --change MigrationServer to use moved InetAddressUtil > --change SocketCreator to use moved InetAddressUtil > --remove SystemAdmin.backup > --remove SystemAdmin.compactAllDiskStores > --remove SystemAdmin.shutDownAll > --remove SystemAdmin.listMissingDiskStores > --remove SystemAdmin.revokeMissingDiskStores > com.gemstone.gemfire.internal.cache > --replace use of com.gemstone.gemfire.admin.OperationCancelledException > --remove use of > com.gemstone.gemfire.admin.internal.SystemMemberCacheEventProcessor > com.gemstone.gemfire.internal.cache.partitioned > --replace use of com.gemstone.gemfire.admin.OperationCancelledException > com.gemstone.gemfire.internal.cache.snapshot > --replace use of com.gemstone.gemfire.admin.RegionNotFoundException > com.gemstone.gemfire.internal.tools.gfsh.app.command.task > --reimplement PartitionedRegionAttributeTask > com.gemstone.gemfire.internal.tools.gfsh.util > --reimplement RegionUtil > com.gemstone.gemfire.management.internal.beans > --change DistributedSystemBridge to use moved classes > com.gemstone.gemfire.management.internal.cli.commands > --change DiskStoreCommands to use moved classes > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1171) AutoBalancerJUnitTest.testOOBWhenAboveThresholdButBelowMin fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226636#comment-15226636
]
Dan Smith commented on GEODE-1171:
--
I think the problem is that when the AutoBalancer is created, it's configured
with a cron schedule that triggers every second. However, it's not expecting
the cron job to actually fire before the test completes. If it does, we get
this failure. I can reproduce the issue by adding a 2 second sleep at the end
of the test.
> AutoBalancerJUnitTest.testOOBWhenAboveThresholdButBelowMin fails
> intermittently
> ---
>
> Key: GEODE-1171
> URL: https://issues.apache.org/jira/browse/GEODE-1171
> Project: Geode
> Issue Type: Bug
>Reporter: Swapnil Bawaskar
>Priority: Blocker
> Labels: CI
>
> Failed in Travis CI. Logs are at:
> https://travis-ci.org/apache/incubator-geode/builds/120748668
> {noformat}
> com.gemstone.gemfire.cache.util.AutoBalancerJUnitTest >
> testOOBWhenAboveThresholdButBelowMin FAILED
> unexpected invocation: cacheOperationFacade.acquireAutoBalanceLock()
> expectations:
> expected once, already invoked 1 time:
> cacheOperationFacade.getTotalTransferSize(); returns <200L>
> expected once, never invoked:
> cacheOperationFacade.getTotalTransferSize(); returns <2000L>
> what happened before this:
> cacheOperationFacade.getTotalTransferSize()
> unexpected invocation: cacheOperationFacade.acquireAutoBalanceLock()
> expectations:
> expected once, already invoked 1 time:
> cacheOperationFacade.getTotalTransferSize(); returns <200L>
> expected once, never invoked:
> cacheOperationFacade.getTotalTransferSize(); returns <2000L>
> what happened before this:
> cacheOperationFacade.getTotalTransferSize()
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1171) AutoBalancerJUnitTest.testOOBWhenAboveThresholdButBelowMin fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-1171:
Assignee: Dan Smith
> AutoBalancerJUnitTest.testOOBWhenAboveThresholdButBelowMin fails
> intermittently
> ---
>
> Key: GEODE-1171
> URL: https://issues.apache.org/jira/browse/GEODE-1171
> Project: Geode
> Issue Type: Bug
>Reporter: Swapnil Bawaskar
>Assignee: Dan Smith
>Priority: Blocker
> Labels: CI
>
> Failed in Travis CI. Logs are at:
> https://travis-ci.org/apache/incubator-geode/builds/120748668
> {noformat}
> com.gemstone.gemfire.cache.util.AutoBalancerJUnitTest >
> testOOBWhenAboveThresholdButBelowMin FAILED
> unexpected invocation: cacheOperationFacade.acquireAutoBalanceLock()
> expectations:
> expected once, already invoked 1 time:
> cacheOperationFacade.getTotalTransferSize(); returns <200L>
> expected once, never invoked:
> cacheOperationFacade.getTotalTransferSize(); returns <2000L>
> what happened before this:
> cacheOperationFacade.getTotalTransferSize()
> unexpected invocation: cacheOperationFacade.acquireAutoBalanceLock()
> expectations:
> expected once, already invoked 1 time:
> cacheOperationFacade.getTotalTransferSize(); returns <200L>
> expected once, never invoked:
> cacheOperationFacade.getTotalTransferSize(); returns <2000L>
> what happened before this:
> cacheOperationFacade.getTotalTransferSize()
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1177) Session replication local cache is reporting bad object sizes
Dan Smith created GEODE-1177: Summary: Session replication local cache is reporting bad object sizes Key: GEODE-1177 URL: https://issues.apache.org/jira/browse/GEODE-1177 Project: Geode Issue Type: Bug Components: http session Reporter: Dan Smith The session replication module has a local cache that uses heap LRU - See PeerToPeerSessionCache.createOrRetrieveLocalRegion. When using LRU, the region uses an object sizer to determine the size of the objects. The default object sizer finds all reachable objects using reflection for the first value in the region, and then reuses that size for all subsequent values of the same class. See EvictionAction.createLRUHeapAttributes(). In the case of session replication, it looks like we put a GemfireHttpSession in the region. Unfortunately, that has references back to the session manager, which has references to an InternalDistributedSystem, which in turn pulls in a whole lot of junk. So the size of the objects reported by the sizer for this local cache are probably completely wrong, which might affect the behavior of the heap LRU. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1171) AutoBalancerJUnitTest.testOOBWhenAboveThresholdButBelowMin fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-1171.
--
Resolution: Fixed
> AutoBalancerJUnitTest.testOOBWhenAboveThresholdButBelowMin fails
> intermittently
> ---
>
> Key: GEODE-1171
> URL: https://issues.apache.org/jira/browse/GEODE-1171
> Project: Geode
> Issue Type: Bug
>Reporter: Swapnil Bawaskar
>Assignee: Dan Smith
>Priority: Blocker
> Labels: CI
>
> Failed in Travis CI. Logs are at:
> https://travis-ci.org/apache/incubator-geode/builds/120748668
> {noformat}
> com.gemstone.gemfire.cache.util.AutoBalancerJUnitTest >
> testOOBWhenAboveThresholdButBelowMin FAILED
> unexpected invocation: cacheOperationFacade.acquireAutoBalanceLock()
> expectations:
> expected once, already invoked 1 time:
> cacheOperationFacade.getTotalTransferSize(); returns <200L>
> expected once, never invoked:
> cacheOperationFacade.getTotalTransferSize(); returns <2000L>
> what happened before this:
> cacheOperationFacade.getTotalTransferSize()
> unexpected invocation: cacheOperationFacade.acquireAutoBalanceLock()
> expectations:
> expected once, already invoked 1 time:
> cacheOperationFacade.getTotalTransferSize(); returns <200L>
> expected once, never invoked:
> cacheOperationFacade.getTotalTransferSize(); returns <2000L>
> what happened before this:
> cacheOperationFacade.getTotalTransferSize()
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-902) Remove Apache header from MX4JModelMBean.java
[ https://issues.apache.org/jira/browse/GEODE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-902: Assignee: Anthony Baker (was: William Markito Oliveira) > Remove Apache header from MX4JModelMBean.java > - > > Key: GEODE-902 > URL: https://issues.apache.org/jira/browse/GEODE-902 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > MX4JModelMBean.java has an Apache header but should not as it is under the > MX4J license. Also, we need to handle this appropriately in LICENSE / NOTICE. > See http://mx4j.sourceforge.net/docs/ch01s06.html. > Discussion thread: > http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3ca44698bc-a87b-48e5-bdf2-29c1a1814...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1025) Remove compile dependency on spring data gemfire/geode
[ https://issues.apache.org/jira/browse/GEODE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1025. -- Resolution: Fixed > Remove compile dependency on spring data gemfire/geode > -- > > Key: GEODE-1025 > URL: https://issues.apache.org/jira/browse/GEODE-1025 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M2 > > > We have a compile dependency on spring data gemfire in the ServerLauncher > class to support launching a server using a spring data gemfire configuration > instead of a cache.xml file. > That's a good feature to have, but it should be part of spring data gemfire, > not geode. Because of this compile dependency on SDG, we currently have a > circular dependency on SDG -> Geode -> SDG. That makes it difficult to do > things like rename packages in geode (GEODE-37) because SDG is still using > the old packages. > Instead of directly depending on spring data gemfire, we should provide an > extension point that SDG can plug into to override the cache server startup > behavior. > The easiest place way to do this is just to use the java ServiceLoader > mechanism. We can provide an interface for a plugin that replaces startup > behavior of the server. SDG can provide an implementation of this interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231297#comment-15231297 ] Dan Smith commented on GEODE-1123: -- This new failure is caused by TcpServerBackwardCompatDUnitTest running before hand and leaving a distributed system running. See GEODE-1196. > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Bruce Schuchardt > Labels: CI > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1196) TcpServerBackwardCompatDUnitTest leaves a DistributedSystem connected in one of its members causing DistTXDebugDUnitTest to fail
[
https://issues.apache.org/jira/browse/GEODE-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231296#comment-15231296
]
Dan Smith commented on GEODE-1196:
--
The cause is that TcpServerBackwardCompatDUnitTest creates a DistributedSystem
in members without using DistributedTestCase.getSystem. When
DistTXDebugDUnitTest looks to create a DistributedSystem,
DistributedTestCase.getSystem gets confused and returns the system creating by
TcpServerBackwardCompatDUnitTest, which is connected to the wrong locator.
DistributedTestCase.getSystem gets confused because tries to compare the
properties it saw the last time it was called with the new properties that are
requested, and it only creates a new system if they don't match. In this case,
the existing system never updated the list of properties that don't match.
Regardless, it sounds like the best fix is just to always disconnect the DS at
the end of a test. This used to add a bunch of time to precheckin, but it looks
like it is not that expensive to disconnect and reconnect every test now.
> TcpServerBackwardCompatDUnitTest leaves a DistributedSystem connected in one
> of its members causing DistTXDebugDUnitTest to fail
>
>
> Key: GEODE-1196
> URL: https://issues.apache.org/jira/browse/GEODE-1196
> Project: Geode
> Issue Type: Bug
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>
> The failing test cases are:
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPRRR2_putall
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR2
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXRR2
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXDestroy_invalidate
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR_removeAll
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR_putall
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR_RR
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPRRR2_create
> Although there are a few other ones, the main exception is this
> {{PartitionedRegionStorageException}}:
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest$7.call in VM 3 running on
> Host ip-10-32-39-161.ore1.vpc.pivotal.io with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:439)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:381)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:346)
> at
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR2(DistTXDebugDUnitTest.java:501)
> 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:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>
[jira] [Commented] (GEODE-1193) Remove servlet-api jar from binary distributions
[
https://issues.apache.org/jira/browse/GEODE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231309#comment-15231309
]
Dan Smith commented on GEODE-1193:
--
I think this is getting pulled in as a dependency of jetty. Jetty is part of
the compile dependencies of geode-core, for the code that launches pulse and
the REST API webapps:
{noformat}
compile - Compile classpath for source set 'main'.
+--- org.eclipse.jetty:jetty-webapp:9.3.6.v20151106
|+--- org.eclipse.jetty:jetty-xml:9.3.6.v20151106
||\--- org.eclipse.jetty:jetty-util:9.3.6.v20151106
|\--- org.eclipse.jetty:jetty-servlet:9.3.6.v20151106
| \--- org.eclipse.jetty:jetty-security:9.3.6.v20151106
| \--- org.eclipse.jetty:jetty-server:9.3.6.v20151106
| +--- javax.servlet:javax.servlet-api:3.1.0
<
| +--- org.eclipse.jetty:jetty-http:9.3.6.v20151106
| |\--- org.eclipse.jetty:jetty-util:9.3.6.v20151106
| \--- org.eclipse.jetty:jetty-io:9.3.6.v20151106
|\--- org.eclipse.jetty:jetty-util:9.3.6.v20151106
{noformat}
> Remove servlet-api jar from binary distributions
>
>
> Key: GEODE-1193
> URL: https://issues.apache.org/jira/browse/GEODE-1193
> Project: Geode
> Issue Type: Bug
> Components: build, extensions
>Reporter: Anthony Baker
>
> See thread:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3cdc647cd5-2314-4514-b61e-f4b1a4a78...@pivotal.io%3e
> We're including multiple servlet-api jars in the binary distribution. We
> probably don't need any of them. Investigate if we can move to a 'provided'
> dependency instead of 'compile'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1196) TcpServerBackwardCompatDUnitTest leaves a DistributedSystem connected in one of its members causing DistTXDebugDUnitTest to fail
[
https://issues.apache.org/jira/browse/GEODE-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231402#comment-15231402
]
Dan Smith commented on GEODE-1196:
--
Barry has a fix pending already to change the framework to disconnect after
every test.
> TcpServerBackwardCompatDUnitTest leaves a DistributedSystem connected in one
> of its members causing DistTXDebugDUnitTest to fail
>
>
> Key: GEODE-1196
> URL: https://issues.apache.org/jira/browse/GEODE-1196
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Barry Oglesby
>Assignee: Bruce Schuchardt
>
> The failing test cases are:
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPRRR2_putall
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR2
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXRR2
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXDestroy_invalidate
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR_removeAll
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR_putall
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR_RR
> - com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPRRR2_create
> Although there are a few other ones, the main exception is this
> {{PartitionedRegionStorageException}}:
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest$7.call in VM 3 running on
> Host ip-10-32-39-161.ore1.vpc.pivotal.io with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:439)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:381)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:346)
> at
> com.gemstone.gemfire.disttx.DistTXDebugDUnitTest.testTXPR2(DistTXDebugDUnitTest.java:501)
> 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: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.GeneratedMethodAccessor6.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(ContextClassL
[jira] [Updated] (GEODE-1200) Deprecation of InetAddressUtil
[ https://issues.apache.org/jira/browse/GEODE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1200: - Fix Version/s: (was: 1.0.0-incubating.M2) > Deprecation of InetAddressUtil > -- > > Key: GEODE-1200 > URL: https://issues.apache.org/jira/browse/GEODE-1200 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1146) CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients
[ https://issues.apache.org/jira/browse/GEODE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1146: - Assignee: Bruce Schuchardt > CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients > -- > > Key: GEODE-1146 > URL: https://issues.apache.org/jira/browse/GEODE-1146 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jianxia Chen >Assignee: Bruce Schuchardt > Labels: CI > > https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2082/testReport/com.gemstone.gemfire.cache.query.dunit/QueryUsingPoolDUnitTest/testBindParamsWithMulitipleClients/ > 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 1143688 > [fatal 2016/03/29 22:31:26.669 PDT tid=0xc63] > Membership service failure: Member isn't responding to heartbeat requests > com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to > heartbeat requests > at > com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2586) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:885) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:578) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1542) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1089) > at org.jgroups.JChannel.invokeCallback(JChannel.java:817) > at org.jgroups.JChannel.up(JChannel.java:741) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:392) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:71) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:75) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1590) > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1802) > at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1718) > at org.jgroups.protocols.TP.receive(TP.java:1643) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160) > at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1146) CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients
[ https://issues.apache.org/jira/browse/GEODE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1146: - Component/s: membership > CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients > -- > > Key: GEODE-1146 > URL: https://issues.apache.org/jira/browse/GEODE-1146 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jianxia Chen >Assignee: Bruce Schuchardt > Labels: CI > > https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2082/testReport/com.gemstone.gemfire.cache.query.dunit/QueryUsingPoolDUnitTest/testBindParamsWithMulitipleClients/ > 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 1143688 > [fatal 2016/03/29 22:31:26.669 PDT tid=0xc63] > Membership service failure: Member isn't responding to heartbeat requests > com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to > heartbeat requests > at > com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2586) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:885) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:578) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1542) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1089) > at org.jgroups.JChannel.invokeCallback(JChannel.java:817) > at org.jgroups.JChannel.up(JChannel.java:741) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:392) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:71) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:75) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1590) > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1802) > at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1718) > at org.jgroups.protocols.TP.receive(TP.java:1643) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160) > at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1146) CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients
[ https://issues.apache.org/jira/browse/GEODE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231439#comment-15231439 ] Dan Smith commented on GEODE-1146: -- Looks like there is a force disconnect happening in the middle of this test. > CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients > -- > > Key: GEODE-1146 > URL: https://issues.apache.org/jira/browse/GEODE-1146 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jianxia Chen >Assignee: Bruce Schuchardt > Labels: CI > > https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2082/testReport/com.gemstone.gemfire.cache.query.dunit/QueryUsingPoolDUnitTest/testBindParamsWithMulitipleClients/ > 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 1143688 > [fatal 2016/03/29 22:31:26.669 PDT tid=0xc63] > Membership service failure: Member isn't responding to heartbeat requests > com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to > heartbeat requests > at > com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2586) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:885) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:578) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1542) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1089) > at org.jgroups.JChannel.invokeCallback(JChannel.java:817) > at org.jgroups.JChannel.up(JChannel.java:741) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:392) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:71) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:75) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1590) > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1802) > at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1718) > at org.jgroups.protocols.TP.receive(TP.java:1643) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160) > at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1183) CI Failure: CacheClientNotifierDUnitTest.testMultipleCacheServer
[ https://issues.apache.org/jira/browse/GEODE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1183: - Component/s: client queues > CI Failure: CacheClientNotifierDUnitTest.testMultipleCacheServer > > > Key: GEODE-1183 > URL: https://issues.apache.org/jira/browse/GEODE-1183 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Jinmei Liao > Labels: CI > > Geode_develop_DistributedTests/2162/ > Revision: 8622d63a1cf7f065bcc91876b12867158720c6c1 > 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 3722 > [fatal 2016/04/06 01:13:44.891 PDT 1> tid=0x1cd] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:22793 Thread 1,5,Handshaker 0.0.0.0/0.0.0.0:22793] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > --- > Found suspect string in log4j at line 4185 > [fatal 2016/04/06 01:13:45.259 PDT 1> tid=0x1ed] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:26142 Thread 1,5,Handshaker 0.0.0.0/0.0.0.0:26142] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > --- > Found suspect string in log4j at line 4436 > [fatal 2016/04/06 01:13:45.381 PDT 0> tid=0x1c5] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:26142 Thread 0,5,Handshaker 0.0.0.0/0.0.0.0:26142] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > -
[jira] [Resolved] (GEODE-1123) CI failure: StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions
[ https://issues.apache.org/jira/browse/GEODE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1123. -- Resolution: Fixed Fix Version/s: 1.0.0-incubating.M2 GEODE-1196 is fixed, that should fix the latest failure of this test as well. > CI failure: > StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions > -- > > Key: GEODE-1123 > URL: https://issues.apache.org/jira/browse/GEODE-1123 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Bruce Schuchardt > Labels: CI > Fix For: 1.0.0-incubating.M2 > > > This test failed in revision 57b00b12d4abcf59769171e333aa76d76e5bd0a0 > junit.framework.AssertionFailedError: expected:<4> but was:<5> > 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.distributed.internal.streaming.StreamingOperationManyDUnitTest.testStreamingManyProvidersNoExceptions(StreamingOperationManyDUnitTest.java:67) > 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.GeneratedMethodAccessor288.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.GeneratedMethodAccessor287.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) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1203) gfsh connect --use-http reports a ClassNotFoundException
[
https://issues.apache.org/jira/browse/GEODE-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1203:
-
Component/s: rest (admin)
> gfsh connect --use-http reports a ClassNotFoundException
>
>
> Key: GEODE-1203
> URL: https://issues.apache.org/jira/browse/GEODE-1203
> Project: Geode
> Issue Type: Bug
> Components: rest (admin)
>Reporter: Dan Smith
>
> Connecting with the admin REST API is now broken. I think it's because the
> spring-web jar is no longer placed in the lib directory or added to the
> gfsh-deps.jar. In geode-assembly/build.gradle, the gfshDepsJars tries to add
> spring-web to the classpath, but it is not actually part of the runtime
> configuration so this expression evaluates to null
> {code}
> def springWeb = configurations.runtime.collect { it.getName() }.find {
> it.contains('spring-web') }
> {code}
> {noformat}
> gfsh>connect --use-http --url=http://localhost:7070/gemfire/v1
> Exception in thread "Gfsh Launcher" java.lang.NoClassDefFoundError:
> org/springframework/http/client/ClientHttpRequestFactory
> at
> com.gemstone.gemfire.management.internal.cli.commands.ShellCommands.connect(ShellCommands.java:214)
> 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.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> com.gemstone.gemfire.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:110)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:127)
> at
> com.gemstone.gemfire.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:891)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.springframework.http.client.ClientHttpRequestFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 11 more
> Exception in thread "main" java.lang.NullPointerException
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.parseOptions(Launcher.java:235)
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.parseCommandLine(Launcher.java:243)
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.main(Launcher.java:95)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1203) gfsh connect --use-http reports a ClassNotFoundException
Dan Smith created GEODE-1203:
Summary: gfsh connect --use-http reports a ClassNotFoundException
Key: GEODE-1203
URL: https://issues.apache.org/jira/browse/GEODE-1203
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
Connecting with the admin REST API is now broken. I think it's because the
spring-web jar is no longer placed in the lib directory or added to the
gfsh-deps.jar. In geode-assembly/build.gradle, the gfshDepsJars tries to add
spring-web to the classpath, but it is not actually part of the runtime
configuration so this expression evaluates to null
{code}
def springWeb = configurations.runtime.collect { it.getName() }.find {
it.contains('spring-web') }
{code}
{noformat}
gfsh>connect --use-http --url=http://localhost:7070/gemfire/v1
Exception in thread "Gfsh Launcher" java.lang.NoClassDefFoundError:
org/springframework/http/client/ClientHttpRequestFactory
at
com.gemstone.gemfire.management.internal.cli.commands.ShellCommands.connect(ShellCommands.java:214)
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.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
at
com.gemstone.gemfire.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:110)
at
org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:127)
at
com.gemstone.gemfire.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:891)
at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException:
org.springframework.http.client.ClientHttpRequestFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 11 more
Exception in thread "main" java.lang.NullPointerException
at
com.gemstone.gemfire.management.internal.cli.Launcher.parseOptions(Launcher.java:235)
at
com.gemstone.gemfire.management.internal.cli.Launcher.parseCommandLine(Launcher.java:243)
at
com.gemstone.gemfire.management.internal.cli.Launcher.main(Launcher.java:95)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1183) CI Failure: CacheClientNotifierDUnitTest.testMultipleCacheServer
[ https://issues.apache.org/jira/browse/GEODE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235509#comment-15235509 ] Dan Smith commented on GEODE-1183: -- This is a new test method added in 49e3f523d16389f5e84847c6dcfd6ab45427f8c2 that seems to be failing fairly frequently. > CI Failure: CacheClientNotifierDUnitTest.testMultipleCacheServer > > > Key: GEODE-1183 > URL: https://issues.apache.org/jira/browse/GEODE-1183 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Jinmei Liao > Labels: CI > > Geode_develop_DistributedTests/2162/ > Revision: 8622d63a1cf7f065bcc91876b12867158720c6c1 > 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 3722 > [fatal 2016/04/06 01:13:44.891 PDT 1> tid=0x1cd] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:22793 Thread 1,5,Handshaker 0.0.0.0/0.0.0.0:22793] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > --- > Found suspect string in log4j at line 4185 > [fatal 2016/04/06 01:13:45.259 PDT 1> tid=0x1ed] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:26142 Thread 1,5,Handshaker 0.0.0.0/0.0.0.0:26142] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > --- > Found suspect string in log4j at line 4436 > [fatal 2016/04/06 01:13:45.381 PDT 0> tid=0x1c5] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:26142 Thread 0,5,Handshaker 0.0.0.0/0.0.0.0:26142] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142
[jira] [Updated] (GEODE-1183) CI Failure: CacheClientNotifierDUnitTest.testMultipleCacheServer
[ https://issues.apache.org/jira/browse/GEODE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1183: - Assignee: xiaojian zhou > CI Failure: CacheClientNotifierDUnitTest.testMultipleCacheServer > > > Key: GEODE-1183 > URL: https://issues.apache.org/jira/browse/GEODE-1183 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Jinmei Liao >Assignee: xiaojian zhou > Labels: CI > > Geode_develop_DistributedTests/2162/ > Revision: 8622d63a1cf7f065bcc91876b12867158720c6c1 > 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 3722 > [fatal 2016/04/06 01:13:44.891 PDT 1> tid=0x1cd] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:22793 Thread 1,5,Handshaker 0.0.0.0/0.0.0.0:22793] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > --- > Found suspect string in log4j at line 4185 > [fatal 2016/04/06 01:13:45.259 PDT 1> tid=0x1ed] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:26142 Thread 1,5,Handshaker 0.0.0.0/0.0.0.0:26142] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > 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) > --- > Found suspect string in log4j at line 4436 > [fatal 2016/04/06 01:13:45.381 PDT 0> tid=0x1c5] Uncaught exception in thread Thread[Handshaker > 0.0.0.0/0.0.0.0:26142 Thread 0,5,Handshaker 0.0.0.0/0.0.0.0:26142] > java.lang.IllegalThreadStateException > at java.lang.Thread.start(Thread.java:705) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:639) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:454) > at > com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:350) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1595) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1374) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.la
[jira] [Created] (GEODE-1217) jansi should be marked as optional in the pom
Dan Smith created GEODE-1217: Summary: jansi should be marked as optional in the pom Key: GEODE-1217 URL: https://issues.apache.org/jira/browse/GEODE-1217 Project: Geode Issue Type: Bug Reporter: Dan Smith jansi is only required for gfsh. The other gfsh related jars like jline and spring-shell are marked as optional. jansi should be marked as optional as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1217) jansi should be marked as optional in the pom
[ https://issues.apache.org/jira/browse/GEODE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1217: Assignee: Dan Smith > jansi should be marked as optional in the pom > - > > Key: GEODE-1217 > URL: https://issues.apache.org/jira/browse/GEODE-1217 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith > > jansi is only required for gfsh. The other gfsh related jars like jline and > spring-shell are marked as optional. jansi should be marked as optional as > well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1218) jna should not be marked optional in the pom
Dan Smith created GEODE-1218: Summary: jna should not be marked optional in the pom Key: GEODE-1218 URL: https://issues.apache.org/jira/browse/GEODE-1218 Project: Geode Issue Type: Bug Reporter: Dan Smith JNA is technically not required for geode to function, but it is needed for common features like disk stores and off heap memory. It's better for this jar to be bundled by default than for a user to need to discover that it should be added to the classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1218) jna should not be marked optional in the pom
[ https://issues.apache.org/jira/browse/GEODE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1218: Assignee: Dan Smith > jna should not be marked optional in the pom > > > Key: GEODE-1218 > URL: https://issues.apache.org/jira/browse/GEODE-1218 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith > > JNA is technically not required for geode to function, but it is needed for > common features like disk stores and off heap memory. It's better for this > jar to be bundled by default than for a user to need to discover that it > should be added to the classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1203) gfsh connect --use-http reports a ClassNotFoundException
[
https://issues.apache.org/jira/browse/GEODE-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1203:
-
Affects Version/s: 1.0.0-incubating.M2
> gfsh connect --use-http reports a ClassNotFoundException
>
>
> Key: GEODE-1203
> URL: https://issues.apache.org/jira/browse/GEODE-1203
> Project: Geode
> Issue Type: Bug
> Components: rest (admin)
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Dan Smith
>
> Connecting with the admin REST API is now broken. I think it's because the
> spring-web jar is no longer placed in the lib directory or added to the
> gfsh-deps.jar. In geode-assembly/build.gradle, the gfshDepsJars tries to add
> spring-web to the classpath, but it is not actually part of the runtime
> configuration so this expression evaluates to null
> {code}
> def springWeb = configurations.runtime.collect { it.getName() }.find {
> it.contains('spring-web') }
> {code}
> {noformat}
> gfsh>connect --use-http --url=http://localhost:7070/gemfire/v1
> Exception in thread "Gfsh Launcher" java.lang.NoClassDefFoundError:
> org/springframework/http/client/ClientHttpRequestFactory
> at
> com.gemstone.gemfire.management.internal.cli.commands.ShellCommands.connect(ShellCommands.java:214)
> 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.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> com.gemstone.gemfire.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:110)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:127)
> at
> com.gemstone.gemfire.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:891)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.springframework.http.client.ClientHttpRequestFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 11 more
> Exception in thread "main" java.lang.NullPointerException
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.parseOptions(Launcher.java:235)
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.parseCommandLine(Launcher.java:243)
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.main(Launcher.java:95)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1018) CI Failure: SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
[
https://issues.apache.org/jira/browse/GEODE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1018:
-
Fix Version/s: (was: 1.0.0-incubating.M2)
> CI Failure:
> SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
>
>
> Key: GEODE-1018
> URL: https://issues.apache.org/jira/browse/GEODE-1018
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: nabarun
> Labels: CI
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest$$Lambda$162/1962539952.run
> in VM 2 running on Host cc2-ub.gemstone.com with 8 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:379)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:321)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:272)
> at
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent(SerialWANPropogationDUnitTest.java:905)
> 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.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)
> Caused by: java.lang.AssertionError: Event never occurred after 24 ms:
> Expected r
[jira] [Assigned] (GEODE-1018) CI Failure: SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
[
https://issues.apache.org/jira/browse/GEODE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-1018:
Assignee: Dan Smith (was: nabarun)
> CI Failure:
> SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
>
>
> Key: GEODE-1018
> URL: https://issues.apache.org/jira/browse/GEODE-1018
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: Dan Smith
> Labels: CI
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest$$Lambda$162/1962539952.run
> in VM 2 running on Host cc2-ub.gemstone.com with 8 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:379)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:321)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:272)
> at
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent(SerialWANPropogationDUnitTest.java:905)
> 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.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)
> Caused by: java.lang.AssertionError: Event never occurred after 24 ms:
> Expected re
[jira] [Commented] (GEODE-1018) CI Failure: SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
[
https://issues.apache.org/jira/browse/GEODE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239612#comment-15239612
]
Dan Smith commented on GEODE-1018:
--
I saw another failure from this same test. This time, it was an NPE in the
logs.
{noformat}
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 3865
[error 2016/04/13 07:45:59.791 UTC :1028 shared ordered uid=654 port=43089>
tid=0x29f7] Exception occurred in CacheListener
java.lang.NullPointerException
at
com.gemstone.gemfire.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:80)
at
com.gemstone.gemfire.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:162)
at
com.gemstone.gemfire.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:9242)
at
com.gemstone.gemfire.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:7680)
at
com.gemstone.gemfire.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:7472)
at
com.gemstone.gemfire.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2611)
at
com.gemstone.gemfire.internal.cache.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:161)
at
com.gemstone.gemfire.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:7408)
at
com.gemstone.gemfire.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1458)
at
com.gemstone.gemfire.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:7182)
at
com.gemstone.gemfire.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:7154)
at
com.gemstone.gemfire.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:49)
at
com.gemstone.gemfire.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:7119)
at
com.gemstone.gemfire.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1806)
at
com.gemstone.gemfire.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1288)
at
com.gemstone.gemfire.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2421)
at
com.gemstone.gemfire.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:1103)
at
com.gemstone.gemfire.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:131)
at
com.gemstone.gemfire.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1165)
at
com.gemstone.gemfire.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1065)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:442)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.scheduleIncomingMessage(DistributionManager.java:3563)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.handleIncomingDMsg(DistributionManager.java:3186)
at
com.gemstone.gemfire.distributed.internal.DistributionManager$MyListener.messageReceived(DistributionManager.java:4385)
at
com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.dispatchMessage(GMSMembershipManager.java:1135)
at
com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.handleOrDeferMessage(GMSMembershipManager.java:1063)
at
com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager$MyDCReceiver.messageReceived(GMSMembershipManager.java:417)
at
com.gemstone.gemfire.distributed.internal.direct.DirectChannel.receive(DirectChannel.java:751)
at
com.gemstone.gemfire.internal.tcp.TCPConduit.messageReceived(TCPConduit.java:833)
at
com.gemstone.gemfire.internal.tcp.Connection.dispatchMessage(Connection.java:3994)
at
com.gemstone.gemfire.internal.tcp.Connection.processNIOBuffer(Connection.java:3578)
at
com.gemstone.gemfire.internal.tcp.Connection.runNioReader(Connection.java:1870)
at
com.gemstone.gemfire.internal.tcp.Connection.run(Connection.java:1739)
at java.lang.Thread.run(Thread.java:745)
{noformat}
It looks to me like the product code has race because it's checking getQueues
twice. getQueues could return null the second time if the queue is stopped
because the event processor is set to null during the stop
{code}
if
[jira] [Resolved] (GEODE-1018) CI Failure: SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
[
https://issues.apache.org/jira/browse/GEODE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-1018.
--
> CI Failure:
> SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
>
>
> Key: GEODE-1018
> URL: https://issues.apache.org/jira/browse/GEODE-1018
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: Dan Smith
> Labels: CI
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest$$Lambda$162/1962539952.run
> in VM 2 running on Host cc2-ub.gemstone.com with 8 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:379)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:321)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:272)
> at
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent(SerialWANPropogationDUnitTest.java:905)
> 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.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)
> Caused by: java.lang.AssertionError: Event never occurred after 24 ms:
> Expected region entries: 8000 but actual entries: 7650 p
[jira] [Updated] (GEODE-1018) CI Failure: SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
[
https://issues.apache.org/jira/browse/GEODE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1018:
-
Fix Version/s: 1.0.0-incubating.M3
> CI Failure:
> SerialWANPropogationOffHeapDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent
>
>
> Key: GEODE-1018
> URL: https://issues.apache.org/jira/browse/GEODE-1018
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: Dan Smith
> Labels: CI
> Fix For: 1.0.0-incubating.M3
>
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest$$Lambda$162/1962539952.run
> in VM 2 running on Host cc2-ub.gemstone.com with 8 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:379)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:321)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:272)
> at
> com.gemstone.gemfire.internal.cache.wan.serial.SerialWANPropogationDUnitTest.testReplicatedSerialPropagationWithRemoteReceiverRestarted_SenderReceiverPersistent(SerialWANPropogationDUnitTest.java:905)
> 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.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)
> Caused by: java.lang.AssertionError: Event never occ
[jira] [Updated] (GEODE-1212) Cleanup replicate region support for lucene index
[ https://issues.apache.org/jira/browse/GEODE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1212: - Fix Version/s: (was: 1.0.0-incubating.M2) 1.0.0-incubating.M3 > Cleanup replicate region support for lucene index > - > > Key: GEODE-1212 > URL: https://issues.apache.org/jira/browse/GEODE-1212 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: xiaojian zhou >Assignee: xiaojian zhou > Fix For: 1.0.0-incubating.M3 > > > Current version we only support lucene index on partition region. Need to > clean up the code for support of replicated region. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-235) EntryEvent toString should describe the region the event is on
[
https://issues.apache.org/jira/browse/GEODE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-235:
Fix Version/s: 1.0.0-incubating.M3
> EntryEvent toString should describe the region the event is on
> --
>
> Key: GEODE-235
> URL: https://issues.apache.org/jira/browse/GEODE-235
> Project: Geode
> Issue Type: Improvement
> Components: regions
>Reporter: Darrel Schneider
>Assignee: Scott Jewell
> Fix For: 1.0.0-incubating.M3
>
>
> When an EntryEvent gets logged it looks something like this:
> {code}
> Event=EntryEventImpl[op=CREATE;key=112;oldValue=null;newValue=VMCachedDeserializable@2009740363;callbackArg=null;originRemote=true;originMember=cc2-rh6:3889;callbacksInvoked;version={v1;
> rv1; mbr=cc2-rh6:50532; time=1439996558405;
> remote};id=EventID[threadID=61;sequenceID=389];isFromServer]
> {code}
> Given that every EntryEvent is also a CacheEvent which has a getRegion method
> we should also show the fully qualified region name for the event.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1226) Release process should not require putting passwords in plain text files
Dan Smith created GEODE-1226:
Summary: Release process should not require putting passwords in
plain text files
Key: GEODE-1226
URL: https://issues.apache.org/jira/browse/GEODE-1226
Project: Geode
Issue Type: Task
Reporter: Dan Smith
Our current release steps require putting your apache password and gpg keyring
password in a plain text file.
https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
{noformat}
signing.password=YourSuperSecretPassphrase # Plaintext passphrase to
decrypt key
nexusPassword=password # Your password on Apache's
LDAP
{noformat}
We should change the build to prompt for a password if required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1226) Release process should not require putting passwords in plain text files
[
https://issues.apache.org/jira/browse/GEODE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-1226:
Assignee: Dan Smith
> Release process should not require putting passwords in plain text files
>
>
> Key: GEODE-1226
> URL: https://issues.apache.org/jira/browse/GEODE-1226
> Project: Geode
> Issue Type: Task
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> Our current release steps require putting your apache password and gpg
> keyring password in a plain text file.
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> {noformat}
> signing.password=YourSuperSecretPassphrase # Plaintext passphrase to
> decrypt key
> nexusPassword=password # Your password on Apache's
> LDAP
> {noformat}
> We should change the build to prompt for a password if required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-534) CI failure: JSSESocketJUnitTest.testSSLSocket SSLHandshakeException: No appropriate protocol
[ https://issues.apache.org/jira/browse/GEODE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-534: Assignee: Barry Oglesby (was: Jens Deppe) > CI failure: JSSESocketJUnitTest.testSSLSocket SSLHandshakeException: No > appropriate protocol > > > Key: GEODE-534 > URL: https://issues.apache.org/jira/browse/GEODE-534 > Project: Geode > Issue Type: Bug >Reporter: Darrel Schneider >Assignee: Barry Oglesby > Labels: CI > Fix For: 1.0.0-incubating.M1 > > > javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is > disabled or cipher suites are inappropriate) > at sun.security.ssl.Handshaker.activate(Handshaker.java:503) > at > sun.security.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1482) > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1351) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) > at > com.gemstone.gemfire.internal.SocketCreator.configureClientSSLSocket(SocketCreator.java:1112) > at > com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:998) > at > com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:956) > at > com.gemstone.gemfire.internal.SocketCreator.connectForServer(SocketCreator.java:930) > at > com.gemstone.gemfire.internal.JSSESocketJUnitTest.testSSLSocket(JSSESocketJUnitTest.java:119) > This test is explicitly using SSL_RSA_WITH_RC4_128_MD5 when the client > connects to the server. > But in 1.8u51 this cipher was disabled: > http://bugs.java.com/view_bug.do?bug_id=8076221 > I think we should just change this test to use a different cipher. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1226) Release process should not require putting passwords in plain text files
[
https://issues.apache.org/jira/browse/GEODE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-1226.
--
Resolution: Fixed
> Release process should not require putting passwords in plain text files
>
>
> Key: GEODE-1226
> URL: https://issues.apache.org/jira/browse/GEODE-1226
> Project: Geode
> Issue Type: Task
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> Our current release steps require putting your apache password and gpg
> keyring password in a plain text file.
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> {noformat}
> signing.password=YourSuperSecretPassphrase # Plaintext passphrase to
> decrypt key
> nexusPassword=password # Your password on Apache's
> LDAP
> {noformat}
> We should change the build to prompt for a password if required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1226) Release process should not require putting passwords in plain text files
[
https://issues.apache.org/jira/browse/GEODE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1226:
-
Fix Version/s: 1.0.0-incubating.M3
> Release process should not require putting passwords in plain text files
>
>
> Key: GEODE-1226
> URL: https://issues.apache.org/jira/browse/GEODE-1226
> Project: Geode
> Issue Type: Task
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> Our current release steps require putting your apache password and gpg
> keyring password in a plain text file.
> https://cwiki.apache.org/confluence/display/GEODE/Release+Steps
> {noformat}
> signing.password=YourSuperSecretPassphrase # Plaintext passphrase to
> decrypt key
> nexusPassword=password # Your password on Apache's
> LDAP
> {noformat}
> We should change the build to prompt for a password if required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1206) DiskStoreCommandsDUnitTest.testCreateDiskStore
[ https://issues.apache.org/jira/browse/GEODE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1206: - Component/s: management > DiskStoreCommandsDUnitTest.testCreateDiskStore > -- > > Key: GEODE-1206 > URL: https://issues.apache.org/jira/browse/GEODE-1206 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jinmei Liao > Labels: CI > > Geode_develop_DistributedTests/2206/ > Revision: 616bc27de8621224a9c7fba19a84dfc4eb4d520f > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase$1.call > in VM 0 running on Host cc1-rh6.gemstone.com with 4 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:439) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:381) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:346) > at > com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.createDefaultSetup(CliCommandTestBase.java:97) > at > com.gemstone.gemfire.management.internal.cli.commands.DiskStoreCommandsDUnitTest.testCreateDiskStore(DiskStoreCommandsDUnitTest.java:835) > 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.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) > Caused by: com.gemstone.gemfire.management.ManagementException: > java.rmi.server.ExportException: Port already in use: 20598; nested exception > is: > java.net.BindExcept
[jira] [Updated] (GEODE-1207) WANSSLDUnitTest.testSenderSSLReceiverSSL
[ https://issues.apache.org/jira/browse/GEODE-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1207: - Component/s: wan > WANSSLDUnitTest.testSenderSSLReceiverSSL > > > Key: GEODE-1207 > URL: https://issues.apache.org/jira/browse/GEODE-1207 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Jinmei Liao > Labels: CI > > Geode_develop_DistributedTests/2224/ > Revision: 616bc27de8621224a9c7fba19a84dfc4eb4d520f > 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 2115 > [fatal 2016/04/11 07:01:29.111 PDT 0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] SSL Error in connecting > to peer /127.0.0.1[59,369]. > javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? > at > sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710) > at sun.security.ssl.InputRecord.read(InputRecord.java:527) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) > at > com.gemstone.gemfire.internal.SocketCreator.configureServerSSLSocket(SocketCreator.java:1055) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.accept(AcceptorImpl.java:1308) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.run(AcceptorImpl.java:1208) > at java.lang.Thread.run(Thread.java:745) > --- > Found suspect string in log4j at line 2128 > [error 2016/04/11 07:01:29.112 PDT 0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] Cache server: Unexpected > IOException from accept > --- > Found suspect string in log4j at line 2130 > [fatal 2016/04/11 07:01:29.112 PDT tid=0x1afa] > Uncaught exception in thread Thread[WAN Locator Discovery Thread,5,WAN > Locator Discovery Logger Group] > java.lang.ClassCastException: java.lang.Class cannot be cast to > com.gemstone.gemfire.cache.client.internal.locator.wan.RemoteLocatorJoinResponse > at > com.gemstone.gemfire.cache.client.internal.locator.wan.LocatorDiscovery.exchangeRemoteLocators(LocatorDiscovery.java:176) > at > com.gemstone.gemfire.cache.client.internal.locator.wan.LocatorDiscovery$RemoteLocatorDiscovery.run(LocatorDiscovery.java:119) > 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) > Stacktrace > 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 2115 > [fatal 2016/04/11 07:01:29.111 PDT 0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] SSL Error in connecting > to peer /127.0.0.1[59,369]. > javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? > at > sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710) > at sun.security.ssl.InputRecord.read(InputRecord.java:527) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387) > at > com.gemstone.gemfire.internal.SocketCreator.configureServerSSLSocket(SocketCreator.java:1055) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.accept(AcceptorImpl.java:1308) > at > com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.run(AcceptorImpl.java:1208) > at java.lang.Thread.run(Thread.java:745) > --- > Found suspect string in log4j at line 2128 > [error 2016/04/11 07:01:29.112 PDT 0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] Cache server: Unexpected > IOException from accept > --- > Found suspect string in log4j at line 2130 > [fatal 2016/04/11 07:0
[jira] [Resolved] (GEODE-336) Function extends Identifiable without specifying generics type for Identifiable
[
https://issues.apache.org/jira/browse/GEODE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-336.
-
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
Applied the suggested change.
> Function extends Identifiable without specifying generics type for
> Identifiable
> ---
>
> Key: GEODE-336
> URL: https://issues.apache.org/jira/browse/GEODE-336
> Project: Geode
> Issue Type: Bug
>Reporter: Konstantin Ignatyev
>Assignee: Dan Smith
>Priority: Critical
> Fix For: 1.0.0-incubating.M3
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Function interface is defined as
> public interface Function extends Identifiable {
>public String getId();
> ...}
> but that is not correct because Identifiable requires type parameter
> public interface Identifiable> extends Serializable {
>public T getId();
> }
> so when custom function is defined as
> class SomeFunction extends FunctionAdapter {
> override def getId:String = "SomeFunction-v1"
> }
> Java compiler tolerates that, but Scala compiler refuses to compile because
> because String is not compatible with 'Nothing' that is expected from getId
> because Function extends Identifiable without specifying type.
> Solution:
> define Function as
> public interface Function extends Identifiable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1088) shutdown-all should skip member dependency checks when restarted
[
https://issues.apache.org/jira/browse/GEODE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-1088.
--
Resolution: Won't Fix
It's not possible to skip the checks on restart without risking data loss or
ConflictingData erorrs, for the reasons I've outlined in the comments.
> shutdown-all should skip member dependency checks when restarted
>
>
> Key: GEODE-1088
> URL: https://issues.apache.org/jira/browse/GEODE-1088
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Soubhik Chakraborty
>
> Right now a Geode cluster when started, it waits for other members to start
> (for persistent regions only). These members are recorded when this member is
> stopped via individual stop or as part of shutdown-all.
> Because {code}shutdown-all{code} indicates the entire cluster is going down
> and if incoming traffic is stopped first, all cluster members can be
> gauranteed to be in a consistent state while its stopped. Therefore, members
> stopped cleanly using shutdown-all can skip member dependency checks while
> starting up.
> A more detailed proposition is listed in following ticket
> https://snappydata.atlassian.net/browse/SNAP-586
> I need team's help (esp. [~upthewaterspout], [~bschuchardt]) to share any
> insight, pitfalls they see in the proposition. Listing the proposed sequence
> of steps here for reference.
> There are 2 main cases we need to tackle.
> # make shutdown-all two phase (assuming all members are healthy)
> #* Phase-I ; stop network interfaces of all servers (via p2p messaging)
> #* wait for inflight operations to complete viz.
> #*# ongoing commits ? (note: due to n/w stop user will already see
> failure)
> #*# restrict new commits (n/w stopped already, so new commits won't
> arrive)
> #*# rollback existing transactions (as new commit/rollback won't come
> from user)
> #*# introduce an op counter and monitor it for zero on each member for
> non-tx operations (distribution stats counter can be used ?)
> #*# invoke disk sync procedure ?
> #* Phase-II : trigger shutdown on each of the VMs (via p2p messaging)
> #** right now during shutdown-all there are lots of chatter at jgroups
> level suspecting each other. should it be attempted to avoid ?
> #* skip member dependency check during restart by reading a recorded entry
> somewhere (data dictionary ?)
> # if one or more members are unreachable (hunged member), only way remains is
> to shutdown via script.
> #* Need to think more on how to recognize hunged members and what should be
> done before "kill -9" like record those member list.
> #* these recorded members should be started at last after starting all
> those members which did shutdown cleanly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (GEODE-1088) shutdown-all should skip member dependency checks when restarted
[
https://issues.apache.org/jira/browse/GEODE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith closed GEODE-1088.
Assignee: Dan Smith
> shutdown-all should skip member dependency checks when restarted
>
>
> Key: GEODE-1088
> URL: https://issues.apache.org/jira/browse/GEODE-1088
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Soubhik Chakraborty
>Assignee: Dan Smith
>
> Right now a Geode cluster when started, it waits for other members to start
> (for persistent regions only). These members are recorded when this member is
> stopped via individual stop or as part of shutdown-all.
> Because {code}shutdown-all{code} indicates the entire cluster is going down
> and if incoming traffic is stopped first, all cluster members can be
> gauranteed to be in a consistent state while its stopped. Therefore, members
> stopped cleanly using shutdown-all can skip member dependency checks while
> starting up.
> A more detailed proposition is listed in following ticket
> https://snappydata.atlassian.net/browse/SNAP-586
> I need team's help (esp. [~upthewaterspout], [~bschuchardt]) to share any
> insight, pitfalls they see in the proposition. Listing the proposed sequence
> of steps here for reference.
> There are 2 main cases we need to tackle.
> # make shutdown-all two phase (assuming all members are healthy)
> #* Phase-I ; stop network interfaces of all servers (via p2p messaging)
> #* wait for inflight operations to complete viz.
> #*# ongoing commits ? (note: due to n/w stop user will already see
> failure)
> #*# restrict new commits (n/w stopped already, so new commits won't
> arrive)
> #*# rollback existing transactions (as new commit/rollback won't come
> from user)
> #*# introduce an op counter and monitor it for zero on each member for
> non-tx operations (distribution stats counter can be used ?)
> #*# invoke disk sync procedure ?
> #* Phase-II : trigger shutdown on each of the VMs (via p2p messaging)
> #** right now during shutdown-all there are lots of chatter at jgroups
> level suspecting each other. should it be attempted to avoid ?
> #* skip member dependency check during restart by reading a recorded entry
> somewhere (data dictionary ?)
> # if one or more members are unreachable (hunged member), only way remains is
> to shutdown via script.
> #* Need to think more on how to recognize hunged members and what should be
> done before "kill -9" like record those member list.
> #* these recorded members should be started at last after starting all
> those members which did shutdown cleanly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1248) gfsh shutdown command does not shutdown members waiting for missing disk stores
Dan Smith created GEODE-1248:
Summary: gfsh shutdown command does not shutdown members waiting
for missing disk stores
Key: GEODE-1248
URL: https://issues.apache.org/jira/browse/GEODE-1248
Project: Geode
Issue Type: Bug
Components: persistence
Reporter: Dan Smith
The gfsh shutdown command fails to shutdown members that are in a state of
waiting for another member to recover the latest data. Instead, the shutdown
operation gets stuck waiting for a lock on the cache to shutdown the member.
Steps to reproduce.
1. Start a locator and two members
2. Create a REPLICATED_PERSISTENT region in gfsh
> create region --name="replicate" --type=REPLICATE_PERSISTEN
3. Do a put (probably not necessary)
> put --key="a" --value="a" --region=/replicate
4. shutdown within gfsh
> shutdown --include-locators=false
5. Start one member. It will get stuck waiting for other members to start.
6. shutdown within gfsh again.
> shutdown --include-locators=false
6. List members. You will see that the member is still up.
> list members
The end result after (6) is that the member is still up. In the stack dump, we
see the shutdown is blocked on the cache lock.
{noformat}
"Function Execution Processor1" #62 daemon prio=10 os_prio=0
tid=0x7fe988013800 nid=0xf83a waiting for monitor entry [0x7fe96e062000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
com.gemstone.gemfire.cache.CacheFactory.getAnyInstance(CacheFactory.java:292)
- waiting to lock <0x00071f13e170> (a java.lang.Class for
com.gemstone.gemfire.cache.CacheFactory)
at
com.gemstone.gemfire.management.internal.cli.functions.ShutDownFunction.execute(ShutDownFunction.java:46)
at
com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
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:655)
at
com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1115)
at java.lang.Thread.run(Thread.java:745)
"main" #1 prio=5 os_prio=0 tid=0x7fea0400a000 nid=0xf7dd in Object.wait()
[0x7fea0afa4000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at
com.gemstone.gemfire.internal.cache.persistence.PersistenceAdvisorImpl$MembershipChangeListener.waitForChange(PersistenceAdvisorImpl.java:1144)
- locked <0x00078b067058> (a
com.gemstone.gemfire.internal.cache.persistence.PersistenceAdvisorImpl$MembershipChangeListener)
at
com.gemstone.gemfire.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:875)
at
com.gemstone.gemfire.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:55)
at
com.gemstone.gemfire.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1389)
at
com.gemstone.gemfire.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1217)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3153)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3047)
at
com.gemstone.gemfire.internal.cache.xmlcache.RegionCreation.createRoot(RegionCreation.java:262)
at
com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.initializeRegions(CacheCreation.java:555)
at
com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:528)
at
com.gemstone.gemfire.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:353)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4319)
at
com.gemstone.gemfire.internal.cache.ClusterConfigurationLoader.applyClusterConfiguration(ClusterConfigurationLoader.java:141)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.requestAndApplySharedConfiguration(GemFireCacheImpl.java:1020)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1161)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:785)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:773)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:178)
- locked <0x00071f13e170> (a java.lang.Cl
[jira] [Resolved] (GEODE-978) CI Failure: CacheXml70GatewayDUnitTest.testGatewayReceiver failed with BindException
[
https://issues.apache.org/jira/browse/GEODE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-978.
-
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
> CI Failure: CacheXml70GatewayDUnitTest.testGatewayReceiver failed with
> BindException
>
>
> Key: GEODE-978
> URL: https://issues.apache.org/jira/browse/GEODE-978
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
> Labels: CI, Flaky
> Fix For: 1.0.0-incubating.M3
>
>
> Geode_develop_DistributedTests
> Private Build #1613 (Feb 14, 2016 7:09:43 AM)
> Revision: 28ee7c15426c3cc6b43204d28ccf9ff17cafdab4
> Error Message
> {noformat}
> com.gemstone.gemfire.GemFireIOException: While starting cache server
> CacheServer on port=54332 client subscription config policy=none client
> subscription config capacity=1 client subscription config overflow directory=.
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.GemFireIOException: While starting cache server
> CacheServer on port=54332 client subscription config policy=none client
> subscription config capacity=1 client subscription config overflow directory=.
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.startCacheServers(CacheCreation.java:653)
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:567)
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:355)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4385)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1361)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1173)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:797)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:179)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:170)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.createCache(CacheTestCase.java:111)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:280)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:259)
> at
> com.gemstone.gemfire.cache30.CacheXmlTestCase.testXml(CacheXmlTestCase.java:137)
> at
> com.gemstone.gemfire.cache30.CacheXmlTestCase.testXml(CacheXmlTestCase.java:114)
> at
> com.gemstone.gemfire.cache.CacheXml70GatewayDUnitTest.testGatewayReceiver(CacheXml70GatewayDUnitTest.java:112)
> 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.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.me
[jira] [Assigned] (GEODE-978) CI Failure: CacheXml70GatewayDUnitTest.testGatewayReceiver failed with BindException
[
https://issues.apache.org/jira/browse/GEODE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-978:
---
Assignee: Dan Smith
> CI Failure: CacheXml70GatewayDUnitTest.testGatewayReceiver failed with
> BindException
>
>
> Key: GEODE-978
> URL: https://issues.apache.org/jira/browse/GEODE-978
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: Dan Smith
> Labels: CI, Flaky
> Fix For: 1.0.0-incubating.M3
>
>
> Geode_develop_DistributedTests
> Private Build #1613 (Feb 14, 2016 7:09:43 AM)
> Revision: 28ee7c15426c3cc6b43204d28ccf9ff17cafdab4
> Error Message
> {noformat}
> com.gemstone.gemfire.GemFireIOException: While starting cache server
> CacheServer on port=54332 client subscription config policy=none client
> subscription config capacity=1 client subscription config overflow directory=.
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.GemFireIOException: While starting cache server
> CacheServer on port=54332 client subscription config policy=none client
> subscription config capacity=1 client subscription config overflow directory=.
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.startCacheServers(CacheCreation.java:653)
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:567)
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:355)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4385)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1361)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1173)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:797)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:179)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:170)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.createCache(CacheTestCase.java:111)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:280)
> at
> com.gemstone.gemfire.cache30.CacheTestCase.getCache(CacheTestCase.java:259)
> at
> com.gemstone.gemfire.cache30.CacheXmlTestCase.testXml(CacheXmlTestCase.java:137)
> at
> com.gemstone.gemfire.cache30.CacheXmlTestCase.testXml(CacheXmlTestCase.java:114)
> at
> com.gemstone.gemfire.cache.CacheXml70GatewayDUnitTest.testGatewayReceiver(CacheXml70GatewayDUnitTest.java:112)
> 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.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.mess
[jira] [Commented] (GEODE-1236) GFSH shutdown of a cache server causes JVM to exit before completing shutdown
[
https://issues.apache.org/jira/browse/GEODE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248618#comment-15248618
]
Dan Smith commented on GEODE-1236:
--
Does this affect members started with gfsh start server? I thought the server
had a main thread that was not a daemon?
> GFSH shutdown of a cache server causes JVM to exit before completing shutdown
> -
>
> Key: GEODE-1236
> URL: https://issues.apache.org/jira/browse/GEODE-1236
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management
>Reporter: Bruce Schuchardt
>
> Logs of a cache server being shut down by gfsh show that the
> DistributedSystem is not completing shutdown before the JVM exits. This is
> probably due to all non-daemon threads being terminated before shutdown
> completes. Other members see the "shut down" as a crash and if too many
> servers are "shut down" in this way at the same time it can cause other
> members to declare a loss of quorum and shut themselves down.
> Here is the log from a server shut down by gfsh:
> {noformat}
> [info 2016/04/15 14:45:20.614 UTC cacheserver4 Processor2> tid=0x67] Received GFSH shutdown. Shutting down member
> 10.0.16.168(cacheserver4:7984):14494
> [info 2016/04/15 14:45:20.664 UTC cacheserver4 Processor2> tid=0x67] GemFireCache[id = 965586344; isClosing = true;
> isShutDownAll = false; closingGatewayHubsByShutdownAll = false; created = Fri
> Apr 15 14:42:17 UTC 2016; server = true; copyOnRead = false; lockLease = 120;
> lockTimeout = 60]: Now closing.
> [info 2016/04/15 14:45:20.664 UTC cacheserver4 Processor2> tid=0x67] Resetting original MemoryPoolMXBean heap threshold
> bytes 0 on pool CMS Old Gen
> [info 2016/04/15 14:45:20.669 UTC cacheserver4 Processor2> tid=0x67] Bridge server on port 40,404 is shutting down.
> [info 2016/04/15 14:45:20.744 UTC cacheserver4 Processor2> tid=0x67] Rest Server on port 9,090 is shutting down
> [info 2016/04/15 14:45:20.745 UTC cacheserver4 Processor2> tid=0x67] Stopping the HTTP service...
> [info 2016/04/15 14:45:20.748 UTC cacheserver4 Processor2> tid=0x67] Stopped ServerConnector@a8c6d1d{HTTP/1.1}{0.0.0.0:9090}
> [info 2016/04/15 14:45:20.748 UTC cacheserver4 Processor2> tid=0x67] Destroying Spring FrameworkServlet 'gemfire-api'
> [info 2016/04/15 14:45:20.749 UTC cacheserver4 Processor2> tid=0x67] Closing WebApplicationContext for namespace
> 'gemfire-api-servlet': startup date [Fri Apr 15 14:42:20 UTC 2016]; root of
> context hierarchy
> [info 2016/04/15 14:45:20.750 UTC cacheserver4 Processor2> tid=0x67] Destroying singletons in
> org.springframework.beans.factory.support.DefaultListableBeanFactory@a7f0ab6:
> defining beans
> [org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,baseControllerAdvice,queryController,functionController,pdxCrudController,swaggerConfig,org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping#0,org.springframework.format.support.FormattingConversionServiceFactoryBean#0,org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter#0,org.springframework.web.servlet.handler.MappedInterceptor#0,org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver#0,org.springframework.web.servlet.mvc.annotation.ResponseStatusExceptionResolver#0,org.springframework.web.servlet.mvc.support.DefaultHandlerExceptionResolver#0,org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping,org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter,org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter,org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler#0,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping#0,contentNegotiationManager,objectMapper,org.springframework.context.annotation.ConfigurationClassPostProcessor.importAwareProcessor,classOrApiAnnotationResourceGrouping,swaggerCache,defaultSwaggerController,springSwaggerConfig,springSwaggerModelConfig,swaggerRequestMappingHandlerMappings,defaultResourceGroupingStrategy,defaultExcludeAnnotations,defaultSwaggerPathProvider,defaultIgnorableParameterTypes,defaultResponseMessages,defaultParameterDataTypes,jacksonScalaSupport,swaggerApiResourceListing,swaggerGlobalSettings,apiListingReferenceScanner,apiPathProvider];
> root of factory hierarchy
> [info 2016/04/15 14:45:20.794 UTC cacheserver4 Processor2> tid=0x67] Stopped
> o.e.j.w.WebAppContext@4afbb6c2{/gemfire-api,file:/var/vcap/store/server/GemFire_root/services/http/0.0.0.0_9090_gemfire-api/webapp/,UNAVAIL
[jira] [Assigned] (GEODE-1259) Required gradle is 2.3 but the wrapper is targeting 2.8
[ https://issues.apache.org/jira/browse/GEODE-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1259: Assignee: Dan Smith > Required gradle is 2.3 but the wrapper is targeting 2.8 > --- > > Key: GEODE-1259 > URL: https://issues.apache.org/jira/browse/GEODE-1259 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Roman Shaposhnik >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > This needs to be fixed since Gradle 2.7 (and I suspect earlier versions) are > failing the build with a very cryptic notice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1259) Required gradle is 2.3 but the wrapper is targeting 2.8
[ https://issues.apache.org/jira/browse/GEODE-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250221#comment-15250221 ] Dan Smith commented on GEODE-1259: -- BUILDING.md also mentions gradle 2.3. That should get updated. > Required gradle is 2.3 but the wrapper is targeting 2.8 > --- > > Key: GEODE-1259 > URL: https://issues.apache.org/jira/browse/GEODE-1259 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Roman Shaposhnik > Fix For: 1.0.0-incubating.M3 > > > This needs to be fixed since Gradle 2.7 (and I suspect earlier versions) are > failing the build with a very cryptic notice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1259) Required gradle is 2.3 but the wrapper is targeting 2.8
[ https://issues.apache.org/jira/browse/GEODE-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250225#comment-15250225 ] Dan Smith commented on GEODE-1259: -- We already have a bug to update the version of gradle, we should make sure gradle is updated in *all* of the correct places at the same time. > Required gradle is 2.3 but the wrapper is targeting 2.8 > --- > > Key: GEODE-1259 > URL: https://issues.apache.org/jira/browse/GEODE-1259 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Roman Shaposhnik >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > This needs to be fixed since Gradle 2.7 (and I suspect earlier versions) are > failing the build with a very cryptic notice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1085) GRADLE UPDATE - Gradle bug defaults Language Level to 6 when IntelliJ imports project from gradle
[ https://issues.apache.org/jira/browse/GEODE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250324#comment-15250324 ] Dan Smith commented on GEODE-1085: -- The gradle issue looks like it is is fixed in 2.11 so if we upgrade gradle this should be fixed. > GRADLE UPDATE - Gradle bug defaults Language Level to 6 when IntelliJ imports > project from gradle > - > > Key: GEODE-1085 > URL: https://issues.apache.org/jira/browse/GEODE-1085 > Project: Geode > Issue Type: Bug > Components: build >Reporter: nabarun >Assignee: Dan Smith > > When the project is imported into IntelliJ IDEA, the gradle plugin defaults > the language level to 6 ignore the setting in the gradle files. [level - 8] > This is a known bug and also reported in GRADLE's JIRA page > https://issues.gradle.org/browse/GRADLE-2198 > and in IntelliJ JIRA page > https://youtrack.jetbrains.com/issue/IDEA-96615#tab=Comments > Gradle must be updated when this fix comes in or if a work around can be > devised in the meantime. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1259) Required gradle is 2.3 but the wrapper is targeting 2.8
[ https://issues.apache.org/jira/browse/GEODE-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250325#comment-15250325 ] Dan Smith commented on GEODE-1259: -- The fix GEODE-1085 is to upgrade gradle - the latest version of gradle fixes the bug we were seeing. -Dan > Required gradle is 2.3 but the wrapper is targeting 2.8 > --- > > Key: GEODE-1259 > URL: https://issues.apache.org/jira/browse/GEODE-1259 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Roman Shaposhnik >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > This needs to be fixed since Gradle 2.7 (and I suspect earlier versions) are > failing the build with a very cryptic notice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1269) Support User Defined Aggregates (UDAs)
Dan Smith created GEODE-1269: Summary: Support User Defined Aggregates (UDAs) Key: GEODE-1269 URL: https://issues.apache.org/jira/browse/GEODE-1269 Project: Geode Issue Type: New Feature Components: querying Reporter: Dan Smith Add support for defining custom aggregate functions in geode queries. There is already some support for built in aggregates like sum and count that came as part of the initial geode code drop. Asif was working on supporting user defined aggregates, and that functionality is now available as a pull request: https://github.com/apache/incubator-geode/pull/130 This code needs to be reviewed, discussed on the mailing list, and any failures resolved before merging it to develop. The specification for these changes is here: https://cwiki.apache.org/confluence/display/GEODE/OQL+Aggregate+functions+and+UDA -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1269) Support User Defined Aggregates (UDAs)
[ https://issues.apache.org/jira/browse/GEODE-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250852#comment-15250852 ] Dan Smith commented on GEODE-1269: -- This pull request has been placed on the feature branch feature/GEODE-1269 > Support User Defined Aggregates (UDAs) > -- > > Key: GEODE-1269 > URL: https://issues.apache.org/jira/browse/GEODE-1269 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith > > Add support for defining custom aggregate functions in geode queries. > There is already some support for built in aggregates like sum and count that > came as part of the initial geode code drop. Asif was working on supporting > user defined aggregates, and that functionality is now available as a pull > request: > https://github.com/apache/incubator-geode/pull/130 > This code needs to be reviewed, discussed on the mailing list, and any > failures resolved before merging it to develop. > The specification for these changes is here: > https://cwiki.apache.org/confluence/display/GEODE/OQL+Aggregate+functions+and+UDA -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1269) Support User Defined Aggregates (UDAs)
[ https://issues.apache.org/jira/browse/GEODE-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250857#comment-15250857 ] Dan Smith commented on GEODE-1269: -- Currently failing tests on the feature branch: ResourceManagerDUnitTest. testRemoveDuringQuery BugJUnitTest. testBug32251 RegionJUnitTest. testQueryServiceInterface RegionJUnitTest. testShortcutMethods UDAPartitionedQueryDUnitTest. testUDANoGroupBy UDAPartitionedQueryDUnitTest. testUDAWithGroupBy IndexCreationJUnitTest. testIndexCreation QueryFromClauseCanonicalizationJUnitTest. testCanonicalizedFromClause CompactRangeIndexJUnitTest. testUpdateInProgressWithMethodInvocationInIndexClauseShouldNotThrowException AnalyzeSerializablesJUnitTest. testDataSerializables AnalyzeSerializablesJUnitTest. testSerializables > Support User Defined Aggregates (UDAs) > -- > > Key: GEODE-1269 > URL: https://issues.apache.org/jira/browse/GEODE-1269 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith > > Add support for defining custom aggregate functions in geode queries. > There is already some support for built in aggregates like sum and count that > came as part of the initial geode code drop. Asif was working on supporting > user defined aggregates, and that functionality is now available as a pull > request: > https://github.com/apache/incubator-geode/pull/130 > This code needs to be reviewed, discussed on the mailing list, and any > failures resolved before merging it to develop. > The specification for these changes is here: > https://cwiki.apache.org/confluence/display/GEODE/OQL+Aggregate+functions+and+UDA -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1266) Remove Pivotal copyright from RemoteCQTransactionDUnitTest.java
[ https://issues.apache.org/jira/browse/GEODE-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1266: Assignee: Dan Smith (was: Anthony Baker) > Remove Pivotal copyright from RemoteCQTransactionDUnitTest.java > --- > > Key: GEODE-1266 > URL: https://issues.apache.org/jira/browse/GEODE-1266 > Project: Geode > Issue Type: Bug > Components: cq >Affects Versions: 1.0.0-incubating.M2 >Reporter: Anthony Baker >Assignee: Dan Smith >Priority: Minor > Fix For: 1.0.0-incubating.M3 > > > The Pivotal copyright banner should be removed from > RemoteCQTransactionDUnitTest.java. > Location: > geode-cq/src/test/java/com/gemstone/gemfire/internal/cache/RemoteCQTransactionDUnitTest.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1271) Fix sha256 file format and extension
Dan Smith created GEODE-1271: Summary: Fix sha256 file format and extension Key: GEODE-1271 URL: https://issues.apache.org/jira/browse/GEODE-1271 Project: Geode Issue Type: Bug Reporter: Dan Smith The suffix for the SHA256 files should be sha256, not sha-256. The .sha256 file should work with 'sha256sum -c' The .md5 file should work with md5sum -c -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1271) Fix sha256 file format and extension
[ https://issues.apache.org/jira/browse/GEODE-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1271: - Component/s: build > Fix sha256 file format and extension > > > Key: GEODE-1271 > URL: https://issues.apache.org/jira/browse/GEODE-1271 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > The suffix for the SHA256 files should be sha256, not sha-256. > The .sha256 file should work with 'sha256sum -c' > The .md5 file should work with md5sum -c -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1271) Fix sha256 file format and extension
[ https://issues.apache.org/jira/browse/GEODE-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-1271: Assignee: Dan Smith > Fix sha256 file format and extension > > > Key: GEODE-1271 > URL: https://issues.apache.org/jira/browse/GEODE-1271 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > The suffix for the SHA256 files should be sha256, not sha-256. > The .sha256 file should work with 'sha256sum -c' > The .md5 file should work with md5sum -c -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1271) Fix sha256 file format and extension
[ https://issues.apache.org/jira/browse/GEODE-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1271: - Fix Version/s: 1.0.0-incubating.M3 > Fix sha256 file format and extension > > > Key: GEODE-1271 > URL: https://issues.apache.org/jira/browse/GEODE-1271 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > The suffix for the SHA256 files should be sha256, not sha-256. > The .sha256 file should work with 'sha256sum -c' > The .md5 file should work with md5sum -c -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1271) Fix sha256 file format and extension
[ https://issues.apache.org/jira/browse/GEODE-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1271. -- Resolution: Fixed > Fix sha256 file format and extension > > > Key: GEODE-1271 > URL: https://issues.apache.org/jira/browse/GEODE-1271 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > The suffix for the SHA256 files should be sha256, not sha-256. > The .sha256 file should work with 'sha256sum -c' > The .md5 file should work with md5sum -c -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1283) CI failure: CacheClientNotifierDUnitTest.testMultipleCacheServer
[
https://issues.apache.org/jira/browse/GEODE-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-1283.
--
Resolution: Fixed
> CI failure: CacheClientNotifierDUnitTest.testMultipleCacheServer
>
>
> Key: GEODE-1283
> URL: https://issues.apache.org/jira/browse/GEODE-1283
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Jens Deppe
> Labels: CI
>
> DistributedTests # 2328
> {noformat}
> Error Message
> 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 3601
> [fatal 2016/04/20 03:34:12.715 PDT 2> tid=0xe0] Uncaught exception in thread Thread[Handshaker
> 0.0.0.0/0.0.0.0:29540 Thread 2,5,Handshaker 0.0.0.0/0.0.0.0:29540]
> java.lang.IllegalThreadStateException
> at java.lang.Thread.start(Thread.java:705)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:570)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:385)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:281)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1594)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1373)
> 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)
> ---
> Found suspect string in log4j at line 4250
> [fatal 2016/04/20 03:34:13.261 PDT 4> tid=0xee] Uncaught exception in thread Thread[Handshaker
> 0.0.0.0/0.0.0.0:29540 Thread 4,5,Handshaker 0.0.0.0/0.0.0.0:29540]
> java.lang.IllegalThreadStateException
> at java.lang.Thread.start(Thread.java:705)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:570)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:385)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:281)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1594)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1373)
> 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)
> Stacktrace
> 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 3601
> [fatal 2016/04/20 03:34:12.715 PDT 2> tid=0xe0] Uncaught exception in thread Thread[Handshaker
> 0.0.0.0/0.0.0.0:29540 Thread 2,5,Handshaker 0.0.0.0/0.0.0.0:29540]
> java.lang.IllegalThreadStateException
> at java.lang.Thread.start(Thread.java:705)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientProxy.startOrResumeMessageDispatcher(CacheClientProxy.java:1826)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:570)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerGFEClient(CacheClientNotifier.java:385)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.registerClient(CacheClientNotifier.java:281)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1594)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$5.run(AcceptorImpl.java:1373)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> jav
[jira] [Updated] (GEODE-1303) CqServiceImpl.processEntryEvent(CacheEvent, Profile, Profile[], FilterRoutingInfo)
[
https://issues.apache.org/jira/browse/GEODE-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1303:
-
Component/s: (was: querying)
> CqServiceImpl.processEntryEvent(CacheEvent, Profile, Profile[],
> FilterRoutingInfo)
> --
>
> Key: GEODE-1303
> URL: https://issues.apache.org/jira/browse/GEODE-1303
> Project: Geode
> Issue Type: Improvement
> Components: offheap
>Reporter: Darrel Schneider
>
> Currently CqServerImpl.processEntryEvent copies each off-heap value it adds
> to cqUnfilteredEventsSet_newValue to the heap in this code:
> if (cqUnfilteredEventsSet_newValue.isEmpty() &&
> (event.getOperation().isCreate() || event.getOperation().isUpdate())) {
> Object newValue = entryEvent.getNewValue(); // TODO OFFHEAP: optimize
> by not copying the value on to the heap
> if (newValue != null) {
> //We have a new value to run the query on
> cqUnfilteredEventsSet_newValue.add(newValue);
> }
> }
> The cqUnfilteredEventsSet_newValue does not live past this method call. The
> values in it are later passed to evaluateQuery.
> It would be nice if we didn't need to copy the values to the heap in this
> code. It would be easy enough to retain them and then release everything in
> cqUnfilteredEventsSet_newValue in a finally block. But can evaluateQuery
> handle an offheap reference? If so then this would be a nice optimization for
> cqs on offheap regions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1218) jna should not be marked optional in the pom
[ https://issues.apache.org/jira/browse/GEODE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1218. -- Resolution: Fixed Fix Version/s: 1.0.0-incubating.M3 > jna should not be marked optional in the pom > > > Key: GEODE-1218 > URL: https://issues.apache.org/jira/browse/GEODE-1218 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > JNA is technically not required for geode to function, but it is needed for > common features like disk stores and off heap memory. It's better for this > jar to be bundled by default than for a user to need to discover that it > should be added to the classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1217) jansi should be marked as optional in the pom
[ https://issues.apache.org/jira/browse/GEODE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-1217. -- Resolution: Fixed Fix Version/s: 1.0.0-incubating.M3 > jansi should be marked as optional in the pom > - > > Key: GEODE-1217 > URL: https://issues.apache.org/jira/browse/GEODE-1217 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > jansi is only required for gfsh. The other gfsh related jars like jline and > spring-shell are marked as optional. jansi should be marked as optional as > well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-796) Stand alone Geode Server process did not return query results in gfsh
[ https://issues.apache.org/jira/browse/GEODE-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-796: Component/s: (was: querying) > Stand alone Geode Server process did not return query results in gfsh > - > > Key: GEODE-796 > URL: https://issues.apache.org/jira/browse/GEODE-796 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Luke Shannon > > I started a single server process with JMX enabled: > gfsh start server \ >--name=$SERVER_NAME \ >--use-cluster-configuration=false \ >--classpath=$CLASSPATH \ >--server-port=0 \ >--dir=$SERVER_DIR_LOCATION/$SERVER_NAME \ >--J=-Xms1g \ >--J=-Xmx1g \ >--J=-Dgemfire.jmx-manager=true \ >--J=-Dgemfire.jmx-manager-start=true \ >--properties-file=$CONF_DIR/gemfire.properties \ >--spring-xml-location=file:///$CONF_DIR/spring-cache.xml > I was able to connect to gfsh using the JMX-Manager argument for gfsh > connect. When I tried to list the members I got a 'null' back in gfsh. For a > query count(*) on a region, the correct right entry count was returned, > however select * just returned a 'null'. There were no errors in the server > logs. When I did the same config, however this time started a locator (and > referenced it in the server start command) I was able to connect using the > locator argument of connect. Everything worked as expected this time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1285) CI failure: DistributedAckOverflowRegionCCEOffHeapDUnitTest.testTombstones
[
https://issues.apache.org/jira/browse/GEODE-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1285:
-
Component/s: regions
> CI failure: DistributedAckOverflowRegionCCEOffHeapDUnitTest.testTombstones
> --
>
> Key: GEODE-1285
> URL: https://issues.apache.org/jira/browse/GEODE-1285
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Jens Deppe
> Labels: CI
>
> DistributedTests # 2334
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$288.run in VM 1 running on
> Host cc1-co.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$288.run in VM 1 running on
> Host cc1-co.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8580)
> at
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testTombstones(DistributedAckRegionCCEDUnitTest.java:304)
> 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.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)
> Caused by: junit.framework
[jira] [Updated] (GEODE-1285) CI failure: DistributedAckOverflowRegionCCEOffHeapDUnitTest.testTombstones
[
https://issues.apache.org/jira/browse/GEODE-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1285:
-
Assignee: Darrel Schneider
> CI failure: DistributedAckOverflowRegionCCEOffHeapDUnitTest.testTombstones
> --
>
> Key: GEODE-1285
> URL: https://issues.apache.org/jira/browse/GEODE-1285
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Jens Deppe
>Assignee: Darrel Schneider
> Labels: CI
>
> DistributedTests # 2334
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$288.run in VM 1 running on
> Host cc1-co.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$288.run in VM 1 running on
> Host cc1-co.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8580)
> at
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testTombstones(DistributedAckRegionCCEDUnitTest.java:304)
> 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.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
[jira] [Commented] (GEODE-988) CI Failure: CqPerfUsingPoolDUnitTest.testMatchingCqs failed with AssertionFailedError
[
https://issues.apache.org/jira/browse/GEODE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258911#comment-15258911
]
Dan Smith commented on GEODE-988:
-
This test is still failing. With 06e920ede5618c89f4bc5837c8f85724e229ae1b, I
still see this failure:
{noformat}
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.cache.query.cq.dunit.CqQueryUsingPoolDUnitTest$24.run in
VM 1 running on Host cc4-rh6.gemstone.com with 4 VMs
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
at
com.gemstone.gemfire.cache.query.cq.dunit.CqQueryUsingPoolDUnitTest.validateCQ(CqQueryUsingPoolDUnitTest.java:984)
at
com.gemstone.gemfire.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest.testMatchingCqs(CqPerfUsingPoolDUnitTest.java:453)
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.GeneratedMethodAccessor277.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.GeneratedMethodAccessor276.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: Total Event Count mismatch
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.TestCase.assertEquals(TestCase.java:401)
at
com.gemstone.gemfire.cache.query.cq.dunit.CqQueryUsingPoolDUnitTest$24.run2(CqQueryUsingPoolDUnitTest.java:1012)
at
com.gemstone.gemfire.cache30.CacheSerializableRunnable.run(CacheSerializableRunnable.java:66)
at sun.reflect.GeneratedMethodAccessor437.invoke(Unknown Source)
at
sun.reflect.Delegating
[jira] [Created] (GEODE-1316) Update @since tags to include GemFire or Geode in the version name
Dan Smith created GEODE-1316: Summary: Update @since tags to include GemFire or Geode in the version name Key: GEODE-1316 URL: https://issues.apache.org/jira/browse/GEODE-1316 Project: Geode Issue Type: Task Components: docs Reporter: Dan Smith Based on [this discussion|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3CCAFh%2B7k1nPayKdS--rvqG4uvB%3DjKnTibNqHkfFJf0Kkiy9wQ7bw%40mail.gmail.com%3E] on the mailing list, we want to update all of our \@since tags to be either Geode x.y.z or GemFire x.y.z, depending on when the new method was added to the public API. We need to go through all of the existing tags and update them to match this standard. Almost all of them should become \@since GemFire x.y.z unless they are 1.0 or 9.0, in which case they should probably be \@since Geode 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1316) Update @since tags to include GemFire or Geode in the version name
[ https://issues.apache.org/jira/browse/GEODE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1316: - Fix Version/s: 1.0.0-incubating.M3 > Update @since tags to include GemFire or Geode in the version name > -- > > Key: GEODE-1316 > URL: https://issues.apache.org/jira/browse/GEODE-1316 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > Based on [this > discussion|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3CCAFh%2B7k1nPayKdS--rvqG4uvB%3DjKnTibNqHkfFJf0Kkiy9wQ7bw%40mail.gmail.com%3E] > on the mailing list, we want to update all of our \@since tags to be either > Geode x.y.z or GemFire x.y.z, depending on when the new method was added to > the public API. > We need to go through all of the existing tags and update them to match this > standard. Almost all of them should become \@since GemFire x.y.z unless they > are 1.0 or 9.0, in which case they should probably be \@since Geode 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-409) CI cleanup
[ https://issues.apache.org/jira/browse/GEODE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-409. - Resolution: Fixed > CI cleanup > --- > > Key: GEODE-409 > URL: https://issues.apache.org/jira/browse/GEODE-409 > Project: Geode > Issue Type: Task > Components: general >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira > Labels: ci, squashaton > > CI cleanup master ticket > This is part of the "squashathon" effort to clean up CI failures. > Tickets fixed as part of this effort should have this ticket as parent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-409) CI cleanup
[ https://issues.apache.org/jira/browse/GEODE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-409: Fix Version/s: 1.0.0-incubating.M1 > CI cleanup > --- > > Key: GEODE-409 > URL: https://issues.apache.org/jira/browse/GEODE-409 > Project: Geode > Issue Type: Task > Components: general >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira > Labels: ci, squashaton > Fix For: 1.0.0-incubating.M1 > > > CI cleanup master ticket > This is part of the "squashathon" effort to clean up CI failures. > Tickets fixed as part of this effort should have this ticket as parent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (GEODE-409) CI cleanup
[ https://issues.apache.org/jira/browse/GEODE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith closed GEODE-409. --- This squashathon was finished a long time ago. > CI cleanup > --- > > Key: GEODE-409 > URL: https://issues.apache.org/jira/browse/GEODE-409 > Project: Geode > Issue Type: Task > Components: general >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira > Labels: ci, squashaton > Fix For: 1.0.0-incubating.M1 > > > CI cleanup master ticket > This is part of the "squashathon" effort to clean up CI failures. > Tickets fixed as part of this effort should have this ticket as parent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-10) HDFS Integration
[ https://issues.apache.org/jira/browse/GEODE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260925#comment-15260925 ] Dan Smith commented on GEODE-10: This code has all been removed from develop. I created a feature branch - feature/GEODE-10, which has all of the code added back on for anyone who wants to pick this up and get this code cleaned up. Before this can be integrated back with develop: * The tests should pass consistently * This code should be refactored into a separate subproject, rather than just a whole bunch of changes to geode-core * The overall spec should be discussed and approved of by the dev list. I believe this code was working, far as writing changes to HDFS and reading from HDFS on gets and iterations. I'm not sure the whole concept of "operational data" mentioned in the attached PDF was ever completely worked out, or if any InputFormat to read the data from HDFS was ever finished. > HDFS Integration > > > Key: GEODE-10 > URL: https://issues.apache.org/jira/browse/GEODE-10 > Project: Geode > Issue Type: New Feature > Components: hdfs >Reporter: Dan Smith >Assignee: Ashvin > Attachments: GEODE-HDFSPersistence-Draft-060715-2109-21516.pdf > > > Ability to persist data on HDFS had been under development for GemFire. It > was part of the latest code drop, GEODE-8. As part of this feature we are > proposing some changes to the HdfsStore management API (see attached doc for > details). > # The current API has nested configuration for compaction and async queue. > This nested structure forces user to execute multiple steps to manage a > store. It also does not seem to be consistent with other management APIs > # Some member names in current API are confusing > HDFS Integration: Geode as a transactional layer that microbatches data out > to Hadoop. This capability makes Geode a NoSQL store that can sit on top of > Hadoop and parallelize the process of moving data from the in memory tier > into Hadoop, making it very useful for capturing and processing fast data > while making it available for Hadoop jobs relatively quickly. The key > requirements being met here are > # Ingest data into HDFS parallely > # Cache bloom filters and allow fast lookups of individual elements > # Have programmable policies for deciding what stays in memory > # Roll files in HDFS > # Index data that is in memory > # Have expiration policies that allows the transactional set to decay out > older data > # Solution needs to support replicated and partitioned regions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
