[jira] [Commented] (GEODE-2517) Data transfer of size > 2GB from server to client results in a hang and eventual timeout exception
[
https://issues.apache.org/jira/browse/GEODE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890538#comment-15890538
]
Bruce Schuchardt commented on GEODE-2517:
-
[~nnag] can you suggest a way to make #4, forcing a chunk to be large, happen?
> Data transfer of size > 2GB from server to client results in a hang and
> eventual timeout exception
> --
>
> Key: GEODE-2517
> URL: https://issues.apache.org/jira/browse/GEODE-2517
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.1.0
>Reporter: nabarun
>
> *Situation*:
> 1. Create a server and client.
> 2. Fill the server with a large amount of data.
> 3. Create a query that will result in over 600,000 entries as result.
> 4. Chunk the result set in such a way that one chunk will result in a size
> greater than 2GB
> 5. Execute the query from the client.
> *Expected*:
> Message too large exception.
> *Cause / Fix for the issue*:
> If the number of parts to be transmitted is one then in sendBytes()
> {code:title=Message.java}
> for (int i = 0; i < this.numberOfParts; i++) {
> Part part = this.partsList[i];
> headerLen += PART_HEADER_SIZE;
> totalPartLen += part.getLength();
> }
> {code}
> * Here the part.getLength() is an int, so if the size is greater than 2GB we
> have already overflowed the int barrier and we are putting a negative value
> in totalPartLen
> so when we do the below check :
> {code:title=Message.java}
> if ((headerLen + totalPartLen) > Integer.MAX_VALUE) {
> throw new MessageTooLargeException(
> "Message size (" + (headerLen + totalPartLen) + ") exceeds
> maximum integer value");
> }
> {code}
> The comparison is between a negative number and positive number
> [Integer.MAX_VALUE] hence it will always skip this loop.
> and ultimately result in this exception.
> {noformat}
> java.io.IOException: Part length ( -508,098,123 ) and number of parts ( 1 )
> inconsistent
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.readPayloadFields(Message.java:836)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ChunkedMessage.readChunk(ChunkedMessage.java:276)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ChunkedMessage.receiveChunk(ChunkedMessage.java:220)
> at
> com.gemstone.gemfire.cache.client.internal.ExecuteRegionFunctionOp$ExecuteRegionFunctionOpImpl.processResponse(ExecuteRegionFunctionOp.java:482)
> at
> com.gemstone.gemfire.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:215)
> at
> com.gemstone.gemfire.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:153)
> at
> com.gemstone.gemfire.cache.client.internal.AbstractOp.attempt(AbstractOp.java:369)
> at
> com.gemstone.gemfire.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:252)
> at
> com.gemstone.gemfire.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:319)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:933)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:158)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:716)
> at
> com.gemstone.gemfire.cache.client.internal.ExecuteRegionFunctionOp.execute(ExecuteRegionFunctionOp.java:159)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.executeFunction(ServerRegionProxy.java:801)
> at
> com.gemstone.gemfire.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:212)
> at
> com.gemstone.gemfire.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:165)
> at
> com.gemstone.gemfire.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:363)
> at com.bookshop.buslogic.TestClient.run(TestClient.java:40)
> at com.bookshop.buslogic.TestClient.main(TestClient.java:21)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2569) Unhelpful log message
Bruce Schuchardt created GEODE-2569: --- Summary: Unhelpful log message Key: GEODE-2569 URL: https://issues.apache.org/jira/browse/GEODE-2569 Project: Geode Issue Type: Bug Components: membership, messaging Reporter: Bruce Schuchardt I found this in a log file: Unable to form a TCP/IP connection to null in over 31 seconds Just prior to this the same thread logged this: Unable to form a TCP/IP connection to 10.32.109.100(15954):48987 in over 31 seconds The member mentioned was being removed from the membership view in another thread during this time and nothing malfunctioned, but it isn't useful to print the message with "null" in it. We should supress that message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2569) Unhelpful log message
[ https://issues.apache.org/jira/browse/GEODE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2569: Priority: Trivial (was: Major) > Unhelpful log message > - > > Key: GEODE-2569 > URL: https://issues.apache.org/jira/browse/GEODE-2569 > Project: Geode > Issue Type: Bug > Components: membership, messaging >Reporter: Bruce Schuchardt >Priority: Trivial > > I found this in a log file: > Unable to form a TCP/IP connection to null in over 31 seconds > Just prior to this the same thread logged this: > Unable to form a TCP/IP connection to 10.32.109.100(15954):48987 in over > 31 seconds > The member mentioned was being removed from the membership view in another > thread during this time and nothing malfunctioned, but it isn't useful to > print the message with "null" in it. We should supress that message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2413) peer-to-peer authentication: Peer need to re-authenticate coordinator while accepting view message
[ https://issues.apache.org/jira/browse/GEODE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891223#comment-15891223 ] Bruce Schuchardt commented on GEODE-2413: - Hitesh, I think you need to clarify whether this is the new encrypted UDP communications or the Geode security authentication service. I think you're talking about the new encrypted UDP communications. This is causing confusion. > peer-to-peer authentication: Peer need to re-authenticate coordinator while > accepting view message > -- > > Key: GEODE-2413 > URL: https://issues.apache.org/jira/browse/GEODE-2413 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Hitesh Khamesra >Assignee: Hitesh Khamesra > > In peer-to-peer authentication, coordinator authenticates the joining member. > Then coordinator includes that new member in the cluster and sends new view > message. This view message should include coordinator's credential so that > joining member can authenticate coordinator as well (i.e. mutual > authentication) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2413) peer-to-peer authentication: Peer need to re-authenticate coordinator while accepting view message
[ https://issues.apache.org/jira/browse/GEODE-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891261#comment-15891261 ] Bruce Schuchardt commented on GEODE-2413: - thanks for the clarification [~hiteshkh25]. It looks like we are sending the credential but are not having it checked in GMSJoinLeave.processViewMessage(). > peer-to-peer authentication: Peer need to re-authenticate coordinator while > accepting view message > -- > > Key: GEODE-2413 > URL: https://issues.apache.org/jira/browse/GEODE-2413 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Hitesh Khamesra >Assignee: Hitesh Khamesra > > In peer-to-peer authentication, coordinator authenticates the joining member. > Then coordinator includes that new member in the cluster and sends new view > message. This view message should include coordinator's credential so that > joining member can authenticate coordinator as well (i.e. mutual > authentication) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-1793) Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
[
https://issues.apache.org/jira/browse/GEODE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893251#comment-15893251
]
Bruce Schuchardt commented on GEODE-1793:
-
I managed to get this test to fail & see that the second locator, in vm_2, was
supposed to shut down but instead it created its own cluster:
{noformat}
[vm2] [info 2017/03/02 15:19:56.969 PST
tid=0x13] Starting membership services
[vm2] [info 2017/03/02 15:19:56.979 PST
tid=0x13] JGroups channel created (took 9ms)
[vm2] [info 2017/03/02 15:19:56.980 PST
tid=0x13] GemFire P2P Listener started on /10.118.32.92:39824
[vm2] [info 2017/03/02 15:19:56.980 PST tid=0x21c] Started failure detection server thread on /10.118.32.92:59150.
[vm2] [info 2017/03/02 15:19:56.980 PST
tid=0x13] Peer locator is connecting to local membership services with ID
trout(2830:locator):32771
[vm2] [info 2017/03/02 15:19:57.164 PST
tid=0x13] This member is becoming the membership coordinator with address
trout(2830:locator):32771
{noformat}
It was correctly configured with two locator addresses and its SSL
configuration appeared to be okay. The other locator, in vm_1, correctly had
SSL disabled. The SSL locator was unable to recover from the non-SSL locator:
{noformat}
[vm2] [info 2017/03/02 15:19:56.961 PST
tid=0x13] GemFire peer location service starting. Other locators:
trout.gemstone.com[46843] Locators preferred as coordinators: false Network
partition detection enabled: false View persistence file: locator0view.dat
[vm2] [info 2017/03/02 15:19:56.961 PST
tid=0x13] Peer locator attempting to recover from
trout.gemstone.com/10.118.32.92:46843
[vm2] [info 2017/03/02 15:19:56.963 PST
tid=0x13] Peer locator was unable to recover state from this locator
[vm2] [info 2017/03/02 15:19:56.963 PST
tid=0x13] recovery file not found:
/export/trout1/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/dunit/vm2/locator0view.dat
[vm2] [info 2017/03/02 15:19:56.963 PST
tid=0x13] Starting distributed system
{noformat}
So this appears to be a problem with Geode, not the test. It is the Geode
functionality that is "flaky", working most of the time but not 100%.
> Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
> ---
>
> Key: GEODE-1793
> URL: https://issues.apache.org/jira/browse/GEODE-1793
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Udo Kohlmeyer
>Assignee: Galen O'Sullivan
>Priority: Minor
>
> This test fails due to something not cleaning itself properly. Undetermined
> what the problem is, but it will run perfectly by itself everytime, but once
> run inside of the TestClass it fails
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-1793) Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
[ https://issues.apache.org/jira/browse/GEODE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893271#comment-15893271 ] Bruce Schuchardt commented on GEODE-1793: - In another run with modified logging I can see that the SSL locator did not see an SSLHandshakeException as expected but merely an IOException [vm2] [info 2017/03/02 15:40:00.701 PST tid=0x13] Peer locator could not recover membership view from trout.gemstone.com/10.118.32.92:38254: Connection reset So this appears to be an inconsistency in SSL implementations used by the JVM. > Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL > --- > > Key: GEODE-1793 > URL: https://issues.apache.org/jira/browse/GEODE-1793 > Project: Geode > Issue Type: Bug > Components: locator >Reporter: Udo Kohlmeyer >Assignee: Galen O'Sullivan >Priority: Minor > > This test fails due to something not cleaning itself properly. Undetermined > what the problem is, but it will run perfectly by itself everytime, but once > run inside of the TestClass it fails -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2542) LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode Nightly Build
[
https://issues.apache.org/jira/browse/GEODE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2542.
-
Resolution: Fixed
Fix Version/s: 1.2.0
commit 0bdfd0e35d8c02f23082f23c2c3552678ccd7421
Author: Bruce Schuchardt
Date: Thu Mar 16 10:15:06 2017 -0700
GEODE-2542 LocatorDUnitTest and LocatorUDPSecurityDUnitTest flakyness
The fix for GEODE-1793 removed the short join-timeouts from this test class
that caused periodic failure to join the distributed system.
> LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode
> Nightly Build
> ---
>
> Key: GEODE-2542
> URL: https://issues.apache.org/jira/browse/GEODE-2542
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Kirk Lund
> Labels: Flaky
> Fix For: 1.2.0
>
>
> testMultipleLocators:
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> asf919.gq1.ygridcore.net with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:280)
> at
> org.apache.geode.distributed.LocatorDUnitTest.testMultipleLocators(LocatorDUnitTest.java:1567)
> 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:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
[jira] [Created] (GEODE-2684) org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup
Bruce Schuchardt created GEODE-2684: --- Summary: org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup Key: GEODE-2684 URL: https://issues.apache.org/jira/browse/GEODE-2684 Project: Geode Issue Type: Bug Components: membership Reporter: Bruce Schuchardt These classes contain a lot of commented-out code, poorly named methods and incorrect calculations that need to be cleaned up. For instance, Connection contains this: short aShort = -1; bytes[x] = (byte)(aShort & 0xff / 0x100); bytes[x+1] = (byte)(aShort & 0xff); which is incorrect and results in bytes[x] being zero when the intent is for it to be 255. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2709) modify backward-compatibility support to work better with geode
Bruce Schuchardt created GEODE-2709: --- Summary: modify backward-compatibility support to work better with geode Key: GEODE-2709 URL: https://issues.apache.org/jira/browse/GEODE-2709 Project: Geode Issue Type: Improvement Components: serialization Reporter: Bruce Schuchardt Backward-compatibility support currently pays attention to a version's Product name and its compareTo method pays attention to the major/minor/etc numerals. This is an artifact of the GemFireXD effort at Pivotal a few years ago and should be removed. The Product name is no longer needed at all and compareTo should just compare the version ordinals. All places that compare versions should be scrutinized to make sure this change doesn't break anything. All methods with names beginning with toDataPre_ or fromDataPre_ need to be changed to remove the product name and the sanctionedDataSerializables.txt database needs to be updated to have these new method names and fingerprints (generated by the AnalyzeSerializablesJUnitTest). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (GEODE-2653) GMSJoinLeaveJUnitTest.testRemoveMember fails with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-2653:
---
Assignee: Galen O'Sullivan
> GMSJoinLeaveJUnitTest.testRemoveMember fails with AssertionError
>
>
> Key: GEODE-2653
> URL: https://issues.apache.org/jira/browse/GEODE-2653
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Reporter: Kirk Lund
>Assignee: Galen O'Sullivan
> Labels: Flaky
>
> Intermittent failure stack:
> {noformat}
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeaveJUnitTest
> > testRemoveMember FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeaveJUnitTest.testRemoveMember(GMSJoinLeaveJUnitTest.java:337)
> {noformat}
> This test looks like it's flaky due to the Thread sleep:
> {noformat}
> @Test
> public void testRemoveMember() throws Exception {
> initMocks();
> prepareAndInstallView(mockMembers[0], createMemberList(mockMembers[0],
> gmsJoinLeaveMemberId));
> MethodExecuted removeMessageSent = new MethodExecuted();
>
> when(messenger.send(any(RemoveMemberMessage.class))).thenAnswer(removeMessageSent);
> gmsJoinLeave.remove(mockMembers[0], "removing for test");
> Thread.sleep(ServiceConfig.MEMBER_REQUEST_COLLECTION_INTERVAL * 2);
> assertTrue(removeMessageSent.methodExecuted);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2718) inconsistent reads during network partition
[ https://issues.apache.org/jira/browse/GEODE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943608#comment-15943608 ] Bruce Schuchardt commented on GEODE-2718: - The membership service will need to deliver viewChanged notification to membership listeners in order for BucketRegion listeners to know if data loss occurred in a single view change. Currently they get memberCrashed notifications for individual members but have no way of knowing if redundant copies of buckets were also lost in the same view. > inconsistent reads during network partition > --- > > Key: GEODE-2718 > URL: https://issues.apache.org/jira/browse/GEODE-2718 > Project: Geode > Issue Type: Bug > Components: membership, regions >Reporter: Swapnil Bawaskar > > non-persistent partitioned regions exhibit the following behavior: > In the event of a network partition where all copies of a bucket end up on > the losing side, a get() operation returns a null. A null can signify that > the key did not exist, so we should be more explicit about the network > partition and throw an error like PartitionOfflineException (which is thrown > if the region was persistent). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2724) NPE shutting down locator
Bruce Schuchardt created GEODE-2724:
---
Summary: NPE shutting down locator
Key: GEODE-2724
URL: https://issues.apache.org/jira/browse/GEODE-2724
Project: Geode
Issue Type: Bug
Components: pulse
Reporter: Bruce Schuchardt
Locator shutdown threw an NPE when stopping a Jetty server in Pulse code:
{code}
[warning 2017/03/28 08:56:25.493 IST locator1 tid=0x4a] Failed to
stop the HTTP service because: null
java.lang.NullPointerException
at
org.apache.geode.tools.pulse.internal.data.Repository.removeAllClusters(Repository.java:225)
at
org.apache.geode.tools.pulse.internal.PulseAppListener.contextDestroyed(PulseAppListener.java:84)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:843)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:543)
at
org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:824)
at
org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:353)
at
org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1385)
at
org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1349)
at
org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:872)
at
org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:269)
at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:541)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
at org.eclipse.jetty.server.Server.doStop(Server.java:476)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.apache.geode.management.internal.ManagementAgent.stopHttpService(ManagementAgent.java:328)
at
org.apache.geode.management.internal.ManagementAgent.stopAgent(ManagementAgent.java:156)
at
org.apache.geode.management.internal.SystemManagementService.close(SystemManagementService.java:265)
at
org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheRemoval(ManagementAdapter.java:735)
at
org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:117)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2146)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:536)
at
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2149)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1314)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:964)
at
org.apache.geode.management.internal.beans.MemberMBeanBridge$1.run(MemberMBeanBridge.java:1000)
at java.lang.Thread.run(Thread.java:745)
[error 2017/03/28 08:56:25.494 IST locator1 tid=0x4a] Failed to
properly release resources held by the HTTP service: !STOPPED
java.lang.IllegalStateException: !STOPPED
at
org.eclipse.jetty.server.handler.HandlerWrapper.destroy(HandlerWrapper.java:134)
at
org.apache.geode.management.internal.ManagementAgent.stopHttpService(ManagementAgent.java:333)
at
org.apache.geode.management.internal.ManagementAgent.stopAgent(ManagementAgent.java:156)
at
org.apache.geode.management.internal.SystemManagementService.close(SystemManagementService.java:265)
at
org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheRemoval(ManagementAdapter.java:735)
at
org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:117)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2146)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:536)
at
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2149)
at
org.apache.geode.distributed.internal.InternalDistribut
[jira] [Commented] (GEODE-2718) inconsistent reads during network partition
[ https://issues.apache.org/jira/browse/GEODE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949218#comment-15949218 ] Bruce Schuchardt commented on GEODE-2718: - I was talking with [~dschneider] about this ticket and he pointed out that the bucket advisors don't really need to see the view change. They just need to notice that data has been lost . I think the correct thing to do is take advantage of the redundancy zone (rack aware) feature of Geode to make sure you don't lose data in the event of a network partition. That will cause buckets to be backed up on a different rack. > inconsistent reads during network partition > --- > > Key: GEODE-2718 > URL: https://issues.apache.org/jira/browse/GEODE-2718 > Project: Geode > Issue Type: Bug > Components: membership, regions >Reporter: Swapnil Bawaskar > > non-persistent partitioned regions exhibit the following behavior: > In the event of a network partition where all copies of a bucket end up on > the losing side, a get() operation returns a null. A null can signify that > the key did not exist, so we should be more explicit about the network > partition and throw an error like PartitionOfflineException (which is thrown > if the region was persistent). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2718) inconsistent reads during network partition
[ https://issues.apache.org/jira/browse/GEODE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2718: Component/s: (was: membership) > inconsistent reads during network partition > --- > > Key: GEODE-2718 > URL: https://issues.apache.org/jira/browse/GEODE-2718 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Swapnil Bawaskar > > non-persistent partitioned regions exhibit the following behavior: > In the event of a network partition where all copies of a bucket end up on > the losing side, a get() operation returns a null. A null can signify that > the key did not exist, so we should be more explicit about the network > partition and throw an error like PartitionOfflineException (which is thrown > if the region was persistent). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2732) after auto-reconnect a server is restarted on the default port of 40404
Bruce Schuchardt created GEODE-2732:
---
Summary: after auto-reconnect a server is restarted on the default
port of 40404
Key: GEODE-2732
URL: https://issues.apache.org/jira/browse/GEODE-2732
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce Schuchardt
If you start a server using gfsh with the server defined in a cache.xml and you
specify the server's port Geode will ignore this setting in the event of an
auto-reconnect. I observed this in a GemFire deployment and the code in this
area hasn't changed in Apache Geode. By chance port 40404 was already in use
when the auto-reconnect occurred and an exception was thrown.
{noformat}
com.gemstone.gemfire.GemFireIOException: While starting bridge server
CacheServer on port=40404 client subscription config policy=none client
subscription config capacity=1 client subscription config overflow directory=.
at
com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:611)
at
com.gemstone.gemfire.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:340)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4263)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1178)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1020)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:684)
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2909)
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2655)
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1058)
at
com.gemstone.gemfire.distributed.internal.DistributionManager$MyListener.membershipFailure(DistributionManager.java:4822)
at
com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMembershipManager.uncleanShutdown(JGroupMembershipManager.java:2733)
at
com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMembershipManager$Puller.channelClosing(JGroupMembershipManager.java:1213)
at
com.gemstone.org.jgroups.JChannel$CloserThread.run(JChannel.java:1617)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:463)
at sun.nio.ch.Net.bind(Net.java:455)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:432)
at
com.gemstone.gemfire.internal.cache.BridgeServerImpl.start(BridgeServerImpl.java:342)
at
com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:607)
... 12 more
{noformat}
I think the fix is to get rid of the ThreadLocal storage of the port and bind
address in CacheServerLauncher. These variables are used by the XML parser to
configure a server. Gfsh sets them in its thread but they aren't available in
the auto-reconnect thread that rebuilds the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2684) org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup
[ https://issues.apache.org/jira/browse/GEODE-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2684: Issue Type: Task (was: Bug) > org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup > -- > > Key: GEODE-2684 > URL: https://issues.apache.org/jira/browse/GEODE-2684 > Project: Geode > Issue Type: Task > Components: membership >Reporter: Bruce Schuchardt > > These classes contain a lot of commented-out code, poorly named methods and > incorrect calculations that need to be cleaned up. For instance, Connection > contains this: > short aShort = -1; > bytes[x] = (byte)(aShort & 0xff / 0x100); > bytes[x+1] = (byte)(aShort & 0xff); > which is incorrect and results in bytes[x] being zero when the intent is for > it to be 255. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2754) CI failure: WanAutoDiscoveryDUnitTest
Bruce Schuchardt created GEODE-2754:
---
Summary: CI failure: WanAutoDiscoveryDUnitTest
Key: GEODE-2754
URL: https://issues.apache.org/jira/browse/GEODE-2754
Project: Geode
Issue Type: Bug
Components: wan
Reporter: Bruce Schuchardt
Two new tests in this class fail if the network happens to have a machine named
"unknown".
{noformat}
:geode-wan:distributedTest
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest >
testValidAndInvalidHostRemoteLocators FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest$$Lambda$1538/701582275.run
in VM 2 running on Host trout.gemstone.com with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
at org.apache.geode.test.dunit.VM.invoke(VM.java:292)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.testRemoteLocators(WanAutoDiscoveryDUnitTest.java:645)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.testValidAndInvalidHostRemoteLocators(WanAutoDiscoveryDUnitTest.java:622)
Caused by:
java.lang.AssertionError: expected:<1> but was:<2>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.geode.internal.cache.wan.WANTestBase.verifyPool(WANTestBase.java:3446)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.lambda$testRemoteLocators$1f02559b$1(WanAutoDiscoveryDUnitTest.java:645)
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest >
testInvalidHostRemoteLocators FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest$$Lambda$1538/701582275.run
in VM 2 running on Host trout.gemstone.com with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
at org.apache.geode.test.dunit.VM.invoke(VM.java:292)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.testRemoteLocators(WanAutoDiscoveryDUnitTest.java:645)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.testInvalidHostRemoteLocators(WanAutoDiscoveryDUnitTest.java:611)
Caused by:
java.lang.AssertionError: expected null, but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at
org.apache.geode.internal.cache.wan.WANTestBase.verifyPool(WANTestBase.java:3448)
at
org.apache.geode.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.lambda$testRemoteLocators$1f02559b$1(WanAutoDiscoveryDUnitTest.java:645)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-2732) after auto-reconnect a server is restarted on the default port of 40404
[
https://issues.apache.org/jira/browse/GEODE-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2732.
-
Resolution: Fixed
Fix Version/s: 1.2.0
> after auto-reconnect a server is restarted on the default port of 40404
> ---
>
> Key: GEODE-2732
> URL: https://issues.apache.org/jira/browse/GEODE-2732
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> If you start a server using gfsh with the server defined in a cache.xml and
> you specify the server's port Geode will ignore this setting in the event of
> an auto-reconnect. I observed this in a GemFire deployment and the code in
> this area hasn't changed in Apache Geode. By chance port 40404 was already
> in use when the auto-reconnect occurred and an exception was thrown.
> {noformat}
> com.gemstone.gemfire.GemFireIOException: While starting bridge server
> CacheServer on port=40404 client subscription config policy=none client
> subscription config capacity=1 client subscription config overflow directory=.
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:611)
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:340)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4263)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1178)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1020)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:684)
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2909)
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2655)
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1058)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$MyListener.membershipFailure(DistributionManager.java:4822)
> at
> com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMembershipManager.uncleanShutdown(JGroupMembershipManager.java:2733)
> at
> com.gemstone.gemfire.distributed.internal.membership.jgroup.JGroupMembershipManager$Puller.channelClosing(JGroupMembershipManager.java:1213)
> at
> com.gemstone.org.jgroups.JChannel$CloserThread.run(JChannel.java:1617)
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:463)
> at sun.nio.ch.Net.bind(Net.java:455)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:432)
> at
> com.gemstone.gemfire.internal.cache.BridgeServerImpl.start(BridgeServerImpl.java:342)
> at
> com.gemstone.gemfire.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:607)
> ... 12 more
> {noformat}
> I think the fix is to get rid of the ThreadLocal storage of the port and bind
> address in CacheServerLauncher. These variables are used by the XML parser
> to configure a server. Gfsh sets them in its thread but they aren't
> available in the auto-reconnect thread that rebuilds the cache.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-2684) org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup
[ https://issues.apache.org/jira/browse/GEODE-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2684. - Resolution: Fixed Fix Version/s: 1.2.0 > org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup > -- > > Key: GEODE-2684 > URL: https://issues.apache.org/jira/browse/GEODE-2684 > Project: Geode > Issue Type: Task > Components: membership >Reporter: Bruce Schuchardt > Fix For: 1.2.0 > > > These classes contain a lot of commented-out code, poorly named methods and > incorrect calculations that need to be cleaned up. For instance, Connection > contains this: > short aShort = -1; > bytes[x] = (byte)(aShort & 0xff / 0x100); > bytes[x+1] = (byte)(aShort & 0xff); > which is incorrect and results in bytes[x] being zero when the intent is for > it to be 255. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2751) UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer fails on Jenkins
[ https://issues.apache.org/jira/browse/GEODE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2751. - Resolution: Fixed Fix Version/s: 1.2.0 > UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer > fails on Jenkins > --- > > Key: GEODE-2751 > URL: https://issues.apache.org/jira/browse/GEODE-2751 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Hitesh Khamesra > Fix For: 1.2.0 > > > Error Message > org.junit.ComparisonFailure: > expected:<[67.195.81.156](15619):32...> but > was:<[asf912](15619):32...> > Stacktrace > org.junit.ComparisonFailure: > expected:<[67.195.81.156](15619):32...> but > was:<[asf912](15619):32...> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest.doTestSystemClientEventsInServer(UniversalMembershipListenerAdapterDUnitTest.java:946) > at > org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer(UniversalMembershipListenerAdapterDUnitTest.java:731) > 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:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.GeneratedMethodAccessor352.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > at sun.reflect.GeneratedMethodAccessor351.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispat
[jira] [Commented] (GEODE-2724) NPE shutting down locator
[
https://issues.apache.org/jira/browse/GEODE-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966681#comment-15966681
]
Bruce Schuchardt commented on GEODE-2724:
-
[~jstewart] this was from the Geode users mailing list. I'll forward the
conversation to you.
> NPE shutting down locator
> -
>
> Key: GEODE-2724
> URL: https://issues.apache.org/jira/browse/GEODE-2724
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Bruce Schuchardt
>
> Locator shutdown threw an NPE when stopping a Jetty server in Pulse code:
> {code}
> [warning 2017/03/28 08:56:25.493 IST locator1 tid=0x4a] Failed to
> stop the HTTP service because: null
> java.lang.NullPointerException
> at
> org.apache.geode.tools.pulse.internal.data.Repository.removeAllClusters(Repository.java:225)
> at
> org.apache.geode.tools.pulse.internal.PulseAppListener.contextDestroyed(PulseAppListener.java:84)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:843)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:543)
> at
> org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:824)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:353)
> at
> org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1385)
> at
> org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1349)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:872)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:269)
> at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:541)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
> at org.eclipse.jetty.server.Server.doStop(Server.java:476)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> at
> org.apache.geode.management.internal.ManagementAgent.stopHttpService(ManagementAgent.java:328)
> at
> org.apache.geode.management.internal.ManagementAgent.stopAgent(ManagementAgent.java:156)
> at
> org.apache.geode.management.internal.SystemManagementService.close(SystemManagementService.java:265)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheRemoval(ManagementAdapter.java:735)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:117)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2146)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:536)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2149)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1314)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:964)
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge$1.run(MemberMBeanBridge.java:1000)
> at java.lang.Thread.run(Thread.java:745)
> [error 2017/03/28 08:56:25.494 IST locator1 tid=0x4a] Failed to
> properly release resources held by the HTTP service: !STOPPED
> java.lang.IllegalStateException: !STOPPED
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.destroy(HandlerWrapper.java:134)
> at
> org.apache.geode.management.internal.ManagementAgent.stopHttpService(ManagementAgent.java:333)
> at
> org.apache.geode.management.internal.ManagementAgent.stopAgent(ManagementAgent.java:156)
> at
> org.apache.geode.management.internal.SystemManagementService.close(SystemManagementService.java:265)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheRemoval(ManagementAdapter.java:735)
> at
> org.apache.geode.management.internal.beans.ManagementListener.ha
[jira] [Comment Edited] (GEODE-2724) NPE shutting down locator
[
https://issues.apache.org/jira/browse/GEODE-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966681#comment-15966681
]
Bruce Schuchardt edited comment on GEODE-2724 at 4/12/17 9:35 PM:
--
[~jstewart] this was from the Geode users mailing list. I'll forward the
conversation to you.
Here are the instructions from the person who ran into the problem:
Steps:
1. Start locator
2. Start pulse
3. Do some activity in pulse [some clicks -- opening random tabs] [Don't logout]
3. Stop locator
4. Locator is still running in system even after message saying it was stopped
was (Author: bschuchardt):
[~jstewart] this was from the Geode users mailing list. I'll forward the
conversation to you.
> NPE shutting down locator
> -
>
> Key: GEODE-2724
> URL: https://issues.apache.org/jira/browse/GEODE-2724
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Bruce Schuchardt
>
> Locator shutdown threw an NPE when stopping a Jetty server in Pulse code:
> {code}
> [warning 2017/03/28 08:56:25.493 IST locator1 tid=0x4a] Failed to
> stop the HTTP service because: null
> java.lang.NullPointerException
> at
> org.apache.geode.tools.pulse.internal.data.Repository.removeAllClusters(Repository.java:225)
> at
> org.apache.geode.tools.pulse.internal.PulseAppListener.contextDestroyed(PulseAppListener.java:84)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:843)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:543)
> at
> org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:824)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:353)
> at
> org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1385)
> at
> org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1349)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:872)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:269)
> at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:541)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:143)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:161)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:73)
> at org.eclipse.jetty.server.Server.doStop(Server.java:476)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
> at
> org.apache.geode.management.internal.ManagementAgent.stopHttpService(ManagementAgent.java:328)
> at
> org.apache.geode.management.internal.ManagementAgent.stopAgent(ManagementAgent.java:156)
> at
> org.apache.geode.management.internal.SystemManagementService.close(SystemManagementService.java:265)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheRemoval(ManagementAdapter.java:735)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:117)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2146)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:536)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2149)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1314)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:964)
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge$1.run(MemberMBeanBridge.java:1000)
> at java.lang.Thread.run(Thread.java:745)
> [error 2017/03/28 08:56:25.494 IST locator1 tid=0x4a] Failed to
> properly release resources held by the HTTP service: !STOPPED
> java.lang.IllegalStateException: !STOPPED
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.destroy(HandlerWrapper.java:134)
> at
> org.apache.geode.management.internal.Manageme
[jira] [Commented] (GEODE-2734) Investigate/discuss message encoding
[ https://issues.apache.org/jira/browse/GEODE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968225#comment-15968225 ] Bruce Schuchardt commented on GEODE-2734: - I don't think this is something that should be discussed, though asking folks to pitch in names for consideration is a good idea. Instead of a discussion we need to benchmark proposed solutions and also consider writing one from scratch for Geode. See https://cwiki.apache.org/confluence/display/GEODE/Message+Serialization+and+Transmission > Investigate/discuss message encoding > > > Key: GEODE-2734 > URL: https://issues.apache.org/jira/browse/GEODE-2734 > Project: Geode > Issue Type: Sub-task > Components: messaging >Reporter: Brian Baynes > > Out of all the great ways to encode messages (Thrift, Protobuf, etc), which > should we use here? Let's discuss and come to consensus. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks.
[ https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968227#comment-15968227 ] Bruce Schuchardt commented on GEODE-2746: - Brian, would you create individual tickets for the different protocols. I think we're down to gRPC, Thrift and Avro. Then people can divide them up and test. Folks doing this work, please look at this document for some requirements (& feel free, of course to comment on the requirements). See https://cwiki.apache.org/confluence/display/GEODE/Message+Serialization+and+Transmission > Investigate and Evaluate Existing RPC frameworks. > - > > Key: GEODE-2746 > URL: https://issues.apache.org/jira/browse/GEODE-2746 > Project: Geode > Issue Type: Sub-task > Components: messaging >Reporter: Galen O'Sullivan > > There are several existing RPC frameworks for which you can define the > structure of your protocol and the tool will generate code for talking over > the wire, generally down to serialization of objects. > If one of those RPC frameworks does not fit all our requirements, we'll > design our own binary protocol. This protocol would define both what kind of > messages can be sent and how they are encoded on the wire. How we encode the > objects that we are sending in requests, however, could still be pluggable. > A few contenders: > * [BERT|http://bert-rpc.org] > * [thrift|https://thrift.apache.org/] > * [gRPC|http://www.grpc.io/] > * [Avro|https://avro.apache.org/] > These are two not-entirely-common features we will need to have: > * support for SSL/TLS, ability to connect to a server with IP & port. > * support for push messages from the server without polling (this is needed > for CQs). > This is one half of GEODE-2734. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2673) PartitionedRegionMultipleDUnitTest.testPartitionedRegionDestroyAndContainsAPI fails intermittently with ForcedDisconnectException
[
https://issues.apache.org/jira/browse/GEODE-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2673.
-
Resolution: Won't Fix
A ForcedDisconnectException in a distributed test indicates either a sick JVM,
often doing GC and sometimes on the metaspace, or an environmental problem such
as insufficient resources to run the host VM. As this test hasn't failed in
Geode Jenkins or any Pivotal-private concourse runs that I can find I have no
way of checking on the environment or the logs of this particular run.
If this test, or any other for that matter, fails with a
ForcedDisconnectException the machine hosting the run should be examined and
the logs of the failed test should be examined for GC activity.
> PartitionedRegionMultipleDUnitTest.testPartitionedRegionDestroyAndContainsAPI
> fails intermittently with ForcedDisconnectException
> -
>
> Key: GEODE-2673
> URL: https://issues.apache.org/jira/browse/GEODE-2673
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Reporter: Kirk Lund
> Labels: Flaky
>
> Test passes when run by itself:
> {noformat}
> ./gradlew -DdistributedTest.single=PartitionedRegionMultipleDUnitTest
> geode-core:distributedTest
> {noformat}
> But fails intermittently in precheckin:
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionMultipleDUnitTest >
> testPartitionedRegionDestroyAndContainsAPI FAILED
> java.lang.AssertionError: exception during 0
> at org.apache.geode.test.dunit.Assert.fail(Assert.java:60)
> at
> org.apache.geode.internal.cache.PartitionedRegionMultipleDUnitTest.testPartitionedRegionDestroyAndContainsAPI(PartitionedRegionMultipleDUnitTest.java:231)
> Caused by:
> java.lang.AssertionError: Validation failed for key =
> 0testPartitionedRegionDestroyAndContainsAPI3Value got = null
> 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 1807
> [fatal 2017/03/13 23:48:06.633 UTC
> tid=0xc5] Membership service failure: this member is no longer in the view
> but is initiating connections
> org.apache.geode.ForcedDisconnectException: this member is no longer in
> the view but is initiating connections
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2517)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:998)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:635)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1702)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1286)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> 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:390)
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1070)
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:785)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:74)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:72)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1601)
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1817)
> at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1729)
> at org.jgroups.protocols.TP.receive(TP.java:1654)
> at
> org.apache.geode.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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (GEODE-717) CI failure: RedisDistDUnitTest.testConcCreateDestroy
[ https://issues.apache.org/jira/browse/GEODE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-717: -- Assignee: (was: Dan Smith) > CI failure: RedisDistDUnitTest.testConcCreateDestroy > > > Key: GEODE-717 > URL: https://issues.apache.org/jira/browse/GEODE-717 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jianxia Chen > Labels: CI, Flaky > > Failed 1 times in the last 30 runs. Stability: 96 % > Error Message > dunit.RMIException: While invoking > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host > kuwait.gemstone.com with 4 VMs > Stacktrace > dunit.RMIException: While invoking > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host > kuwait.gemstone.com with 4 VMs > at dunit.VM.invoke(VM.java:369) > at dunit.VM.invoke(VM.java:312) > at dunit.VM.invoke(VM.java:280) > at > com.gemstone.gemfire.redis.RedisDistDUnitTest.setUp(RedisDistDUnitTest.java:94) > at junit.framework.TestCase.runBare(TestCase.java:139) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor33.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.GeneratedMethodAccessor32.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: java.lang.RuntimeException: Could not start Server > at > com.gemstone.gemfire.redis.GemFireRedisServer.start(GemFireRedisServer.java:387) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.startRedisServer(GemFireCacheImpl.java:1243) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1167) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:774) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:794) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:179) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:226) > at > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call(RedisDistDUnitTest.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native M
[jira] [Updated] (GEODE-717) CI failure: RedisDistDUnitTest.testConcCreateDestroy
[ https://issues.apache.org/jira/browse/GEODE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-717: --- Component/s: redis > CI failure: RedisDistDUnitTest.testConcCreateDestroy > > > Key: GEODE-717 > URL: https://issues.apache.org/jira/browse/GEODE-717 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jianxia Chen >Assignee: Dan Smith > Labels: CI, Flaky > > Failed 1 times in the last 30 runs. Stability: 96 % > Error Message > dunit.RMIException: While invoking > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host > kuwait.gemstone.com with 4 VMs > Stacktrace > dunit.RMIException: While invoking > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host > kuwait.gemstone.com with 4 VMs > at dunit.VM.invoke(VM.java:369) > at dunit.VM.invoke(VM.java:312) > at dunit.VM.invoke(VM.java:280) > at > com.gemstone.gemfire.redis.RedisDistDUnitTest.setUp(RedisDistDUnitTest.java:94) > at junit.framework.TestCase.runBare(TestCase.java:139) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor33.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.GeneratedMethodAccessor32.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: java.lang.RuntimeException: Could not start Server > at > com.gemstone.gemfire.redis.GemFireRedisServer.start(GemFireRedisServer.java:387) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.startRedisServer(GemFireCacheImpl.java:1243) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1167) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:774) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:794) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:179) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:226) > at > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call(RedisDistDUnitTest.java:89) > at sun.reflect.NativeMethodAccessorImpl.in
[jira] [Updated] (GEODE-576) CI Failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction
[
https://issues.apache.org/jira/browse/GEODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-576:
---
Component/s: (was: functions)
messaging
> CI Failure:
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction
>
>
> Key: GEODE-576
> URL: https://issues.apache.org/jira/browse/GEODE-576
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Barry Oglesby
> Labels: CI, Flaky
>
> Geode_develop_DistributedTests
> Private Build #612 (Nov 17, 2015 5:09:11 PM)
> Revision: 90b9a632b9738319fc7a7fddb93b6bef9ff57f7d
> Error Message
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> {noformat}
> Stacktrace
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> at dunit.AsyncInvocation.getResult(AsyncInvocation.java:195)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:121)
> 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.GeneratedMethodAccessor137.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.GeneratedMethodAccessor136.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: dunit.RMIException: While invoking
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest$2.run
> in VM 0 running on Host rooktwo.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM$2.run(VM.java:220)
> at java.lang.Thread.run(Thread.java:745)
> at dunit.AsyncInvocation.run(AsyncInvocation.java:209)
> Caused by:
> com.gemstone.gemfire.distrib
[jira] [Updated] (GEODE-516) GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-516:
---
Component/s: (was: gfsh)
messaging
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has
> NullPointerException
> -
>
> Key: GEODE-516
> URL: https://issues.apache.org/jira/browse/GEODE-516
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: xiaojian zhou
>Assignee: Jinmei Liao
> Labels: Flaky, ShowDeadlockCommand
>
> revision 0cc9d895b9f4465138d0fa223b0a0cadc1107893
> {noformat}
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.distributed.internal.deadlock.DeadlockDetector.prettyFormat(DeadlockDetector.java:151)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (GEODE-516) GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-516:
--
Assignee: (was: Jinmei Liao)
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has
> NullPointerException
> -
>
> Key: GEODE-516
> URL: https://issues.apache.org/jira/browse/GEODE-516
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: xiaojian zhou
> Labels: Flaky, ShowDeadlockCommand
>
> revision 0cc9d895b9f4465138d0fa223b0a0cadc1107893
> {noformat}
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.distributed.internal.deadlock.DeadlockDetector.prettyFormat(DeadlockDetector.java:151)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2151) PartitionedRegionLoadModelJUnitTest fails depending on /etc/hosts config
[
https://issues.apache.org/jira/browse/GEODE-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-2151:
Component/s: messaging
> PartitionedRegionLoadModelJUnitTest fails depending on /etc/hosts config
>
>
> Key: GEODE-2151
> URL: https://issues.apache.org/jira/browse/GEODE-2151
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Galen O'Sullivan
>
> I was getting the following error while running the unit tests:
> {code}
> org.apache.geode.internal.cache.partitioned.PartitionedRegionLoadModelJUnitTest
> > testRedundancySatisfactionPreferRemoteIp FAILED
> java.lang.AssertionError:
> expected:<[Create[member=192.168.1.50(41227):3,bucketId=0],
> Create[member=192.168.1.50(41227):3,bucketId=1],
> Create[member=192.168.1.50(41227):3,bucketId=2]]> but
> was:<[Create[member=192.168.1.50(41227):3,bucketId=0],
> Create[member=192.168.1.50(41227):1,bucketId=1],
> Create[member=192.168.1.50(41227):3,bucketId=2]]>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionLoadModelJUnitTest.testRedundancySatisfactionPreferRemoteIp(PartitionedRegionLoadModelJUnitTest.java:227)
> 2931 tests completed, 1 failed, 10 skipped
> {code}
> My `/etc/hosts` file had the following line:
> {code}
> 127.0.0.1 localhost gosullivan-mbpro
> {code}
> Changing it to this fixed the problem:
> {code}
> 127.0.0.1 localhost
> 255.255.255.255 broadcasthost
> ::1 localhost
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (GEODE-516) GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-516:
--
Assignee: Bruce Schuchardt
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has
> NullPointerException
> -
>
> Key: GEODE-516
> URL: https://issues.apache.org/jira/browse/GEODE-516
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: xiaojian zhou
>Assignee: Bruce Schuchardt
> Labels: Flaky, ShowDeadlockCommand
>
> revision 0cc9d895b9f4465138d0fa223b0a0cadc1107893
> {noformat}
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.distributed.internal.deadlock.DeadlockDetector.prettyFormat(DeadlockDetector.java:151)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (GEODE-576) CI Failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction
[
https://issues.apache.org/jira/browse/GEODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-576:
--
Assignee: Bruce Schuchardt
> CI Failure:
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction
>
>
> Key: GEODE-576
> URL: https://issues.apache.org/jira/browse/GEODE-576
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Barry Oglesby
>Assignee: Bruce Schuchardt
> Labels: CI, Flaky
>
> Geode_develop_DistributedTests
> Private Build #612 (Nov 17, 2015 5:09:11 PM)
> Revision: 90b9a632b9738319fc7a7fddb93b6bef9ff57f7d
> Error Message
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> {noformat}
> Stacktrace
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> at dunit.AsyncInvocation.getResult(AsyncInvocation.java:195)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:121)
> 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.GeneratedMethodAccessor137.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.GeneratedMethodAccessor136.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: dunit.RMIException: While invoking
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest$2.run
> in VM 0 running on Host rooktwo.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM$2.run(VM.java:220)
> at java.lang.Thread.run(Thread.java:745)
> at dunit.AsyncInvocation.run(AsyncInvocation.java:209)
> Caused by:
> com.gemstone.ge
[jira] [Assigned] (GEODE-510) Bug48571DUnitTest.testStatsMatchWithSize failed
[
https://issues.apache.org/jira/browse/GEODE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-510:
--
Assignee: (was: Hitesh Khamesra)
> Bug48571DUnitTest.testStatsMatchWithSize failed
> ---
>
> Key: GEODE-510
> URL: https://issues.apache.org/jira/browse/GEODE-510
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: xiaojian zhou
> Labels: CI, Flaky
> Fix For: 1.0.0-incubating.M3, 1.2.0
>
>
> revision d08e51d2eaa391fcda11cd18ee4413aa5fe6b80d
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.ha.Bug48571DUnitTest.createClientCache in
> VM 1 running on Host venezuela.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:170)
> at
> com.gemstone.gemfire.internal.cache.ha.Bug48571DUnitTest.testStatsMatchWithSize(Bug48571DUnitTest.java:99)
> 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.GeneratedMethodAccessor176.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.GeneratedMethodAccessor175.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:
> com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException:
> com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:199)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:531)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:775)
> at
> com.gemstone.gemfire
[jira] [Resolved] (GEODE-510) Bug48571DUnitTest.testStatsMatchWithSize failed
[
https://issues.apache.org/jira/browse/GEODE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-510.
Fix Version/s: 1.2.0
> Bug48571DUnitTest.testStatsMatchWithSize failed
> ---
>
> Key: GEODE-510
> URL: https://issues.apache.org/jira/browse/GEODE-510
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: xiaojian zhou
> Labels: CI, Flaky
> Fix For: 1.2.0, 1.0.0-incubating.M3
>
>
> revision d08e51d2eaa391fcda11cd18ee4413aa5fe6b80d
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.ha.Bug48571DUnitTest.createClientCache in
> VM 1 running on Host venezuela.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:170)
> at
> com.gemstone.gemfire.internal.cache.ha.Bug48571DUnitTest.testStatsMatchWithSize(Bug48571DUnitTest.java:99)
> 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.GeneratedMethodAccessor176.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.GeneratedMethodAccessor175.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:
> com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException:
> com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:199)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:531)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:775)
> at
> com.gemstone.gemfire.cache.client.interna
[jira] [Created] (GEODE-2804) Allow a locator host to be taken off line and replaced with a different machine having the same host name
Bruce Schuchardt created GEODE-2804: --- Summary: Allow a locator host to be taken off line and replaced with a different machine having the same host name Key: GEODE-2804 URL: https://issues.apache.org/jira/browse/GEODE-2804 Project: Geode Issue Type: Improvement Components: client/server, membership, native client Reporter: Bruce Schuchardt It is not unlikely that in a long-running system a machine hosting a locator will break down and need to be replace, or that a virtual machine hosting a locator will be stopped and restarted. In either case the machine may have a different IP address. Clients and servers currently cache the IP address of a locator and should be changed to re-resolve the host name if the address stops being usable. Servers currently cannot be started if they are given a host name that can not be resolved. They should be changed to allow this and start up if they are able to contact one or more of the other locators in their "locators" setting. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-2804) Allow a locator host to be taken off line and replaced with a different machine having the same host name
[ https://issues.apache.org/jira/browse/GEODE-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2804: Affects Version/s: 1.1.1 > Allow a locator host to be taken off line and replaced with a different > machine having the same host name > - > > Key: GEODE-2804 > URL: https://issues.apache.org/jira/browse/GEODE-2804 > Project: Geode > Issue Type: Improvement > Components: client/server, membership, native client >Affects Versions: 1.1.1 >Reporter: Bruce Schuchardt > > It is not unlikely that in a long-running system a machine hosting a locator > will break down and need to be replace, or that a virtual machine hosting a > locator will be stopped and restarted. In either case the machine may have a > different IP address. > Clients and servers currently cache the IP address of a locator and should be > changed to re-resolve the host name if the address stops being usable. > Servers currently cannot be started if they are given a host name that can > not be resolved. They should be changed to allow this and start up if they > are able to contact one or more of the other locators in their "locators" > setting. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (GEODE-1561) CI Failure: GemfireDataCommandsDUnitTest.testSimulateForEntireDS assertion failure
[ https://issues.apache.org/jira/browse/GEODE-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-1561: Component/s: (was: rest (dev)) rest (admin) > CI Failure: GemfireDataCommandsDUnitTest.testSimulateForEntireDS assertion > failure > --- > > Key: GEODE-1561 > URL: https://issues.apache.org/jira/browse/GEODE-1561 > Project: Geode > Issue Type: Bug > Components: rest (admin) >Reporter: Scott Jewell >Assignee: Jinmei Liao > Labels: CI, Flaky > > Error Message > java.lang.AssertionError: expected: but was: > Stacktrace > java.lang.AssertionError: expected: but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testSimulateForEntireDS(GemfireDataCommandsDUnitTest.java:1831) > 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:498) > 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.ExternalResource$1.evaluate(ExternalResource.java:48) > 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.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > 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] [Assigned] (GEODE-1228) ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover
[
https://issues.apache.org/jira/browse/GEODE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-1228:
---
Assignee: Bruce Schuchardt (was: Udo Kohlmeyer)
> ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover
> -
>
> Key: GEODE-1228
> URL: https://issues.apache.org/jira/browse/GEODE-1228
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: xiaojian zhou
>Assignee: Bruce Schuchardt
> Labels: CI, Flaky
> Fix For: 1.0.0-incubating.M3
>
>
> {noformat}
> Geode_develop_DistributedTests/2260
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.security.ClientAuthzObjectModDUnitTest$$Lambda$517/1376300375.call
> in VM 0 running on Host japan.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.security.ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover(ClientAuthzObjectModDUnitTest.java:117)
> 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.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.dispatc
[jira] [Commented] (GEODE-1228) ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover
[
https://issues.apache.org/jira/browse/GEODE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977636#comment-15977636
]
Bruce Schuchardt commented on GEODE-1228:
-
I'll modify this test to use the locator to find servers and let the servers do
a wild-card bind. That will avoid any use of AvailablePortHelper.
> ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover
> -
>
> Key: GEODE-1228
> URL: https://issues.apache.org/jira/browse/GEODE-1228
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: xiaojian zhou
>Assignee: Bruce Schuchardt
> Labels: CI, Flaky
> Fix For: 1.0.0-incubating.M3
>
>
> {noformat}
> Geode_develop_DistributedTests/2260
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.security.ClientAuthzObjectModDUnitTest$$Lambda$517/1376300375.call
> in VM 0 running on Host japan.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.security.ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover(ClientAuthzObjectModDUnitTest.java:117)
> 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.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.i
[jira] [Updated] (GEODE-516) GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-516:
---
Fix Version/s: 1.2.0
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has
> NullPointerException
> -
>
> Key: GEODE-516
> URL: https://issues.apache.org/jira/browse/GEODE-516
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: xiaojian zhou
> Labels: Flaky, ShowDeadlockCommand
> Fix For: 1.2.0
>
>
> revision 0cc9d895b9f4465138d0fa223b0a0cadc1107893
> {noformat}
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.distributed.internal.deadlock.DeadlockDetector.prettyFormat(DeadlockDetector.java:151)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-516) GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-516.
Resolution: Fixed
Assignee: (was: Bruce Schuchardt)
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction has
> NullPointerException
> -
>
> Key: GEODE-516
> URL: https://issues.apache.org/jira/browse/GEODE-516
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: xiaojian zhou
> Labels: Flaky, ShowDeadlockCommand
>
> revision 0cc9d895b9f4465138d0fa223b0a0cadc1107893
> {noformat}
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.distributed.internal.deadlock.DeadlockDetector.prettyFormat(DeadlockDetector.java:151)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-576) CI Failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction
[
https://issues.apache.org/jira/browse/GEODE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-576.
Resolution: Fixed
Assignee: (was: Bruce Schuchardt)
Fix Version/s: 1.2.0
> CI Failure:
> GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction
>
>
> Key: GEODE-576
> URL: https://issues.apache.org/jira/browse/GEODE-576
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Barry Oglesby
> Labels: CI, Flaky
> Fix For: 1.2.0
>
>
> Geode_develop_DistributedTests
> Private Build #612 (Nov 17, 2015 5:09:11 PM)
> Revision: 90b9a632b9738319fc7a7fddb93b6bef9ff57f7d
> Error Message
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> {noformat}
> Stacktrace
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> at dunit.AsyncInvocation.getResult(AsyncInvocation.java:195)
> at
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithFunction(GemFireDeadlockDetectorDUnitTest.java:121)
> 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.GeneratedMethodAccessor137.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.GeneratedMethodAccessor136.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: dunit.RMIException: While invoking
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest$2.run
> in VM 0 running on Host rooktwo.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM$2.run(VM.java:220)
> at java.lang.Thread.run(Thread.java:745)
> at dunit.AsyncInvocation.run(Async
[jira] [Resolved] (GEODE-1923) CI Failure: FixedPRSinglehopDUnitTest.test_FPAmetadataFetch
[ https://issues.apache.org/jira/browse/GEODE-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-1923. - Resolution: Duplicate (was: Fixed) Assignee: (was: Galen O'Sullivan) A new ticket was opened for this test, GEODE-2752. > CI Failure: FixedPRSinglehopDUnitTest.test_FPAmetadataFetch > --- > > Key: GEODE-1923 > URL: https://issues.apache.org/jira/browse/GEODE-1923 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.0.0-incubating >Reporter: Eric Shu > Labels: ci, flaky > Fix For: 1.2.0 > > > java.lang.AssertionError: expected: but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest.updateIntoSinglePR(FixedPRSinglehopDUnitTest.java:765) > at > org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest.test_FPAmetadataFetch(FixedPRSinglehopDUnitTest.java:339) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatc
[jira] [Commented] (GEODE-2752) FixedPRSinglehopDUnitTest.test_FPAmetadataFetch fails on Jenkins
[
https://issues.apache.org/jira/browse/GEODE-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981836#comment-15981836
]
Bruce Schuchardt commented on GEODE-2752:
-
The test creates two servers with a fixed partition region. It then creates a
third server and waits for the server to say it has the expected number of
buckets. It performs get() operations on the region that should force a
metadata refresh, prints out the bucket->server mappings and finally performs
put() operations and expects no metadata refresh. Unfortunately creation of
buckets in the servers and the promotion of the bucket to primary are not
atomic and, if the servers don't have a primary they will not notify the client
to refresh its metadata.
I think this is a flaw in PartitionRegion.setNetworkHop. This line:
{code}
if (this.isDataStore() && !getMyId().equals(targetNode)) {
{code}
Instead of checking for a datastore it should check to see if it has the
bucket. If it doesn't have the bucket it should tell the client to refresh its
metadata.
> FixedPRSinglehopDUnitTest.test_FPAmetadataFetch fails on Jenkins
>
>
> Key: GEODE-2752
> URL: https://issues.apache.org/jira/browse/GEODE-2752
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Hitesh Khamesra
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest$$Lambda$90/1893223347.call
> in VM 0 running on Host asf912.gq1.ygridcore.net with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:315)
> at
> org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest.test_FPAmetadataFetch(FixedPRSinglehopDUnitTest.java:283)
> 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:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderD
[jira] [Updated] (GEODE-2752) FixedPRSinglehopDUnitTest.test_FPAmetadataFetch fails on Jenkins
[ https://issues.apache.org/jira/browse/GEODE-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2752: Labels: flaky (was: ) > FixedPRSinglehopDUnitTest.test_FPAmetadataFetch fails on Jenkins > > > Key: GEODE-2752 > URL: https://issues.apache.org/jira/browse/GEODE-2752 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Hitesh Khamesra > Labels: flaky > > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest$$Lambda$90/1893223347.call > in VM 0 running on Host asf912.gq1.ygridcore.net with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:377) > at org.apache.geode.test.dunit.VM.invoke(VM.java:347) > at org.apache.geode.test.dunit.VM.invoke(VM.java:315) > at > org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest.test_FPAmetadataFetch(FixedPRSinglehopDUnitTest.java:283) > 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:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.remote.i
[jira] [Resolved] (GEODE-2752) FixedPRSinglehopDUnitTest.test_FPAmetadataFetch fails on Jenkins
[ https://issues.apache.org/jira/browse/GEODE-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2752. - Resolution: Fixed Fix Version/s: 1.2.0 > FixedPRSinglehopDUnitTest.test_FPAmetadataFetch fails on Jenkins > > > Key: GEODE-2752 > URL: https://issues.apache.org/jira/browse/GEODE-2752 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Hitesh Khamesra > Labels: flaky > Fix For: 1.2.0 > > > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest$$Lambda$90/1893223347.call > in VM 0 running on Host asf912.gq1.ygridcore.net with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:377) > at org.apache.geode.test.dunit.VM.invoke(VM.java:347) > at org.apache.geode.test.dunit.VM.invoke(VM.java:315) > at > org.apache.geode.internal.cache.FixedPRSinglehopDUnitTest.test_FPAmetadataFetch(FixedPRSinglehopDUnitTest.java:283) > 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:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDisp
[jira] [Resolved] (GEODE-1228) ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover
[
https://issues.apache.org/jira/browse/GEODE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-1228.
-
Fix Version/s: (was: 1.0.0-incubating.M3)
1.2.0
> ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover
> -
>
> Key: GEODE-1228
> URL: https://issues.apache.org/jira/browse/GEODE-1228
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: xiaojian zhou
>Assignee: Bruce Schuchardt
> Labels: CI, Flaky
> Fix For: 1.2.0
>
>
> {noformat}
> Geode_develop_DistributedTests/2260
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.security.ClientAuthzObjectModDUnitTest$$Lambda$517/1376300375.call
> in VM 0 running on Host japan.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.security.ClientAuthzObjectModDUnitTest.testAllOpsObjectModWithFailover(ClientAuthzObjectModDUnitTest.java:117)
> 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.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.disp
[jira] [Created] (GEODE-2865) data loss in initial-image replication with multicast
Bruce Schuchardt created GEODE-2865:
---
Summary: data loss in initial-image replication with multicast
Key: GEODE-2865
URL: https://issues.apache.org/jira/browse/GEODE-2865
Project: Geode
Issue Type: Bug
Components: messaging
Reporter: Bruce Schuchardt
During initial image replication ("get initial image") a state-flush operation
is performed to ensure that all in-flight operations are applied to the region
being replicated prior to replication starting. If multicast is enabled for a
region it is currently possible for the state-flush to miss one or more
in-flight operations, so that the new repilcate is missing changes that are
reflected in the region being replicated.
For example, process A sends a multicast put() replication message to process
B. Simultaneously process C is replicating the affected region and performs a
state-flush. Process A sends a state-stabilization message to process B noting
its multicast channel state (NAKACK2 outgoing message counter). Process B
receives this and waits for the multicast channel state to show that it has
received all of the messages. Process B then sends a state-stabilized message
to process C (the new replicate).
The state-stabilization algorithm in this case is faulty because it is
performed in the waiting-thread pool. The algorithm assumes that it is
executing in the serial-executor thread pool so that any messages that happened
before it have been applied to the region. This can allow messages to have
been received and scheduled for the serial-executor but not be applied to the
region before replication begins.
The membership manager should be modified to ensure that the serial-executor
queue has been flushed before giving the state-flush operation the go-ahead to
begin replication.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2875) shutdown is taking as long as 20 seconds
Bruce Schuchardt created GEODE-2875: --- Summary: shutdown is taking as long as 20 seconds Key: GEODE-2875 URL: https://issues.apache.org/jira/browse/GEODE-2875 Project: Geode Issue Type: Bug Components: membership Reporter: Bruce Schuchardt Recent changes have introduced a bug where sometimes, particularly during shutdown of a lot of servers, the shutdown process will stall for as long as 20 seconds. This appears to be due to changes that keep a membership coordinator from sending out a new view during shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2875) shutdown is taking as long as 20 seconds
[ https://issues.apache.org/jira/browse/GEODE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2875. - Resolution: Fixed > shutdown is taking as long as 20 seconds > > > Key: GEODE-2875 > URL: https://issues.apache.org/jira/browse/GEODE-2875 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > Recent changes have introduced a bug where sometimes, particularly during > shutdown of a lot of servers, the shutdown process will stall for as long as > 20 seconds. This appears to be due to changes that keep a membership > coordinator from sending out a new view during shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client
[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002921#comment-16002921 ] Bruce Schuchardt commented on GEODE-2891: - If this is a C++ client issue the component should be "native client", not "client server" > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Gregory Vortman > Fix For: 1.1.1 > > Attachments: gemfire-connect-timeout-violation.docx > > > 1.C++ native client doesn’t honour read-timeout-milli-sec in a consistent > way while connecting to a server > 2.The lock on the connection pool has a very high granularity. Even if > the client can’t connect to one server, all other threads which are working > with totally different servers get affected by it -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2898) A non-responsive SSL client can block a server's "acceptor" thread
Bruce Schuchardt created GEODE-2898: --- Summary: A non-responsive SSL client can block a server's "acceptor" thread Key: GEODE-2898 URL: https://issues.apache.org/jira/browse/GEODE-2898 Project: Geode Issue Type: Bug Components: client/server Reporter: Bruce Schuchardt During the handoff to the handshake thread pool the accept thread can be blocked in the SSL handshake. The SSL handshake should be moved to the handshake thread pool. The goal is allow the server to reject clients that haven't finished the handshake in the allotted time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client
[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003160#comment-16003160 ] Bruce Schuchardt commented on GEODE-2891: - You can work on a clone of the github repo and submit a pull request. You might want to assign the JIRA ticket to someone on your team if you are going to do this. Here is the process for submitting a pull request: https://cwiki.apache.org/confluence/display/GEODE/Code+contributions > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Gregory Vortman > Fix For: 1.1.1 > > Attachments: gemfire-connect-timeout-violation.docx > > > 1.C++ native client doesn’t honour read-timeout-milli-sec in a consistent > way while connecting to a server > 2.The lock on the connection pool has a very high granularity. Even if > the client can’t connect to one server, all other threads which are working > with totally different servers get affected by it -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2896) ClassCastException in GMSMembershipManagerJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003706#comment-16003706
]
Bruce Schuchardt commented on GEODE-2896:
-
HighPriorityAckedMessage should ignore the result of
ds.getDistributionManager() if it's not an instance of DistributionManager.
> ClassCastException in GMSMembershipManagerJUnitTest
> ---
>
> Key: GEODE-2896
> URL: https://issues.apache.org/jira/browse/GEODE-2896
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: nabarun
>Assignee: nabarun
>
> {noformat}
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureDueToForcedDisconnect FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureDueToForcedDisconnect(GMSMembershipManagerJUnitTest.java:343)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testStartupEvents FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testStartupEvents(GMSMembershipManagerJUnitTest.java:219)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testSendToEmptyListIsRejected FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testSendToEmptyListIsRejected(GMSMembershipManagerJUnitTest.java:177)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendAllRecipients FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendAllRecipients(GMSMembershipManagerJUnitTest.java:331)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSend FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSend(GMSMembershipManagerJUnitTest.java:281)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToOneRecipient FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureToOneRecipient(GMSMembershipManagerJUnitTest.java:294)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToAll FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureToAll(GMSMembershipManagerJUnitTest.jav
[jira] [Closed] (GEODE-2898) A non-responsive SSL client can block a server's "acceptor" thread
[ https://issues.apache.org/jira/browse/GEODE-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt closed GEODE-2898. --- > A non-responsive SSL client can block a server's "acceptor" thread > -- > > Key: GEODE-2898 > URL: https://issues.apache.org/jira/browse/GEODE-2898 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Bruce Schuchardt > Fix For: 1.2.0 > > > During the handoff to the handshake thread pool the accept thread can be > blocked in the SSL handshake. The SSL handshake should be moved to the > handshake thread pool. The goal is allow the server to reject clients that > haven't finished the handshake in the allotted time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2898) A non-responsive SSL client can block a server's "acceptor" thread
[ https://issues.apache.org/jira/browse/GEODE-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2898. - Resolution: Fixed Fix Version/s: 1.2.0 > A non-responsive SSL client can block a server's "acceptor" thread > -- > > Key: GEODE-2898 > URL: https://issues.apache.org/jira/browse/GEODE-2898 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Bruce Schuchardt > Fix For: 1.2.0 > > > During the handoff to the handshake thread pool the accept thread can be > blocked in the SSL handshake. The SSL handshake should be moved to the > handshake thread pool. The goal is allow the server to reject clients that > haven't finished the handshake in the allotted time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (GEODE-2875) shutdown is taking as long as 20 seconds
[ https://issues.apache.org/jira/browse/GEODE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reopened GEODE-2875: - Assignee: Bruce Schuchardt The fix for this issue causes one of the test cases in LocatorDUnitTest to fail consistently. With the fix we don't create any TCP/IP connections in this test during startup but the test expects one to have been created and it expects the connection's reader-thread to have initiated suspect processing. The test needs to be altered to ensure that this thread has been created by sending message that requires a reply. The reply will be sent over the expected connection, ensuring that there is a reader-thread. > shutdown is taking as long as 20 seconds > > > Key: GEODE-2875 > URL: https://issues.apache.org/jira/browse/GEODE-2875 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > > Recent changes have introduced a bug where sometimes, particularly during > shutdown of a lot of servers, the shutdown process will stall for as long as > 20 seconds. This appears to be due to changes that keep a membership > coordinator from sending out a new view during shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-2915) Messages rejected due to unknown "vmkind"
Bruce Schuchardt created GEODE-2915:
---
Summary: Messages rejected due to unknown "vmkind"
Key: GEODE-2915
URL: https://issues.apache.org/jira/browse/GEODE-2915
Project: Geode
Issue Type: Bug
Components: messaging
Reporter: Bruce Schuchardt
Periodically we are seeing messages being rejected with the following error:
{noformat}
[warning 2017/02/25 10:28:49.539 PST
gemfire2_rs-FullRegression-2017-02-25-03-00-45-client-30_6335
tid=0x14] Membership: Error handling startup event
org.apache.geode.InternalGemFireError: Unknown member type: 0
at
org.apache.geode.distributed.internal.DistributionManager.addNewMember(DistributionManager.java:1787)
at
org.apache.geode.distributed.internal.DistributionManager$MyListener.newMemberConnected(DistributionManager.java:4319)
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.addSurpriseMember(GMSMembershipManager.java:972)
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.dispatchMessage(GMSMembershipManager.java:1094)
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.processStartupEvent(GMSMembershipManager.java:1204)
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.startEventProcessing(GMSMembershipManager.java:1254)
at
org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1185)
at
org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:687)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:299)
at
org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202)
at
hydra.DistributedSystemHelper._connect(DistributedSystemHelper.java:110)
at
hydra.DistributedSystemHelper.connect(DistributedSystemHelper.java:73)
at perffmwk.PerformanceStatistics.factory(PerformanceStatistics.java:93)
at
cacheperf.CachePerfStats.getStatisticDescriptors(CachePerfStats.java:96)
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:498)
at hydra.MethExecutor.execute(MethExecutor.java:182)
at hydra.MethExecutor.execute(MethExecutor.java:150)
at
perffmwk.PerformanceStatistics.getStatisticsType(PerformanceStatistics.java:139)
at
perffmwk.PerformanceStatistics.getInstance(PerformanceStatistics.java:125)
at
perffmwk.PerformanceStatistics.getInstance(PerformanceStatistics.java:105)
at cacheperf.CachePerfStats.getInstance(CachePerfStats.java:216)
at cacheperf.CachePerfClient.openStatistics(CachePerfClient.java:965)
at
cacheperf.CachePerfClient.openStatisticsTask(CachePerfClient.java:959)
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:498)
at hydra.MethExecutor.execute(MethExecutor.java:182)
at hydra.MethExecutor.execute(MethExecutor.java:150)
at hydra.TestTask.execute(TestTask.java:192)
at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (GEODE-2875) shutdown is taking as long as 20 seconds
[ https://issues.apache.org/jira/browse/GEODE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt closed GEODE-2875. --- > shutdown is taking as long as 20 seconds > > > Key: GEODE-2875 > URL: https://issues.apache.org/jira/browse/GEODE-2875 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.2.0 > > > Recent changes have introduced a bug where sometimes, particularly during > shutdown of a lot of servers, the shutdown process will stall for as long as > 20 seconds. This appears to be due to changes that keep a membership > coordinator from sending out a new view during shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2875) shutdown is taking as long as 20 seconds
[ https://issues.apache.org/jira/browse/GEODE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2875. - Resolution: Fixed Fix Version/s: 1.2.0 > shutdown is taking as long as 20 seconds > > > Key: GEODE-2875 > URL: https://issues.apache.org/jira/browse/GEODE-2875 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.2.0 > > > Recent changes have introduced a bug where sometimes, particularly during > shutdown of a lot of servers, the shutdown process will stall for as long as > 20 seconds. This appears to be due to changes that keep a membership > coordinator from sending out a new view during shutdown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (GEODE-2865) data loss in initial-image replication with multicast
[
https://issues.apache.org/jira/browse/GEODE-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt closed GEODE-2865.
---
> data loss in initial-image replication with multicast
> -
>
> Key: GEODE-2865
> URL: https://issues.apache.org/jira/browse/GEODE-2865
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> During initial image replication ("get initial image") a state-flush
> operation is performed to ensure that all in-flight operations are applied to
> the region being replicated prior to replication starting. If multicast is
> enabled for a region it is currently possible for the state-flush to miss one
> or more in-flight operations, so that the new repilcate is missing changes
> that are reflected in the region being replicated.
> For example, process A sends a multicast put() replication message to process
> B. Simultaneously process C is replicating the affected region and performs
> a state-flush. Process A sends a state-stabilization message to process B
> noting its multicast channel state (NAKACK2 outgoing message counter).
> Process B receives this and waits for the multicast channel state to show
> that it has received all of the messages. Process B then sends a
> state-stabilized message to process C (the new replicate).
> The state-stabilization algorithm in this case is faulty because it is
> performed in the waiting-thread pool. The algorithm assumes that it is
> executing in the serial-executor thread pool so that any messages that
> happened before it have been applied to the region. This can allow messages
> to have been received and scheduled for the serial-executor but not be
> applied to the region before replication begins.
> The membership manager should be modified to ensure that the serial-executor
> queue has been flushed before giving the state-flush operation the go-ahead
> to begin replication.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-2865) data loss in initial-image replication with multicast
[
https://issues.apache.org/jira/browse/GEODE-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2865.
-
Resolution: Fixed
Fix Version/s: 1.2.0
> data loss in initial-image replication with multicast
> -
>
> Key: GEODE-2865
> URL: https://issues.apache.org/jira/browse/GEODE-2865
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> During initial image replication ("get initial image") a state-flush
> operation is performed to ensure that all in-flight operations are applied to
> the region being replicated prior to replication starting. If multicast is
> enabled for a region it is currently possible for the state-flush to miss one
> or more in-flight operations, so that the new repilcate is missing changes
> that are reflected in the region being replicated.
> For example, process A sends a multicast put() replication message to process
> B. Simultaneously process C is replicating the affected region and performs
> a state-flush. Process A sends a state-stabilization message to process B
> noting its multicast channel state (NAKACK2 outgoing message counter).
> Process B receives this and waits for the multicast channel state to show
> that it has received all of the messages. Process B then sends a
> state-stabilized message to process C (the new replicate).
> The state-stabilization algorithm in this case is faulty because it is
> performed in the waiting-thread pool. The algorithm assumes that it is
> executing in the serial-executor thread pool so that any messages that
> happened before it have been applied to the region. This can allow messages
> to have been received and scheduled for the serial-executor but not be
> applied to the region before replication begins.
> The membership manager should be modified to ensure that the serial-executor
> queue has been flushed before giving the state-flush operation the go-ahead
> to begin replication.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-2915) Messages rejected due to unknown "vmkind"
[
https://issues.apache.org/jira/browse/GEODE-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2915.
-
Resolution: Fixed
Fix Version/s: 1.2.0
> Messages rejected due to unknown "vmkind"
> -
>
> Key: GEODE-2915
> URL: https://issues.apache.org/jira/browse/GEODE-2915
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> Periodically we are seeing messages being rejected with the following error:
> {noformat}
> [warning 2017/02/25 10:28:49.539 PST
> gemfire2_rs-FullRegression-2017-02-25-03-00-45-client-30_6335
>
> tid=0x14] Membership: Error handling startup event
> org.apache.geode.InternalGemFireError: Unknown member type: 0
> at
> org.apache.geode.distributed.internal.DistributionManager.addNewMember(DistributionManager.java:1787)
> at
> org.apache.geode.distributed.internal.DistributionManager$MyListener.newMemberConnected(DistributionManager.java:4319)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.addSurpriseMember(GMSMembershipManager.java:972)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.dispatchMessage(GMSMembershipManager.java:1094)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.processStartupEvent(GMSMembershipManager.java:1204)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.startEventProcessing(GMSMembershipManager.java:1254)
> at
> org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1185)
> at
> org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:687)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:299)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202)
> at
> hydra.DistributedSystemHelper._connect(DistributedSystemHelper.java:110)
> at
> hydra.DistributedSystemHelper.connect(DistributedSystemHelper.java:73)
> at
> perffmwk.PerformanceStatistics.factory(PerformanceStatistics.java:93)
> at
> cacheperf.CachePerfStats.getStatisticDescriptors(CachePerfStats.java:96)
> 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:498)
> at hydra.MethExecutor.execute(MethExecutor.java:182)
> at hydra.MethExecutor.execute(MethExecutor.java:150)
> at
> perffmwk.PerformanceStatistics.getStatisticsType(PerformanceStatistics.java:139)
> at
> perffmwk.PerformanceStatistics.getInstance(PerformanceStatistics.java:125)
> at
> perffmwk.PerformanceStatistics.getInstance(PerformanceStatistics.java:105)
> at cacheperf.CachePerfStats.getInstance(CachePerfStats.java:216)
> at cacheperf.CachePerfClient.openStatistics(CachePerfClient.java:965)
> at
> cacheperf.CachePerfClient.openStatisticsTask(CachePerfClient.java:959)
> 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:498)
> at hydra.MethExecutor.execute(MethExecutor.java:182)
> at hydra.MethExecutor.execute(MethExecutor.java:150)
> at hydra.TestTask.execute(TestTask.java:192)
> at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2954) Old client gets null memberID in cache listener
[
https://issues.apache.org/jira/browse/GEODE-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-2954:
Component/s: (was: regions)
membership
> Old client gets null memberID in cache listener
> ---
>
> Key: GEODE-2954
> URL: https://issues.apache.org/jira/browse/GEODE-2954
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> I was doing backward compatibility testing and found a 1.0 client was getting
> a null memberID in a cache listener
> {noformat}
> [info 2017/05/18 16:27:38.957 PDT trout(bridgegemfire5_trout_2254:2254):1030 port 21051> tid=0x2f]
> Invoked util.SilenceListener for key Object_7399: afterDestroy in edge1, pid
> 2267, vmID 5, operation DESTROY
> whereIWasRegistered: 2267
> event.getKey(): Object_7399
> event.getOldValue(): (contains 6 levels, aPrimitiveLong=6409636308677575978)>
> event.getNewValue(): null
> event.getOperation().isLoad(): false
> event.getOperation().isLocalLoad(): false
> event.getOperation().isNetLoad(): false
> event.getOperation().isNetSearch(): false
> event.isConcurrencyConflict(): false
> event.getDistributedMember(): null
> event.getCallbackArgument(): null
> event.getRegion(): /testRegion
> event.getOperation().isDistributed(): true
> event.getOperation().isExpiration(): false
> event.isOriginRemote(): true
> {noformat}
> This was in an old test suite whose testing infrastructure isn't in the Geode
> repo. I'm writing a unit test to reproduce the problem.
> If you look at EventID.java you can see that it catches IOExceptions in
> deserializing the memberID of the event and returns null without logging the
> problem.
> {code}
> try {
> result = InternalDistributedMember.readEssentialData(dis);
> } catch (IOException e) {
> // nothing can be done about this
> } catch (ClassNotFoundException e) {
> // ditto
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (GEODE-2954) Old client gets null memberID in cache listener
[
https://issues.apache.org/jira/browse/GEODE-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-2954:
---
Assignee: Bruce Schuchardt
> Old client gets null memberID in cache listener
> ---
>
> Key: GEODE-2954
> URL: https://issues.apache.org/jira/browse/GEODE-2954
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> I was doing backward compatibility testing and found a 1.0 client was getting
> a null memberID in a cache listener
> {noformat}
> [info 2017/05/18 16:27:38.957 PDT trout(bridgegemfire5_trout_2254:2254):1030 port 21051> tid=0x2f]
> Invoked util.SilenceListener for key Object_7399: afterDestroy in edge1, pid
> 2267, vmID 5, operation DESTROY
> whereIWasRegistered: 2267
> event.getKey(): Object_7399
> event.getOldValue(): (contains 6 levels, aPrimitiveLong=6409636308677575978)>
> event.getNewValue(): null
> event.getOperation().isLoad(): false
> event.getOperation().isLocalLoad(): false
> event.getOperation().isNetLoad(): false
> event.getOperation().isNetSearch(): false
> event.isConcurrencyConflict(): false
> event.getDistributedMember(): null
> event.getCallbackArgument(): null
> event.getRegion(): /testRegion
> event.getOperation().isDistributed(): true
> event.getOperation().isExpiration(): false
> event.isOriginRemote(): true
> {noformat}
> This was in an old test suite whose testing infrastructure isn't in the Geode
> repo. I'm writing a unit test to reproduce the problem.
> If you look at EventID.java you can see that it catches IOExceptions in
> deserializing the memberID of the event and returns null without logging the
> problem.
> {code}
> try {
> result = InternalDistributedMember.readEssentialData(dis);
> } catch (IOException e) {
> // nothing can be done about this
> } catch (ClassNotFoundException e) {
> // ditto
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (GEODE-2954) Old client gets null memberID in cache listener
Bruce Schuchardt created GEODE-2954:
---
Summary: Old client gets null memberID in cache listener
Key: GEODE-2954
URL: https://issues.apache.org/jira/browse/GEODE-2954
Project: Geode
Issue Type: Bug
Components: regions
Reporter: Bruce Schuchardt
Fix For: 1.2.0
I was doing backward compatibility testing and found a 1.0 client was getting a
null memberID in a cache listener
{noformat}
[info 2017/05/18 16:27:38.957 PDT :1030 port 21051> tid=0x2f]
Invoked util.SilenceListener for key Object_7399: afterDestroy in edge1, pid
2267, vmID 5, operation DESTROY
whereIWasRegistered: 2267
event.getKey(): Object_7399
event.getOldValue():
event.getNewValue(): null
event.getOperation().isLoad(): false
event.getOperation().isLocalLoad(): false
event.getOperation().isNetLoad(): false
event.getOperation().isNetSearch(): false
event.isConcurrencyConflict(): false
event.getDistributedMember(): null
event.getCallbackArgument(): null
event.getRegion(): /testRegion
event.getOperation().isDistributed(): true
event.getOperation().isExpiration(): false
event.isOriginRemote(): true
{noformat}
This was in an old test suite whose testing infrastructure isn't in the Geode
repo. I'm writing a unit test to reproduce the problem.
If you look at EventID.java you can see that it catches IOExceptions in
deserializing the memberID of the event and returns null without logging the
problem.
{code}
try {
result = InternalDistributedMember.readEssentialData(dis);
} catch (IOException e) {
// nothing can be done about this
} catch (ClassNotFoundException e) {
// ditto
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (GEODE-2981) Fix the line feed code of the test expected value
[ https://issues.apache.org/jira/browse/GEODE-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2981: Component/s: management > Fix the line feed code of the test expected value > - > > Key: GEODE-2981 > URL: https://issues.apache.org/jira/browse/GEODE-2981 > Project: Geode > Issue Type: Test > Components: management, tests >Reporter: Masaki Yamakawa >Priority: Minor > > I mainly use the Windows. When I run the test on Windows, because Assertion > fails due to the difference in line feed code, I want to change this so that > it does not depend on the runtime environment. > The target classes are as follows: > - org.apache.geode.management.internal.cli.shell.GfshJunitTest > - org.apache.geode.management.internal.cli.help.HelpBlockUnitTest > - org.apache.geode.management.internal.cli.help.HelperUnitTest -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (GEODE-2981) Fix the line feed code of the test expected value
[ https://issues.apache.org/jira/browse/GEODE-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023895#comment-16023895 ] Bruce Schuchardt commented on GEODE-2981: - This test is also consistently failing on my Windows 7 machine. > Fix the line feed code of the test expected value > - > > Key: GEODE-2981 > URL: https://issues.apache.org/jira/browse/GEODE-2981 > Project: Geode > Issue Type: Test > Components: management, tests >Reporter: Masaki Yamakawa >Priority: Minor > > I mainly use the Windows. When I run the test on Windows, because Assertion > fails due to the difference in line feed code, I want to change this so that > it does not depend on the runtime environment. > The target classes are as follows: > - org.apache.geode.management.internal.cli.shell.GfshJunitTest > - org.apache.geode.management.internal.cli.help.HelpBlockUnitTest > - org.apache.geode.management.internal.cli.help.HelperUnitTest -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (GEODE-2954) Old client gets null memberID in cache listener
[
https://issues.apache.org/jira/browse/GEODE-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt closed GEODE-2954.
---
> Old client gets null memberID in cache listener
> ---
>
> Key: GEODE-2954
> URL: https://issues.apache.org/jira/browse/GEODE-2954
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> I was doing backward compatibility testing and found a 1.0 client was getting
> a null memberID in a cache listener
> {noformat}
> [info 2017/05/18 16:27:38.957 PDT trout(bridgegemfire5_trout_2254:2254):1030 port 21051> tid=0x2f]
> Invoked util.SilenceListener for key Object_7399: afterDestroy in edge1, pid
> 2267, vmID 5, operation DESTROY
> whereIWasRegistered: 2267
> event.getKey(): Object_7399
> event.getOldValue(): (contains 6 levels, aPrimitiveLong=6409636308677575978)>
> event.getNewValue(): null
> event.getOperation().isLoad(): false
> event.getOperation().isLocalLoad(): false
> event.getOperation().isNetLoad(): false
> event.getOperation().isNetSearch(): false
> event.isConcurrencyConflict(): false
> event.getDistributedMember(): null
> event.getCallbackArgument(): null
> event.getRegion(): /testRegion
> event.getOperation().isDistributed(): true
> event.getOperation().isExpiration(): false
> event.isOriginRemote(): true
> {noformat}
> This was in an old test suite whose testing infrastructure isn't in the Geode
> repo. I'm writing a unit test to reproduce the problem.
> If you look at EventID.java you can see that it catches IOExceptions in
> deserializing the memberID of the event and returns null without logging the
> problem.
> {code}
> try {
> result = InternalDistributedMember.readEssentialData(dis);
> } catch (IOException e) {
> // nothing can be done about this
> } catch (ClassNotFoundException e) {
> // ditto
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (GEODE-2954) Old client gets null memberID in cache listener
[
https://issues.apache.org/jira/browse/GEODE-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2954.
-
Resolution: Fixed
> Old client gets null memberID in cache listener
> ---
>
> Key: GEODE-2954
> URL: https://issues.apache.org/jira/browse/GEODE-2954
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> I was doing backward compatibility testing and found a 1.0 client was getting
> a null memberID in a cache listener
> {noformat}
> [info 2017/05/18 16:27:38.957 PDT trout(bridgegemfire5_trout_2254:2254):1030 port 21051> tid=0x2f]
> Invoked util.SilenceListener for key Object_7399: afterDestroy in edge1, pid
> 2267, vmID 5, operation DESTROY
> whereIWasRegistered: 2267
> event.getKey(): Object_7399
> event.getOldValue(): (contains 6 levels, aPrimitiveLong=6409636308677575978)>
> event.getNewValue(): null
> event.getOperation().isLoad(): false
> event.getOperation().isLocalLoad(): false
> event.getOperation().isNetLoad(): false
> event.getOperation().isNetSearch(): false
> event.isConcurrencyConflict(): false
> event.getDistributedMember(): null
> event.getCallbackArgument(): null
> event.getRegion(): /testRegion
> event.getOperation().isDistributed(): true
> event.getOperation().isExpiration(): false
> event.isOriginRemote(): true
> {noformat}
> This was in an old test suite whose testing infrastructure isn't in the Geode
> repo. I'm writing a unit test to reproduce the problem.
> If you look at EventID.java you can see that it catches IOExceptions in
> deserializing the memberID of the event and returns null without logging the
> problem.
> {code}
> try {
> result = InternalDistributedMember.readEssentialData(dis);
> } catch (IOException e) {
> // nothing can be done about this
> } catch (ClassNotFoundException e) {
> // ditto
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (GEODE-2898) A non-responsive SSL client can block a server's "acceptor" thread
[ https://issues.apache.org/jira/browse/GEODE-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031456#comment-16031456 ] Bruce Schuchardt commented on GEODE-2898: - I think there should be a separate ticket for TcpServer > A non-responsive SSL client can block a server's "acceptor" thread > -- > > Key: GEODE-2898 > URL: https://issues.apache.org/jira/browse/GEODE-2898 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Bruce Schuchardt > Fix For: 1.2.0 > > > During the handoff to the handshake thread pool the accept thread can be > blocked in the SSL handshake. The SSL handshake should be moved to the > handshake thread pool. The goal is allow the server to reject clients that > haven't finished the handshake in the allotted time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (GEODE-3024) race condition between server and restarted locator preparing membership views
Bruce Schuchardt created GEODE-3024: --- Summary: race condition between server and restarted locator preparing membership views Key: GEODE-3024 URL: https://issues.apache.org/jira/browse/GEODE-3024 Project: Geode Issue Type: Bug Components: membership Reporter: Bruce Schuchardt When a locator is restarted & recovers from disk it will try to take over the role of membership coordinator for the cluster if it finds the current coordinator is a cache server. If the cache server is in the process of sending out a new view it may get into a race with the locator in sending out view preparation messages. The locator will send out a view-prep message and the server will also send one. Responses to the view-prep message will include the conflicting view and each of the two processes will create a new view and send it out. This repeats ad-infinitum. This problem was observed in a system that was shutting down at the same time a locator was being restarted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (GEODE-2121) add DLockTest, MembershipTest, ClientServerTest, ClientSubscriptionTest and RestAPITest categories
[ https://issues.apache.org/jira/browse/GEODE-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2121. - Resolution: Fixed the test categories have been created > add DLockTest, MembershipTest, ClientServerTest, ClientSubscriptionTest and > RestAPITest categories > -- > > Key: GEODE-2121 > URL: https://issues.apache.org/jira/browse/GEODE-2121 > Project: Geode > Issue Type: Test > Components: client queues, client/server, distributed lock service, > membership, rest (dev), serialization >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > > I need these test categories in order to run code-coverage analysis for the > components I usually work with. The categories should be added to the > appropriate unit tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2193) a member is kicked out immediately after joining
Bruce Schuchardt created GEODE-2193: --- Summary: a member is kicked out immediately after joining Key: GEODE-2193 URL: https://issues.apache.org/jira/browse/GEODE-2193 Project: Geode Issue Type: Bug Components: membership Reporter: Bruce Schuchardt Assignee: Mark Bretl We have observed a number of cases where a member is kicked out immediately after joining. The problem seems to be this: 1) the member sends a join request to the current coordinator 2) the current coordinator is in the process of shutting down 3) the current coordinator sends a view preparation message admitting the new member 4) another member receives the current coordinator's shutdown message and initiates becoming the coordinator 5) the new coordinator sends out a membership view that does not include the new member 6) the new member receives the prepared view and continues with startup 7) the new member sends startup messages to other members 8) the other members have the new coordinator's view and request removal of the new member as being rogue 9) the new coordinator sends a Leave message to the new member, causing it to issue a ForcedDisconnect The old coordinator should not initiate a new view if it is shutting down. It needs to have cancellation & shutdown checks in its view transmission methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2193) a member is kicked out immediately after joining
[ https://issues.apache.org/jira/browse/GEODE-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2193. - Resolution: Fixed Fix Version/s: 1.1.0 > a member is kicked out immediately after joining > > > Key: GEODE-2193 > URL: https://issues.apache.org/jira/browse/GEODE-2193 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.1.0 > > > We have observed a number of cases where a member is kicked out immediately > after joining. The problem seems to be this: > 1) the member sends a join request to the current coordinator > 2) the current coordinator is in the process of shutting down > 3) the current coordinator sends a view preparation message admitting the new > member > 4) another member receives the current coordinator's shutdown message and > initiates becoming the coordinator > 5) the new coordinator sends out a membership view that does not include the > new member > 6) the new member receives the prepared view and continues with startup > 7) the new member sends startup messages to other members > 8) the other members have the new coordinator's view and request removal of > the new member as being rogue > 9) the new coordinator sends a Leave message to the new member, causing it to > issue a ForcedDisconnect > The old coordinator should not initiate a new view if it is shutting down. > It needs to have cancellation & shutdown checks in its view transmission > methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2193) a member is kicked out immediately after joining
[ https://issues.apache.org/jira/browse/GEODE-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-2193: --- Assignee: Bruce Schuchardt (was: Mark Bretl) > a member is kicked out immediately after joining > > > Key: GEODE-2193 > URL: https://issues.apache.org/jira/browse/GEODE-2193 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.1.0 > > > We have observed a number of cases where a member is kicked out immediately > after joining. The problem seems to be this: > 1) the member sends a join request to the current coordinator > 2) the current coordinator is in the process of shutting down > 3) the current coordinator sends a view preparation message admitting the new > member > 4) another member receives the current coordinator's shutdown message and > initiates becoming the coordinator > 5) the new coordinator sends out a membership view that does not include the > new member > 6) the new member receives the prepared view and continues with startup > 7) the new member sends startup messages to other members > 8) the other members have the new coordinator's view and request removal of > the new member as being rogue > 9) the new coordinator sends a Leave message to the new member, causing it to > issue a ForcedDisconnect > The old coordinator should not initiate a new view if it is shutting down. > It needs to have cancellation & shutdown checks in its view transmission > methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2213) Deadlock in GMSJoinLeaveJUnitTest
Bruce Schuchardt created GEODE-2213:
---
Summary: Deadlock in GMSJoinLeaveJUnitTest
Key: GEODE-2213
URL: https://issues.apache.org/jira/browse/GEODE-2213
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce Schuchardt
Assignee: Mark Bretl
My precheckin run hung in integrationTests with this deadlock:
{noformat}
Found one Java-level deadlock:
=
"Geode Membership View Creator":
waiting to lock monitor 0x153187e8 (object 0xf09102e8, a
java.util.LinkedList),
which is held by "Test worker"
"Test worker":
waiting to lock monitor 0x149d5ad8 (object 0xf09227a8, a
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator),
which is held by "Geode Membership View Creator"
Java stack information for the threads listed above:
===
"Geode Membership View Creator":
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2153)
- waiting to lock <0xf09102e8> (a java.util.LinkedList)
- locked <0xf09227a8> (a
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2137)
"Test worker":
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2143)
- waiting to lock <0xf09227a8> (a
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.recordViewRequest(GMSJoinLeave.java:679)
- locked <0xf09102e8> (a java.util.LinkedList)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:666)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1704)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeaveJUnitTest.testViewNotSentWhenShuttingDown(GMSJoinLeaveJUnitTest.java:1103)
{noformat}
This looks like a pretty straightforward lock inversion that could happen any
time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2213) Deadlock in GMSJoinLeaveJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-2213:
Assignee: (was: Mark Bretl)
> Deadlock in GMSJoinLeaveJUnitTest
> -
>
> Key: GEODE-2213
> URL: https://issues.apache.org/jira/browse/GEODE-2213
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>
> My precheckin run hung in integrationTests with this deadlock:
> {noformat}
> Found one Java-level deadlock:
> =
> "Geode Membership View Creator":
> waiting to lock monitor 0x153187e8 (object 0xf09102e8, a
> java.util.LinkedList),
> which is held by "Test worker"
> "Test worker":
> waiting to lock monitor 0x149d5ad8 (object 0xf09227a8, a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator),
> which is held by "Geode Membership View Creator"
> Java stack information for the threads listed above:
> ===
> "Geode Membership View Creator":
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2153)
> - waiting to lock <0xf09102e8> (a java.util.LinkedList)
> - locked <0xf09227a8> (a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2137)
> "Test worker":
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2143)
> - waiting to lock <0xf09227a8> (a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.recordViewRequest(GMSJoinLeave.java:679)
> - locked <0xf09102e8> (a java.util.LinkedList)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:666)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1704)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeaveJUnitTest.testViewNotSentWhenShuttingDown(GMSJoinLeaveJUnitTest.java:1103)
> {noformat}
> This looks like a pretty straightforward lock inversion that could happen any
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2215) NPE in ViewCreator thread setting public keys into a NetView
Bruce Schuchardt created GEODE-2215:
---
Summary: NPE in ViewCreator thread setting public keys into a
NetView
Key: GEODE-2215
URL: https://issues.apache.org/jira/browse/GEODE-2215
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce Schuchardt
Assignee: Mark Bretl
I saw an NPE in a ViewCreator thread and created this unit test to reproduce
the problem:
{code}
public void testNullPublicKeysNotRetained() throws Exception {
NetView view = new NetView(members.get(0), 2, new ArrayList<>(members));
setFailureDetectionPorts(view);
NetView newView = new NetView(view, 3);
for (InternalDistributedMember member: view.getMembers()) {
view.setPublicKey(member, null);
}
newView.setPublicKeys(view);
for (InternalDistributedMember member: view.getMembers()){
assertNull(newView.getPublicKey(member));
assertNull(view.getPublicKey(member));
}
}
{code}
The problem seems to be that some Maps that NetView uses to hold these keys
accept null values whlie others do not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1550) CI Failure: MembershipJUnitTest.testMultipleManagersInSameProcess assertion failure
[ https://issues.apache.org/jira/browse/GEODE-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-1550: Assignee: (was: Anthony Baker) > CI Failure: MembershipJUnitTest.testMultipleManagersInSameProcess assertion > failure > --- > > Key: GEODE-1550 > URL: https://issues.apache.org/jira/browse/GEODE-1550 > Project: Geode > Issue Type: Bug > Components: membership, messaging >Reporter: Scott Jewell > Labels: CI > > java.lang.AssertionError: Expected a multicast message to be received > at org.junit.Assert.fail(Assert.java:88) > at > com.gemstone.gemfire.distributed.internal.membership.MembershipJUnitTest.testMultipleManagersInSameProcess(MembershipJUnitTest.java:178) > 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.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.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.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:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.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.ThreadPoolEx
[jira] [Resolved] (GEODE-2213) Deadlock in GMSJoinLeaveJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2213.
-
Resolution: Fixed
Fix Version/s: 1.1.0
> Deadlock in GMSJoinLeaveJUnitTest
> -
>
> Key: GEODE-2213
> URL: https://issues.apache.org/jira/browse/GEODE-2213
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> My precheckin run hung in integrationTests with this deadlock:
> {noformat}
> Found one Java-level deadlock:
> =
> "Geode Membership View Creator":
> waiting to lock monitor 0x153187e8 (object 0xf09102e8, a
> java.util.LinkedList),
> which is held by "Test worker"
> "Test worker":
> waiting to lock monitor 0x149d5ad8 (object 0xf09227a8, a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator),
> which is held by "Geode Membership View Creator"
> Java stack information for the threads listed above:
> ===
> "Geode Membership View Creator":
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2153)
> - waiting to lock <0xf09102e8> (a java.util.LinkedList)
> - locked <0xf09227a8> (a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2137)
> "Test worker":
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2143)
> - waiting to lock <0xf09227a8> (a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.recordViewRequest(GMSJoinLeave.java:679)
> - locked <0xf09102e8> (a java.util.LinkedList)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:666)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1704)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeaveJUnitTest.testViewNotSentWhenShuttingDown(GMSJoinLeaveJUnitTest.java:1103)
> {noformat}
> This looks like a pretty straightforward lock inversion that could happen any
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2215) NPE in ViewCreator thread setting public keys into a NetView
[
https://issues.apache.org/jira/browse/GEODE-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2215.
-
Resolution: Fixed
Assignee: Bruce Schuchardt (was: Mark Bretl)
Fix Version/s: 1.1.0
> NPE in ViewCreator thread setting public keys into a NetView
>
>
> Key: GEODE-2215
> URL: https://issues.apache.org/jira/browse/GEODE-2215
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> I saw an NPE in a ViewCreator thread and created this unit test to reproduce
> the problem:
> {code}
> public void testNullPublicKeysNotRetained() throws Exception {
> NetView view = new NetView(members.get(0), 2, new ArrayList<>(members));
> setFailureDetectionPorts(view);
> NetView newView = new NetView(view, 3);
> for (InternalDistributedMember member: view.getMembers()) {
> view.setPublicKey(member, null);
> }
> newView.setPublicKeys(view);
> for (InternalDistributedMember member: view.getMembers()){
> assertNull(newView.getPublicKey(member));
> assertNull(view.getPublicKey(member));
> }
> }
> {code}
> The problem seems to be that some Maps that NetView uses to hold these keys
> accept null values whlie others do not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2213) Deadlock in GMSJoinLeaveJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-2213:
---
Assignee: Bruce Schuchardt
> Deadlock in GMSJoinLeaveJUnitTest
> -
>
> Key: GEODE-2213
> URL: https://issues.apache.org/jira/browse/GEODE-2213
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> My precheckin run hung in integrationTests with this deadlock:
> {noformat}
> Found one Java-level deadlock:
> =
> "Geode Membership View Creator":
> waiting to lock monitor 0x153187e8 (object 0xf09102e8, a
> java.util.LinkedList),
> which is held by "Test worker"
> "Test worker":
> waiting to lock monitor 0x149d5ad8 (object 0xf09227a8, a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator),
> which is held by "Geode Membership View Creator"
> Java stack information for the threads listed above:
> ===
> "Geode Membership View Creator":
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2153)
> - waiting to lock <0xf09102e8> (a java.util.LinkedList)
> - locked <0xf09227a8> (a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2137)
> "Test worker":
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.informToPendingJoinRequests(GMSJoinLeave.java:2143)
> - waiting to lock <0xf09227a8> (a
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.recordViewRequest(GMSJoinLeave.java:679)
> - locked <0xf09102e8> (a java.util.LinkedList)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:666)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1704)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeaveJUnitTest.testViewNotSentWhenShuttingDown(GMSJoinLeaveJUnitTest.java:1103)
> {noformat}
> This looks like a pretty straightforward lock inversion that could happen any
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2228) FutureResult.get() does not check for cancellation prior to waiting for a result
Bruce Schuchardt created GEODE-2228:
---
Summary: FutureResult.get() does not check for cancellation prior
to waiting for a result
Key: GEODE-2228
URL: https://issues.apache.org/jira/browse/GEODE-2228
Project: Geode
Issue Type: Bug
Components: distributed lock service
Reporter: Bruce Schuchardt
A system was found hung with a thread in this state:
{noformat}
vm_0_bridge1_w1-gst-dev23_17330:ServerConnection on port 21566 Thread 352
ID=861 state=TIMED_WAITING
waiting to lock
at sun.misc.Unsafe.park(Native Method)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
at
com.gemstone.gemfire.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:55)
at
com.gemstone.gemfire.internal.util.concurrent.FutureResult.get(FutureResult.java:54)
at
com.gemstone.gemfire.distributed.internal.locks.DLockService.waitForLockGrantorFutureResult(DLockService.java:774)
at
com.gemstone.gemfire.distributed.internal.locks.DLockService.notLockGrantorId(DLockService.java:837)
at
com.gemstone.gemfire.distributed.internal.locks.DLockService.releaseTryLocks(DLockService.java:2216)
at
com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.release(TXLockServiceImpl.java:222)
locked
at
com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:91)
at
com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:120)
at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:730)
at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:447)
at
com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:234)
at
com.gemstone.gemfire.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:325)
{noformat}
No other threads were trying to find the lock grantor and further testing
showed that the FutureResult that this thread was using must have been
cancelled by another thread. I wrote a unit test and found that FutureResult
is not respecting its cancelled state in its get() methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2228) FutureResult.get() does not check for cancellation prior to waiting for a result
[
https://issues.apache.org/jira/browse/GEODE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-2228:
---
Assignee: Bruce Schuchardt
> FutureResult.get() does not check for cancellation prior to waiting for a
> result
> -
>
> Key: GEODE-2228
> URL: https://issues.apache.org/jira/browse/GEODE-2228
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>
> A system was found hung with a thread in this state:
> {noformat}
> vm_0_bridge1_w1-gst-dev23_17330:ServerConnection on port 21566 Thread 352
> ID=861 state=TIMED_WAITING
> waiting to lock
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
> at
> com.gemstone.gemfire.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:55)
> at
> com.gemstone.gemfire.internal.util.concurrent.FutureResult.get(FutureResult.java:54)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.waitForLockGrantorFutureResult(DLockService.java:774)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.notLockGrantorId(DLockService.java:837)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.releaseTryLocks(DLockService.java:2216)
> at
> com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.release(TXLockServiceImpl.java:222)
> locked
> at
> com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:91)
> at
> com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:120)
> at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:730)
> at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:447)
> at
> com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:234)
> at
> com.gemstone.gemfire.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:325)
> {noformat}
> No other threads were trying to find the lock grantor and further testing
> showed that the FutureResult that this thread was using must have been
> cancelled by another thread. I wrote a unit test and found that FutureResult
> is not respecting its cancelled state in its get() methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1893) remove ability to create a locator without all location services
[ https://issues.apache.org/jira/browse/GEODE-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-1893: --- Assignee: Bruce Schuchardt > remove ability to create a locator without all location services > > > Key: GEODE-1893 > URL: https://issues.apache.org/jira/browse/GEODE-1893 > Project: Geode > Issue Type: Wish > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > > Both the API and DistributedSystem properties allow you to create a Locator > that has server or peer location services disabled. These options should > never have been added and need to be removed. A Locator should always start > all location services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2024) Deadlock creating a new distributed lock service Grantor while transactions are in progress
[
https://issues.apache.org/jira/browse/GEODE-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2024.
-
Resolution: Fixed
Fixed in GEODE-2228. FutureResult wasn't checking for cancellation in its
get(time,timeunit) method.
> Deadlock creating a new distributed lock service Grantor while transactions
> are in progress
> ---
>
> Key: GEODE-2024
> URL: https://issues.apache.org/jira/browse/GEODE-2024
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> An integration test running transactions in client caches while servers are
> killed and restarted one by one encountered a hang when the server currrently
> serving as the distributed-lock "grantor" was killed and another server
> attempted to take on the role.
> The stack traces below are from a build prior to package renaming.
> TX commit thread:
> {noformat}
> vm_0_bridge1_w1-gst-dev23_17330:ServerConnection on port 21566 Thread 352
> ID=861 state=TIMED_WAITING
> waiting to lock
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
> at
> com.gemstone.gemfire.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:55)
> at
> com.gemstone.gemfire.internal.util.concurrent.FutureResult.get(FutureResult.java:54)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.waitForLockGrantorFutureResult(DLockService.java:774)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.notLockGrantorId(DLockService.java:837)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.releaseTryLocks(DLockService.java:2216)
> at
> com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.release(TXLockServiceImpl.java:222)
> locked
> at
> com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:91)
> at
> com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:120)
> at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:730)
> at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:447)
> at
> com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:234)
> at
> com.gemstone.gemfire.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:325)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.command.CommitCommand.cmdExecute(CommitCommand.java:80)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:177)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:799)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:930)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1179)
> 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:555)
> at java.lang.Thread.run(Thread.java:745)
> Locked synchronizers:
> java.util.concurrent.ThreadPoolExecutor$Worker@549109017
> java.util.concurrent.locks.ReentrantLock$NonfairSync@317942158
> {noformat}
> Grantor trying to recover:
> {noformat}
> "ServerConnection on port 21566 Thread 356" daemon prio=10
> tid=0x7f9cf8020800 nid=0x5c9e waiting on condition [0x7f9c698d6000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xf4f2e4d0> (a
> java.util.concurrent.CountDownLatch$Sync)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
> at
> com.gemstone.gemfire.inter
[jira] [Created] (GEODE-2235) test is missing @Test: PrCqUsingPoolDUnitTest.testCqOnAccessorServerWithUpdatesResultingInDestroyedCQEvents
Bruce Schuchardt created GEODE-2235: --- Summary: test is missing @Test: PrCqUsingPoolDUnitTest.testCqOnAccessorServerWithUpdatesResultingInDestroyedCQEvents Key: GEODE-2235 URL: https://issues.apache.org/jira/browse/GEODE-2235 Project: Geode Issue Type: Test Components: cq Reporter: Bruce Schuchardt I noticed that this test is missing @Test. It wasn't added when we switched to JUnit4 so it's no longer being executed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1893) remove ability to create a locator without all location services
[ https://issues.apache.org/jira/browse/GEODE-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-1893. - Resolution: Fixed Fix Version/s: 1.1.0 > remove ability to create a locator without all location services > > > Key: GEODE-1893 > URL: https://issues.apache.org/jira/browse/GEODE-1893 > Project: Geode > Issue Type: Wish > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.1.0 > > > Both the API and DistributedSystem properties allow you to create a Locator > that has server or peer location services disabled. These options should > never have been added and need to be removed. A Locator should always start > all location services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2239) CI failure: org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs
Bruce Schuchardt created GEODE-2239:
---
Summary: CI failure:
org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs
Key: GEODE-2239
URL: https://issues.apache.org/jira/browse/GEODE-2239
Project: Geode
Issue Type: Bug
Components: serialization
Reporter: Bruce Schuchardt
This test failed in Jenkins build #692. It has a hard-coded port 40405 and
fails if the port isn't available.
https://builds.apache.org/job/Geode-nightly/692/testReport/
{noformat}
org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs
Error Details
java.net.BindException: Failed to create server socket on null[40,405]
Stack Trace
java.net.BindException: Failed to create server socket on null[40,405]
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:782)
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:744)
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:711)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:436)
at
org.apache.geode.internal.cache.CacheServerImpl.start(CacheServerImpl.java:318)
at
org.apache.geode.pdx.JSONFormatterJUnitTest.setUp(JSONFormatterJUnitTest.java:59)
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:498)
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.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
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.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
at
org.gradle.internal.concurrent.ExecutorPolicy$
[jira] [Updated] (GEODE-2239) CI failure: org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs
[
https://issues.apache.org/jira/browse/GEODE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-2239:
Labels: ci flaky (was: )
> CI failure: org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs
> -
>
> Key: GEODE-2239
> URL: https://issues.apache.org/jira/browse/GEODE-2239
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Bruce Schuchardt
> Labels: ci, flaky
>
> This test failed in Jenkins build #692. It has a hard-coded port 40405 and
> fails if the port isn't available.
> https://builds.apache.org/job/Geode-nightly/692/testReport/
> {noformat}
> org.apache.geode.pdx.JSONFormatterJUnitTest.testJSONFormatterAPIs
> Error Details
> java.net.BindException: Failed to create server socket on null[40,405]
> Stack Trace
> java.net.BindException: Failed to create server socket on null[40,405]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:782)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:744)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:711)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:436)
> at
> org.apache.geode.internal.cache.CacheServerImpl.start(CacheServerImpl.java:318)
> at
> org.apache.geode.pdx.JSONFormatterJUnitTest.setUp(JSONFormatterJUnitTest.java:59)
> 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:498)
> 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.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> 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.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradl
[jira] [Commented] (GEODE-2232) Rename GemFireConfigException
[ https://issues.apache.org/jira/browse/GEODE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768418#comment-15768418 ] Bruce Schuchardt commented on GEODE-2232: - Wouldn't changing the names of these exceptions cause the serialized form of their subclasses to change? GemFireConfigException is probably fine but there are a lot of subclasses of other "GemFire" exception classes like GemFireException. I have it on my to-do list to merge my backward-compatibility unit testing framework to develop. We could test to see what happens using it. > Rename GemFireConfigException > - > > Key: GEODE-2232 > URL: https://issues.apache.org/jira/browse/GEODE-2232 > Project: Geode > Issue Type: Improvement > Components: docs, general >Reporter: Dor >Assignee: Bruce Schuchardt > Fix For: 1.1.0 > > > All GemFire*Exception classes should be refactor renamed to have Geode as a > prefix instead. > For example: >GemFireConfigException - Should be GeodeConfigException. >GemFireException Should be GeodeException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2232) Rename GemFireConfigException
[ https://issues.apache.org/jira/browse/GEODE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770382#comment-15770382 ] Bruce Schuchardt commented on GEODE-2232: - I did some testing to see if renaming GemFireException to something else would affect the serialization of instances of its subclasses and am happy to report that it did not. That means that this _is_ something that can be handled by the old-client-support service. > Rename GemFireConfigException > - > > Key: GEODE-2232 > URL: https://issues.apache.org/jira/browse/GEODE-2232 > Project: Geode > Issue Type: Improvement > Components: docs, general >Reporter: Dor >Assignee: Bruce Schuchardt > Fix For: 1.1.0 > > > All GemFire*Exception classes should be refactor renamed to have Geode as a > prefix instead. > For example: >GemFireConfigException - Should be GeodeConfigException. >GemFireException Should be GeodeException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2228) FutureResult.get() does not check for cancellation prior to waiting for a result
[
https://issues.apache.org/jira/browse/GEODE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt resolved GEODE-2228.
-
Resolution: Fixed
> FutureResult.get() does not check for cancellation prior to waiting for a
> result
> -
>
> Key: GEODE-2228
> URL: https://issues.apache.org/jira/browse/GEODE-2228
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>
> A system was found hung with a thread in this state:
> {noformat}
> vm_0_bridge1_w1-gst-dev23_17330:ServerConnection on port 21566 Thread 352
> ID=861 state=TIMED_WAITING
> waiting to lock
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1033)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
> at
> com.gemstone.gemfire.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:55)
> at
> com.gemstone.gemfire.internal.util.concurrent.FutureResult.get(FutureResult.java:54)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.waitForLockGrantorFutureResult(DLockService.java:774)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.notLockGrantorId(DLockService.java:837)
> at
> com.gemstone.gemfire.distributed.internal.locks.DLockService.releaseTryLocks(DLockService.java:2216)
> at
> com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.release(TXLockServiceImpl.java:222)
> locked
> at
> com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:91)
> at
> com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:120)
> at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:730)
> at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:447)
> at
> com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:234)
> at
> com.gemstone.gemfire.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:325)
> {noformat}
> No other threads were trying to find the lock grantor and further testing
> showed that the FutureResult that this thread was using must have been
> cancelled by another thread. I wrote a unit test and found that FutureResult
> is not respecting its cancelled state in its get() methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2248) DLock unit test code coverage is poor
Bruce Schuchardt created GEODE-2248: --- Summary: DLock unit test code coverage is poor Key: GEODE-2248 URL: https://issues.apache.org/jira/browse/GEODE-2248 Project: Geode Issue Type: Bug Components: distributed lock service Reporter: Bruce Schuchardt Distributed Lock Service unit test code coverage needs to be improved. While some classes have decent coverage others have little or no coverage. DLockQueryProcessor, for instance, has 0% coverage along with DeposeGrantorProcessor DistributedMemberLock and DLockRemoteToken. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2248) DLock unit test code coverage is poor
[ https://issues.apache.org/jira/browse/GEODE-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-2248: Attachment: dlockCodeCoverage.jpg Here is an IntelliJ report of code coverage from the distributedLockTests unit test category. > DLock unit test code coverage is poor > - > > Key: GEODE-2248 > URL: https://issues.apache.org/jira/browse/GEODE-2248 > Project: Geode > Issue Type: Bug > Components: distributed lock service >Reporter: Bruce Schuchardt > Attachments: dlockCodeCoverage.jpg > > > Distributed Lock Service unit test code coverage needs to be improved. While > some classes have decent coverage others have little or no coverage. > DLockQueryProcessor, for instance, has 0% coverage along with > DeposeGrantorProcessor DistributedMemberLock and DLockRemoteToken. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-165) Add build support for generating antlr classes from grammar
[
https://issues.apache.org/jira/browse/GEODE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781062#comment-15781062
]
Bruce Schuchardt commented on GEODE-165:
IntelliJ Idea 2016.3.1 builds are broken by this change. A workaround is to do
a command-line build to have the generated-source files be created.
> Add build support for generating antlr classes from grammar
> ---
>
> Key: GEODE-165
> URL: https://issues.apache.org/jira/browse/GEODE-165
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Dan Smith
>Assignee: Avinash Dongre
>
> The OQL engine currently uses antlr to generate some parsing classes from
> gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/oql.g
> These are the generated classes. They are currently checked into the source.
> OQLLexer.java
> OQLLexerTokenTypes.java
> OQLLexerTokenTypes.txt
> OQLParser.java
> They can be generated manually by running antlr.Tool on the provided grammar.
> cd gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/
> java -cp antlr.jar antlr.Tool oql.g
> We should add support to the gradle build to generate these classes.
> In my opinion we should also remove the checked in classes. With gradle we
> can configure things so that the gradle eclipse target will generate these
> classes and make them available to the IDE as well. Look at
> gemfire-core/build.gradle for how we do this with the version properties file:
> sourceSets {
> main {
> output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GEODE-165) Add build support for generating antlr classes from grammar
[
https://issues.apache.org/jira/browse/GEODE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781062#comment-15781062
]
Bruce Schuchardt edited comment on GEODE-165 at 12/27/16 7:24 PM:
--
IntelliJ Idea 2016.3.1 builds are broken by this change. You must close your
project and re-import the gradle build to fix the problem. A workaround is to
generate the absent source files with gradle.
was (Author: bschuchardt):
IntelliJ Idea 2016.3.1 builds are broken by this change. A workaround is to do
a command-line build to have the generated-source files be created.
> Add build support for generating antlr classes from grammar
> ---
>
> Key: GEODE-165
> URL: https://issues.apache.org/jira/browse/GEODE-165
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Dan Smith
>Assignee: Avinash Dongre
>
> The OQL engine currently uses antlr to generate some parsing classes from
> gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/oql.g
> These are the generated classes. They are currently checked into the source.
> OQLLexer.java
> OQLLexerTokenTypes.java
> OQLLexerTokenTypes.txt
> OQLParser.java
> They can be generated manually by running antlr.Tool on the provided grammar.
> cd gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/
> java -cp antlr.jar antlr.Tool oql.g
> We should add support to the gradle build to generate these classes.
> In my opinion we should also remove the checked in classes. With gradle we
> can configure things so that the gradle eclipse target will generate these
> classes and make them available to the IDE as well. Look at
> gemfire-core/build.gradle for how we do this with the version properties file:
> sourceSets {
> main {
> output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
