[jira] [Commented] (GEODE-7541) Break dependency on SocketCreator/Factory & SecurableCommunicationChannel

2019-12-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7541:


Commit c2af830d244229aa73af3b70394ab0921ac2caa7 in geode's branch 
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c2af830 ]

GEODE-7541: revert one change (#4526)

One of the changes for this ticket is causing unit test failures on
some machines - especially Macs - in the form of

java.lang.RuntimeException: Failed to start locator
  Caused by:
  org.apache.geode.GemFireConfigException: This process is attempting to 
join with a loopback address (gzhou-mbpro/127.0.0.1) using a locator that does 
not have a local address (/10.255.200.197:60167). On Unix this usually means 
that /etc/hosts is misconfigured.

> Break dependency on SocketCreator/Factory & SecurableCommunicationChannel
> -
>
> Key: GEODE-7541
> URL: https://issues.apache.org/jira/browse/GEODE-7541
> Project: Geode
>  Issue Type: Sub-task
>  Components: membership
>Reporter: Ernest Burghardt
>Priority: Major
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> SocketCreator & SocketCreatorFactory.
> {color:#a8c023}which should also allow for break dependency on 
> internal.security{color}SecurableCommunicationChannel
>  
> Also look at usage of
> {code:java}
> OSProcess {code}
> in JGroupsMessenger
> {code:java}
> SocketCreator.resolve_dns ? 
> SocketCreator.getHostName(jgAddress.getInetAddress())
>  : jgAddress.getInetAddress().getHostAddress();
> GMSMemberData gmsMember = new GMSMemberData(jgAddress.getInetAddress(),
>  hostname, jgAddress.getPort(),
>  OSProcess.getId(),{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7541) Break dependency on SocketCreator/Factory & SecurableCommunicationChannel

2019-12-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7541:


Commit 1ab69cda2a7440d64c9edae4507b1a1304a1c2ec in geode's branch 
refs/heads/feature/GEODE-7541b from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ab69cd ]

GEODE-7541: revert one change

One of the changes for this ticket is causing unit test failures on
some machines - especially Macs - in the form of

java.lang.RuntimeException: Failed to start locator
  Caused by:
  org.apache.geode.GemFireConfigException: This process is attempting to 
join with a loopback address (gzhou-mbpro/127.0.0.1) using a locator that does 
not have a local address (/10.255.200.197:60167). On Unix this usually means 
that /etc/hosts is misconfigured.


> Break dependency on SocketCreator/Factory & SecurableCommunicationChannel
> -
>
> Key: GEODE-7541
> URL: https://issues.apache.org/jira/browse/GEODE-7541
> Project: Geode
>  Issue Type: Sub-task
>  Components: membership
>Reporter: Ernest Burghardt
>Priority: Major
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> SocketCreator & SocketCreatorFactory.
> {color:#a8c023}which should also allow for break dependency on 
> internal.security{color}SecurableCommunicationChannel
>  
> Also look at usage of
> {code:java}
> OSProcess {code}
> in JGroupsMessenger
> {code:java}
> SocketCreator.resolve_dns ? 
> SocketCreator.getHostName(jgAddress.getInetAddress())
>  : jgAddress.getInetAddress().getHostAddress();
> GMSMemberData gmsMember = new GMSMemberData(jgAddress.getInetAddress(),
>  hostname, jgAddress.getPort(),
>  OSProcess.getId(),{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7612) Move statistics and logging implementation into .cpp files

2019-12-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7612:


Commit cbe6415a439ddc8685715f24dd221e3df1323cc6 in geode-native's branch 
refs/heads/develop from Matthew Reddington
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=cbe6415 ]

GEODE-7612: Fix test breakage

Removed broken debug exclusion that never worked anyway


> Move statistics and logging implementation into .cpp files
> --
>
> Key: GEODE-7612
> URL: https://issues.apache.org/jira/browse/GEODE-7612
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Priority: Major
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> As a developer, I would like to minimize the time spent recompiling code that 
> I haven't modified.  One important way to improve this situation in the 
> native client is to move some of the bazillions of inline methods declared in 
> headers into .cpp files.  A change to one of these methods then triggers a 
> recompile of just that file, rather than the large number of native client 
> files that inevitably include the header.
> This item covers the above transformation for the internal classes involved 
> in logging and statistics.  While there, we should clean up a couple of other 
> things that are unnecessary, such as the use of our own `NonCopyable` and 
> `NonAssignable`, both of which can now easily be accomplished with a standard 
> C++ 11 mechanism.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GEODE-7623) AlertingAction thread local looks like it will no longer have any effect

2019-12-24 Thread Dan Smith (Jira)
Dan Smith created GEODE-7623:


 Summary: AlertingAction thread local looks like it will no longer 
have any effect
 Key: GEODE-7623
 URL: https://issues.apache.org/jira/browse/GEODE-7623
 Project: Geode
  Issue Type: Bug
  Components: logging, membership
Reporter: Dan Smith


>From code inspection, it looks like the changes in dffcb944 have made the 
>AlertingAction class effectively useless.

The class has a thread local that is set when we start sending an alert. But 
dffcb944 changed the alert process such that shortly after the thread local is 
set, the bulk of the alerting logic happens in a *separate* thread, without the 
thread local, in ClusterAlertMessaging.sendAlert.

Therefore, this thread local has no effect. If this behavior was previously 
useful, we need to set the thread local inside this new executor thread, 
perhaps? Or find some other way to prevent the executor from triggering new 
alerts?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-6107) CI Failure: org.apache.geode.management.JMXMBeanReconnectDUnitTest > testRemoteBeanKnowledge_MaintainServerAndCrashLocator

2019-12-24 Thread Benjamin P Ross (Jira)


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

Benjamin P Ross commented on GEODE-6107:


Another CI failure: 
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1433]

 I agree with Owen, if we know that this test fails because of a product issue 
we should either leave this story open or have a different story to track the 
known issue.

> CI Failure: org.apache.geode.management.JMXMBeanReconnectDUnitTest > 
> testRemoteBeanKnowledge_MaintainServerAndCrashLocator
> --
>
> Key: GEODE-6107
> URL: https://issues.apache.org/jira/browse/GEODE-6107
> Project: Geode
>  Issue Type: Bug
>Reporter: Ryan McMahon
>Assignee: Helena Bales
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.9.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Build:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/172
> Results:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.210/test-results/distributedTest/1543449109/
> Artifacts:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.210/test-artifacts/1543449109/distributedtestfiles-OpenJDK8-1.9.0-build.210.tgz
> {noformat}org.apache.geode.management.JMXMBeanReconnectDUnitTest > 
> testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with alias 
> 'Locators must agree on the state of the system' didn't complete within 300 
> seconds because assertion condition defined as a lambda expression in 
> org.apache.geode.management.JMXMBeanReconnectDUnitTest 
> Expecting:
>   <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
> GemFire:service=FileUploader,type=Distributed,
> GemFire:service=System,type=Distributed,
> 
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-one,
> 
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-one,
> GemFire:service=Locator,type=Member,member=locator-one,
> GemFire:type=Member,member=locator-one,
> 
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-two,
> 
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-two,
> GemFire:service=Locator,type=Member,member=locator-two,
> GemFire:type=Member,member=locator-two,
> 
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> GemFire:service=CacheServer,port=33929,type=Member,member=server-2,
> GemFire:type=Member,member=server-2,
> 
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> GemFire:service=CacheServer,port=46497,type=Member,member=server-3,
> GemFire:type=Member,member=server-3]>
> to contain exactly (and in same order):
>   <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
> GemFire:service=FileUploader,type=Distributed,
> GemFire:service=System,type=Distributed,
> 
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-one,
> GemFire:service=Locator,type=Member,member=locator-one,
> GemFire:type=Member,member=locator-one,
> 
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-two,
> 
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-two,
> GemFire:service=Locator,type=Member,member=locator-two,
> GemFire:type=Member,member=locator-two,
> 
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> GemFire:service=CacheServer,port=33929,type=Member,member=server-2,
> GemFire:type=Member,member=server-2,
> 
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> GemFire:service=CacheServer,port=46497,type=Member,member=server-3,
> GemFire:type=Member,member=server-3]>
> but some elements were not expected:
>   
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-one]>
> .
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> 

[jira] [Comment Edited] (GEODE-7622) CI Failure: JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails with ConditionTimeoutException

2019-12-24 Thread Benjamin P Ross (Jira)


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

Benjamin P Ross edited comment on GEODE-7622 at 12/24/19 7:00 PM:
--

Resolving this issue since it's a duplicate of 
https://issues.apache.org/jira/browse/GEODE-6107


was (Author: sarm kahel):
Resolving this issue since it's a duplicate of 
https://issues.apache.org/jira/browse/GEODE-7106

> CI Failure: 
> JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails 
> with ConditionTimeoutException
> 
>
> Key: GEODE-7622
> URL: https://issues.apache.org/jira/browse/GEODE-7622
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Benjamin P Ross
>Priority: Major
>
> We've seen JMXMBeanReconnectDUnitTest fail intermittently with 
> {code:java}
> org.awaitility.core.ConditionTimeoutException: Condition with alias 'Locators 
> must agree on the state of the system' didn't complete within 300 seconds 
> because assertion condition defined as a lambda expression in 
> org.apache.geode.management.JMXMBeanReconnectDUnitTest 
> 18:26:35Expecting:
> 18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 18:26:35GemFire:service=AccessControl,type=Distributed,
> 18:26:35GemFire:service=FileUploader,type=Distributed,
> 18:26:35GemFire:service=System,type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-0,
> 18:26:35GemFire:type=Member,member=locator-0,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-1,
> 18:26:35GemFire:type=Member,member=locator-1,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> 18:26:35
> GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
> 18:26:35GemFire:type=Member,member=server-2,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> 18:26:35
> GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
> 18:26:35GemFire:type=Member,member=server-3]>
> 18:26:35to contain exactly (and in same order):
> 18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 18:26:35GemFire:service=AccessControl,type=Distributed,
> 18:26:35GemFire:service=FileUploader,type=Distributed,
> 18:26:35GemFire:service=System,type=Distributed,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-0,
> 18:26:35GemFire:type=Member,member=locator-0,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-1,
> 18:26:35GemFire:type=Member,member=locator-1,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> 18:26:35
> GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
> 18:26:35GemFire:type=Member,member=server-2,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> 18:26:35
> GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
> 18:26:35GemFire:type=Member,member=server-3]>
> 18:26:35but some elements were not expected:
> 18:26:35  
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0]>
> 18:26:35.
> 18:26:35at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 18:26:35at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 18:26:35at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 18:26:35at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 18:26:35at 
> 

[jira] [Commented] (GEODE-7622) CI Failure: JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails with ConditionTimeoutException

2019-12-24 Thread Benjamin P Ross (Jira)


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

Benjamin P Ross commented on GEODE-7622:


Resolving this issue since it's a duplicate of 
https://issues.apache.org/jira/browse/GEODE-7106

> CI Failure: 
> JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails 
> with ConditionTimeoutException
> 
>
> Key: GEODE-7622
> URL: https://issues.apache.org/jira/browse/GEODE-7622
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Benjamin P Ross
>Priority: Major
>
> We've seen JMXMBeanReconnectDUnitTest fail intermittently with 
> {code:java}
> org.awaitility.core.ConditionTimeoutException: Condition with alias 'Locators 
> must agree on the state of the system' didn't complete within 300 seconds 
> because assertion condition defined as a lambda expression in 
> org.apache.geode.management.JMXMBeanReconnectDUnitTest 
> 18:26:35Expecting:
> 18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 18:26:35GemFire:service=AccessControl,type=Distributed,
> 18:26:35GemFire:service=FileUploader,type=Distributed,
> 18:26:35GemFire:service=System,type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-0,
> 18:26:35GemFire:type=Member,member=locator-0,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-1,
> 18:26:35GemFire:type=Member,member=locator-1,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> 18:26:35
> GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
> 18:26:35GemFire:type=Member,member=server-2,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> 18:26:35
> GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
> 18:26:35GemFire:type=Member,member=server-3]>
> 18:26:35to contain exactly (and in same order):
> 18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 18:26:35GemFire:service=AccessControl,type=Distributed,
> 18:26:35GemFire:service=FileUploader,type=Distributed,
> 18:26:35GemFire:service=System,type=Distributed,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-0,
> 18:26:35GemFire:type=Member,member=locator-0,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-1,
> 18:26:35GemFire:type=Member,member=locator-1,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> 18:26:35
> GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
> 18:26:35GemFire:type=Member,member=server-2,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> 18:26:35
> GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
> 18:26:35GemFire:type=Member,member=server-3]>
> 18:26:35but some elements were not expected:
> 18:26:35  
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0]>
> 18:26:35.
> 18:26:35at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 18:26:35at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 18:26:35at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 18:26:35at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 18:26:35at 
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> 18:26:35at 
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.before(JMXMBeanReconnectDUnitTest.java:94)
> 18:26:35
> 18:26:35

[jira] [Resolved] (GEODE-7622) CI Failure: JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails with ConditionTimeoutException

2019-12-24 Thread Benjamin P Ross (Jira)


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

Benjamin P Ross resolved GEODE-7622.

Resolution: Duplicate

> CI Failure: 
> JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails 
> with ConditionTimeoutException
> 
>
> Key: GEODE-7622
> URL: https://issues.apache.org/jira/browse/GEODE-7622
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Benjamin P Ross
>Priority: Major
>
> We've seen JMXMBeanReconnectDUnitTest fail intermittently with 
> {code:java}
> org.awaitility.core.ConditionTimeoutException: Condition with alias 'Locators 
> must agree on the state of the system' didn't complete within 300 seconds 
> because assertion condition defined as a lambda expression in 
> org.apache.geode.management.JMXMBeanReconnectDUnitTest 
> 18:26:35Expecting:
> 18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 18:26:35GemFire:service=AccessControl,type=Distributed,
> 18:26:35GemFire:service=FileUploader,type=Distributed,
> 18:26:35GemFire:service=System,type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-0,
> 18:26:35GemFire:type=Member,member=locator-0,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-1,
> 18:26:35GemFire:type=Member,member=locator-1,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> 18:26:35
> GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
> 18:26:35GemFire:type=Member,member=server-2,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> 18:26:35
> GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
> 18:26:35GemFire:type=Member,member=server-3]>
> 18:26:35to contain exactly (and in same order):
> 18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> 18:26:35GemFire:service=AccessControl,type=Distributed,
> 18:26:35GemFire:service=FileUploader,type=Distributed,
> 18:26:35GemFire:service=System,type=Distributed,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-0,
> 18:26:35GemFire:type=Member,member=locator-0,
> 18:26:35
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> 18:26:35GemFire:service=Locator,type=Member,member=locator-1,
> 18:26:35GemFire:type=Member,member=locator-1,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> 18:26:35
> GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
> 18:26:35GemFire:type=Member,member=server-2,
> 18:26:35
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> 18:26:35
> GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
> 18:26:35GemFire:type=Member,member=server-3]>
> 18:26:35but some elements were not expected:
> 18:26:35  
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
> 18:26:35
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0]>
> 18:26:35.
> 18:26:35at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 18:26:35at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 18:26:35at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 18:26:35at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 18:26:35at 
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> 18:26:35at 
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.before(JMXMBeanReconnectDUnitTest.java:94)
> 18:26:35
> 18:26:35Caused by:
> 18:26:35java.lang.AssertionError: 
> 18:26:35Expecting:
> 18:26:35  
> 

[jira] [Created] (GEODE-7622) CI Failure: JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails with ConditionTimeoutException

2019-12-24 Thread Benjamin P Ross (Jira)
Benjamin P Ross created GEODE-7622:
--

 Summary: CI Failure: 
JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainLocatorAndCrashServer fails 
with ConditionTimeoutException
 Key: GEODE-7622
 URL: https://issues.apache.org/jira/browse/GEODE-7622
 Project: Geode
  Issue Type: Bug
  Components: tests
Reporter: Benjamin P Ross


We've seen JMXMBeanReconnectDUnitTest fail intermittently with 
{code:java}
org.awaitility.core.ConditionTimeoutException: Condition with alias 'Locators 
must agree on the state of the system' didn't complete within 300 seconds 
because assertion condition defined as a lambda expression in 
org.apache.geode.management.JMXMBeanReconnectDUnitTest 
18:26:35Expecting:
18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
18:26:35GemFire:service=AccessControl,type=Distributed,
18:26:35GemFire:service=FileUploader,type=Distributed,
18:26:35GemFire:service=System,type=Distributed,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
18:26:35
GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0,
18:26:35GemFire:service=Locator,type=Member,member=locator-0,
18:26:35GemFire:type=Member,member=locator-0,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
18:26:35
GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
18:26:35GemFire:service=Locator,type=Member,member=locator-1,
18:26:35GemFire:type=Member,member=locator-1,
18:26:35
GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
18:26:35
GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
18:26:35GemFire:type=Member,member=server-2,
18:26:35
GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
18:26:35
GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
18:26:35GemFire:type=Member,member=server-3]>
18:26:35to contain exactly (and in same order):
18:26:35  <[GemFire:service=Region,name="/test-region-1",type=Distributed,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
18:26:35GemFire:service=AccessControl,type=Distributed,
18:26:35GemFire:service=FileUploader,type=Distributed,
18:26:35GemFire:service=System,type=Distributed,
18:26:35GemFire:service=Locator,type=Member,member=locator-0,
18:26:35GemFire:type=Member,member=locator-0,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
18:26:35
GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
18:26:35GemFire:service=Locator,type=Member,member=locator-1,
18:26:35GemFire:type=Member,member=locator-1,
18:26:35
GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
18:26:35
GemFire:service=CacheServer,port=35679,type=Member,member=server-2,
18:26:35GemFire:type=Member,member=server-2,
18:26:35
GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
18:26:35
GemFire:service=CacheServer,port=44573,type=Member,member=server-3,
18:26:35GemFire:type=Member,member=server-3]>
18:26:35but some elements were not expected:
18:26:35  
<[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
18:26:35
GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0]>
18:26:35.
18:26:35at 
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
18:26:35at 
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
18:26:35at 
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
18:26:35at 
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
18:26:35at 
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
18:26:35at 
org.apache.geode.management.JMXMBeanReconnectDUnitTest.before(JMXMBeanReconnectDUnitTest.java:94)
18:26:35
18:26:35Caused by:
18:26:35java.lang.AssertionError: 
18:26:35Expecting:
18:26:35  
<[GemFire:service=Region,name="/test-region-1",type=Distributed,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
18:26:35GemFire:service=AccessControl,type=Distributed,
18:26:35GemFire:service=FileUploader,type=Distributed,
18:26:35GemFire:service=System,type=Distributed,
18:26:35
GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
18:26:35   

[jira] [Updated] (GEODE-7456) Extract DirectChannel out of GMSMembershipManager

2019-12-24 Thread Dan Smith (Jira)


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

Dan Smith updated GEODE-7456:
-
Fix Version/s: (was: 1.11.0)
   1.12.0

> Extract DirectChannel out of GMSMembershipManager
> -
>
> Key: GEODE-7456
> URL: https://issues.apache.org/jira/browse/GEODE-7456
> Project: Geode
>  Issue Type: Sub-task
>  Components: membership
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Fix For: 1.12.0
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> The GMSMembershipManager class represents the core class of the membership 
> subsystem. However, it currently is also responsible for owning and 
> delagating `send` calls to the DirectChannel.
> We should pull the DirectChannel related logic out of GMSMembershipManager 
> and move GMSMembershipManager back into the .gms package, indicating that is 
> part of the code to be moved to a future geode-membership module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7386) CI failure: JmxCredentialTypeTest > testWithNonStringCredential failed with AssertionError

2019-12-24 Thread Jinmei Liao (Jira)


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

Jinmei Liao commented on GEODE-7386:


resolved by: 

Revert "GEODE-7373: add jmx credential type constraint (#4236)" (#4265)

This reverts commit 94fedfd7

214b8d82 Jinmei Liao  on 10/31/19 at 3:17 PM
committed by GitHub 

> CI failure: JmxCredentialTypeTest > testWithNonStringCredential failed with 
> AssertionError
> --
>
> Key: GEODE-7386
> URL: https://issues.apache.org/jira/browse/GEODE-7386
> Project: Geode
>  Issue Type: Bug
>  Components: jmx, management, security
>Reporter: Barrett Oglesby
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.11.0
>
>
> This test has failed in the last 2 IntegrationTestOpenJDK8 builds:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1223
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1224
> {noformat}
> org.apache.geode.management.internal.security.JmxCredentialTypeTest > 
> testWithNonStringCredential FAILED
> java.lang.AssertionError: 
> Expecting:
>  <"Unsupported type: java.lang.Integer">
> to contain:
>  <"filter status: REJECTED"> 
> at 
> org.apache.geode.management.internal.security.JmxCredentialTypeTest.testWithNonStringCredential(JmxCredentialTypeTest.java:47)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (GEODE-7466) HARegionQueueTest queuePutElidesSequenceIdLowerThanOrEqualToLastSeenSequenceId can throw a NullPointerException if the CacheClientNotifier instance is set

2019-12-24 Thread Alexander Murmann (Jira)


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

Alexander Murmann updated GEODE-7466:
-
Fix Version/s: (was: 1.11.0)
   1.12.0

> HARegionQueueTest 
> queuePutElidesSequenceIdLowerThanOrEqualToLastSeenSequenceId can throw a 
> NullPointerException if the CacheClientNotifier instance is set
> --
>
> Key: GEODE-7466
> URL: https://issues.apache.org/jira/browse/GEODE-7466
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Barrett Oglesby
>Priority: Major
> Fix For: 1.12.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Testing has shown this NPE can occur:
> {noformat}
> java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
> at 
> org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.getClientProxy(CacheClientNotifier.java:1197)
> at 
> org.apache.geode.internal.cache.ha.HARegionQueue$DispatchedAndCurrentEvents.putObject(HARegionQueue.java:3023)
> at 
> org.apache.geode.internal.cache.ha.HARegionQueue.basicPut(HARegionQueue.java:679)
> at 
> org.apache.geode.internal.cache.ha.HARegionQueue.put(HARegionQueue.java:631)
> at 
> org.apache.geode.internal.cache.ha.HARegionQueueTest.queuePutElidesSequenceIdLowerThanOrEqualToLastSeenSequenceId(HARegionQueueTest.java:119)
> {noformat}
> HARegionQueue.java:3023 is here:
> {noformat}
> CacheClientNotifier ccn = 
> CacheClientNotifier.getInstance();
> if (ccn != null) {
> HARegionQueue.java:3023 ->
> ccn.getClientProxy(owningQueue.clientProxyID).getStatistics().incMessagesFailedQueued();
> }
> {noformat}
> The HARegionQueueTest does not create a CacheClientNotifier, so it seems like 
> its created in another test and that test affects this one.
> If a CacheClientNotifier is created in this test, then the same NPE is thrown 
> because owningQueue.clientProxyID is null.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (GEODE-7148) inconsistent output between "/management/experimental/members/" and "/management/experimental/members/memberid" in REST API V2

2019-12-24 Thread Alexander Murmann (Jira)


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

Alexander Murmann resolved GEODE-7148.
--
Resolution: Won't Fix

> inconsistent output between "/management/experimental/members/" and 
> "/management/experimental/members/memberid" in REST API V2
> --
>
> Key: GEODE-7148
> URL: https://issues.apache.org/jira/browse/GEODE-7148
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Gang Yan
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.11.0
>
>
> the output of "/management/experimental/members/" and 
> "/management/experimental/members/memberid" in REST API V2 are inconsistent.
>  
> output for "/management/experimental/members/":
>  
> {code:json}
> {
> "statusCode": "OK",
> "result": [
> {
> "configuration": {
> "class": 
> "org.apache.geode.management.configuration.MemberConfig"
> },
> "runtimeInfo": [
> {
> "class": 
> "org.apache.geode.management.runtime.MemberInformation",
> "memberName": "g1-g2-s3",
> "id": "10.118.20.61(g1-g2-s3:12432):41004",
> "workingDirPath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3",
> "groups": "g1,g2",
> "logFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3/g1-g2-s3.log",
> "statArchiveFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3",
> "locators": "10.118.20.61[58099],10.118.20.61[58077]",
> "status": "online",
> "heapUsage": 104,
> "maxHeapSize": 7282,
> "initHeapSize": 512,
> "cacheXmlFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3/cache.xml",
> "host": "10.118.20.61",
> "processId": 12432,
> "locatorPort": 0,
> "httpServicePort": 7070,
> "clientCount": 0,
> "cpuUsage": 0.0,
> "hostedRegions": [
> "Foo6",
> "r_sg_1",
> "REGION6",
> "r_mG_1_2",
> "customers4",
> "customers13"
> ],
> "webSSL": false,
> "secured": false,
> "cacheServerInfo": [
> {
> "port": 58188,
> "maxConnections": 800,
> "maxThreads": 0,
> "running": true
> }
> ],
> "server": true,
> "coordinator": false
> },
> {
> "class": 
> "org.apache.geode.management.runtime.MemberInformation",
> "memberName": "g2-s2",
> "id": "10.118.20.61(g2-s2:12428):41003",
> "workingDirPath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2",
> "groups": "g2",
> "logFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2/g2-s2.log",
> "statArchiveFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2",
> "locators": "10.118.20.61[58099],10.118.20.61[58077]",
> "status": "online",
> "heapUsage": 183,
> "maxHeapSize": 7282,
> "initHeapSize": 512,
> "cacheXmlFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2/cache.xml",
> "host": "10.118.20.61",
> "processId": 12428,
> "locatorPort": 0,
> "httpServicePort": 7070,
> "clientCount": 0,
> "cpuUsage": 0.0,
> "hostedRegions": [
> "Foo6",
> "REGION6",
> "r_mG_1_2",
> "customers13"
> ],
> "webSSL": false,
> "secured": false,
>  

[jira] [Reopened] (GEODE-7148) inconsistent output between "/management/experimental/members/" and "/management/experimental/members/memberid" in REST API V2

2019-12-24 Thread Alexander Murmann (Jira)


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

Alexander Murmann reopened GEODE-7148:
--

> inconsistent output between "/management/experimental/members/" and 
> "/management/experimental/members/memberid" in REST API V2
> --
>
> Key: GEODE-7148
> URL: https://issues.apache.org/jira/browse/GEODE-7148
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Gang Yan
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.11.0
>
>
> the output of "/management/experimental/members/" and 
> "/management/experimental/members/memberid" in REST API V2 are inconsistent.
>  
> output for "/management/experimental/members/":
>  
> {code:json}
> {
> "statusCode": "OK",
> "result": [
> {
> "configuration": {
> "class": 
> "org.apache.geode.management.configuration.MemberConfig"
> },
> "runtimeInfo": [
> {
> "class": 
> "org.apache.geode.management.runtime.MemberInformation",
> "memberName": "g1-g2-s3",
> "id": "10.118.20.61(g1-g2-s3:12432):41004",
> "workingDirPath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3",
> "groups": "g1,g2",
> "logFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3/g1-g2-s3.log",
> "statArchiveFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3",
> "locators": "10.118.20.61[58099],10.118.20.61[58077]",
> "status": "online",
> "heapUsage": 104,
> "maxHeapSize": 7282,
> "initHeapSize": 512,
> "cacheXmlFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g1-g2-s3/cache.xml",
> "host": "10.118.20.61",
> "processId": 12432,
> "locatorPort": 0,
> "httpServicePort": 7070,
> "clientCount": 0,
> "cpuUsage": 0.0,
> "hostedRegions": [
> "Foo6",
> "r_sg_1",
> "REGION6",
> "r_mG_1_2",
> "customers4",
> "customers13"
> ],
> "webSSL": false,
> "secured": false,
> "cacheServerInfo": [
> {
> "port": 58188,
> "maxConnections": 800,
> "maxThreads": 0,
> "running": true
> }
> ],
> "server": true,
> "coordinator": false
> },
> {
> "class": 
> "org.apache.geode.management.runtime.MemberInformation",
> "memberName": "g2-s2",
> "id": "10.118.20.61(g2-s2:12428):41003",
> "workingDirPath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2",
> "groups": "g2",
> "logFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2/g2-s2.log",
> "statArchiveFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2",
> "locators": "10.118.20.61[58099],10.118.20.61[58077]",
> "status": "online",
> "heapUsage": 183,
> "maxHeapSize": 7282,
> "initHeapSize": 512,
> "cacheXmlFilePath": 
> "/Users/gyan/IdeaProjects/geode_dev/geode-assembly/build/install/apache-geode/bin/g2-s2/cache.xml",
> "host": "10.118.20.61",
> "processId": 12428,
> "locatorPort": 0,
> "httpServicePort": 7070,
> "clientCount": 0,
> "cpuUsage": 0.0,
> "hostedRegions": [
> "Foo6",
> "REGION6",
> "r_mG_1_2",
> "customers13"
> ],
> "webSSL": false,
> "secured": false,
> 

[jira] [Commented] (GEODE-7541) Break dependency on SocketCreator/Factory & SecurableCommunicationChannel

2019-12-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7541:


Commit 0cf6c42b73e935b2a43354f8bdd2efc0c3b6f59a in geode's branch 
refs/heads/feature/GEODE-7541c from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0cf6c42 ]

GEODE-7541: move SocketCreator localhost lookup to geode-common

General host address lookup remains in SocketCreator while localhost-
related functionality has moved to LocalHostUtil.


> Break dependency on SocketCreator/Factory & SecurableCommunicationChannel
> -
>
> Key: GEODE-7541
> URL: https://issues.apache.org/jira/browse/GEODE-7541
> Project: Geode
>  Issue Type: Sub-task
>  Components: membership
>Reporter: Ernest Burghardt
>Priority: Major
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> SocketCreator & SocketCreatorFactory.
> {color:#a8c023}which should also allow for break dependency on 
> internal.security{color}SecurableCommunicationChannel
>  
> Also look at usage of
> {code:java}
> OSProcess {code}
> in JGroupsMessenger
> {code:java}
> SocketCreator.resolve_dns ? 
> SocketCreator.getHostName(jgAddress.getInetAddress())
>  : jgAddress.getInetAddress().getHostAddress();
> GMSMemberData gmsMember = new GMSMemberData(jgAddress.getInetAddress(),
>  hostname, jgAddress.getPort(),
>  OSProcess.getId(),{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (GEODE-7386) CI failure: JmxCredentialTypeTest > testWithNonStringCredential failed with AssertionError

2019-12-24 Thread Dick Cavender (Jira)


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

Dick Cavender updated GEODE-7386:
-
Description: 
This test has failed in the last 2 IntegrationTestOpenJDK8 builds:

https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1223
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1224
{noformat}
org.apache.geode.management.internal.security.JmxCredentialTypeTest > 
testWithNonStringCredential FAILED
java.lang.AssertionError: 
Expecting:
 <"Unsupported type: java.lang.Integer">

to contain:
 <"filter status: REJECTED"> 
at 
org.apache.geode.management.internal.security.JmxCredentialTypeTest.testWithNonStringCredential(JmxCredentialTypeTest.java:47)
{noformat}


  was:
This test has failed in the last 2 IntegrationTestOpenJDK8 builds:

https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1223
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1224
{noformat}
org.apache.geode.management.internal.security.JmxCredentialTypeTest > 
testWithNonStringCredential FAILED
java.lang.AssertionError: 
Expecting:
 <"Unsupported type: java.lang.Integer">
to contain:
 <"filter status: REJECTED"> 
at 
org.apache.geode.management.internal.security.JmxCredentialTypeTest.testWithNonStringCredential(JmxCredentialTypeTest.java:47)
{noformat}



> CI failure: JmxCredentialTypeTest > testWithNonStringCredential failed with 
> AssertionError
> --
>
> Key: GEODE-7386
> URL: https://issues.apache.org/jira/browse/GEODE-7386
> Project: Geode
>  Issue Type: Bug
>  Components: jmx, management, security
>Reporter: Barrett Oglesby
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.11.0
>
>
> This test has failed in the last 2 IntegrationTestOpenJDK8 builds:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1223
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1224
> {noformat}
> org.apache.geode.management.internal.security.JmxCredentialTypeTest > 
> testWithNonStringCredential FAILED
> java.lang.AssertionError: 
> Expecting:
>  <"Unsupported type: java.lang.Integer">
> to contain:
>  <"filter status: REJECTED"> 
> at 
> org.apache.geode.management.internal.security.JmxCredentialTypeTest.testWithNonStringCredential(JmxCredentialTypeTest.java:47)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GEODE-7621) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion. luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion fails wit

2019-12-24 Thread Benjamin P Ross (Jira)
Benjamin P Ross created GEODE-7621:
--

 Summary: CI Failure: 
RollingUpgradeQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion. 
luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion fails 
with DSFIDNotFoundException
 Key: GEODE-7621
 URL: https://issues.apache.org/jira/browse/GEODE-7621
 Project: Geode
  Issue Type: Bug
  Components: tests
Reporter: Benjamin P Ross


We've seen 
luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion fail 
intermittently with:
{code:java}
error 2019/12/23 22:05:05.434 GMT  tid=49] 
Exception deserializing message payload: [dst: 172.17.0.8:32772, src: 
172.17.0.8:41002 (2 headers), size=105 bytes, 
flags=OOB|DONT_BUNDLE|NO_FC|SKIP_BARRIER]error 2019/12/23 22:05:05.434 GMT 
 tid=49] Exception deserializing message 
payload: [dst: 172.17.0.8:32772, src: 172.17.0.8:41002 (2 headers), 
size=105 bytes, flags=OOB|DONT_BUNDLE|NO_FC|SKIP_BARRIER]    
org.apache.geode.internal.DSFIDNotFoundException: Unknown 
DataSerializableFixedID: -158    at 
org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:998)    at 
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2693)
    at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)    
at 
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.deserializeMessage(JGroupsMessenger.java:1118)
    at 
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.readJGMessage(JGroupsMessenger.java:1010)
    at 
org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1276)
    at org.jgroups.JChannel.invokeCallback(JChannel.java:816)    at 
org.jgroups.JChannel.up(JChannel.java:741)    at 
org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)    at 
org.jgroups.protocols.FRAG2.up(FRAG2.java:165)    at 
org.jgroups.protocols.FlowControl.up(FlowControl.java:390)    at 
org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1070)    at 
org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:785)    at 
org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426)    at 
org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:74)
    at 
org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:72)
    at org.jgroups.protocols.TP.passMessageUp(TP.java:1601)    at 
org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1817)    at 
org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)    at 
org.jgroups.protocols.TP.handleSingleMessage(TP.java:1729)    at 
org.jgroups.protocols.TP.receive(TP.java:1654)    at 
org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
    at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)    at 
java.base/java.lang.Thread.run(Thread.java:834){code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7541) Break dependency on SocketCreator/Factory & SecurableCommunicationChannel

2019-12-24 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7541:


Commit 1ab69cda2a7440d64c9edae4507b1a1304a1c2ec in geode's branch 
refs/heads/feature/GEODE-7541b from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ab69cd ]

GEODE-7541: revert one change

One of the changes for this ticket is causing unit test failures on
some machines - especially Macs - in the form of

java.lang.RuntimeException: Failed to start locator
  Caused by:
  org.apache.geode.GemFireConfigException: This process is attempting to 
join with a loopback address (gzhou-mbpro/127.0.0.1) using a locator that does 
not have a local address (/10.255.200.197:60167). On Unix this usually means 
that /etc/hosts is misconfigured.


> Break dependency on SocketCreator/Factory & SecurableCommunicationChannel
> -
>
> Key: GEODE-7541
> URL: https://issues.apache.org/jira/browse/GEODE-7541
> Project: Geode
>  Issue Type: Sub-task
>  Components: membership
>Reporter: Ernest Burghardt
>Priority: Major
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> SocketCreator & SocketCreatorFactory.
> {color:#a8c023}which should also allow for break dependency on 
> internal.security{color}SecurableCommunicationChannel
>  
> Also look at usage of
> {code:java}
> OSProcess {code}
> in JGroupsMessenger
> {code:java}
> SocketCreator.resolve_dns ? 
> SocketCreator.getHostName(jgAddress.getInetAddress())
>  : jgAddress.getInetAddress().getHostAddress();
> GMSMemberData gmsMember = new GMSMemberData(jgAddress.getInetAddress(),
>  hostname, jgAddress.getPort(),
>  OSProcess.getId(),{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GEODE-7620) Improve build on macOS Catalina

2019-12-24 Thread Jacob Barrett (Jira)
Jacob Barrett created GEODE-7620:


 Summary: Improve build on macOS Catalina
 Key: GEODE-7620
 URL: https://issues.apache.org/jira/browse/GEODE-7620
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Jacob Barrett


Improve build to not require SDK headers installation.

Update third party dependencies.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)