date:20180416

[jira] [Updated] (GEODE-5088) Remove getContentAsString from CommandResult

2018-04-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated GEODE-5088:
--
Labels: pull-request-available  (was: )

> Remove getContentAsString from CommandResult
> 
>
> Key: GEODE-5088
> URL: https://issues.apache.org/jira/browse/GEODE-5088
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>
> This allows for more specific response interrogation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread Jens Deppe (JIRA)


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

Jens Deppe resolved GEODE-5080.
---
   Resolution: Fixed
Fix Version/s: 1.7.0

> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>   at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
>

[jira] [Updated] (GEODE-5018) Cache should wrap CacheImpl (fully honor the pimpl model)

2018-04-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated GEODE-5018:
--
Labels: pull-request-available  (was: )

> Cache should wrap CacheImpl (fully honor the pimpl model)
> -
>
> Key: GEODE-5018
> URL: https://issues.apache.org/jira/browse/GEODE-5018
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Ernest Burghardt
>Priority: Major
>  Labels: pull-request-available
>
> CacheImpl should own TypeRegistry etc... i.e. fix anything not honoring the 
> pimpl model...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5080:


Commit 3e4931858487a0b6ae1e23218dbf806c5f9f1359 in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3e49318 ]

GEODE-5080: Ensure that reconnect sequence has started (#1805)



> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   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

[jira] [Assigned] (GEODE-5087) SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting intermittently fail

2018-04-16 Thread xiaojian zhou (JIRA)


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

xiaojian zhou reassigned GEODE-5087:


Assignee: xiaojian zhou

> SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting
>  intermittently fail 
> ---
>
> Key: GEODE-5087
> URL: https://issues.apache.org/jira/browse/GEODE-5087
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>
> I introduced this dunit test for GEODE-4942, while GEODE-4942 is for parallel 
> gateway sender, the test is for serial gateway sender. And I did reproduce 
> the issue: event is dropped at primary sender (because it's not running yet), 
> but event has been put into unprocessedEventsMap at secondary sender's queue 
> and will stay there forever.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5087) SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting intermittently fail

2018-04-16 Thread xiaojian zhou (JIRA)

xiaojian zhou created GEODE-5087:


 Summary: 
SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting
 intermittently fail 
 Key: GEODE-5087
 URL: https://issues.apache.org/jira/browse/GEODE-5087
 Project: Geode
  Issue Type: Bug
  Components: wan
Reporter: xiaojian zhou


I introduced this dunit test for GEODE-4942, while GEODE-4942 is for parallel 
gateway sender, the test is for serial gateway sender. And I did reproduce the 
issue: event is dropped at primary sender (because it's not running yet), but 
event has been put into unprocessedEventsMap at secondary sender's queue and 
will stay there forever.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals

2018-04-16 Thread xiaojian zhou (JIRA)


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

xiaojian zhou resolved GEODE-4624.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

fixed in GEODE-4647 revision 

69815f90ad22c10b0a9b7236c02f9bf04ec28223

> Add a new stat for AyncEventQueue/GatewaySender to track the processing of 
> queueRemovals
> 
>
> Key: GEODE-4624
> URL: https://issues.apache.org/jira/browse/GEODE-4624
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Affects Versions: 1.5.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: xiaojian zhou
>Priority: Major
> Fix For: 1.6.0
>
>
> We currently track the number of events queues, queue size and 
> eventsDistributed ... but we don't track the number of events removed via 
> queue removal. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

2018-04-16 Thread xiaojian zhou (JIRA)


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

xiaojian zhou resolved GEODE-4647.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4647:


Commit 69815f90ad22c10b0a9b7236c02f9bf04ec28223 in geode's branch 
refs/heads/develop from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=69815f9 ]

GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary
gateway sender queue


> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4954:


Commit 00aa0de0f3c2f89fae31a4ac0bc75bd8596cb15b in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=00aa0de ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core:cache (#1783)




> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4955:


Commit 00aa0de0f3c2f89fae31a4ac0bc75bd8596cb15b in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=00aa0de ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core:cache (#1783)




> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4647:


Commit 3977040ece878609bfec34f27b15dbba1b403f94 in geode's branch 
refs/heads/feature/GEODE-4647 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3977040 ]

GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary
gateway sender queue


> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5086) Clarify Java 8 (not 9) requirement in docs

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5086:


Commit 2f607ffe4918ff6bab4ea8deee6f10130a96d0fc in geode's branch 
refs/heads/feature/GEODE-4647 from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2f607ff ]

GEODE-5086 Clarify docs: we need version 8 Java (#1808)

- Also updated a few places that called out a specific version 8
update, and changed them to use a variable instead of a specific
version

> Clarify Java 8 (not 9) requirement in docs
> --
>
> Key: GEODE-5086
> URL: https://issues.apache.org/jira/browse/GEODE-5086
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Our docs state that Geode works with Java 8 an above.  That would imply Java 
> 9, and we don't work with Java 9.  So, clarify the docs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5000) When initializing a client cache, we don't need to request/apply cluster configuration

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5000:


Commit ad11ef0dd338eb0baf5f36a4d71899fe892ed0d0 in geode's branch 
refs/heads/feature/GEODE-4647 from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad11ef0 ]

GEODE-5000: fix logging message. (#1763)



> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --
>
> Key: GEODE-5000
> URL: https://issues.apache.org/jira/browse/GEODE-5000
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The user running a gemfire client doesn't have write access to the local dirs 
> in the customer environment, and they get an stack trace in their logs. This 
> is caused by a client cache trying to request/apply cluster configuration.
> {noformat}
> [error 2018/02/12 17:52:13.899 EST  tid=0x12] Error 
> when attempting to deploy JAR files on load.
> java.io.IOException: Unable to write to deploy directory
> at 
> org.apache.geode.internal.JarDeployer.verifyWritableDeployDirectory(JarDeployer.java:626)
> at 
> org.apache.geode.internal.JarDeployer.loadPreviouslyDeployedJars(JarDeployer.java:74)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1242)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:794)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createClient(GemFireCacheImpl.java:767)
> at 
> org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:257)
> at 
> org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:207){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5022) Transactions do not support propagating deltas

2018-04-16 Thread Karen Smoler Miller (JIRA)


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

Karen Smoler Miller updated GEODE-5022:
---
Component/s: docs

> Transactions do not support propagating deltas
> --
>
> Key: GEODE-5022
> URL: https://issues.apache.org/jira/browse/GEODE-5022
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, transactions
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0
>Reporter: Bruce Schuchardt
>Priority: Minor
> Attachments: TransactionsWithDeltaDUnitTest.java
>
>
> Client to server transactions propagate a delta from the client to the 
> server.  The server then applies the delta to its cache and forgets about it. 
>  It transmits the full object to other servers and to clients.
> Server-initiated transactions also ignore delta values.
> I'm attaching a client/server test that demonstrates the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4791:


Commit b5444f895e1ff6ca61400adacc7c024518262052 in geode's branch 
refs/heads/feature/GEODE-4791 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b5444f8 ]

GEODE-4791: move metainf in java.gradle


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-5086) Clarify Java 8 (not 9) requirement in docs

2018-04-16 Thread Karen Smoler Miller (JIRA)


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

Karen Smoler Miller resolved GEODE-5086.

   Resolution: Fixed
Fix Version/s: 1.7.0

> Clarify Java 8 (not 9) requirement in docs
> --
>
> Key: GEODE-5086
> URL: https://issues.apache.org/jira/browse/GEODE-5086
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Our docs state that Geode works with Java 8 an above.  That would imply Java 
> 9, and we don't work with Java 9.  So, clarify the docs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-717) CI failure: RedisDistDUnitTest.testConcCreateDestroy

2018-04-16 Thread Addison (JIRA)


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

Addison resolved GEODE-717.
---
Resolution: Won't Do

> CI failure: RedisDistDUnitTest.testConcCreateDestroy
> 
>
> Key: GEODE-717
> URL: https://issues.apache.org/jira/browse/GEODE-717
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Jianxia Chen
>Priority: Major
>  Labels: CI, Flaky
>
> Failed 1 times in the last 30 runs. Stability: 96 %
> Error Message
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host 
> kuwait.gemstone.com with 4 VMs
> Stacktrace
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host 
> kuwait.gemstone.com with 4 VMs
>   at dunit.VM.invoke(VM.java:369)
>   at dunit.VM.invoke(VM.java:312)
>   at dunit.VM.invoke(VM.java:280)
>   at 
> com.gemstone.gemfire.redis.RedisDistDUnitTest.setUp(RedisDistDUnitTest.java:94)
>   at junit.framework.TestCase.runBare(TestCase.java:139)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.RuntimeException: Could not start Server
>   at 
> com.gemstone.gemfire.redis.GemFireRedisServer.start(GemFireRedisServer.java:387)
>   at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.startRedisServer(GemFireCacheImpl.java:1243)
>   at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1167)
>   at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:774)
>   at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:794)
>   at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:179)
>   at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:226)
>   at 
> com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call(RedisDistDUnitTest.java:89)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native

[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4954:


Commit 00aa0de0f3c2f89fae31a4ac0bc75bd8596cb15b in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=00aa0de ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core:cache (#1783)




> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4955:


Commit 00aa0de0f3c2f89fae31a4ac0bc75bd8596cb15b in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=00aa0de ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core:cache (#1783)




> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-2380) Replace use of geode-json with Jackson

2018-04-16 Thread Addison (JIRA)


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

Addison resolved GEODE-2380.

Resolution: Duplicate

> Replace use of geode-json with Jackson
> --
>
> Key: GEODE-2380
> URL: https://issues.apache.org/jira/browse/GEODE-2380
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management, pulse, rest (admin), rest (dev)
>Reporter: Kirk Lund
>Priority: Major
>  Labels: HttpService, gfsh, jmx, json
>
> The following classes use geode-json which is a fork of org.json:
> geode-core main classes:
> * 
> geode-core/src/main/java/org/apache/geode/management/internal/cli/domain/DataCommandResult.java
> * 
> geode-core/src/main/java/org/apache/geode/management/internal/cli/json/GfJsonObject.java
> * 
> geode-core/src/main/java/org/apache/geode/management/internal/cli/modes/CommandModes.java
> * 
> geode-core/src/main/java/org/apache/geode/management/internal/cli/util/JsonUtil.java
> geode-web-api classes:
> * 
> geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/AbstractBaseController.java
> geode-assembly test classes
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/GeodeRestClient.java
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityIntegrationTest.java
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityPostProcessorTest.java
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/SwaggerVerificationIntegrationTest.java
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/controllers/RestAPIsAndInterOpsDUnitTest.java
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/controllers/RestQueryAndFunctionIntegrationTest.java
> * 
> geode-assembly/src/test/java/org/apache/geode/rest/internal/web/controllers/RestAPIsWithSSLDUnitTest.java
> geode-core test classes:
> * 
> geode-core/src/test/java/org/apache/geode/distributed/internal/deadlock/GemFireDeadlockDetectorDUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/management/DataBrowserJSONValidationJUnitTest.java
> * geode-core/src/test/java/org/apache/geode/management/QueryDataDUnitTest.java
> * geode-core/src/test/java/org/apache/geode/pdx/JSONFormatterJUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/pdx/JSONPdxClientServerDUnitTest.java
> * 
> geode-core/src/test/java/org/apache/geode/pdx/TestObjectForJSONFOrmatter.java
> geode-pulse test classes:
> * 
> geode-core/src/test/java/org/apache/geode/tools/pulse/tests/junit/ClusterSelectedRegionServiceTest.java
> * 
> geode-core/src/test/java/org/apache/geode/tools/pulse/tests/junit/ClusterSelectedRegionsMemberServiceTest.java
> * 
> geode-core/src/test/java/org/apache/geode/tools/pulse/tests/junit/MemberGatewayHubServiceTest.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5000) When initializing a client cache, we don't need to request/apply cluster configuration

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5000:


Commit ad11ef0dd338eb0baf5f36a4d71899fe892ed0d0 in geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad11ef0 ]

GEODE-5000: fix logging message. (#1763)



> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --
>
> Key: GEODE-5000
> URL: https://issues.apache.org/jira/browse/GEODE-5000
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The user running a gemfire client doesn't have write access to the local dirs 
> in the customer environment, and they get an stack trace in their logs. This 
> is caused by a client cache trying to request/apply cluster configuration.
> {noformat}
> [error 2018/02/12 17:52:13.899 EST  tid=0x12] Error 
> when attempting to deploy JAR files on load.
> java.io.IOException: Unable to write to deploy directory
> at 
> org.apache.geode.internal.JarDeployer.verifyWritableDeployDirectory(JarDeployer.java:626)
> at 
> org.apache.geode.internal.JarDeployer.loadPreviouslyDeployedJars(JarDeployer.java:74)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1242)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:794)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createClient(GemFireCacheImpl.java:767)
> at 
> org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:257)
> at 
> org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:207){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-2323) JSONFormatter refactor/improvements

2018-04-16 Thread Addison (JIRA)


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

Addison resolved GEODE-2323.

Resolution: Done

> JSONFormatter refactor/improvements
> ---
>
> Key: GEODE-2323
> URL: https://issues.apache.org/jira/browse/GEODE-2323
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Hitesh Khamesra
>Priority: Major
>
> 1. Maybe this could be a little "smarter". Maybe you have a DataMapperFactory 
> or PDXDataMapperFactory. Then this could return you the correct dataMapper.
> This is also a pattern that would allow us to be more extendable.
> 2. The add**Field method all follow a simple pattern... log method and field 
> information  add field to a field list
> Could we not get a generic method out of this and instead of "copy paste" the 
> same logic over and over again... rather call the generic method:
> insertField(parentMethodName,fieldName,value,FieldType)
> 3. maybe a very niche "improvement" but could we be "smart" and order the 
> fields in alphabetical AND maybe data types? In ReflectionPdxSerializer we 
> try and do fixed length fields before we do variable length. Might be a 
> "nice" improvement.
> 4. Maybe as part of a refactor the Factory can be held onto. According to the 
> docs they are reusable and thread-safe.
>  An issue was opened.  Fixed  Drop
>  
> 5. Maybe we can have a "getJSONParser(Object input)" method that would return 
> a jsonParser. Then we can merge the two fromJson methods or at least not 
> duplicate the internals.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5086) Clarify Java 8 (not 9) requirement in docs

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5086:


Commit 2f607ffe4918ff6bab4ea8deee6f10130a96d0fc in geode's branch 
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2f607ff ]

GEODE-5086 Clarify docs: we need version 8 Java (#1808)

- Also updated a few places that called out a specific version 8
update, and changed them to use a variable instead of a specific
version

> Clarify Java 8 (not 9) requirement in docs
> --
>
> Key: GEODE-5086
> URL: https://issues.apache.org/jira/browse/GEODE-5086
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Our docs state that Geode works with Java 8 an above.  That would imply Java 
> 9, and we don't work with Java 9.  So, clarify the docs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-1697) RedisDistDUnitTest.testConcOps

2018-04-16 Thread Addison (JIRA)


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

Addison resolved GEODE-1697.

Resolution: Won't Fix

> RedisDistDUnitTest.testConcOps
> --
>
> Key: GEODE-1697
> URL: https://issues.apache.org/jira/browse/GEODE-1697
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Kevin Duling
>Assignee: Addison
>Priority: Major
>  Labels: ci
>
> In Geode_develop_DistributedTests/3405:
> {noformat}
> Error Message
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
> Stacktrace
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155)
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178)
>   at 
> org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
>

[jira] [Reopened] (GEODE-1697) RedisDistDUnitTest.testConcOps

2018-04-16 Thread Addison (JIRA)


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

Addison reopened GEODE-1697:

  Assignee: Addison  (was: Hitesh Khamesra)

> RedisDistDUnitTest.testConcOps
> --
>
> Key: GEODE-1697
> URL: https://issues.apache.org/jira/browse/GEODE-1697
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Kevin Duling
>Assignee: Addison
>Priority: Major
>  Labels: ci
>
> In Geode_develop_DistributedTests/3405:
> {noformat}
> Error Message
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
> Stacktrace
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155)
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178)
>   at 
> org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
>

[jira] [Resolved] (GEODE-1697) RedisDistDUnitTest.testConcOps

2018-04-16 Thread Addison (JIRA)


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

Addison resolved GEODE-1697.

Resolution: Not A Problem

> RedisDistDUnitTest.testConcOps
> --
>
> Key: GEODE-1697
> URL: https://issues.apache.org/jira/browse/GEODE-1697
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Kevin Duling
>Assignee: Hitesh Khamesra
>Priority: Major
>  Labels: ci
>
> In Geode_develop_DistributedTests/3405:
> {noformat}
> Error Message
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
> Stacktrace
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155)
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178)
>   at 
> org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
>

[jira] [Assigned] (GEODE-5085) authentication failure when auto-reconnecting

2018-04-16 Thread Bruce Schuchardt (JIRA)


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

Bruce Schuchardt reassigned GEODE-5085:
---

Assignee: Bruce Schuchardt

> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
>  Issue Type: Bug
>  Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() 
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to 
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
>   @Override
>   public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
>   dsProperties = new Properties();
>   dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
>   dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
>   dsProperties.put(DISABLE_AUTO_RECONNECT, "false");
>   dsProperties.put(ENABLE_CLUSTER_CONFIGURATION, "false");
>   dsProperties.put(LOCATORS, "localHost[" + locatorPort + "]");
>   dsProperties.put(MCAST_PORT, "0");
>   dsProperties.put(MEMBER_TIMEOUT, "1000");
>   dsProperties.put(LOG_LEVEL, LogWriterUtils.getDUnitLogLevel());
>   dsProperties.put(SECURITY_MANAGER, 
> SimpleSecurityManager.class.getName());
>   dsProperties.put("security-username", "clusterManage");
>   dsProperties.put("security-password", "clusterManage");

[jira] [Updated] (GEODE-4990) Race Condition When Using Cluster Configuration Service

2018-04-16 Thread Barbara Pruijn (JIRA)


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

Barbara Pruijn updated GEODE-4990:
--
Fix Version/s: (was: 1.6.0)
   1.7.0

> Race Condition When Using Cluster Configuration Service
> ---
>
> Key: GEODE-4990
> URL: https://issues.apache.org/jira/browse/GEODE-4990
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, locator
>Affects Versions: 1.4.0
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> There's a small window of time on which the locator 
> ({{enable-cluster-configuration=true}}) is receiving TCP requests from 
> starting up servers ({{use-cluster-configuration=true}}) but the cluster 
> configuration service is not yet fully loaded, because of this the servers 
> fail to startup and throw the following exception:
> {noformat}
> Exception in thread "main" org.apache.geode.cache.execute.FunctionException: 
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.execute.FunctionStreamingResultCollector.getResult(FunctionStreamingResultCollector.java:232)
>   at 
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:285)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1036)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:835)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:775)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:764)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:175)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:222)
>   at 
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
>   at 
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:844)
>   at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:762)
>   at 
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:692)
>   at 
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:226)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:970)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The logs from the locator, when using {{log-level=fine}} show the following:
> {noformat}
> [fine 2018/04/03 15:24:40.501 IST locator1  
> tid=0x51] Exception occurred on remote member while executing Function: 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction
> java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
>

[jira] [Commented] (GEODE-4991) JDBC connector should not hard code quotes around identifiers in SQL statements

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4991:


Commit 3efb4da0fb79ad418e0b463e31dd31b23788696b in geode's branch 
refs/heads/feature/GEODE-4791 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3efb4da ]

GEODE-4991: do no use hard coded quotes (#1728)

java.sql.DatabaseMetaData.getIdentifierQuoteString is now used when quoting 
identifiers.
If this method returns null, an empty string, or a string with all spaces then 
no quoting will be done.


> JDBC connector should not hard code quotes around identifiers in SQL 
> statements
> ---
>
> Key: GEODE-4991
> URL: https://issues.apache.org/jira/browse/GEODE-4991
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently the JDBC connector has double quotes around all identifiers in SQL 
> statements it creates.
> Instead of always using double quotes, it should instead ask JDBC using 
> java.sql.DatabaseMetaData.getIdentifierQuoteString() what the quote string is 
> and use that.
> For databases that do not support quoting identifiers a space is returned.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4791:


Commit 38fad9860c236160499ce8faa4a722099bf09190 in geode's branch 
refs/heads/feature/GEODE-4791 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=38fad98 ]

GEODE-4791: fixing extensions module project name references


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4942) Secondary Gateway Sender queue after GII might leave some event un-drained

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4942:


Commit 26f976b12637b64f34d0c58833e094fce56e in geode's branch 
refs/heads/feature/GEODE-4791 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=26f976b ]

Revert "GEODE-4942: when sender is starting, and not running yet, put event at 
primary should be saved for QueueRemovalMessage (#1740)"

This reverts commit e42ebec32518c014ab6bd3ffe6d1ee3cab813762.
Due to acceptance test failed after merge. Need to double check the merge.


> Secondary Gateway Sender queue after GII might leave some event un-drained
> --
>
> Key: GEODE-4942
> URL: https://issues.apache.org/jira/browse/GEODE-4942
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> We found this problem in #49196. It has been fixed several times. I just 
> reproduced another scenario via 
> ParallelGatewaySenderOperationsDUnitTest.
> testParallelPropagationSenderStartAfterStop_Scenario2.
> The test did not check the drain of secondary queue, if added the checking. 
> sometime it will fail with some event stay in secondary queue forever. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4915) ClusterConfigLocatorRestartDUnitTest fails intermittently

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4915:


Commit 84b823908461a69dc6e020de3e937ccde771568b in geode's branch 
refs/heads/feature/GEODE-4791 from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=84b8239 ]

GEODE-4915: Ignore the 'for testing' exception (#1752)

* GEODE-4915: Ignore the 'for testing' exception

> ClusterConfigLocatorRestartDUnitTest fails intermittently
> -
>
> Key: GEODE-4915
> URL: https://issues.apache.org/jira/browse/GEODE-4915
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Reporter: Jens Deppe
>Assignee: Kenneth Howe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> This test has timing issues and needs to be more robust.
> Adding test name and failure details from 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/254
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects 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 1217
> [fatal 2018/04/06 05:00:39.119 UTC  172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516> 
> tid=0x65] Uncaught exception in thread Thread[P2P message reader for 
> 172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516,10,P2P 
> Reader Threads]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: 
> org.apache.geode.ForcedDisconnectException: for testing
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services$Stopper.generateCancelledException(Services.java:402)
>   at 
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
>   at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.remove(GMSJoinLeave.java:1645)
>   at 
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.inlineCheckIfAvailable(GMSHealthMonitor.java:1328)
>   at 
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:616)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.verifyMember(GMSMembershipManager.java:1674)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.suspectMember(GMSMembershipManager.java:1657)
>   at 
> org.apache.geode.internal.tcp.Connection.initiateSuspicionIfSharedUnordered(Connection.java:1917)
>   at org.apache.geode.internal.tcp.Connection.run(Connection.java:1697)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5027) Bump version to 1.6.0

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5027:


Commit b34f73c5baa17c398dcb16d637154f7e0f0fb2e5 in geode's branch 
refs/heads/feature/GEODE-4791 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b34f73c ]

GEODE-5027 Bump version to 1.6.0 and add v1.5.0 for testing

Reducing the amount of servers or locators in a number of 
RollingUpgradeDUnitTest
methods and accelerating the startup of the initial locators in clusters
created by the test.

This reduces the runtime of the test from 14 minutes to 9 minutes


> Bump version to 1.6.0
> -
>
> Key: GEODE-5027
> URL: https://issues.apache.org/jira/browse/GEODE-5027
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> Bump the version to 1.6.0 and add 1.5.0 as an "old version" for backward 
> compatibility tests.
> Also clean up the CommandInitializer tables.  We're creating a new table for 
> every version even when there are no messaging changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4915) ClusterConfigLocatorRestartDUnitTest fails intermittently

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4915:


Commit 84b823908461a69dc6e020de3e937ccde771568b in geode's branch 
refs/heads/feature/GEODE-4791 from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=84b8239 ]

GEODE-4915: Ignore the 'for testing' exception (#1752)

* GEODE-4915: Ignore the 'for testing' exception

> ClusterConfigLocatorRestartDUnitTest fails intermittently
> -
>
> Key: GEODE-4915
> URL: https://issues.apache.org/jira/browse/GEODE-4915
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Reporter: Jens Deppe
>Assignee: Kenneth Howe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> This test has timing issues and needs to be more robust.
> Adding test name and failure details from 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/254
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects 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 1217
> [fatal 2018/04/06 05:00:39.119 UTC  172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516> 
> tid=0x65] Uncaught exception in thread Thread[P2P message reader for 
> 172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516,10,P2P 
> Reader Threads]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: 
> org.apache.geode.ForcedDisconnectException: for testing
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services$Stopper.generateCancelledException(Services.java:402)
>   at 
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
>   at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.remove(GMSJoinLeave.java:1645)
>   at 
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.inlineCheckIfAvailable(GMSHealthMonitor.java:1328)
>   at 
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:616)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.verifyMember(GMSMembershipManager.java:1674)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.suspectMember(GMSMembershipManager.java:1657)
>   at 
> org.apache.geode.internal.tcp.Connection.initiateSuspicionIfSharedUnordered(Connection.java:1917)
>   at org.apache.geode.internal.tcp.Connection.run(Connection.java:1697)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5085) authentication failure when auto-reconnecting

2018-04-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated GEODE-5085:
--
Labels: pull-request-available  (was: )

> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
>  Issue Type: Bug
>  Components: membership, security
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() 
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to 
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
>   @Override
>   public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
>   dsProperties = new Properties();
>   dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
>   dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
>   dsProperties.put(DISABLE_AUTO_RECONNECT, "false");
>   dsProperties.put(ENABLE_CLUSTER_CONFIGURATION, "false");
>   dsProperties.put(LOCATORS, "localHost[" + locatorPort + "]");
>   dsProperties.put(MCAST_PORT, "0");
>   dsProperties.put(MEMBER_TIMEOUT, "1000");
>   dsProperties.put(LOG_LEVEL, LogWriterUtils.getDUnitLogLevel());
>   dsProperties.put(SECURITY_MANAGER, 
> SimpleSecurityManager.class.getName());
>   dsProperties.put("security-username", "clusterManage");
>   dsProperties.put("security-password", "clusterManage");
>   addDSProps(dsProperties);
> }
> return dsProperties;
>   }
> {code}



--

[jira] [Commented] (GEODE-5085) authentication failure when auto-reconnecting

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5085:


Commit 75ccfede2e559596cd6e0aedcf4b7e181e954920 in geode's branch 
refs/heads/feature/GEODE-5085 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=75ccfed ]

GEODE-5085 authentication failure when auto-reconnecting

Added DistributionConfig security properties to the props used to reconnect
to the distributed system.

Modified the getSecurityProps implementation to stop sharing the internal
state of the configuration object and to convert values into external form.
Security-log-level, for instance, was a number instead of the corresponding
level name.

Added a security manager to all of the ReconnectDUnitTest test cases.


> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
>  Issue Type: Bug
>  Components: membership, security
>Reporter: Bruce Schuchardt
>Priority: Major
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() 
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to 
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
>   @Override
>   public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
>   dsProperties = new Properties();
>   dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
>   dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
>

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4791:


Commit 22905ee4bac13664bf7ea9e01445aa765248e552 in geode's branch 
refs/heads/feature/GEODE-4791 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=22905ee ]

GEODE-4791: WIP


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4791) Increase gradle version from 3.5.1 to 4.51

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4791:


Commit 9c60b5ff7fb49e235f4a19e6fff241ccfb5be888 in geode's branch 
refs/heads/feature/GEODE-4791 from [~ukohlmeyer]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9c60b5f ]

GEODE-4791: fixing extensions module project name references


> Increase gradle version from 3.5.1 to 4.51
> --
>
> Key: GEODE-4791
> URL: https://issues.apache.org/jira/browse/GEODE-4791
> Project: Geode
>  Issue Type: Improvement
>  Components: build, general
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5068:


Commit 82092e83725bf9b879256dfd46de25fdbdc38266 in geode's branch 
refs/heads/feature/GEODE-4647 from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82092e8 ]

GEODE-5068: bump Jackson version. (#1796)

GEODE-5068: bump Jackson version to 2.9.5.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5057) Remove 'experimental' from JDBC Connector code

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5057:


Commit 4e249f7c2f834a056a85b14de8728bce60d73e27 in geode's branch 
refs/heads/feature/GEODE-4647 from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e249f7 ]

GEODE-5057: Removed experimental tag from Jdbc connector code base (#1789)

* GEODE-5057: Removed experimental tag from Jdbc connector 



> Remove 'experimental' from JDBC Connector code
> --
>
> Key: GEODE-5057
> URL: https://issues.apache.org/jira/browse/GEODE-5057
> Project: Geode
>  Issue Type: Task
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Remove 'experimental' from JDBC Connector code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4955:


Commit 5707de5e0edea1ae94b1f5c99d62b2fb6700f0d2 in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5707de5 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core module tests (#1788)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4955:


Commit 50573481dd71d40d9d441fb313906611b3605fb2 in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5057348 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core (#1786)



> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4384) gfsh command to destroy jndi binding

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4384:


Commit ac7db5b2950af134233c976b3f63f3e48e8d3fb9 in geode's branch 
refs/heads/feature/GEODE-4647 from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ac7db5b ]

GEODE-4384 Add docs for gfsh destroy jndi-binding command (#1780)



> gfsh command to destroy jndi binding
> 
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy 
> jndi-binding --name=jndi-binding-name}}
>  Then the datasource will be deleted from the cluster and the binding will be 
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4863) refactor jdbc commands to use this public api

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4863:


Commit 4bc6c5a9b9abe9cf0e3c8e68802262efcdb9c735 in geode's branch 
refs/heads/feature/GEODE-4647 from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4bc6c5a ]

GEODE-4863: refactor jdbc commands to use this public cluster configuration api 
(#1802)

   fix a NullPointer in CCService.getCustomCacheElement

> refactor jdbc commands to use this public api
> -
>
> Key: GEODE-4863
> URL: https://issues.apache.org/jira/browse/GEODE-4863
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> they will need to create a custom config object based on their own xsd.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5069) Reduce direct exposure of GfJsonObject from CommandResult

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5069:


Commit b52492c43de7d220a90c9cd914ef710ab331546e in geode's branch 
refs/heads/feature/GEODE-4647 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b52492c ]

GEODE-5069: Reduce direct exposure of GfJsonObject from CommandResult (#1795)

- Methods getGfJsonObject() and getTableContent() are now private.
- getContent() is still public but only used by CommandResponseBuilder. This
  will change in subsequent PRs.

> Reduce direct exposure of GfJsonObject from CommandResult
> -
>
> Key: GEODE-5069
> URL: https://issues.apache.org/jira/browse/GEODE-5069
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5057) Remove 'experimental' from JDBC Connector code

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5057:


Commit 4e249f7c2f834a056a85b14de8728bce60d73e27 in geode's branch 
refs/heads/feature/GEODE-4647 from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e249f7 ]

GEODE-5057: Removed experimental tag from Jdbc connector code base (#1789)

* GEODE-5057: Removed experimental tag from Jdbc connector 



> Remove 'experimental' from JDBC Connector code
> --
>
> Key: GEODE-5057
> URL: https://issues.apache.org/jira/browse/GEODE-5057
> Project: Geode
>  Issue Type: Task
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Remove 'experimental' from JDBC Connector code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4647:


Commit 613aae452a8e3067bd85a77fdfce6b963b9e23e3 in geode's branch 
refs/heads/feature/GEODE-4647 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=613aae4 ]

GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary
gateway sender queue


> Add a new stat for AyncEventQueue/GatewaySender to track 
> secondaryEventsQueueSize
> -
>
> Key: GEODE-4647
> URL: https://issues.apache.org/jira/browse/GEODE-4647
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Jason Huynh
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Currently we have eventsQueueSize which tells us how big the queue is based 
> on how many primary events are in the queue.
> It would be nice to have the same type of stat for how many secondary events 
> are in the queue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4954:


Commit 50573481dd71d40d9d441fb313906611b3605fb2 in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5057348 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  
geode-core (#1786)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-3926) Lucene Query should throw an exception while lucene index is being built on existing region

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3926:


Commit 83c667b12c510f7a10aca57179b9e61f29cfddbb in geode's branch 
refs/heads/feature/GEODE-4647 from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=83c667b ]

GEODE-3926: Catching exception from lucene query computing thread (#1774)



> Lucene Query should throw an exception while lucene index is being built on 
> existing region
> ---
>
> Key: GEODE-3926
> URL: https://issues.apache.org/jira/browse/GEODE-3926
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> When GEODE-3928 is complete, we will have a process to index existing data in 
> a region when a lucene index is added. That process may take some time. While 
> indexing is going on queries should not block for a long period of time or 
> return incorrect results. Instead the query should throw an exception 
> indicating that the index does not exist/is not built yet.
> Acceptance:
> Queries executed while indexing is going on throw an exception, rather than 
> blocking or returning incorrect results.
> Implementation Details:
> GEODE-3928 is about modifying computeRepository to actually do the indexing. 
> Queries also call compute repository, so they will block until 
> computeRepository is done.
> To avoid blocking, we can make  computeRepo to return an IndexRepository in 
> an "building" state. That index repo could contain an asynchronous task that 
> is actually indexing the data. Until the asynchronous task is complete, the 
> IndexRepostory could throw exceptions from query operations. This has the 
> advantage of making sure that whenever computeRepository is called, we always 
> at least start or make sure there is a task running to index the data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4954:


Commit 5707de5e0edea1ae94b1f5c99d62b2fb6700f0d2 in geode's branch 
refs/heads/feature/GEODE-4647 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5707de5 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  non 
geode-core module tests (#1788)



> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5068:


Commit 82092e83725bf9b879256dfd46de25fdbdc38266 in geode's branch 
refs/heads/feature/GEODE-4647 from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82092e8 ]

GEODE-5068: bump Jackson version. (#1796)

GEODE-5068: bump Jackson version to 2.9.5.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4410) DistributedSystem has public method to get internal class StatisticsManager

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-4410:


Commit e8b9cb1beb91cf93d0c317c7e358ebb5533ee80d in geode-native's branch 
refs/heads/develop from [~mmartell]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e8b9cb1 ]

GEODE-4410: Move StatisticsManager from DistributedSystem to Cache. (#273)



> DistributedSystem has public method to get internal class StatisticsManager
> ---
>
> Key: GEODE-4410
> URL: https://issues.apache.org/jira/browse/GEODE-4410
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4842) Remove Cache parameter from PoolFactory::Create in clicache

2018-04-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated GEODE-4842:
--
Labels: pull-request-available  (was: )

> Remove Cache parameter from PoolFactory::Create in clicache
> ---
>
> Key: GEODE-4842
> URL: https://issues.apache.org/jira/browse/GEODE-4842
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Priority: Major
>  Labels: pull-request-available
>
> PoolFactory::Create in clicache takes a Cache parameter which is _completely 
> unused_. This parameter should simply be removed from the API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-5067) Failed dynamic_cast when visibility is set to hidden on Clang

2018-04-16 Thread Ryan McMahon (JIRA)


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

Ryan McMahon resolved GEODE-5067.
-
Resolution: Fixed

> Failed dynamic_cast when visibility is set to hidden on Clang
> -
>
> Key: GEODE-5067
> URL: https://issues.apache.org/jira/browse/GEODE-5067
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The testThinClientBigValue test is failing due to issues with Clang and the 
> cmake 'CXX_VISIBILITY_PRESET hidden' setting.  It appears Clang does not 
> propagate visibility attributes through using statements i.e.
> ```
> using CacheableBytes = CacheableArray;
> ```
> Despite CacheableArray and its base class Serializable being decorated with 
> APACHE_GEODE_EXPORT, dynamic_casts appear to fail. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4920) Alter region does not update PartitionRegionConfig of the region

2018-04-16 Thread nabarun (JIRA)


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

nabarun commented on GEODE-4920:


[~dschneider][~klund] Also we tried to copy the 
getPRConfigWithLatestExpirationAttributes for mutating the the PRConfig for 
GEODE-4919,  we created a new PartitionRegionConfig as shown in 
getPRConfigWithLatestExpirationAttributes and called updatePRConfig for that 
region.

Doing this removes all the 
{noformat}
  /** Nodes participating in this PartitionedRegion */
  private VersionedArrayList nodes = null;
{noformat}

as we create a new PRConfig. This will result in hung rebalance operations, 
adding new queues etc. 



> Alter region does not update PartitionRegionConfig of the region
> 
>
> Key: GEODE-4920
> URL: https://issues.apache.org/jira/browse/GEODE-4920
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, regions
>Reporter: nabarun
>Priority: Major
>
> While using the "alter region" gfsh command to update / mutate the region 
> with new attributes like eviction parameters, the new attributes are not 
> updated in the PartitionedRegionConfig.
> This maybe important because PartitionRegionConfig members are used to 
> determine colocation complete, validation of the gatewaySenders etc.
> GEODE-4919 PR has been raised to add the gateways senders to the PR config.
> We need to determine which command parameters of "alter region" command need 
> to be updated to the PRConfig after the region is altered



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5086) Clarify Java 8 (not 9) requirement in docs

2018-04-16 Thread Karen Smoler Miller (JIRA)

Karen Smoler Miller created GEODE-5086:
--

 Summary: Clarify Java 8 (not 9) requirement in docs
 Key: GEODE-5086
 URL: https://issues.apache.org/jira/browse/GEODE-5086
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Our docs state that Geode works with Java 8 an above.  That would imply Java 9, 
and we don't work with Java 9.  So, clarify the docs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5085) authentication failure when auto-reconnecting

2018-04-16 Thread Bruce Schuchardt (JIRA)

Bruce Schuchardt created GEODE-5085:
---

 Summary: authentication failure when auto-reconnecting
 Key: GEODE-5085
 URL: https://issues.apache.org/jira/browse/GEODE-5085
 Project: Geode
  Issue Type: Bug
  Components: membership, security
Reporter: Bruce Schuchardt


I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() and 
got a failure to authenticate during the reconnect attempt.

{noformat}
[vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
occurred while trying to connect the system during reconnect
[vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to find 
credentials from [10.118.20.59(16110:locator):32770]
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
[vm3]   at 
org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
[vm3]   at 
org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
[vm3]   at 
org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
[vm3]   at 
org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
[vm3]   at 
org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
[vm3]   at 
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
[vm3]   at 
org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
[vm3]   at 
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
[vm3]   at java.lang.Thread.run(Thread.java:748)
{noformat}

The security manager settings were added to getDistributedSystemProperties():

{code}
  @Override
  public Properties getDistributedSystemProperties() {
if (dsProperties == null) {
  dsProperties = new Properties();
  dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
  dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
  dsProperties.put(DISABLE_AUTO_RECONNECT, "false");
  dsProperties.put(ENABLE_CLUSTER_CONFIGURATION, "false");
  dsProperties.put(LOCATORS, "localHost[" + locatorPort + "]");
  dsProperties.put(MCAST_PORT, "0");
  dsProperties.put(MEMBER_TIMEOUT, "1000");
  dsProperties.put(LOG_LEVEL, LogWriterUtils.getDUnitLogLevel());
  dsProperties.put(SECURITY_MANAGER, SimpleSecurityManager.class.getName());
  dsProperties.put("security-username", "clusterManage");
  dsProperties.put("security-password", "clusterManage");
  addDSProps(dsProperties);
}
return dsProperties;
  }
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool

2018-04-16 Thread John Blum (JIRA)


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

John Blum commented on GEODE-5081:
--

[~bschuchardt]- there is no *public* {{ClientCacheFactory.getPoolFactory()}} 
method that users can access.  That 
[method|https://github.com/apache/geode/blob/rel/v1.5.0/geode-core/src/main/java/org/apache/geode/cache/client/ClientCacheFactory.java#L265]
 is *private*.

> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property 
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}} 
> configuration property when 
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
>  a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class.  The 
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried 
> using the {{o.a.g.cache.client.Pool's}} [property 
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to 
> the 
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
>  when configuring the "DEFAULT" _Pool_, i.e. there is no 
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5057) Remove 'experimental' from JDBC Connector code

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5057:


Commit 4e249f7c2f834a056a85b14de8728bce60d73e27 in geode's branch 
refs/heads/develop from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e249f7 ]

GEODE-5057: Removed experimental tag from Jdbc connector code base (#1789)

* GEODE-5057: Removed experimental tag from Jdbc connector 



> Remove 'experimental' from JDBC Connector code
> --
>
> Key: GEODE-5057
> URL: https://issues.apache.org/jira/browse/GEODE-5057
> Project: Geode
>  Issue Type: Task
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Remove 'experimental' from JDBC Connector code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5057) Remove 'experimental' from JDBC Connector code

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5057:


Commit 4e249f7c2f834a056a85b14de8728bce60d73e27 in geode's branch 
refs/heads/develop from [~agingade]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e249f7 ]

GEODE-5057: Removed experimental tag from Jdbc connector code base (#1789)

* GEODE-5057: Removed experimental tag from Jdbc connector 



> Remove 'experimental' from JDBC Connector code
> --
>
> Key: GEODE-5057
> URL: https://issues.apache.org/jira/browse/GEODE-5057
> Project: Geode
>  Issue Type: Task
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Remove 'experimental' from JDBC Connector code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated GEODE-5080:
--
Labels: pull-request-available  (was: )

> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>   at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
>

[jira] [Updated] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread Jens Deppe (JIRA)


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

Jens Deppe updated GEODE-5080:
--
Labels:   (was: ci)

> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>   at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>

[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException

2018-04-16 Thread Eric Shu (JIRA)


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

Eric Shu updated GEODE-5046:

Affects Version/s: (was: 1.6.0)

> RemotePutMessage.distribute should handle RegionDestoryedException
> --
>
> Key: GEODE-5046
> URL: https://issues.apache.org/jira/browse/GEODE-5046
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> RemotePutMessage.distribute() tries to get a version tag from a remote member 
> in a loop. It tries another member if one member failed. 
> It is possible that a region is destroyed on a member, and the method should 
> handle it and retry to another member instead of failing the operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException

2018-04-16 Thread Eric Shu (JIRA)


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

Eric Shu updated GEODE-5046:

Fix Version/s: (was: 1.7.0)
   1.6.0

> RemotePutMessage.distribute should handle RegionDestoryedException
> --
>
> Key: GEODE-5046
> URL: https://issues.apache.org/jira/browse/GEODE-5046
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> RemotePutMessage.distribute() tries to get a version tag from a remote member 
> in a loop. It tries another member if one member failed. 
> It is possible that a region is destroyed on a member, and the method should 
> handle it and retry to another member instead of failing the operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5081:


Commit 948ca6038cddda8381c61598a96c9fa8ded78d27 in geode's branch 
refs/heads/feature/GEODE-5081 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=948ca60 ]

GEODE-5081 ClientCacheFactory is missing the 
setPoolSubscriptionTimeoutMultiplier()

Added the missing method & a test for it


> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property 
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}} 
> configuration property when 
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
>  a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class.  The 
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried 
> using the {{o.a.g.cache.client.Pool's}} [property 
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to 
> the 
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
>  when configuring the "DEFAULT" _Pool_, i.e. there is no 
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4897) Availability is wrong on some commands.

2018-04-16 Thread Barbara Pruijn (JIRA)


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

Barbara Pruijn resolved GEODE-4897.
---
Resolution: Duplicate

https://issues.apache.org/jira/browse/GEODE-5048

> Availability is wrong on some commands.
> ---
>
> Key: GEODE-4897
> URL: https://issues.apache.org/jira/browse/GEODE-4897
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Priority: Major
>
> For example, look at any JDBC connector commands or ListJndiBindingCommand 
> and could be more. When you launch gfsh (and not connected) then you can see 
> these commands are available.
> {noformat}
> create jdbc-connection (Available)
> (Experimental) Create a connection for communicating with a database through 
> jdbc.
> create jdbc-mapping (Available)
> (Experimental) Create a mapping for a region for use with a JDBC database 
> connection.{noformat}
> {{There is a test to test the availability marker but the test itself has a 
> bug due to which the command authors are not warned about the marker. Look 
> into CommandAvailabilityIndicatorTest}}
> {noformat}
> if (cliMetaData != null && !cliMetaData.shellOnly()) -> here cliMetaData 
> could be null if the command author forget to annotate the command.{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5048) Availability Indicator for "list jndi-bindings", "list jdbc-connections" and "list jdbc-mappings" are wrong

2018-04-16 Thread Barbara Pruijn (JIRA)


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

Barbara Pruijn updated GEODE-5048:
--
Fix Version/s: 1.7.0

> Availability Indicator for "list jndi-bindings", "list jdbc-connections" and 
> "list jdbc-mappings" are wrong
> ---
>
> Key: GEODE-5048
> URL: https://issues.apache.org/jira/browse/GEODE-5048
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> those commands, when not connected to a locator, should be listed as "not 
> available" in gfsh help, but they are listed as "available".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4897) Availability is wrong on some commands.

2018-04-16 Thread Barbara Pruijn (JIRA)


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

Barbara Pruijn updated GEODE-4897:
--
Fix Version/s: 1.7.0

> Availability is wrong on some commands.
> ---
>
> Key: GEODE-4897
> URL: https://issues.apache.org/jira/browse/GEODE-4897
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Priority: Major
> Fix For: 1.7.0
>
>
> For example, look at any JDBC connector commands or ListJndiBindingCommand 
> and could be more. When you launch gfsh (and not connected) then you can see 
> these commands are available.
> {noformat}
> create jdbc-connection (Available)
> (Experimental) Create a connection for communicating with a database through 
> jdbc.
> create jdbc-mapping (Available)
> (Experimental) Create a mapping for a region for use with a JDBC database 
> connection.{noformat}
> {{There is a test to test the availability marker but the test itself has a 
> bug due to which the command authors are not warned about the marker. Look 
> into CommandAvailabilityIndicatorTest}}
> {noformat}
> if (cliMetaData != null && !cliMetaData.shellOnly()) -> here cliMetaData 
> could be null if the command author forget to annotate the command.{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread Jens Deppe (JIRA)


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

Jens Deppe updated GEODE-5080:
--
Component/s: (was: management)

> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: ci
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>   at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
>

[jira] [Commented] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5046:


Commit e6e820df0caca4bfc5369725c2bff0cb2c6381f2 in geode's branch 
refs/heads/release/1.6.0 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6e820d ]

GEODE-5046: Handle RegionDestroyedException in RemotePutMessage to re… (#1773)

   cherry-pick 2203273307a8695dafc3b617cac9979ff0305f9b


> RemotePutMessage.distribute should handle RegionDestoryedException
> --
>
> Key: GEODE-5046
> URL: https://issues.apache.org/jira/browse/GEODE-5046
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0, 1.6.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> RemotePutMessage.distribute() tries to get a version tag from a remote member 
> in a loop. It tries another member if one member failed. 
> It is possible that a region is destroyed on a member, and the method should 
> handle it and retry to another member instead of failing the operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread Jens Deppe (JIRA)


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

Jens Deppe reassigned GEODE-5080:
-

Assignee: Jens Deppe

> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: ci
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>   at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
>

[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5068:


Commit 7dcc313271fc4e58fdee6f6994b32b5b17500d74 in geode's branch 
refs/heads/release/1.6.0 from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7dcc313 ]

GEODE-5068: bump Jackson version. (#1796) (#1801)

GEODE-5068: bump Jackson version to 2.9.5.

> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5068:


Commit 7dcc313271fc4e58fdee6f6994b32b5b17500d74 in geode's branch 
refs/heads/release/1.6.0 from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7dcc313 ]

GEODE-5068: bump Jackson version. (#1796) (#1801)

GEODE-5068: bump Jackson version to 2.9.5.

> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4936) Update version dependency for jackson-databind

2018-04-16 Thread Kenneth Howe (JIRA)


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

Kenneth Howe resolved GEODE-4936.
-
   Resolution: Duplicate
Fix Version/s: 1.6.0

> Update version dependency for jackson-databind
> --
>
> Key: GEODE-4936
> URL: https://issues.apache.org/jira/browse/GEODE-4936
> Project: Geode
>  Issue Type: Bug
>  Components: build, pulse
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Priority: Major
> Fix For: 1.6.0
>
>
> jackson-databind version 2.9.5 fixes an incomplete fix in version 2.9.4



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool

2018-04-16 Thread Bruce Schuchardt (JIRA)


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

Bruce Schuchardt commented on GEODE-5081:
-

I'll add  the missing method.  Meanwhile you can use 
ClientCacheFactory.getPoolFactory().setSubscriptionTimeoutMultiplier(int) 

> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property 
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}} 
> configuration property when 
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
>  a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class.  The 
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried 
> using the {{o.a.g.cache.client.Pool's}} [property 
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to 
> the 
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
>  when configuring the "DEFAULT" _Pool_, i.e. there is no 
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5064) Remove unused code and if clause that does not get thrown

2018-04-16 Thread Jason Huynh (JIRA)


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

Jason Huynh updated GEODE-5064:
---
Fix Version/s: 1.6.0

> Remove unused code and if clause that does not get thrown
> -
>
> Key: GEODE-5064
> URL: https://issues.apache.org/jira/browse/GEODE-5064
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There appears to be an exception that should be thrown, but upon futher 
> inspection, this clause can never be hit because the boolean it checks is 
> never set to true;
>  
> In LocalRegion:
> logger.info("Failed to create index {} on region {} with exception: {}",
>  icd.getIndexName(), this.getFullPath(), ex);
> // Check if the region index creation is from cache.xml, in that case throw 
> exception.
> // Other case is when bucket regions are created dynamically, in that case 
> ignore the
> // exception.
> if (internalRegionArgs.getDeclarativeIndexCreation()) {
>  throw new 
> InternalGemFireError(LocalizedStrings.GemFireCache_INDEX_CREATION_EXCEPTION_1
>  .toLocalizedString(icd.getIndexName(), this.getFullPath()), ex);
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool

2018-04-16 Thread Bruce Schuchardt (JIRA)


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

Bruce Schuchardt reassigned GEODE-5081:
---

Assignee: Bruce Schuchardt

> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property 
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}} 
> configuration property when 
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
>  a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class.  The 
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried 
> using the {{o.a.g.cache.client.Pool's}} [property 
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to 
> the 
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
>  when configuring the "DEFAULT" _Pool_, i.e. there is no 
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5084) Create index command with --member option would update cluster configuration

2018-04-16 Thread Jinmei Liao (JIRA)

Jinmei Liao created GEODE-5084:
--

 Summary: Create index command with --member option would update 
cluster configuration
 Key: GEODE-5084
 URL: https://issues.apache.org/jira/browse/GEODE-5084
 Project: Geode
  Issue Type: Bug
  Components: gfsh
Reporter: Jinmei Liao


executing "create index --member=xyz" command would end up updating the cluster 
configuration for the entire cluster, but the command is meant to affect only 
one member only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5083) Alter region --name option no longer auto completes

2018-04-16 Thread Jinmei Liao (JIRA)


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

Jinmei Liao updated GEODE-5083:
---
Labels: quick_to_fix  (was: )

> Alter region --name option no longer auto completes
> ---
>
> Key: GEODE-5083
> URL: https://issues.apache.org/jira/browse/GEODE-5083
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: quick_to_fix
>
> when "alter region --name=" is typed, tabbing should show a list of available 
> regions



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5083) Alter region --name option no longer auto completes

2018-04-16 Thread Jinmei Liao (JIRA)

Jinmei Liao created GEODE-5083:
--

 Summary: Alter region --name option no longer auto completes
 Key: GEODE-5083
 URL: https://issues.apache.org/jira/browse/GEODE-5083
 Project: Geode
  Issue Type: Bug
  Components: gfsh
Reporter: Jinmei Liao


when "alter region --name=" is typed, tabbing should show a list of available 
regions



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5080) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects

2018-04-16 Thread Barbara Pruijn (JIRA)


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

Barbara Pruijn updated GEODE-5080:
--
Labels: ci  (was: )

> CI Failure: 
> ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects
> -
>
> Key: GEODE-5080
> URL: https://issues.apache.org/jira/browse/GEODE-5080
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Jens Deppe
>Priority: Major
>  Labels: ci
>
> This test intermittently fails with with following:
> {noformat}
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest
>  > serverRestartsAfterLocatorReconnects FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/761947362.call
>  in VM 3 running on Host b669312074c0 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:203)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:196)
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:182)
> at 
> org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:65)
> Caused by:
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {noformat}
> The detailed test failure shows the following cause:
> {noformat}
> Caused by: org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:661)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
>   at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:172)
>   at 
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:78)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$a2926408$1(ClusterStartupRule.java:212)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>   at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
>

[jira] [Commented] (GEODE-5069) Reduce direct exposure of GfJsonObject from CommandResult

2018-04-16 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-5069:


Commit b52492c43de7d220a90c9cd914ef710ab331546e in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b52492c ]

GEODE-5069: Reduce direct exposure of GfJsonObject from CommandResult (#1795)

- Methods getGfJsonObject() and getTableContent() are now private.
- getContent() is still public but only used by CommandResponseBuilder. This
  will change in subsequent PRs.

> Reduce direct exposure of GfJsonObject from CommandResult
> -
>
> Key: GEODE-5069
> URL: https://issues.apache.org/jira/browse/GEODE-5069
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4990) Race Condition When Using Cluster Configuration Service

2018-04-16 Thread JIRA


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

Juan José Ramos Cassella resolved GEODE-4990.
-
   Resolution: Fixed
Fix Version/s: 1.6.0

> Race Condition When Using Cluster Configuration Service
> ---
>
> Key: GEODE-4990
> URL: https://issues.apache.org/jira/browse/GEODE-4990
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, locator
>Affects Versions: 1.4.0
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> There's a small window of time on which the locator 
> ({{enable-cluster-configuration=true}}) is receiving TCP requests from 
> starting up servers ({{use-cluster-configuration=true}}) but the cluster 
> configuration service is not yet fully loaded, because of this the servers 
> fail to startup and throw the following exception:
> {noformat}
> Exception in thread "main" org.apache.geode.cache.execute.FunctionException: 
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.execute.FunctionStreamingResultCollector.getResult(FunctionStreamingResultCollector.java:232)
>   at 
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:285)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1036)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:835)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:775)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:764)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:175)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:222)
>   at 
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
>   at 
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:844)
>   at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:762)
>   at 
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:692)
>   at 
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:226)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:970)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The logs from the locator, when using {{log-level=fine}} show the following:
> {noformat}
> [fine 2018/04/03 15:24:40.501 IST locator1  
> tid=0x51] Exception occurred on remote member while executing Function: 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction
> java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>

84 matches

Mail list logo