[jira] [Commented] (GEODE-3472) Code Cleanup: remove dead code from /management.

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3472:
---

Github user galen-pivotal commented on the issue:

https://github.com/apache/geode/pull/730
  
I haven't reviewed this, but :+1: deleting commented code is a GOOD THING.


> Code Cleanup: remove dead code from /management.
> 
>
> Key: GEODE-3472
> URL: https://issues.apache.org/jira/browse/GEODE-3472
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>
> There is a great deal of dead, commented, and unused code in the codebase.  
> This ticket addresses some of it, limiting scope to those files in 
> `geode-core/**/management/**` to keep the eventual diff relatively small.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3447:
---

Github user galen-pivotal commented on a diff in the pull request:

https://github.com/apache/geode/pull/719#discussion_r134635734
  
--- Diff: 
geode-protobuf/src/test/java/org/apache/geode/protocol/AuthorizationIntegrationTest.java
 ---
@@ -0,0 +1,206 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more 
contributor license
+ * agreements. See the NOTICE file distributed with this work for 
additional information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache 
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the 
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software 
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF 
ANY KIND, either express
+ * or implied. See the License for the specific language governing 
permissions and limitations under
+ * the License.
+ */
+package org.apache.geode.protocol;
+
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertTrue;
+import static org.mockito.ArgumentMatchers.any;
+import static org.mockito.ArgumentMatchers.same;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.OutputStream;
+import java.net.Socket;
+import java.util.Properties;
+import java.util.concurrent.TimeUnit;
+
+import org.awaitility.Awaitility;
+import org.junit.After;
+import org.junit.Before;
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.contrib.java.lang.system.RestoreSystemProperties;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.cache.server.CacheServer;
+import org.apache.geode.internal.AvailablePortHelper;
+import org.apache.geode.management.internal.security.ResourceConstants;
+import org.apache.geode.protocol.protobuf.AuthenticationAPI;
+import org.apache.geode.protocol.protobuf.ClientProtocol;
+import org.apache.geode.protocol.protobuf.ProtobufSerializationService;
+import org.apache.geode.protocol.protobuf.ProtocolErrorCode;
+import org.apache.geode.protocol.protobuf.RegionAPI;
+import 
org.apache.geode.protocol.protobuf.serializer.ProtobufProtocolSerializer;
+import org.apache.geode.protocol.protobuf.utilities.ProtobufUtilities;
+import org.apache.geode.security.ResourcePermission;
+import org.apache.geode.security.SecurityManager;
+import 
org.apache.geode.serialization.registry.exception.CodecAlreadyRegisteredForTypeException;
+import org.apache.geode.test.junit.categories.IntegrationTest;
+
+@Category(IntegrationTest.class)
+public class AuthorizationIntegrationTest {
+
+  private static final String TEST_USERNAME = "bob";
+  private static final String TEST_PASSWORD = "bobspassword";
+  public static final String TEST_REGION = "testRegion";
+
+  @Rule
+  public final RestoreSystemProperties restoreSystemProperties = new 
RestoreSystemProperties();
+
+  private Cache cache;
+  private int cacheServerPort;
+  private CacheServer cacheServer;
+  private Socket socket;
+  private OutputStream outputStream;
+  private ProtobufSerializationService serializationService;
+  private InputStream inputStream;
+  private ProtobufProtocolSerializer protobufProtocolSerializer;
+  private Object securityPrincipal;
+  private SecurityManager mockSecurityManager;
+  private String testRegion;
+  public static final ResourcePermission READ_PERMISSION =
+  new ResourcePermission(ResourcePermission.Resource.DATA, 
ResourcePermission.Operation.READ);
+  public static final ResourcePermission WRITE_PERMISSION =
+  new ResourcePermission(ResourcePermission.Resource.DATA, 
ResourcePermission.Operation.WRITE);
+
+  @Before
+  public void setUp() throws IOException, 
CodecAlreadyRegisteredForTypeException {
+Properties expectedAuthProperties = new Properties();
+expectedAuthProperties.setProperty(ResourceConstants.USER_NAME, 
TEST_USERNAME);
+expectedAuthProperties.setProperty(ResourceConstants.PASSWORD, 
TEST_PASSWORD);
+
+securityPrincipal = new Object();
+mockSecurityManager = mock(SecurityManager.class);
+   

[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3447:
---

Github user galen-pivotal commented on a diff in the pull request:

https://github.com/apache/geode/pull/719#discussion_r134633950
  
--- Diff: 
geode-core/src/main/java/org/apache/geode/security/StreamAuthorizer.java ---
@@ -0,0 +1,19 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more 
contributor license
+ * agreements. See the NOTICE file distributed with this work for 
additional information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache 
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the 
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software 
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF 
ANY KIND, either express
+ * or implied. See the License for the specific language governing 
permissions and limitations under
+ * the License.
+ */
+package org.apache.geode.security;
+
+public interface StreamAuthorizer {
+  boolean authorize(ResourcePermission permissionRequested);
--- End diff --

We may need to refactor this at some point when operations start needing 
more than one permission (which depends on whether write authorization implies 
read authorization), but I think that's more than a failing of the security API 
than ours, and it should be possible to do everything we need for the alpha 
anyways (no getAndSet yet).


> Implement client authorization for the new protocol
> ---
>
> Key: GEODE-3447
> URL: https://issues.apache.org/jira/browse/GEODE-3447
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Bruce Schuchardt
>
> As a user of the new client/server protocol, I need to make sure the clients 
> using the protocol to access my grid are authorized to perform each operation 
> they attempt.
> Implement client authorization for operations in new protocol based on 
> existing authorization configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3447:
---

Github user galen-pivotal commented on a diff in the pull request:

https://github.com/apache/geode/pull/719#discussion_r134634705
  
--- Diff: 
geode-protobuf/src/main/java/org/apache/geode/protocol/protobuf/registry/OperationContextRegistry.java
 ---
@@ -47,41 +48,57 @@ private void addContexts() {
 operationContexts.put(RequestAPICase.GETREQUEST,
 new OperationContext<>(ClientProtocol.Request::getGetRequest,
 new GetRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setGetResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setGetResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.READ)));
 
 operationContexts.put(RequestAPICase.GETALLREQUEST,
 new OperationContext<>(ClientProtocol.Request::getGetAllRequest,
 new GetAllRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setGetAllResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setGetAllResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.READ)));
 
 operationContexts.put(RequestAPICase.PUTREQUEST,
 new OperationContext<>(ClientProtocol.Request::getPutRequest,
 new PutRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setPutResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setPutResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.WRITE)));
 
 operationContexts.put(RequestAPICase.PUTALLREQUEST,
 new OperationContext<>(ClientProtocol.Request::getPutAllRequest,
 new PutAllRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setPutAllResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setPutAllResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.WRITE)));
 
 operationContexts.put(RequestAPICase.REMOVEREQUEST,
 new OperationContext<>(ClientProtocol.Request::getRemoveRequest,
 new RemoveRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setRemoveResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setRemoveResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.WRITE)));
 
 operationContexts.put(RequestAPICase.GETREGIONNAMESREQUEST,
 new 
OperationContext<>(ClientProtocol.Request::getGetRegionNamesRequest,
 new GetRegionNamesRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setGetRegionNamesResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setGetRegionNamesResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.READ)));
 
 operationContexts.put(RequestAPICase.GETREGIONREQUEST,
 new OperationContext<>(ClientProtocol.Request::getGetRegionRequest,
 new GetRegionRequestOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setGetRegionResponse(opsResp)));
+opsResp -> 
ClientProtocol.Response.newBuilder().setGetRegionResponse(opsResp),
+new ResourcePermission(ResourcePermission.Resource.DATA,
+ResourcePermission.Operation.READ)));
 
-operationContexts.put(RequestAPICase.GETAVAILABLESERVERSREQUEST, new 
OperationContext<>(
-ClientProtocol.Request::getGetAvailableServersRequest,
-new GetAvailableServersOperationHandler(),
-opsResp -> 
ClientProtocol.Response.newBuilder().setGetAvailableServersResponse(opsResp)));
+operationContexts.put(RequestAPICase.GETAVAILABLESERVERSREQUEST,
--- End diff --

This is one that should be authorized for either read or write... is read a 
subset of write? I don't know.


> Implement client authorization for the new protocol
> ---
>
> Key: GEODE-3447
> URL: https://issues.apache.org/jira/browse/

[jira] [Reopened] (GEODE-3249) Validate internal client/server messages

2017-08-22 Thread Karen Smoler Miller (JIRA)

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

Karen Smoler Miller reopened GEODE-3249:

  Assignee: Karen Smoler Miller  (was: Bruce Schuchardt)

I've re-opened this ticket, as a small docs task goes with it. 

> Validate internal client/server messages
> 
>
> Key: GEODE-3249
> URL: https://issues.apache.org/jira/browse/GEODE-3249
> Project: Geode
>  Issue Type: Bug
>  Components: docs, messaging
>Reporter: Anthony Baker
>Assignee: Karen Smoler Miller
> Fix For: 1.3.0, 1.2.1
>
>
> Some message types can not be invoked directly by an end user.  For 
> validation purposes, we should treat these messages the same way we treat 
> normal messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (GEODE-3507) actualRedundantCopies stat in org.apache.geode.internal.cache.PartitionedRegionStats can go negative

2017-08-22 Thread Lynn Gallinat (JIRA)
Lynn Gallinat created GEODE-3507:


 Summary: actualRedundantCopies stat in 
org.apache.geode.internal.cache.PartitionedRegionStats can go negative
 Key: GEODE-3507
 URL: https://issues.apache.org/jira/browse/GEODE-3507
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Lynn Gallinat


The actualRedundantCopies can be set to a negative value through the 
org.apache.geode.internal.cache.PartitionedRegionRedundancyTrackerTest class. 
This behavior was introduced in the fix for GEODE-3049.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3507) actualRedundantCopies stat in org.apache.geode.internal.cache.PartitionedRegionStats can go negative

2017-08-22 Thread Lynn Gallinat (JIRA)

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

Lynn Gallinat reassigned GEODE-3507:


Assignee: Lynn Gallinat

> actualRedundantCopies stat in 
> org.apache.geode.internal.cache.PartitionedRegionStats can go negative
> 
>
> Key: GEODE-3507
> URL: https://issues.apache.org/jira/browse/GEODE-3507
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Lynn Gallinat
>Assignee: Lynn Gallinat
>
> The actualRedundantCopies can be set to a negative value through the 
> org.apache.geode.internal.cache.PartitionedRegionRedundancyTrackerTest class. 
> This behavior was introduced in the fix for GEODE-3049.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3276) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > testParallelPropagationWithRemoteRegionDestroy FAILED

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3276:
---

Github user jhuynh1 commented on a diff in the pull request:

https://github.com/apache/geode/pull/732#discussion_r134622619
  
--- Diff: 
geode-wan/src/main/java/org/apache/geode/internal/cache/wan/parallel/ParallelGatewaySenderImpl.java
 ---
@@ -107,6 +107,9 @@ public void stop() {
   if (ev != null && !ev.isStopped()) {
 ev.stopProcessing();
   }
+  if (ev != null && ev.getDispatcher() != null) {
--- End diff --

Is it possible to pull this check and shutdown into a method?  Looks like 
it's used a few times throughout the code


> CI failure: 
> org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > 
> testParallelPropagationWithRemoteRegionDestroy FAILED
> --
>
> Key: GEODE-3276
> URL: https://issues.apache.org/jira/browse/GEODE-3276
> Project: Geode
>  Issue Type: Bug
>  Components: statistics, wan
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: nabarun
>
> {noformat}
> org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > 
> testParallelPropagationWithRemoteRegionDestroy FAILED
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
> Caused by:
> java.lang.OutOfMemoryError: Java heap space
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund commented on GEODE-3506:
--

I suspect this is a real bug and not a flaky test.

> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails 
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}
> Full stack trace:
> {noformat}
> java.lang.IllegalStateException: Failed to read status file
> at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at 
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
> at 
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
> at 
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
> at 
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at 
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3506:
-
Component/s: (was: tests)

> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails 
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}
> Full stack trace:
> {noformat}
> java.lang.IllegalStateException: Failed to read status file
> at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at 
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
> at 
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
> at 
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
> at 
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at 
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3506:
-
Description: 
{noformat}
org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
startDeletesStaleControlFiles FAILED
java.lang.IllegalStateException: Failed to read status file
{noformat}
Full stack trace:
{noformat}
java.lang.IllegalStateException: Failed to read status file
at 
org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
at 
org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
at 
org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
at 
org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
at 
org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
at 
org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
at 
org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}

  was:
{noformat}
org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
startDeletesStaleControlFiles FAILED
java.lang.IllegalStateException: Failed to read status file
{noformat}


> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails 
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}
> Full stack trace:
> {noformat}
> java.lang.IllegalStateException: Failed to read status file
> at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at 
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
> at 
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
> at 
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
> at 
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at 
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (GEODE-3461) BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-3461.
--
   Resolution: Fixed
Fix Version/s: 1.3.0

> BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3461
> URL: https://issues.apache.org/jira/browse/GEODE-3461
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: CI, Flaky
> Fix For: 1.3.0
>
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
> expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest.waitUntilProcessStops(AbstractProcessStreamReaderIntegrationTest.java:169)
> at 
> org.apache.geode.internal.process.BaseProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed(BaseProcessStreamReaderIntegrationTest.java:48)
> 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.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.Deleg

[jira] [Resolved] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-3505.
--
   Resolution: Fixed
Fix Version/s: 1.3.0

> NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> 
>
> Key: GEODE-3505
> URL: https://issues.apache.org/jira/browse/GEODE-3505
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: Flaky
> Fix For: 1.3.0
>
>
> {noformat}
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
>  > processTerminatesWhenDestroyed FAILED
> org.awaitility.core.ConditionTimeoutException: Condition defined as a 
> lambda expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (GEODE-3164) ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails intermittently with AssertionError

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-3164.
--
   Resolution: Fixed
Fix Version/s: 1.3.0

> ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails 
> intermittently with AssertionError
> --
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky
> Fix For: 1.3.0
>
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3461) BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3461:
---

Github user asfgit closed the pull request at:

https://github.com/apache/geode/pull/729


> BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3461
> URL: https://issues.apache.org/jira/browse/GEODE-3461
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: CI, Flaky
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
> expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest.waitUntilProcessStops(AbstractProcessStreamReaderIntegrationTest.java:169)
> at 
> org.apache.geode.internal.process.BaseProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed(BaseProcessStreamReaderIntegrationTest.java:48)
> 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.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.NativeMethodAcce

[jira] [Commented] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3505:


Commit 6f7667d90e56d4dec6f2670a1c46e40b4e354026 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=6f7667d ]

GEODE-3461: increase test timeouts

Also fixes:
* GEODE-3505

This closes #729


> NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> 
>
> Key: GEODE-3505
> URL: https://issues.apache.org/jira/browse/GEODE-3505
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: Flaky
>
> {noformat}
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
>  > processTerminatesWhenDestroyed FAILED
> org.awaitility.core.ConditionTimeoutException: Condition defined as a 
> lambda expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3164) ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails intermittently with AssertionError

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3164:


Commit afded2a8d960359f4e319e76bf5e39720151ae0d in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=afded2a ]

GEODE-3164: fix flakiness with await


> ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails 
> intermittently with AssertionError
> --
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-2859) ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction failing in CI.

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-2859:


Commit a0ad56896a8ed183f1e1db0ddc24e6857640de58 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a0ad568 ]

GEODE-2859: minor cleanup


> ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction failing in CI.
> 
>
> Key: GEODE-2859
> URL: https://issues.apache.org/jira/browse/GEODE-2859
> Project: Geode
>  Issue Type: Test
>  Components: gfsh, membership, messaging, tests
>Reporter: Galen O'Sullivan
>Assignee: Jared Stewart
> Fix For: 1.2.0
>
>
> https://builds.apache.org/job/Geode-nightly/821/
> This test is a copy of GemFireDeadlockDetectorDUnitTest.java, which was 
> recently updated (https://reviews.apache.org/r/58541/diff/1#index_header). 
> Probably it needs the same fix or related.
> ShowDeadlockDUnitTest.testNoDeadlock also fails in this test run.
> {code}
> Error Message
> java.lang.AssertionError
> Stacktrace
> 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.management.internal.cli.commands.ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction(ShowDeadlockDUnitTest.java:156)
>   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.refl

[jira] [Commented] (GEODE-3461) BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3461:


Commit 6f7667d90e56d4dec6f2670a1c46e40b4e354026 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=6f7667d ]

GEODE-3461: increase test timeouts

Also fixes:
* GEODE-3505

This closes #729


> BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3461
> URL: https://issues.apache.org/jira/browse/GEODE-3461
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: CI, Flaky
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
> expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest.waitUntilProcessStops(AbstractProcessStreamReaderIntegrationTest.java:169)
> at 
> org.apache.geode.internal.process.BaseProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed(BaseProcessStreamReaderIntegrationTest.java:48)
> 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.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 
> o

[jira] [Commented] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails intermittently with ConditionTimeoutException

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3335:


Commit c95b32ee8c95f2a95767ce771eb6b2f5ee8492c7 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c95b32e ]

GEODE-3335: add FlakyTest category to testNavigationAPIS


> CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails 
> intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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.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.process

[jira] [Commented] (GEODE-3395) Variable-ize product version and name in user guide

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3395:


Commit e2c3d531f6bf7aeddb0ce38ab356ec415e32fb48 in geode's branch 
refs/heads/feature/GEODE-3447 from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=e2c3d53 ]

GEODE-3395 Variable-ize product version and name in user guide - Topo & Comms


>  Variable-ize product version and name in user guide
> 
>
> Key: GEODE-3395
> URL: https://issues.apache.org/jira/browse/GEODE-3395
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>
> The Guide contains many occurrences of the product version string ("1.2", 
> "1.1", and "1.0-incubating" are recent examples) scattered over about 900 
> files.  It would be a great convenience to those who write and edit these 
> files to define the version number symbolically so it could be updated in one 
> central location. A template variable in the book's config.yml file would be 
> an obvious candidate for the implementation.
> Similarly, it would be handy to provide symbolic identifiers for the product 
> name, long and short: "Apache Geode" and "Geode", respectively.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3447:


Commit a2b678aa06af73d218da6e9ae8d95f2942d23a7b in geode's branch 
refs/heads/feature/GEODE-3447 from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a2b678a ]

GEODE-3447 Implement client authorization for the new protocol

Implementation of authorization checks for the new protocol.


> Implement client authorization for the new protocol
> ---
>
> Key: GEODE-3447
> URL: https://issues.apache.org/jira/browse/GEODE-3447
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Bruce Schuchardt
>
> As a user of the new client/server protocol, I need to make sure the clients 
> using the protocol to access my grid are authorized to perform each operation 
> they attempt.
> Implement client authorization for operations in new protocol based on 
> existing authorization configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit 0cc60434cd75814e755b88be39af53b32d53faeb in geode's branch 
refs/heads/feature/GEODE-3447 from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0cc6043 ]

GEODE-3406: Address more PR feedback

Signed-off-by: Alexander Murmann 


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Hitesh Khamesra
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3047) CI failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs (ConflictingPersistentDataException)

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3047:


Commit 35d3a97edd5c6e8b3f4dd73af51771b0c4728cf6 in geode's branch 
refs/heads/feature/GEODE-3447 from [~agingade]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=35d3a97 ]

GEODE-3047 Atomic creation flag is not set if the region is recoverd from the 
disk.

While creating bucket region, to satisfy the redudndancy copies the bucket 
regions
are created on all vailable nodes. The initialization (setting persistentIDs) of
these buckets are done after creating buckets on all the nodes. This introduced
a race condition for the bucket region which are recovered from the disk to
exchange thier old id with the peer node resulting in ConflictingPersistentData
Exception.

The changes are done so that the regions persistent ids are set as soon as they
are created/initialized.


> CI failure: 
> PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs 
> (ConflictingPersistentDataException)
> ---
>
> Key: GEODE-3047
> URL: https://issues.apache.org/jira/browse/GEODE-3047
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Lynn Gallinat
>Assignee: Anilkumar Gingade
> Fix For: 1.3.0
>
>
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest > 
> testClientMetadataForPersistentPrs FAILED
> 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 11823
> [error 2017/06/05 16:15:06.807 UTC  _B__CUSTOMER_0> tid=0xe9] A DiskAccessException has occurred while writing to 
> the disk for region /__PR/_B__SHIPMENT_0. The cache will be closed.
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: 
> Region /__PR/_B__SHIPMENT_0 refusing to initialize from member 
> 172.17.0.3(177):32773 with persistent data 
> /172.17.0.3:/tmp/gemfire-build/geode/geode-core/build/distributedTest305/dunit/vm1/diskDir/disk1
>  created at timestamp 1496679288068 version 0 diskStoreId 
> bd6add692799471a-af82daaafb9c36e8 name null which was offline when the local 
> data from 
> /172.17.0.3:/tmp/gemfire-build/geode/geode-core/build/distributedTest305/dunit/vm2/diskDir/disk2
>  created at timestamp 1496679291626 version 0 diskStoreId 
> 5a4a04c19efe4961-90fba2925786d398 name null was last online
>   at 
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:757)
>   at 
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:818)
>   at 
> org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1144)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1023)
>   at 
> org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:253)
>   at 
> org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:962)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:726)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:414)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucketRecursively(PartitionedRegionDataStore.java:272)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucketRecursively(PartitionedRegionDataStore.java:289)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2815)
>   at 
> org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:423)
>   at 
> org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:389)
>   at 
> org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1736)
>   at 
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:61)
>   at 
> org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.java:1728)
>   at java.lang.Thread.run(Thread.java:748)




[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit 31e82d6d64187ba7a6d71771806a0b107a811c11 in geode's branch 
refs/heads/feature/GEODE-3447 from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=31e82d6 ]

GEODE-3406: Fixed test failures.

Now TcpServerFactory doesn't look for protobuf enabled property.
If service is not available then it just ignores that


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Hitesh Khamesra
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3472) Code Cleanup: remove dead code from /management.

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3472:
---

Github user PurelyApplied commented on a diff in the pull request:

https://github.com/apache/geode/pull/730#discussion_r134618712
  
--- Diff: 
geode-core/src/main/java/org/apache/geode/management/internal/cli/result/AbstractResultData.java
 ---
@@ -147,11 +147,10 @@ public ResultData addAsFile(String fileName, String 
fileContents, String message
 
   public ResultData addAsFile(String fileName, byte[] data, int fileType, 
String message,
   boolean addTimeStampToName) {
-byte[] bytes = data;
--- End diff --

I might by projecting my Python and C expectations into my relatively new 
Java experience, but I thought this assignment wouldn't change the mutability 
of `data`.  Wouldn't this need `byte[] bytes = data.clone();` to actually 
provided immutability to `data`?  Or is Java more defensive than I realized?


> Code Cleanup: remove dead code from /management.
> 
>
> Key: GEODE-3472
> URL: https://issues.apache.org/jira/browse/GEODE-3472
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>
> There is a great deal of dead, commented, and unused code in the codebase.  
> This ticket addresses some of it, limiting scope to those files in 
> `geode-core/**/management/**` to keep the eventual diff relatively small.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3395) Variable-ize product version and name in user guide

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3395:


Commit c0f6c841862c64a0b82594045320e82f558452ba in geode's branch 
refs/heads/feature/GEODE-3447 from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c0f6c84 ]

GEODE-3395 Variable-ize product version and name in user guide - Topo & Comms, 
format repair


>  Variable-ize product version and name in user guide
> 
>
> Key: GEODE-3395
> URL: https://issues.apache.org/jira/browse/GEODE-3395
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>
> The Guide contains many occurrences of the product version string ("1.2", 
> "1.1", and "1.0-incubating" are recent examples) scattered over about 900 
> files.  It would be a great convenience to those who write and edit these 
> files to define the version number symbolically so it could be updated in one 
> central location. A template variable in the book's config.yml file would be 
> an obvious candidate for the implementation.
> Similarly, it would be handy to provide symbolic identifiers for the product 
> name, long and short: "Apache Geode" and "Geode", respectively.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3445) Add Gfsh Connect option --skip-ssl-validation

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3445:


Commit b77e1c7d1e1dc31a539496483c8e9f739155f021 in geode's branch 
refs/heads/feature/GEODE-3447 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b77e1c7 ]

GEODE-3445: Add gfsh connect option --skip-ssl-validation


> Add Gfsh Connect option --skip-ssl-validation
> -
>
> Key: GEODE-3445
> URL: https://issues.apache.org/jira/browse/GEODE-3445
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> We have users who would like to connect to a locator from gfsh over HTTPS 
> without verifying the hostname of the locator.  (This is a common pattern in 
> testing environments or where self-signed certificates are used.)  We already 
> have some code used for tests to enable this behavior:
> {noformat}
>// This is for testing purpose only. If we remove this piece of code we 
> will
> // get a java.security.cert.CertificateException
> // as matching hostname can not be obtained in all test environment.
> HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier() {
>   @Override
>   public boolean verify(String string, SSLSession ssls) {
> return true;
>   }
> });
> {noformat}
> We just need to conditionally call this code inside Gfsh Connect if the 
> --skip-ssl-validation option is specified.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit a4fc1ddf628766cd5f3e7fb9e9469f523d20dbf2 in geode's branch 
refs/heads/feature/GEODE-3447 from [~amurmann]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a4fc1dd ]

GEODE-3406: Exclude new exception class from analyze serialiable test

Signed-off-by: Hitesh Khamesra 


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Hitesh Khamesra
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file

2017-08-22 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-3506:


 Summary: 
LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails 
intermittently with IllegalStateException: Failed to read status file
 Key: GEODE-3506
 URL: https://issues.apache.org/jira/browse/GEODE-3506
 Project: Geode
  Issue Type: Bug
  Components: gfsh, management, tests
Reporter: Kirk Lund


{noformat}
org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
startDeletesStaleControlFiles FAILED
java.lang.IllegalStateException: Failed to read status file
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-3506:


Assignee: Kirk Lund

> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails 
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3461) BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3461:
---

Github user kirklund commented on the issue:

https://github.com/apache/geode/pull/729
  
This PR should also fix GEODE-3505.


> BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3461
> URL: https://issues.apache.org/jira/browse/GEODE-3461
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: CI, Flaky
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
> expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest.waitUntilProcessStops(AbstractProcessStreamReaderIntegrationTest.java:169)
> at 
> org.apache.geode.internal.process.BaseProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed(BaseProcessStreamReaderIntegrationTest.java:48)
> 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.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)

[jira] [Assigned] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-3505:


Assignee: Kirk Lund

> NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> 
>
> Key: GEODE-3505
> URL: https://issues.apache.org/jira/browse/GEODE-3505
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: Flaky
>
> {noformat}
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
>  > processTerminatesWhenDestroyed FAILED
> org.awaitility.core.ConditionTimeoutException: Condition defined as a 
> lambda expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund commented on GEODE-3505:
--

I think this test failure has the same underlying cause as GEODE-3461.

> NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> 
>
> Key: GEODE-3505
> URL: https://issues.apache.org/jira/browse/GEODE-3505
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>  Labels: Flaky
>
> {noformat}
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
>  > processTerminatesWhenDestroyed FAILED
> org.awaitility.core.ConditionTimeoutException: Condition defined as a 
> lambda expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3505:
-
Labels: Flaky  (was: )

> NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> 
>
> Key: GEODE-3505
> URL: https://issues.apache.org/jira/browse/GEODE-3505
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, tests
>Reporter: Kirk Lund
>  Labels: Flaky
>
> {noformat}
> org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest
>  > processTerminatesWhenDestroyed FAILED
> org.awaitility.core.ConditionTimeoutException: Condition defined as a 
> lambda expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3461) BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3461:
-
Summary: 
BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails 
intermittently with ConditionTimeoutException  (was: 
BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails 
intermittently)

> BlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
> fails intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3461
> URL: https://issues.apache.org/jira/browse/GEODE-3461
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: CI, Flaky
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
> expression in 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
> expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at 
> org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest.waitUntilProcessStops(AbstractProcessStreamReaderIntegrationTest.java:169)
> at 
> org.apache.geode.internal.process.BaseProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed(BaseProcessStreamReaderIntegrationTest.java:48)
> 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.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.Nati

[jira] [Created] (GEODE-3505) NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-3505:


 Summary: 
NonBlockingProcessStreamReaderIntegrationTest.processTerminatesWhenDestroyed 
fails intermittently with ConditionTimeoutException
 Key: GEODE-3505
 URL: https://issues.apache.org/jira/browse/GEODE-3505
 Project: Geode
  Issue Type: Bug
  Components: gfsh, management, tests
Reporter: Kirk Lund


{noformat}
org.apache.geode.internal.process.NonBlockingProcessStreamReaderIntegrationTest 
> processTerminatesWhenDestroyed FAILED
org.awaitility.core.ConditionTimeoutException: Condition defined as a 
lambda expression in 
org.apache.geode.internal.process.AbstractProcessStreamReaderIntegrationTest 
expected:<[fals]e> but was:<[tru]e> within 2 milliseconds.
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3472) Code Cleanup: remove dead code from /management.

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3472:
---

Github user pdxrunner commented on a diff in the pull request:

https://github.com/apache/geode/pull/730#discussion_r134616035
  
--- Diff: 
geode-core/src/main/java/org/apache/geode/management/internal/cli/result/AbstractResultData.java
 ---
@@ -147,11 +147,10 @@ public ResultData addAsFile(String fileName, String 
fileContents, String message
 
   public ResultData addAsFile(String fileName, byte[] data, int fileType, 
String message,
   boolean addTimeStampToName) {
-byte[] bytes = data;
--- End diff --

I think the contents of `data` should be treated as if it were immutable in 
this usage, so don't make this and the following change.


> Code Cleanup: remove dead code from /management.
> 
>
> Key: GEODE-3472
> URL: https://issues.apache.org/jira/browse/GEODE-3472
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>
> There is a great deal of dead, commented, and unused code in the codebase.  
> This ticket addresses some of it, limiting scope to those files in 
> `geode-core/**/management/**` to keep the eventual diff relatively small.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3276) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > testParallelPropagationWithRemoteRegionDestroy FAILED

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3276:
---

GitHub user nabarunnag opened a pull request:

https://github.com/apache/geode/pull/732

GEODE-3276: Managing race conditions while the senders are stopped

* When a connection is initialized, a readAckThread may be alive from a 
previous incarnation.
* This AckThread will be stuck on a read socket with no timeout as 
nothing was dispatched.
* Also while it was stuck on the read, it will hold a connection 
lifecycle read lock
* The initialize connection needs a connection life cycle write lock to 
start the connection but the read lock is held by the ack thread.
* This results in a deadlock and eventually a hang.
* Another situation is that we set the flag isStopped for the event 
processor before actually shutting down the diapatcher and ack thread.
* So after the flag is set and before actually shutting down the 
dispatcher and ackThread, a gateway proxy stomper thread gets in between these 
two steps of execution.
* The stomper thread checks the isStopped flag, which was set to true, 
and proceeds to destroy the connection pool. However the dispatcher and 
ackThread were still running.
* This results in a out of heap memory exception while the ack thread 
is reading from the socket while connection pool was destroyed.
* To solve this issue, the stomper thread checks if the event processor 
and dispatcher exists, if true then we close the input streams before 
destroying the connection pool.

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [ ] Does `gradlew build` run cleanly?

- [ ] Have you written or updated unit tests to verify your changes?

- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to d...@geode.apache.org.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nabarunnag/incubator-geode feature/GEODE-3276

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/geode/pull/732.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #732


commit 9618f69d2620f5a3d3a6a8576631906a61b512f9
Author: nabarun 
Date:   2017-08-17T17:51:15Z

GEODE-3276: Managing race conditions while the senders are stopped

* When a connection is initialized, a readAckThread may be alive from a 
previous incarnation.
* This AckThread will be stuck on a read socket with no timeout as 
nothing was dispatched.
* Also while it was stuck on the read, it will hold a connection 
lifecycle read lock
* The initialize connection needs a connection life cycle write lock to 
start the connection but the read lock is held by the ack thread.
* This results in a deadlock and eventually a hang.
* Another situation is that we set the flag isStopped for the event 
processor before actually shutting down the diapatcher and ack thread.
* So after the flag is set and before actually shutting down the 
dispatcher and ackThread, a gateway proxy stomper thread gets in between these 
two steps of execution.
* The stomper thread checks the isStopped flag, which was set to true, 
and proceeds to destroy the connection pool. However the dispatcher and 
ackThread were still running.
* This results in a out of heap memory exception while the ack thread 
is reading from the socket while connection pool was destroyed.
* To solve this issue, the stomper thread checks if the event processor 
and dispatcher exists, if true then we close the input streams before 
destroying the connection pool.




> CI failure: 
> org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > 
> testParallelPropagationWithRemoteRegionDestroy FAILED
> --

[jira] [Commented] (GEODE-3308) Add lucene backward compatibility and rolling upgrade dunit tests

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3308:
---

Github user nabarunnag closed the pull request at:

https://github.com/apache/geode/pull/659


> Add lucene backward compatibility and rolling upgrade dunit tests 
> --
>
> Key: GEODE-3308
> URL: https://issues.apache.org/jira/browse/GEODE-3308
> Project: Geode
>  Issue Type: Test
>  Components: lucene
>Reporter: nabarun
>Assignee: nabarun
> Fix For: 1.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3276) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > testParallelPropagationWithRemoteRegionDestroy FAILED

2017-08-22 Thread nabarun (JIRA)

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

nabarun reassigned GEODE-3276:
--

Assignee: nabarun

> CI failure: 
> org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > 
> testParallelPropagationWithRemoteRegionDestroy FAILED
> --
>
> Key: GEODE-3276
> URL: https://issues.apache.org/jira/browse/GEODE-3276
> Project: Geode
>  Issue Type: Bug
>  Components: statistics, wan
>Affects Versions: 1.2.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: nabarun
>
> {noformat}
> org.apache.geode.internal.cache.wan.parallel.ParallelWANStatsDUnitTest > 
> testParallelPropagationWithRemoteRegionDestroy FAILED
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
> Caused by:
> java.lang.OutOfMemoryError: Java heap space
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (GEODE-3504) User Guide: Add Experimental caveat for Redis and Auto-rebalance

2017-08-22 Thread Dave Barnes (JIRA)

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

Dave Barnes resolved GEODE-3504.

   Resolution: Fixed
Fix Version/s: 1.3.0

"Note: This feature is experimental and is subject to change in future releases 
of Apache Geode."

> User Guide: Add Experimental caveat for Redis and Auto-rebalance
> 
>
> Key: GEODE-3504
> URL: https://issues.apache.org/jira/browse/GEODE-3504
> Project: Geode
>  Issue Type: Improvement
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Minor
> Fix For: 1.3.0
>
>
> The Redis adapter and the Auto-rebalance feature are not fully-baked. Add a 
> caveat to their respective pages to alert the reader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3504) User Guide: Add Experimental caveat for Redis and Auto-rebalance

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3504:


Commit a1ac45dee947dd95c70200e7779275a03b492733 in geode's branch 
refs/heads/develop from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a1ac45d ]

GEODE-3504: Add Experimental caveat for Redis and Auto-rebalance


> User Guide: Add Experimental caveat for Redis and Auto-rebalance
> 
>
> Key: GEODE-3504
> URL: https://issues.apache.org/jira/browse/GEODE-3504
> Project: Geode
>  Issue Type: Improvement
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Minor
>
> The Redis adapter and the Auto-rebalance feature are not fully-baked. Add a 
> caveat to their respective pages to alert the reader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3395) Variable-ize product version and name in user guide

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3395:


Commit c0f6c841862c64a0b82594045320e82f558452ba in geode's branch 
refs/heads/develop from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c0f6c84 ]

GEODE-3395 Variable-ize product version and name in user guide - Topo & Comms, 
format repair


>  Variable-ize product version and name in user guide
> 
>
> Key: GEODE-3395
> URL: https://issues.apache.org/jira/browse/GEODE-3395
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>
> The Guide contains many occurrences of the product version string ("1.2", 
> "1.1", and "1.0-incubating" are recent examples) scattered over about 900 
> files.  It would be a great convenience to those who write and edit these 
> files to define the version number symbolically so it could be updated in one 
> central location. A template variable in the book's config.yml file would be 
> an obvious candidate for the implementation.
> Similarly, it would be handy to provide symbolic identifiers for the product 
> name, long and short: "Apache Geode" and "Geode", respectively.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3454) CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort fails intermittently waiting for server to be running

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3454:
-
Labels: DistributedTest Flaky deprecated  (was: )

> CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort fails 
> intermittently waiting for server to be running
> 
>
> Key: GEODE-3454
> URL: https://issues.apache.org/jira/browse/GEODE-3454
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Jared Stewart
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky, deprecated
>
> {noformat}
> java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ 
> status: running" after 12 ms. Output: 
> 2017-08-17 14:05:30,958 main INFO Log4j appears to be running in a Servlet 
> environment, but there's no log4j-web module available. If you want better 
> web container support, please add the log4j-web JAR to your web archive or 
> server lib directory.
> Starting CacheServer with pid: 0
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:222)
>   at 
> org.apache.geode.internal.cache.CacheServerLauncherDUnitTest.execAndValidate(CacheServerLauncherDUnitTest.java:501)
>   at 
> org.apache.geode.internal.cache.CacheServerLauncherDUnitTest.testWithoutServerPort(CacheServerLauncherDUnitTest.java:364)
>   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.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.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: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(ProxyDispatchAda

[jira] [Commented] (GEODE-2842) Remove unnecessary @CliOption arguments

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-2842:
---

GitHub user PurelyApplied opened a pull request:

https://github.com/apache/geode/pull/731

GEODE-2842: Removed redundant default annotation parameter values.

Driven by IntelliJ inspection, I have extended the reach of this ticket to 
include any annotation, not only `@CliOption`.





Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [x] Is your initial contribution a single, squashed commit?

- [x] Does `gradlew build` run cleanly?

- [n/a] Have you written or updated unit tests to verify your changes?

- [n/a] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to d...@geode.apache.org.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/PurelyApplied/geode geode-2842

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/geode/pull/731.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #731


commit 2f27ae65508935fcf3b4145f2412b450d65019f4
Author: Patrick Rhomberg 
Date:   2017-08-22T21:20:12Z

GEODE-2842: Removed redundant default annotation parameter values.




> Remove unnecessary @CliOption arguments
> ---
>
> Key: GEODE-2842
> URL: https://issues.apache.org/jira/browse/GEODE-2842
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> The {{@CliOption}} annotation specifies default values for some of its fields 
> (like {{mandatory}} and {{unspecifiedDefaultValue}}).  Yet, we often 
> explicitly set those fields to the default value.  For example,
> {noformat}  @CliOption(key = CliStrings.START_LOCATOR__MEMBER_NAME, 
> mandatory = false,
>   unspecifiedDefaultValue = CliMetaData.ANNOTATION_NULL_VALUE,
>   help = CliStrings.START_LOCATOR__MEMBER_NAME__HELP) String 
> memberName {noformat}
> could simply read   
> {noformat}  @CliOption(key = CliStrings.START_LOCATOR__MEMBER_NAME,
>   help = CliStrings.START_LOCATOR__MEMBER_NAME__HELP) String 
> memberName {noformat}
> Removing these redundant/unnecessary arguments will make the code a lot more 
> readable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (GEODE-3047) CI failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs (ConflictingPersistentDataException)

2017-08-22 Thread Anilkumar Gingade (JIRA)

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

Anilkumar Gingade resolved GEODE-3047.
--
   Resolution: Fixed
Fix Version/s: 1.3.0

> CI failure: 
> PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs 
> (ConflictingPersistentDataException)
> ---
>
> Key: GEODE-3047
> URL: https://issues.apache.org/jira/browse/GEODE-3047
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Lynn Gallinat
>Assignee: Anilkumar Gingade
> Fix For: 1.3.0
>
>
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest > 
> testClientMetadataForPersistentPrs FAILED
> 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 11823
> [error 2017/06/05 16:15:06.807 UTC  _B__CUSTOMER_0> tid=0xe9] A DiskAccessException has occurred while writing to 
> the disk for region /__PR/_B__SHIPMENT_0. The cache will be closed.
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: 
> Region /__PR/_B__SHIPMENT_0 refusing to initialize from member 
> 172.17.0.3(177):32773 with persistent data 
> /172.17.0.3:/tmp/gemfire-build/geode/geode-core/build/distributedTest305/dunit/vm1/diskDir/disk1
>  created at timestamp 1496679288068 version 0 diskStoreId 
> bd6add692799471a-af82daaafb9c36e8 name null which was offline when the local 
> data from 
> /172.17.0.3:/tmp/gemfire-build/geode/geode-core/build/distributedTest305/dunit/vm2/diskDir/disk2
>  created at timestamp 1496679291626 version 0 diskStoreId 
> 5a4a04c19efe4961-90fba2925786d398 name null was last online
>   at 
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:757)
>   at 
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:818)
>   at 
> org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1144)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1023)
>   at 
> org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:253)
>   at 
> org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:962)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:726)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:414)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucketRecursively(PartitionedRegionDataStore.java:272)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucketRecursively(PartitionedRegionDataStore.java:289)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2815)
>   at 
> org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:423)
>   at 
> org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:389)
>   at 
> org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1736)
>   at 
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:61)
>   at 
> org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.java:1728)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3047) CI failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs (ConflictingPersistentDataException)

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3047:


Commit 35d3a97edd5c6e8b3f4dd73af51771b0c4728cf6 in geode's branch 
refs/heads/develop from [~agingade]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=35d3a97 ]

GEODE-3047 Atomic creation flag is not set if the region is recoverd from the 
disk.

While creating bucket region, to satisfy the redudndancy copies the bucket 
regions
are created on all vailable nodes. The initialization (setting persistentIDs) of
these buckets are done after creating buckets on all the nodes. This introduced
a race condition for the bucket region which are recovered from the disk to
exchange thier old id with the peer node resulting in ConflictingPersistentData
Exception.

The changes are done so that the regions persistent ids are set as soon as they
are created/initialized.


> CI failure: 
> PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs 
> (ConflictingPersistentDataException)
> ---
>
> Key: GEODE-3047
> URL: https://issues.apache.org/jira/browse/GEODE-3047
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Lynn Gallinat
>Assignee: Anilkumar Gingade
>
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest > 
> testClientMetadataForPersistentPrs FAILED
> 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 11823
> [error 2017/06/05 16:15:06.807 UTC  _B__CUSTOMER_0> tid=0xe9] A DiskAccessException has occurred while writing to 
> the disk for region /__PR/_B__SHIPMENT_0. The cache will be closed.
> org.apache.geode.cache.persistence.ConflictingPersistentDataException: 
> Region /__PR/_B__SHIPMENT_0 refusing to initialize from member 
> 172.17.0.3(177):32773 with persistent data 
> /172.17.0.3:/tmp/gemfire-build/geode/geode-core/build/distributedTest305/dunit/vm1/diskDir/disk1
>  created at timestamp 1496679288068 version 0 diskStoreId 
> bd6add692799471a-af82daaafb9c36e8 name null which was offline when the local 
> data from 
> /172.17.0.3:/tmp/gemfire-build/geode/geode-core/build/distributedTest305/dunit/vm2/diskDir/disk2
>  created at timestamp 1496679291626 version 0 diskStoreId 
> 5a4a04c19efe4961-90fba2925786d398 name null was last online
>   at 
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:757)
>   at 
> org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:818)
>   at 
> org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1144)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1023)
>   at 
> org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:253)
>   at 
> org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:962)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:726)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:414)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucketRecursively(PartitionedRegionDataStore.java:272)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucketRecursively(PartitionedRegionDataStore.java:289)
>   at 
> org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2815)
>   at 
> org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:423)
>   at 
> org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:389)
>   at 
> org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1736)
>   at 
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:61)
>   at 
> org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.java:1728)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA

[jira] [Closed] (GEODE-3382) CI Failure: ClientHealthStatsDUnitTesttestClientHealthStats_SubscriptionDisabled

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund closed GEODE-3382.


> CI Failure: 
> ClientHealthStatsDUnitTesttestClientHealthStats_SubscriptionDisabled
> 
>
> Key: GEODE-3382
> URL: https://issues.apache.org/jira/browse/GEODE-3382
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.2.0
>Reporter: Kenneth Howe
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/422336689.run
>  in VM 0 running on Host cb1ab49db437 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:302)
>   at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
>   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.apache.geode.management.ManagementTestRule$2.evaluate(ManagementTestRule.java:86)
>   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$CatchAndR

[jira] [Resolved] (GEODE-3382) CI Failure: ClientHealthStatsDUnitTesttestClientHealthStats_SubscriptionDisabled

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-3382.
--
Resolution: Duplicate

> CI Failure: 
> ClientHealthStatsDUnitTesttestClientHealthStats_SubscriptionDisabled
> 
>
> Key: GEODE-3382
> URL: https://issues.apache.org/jira/browse/GEODE-3382
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.2.0
>Reporter: Kenneth Howe
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/422336689.run
>  in VM 0 running on Host cb1ab49db437 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:302)
>   at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
>   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.apache.geode.management.ManagementTestRule$2.evaluate(ManagementTestRule.java:86)
>   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.concu

[jira] [Assigned] (GEODE-3164) ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails intermittently with AssertionError

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-3164:


Assignee: Kirk Lund

> ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails 
> intermittently with AssertionError
> --
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3164) ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails intermittently with AssertionError

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3164:
-
Summary: 
ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails 
intermittently with AssertionError  (was: 
ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails 
with assert)

> ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled fails 
> intermittently with AssertionError
> --
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3164) ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails with assert

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3164:
-
Component/s: tests
 management

> ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails 
> with assert
> ---
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3164) ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails with assert

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3164:
-
Labels: DistributedTest Flaky  (was: )

> ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails 
> with assert
> ---
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3164) ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails with assert

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3164:
-
Description: 
{noformat}
org.apache.geode.management.ClientHealthStatsDUnitTest > 
testClientHealthStats_SubscriptionDisabled FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
 in VM 0 running on Host 57af4a2e6a1a 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:292)
at 
org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)

Caused by:
java.lang.AssertionError: 
Expected size:<2> but was:<1> in:
<["172.17.0.4(197:loner):57014:0e60d6fc"]>
at 
org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
at 
org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
{noformat}

  was:
org.apache.geode.management.ClientHealthStatsDUnitTest > 
testClientHealthStats_SubscriptionDisabled FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
 in VM 0 running on Host 57af4a2e6a1a 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:292)
at 
org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)

Caused by:
java.lang.AssertionError: 
Expected size:<2> but was:<1> in:
<["172.17.0.4(197:loner):57014:0e60d6fc"]>
at 
org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
at 
org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)


> ClientHealthStatsDUnitTest:testClientHealthStats_SubscriptionDisabled fails 
> with assert
> ---
>
> Key: GEODE-3164
> URL: https://issues.apache.org/jira/browse/GEODE-3164
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, management, tests
>Reporter: Hitesh Khamesra
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.management.ClientHealthStatsDUnitTest > 
> testClientHealthStats_SubscriptionDisabled FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.ClientHealthStatsDUnitTest$$Lambda$33/1335405829.run
>  in VM 0 running on Host 57af4a2e6a1a 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:292)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.testClientHealthStats_SubscriptionDisabled(ClientHealthStatsDUnitTest.java:136)
> Caused by:
> java.lang.AssertionError: 
> Expected size:<2> but was:<1> in:
> <["172.17.0.4(197:loner):57014:0e60d6fc"]>
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.verifyClientStats(ClientHealthStatsDUnitTest.java:314)
> at 
> org.apache.geode.management.ClientHealthStatsDUnitTest.lambda$testClientHealthStats_SubscriptionDisabled$1db6af62$1(ClientHealthStatsDUnitTest.java:136)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Closed] (GEODE-618) CI Failure: ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund closed GEODE-618.
---

> CI Failure: ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction
> -
>
> Key: GEODE-618
> URL: https://issues.apache.org/jira/browse/GEODE-618
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Jason Huynh
>Assignee: Kirk Lund
>  Labels: CI
> Fix For: 1.0.0-incubating.M1
>
>
> java.lang.NullPointerException
>   at 
> com.gemstone.gemfire.management.internal.cli.result.AbstractResultData.readFileDataAndDump(AbstractResultData.java:211)
>   at 
> com.gemstone.gemfire.management.internal.cli.result.CommandResult.saveIncomingFiles(CommandResult.java:563)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction(ShowDeadlockDUnitTest.java:142)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (GEODE-618) CI Failure: ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-618.
-

I'm going to file a new bug for this. I can't seem to remove the old Resolution.

> CI Failure: ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction
> -
>
> Key: GEODE-618
> URL: https://issues.apache.org/jira/browse/GEODE-618
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Jason Huynh
>Assignee: Kirk Lund
>  Labels: CI
> Fix For: 1.0.0-incubating.M1
>
>
> java.lang.NullPointerException
>   at 
> com.gemstone.gemfire.management.internal.cli.result.AbstractResultData.readFileDataAndDump(AbstractResultData.java:211)
>   at 
> com.gemstone.gemfire.management.internal.cli.result.CommandResult.saveIncomingFiles(CommandResult.java:563)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction(ShowDeadlockDUnitTest.java:142)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-618) CI Failure: ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-618:
---

Assignee: Kirk Lund

> CI Failure: ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction
> -
>
> Key: GEODE-618
> URL: https://issues.apache.org/jira/browse/GEODE-618
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Jason Huynh
>Assignee: Kirk Lund
>  Labels: CI
> Fix For: 1.0.0-incubating.M1
>
>
> java.lang.NullPointerException
>   at 
> com.gemstone.gemfire.management.internal.cli.result.AbstractResultData.readFileDataAndDump(AbstractResultData.java:211)
>   at 
> com.gemstone.gemfire.management.internal.cli.result.CommandResult.saveIncomingFiles(CommandResult.java:563)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction(ShowDeadlockDUnitTest.java:142)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3395) Variable-ize product version and name in user guide

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3395:


Commit e2c3d531f6bf7aeddb0ce38ab356ec415e32fb48 in geode's branch 
refs/heads/develop from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=e2c3d53 ]

GEODE-3395 Variable-ize product version and name in user guide - Topo & Comms


>  Variable-ize product version and name in user guide
> 
>
> Key: GEODE-3395
> URL: https://issues.apache.org/jira/browse/GEODE-3395
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>
> The Guide contains many occurrences of the product version string ("1.2", 
> "1.1", and "1.0-incubating" are recent examples) scattered over about 900 
> files.  It would be a great convenience to those who write and edit these 
> files to define the version number symbolically so it could be updated in one 
> central location. A template variable in the book's config.yml file would be 
> an obvious candidate for the implementation.
> Similarly, it would be handy to provide symbolic identifiers for the product 
> name, long and short: "Apache Geode" and "Geode", respectively.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3447:
---

Github user bschuchardt commented on a diff in the pull request:

https://github.com/apache/geode/pull/719#discussion_r134600589
  
--- Diff: 
geode-protobuf/src/main/java/org/apache/geode/protocol/protobuf/ProtobufSimpleAuthenticator.java
 ---
@@ -40,20 +42,28 @@ public void receiveMessage(InputStream inputStream, 
OutputStream outputStream,
 properties.setProperty("username", 
authenticationRequest.getUsername());
 properties.setProperty("password", 
authenticationRequest.getPassword());
 
+authorizer = null; // authenticating a new user clears current 
authorizer
 try {
   Object principal = securityManager.authenticate(properties);
-  authenticated = principal != null;
+  if (principal != null) {
+authorizer = new ProtobufSimpleAuthorizer(principal, 
securityManager);
+  }
 } catch (AuthenticationFailedException e) {
-  authenticated = false;
+  authorizer = null;
 }
 
-
AuthenticationAPI.SimpleAuthenticationResponse.newBuilder().setAuthenticated(authenticated)
+
AuthenticationAPI.SimpleAuthenticationResponse.newBuilder().setAuthenticated(isAuthenticated())
 .build().writeDelimitedTo(outputStream);
   }
 
   @Override
   public boolean isAuthenticated() {
-return authenticated;
+return authorizer != null;
--- End diff --

A authorizer IS only constructed BECAUSE something was authenticated.  
Therefore this is a valid implementation of isAuthenticated().


> Implement client authorization for the new protocol
> ---
>
> Key: GEODE-3447
> URL: https://issues.apache.org/jira/browse/GEODE-3447
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Bruce Schuchardt
>
> As a user of the new client/server protocol, I need to make sure the clients 
> using the protocol to access my grid are authorized to perform each operation 
> they attempt.
> Implement client authorization for operations in new protocol based on 
> existing authorization configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3447:
---

Github user bschuchardt commented on a diff in the pull request:

https://github.com/apache/geode/pull/719#discussion_r134600066
  
--- Diff: 
geode-protobuf/src/main/java/org/apache/geode/protocol/protobuf/ProtobufSimpleAuthenticator.java
 ---
@@ -40,20 +42,28 @@ public void receiveMessage(InputStream inputStream, 
OutputStream outputStream,
 properties.setProperty("username", 
authenticationRequest.getUsername());
 properties.setProperty("password", 
authenticationRequest.getPassword());
 
+authorizer = null; // authenticating a new user clears current 
authorizer
 try {
   Object principal = securityManager.authenticate(properties);
-  authenticated = principal != null;
+  if (principal != null) {
+authorizer = new ProtobufSimpleAuthorizer(principal, 
securityManager);
--- End diff --

The Principal is part of the implementation of this authentication & 
authorization algorithm and is encapsulated by this class.


> Implement client authorization for the new protocol
> ---
>
> Key: GEODE-3447
> URL: https://issues.apache.org/jira/browse/GEODE-3447
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Bruce Schuchardt
>
> As a user of the new client/server protocol, I need to make sure the clients 
> using the protocol to access my grid are authorized to perform each operation 
> they attempt.
> Implement client authorization for operations in new protocol based on 
> existing authorization configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3447:
---

Github user bschuchardt commented on a diff in the pull request:

https://github.com/apache/geode/pull/719#discussion_r134599066
  
--- Diff: 
geode-protobuf/src/main/java/org/apache/geode/protocol/protobuf/ProtobufSimpleAuthorizer.java
 ---
@@ -0,0 +1,42 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more 
contributor license
+ * agreements. See the NOTICE file distributed with this work for 
additional information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache 
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the 
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software 
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF 
ANY KIND, either express
+ * or implied. See the License for the specific language governing 
permissions and limitations under
+ * the License.
+ */
+package org.apache.geode.protocol.protobuf;
+
+import java.io.EOFException;
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.OutputStream;
+import java.util.Properties;
+
+import org.apache.geode.security.AuthenticationFailedException;
+import org.apache.geode.security.ResourcePermission;
+import org.apache.geode.security.SecurityManager;
+import org.apache.geode.security.StreamAuthenticator;
+import org.apache.geode.security.StreamAuthorizer;
+
+public class ProtobufSimpleAuthorizer implements StreamAuthorizer {
+  private final Object authenticatedPrincipal;
+  private final SecurityManager securityManager;
+
+  public ProtobufSimpleAuthorizer(Object authenticatedPrincipal, 
SecurityManager securityManager) {
+this.authenticatedPrincipal = authenticatedPrincipal;
+this.securityManager = securityManager;
+  }
+
+  @Override
+  public boolean authorize(ResourcePermission permissionRequested) {
--- End diff --

I'd rather not have other code deal with the Principal.  Other 
implementations may not have a Principal.  I.e., a no-op implementation.


> Implement client authorization for the new protocol
> ---
>
> Key: GEODE-3447
> URL: https://issues.apache.org/jira/browse/GEODE-3447
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Bruce Schuchardt
>
> As a user of the new client/server protocol, I need to make sure the clients 
> using the protocol to access my grid are authorized to perform each operation 
> they attempt.
> Implement client authorization for operations in new protocol based on 
> existing authorization configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3454) CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort fails intermittently waiting for server to be running

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund commented on GEODE-3454:
--

This is the dunit for the old, deprecated cacheserver script code that has been 
replaced by GFSH. I recommend refactoring all code that uses the ThreadLocals 
in this class (yikes) and then delete this test, the code and the cacheserver 
scripts (cacheserver and cacheserver.bat).

> CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort fails 
> intermittently waiting for server to be running
> 
>
> Key: GEODE-3454
> URL: https://issues.apache.org/jira/browse/GEODE-3454
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Jared Stewart
>Assignee: Kirk Lund
>
> {noformat}
> java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ 
> status: running" after 12 ms. Output: 
> 2017-08-17 14:05:30,958 main INFO Log4j appears to be running in a Servlet 
> environment, but there's no log4j-web module available. If you want better 
> web container support, please add the log4j-web JAR to your web archive or 
> server lib directory.
> Starting CacheServer with pid: 0
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:222)
>   at 
> org.apache.geode.internal.cache.CacheServerLauncherDUnitTest.execAndValidate(CacheServerLauncherDUnitTest.java:501)
>   at 
> org.apache.geode.internal.cache.CacheServerLauncherDUnitTest.testWithoutServerPort(CacheServerLauncherDUnitTest.java:364)
>   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.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.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: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)
>  

[jira] [Updated] (GEODE-3454) CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort fails intermittently waiting for server to be running

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3454:
-
Summary: CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort 
fails intermittently waiting for server to be running  (was: CI Failure: 
CacheServerLauncherDUnitTest.testWithoutServerPort)

> CI Failure: CacheServerLauncherDUnitTest.testWithoutServerPort fails 
> intermittently waiting for server to be running
> 
>
> Key: GEODE-3454
> URL: https://issues.apache.org/jira/browse/GEODE-3454
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Jared Stewart
>Assignee: Kirk Lund
>
> {noformat}
> java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ 
> status: running" after 12 ms. Output: 
> 2017-08-17 14:05:30,958 main INFO Log4j appears to be running in a Servlet 
> environment, but there's no log4j-web module available. If you want better 
> web container support, please add the log4j-web JAR to your web archive or 
> server lib directory.
> Starting CacheServer with pid: 0
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:222)
>   at 
> org.apache.geode.internal.cache.CacheServerLauncherDUnitTest.execAndValidate(CacheServerLauncherDUnitTest.java:501)
>   at 
> org.apache.geode.internal.cache.CacheServerLauncherDUnitTest.testWithoutServerPort(CacheServerLauncherDUnitTest.java:364)
>   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.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.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: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.

[jira] [Commented] (GEODE-3472) Code Cleanup: remove dead code from /management.

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3472:
---

Github user PurelyApplied commented on the issue:

https://github.com/apache/geode/pull/730
  
Precheckin green after merge with 
`be4551191a17b9f50169f375798785ab5373e975`.  Subsequently rebased again with 
minor merge conflict resolved.


> Code Cleanup: remove dead code from /management.
> 
>
> Key: GEODE-3472
> URL: https://issues.apache.org/jira/browse/GEODE-3472
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>
> There is a great deal of dead, commented, and unused code in the codebase.  
> This ticket addresses some of it, limiting scope to those files in 
> `geode-core/**/management/**` to keep the eventual diff relatively small.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-3335:


Assignee: Kirk Lund  (was: Kenneth Howe)

> CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails 
> intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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.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:

[jira] [Updated] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3335:
-
Summary: CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails 
intermittently with ConditionTimeoutException  (was: CI Failure : 
RegionManagementDUnitTest.testNavigationAPIS)

> CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails 
> intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kenneth Howe
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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.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.NativeMethodAccessor

[jira] [Updated] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails intermittently with ConditionTimeoutException

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3335:
-
Fix Version/s: (was: 1.3.0)

> CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails 
> intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kirk Lund
>  Labels: DistributedTest, Flaky
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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.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 j

[jira] [Commented] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund commented on GEODE-3335:
--

See GEODE-1930: JMX DistributedTests are in need of overhauling. This is one of 
those tests and it's the one which was next on the list to overhaul.

> CI Failure : RegionManagementDUnitTest.testNavigationAPIS
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kenneth Howe
>  Labels: DistributedTest, Flaky
> Fix For: 1.3.0
>
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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.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 
>

[jira] [Commented] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund commented on GEODE-3335:
--

This test continue to fail with intermittently with a ConditionTimeoutException:
{noformat}
org.apache.geode.management.RegionManagementDUnitTest > testNavigationAPIS 
FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
8fa434e550e8 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
at 
org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
at 
org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)

Caused by:
org.awaitility.core.ConditionTimeoutException: Condition defined as a 
lambda expression in org.apache.geode.management.RegionManagementDUnitTest that 
uses org.apache.geode.management.DistributedSystemMXBean, 
org.apache.geode.management.DistributedSystemMXBeanint expected:<[4]> but 
was:<[5]> within 2 minutes.
at 
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
at 
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
at 
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
at 
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
at 
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
at 
org.apache.geode.management.RegionManagementDUnitTest.awaitMemberCount(RegionManagementDUnitTest.java:1062)
at 
org.apache.geode.management.RegionManagementDUnitTest.lambda$verifyNavigationApis$8ec4a763$1(RegionManagementDUnitTest.java:423)
{noformat}

> CI Failure : RegionManagementDUnitTest.testNavigationAPIS
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kenneth Howe
>  Labels: DistributedTest, Flaky
> Fix For: 1.3.0
>
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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

[jira] [Updated] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS

2017-08-22 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-3335:
-
Labels: DistributedTest Flaky  (was: )

> CI Failure : RegionManagementDUnitTest.testNavigationAPIS
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: nabarun
>Assignee: Kenneth Howe
>  Labels: DistributedTest, Flaky
> Fix For: 1.3.0
>
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host 
> 96fffb6d85d3 with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
>   at 
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
>   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.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.

[jira] [Resolved] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread Hitesh Khamesra (JIRA)

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

Hitesh Khamesra resolved GEODE-3406.

Resolution: Fixed

> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Hitesh Khamesra
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread Hitesh Khamesra (JIRA)

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

Hitesh Khamesra reassigned GEODE-3406:
--

Assignee: Hitesh Khamesra  (was: Alexander Murmann)

> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Hitesh Khamesra
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3445) Add Gfsh Connect option --skip-ssl-validation

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3445:


Commit b77e1c7d1e1dc31a539496483c8e9f739155f021 in geode's branch 
refs/heads/develop from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b77e1c7 ]

GEODE-3445: Add gfsh connect option --skip-ssl-validation


> Add Gfsh Connect option --skip-ssl-validation
> -
>
> Key: GEODE-3445
> URL: https://issues.apache.org/jira/browse/GEODE-3445
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> We have users who would like to connect to a locator from gfsh over HTTPS 
> without verifying the hostname of the locator.  (This is a common pattern in 
> testing environments or where self-signed certificates are used.)  We already 
> have some code used for tests to enable this behavior:
> {noformat}
>// This is for testing purpose only. If we remove this piece of code we 
> will
> // get a java.security.cert.CertificateException
> // as matching hostname can not be obtained in all test environment.
> HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier() {
>   @Override
>   public boolean verify(String string, SSLSession ssls) {
> return true;
>   }
> });
> {noformat}
> We just need to conditionally call this code inside Gfsh Connect if the 
> --skip-ssl-validation option is specified.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit 0eb320fad2071c0ebb8cb1e74576ed4a231a9e3b in geode's branch 
refs/heads/develop from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0eb320f ]

GEODE-3406: Address PR feedback

* Rename ExecutionContext -> MessageExecutionContext
* Properly close socket when processing ProtoBuf request in TcpServer
* GetAvailableServersRequestHandler guards against `null` servers
* minor style changes

Signed-off-by: Alexander Murmann 


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit 0cc60434cd75814e755b88be39af53b32d53faeb in geode's branch 
refs/heads/develop from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0cc6043 ]

GEODE-3406: Address more PR feedback

Signed-off-by: Alexander Murmann 


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3400) GetAvailableServers on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3400:


Commit 530f48f35a96c4f8af7e51ed03b1ee2e5e150ebd in geode's branch 
refs/heads/develop from [~amurmann]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=530f48f ]

GEODE-3406: Locator accepts Protobuf requests

Also addresses GEODE-3400, GEODE-3399
This allows the locator to respond to Protobuf requests. Currently it
will only be able to respond to getAvailableServers.

To enable this we are introducing a new value of "0" that will be sent
in place of the Gossip version. After it we expect the same magic byte
("110") as in AcceptorImpl.

This also is gated by the `geode.feature-protobuf-protocol` system
property.

The getAvailableServers request handler now uses the locator directly,
since we are on the locator.

Signed-off-by: Brian Rowe 


> GetAvailableServers on locators
> ---
>
> Key: GEODE-3400
> URL: https://issues.apache.org/jira/browse/GEODE-3400
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Implement GetAvailableServers message on locators. Remove existing 
> implementation from server.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit a4fc1ddf628766cd5f3e7fb9e9469f523d20dbf2 in geode's branch 
refs/heads/develop from [~amurmann]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a4fc1dd ]

GEODE-3406: Exclude new exception class from analyze serialiable test

Signed-off-by: Hitesh Khamesra 


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit 530f48f35a96c4f8af7e51ed03b1ee2e5e150ebd in geode's branch 
refs/heads/develop from [~amurmann]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=530f48f ]

GEODE-3406: Locator accepts Protobuf requests

Also addresses GEODE-3400, GEODE-3399
This allows the locator to respond to Protobuf requests. Currently it
will only be able to respond to getAvailableServers.

To enable this we are introducing a new value of "0" that will be sent
in place of the Gossip version. After it we expect the same magic byte
("110") as in AcceptorImpl.

This also is gated by the `geode.feature-protobuf-protocol` system
property.

The getAvailableServers request handler now uses the locator directly,
since we are on the locator.

Signed-off-by: Brian Rowe 


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3399) Enable protocol feature toggle on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3399:


Commit 530f48f35a96c4f8af7e51ed03b1ee2e5e150ebd in geode's branch 
refs/heads/develop from [~amurmann]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=530f48f ]

GEODE-3406: Locator accepts Protobuf requests

Also addresses GEODE-3400, GEODE-3399
This allows the locator to respond to Protobuf requests. Currently it
will only be able to respond to getAvailableServers.

To enable this we are introducing a new value of "0" that will be sent
in place of the Gossip version. After it we expect the same magic byte
("110") as in AcceptorImpl.

This also is gated by the `geode.feature-protobuf-protocol` system
property.

The getAvailableServers request handler now uses the locator directly,
since we are on the locator.

Signed-off-by: Brian Rowe 


> Enable protocol feature toggle on locators
> --
>
> Key: GEODE-3399
> URL: https://issues.apache.org/jira/browse/GEODE-3399
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server, docs
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Enable protocol feature toggle on locators.  This is the first step toward 
> locators talking new protocol.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3406) Enable new flow for protocol on locators

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3406:


Commit 31e82d6d64187ba7a6d71771806a0b107a811c11 in geode's branch 
refs/heads/develop from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=31e82d6 ]

GEODE-3406: Fixed test failures.

Now TcpServerFactory doesn't look for protobuf enabled property.
If service is not available then it just ignores that


> Enable new flow for protocol on locators
> 
>
> Key: GEODE-3406
> URL: https://issues.apache.org/jira/browse/GEODE-3406
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Alexander Murmann
>
> Enable magic byte and new flow for new protocol on locators.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3504) User Guide: Add Experimental caveat for Redis and Auto-rebalance

2017-08-22 Thread Dave Barnes (JIRA)

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

Dave Barnes updated GEODE-3504:
---
Priority: Minor  (was: Major)

> User Guide: Add Experimental caveat for Redis and Auto-rebalance
> 
>
> Key: GEODE-3504
> URL: https://issues.apache.org/jira/browse/GEODE-3504
> Project: Geode
>  Issue Type: Improvement
>Reporter: Dave Barnes
>Priority: Minor
>
> The Redis adapter and the Auto-rebalance feature are not fully-baked. Add a 
> caveat to their respective pages to alert the reader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3504) User Guide: Add Experimental caveat for Redis and Auto-rebalance

2017-08-22 Thread Dave Barnes (JIRA)

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

Dave Barnes reassigned GEODE-3504:
--

Assignee: Dave Barnes

> User Guide: Add Experimental caveat for Redis and Auto-rebalance
> 
>
> Key: GEODE-3504
> URL: https://issues.apache.org/jira/browse/GEODE-3504
> Project: Geode
>  Issue Type: Improvement
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Minor
>
> The Redis adapter and the Auto-rebalance feature are not fully-baked. Add a 
> caveat to their respective pages to alert the reader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (GEODE-3504) User Guide: Add Experimental caveat for Redis and Auto-rebalance

2017-08-22 Thread Dave Barnes (JIRA)
Dave Barnes created GEODE-3504:
--

 Summary: User Guide: Add Experimental caveat for Redis and 
Auto-rebalance
 Key: GEODE-3504
 URL: https://issues.apache.org/jira/browse/GEODE-3504
 Project: Geode
  Issue Type: Improvement
Reporter: Dave Barnes


The Redis adapter and the Auto-rebalance feature are not fully-baked. Add a 
caveat to their respective pages to alert the reader.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3007) Simplify support for custom GFSH commands

2017-08-22 Thread Jared Stewart (JIRA)

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

Jared Stewart updated GEODE-3007:
-
Fix Version/s: 1.3.0

> Simplify support for custom GFSH commands
> -
>
> Key: GEODE-3007
> URL: https://issues.apache.org/jira/browse/GEODE-3007
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
> Fix For: 1.3.0
>
>
> Geode currently supports three ways to load GFSH commands: 
> 1. Scan the classpath for commands in 
> "org.apache.geode.management.internal.cli.commands”
> 2. Scan the classpath for commands in a package specified by a user via the 
> “user-command-packages” system property. 
> 3. Scan the classpath for commands registered in files inside 
> META-INF.services (e.g. 
> "geode-core/src/test/resources/META-INF/services/org.springframework.shell.core.CommandMarker”)
>  
> After the improvements made by GEODE-2989, there is no reason to require a 
> user to specify the location of their custom commands via one of these 
> mechanisms.  Instead, we should simply scan the entire classpath for any 
> classes implementing CommandMarker (regardless of whatever packages they live 
> in).  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3503) Remove Codec classes for Protobuf encoded primitives

2017-08-22 Thread Udo Kohlmeyer (JIRA)

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

Udo Kohlmeyer reassigned GEODE-3503:


Assignee: Udo Kohlmeyer

> Remove Codec classes for Protobuf encoded primitives
> 
>
> Key: GEODE-3503
> URL: https://issues.apache.org/jira/browse/GEODE-3503
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>
> As per the initial implementation, the client protocol would encode all 
> primitives using specified codecs. To improve on this, all primitives are now 
> encoded using protobuf and the codec classes are not required anymore and can 
> be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Resolved] (GEODE-3386) Create Error type for KeyedErrorResponse and ErrorResponse

2017-08-22 Thread Udo Kohlmeyer (JIRA)

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

Udo Kohlmeyer resolved GEODE-3386.
--
Resolution: Fixed

> Create Error type for KeyedErrorResponse and ErrorResponse
> --
>
> Key: GEODE-3386
> URL: https://issues.apache.org/jira/browse/GEODE-3386
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Alexander Murmann
> Fix For: 1.3.0
>
>
> For logical separation of the new client API, it will be better to have an 
> Error that is contained by ErrorResponse, rather than having 
> KeyedErrorResponse contain an ErrorResponse.
> In pseudo-protobuf,
> {code}
> PutAllResponse {
>   repeated Entry successes = 1,
>   repeated KeyedErrorResponse errors = 2,
> }
> KeyedErrorResponse {
>   Key,
>   ErrorResponse
> }
> ErrorResponse {
>   string
> }
> {code}
> instead,
> {code}
> KeyedErrorResponse {
>   Key,
>   Error,
> }
> {code}
> and 
> {code}
> ErrorResponse {
> Error
> }
> Error {
> string
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (GEODE-3386) Create Error type for KeyedErrorResponse and ErrorResponse

2017-08-22 Thread Udo Kohlmeyer (JIRA)

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

Udo Kohlmeyer updated GEODE-3386:
-
Fix Version/s: 1.3.0

> Create Error type for KeyedErrorResponse and ErrorResponse
> --
>
> Key: GEODE-3386
> URL: https://issues.apache.org/jira/browse/GEODE-3386
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Alexander Murmann
> Fix For: 1.3.0
>
>
> For logical separation of the new client API, it will be better to have an 
> Error that is contained by ErrorResponse, rather than having 
> KeyedErrorResponse contain an ErrorResponse.
> In pseudo-protobuf,
> {code}
> PutAllResponse {
>   repeated Entry successes = 1,
>   repeated KeyedErrorResponse errors = 2,
> }
> KeyedErrorResponse {
>   Key,
>   ErrorResponse
> }
> ErrorResponse {
>   string
> }
> {code}
> instead,
> {code}
> KeyedErrorResponse {
>   Key,
>   Error,
> }
> {code}
> and 
> {code}
> ErrorResponse {
> Error
> }
> Error {
> string
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3386) Create Error type for KeyedErrorResponse and ErrorResponse

2017-08-22 Thread Udo Kohlmeyer (JIRA)

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

Udo Kohlmeyer reassigned GEODE-3386:


Assignee: Alexander Murmann

> Create Error type for KeyedErrorResponse and ErrorResponse
> --
>
> Key: GEODE-3386
> URL: https://issues.apache.org/jira/browse/GEODE-3386
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Alexander Murmann
> Fix For: 1.3.0
>
>
> For logical separation of the new client API, it will be better to have an 
> Error that is contained by ErrorResponse, rather than having 
> KeyedErrorResponse contain an ErrorResponse.
> In pseudo-protobuf,
> {code}
> PutAllResponse {
>   repeated Entry successes = 1,
>   repeated KeyedErrorResponse errors = 2,
> }
> KeyedErrorResponse {
>   Key,
>   ErrorResponse
> }
> ErrorResponse {
>   string
> }
> {code}
> instead,
> {code}
> KeyedErrorResponse {
>   Key,
>   Error,
> }
> {code}
> and 
> {code}
> ErrorResponse {
> Error
> }
> Error {
> string
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-3385) Change GetAllRequest to return list of errors

2017-08-22 Thread Udo Kohlmeyer (JIRA)

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

Udo Kohlmeyer reassigned GEODE-3385:


Assignee: Udo Kohlmeyer

> Change GetAllRequest to return list of errors
> -
>
> Key: GEODE-3385
> URL: https://issues.apache.org/jira/browse/GEODE-3385
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Udo Kohlmeyer
>
> GetAllRequest currently returns a list of successful keys or an error (if 
> getting any key threw an exception). We should instead return a list of 
> errors, similar to PutAllRequest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Assigned] (GEODE-2997) New flow: putAll/getAll

2017-08-22 Thread Udo Kohlmeyer (JIRA)

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

Udo Kohlmeyer reassigned GEODE-2997:


Assignee: Udo Kohlmeyer

> New flow: putAll/getAll
> ---
>
> Key: GEODE-2997
> URL: https://issues.apache.org/jira/browse/GEODE-2997
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Udo Kohlmeyer
>
> Create proto message definitions and op handler for putAll/getAll messages.
> Client should be able to complete putAll/getAll of primitives and JSON with 
> response.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (GEODE-3503) Remove Codec classes for Protobuf encoded primitives

2017-08-22 Thread Udo Kohlmeyer (JIRA)
Udo Kohlmeyer created GEODE-3503:


 Summary: Remove Codec classes for Protobuf encoded primitives
 Key: GEODE-3503
 URL: https://issues.apache.org/jira/browse/GEODE-3503
 Project: Geode
  Issue Type: Sub-task
  Components: client/server
Reporter: Udo Kohlmeyer


As per the initial implementation, the client protocol would encode all 
primitives using specified codecs. To improve on this, all primitives are now 
encoded using protobuf and the codec classes are not required anymore and can 
be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3416) Reduce blocking for SocketCloser.asyncClose

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3416:


Commit be4551191a17b9f50169f375798785ab5373e975 in geode's branch 
refs/heads/develop from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=be45511 ]

GEODE-3416: Reduce synchronization blockages in SocketCloser. This now closes 
#702
Remove synchronization blocks around HashMap. Replace that implementation
with simpler ThreadPool that is not unbounded and does not grow as the
number of remoteAddress (clients/peers) are added


> Reduce blocking for SocketCloser.asyncClose 
> 
>
> Key: GEODE-3416
> URL: https://issues.apache.org/jira/browse/GEODE-3416
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.2.1
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
> Fix For: 1.3.0
>
>
> In the SocketCloser.asyncClose method, there is a synchronization block 
> around at HashMap. This synchronization will cause an effective 
> single-threaded processing capability when closing sockets. this effect 
> becomes more evident with a high number of clients.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3306) Parsing of cache.xml with whitespace fails with Apache Xerces

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3306:
---

Github user asfgit closed the pull request at:

https://github.com/apache/geode/pull/668


> Parsing of cache.xml with whitespace fails with Apache Xerces
> -
>
> Key: GEODE-3306
> URL: https://issues.apache.org/jira/browse/GEODE-3306
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.2.0
>Reporter: Darren Foong
>Priority: Minor
> Fix For: 1.2.0
>
>
> I am using Geode 1.2.0 and Apache Xerces 2.11.0 (not the one included in the 
> Oracle JDK), and I encountered the following error when I tried to 
> programmatically start a cache:
> {noformat}
> org.apache.geode.InternalGemFireError: Did not expected a 
> java.lang.StringBuffer on top of the stack.
> Exception in thread "main" org.apache.geode.InternalGemFireError: Did not 
> expected a java.lang.StringBuffer on top of the stack.
>   at org.apache.geode.internal.Assert.throwError(Assert.java:94)
>   at org.apache.geode.internal.Assert.assertTrue(Assert.java:117)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.endRegionAttributes(CacheXmlParser.java:1257)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.endElement(CacheXmlParser.java:2909)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser$DefaultHandlerDelegate.endElement(CacheXmlParser.java:3374)
>   at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
> Source)
>   at 
> org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown 
> Source)
>   at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown 
> Source)
>   at 
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown 
> Source)
>   at 
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>  Source)
>   at 
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
> Source)
>   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>   at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
> Source)
>   at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>   at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.parse(CacheXmlParser.java:224)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4287)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1390)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1195)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:758)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:745)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:173)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:212)
>   at server.ServerWhitespace.main(ServerWhitespace.java:8)
> {noformat}
> However, this does not happen when I don't use Apache Xerces, i.e. I rely on 
> the version in the Oracle JDK (1.8).
> After getting the Geode source code and stepping through the parsing using 
> the Eclipse debugger, I realised that there were unexpected StringBuffers 
> pushed onto the parse stack, thus causing the problem.
> These StringBuffers were created and pushed by the {{characters()}} method 
> (https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/xmlcache/CacheXmlParser.java#L3270).
>  Changing the log level to {{TRACE}} and examining the parse stack showed 
> that these StringBuffers contained the whitespace (including newlines) 
> between the XML tags in {{cache.xml}}.
> When using the Oracle JDK's version of Xerces, these StringBuffers did not 
> appear on the parse stack despite the whitespace.
> I have a proof of concept on GitHub: 
> https://github.com/darrenfoong/geode-parser-poc The {{cache.xml}} file 
> without whitespace between the tags was parsed without errors by both 
> versions of Xerces.
> It could be the case that the JDK Xerces strips out whitespace while Apache 
> Xerces doesn't; but this could be implemented in {{characters()}} by only 
> pushing non-whitespace char arrays in the {{else}}

[jira] [Commented] (GEODE-3416) Reduce blocking for SocketCloser.asyncClose

2017-08-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-3416:
---

Github user asfgit closed the pull request at:

https://github.com/apache/geode/pull/702


> Reduce blocking for SocketCloser.asyncClose 
> 
>
> Key: GEODE-3416
> URL: https://issues.apache.org/jira/browse/GEODE-3416
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.2.1
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
> Fix For: 1.3.0
>
>
> In the SocketCloser.asyncClose method, there is a synchronization block 
> around at HashMap. This synchronization will cause an effective 
> single-threaded processing capability when closing sockets. this effect 
> becomes more evident with a high number of clients.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3306) Parsing of cache.xml with whitespace fails with Apache Xerces

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3306:


Commit f2891791bf8b84856ef398b63829913439c5c123 in geode's branch 
refs/heads/develop from [~darrenfoong]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f289179 ]

GEODE-3306: Remove whitespace StringBuffers/nodes created by Apache Xerces

This commit makes Geode compatible with the official Apache Xerces
implementation, which calls `characters()` when it reads ignorable
whitespace in `cache.xml`.

The while loop is required to handle comments in `cache.xml`, i.e.
a comment with whitespace before and after will generate two
empty StringBuffers (one for each set of whitespace before and after)
on the parse stack. The while loop removes all "consecutive" whitespace
StringBuffers from the top of the stack.

(This closes #668.)


> Parsing of cache.xml with whitespace fails with Apache Xerces
> -
>
> Key: GEODE-3306
> URL: https://issues.apache.org/jira/browse/GEODE-3306
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.2.0
>Reporter: Darren Foong
>Priority: Minor
> Fix For: 1.2.0
>
>
> I am using Geode 1.2.0 and Apache Xerces 2.11.0 (not the one included in the 
> Oracle JDK), and I encountered the following error when I tried to 
> programmatically start a cache:
> {noformat}
> org.apache.geode.InternalGemFireError: Did not expected a 
> java.lang.StringBuffer on top of the stack.
> Exception in thread "main" org.apache.geode.InternalGemFireError: Did not 
> expected a java.lang.StringBuffer on top of the stack.
>   at org.apache.geode.internal.Assert.throwError(Assert.java:94)
>   at org.apache.geode.internal.Assert.assertTrue(Assert.java:117)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.endRegionAttributes(CacheXmlParser.java:1257)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.endElement(CacheXmlParser.java:2909)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser$DefaultHandlerDelegate.endElement(CacheXmlParser.java:3374)
>   at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
> Source)
>   at 
> org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown 
> Source)
>   at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown 
> Source)
>   at 
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown 
> Source)
>   at 
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>  Source)
>   at 
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
> Source)
>   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>   at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>   at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>   at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>   at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
> Source)
>   at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>   at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
>   at 
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.parse(CacheXmlParser.java:224)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4287)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1390)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1195)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:758)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:745)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:173)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:212)
>   at server.ServerWhitespace.main(ServerWhitespace.java:8)
> {noformat}
> However, this does not happen when I don't use Apache Xerces, i.e. I rely on 
> the version in the Oracle JDK (1.8).
> After getting the Geode source code and stepping through the parsing using 
> the Eclipse debugger, I realised that there were unexpected StringBuffers 
> pushed onto the parse stack, thus causing the problem.
> These StringBuffers were created and pushed by the {{characters()}} method 
> (https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/xmlcache/CacheXmlParser.java#L3270).
>  Changing the log level to {{TRACE}} and examining th

[jira] [Commented] (GEODE-3474) ProtobufSimpleAuthenticator is incompatible with ExampleSecurityManager

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3474:


Commit 5863fd5aa36a95676b45eb8e6ab88621ecdd58b6 in geode's branch 
refs/heads/feature/GEODE-3416 from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5863fd5 ]

GEODE-3474: Fixed failing tests


> ProtobufSimpleAuthenticator is incompatible with ExampleSecurityManager
> ---
>
> Key: GEODE-3474
> URL: https://issues.apache.org/jira/browse/GEODE-3474
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
> Fix For: 1.3.0
>
>
> {{ProtobufSimpleAuthenticator}} uses the property names "username" and 
> password" to provide credentials, but {{ExampleSecurityManager}} uses 
> "security-username" and "security-password". These are defined as 
> {{ResourceConstants.USER_NAME}} and  {{ResourceConstants.PASSWORD}} and 
> therefore probably the correct values to use.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3416) Reduce blocking for SocketCloser.asyncClose

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3416:


Commit 26dcf43647117c1729cc7a7f010de2774785c183 in geode's branch 
refs/heads/feature/GEODE-3416 from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=26dcf43 ]

GEODE-3416: Reduce synchronization blockages in SocketCloser.
Remove synchronization blocks around HashMap. Replace that implementation
with simpler ThreadPool that is not unbounded and does not grow as the
number of remoteAddress (clients/peers) are added


> Reduce blocking for SocketCloser.asyncClose 
> 
>
> Key: GEODE-3416
> URL: https://issues.apache.org/jira/browse/GEODE-3416
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.2.1
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
> Fix For: 1.3.0
>
>
> In the SocketCloser.asyncClose method, there is a synchronization block 
> around at HashMap. This synchronization will cause an effective 
> single-threaded processing capability when closing sockets. this effect 
> becomes more evident with a high number of clients.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-3430) ConnectCommandTest generates non-varargs compilation warnings

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-3430:


Commit c4def6bbb3d8c438cdc8d4b6d31e3e3875f6ab2b in geode's branch 
refs/heads/feature/GEODE-3416 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c4def6b ]

GEODE-3430: fix varargs usage

Also, general cleanup of ConnectCommandTest.

This closes #727


> ConnectCommandTest generates non-varargs compilation warnings
> -
>
> Key: GEODE-3430
> URL: https://issues.apache.org/jira/browse/GEODE-3430
> Project: Geode
>  Issue Type: Bug
>  Components: build, gfsh, tests
>Affects Versions: 1.3.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
> Fix For: 1.3.0
>
>
> {noformat}
> :geode-core:compileTestJava
> /Users/klund/dev/gemfire/open/geode-core/src/test/java/org/apache/geode/management/internal/cli/commands/ConnectCommandTest.java:277:
>  warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
> assertThat(connectCommand.isSslImpliedBySslOptions(null)).isFalse();
>^
>   cast to String for a varargs call
>   cast to String[] for a non-varargs call and to suppress this warning
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (GEODE-1279) Tests for old TRAC bugs should be renamed to useful names

2017-08-22 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-1279:


Commit 2924ef1d0e70a1d67fc4b32dd922fcb0571a4a92 in geode's branch 
refs/heads/feature/GEODE-3416 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=2924ef1 ]

GEODE-1279: rename tests with old bug system numbers

* Bug34387DUnitTest -> CreateAndLocalDestroyInTXRegressionTest
* Bug35214DUnitTest -> EntriesDoNotExpireDuringGIIRegressionTest
* Bug38013DUnitTest -> RemotePRValuesAreNotDeserializedRegressionTest
* Bug34948DUnitTest -> ValuesAreLazilyDeserializedRegressionTest

* cleanup setUp and tearDown in dunit framework


> Tests for old TRAC bugs should be renamed to useful names
> -
>
> Key: GEODE-1279
> URL: https://issues.apache.org/jira/browse/GEODE-1279
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Examples:
> * Bug52289JUnitTest -> FinalStaticArrayShouldNotCauseSegFaultTest
> * Bug36619JUnitTest -> MembershipAttributesAreSerializableTest
> * Bug34387DUnitTest -> CreateAndLocalDestroyInTXRegressionTest
> * Bug35214DUnitTest -> EntriesDoNotExpireDuringGIIRegressionTest
> * Bug38013DUnitTest -> RemotePRValuesAreNotDeserializedRegressionTest
> * Bug34948DUnitTest -> ValuesAreLazilyDeserializedRegressionTest
> Remaining:
> * 
> geode-core/src/test/java/org/apache/geode/cache/query/Bug32947ValueConstraintJUnitTest.java
> * geode-core/src/test/java/org/apache/geode/cache/query/BugJUnitTest.java
> * geode-core/src/test/java/org/apache/geode/cache30/Bug38741DUnitTest.java
> * geode-core/src/test/java/org/apache/geode/cache30/Bug40255JUnitTest.java
> * geode-core/src/test/java/org/apache/geode/cache30/Bug40662JUnitTest.java
> * geode-core/src/test/java/org/apache/geode/cache30/Bug44418JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/distributed/internal/Bug40751DUnitTest.java
> * geode-core/src/test/java/org/apache/geode/internal/Bug49856JUnitTest.java
> * geode-core/src/test/java/org/apache/geode/internal/Bug51616JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug33359DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug33726DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug33726JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug34179TooManyFilesOpenJUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug34583JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug37241DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug37244JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug37377DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug37500JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug39079DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug40299DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug40632DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug41091DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug41733DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug41957DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug42055DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug45164DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug45934DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug47667DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/Bug48182JUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/ha/Bug36853EventsExpiryDUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/ha/Bug48571DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/ha/Bug48879DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug39356DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug43684DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug47388DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/Bug51400DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/tier/Bug40396DUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/internal/cache/tier/soc

  1   2   >