[jira] [Updated] (GEODE-1904) start server should skip assertAvailablePort if --cache-xml is specified when --server-port is not specified

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1904:
-
Assignee: Swapnil Bawaskar

> start server should skip assertAvailablePort if --cache-xml is specified when 
> --server-port is not specified
> 
>
> Key: GEODE-1904
> URL: https://issues.apache.org/jira/browse/GEODE-1904
> Project: Geode
>  Issue Type: Wish
>  Components: management
>Reporter: Kirk Lund
>Assignee: Swapnil Bawaskar
>
> 1) start a server with --server-port 40404
> 2) start a 2nd server without specifying --server-port or 
> --disable-default-server but do specify --cache-xml containing a unique 
> server port
> 3) start will fail due to assertAvailablePort
> The error will look something like:
> java.lang.RuntimeException: An IO error occurred while starting a Server in 
> /dx2-office-dhcp32 on dx2-office-dhcp32[40404]: Network is unreachable; port 
> (40404) is not available on localhost.
> Work-around is to specify --disable-default-server in step #2. This will 
> cause it to skip assertAvailablePort(40404).
> I believe it's more intuitive to the user if we also make the change to skip 
> assertAvailablePort(40404) if --cache-xml is specified when --server-port is 
> not  specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1904) start server should skip assertAvailablePort if --cache-xml is specified when --server-port is not specified

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-1904:


 Summary: start server should skip assertAvailablePort if 
--cache-xml is specified when --server-port is not specified
 Key: GEODE-1904
 URL: https://issues.apache.org/jira/browse/GEODE-1904
 Project: Geode
  Issue Type: Wish
  Components: management
Reporter: Kirk Lund


1) start a server with --server-port 40404
2) start a 2nd server without specifying --server-port or 
--disable-default-server but do specify --cache-xml containing a unique server 
port
3) start will fail due to assertAvailablePort

The error will look something like:

java.lang.RuntimeException: An IO error occurred while starting a Server in 
/dx2-office-dhcp32 on dx2-office-dhcp32[40404]: Network is unreachable; port 
(40404) is not available on localhost.

Work-around is to specify --disable-default-server in step #2. This will cause 
it to skip assertAvailablePort(40404).

I believe it's more intuitive to the user if we also make the change to skip 
assertAvailablePort(40404) if --cache-xml is specified when --server-port is 
not  specified.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1903) Update Website Community > Events

[Joey McAllister (JIRA)]

Joey McAllister created GEODE-1903:
--

 Summary: Update Website Community > Events
 Key: GEODE-1903
 URL: https://issues.apache.org/jira/browse/GEODE-1903
 Project: Geode
  Issue Type: Task
  Components: general
Reporter: Joey McAllister


Remove outdated entries; add:

Geode Clubhouse: DDD, Reactor Programming and Apache Geode Panel wth Vaughn
Vernon
Virtual | Calendar entry

9/21 - 9AM Pacific

Geode Clubhouse: Update on Geode's New Security Infrastructure with Jinmei
Liao
Virtual | Calendar entry

10/19 - 9AM Pacific



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-37:
--

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

GEODE-37: fix up logging for org.apache.geode

* change BASE_LOGGER_NAME to match MAIN_LOGGER_NAME
* change various instances of gemfire to geode
* change GEMFIRE_VERBOSE to GEODE_VERBOSE


> Package renaming - com.gemstone.gemfire -> org.apache.geode
> ---
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: client/server, docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Assignee: Hitesh Khamesra
>Priority: Blocker
> Fix For: 1.0.0-incubating
>
>
> Geode packages should be renamed from com.gemstone -> org.apache.geode in 
> order to allow an easy transition from incubation to become a TLP. 
> Also, it allow the necessary work that may need to be done at the protocol 
> level in order to allow serialization/message exchange between nodes before 
> an actual release using the definitive class/package naming.
> The issue was discussed in the following thread at dev@:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-37:
--

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

GEODE-37: change com.gemstone.gemfire to org.apache.geode


> Package renaming - com.gemstone.gemfire -> org.apache.geode
> ---
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: client/server, docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Assignee: Hitesh Khamesra
>Priority: Blocker
> Fix For: 1.0.0-incubating
>
>
> Geode packages should be renamed from com.gemstone -> org.apache.geode in 
> order to allow an easy transition from incubation to become a TLP. 
> Also, it allow the necessary work that may need to be done at the protocol 
> level in order to allow serialization/message exchange between nodes before 
> an actual release using the definitive class/package naming.
> The issue was discussed in the following thread at dev@:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-1902:


 Summary: Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE 
for backwards compatibility
 Key: GEODE-1902
 URL: https://issues.apache.org/jira/browse/GEODE-1902
 Project: Geode
  Issue Type: Improvement
  Components: logging
Reporter: Kirk Lund


If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they 
either need to change this to GEODE_VERBOSE or we need to add some sort of 
alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1901) authz5_5.dtd and authz6_0.dtd files need to be cleaned up

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1901:
-
Description: 
These files refer to a dtd that's online at gemstone.com:
http://www.gemstone.com/dtd/authz5_5.dtd

The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I can't 
find authz6_0.dtd online anywhere (if that's what it's supposed to be).

This paragraph seems to be messed up:
{noformat}
The contents of a declarative XML file correspond to APIs found in the

  org.apache.geode.security.AccessControl

package. The sample implementation may be used to specify access control
policies.
{noformat}
These files also mention GemStone Systems, Inc. and GemFire (does this need to 
change?).

These files are currently checked into test resources, but they might actually 
be used by security templates/examples.


  was:
These files refer to a dtd that's online at gemstone.com:
http://www.gemstone.com/dtd/authz5_5.dtd

The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I can't 
find authz6_0.dtd online anywhere (if that's what it's supposed to be).

This paragraph seems to be messed up:
{noformat}
The contents of a declarative XML file correspond to APIs found in the

  org.apache.geode.security.AccessControl

package. The sample implementation may be used to specify access control
policies.
{noformat}
These files also mention GemStone Systems, Inc. and GemFire (does this need to 
change?).



> authz5_5.dtd and authz6_0.dtd files need to be cleaned up
> -
>
> Key: GEODE-1901
> URL: https://issues.apache.org/jira/browse/GEODE-1901
> Project: Geode
>  Issue Type: Bug
>  Components: security, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> These files refer to a dtd that's online at gemstone.com:
> http://www.gemstone.com/dtd/authz5_5.dtd
> The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I 
> can't find authz6_0.dtd online anywhere (if that's what it's supposed to be).
> This paragraph seems to be messed up:
> {noformat}
> The contents of a declarative XML file correspond to APIs found in the
>   org.apache.geode.security.AccessControl
> package. The sample implementation may be used to specify access control
> policies.
> {noformat}
> These files also mention GemStone Systems, Inc. and GemFire (does this need 
> to change?).
> These files are currently checked into test resources, but they might 
> actually be used by security templates/examples.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1901) authz5_5.dtd and authz6_0.dtd files need to be cleaned up

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1901:
-
Priority: Minor  (was: Major)

> authz5_5.dtd and authz6_0.dtd files need to be cleaned up
> -
>
> Key: GEODE-1901
> URL: https://issues.apache.org/jira/browse/GEODE-1901
> Project: Geode
>  Issue Type: Bug
>  Components: security, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> These files refer to a dtd that's online at gemstone.com:
> http://www.gemstone.com/dtd/authz5_5.dtd
> The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I 
> can't find authz6_0.dtd online anywhere (if that's what it's supposed to be).
> This paragraph seems to be messed up:
> {noformat}
> The contents of a declarative XML file correspond to APIs found in the
>   org.apache.geode.security.AccessControl
> package. The sample implementation may be used to specify access control
> policies.
> {noformat}
> These files also mention GemStone Systems, Inc. and GemFire (does this need 
> to change?).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1901) authz5_5.dtd and authz6_0.dtd files need to be cleaned up

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-1901:


Assignee: Kirk Lund

> authz5_5.dtd and authz6_0.dtd files need to be cleaned up
> -
>
> Key: GEODE-1901
> URL: https://issues.apache.org/jira/browse/GEODE-1901
> Project: Geode
>  Issue Type: Bug
>  Components: security, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> These files refer to a dtd that's online at gemstone.com:
> http://www.gemstone.com/dtd/authz5_5.dtd
> The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I 
> can't find authz6_0.dtd online anywhere (if that's what it's supposed to be).
> This paragraph seems to be messed up:
> {noformat}
> The contents of a declarative XML file correspond to APIs found in the
>   org.apache.geode.security.AccessControl
> package. The sample implementation may be used to specify access control
> policies.
> {noformat}
> These files also mention GemStone Systems, Inc. and GemFire (does this need 
> to change?).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1901) authz5_5.dtd and authz6_0.dtd files need to be cleaned up

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-1901:


 Summary: authz5_5.dtd and authz6_0.dtd files need to be cleaned up
 Key: GEODE-1901
 URL: https://issues.apache.org/jira/browse/GEODE-1901
 Project: Geode
  Issue Type: Bug
  Components: security, tests
Reporter: Kirk Lund


These files refer to a dtd that's online at gemstone.com:
http://www.gemstone.com/dtd/authz5_5.dtd

The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I can't 
find authz6_0.dtd online anywhere (if that's what it's supposed to be).

This paragraph seems to be messed up:
{noformat}
The contents of a declarative XML file correspond to APIs found in the

  org.apache.geode.security.AccessControl

package. The sample implementation may be used to specify access control
policies.
{noformat}
These files also mention GemStone Systems, Inc. and GemFire (does this need to 
change?).




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1899) Address the custom 'clean' gradle task warning

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/240


> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1899) Address the custom 'clean' gradle task warning

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1899:


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

GEODE-1899: This closes #240


> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1899) Address the custom 'clean' gradle task warning

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1899:


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

GEODE-1899: Renamed the custom 'clean' task to work with Gradle 3.0+


> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1899) Address the custom 'clean' gradle task warning

[ASF GitHub Bot (JIRA)]

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

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

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/240
  
+1


> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-599) CI Failure: DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-599:
---

Commit 67ac4de20b30975fd6e7ff8ba9a41fe665528c90 in incubator-geode's branch 
refs/heads/develop from [~gemzdude]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=67ac4de ]

GEODE-599: Remove Flaky annotation from previously failing tests

This closes #239


> CI Failure: 
> DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync
> -
>
> Key: GEODE-599
> URL: https://issues.apache.org/jira/browse/GEODE-599
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Dan Smith
>Assignee: Scott Jewell
>  Labels: CI, Flaky
>
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996
> {noformat}
> junit.framework.AssertionFailedError: region contents are not consistent 
> expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.z_versionTestClearWithConcurrentEvents(MultiVMRegionTestCase.java:8304)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestClearWithConcurrentEventsAsync(MultiVMRegionTestCase.java:8266)
>   at 
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testClearWithConcurrentEventsAsync(DistributedAckRegionCCEDUnitTest.java:296)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   

[jira] [Commented] (GEODE-599) CI Failure: DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-599:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/239


> CI Failure: 
> DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync
> -
>
> Key: GEODE-599
> URL: https://issues.apache.org/jira/browse/GEODE-599
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Dan Smith
>Assignee: Scott Jewell
>  Labels: CI, Flaky
>
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996
> {noformat}
> junit.framework.AssertionFailedError: region contents are not consistent 
> expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.z_versionTestClearWithConcurrentEvents(MultiVMRegionTestCase.java:8304)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestClearWithConcurrentEventsAsync(MultiVMRegionTestCase.java:8266)
>   at 
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testClearWithConcurrentEventsAsync(DistributedAckRegionCCEDUnitTest.java:296)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> 

[jira] [Commented] (GEODE-1648) Provide ability to disable security for some components

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1648:


Commit 45ecd4cb1f52bb151d7bd003ccb28308bf40b289 in incubator-geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=45ecd4c ]

GEODE-1648: revert commits related to security-enabled-components.

* revert this if we want to pull this back in.


> Provide ability to disable security for some components
> ---
>
> Key: GEODE-1648
> URL: https://issues.apache.org/jira/browse/GEODE-1648
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>Assignee: Kirk Lund
> Fix For: 1.0.0-incubating
>
>
> When the new {{SecurityManager}} interface is used, it will enable 
> authentication and authorization for client-server, jmx, peer-to-peer and 
> WAN. Not all users will want authentication and authorization for all these 
> components as explained in this comment: 
> https://issues.apache.org/jira/browse/GEODE-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369089#comment-15369089
> We should add new geode properties:
> {noformat}
> enable-peer-to-peer-authentication
> enable-client-server-security
> enable-msnsgement-security
> {noformat}
> Update:
> Rather than introducing three new properties, we should add a single new 
> property: {{security-enabled-components}} which will have a default value of 
> {{all}} and can be configured with the same list of components being worked 
> on in GEODE-420. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1900) Missing update (subsctiption) event with partitioned region during bucket rebalance.

[Anilkumar Gingade (JIRA)]

Anilkumar Gingade created GEODE-1900:


 Summary: Missing update (subsctiption) event with partitioned 
region during bucket rebalance.
 Key: GEODE-1900
 URL: https://issues.apache.org/jira/browse/GEODE-1900
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Anilkumar Gingade


Similar to GEODE-1885...In this case the issue is with update and with both 
offheap and non-offheap regions.

During transaction operation, if there is concurrent redundant bucket 
re-balance is in progress, the client can miss update event, if its primary 
queue is hosted on the node where bucket gets moved from.

Consider, three node cluster N1, N2 and N3. With:

Client C1 connected to node N2.
Primary bucket region B1 on N1. And secondary bucket for B1 on N2.
A Transaction is started on N2, which updates an entry on B1.
When the TX is committed. At the same time the Bucket B1 on N2 is moved to 
N3.
The Tx commit message from N1 is sent to N2. This also includes the 
subscription message, satisfying the client C1.
On N2, for offheap region, when bucket is not found locally, the exception 
response is sent to back to N1 without processing the subscription message.

How to reproduce:

Add following tests/lines in ClientServerTransactionDUnitTest:

  public void 
testUpdateSubscriptionEventsWithOffheapPrWhileBucketRegionIsDestroyed() {   
testSubscriptionEventsWithOffheapPrWhenBucketRegionIsDestroyed(forop.UPDATE);
  }

  public void testUpdateSubscriptionEventsWithPrWhileBucketRegionIsDestroyed() {
testSubscriptionEventsWhenBucketRegionIsDestroyed(false, forop.UPDATE);
  }





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1883) AuthInitializer should be made optional

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1883:


Commit 65f35581b9f7dded29ad37d06f5e036d6a9f0aa1 in incubator-geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=65f3558 ]

GEODE-1883: making AuthInit optional when starting a server/client


> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Swapnil Bawaskar
>
> {{AuthInitializer}} is the interface that a client must implement that 
> provides credentials that are verified by the server. The same interface is 
> also used for peer authentication. 
> In order to configure {{AuthInitialize}} any Geode property starting with 
> {{security-}} is passed through to the {{AuthInitialize.getCredentials}} 
> method.
> For simple authentication where only a username and a password are required, 
> users should not really be required to implement the AuthInitialize interface 
> in the presence of property passthrough. 
> Geode should detect {{security-username}} and {{security-password}} 
> properties in gemfire.security OR gfsecurity.properties file and use those 
> for authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (GEODE-1885) Missing subsctiption event with Offheap partitioned region during bucket rebalance.

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade resolved GEODE-1885.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

Changes checked in...

> Missing subsctiption event with Offheap partitioned region during bucket 
> rebalance.
> ---
>
> Key: GEODE-1885
> URL: https://issues.apache.org/jira/browse/GEODE-1885
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Anilkumar Gingade
>Assignee: Anilkumar Gingade
> Fix For: 1.0.0-incubating
>
>
> During transaction operation, if there is concurrent redundant bucket 
> re-balance is in progress, the client can miss a subscription event, if its 
> primary queue is hosted on the node where bucket gets moved from.
> Consider, three node cluster N1, N2 and N3. With:
> - Client C1 connected to node N2.
> - Primary bucket region B1 on N1. And secondary bucket for B1 on N2.
> - A Transaction is started on N2, which creates a entry on B1.
> - When the TX is committed. At the same time the Bucket B1 on N2 is moved to 
> N3.
> - The Tx commit message from N1 is sent to N2. This also includes the 
> subscription message, satisfying the client C1.
> - On N2, for offheap region, when bucket is not found locally, the exception 
> response is sent to back to N1 without processing the subscription message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (GEODE-1885) Missing subsctiption event with Offheap partitioned region during bucket rebalance.

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade closed GEODE-1885.


> Missing subsctiption event with Offheap partitioned region during bucket 
> rebalance.
> ---
>
> Key: GEODE-1885
> URL: https://issues.apache.org/jira/browse/GEODE-1885
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Anilkumar Gingade
>Assignee: Anilkumar Gingade
> Fix For: 1.0.0-incubating
>
>
> During transaction operation, if there is concurrent redundant bucket 
> re-balance is in progress, the client can miss a subscription event, if its 
> primary queue is hosted on the node where bucket gets moved from.
> Consider, three node cluster N1, N2 and N3. With:
> - Client C1 connected to node N2.
> - Primary bucket region B1 on N1. And secondary bucket for B1 on N2.
> - A Transaction is started on N2, which creates a entry on B1.
> - When the TX is committed. At the same time the Bucket B1 on N2 is moved to 
> N3.
> - The Tx commit message from N1 is sent to N2. This also includes the 
> subscription message, satisfying the client C1.
> - On N2, for offheap region, when bucket is not found locally, the exception 
> response is sent to back to N1 without processing the subscription message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-599) CI Failure: DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-599:
--

Github user dschneider-pivotal commented on the issue:

https://github.com/apache/incubator-geode/pull/239
  
this looks good; I will pull it in


> CI Failure: 
> DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync
> -
>
> Key: GEODE-599
> URL: https://issues.apache.org/jira/browse/GEODE-599
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Dan Smith
>Assignee: Scott Jewell
>  Labels: CI, Flaky
>
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996
> {noformat}
> junit.framework.AssertionFailedError: region contents are not consistent 
> expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.z_versionTestClearWithConcurrentEvents(MultiVMRegionTestCase.java:8304)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestClearWithConcurrentEventsAsync(MultiVMRegionTestCase.java:8266)
>   at 
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testClearWithConcurrentEventsAsync(DistributedAckRegionCCEDUnitTest.java:296)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> 

[jira] [Commented] (GEODE-1899) Address the custom 'clean' gradle task warning

[ASF GitHub Bot (JIRA)]

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

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

GitHub user jaredjstewart opened a pull request:

https://github.com/apache/incubator-geode/pull/240

GEODE-1899: Renamed the custom 'clean' task to work with Gradle 3.0+



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

$ git pull https://github.com/jaredjstewart/incubator-geode 
feature/GEODE-1899

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

https://github.com/apache/incubator-geode/pull/240.patch

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

This closes #240


commit 804a1cabc78357bea13844dd767afcc66a7426af
Author: Jared Stewart 
Date:   2016-09-15T20:24:34Z

GEODE-1899: Renamed the custom 'clean' task to work with Gradle 3.0+




> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1885) Missing subsctiption event with Offheap partitioned region during bucket rebalance.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1885:


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

GEODE-1885: Removed call to check readiness (region check) after the offheap 
region entry is released.

GEODE-1885: Missing subsctiption event with Offheap partitioned region during 
bucket rebalance.

During the trasaction commit on redundant bucket region, if the bucket region 
is moved, the call-back logic (to deliver subscription events) were not invoked 
due to check-readiness call with offheap region. The check-readiness throws 
exception, if the region is not found, which causes the code to return early 
without sending the subscription events.

In this scenario, calling check-readiness is not needed...


> Missing subsctiption event with Offheap partitioned region during bucket 
> rebalance.
> ---
>
> Key: GEODE-1885
> URL: https://issues.apache.org/jira/browse/GEODE-1885
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Anilkumar Gingade
>Assignee: Anilkumar Gingade
>
> During transaction operation, if there is concurrent redundant bucket 
> re-balance is in progress, the client can miss a subscription event, if its 
> primary queue is hosted on the node where bucket gets moved from.
> Consider, three node cluster N1, N2 and N3. With:
> - Client C1 connected to node N2.
> - Primary bucket region B1 on N1. And secondary bucket for B1 on N2.
> - A Transaction is started on N2, which creates a entry on B1.
> - When the TX is committed. At the same time the Bucket B1 on N2 is moved to 
> N3.
> - The Tx commit message from N1 is sent to N2. This also includes the 
> subscription message, satisfying the client C1.
> - On N2, for offheap region, when bucket is not found locally, the exception 
> response is sent to back to N1 without processing the subscription message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1885) Missing subsctiption event with Offheap partitioned region during bucket rebalance.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1885:


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

GEODE-1885: Removed call to check readiness (region check) after the offheap 
region entry is released.

GEODE-1885: Missing subsctiption event with Offheap partitioned region during 
bucket rebalance.

During the trasaction commit on redundant bucket region, if the bucket region 
is moved, the call-back logic (to deliver subscription events) were not invoked 
due to check-readiness call with offheap region. The check-readiness throws 
exception, if the region is not found, which causes the code to return early 
without sending the subscription events.

In this scenario, calling check-readiness is not needed...


> Missing subsctiption event with Offheap partitioned region during bucket 
> rebalance.
> ---
>
> Key: GEODE-1885
> URL: https://issues.apache.org/jira/browse/GEODE-1885
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Anilkumar Gingade
>Assignee: Anilkumar Gingade
>
> During transaction operation, if there is concurrent redundant bucket 
> re-balance is in progress, the client can miss a subscription event, if its 
> primary queue is hosted on the node where bucket gets moved from.
> Consider, three node cluster N1, N2 and N3. With:
> - Client C1 connected to node N2.
> - Primary bucket region B1 on N1. And secondary bucket for B1 on N2.
> - A Transaction is started on N2, which creates a entry on B1.
> - When the TX is committed. At the same time the Bucket B1 on N2 is moved to 
> N3.
> - The Tx commit message from N1 is sent to N2. This also includes the 
> subscription message, satisfying the client C1.
> - On N2, for offheap region, when bucket is not found locally, the exception 
> response is sent to back to N1 without processing the subscription message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-37:
--

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

GEODE-37: update formatters to include org.apache.geode

Imports of com.gemstone are still in the formatters and will be listed
at the very bottom. Next up bottom will be listed org.apache.geode.


> Package renaming - com.gemstone.gemfire -> org.apache.geode
> ---
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: client/server, docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Assignee: Hitesh Khamesra
>Priority: Blocker
> Fix For: 1.0.0-incubating
>
>
> Geode packages should be renamed from com.gemstone -> org.apache.geode in 
> order to allow an easy transition from incubation to become a TLP. 
> Also, it allow the necessary work that may need to be done at the protocol 
> level in order to allow serialization/message exchange between nodes before 
> an actual release using the definitive class/package naming.
> The issue was discussed in the following thread at dev@:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-37:
--

Commit 8ea08da3d2baa64ca631641430b54d71ce3ff362 in incubator-geode's branch 
refs/heads/feature/GEODE-1886 from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8ea08da ]

GEODE-37 Merge branch 'feature/GEODE-37_2' into develop

Conflicts:

geode-core/src/main/java/com/gemstone/gemfire/cache/query/internal/IndexTrackingQueryObserver.java


> Package renaming - com.gemstone.gemfire -> org.apache.geode
> ---
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: client/server, docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Assignee: Hitesh Khamesra
>Priority: Blocker
> Fix For: 1.0.0-incubating
>
>
> Geode packages should be renamed from com.gemstone -> org.apache.geode in 
> order to allow an easy transition from incubation to become a TLP. 
> Also, it allow the necessary work that may need to be done at the protocol 
> level in order to allow serialization/message exchange between nodes before 
> an actual release using the definitive class/package naming.
> The issue was discussed in the following thread at dev@:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-420) locator ssl configuration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-420:
---

Commit 8802404990271bb11a1a4a69fb3baabb26f91d91 in incubator-geode's branch 
refs/heads/feature/GEODE-1886 from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8802404 ]

GEODE-420: Updating Javadoc to reflect changes from http to web


> locator ssl configuration
> -
>
> Key: GEODE-420
> URL: https://issues.apache.org/jira/browse/GEODE-420
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, locator
>Reporter: Darrel Schneider
>Assignee: Udo Kohlmeyer
> Fix For: 1.0.0-incubating
>
>
> We currently allow separate SSL configuration for cluster, server, gateway, 
> jmx-manager, and http-service.
> The "server" attributes configure the ssl connections from clients to a cache 
> server.
> The "gateway" attributes configure the ssl connections between a gateway 
> sender and receiver.
> The "jmx-manager" attributes configure the ssl connections between an admin 
> client (for example gfsh) and the jmx-manager.
> The "http-service" attributes configure the ssl connections between REST 
> clients and the http-service.
> The "cluster" attributes configure the ssl connections between the members of 
> a distributed system (peer-to-peer connections) AND to the locators.
> Using "cluster" for the connections to a locator can be a problem.
> Say you trust all your members of a distributed system since they are running 
> on your private network. So no need for ssl on the p2p connections.
> So you disable cluster-ssl. These means that your peers are locators are all 
> using unsecure connections.
> But some of these members are hosting a cache server and have clients 
> connecting to them. So you configure "server" ssl for the client to server 
> connections. But for your clients to find you servers they need to talk to 
> the locator. Since the clients are coming from the outside world you want 
> them to use SSL. So you configure "server" ssl on them for when they connect 
> to the cache server and "cluster" SSL on them for when they connect to the 
> locator. But your locators are configured with "cluster" SSL disabled so that 
> the p2p connects on the internal network will not be SSL.
> So you are either forced to have you client to locator connections to be 
> unsecure or you need to secure all the cluster connections forcing the peers 
> to also use SSL.
> I think we should introduce "locator" SSL configuration options that would 
> allow you to have just the locator and server using SSL and the "cluster" to 
> have SSL disabled.
> Something else to consider would be for the locator to be able to use SSL for 
> clients but non-SSL for locator-to-locator and peers-to-locator connections. 
> I think this would be more complicated because we would need to have 
> different ports that the locator listens on (one for clients and one for 
> locators and members).
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-599) CI Failure: DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-599:
--

GitHub user gemzdude opened a pull request:

https://github.com/apache/incubator-geode/pull/239

GEODE-599: Remove Flaky annotation from previously failing tests



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

$ git pull https://github.com/gemzdude/incubator-geode feature/GEODE-599

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

https://github.com/apache/incubator-geode/pull/239.patch

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

This closes #239


commit 002ecafed83d2b32245ae79dac4cb5e8e84b2abc
Author: Scott Jewell 
Date:   2016-09-14T22:54:31Z

GEODE-599: Remove Flaky annotation from previously failing tests

commit 0add81aee7f1126ca8021cd7f84064fa2c11f75e
Author: Scott Jewell 
Date:   2016-09-15T17:35:27Z

Merge remote-tracking branch 'origin/develop' into feature/GEODE-599




> CI Failure: 
> DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync
> -
>
> Key: GEODE-599
> URL: https://issues.apache.org/jira/browse/GEODE-599
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Dan Smith
>Assignee: Scott Jewell
>  Labels: CI, Flaky
>
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996
> {noformat}
> junit.framework.AssertionFailedError: region contents are not consistent 
> expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.z_versionTestClearWithConcurrentEvents(MultiVMRegionTestCase.java:8304)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestClearWithConcurrentEventsAsync(MultiVMRegionTestCase.java:8266)
>   at 
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testClearWithConcurrentEventsAsync(DistributedAckRegionCCEDUnitTest.java:296)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at 

[jira] [Assigned] (GEODE-1899) Address the custom 'clean' gradle task warning

[Jared Stewart (JIRA)]

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

Jared Stewart reassigned GEODE-1899:


Assignee: Jared Stewart  (was: Kirk Lund)

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1899) Address the custom 'clean' gradle task warning

[Jared Stewart (JIRA)]

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

Jared Stewart commented on GEODE-1899:
--

This custom 'clean' task is being defined for the root project, and is intended 
to make sure that the top level build directory is cleaned any time clean is 
executed for one of the subprojects:
{code}
task clean(type: Delete) {
  delete rootProject.buildDir
  if (!buildRoot.isEmpty()) {
delete buildRoot
  }  
}
{code}
{code}
subprojects {
  // Make sure clean task for rootProject runs last
  clean.finalizedBy rootProject.clean
}
{code}

We simply need to rename our custom 'clean' task to something like 'cleanRoot' 
instead and wire it in appropriately.

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Kirk Lund
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-599) CI Failure: DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-599:
--

Github user gemzdude closed the pull request at:

https://github.com/apache/incubator-geode/pull/238


> CI Failure: 
> DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEventsAsync
> -
>
> Key: GEODE-599
> URL: https://issues.apache.org/jira/browse/GEODE-599
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Dan Smith
>Assignee: Scott Jewell
>  Labels: CI, Flaky
>
> Revision: 25c8f0cc48e831d6afb459767a42c1c98fb47996
> {noformat}
> junit.framework.AssertionFailedError: region contents are not consistent 
> expected: but was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.TestCase.assertEquals(TestCase.java:244)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.z_versionTestClearWithConcurrentEvents(MultiVMRegionTestCase.java:8304)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.versionTestClearWithConcurrentEventsAsync(MultiVMRegionTestCase.java:8266)
>   at 
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testClearWithConcurrentEventsAsync(DistributedAckRegionCCEDUnitTest.java:296)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 

[jira] [Assigned] (GEODE-1899) Address the custom 'clean' gradle task warning

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-1899:


Assignee: Kirk Lund

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Kirk Lund
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1899) Address the custom 'clean' gradle task warning

[Jared Stewart (JIRA)]

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

Jared Stewart updated GEODE-1899:
-
Component/s: management

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-37:
--

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

GEODE-37: update formatters to include org.apache.geode

Imports of com.gemstone are still in the formatters and will be listed
at the very bottom. Next up bottom will be listed org.apache.geode.


> Package renaming - com.gemstone.gemfire -> org.apache.geode
> ---
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: client/server, docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Assignee: Hitesh Khamesra
>Priority: Blocker
> Fix For: 1.0.0-incubating
>
>
> Geode packages should be renamed from com.gemstone -> org.apache.geode in 
> order to allow an easy transition from incubation to become a TLP. 
> Also, it allow the necessary work that may need to be done at the protocol 
> level in order to allow serialization/message exchange between nodes before 
> an actual release using the definitive class/package naming.
> The issue was discussed in the following thread at dev@:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1899) Address the custom 'clean' gradle task warning

[Jared Stewart (JIRA)]

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

Jared Stewart updated GEODE-1899:
-
Priority: Minor  (was: Major)

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1899) Address the custom 'clean' gradle task warning

[Jared Stewart (JIRA)]

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

Jared Stewart updated GEODE-1899:
-
Summary: Address the custom 'clean' gradle task warning  (was: Address the 
custom 'clean' warning)

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jared Stewart
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1899) Address the custom 'clean' warning

[Jared Stewart (JIRA)]

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

Jared Stewart updated GEODE-1899:
-
Description: 
Geode cannot be built using the latest release of Gradle: 
{code}Defining custom 'clean' task when using the standard Gradle lifecycle 
plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}

  was:
Geode cannot be built using the latest release of Gradle: 
{{Defining custom 'clean' task when using the standard Gradle lifecycle plugins 
has been deprecated and is scheduled to be removed in Gradle 3.0}}


> Address the custom 'clean' warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jared Stewart
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1899) Address the custom 'clean' warning

[Jared Stewart (JIRA)]

Jared Stewart created GEODE-1899:


 Summary: Address the custom 'clean' warning
 Key: GEODE-1899
 URL: https://issues.apache.org/jira/browse/GEODE-1899
 Project: Geode
  Issue Type: Improvement
  Components: build
Reporter: Jared Stewart


Geode cannot be built using the latest release of Gradle: 
{{Defining custom 'clean' task when using the standard Gradle lifecycle plugins 
has been deprecated and is scheduled to be removed in Gradle 3.0}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-420) locator ssl configuration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-420:
---

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

GEODE-420: Updating Javadoc to reflect changes from http to web


> locator ssl configuration
> -
>
> Key: GEODE-420
> URL: https://issues.apache.org/jira/browse/GEODE-420
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, locator
>Reporter: Darrel Schneider
>Assignee: Udo Kohlmeyer
> Fix For: 1.0.0-incubating
>
>
> We currently allow separate SSL configuration for cluster, server, gateway, 
> jmx-manager, and http-service.
> The "server" attributes configure the ssl connections from clients to a cache 
> server.
> The "gateway" attributes configure the ssl connections between a gateway 
> sender and receiver.
> The "jmx-manager" attributes configure the ssl connections between an admin 
> client (for example gfsh) and the jmx-manager.
> The "http-service" attributes configure the ssl connections between REST 
> clients and the http-service.
> The "cluster" attributes configure the ssl connections between the members of 
> a distributed system (peer-to-peer connections) AND to the locators.
> Using "cluster" for the connections to a locator can be a problem.
> Say you trust all your members of a distributed system since they are running 
> on your private network. So no need for ssl on the p2p connections.
> So you disable cluster-ssl. These means that your peers are locators are all 
> using unsecure connections.
> But some of these members are hosting a cache server and have clients 
> connecting to them. So you configure "server" ssl for the client to server 
> connections. But for your clients to find you servers they need to talk to 
> the locator. Since the clients are coming from the outside world you want 
> them to use SSL. So you configure "server" ssl on them for when they connect 
> to the cache server and "cluster" SSL on them for when they connect to the 
> locator. But your locators are configured with "cluster" SSL disabled so that 
> the p2p connects on the internal network will not be SSL.
> So you are either forced to have you client to locator connections to be 
> unsecure or you need to secure all the cluster connections forcing the peers 
> to also use SSL.
> I think we should introduce "locator" SSL configuration options that would 
> allow you to have just the locator and server using SSL and the "cluster" to 
> have SSL disabled.
> Something else to consider would be for the locator to be able to use SSL for 
> clients but non-SSL for locator-to-locator and peers-to-locator connections. 
> I think this would be more complicated because we would need to have 
> different ports that the locator listens on (one for clients and one for 
> locators and members).
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1898) geode-core:javadoc is generating warnings

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1898:
-
Priority: Trivial  (was: Major)

> geode-core:javadoc is generating warnings
> -
>
> Key: GEODE-1898
> URL: https://issues.apache.org/jira/browse/GEODE-1898
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> geode-core:javadoc is generating warnings:
> :geode-core:javadoc
> /Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java:136:
>  warning - @return tag has no arguments.
> /Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit.java:1181:
>  warning - @return tag has no arguments.
> 2 warnings



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1898) geode-core:javadoc is generating warnings

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1898:
-
Affects Version/s: 1.0.0-incubating.M3

> geode-core:javadoc is generating warnings
> -
>
> Key: GEODE-1898
> URL: https://issues.apache.org/jira/browse/GEODE-1898
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> geode-core:javadoc is generating warnings:
> :geode-core:javadoc
> /Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java:136:
>  warning - @return tag has no arguments.
> /Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit.java:1181:
>  warning - @return tag has no arguments.
> 2 warnings



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1898) geode-core:javadoc is generating warnings

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1898:
-
Description: 
geode-core:javadoc is generating warnings:

:geode-core:javadoc

/Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java:136:
 warning - @return tag has no arguments.

/Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit.java:1181:
 warning - @return tag has no arguments.

2 warnings


  was:
geode-core:javadoc is generating warnings:
{noformat}
:geode-core:javadoc
/Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java:136:
 warning - @return tag has no arguments.
/Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit.java:1181:
 warning - @return tag has no arguments.
2 warnings
{noformat}



> geode-core:javadoc is generating warnings
> -
>
> Key: GEODE-1898
> URL: https://issues.apache.org/jira/browse/GEODE-1898
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> geode-core:javadoc is generating warnings:
> :geode-core:javadoc
> /Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java:136:
>  warning - @return tag has no arguments.
> /Users/klund/dev/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/tcp/TCPConduit.java:1181:
>  warning - @return tag has no arguments.
> 2 warnings



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (GEODE-1207) WANSSLDUnitTest.testSenderSSLReceiverSSL

[Barry Oglesby (JIRA)]

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

Barry Oglesby resolved GEODE-1207.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> WANSSLDUnitTest.testSenderSSLReceiverSSL
> 
>
> Key: GEODE-1207
> URL: https://issues.apache.org/jira/browse/GEODE-1207
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Jinmei Liao
>Assignee: Barry Oglesby
>  Labels: CI, Flaky
> Fix For: 1.0.0-incubating
>
>
> Geode_develop_DistributedTests/2224/
> Revision: 616bc27de8621224a9c7fba19a84dfc4eb4d520f
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2115
> [fatal 2016/04/11 07:01:29.111 PDT  0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] SSL Error in connecting 
> to peer /127.0.0.1[59,369].
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
>   at 
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
>   at sun.security.ssl.InputRecord.read(InputRecord.java:527)
>   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
>   at 
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
>   at 
> com.gemstone.gemfire.internal.SocketCreator.configureServerSSLSocket(SocketCreator.java:1055)
>   at 
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.accept(AcceptorImpl.java:1308)
>   at 
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.run(AcceptorImpl.java:1208)
>   at java.lang.Thread.run(Thread.java:745)
> ---
> Found suspect string in log4j at line 2128
> [error 2016/04/11 07:01:29.112 PDT  0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] Cache server: Unexpected 
> IOException from accept
> ---
> Found suspect string in log4j at line 2130
> [fatal 2016/04/11 07:01:29.112 PDT  tid=0x1afa] 
> Uncaught exception in thread Thread[WAN Locator Discovery Thread,5,WAN 
> Locator Discovery Logger Group]
> java.lang.ClassCastException: java.lang.Class cannot be cast to 
> com.gemstone.gemfire.cache.client.internal.locator.wan.RemoteLocatorJoinResponse
>   at 
> com.gemstone.gemfire.cache.client.internal.locator.wan.LocatorDiscovery.exchangeRemoteLocators(LocatorDiscovery.java:176)
>   at 
> com.gemstone.gemfire.cache.client.internal.locator.wan.LocatorDiscovery$RemoteLocatorDiscovery.run(LocatorDiscovery.java:119)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Stacktrace
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2115
> [fatal 2016/04/11 07:01:29.111 PDT  0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] SSL Error in connecting 
> to peer /127.0.0.1[59,369].
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
>   at 
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
>   at sun.security.ssl.InputRecord.read(InputRecord.java:527)
>   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
>   at 
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
>   at 
> com.gemstone.gemfire.internal.SocketCreator.configureServerSSLSocket(SocketCreator.java:1055)
>   at 
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.accept(AcceptorImpl.java:1308)
>   at 
> com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl.run(AcceptorImpl.java:1208)
>   at java.lang.Thread.run(Thread.java:745)
> ---
> Found suspect string in log4j at line 2128
> [error 2016/04/11 07:01:29.112 PDT  0.0.0.0/0.0.0.0:28155 local port: 28155> tid=0x359b] Cache server: Unexpected 
> IOException from accept
> 

[jira] [Resolved] (GEODE-1471) GatewayEventFilter callbacks are not invoked when an AsyncEventQueues is configured using xml

[Barry Oglesby (JIRA)]

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

Barry Oglesby resolved GEODE-1471.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> GatewayEventFilter callbacks are not invoked when an AsyncEventQueues is 
> configured using xml
> -
>
> Key: GEODE-1471
> URL: https://issues.apache.org/jira/browse/GEODE-1471
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
> Fix For: 1.0.0-incubating
>
>
> None of the {{GatewayEventFilter}} callbacks are invoked when configuring 
> {{AsyncEventQueues}} using xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1819) BucketRegionQueue size and keySet can become out of sync during initialization and never recover

[Barry Oglesby (JIRA)]

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

Barry Oglesby updated GEODE-1819:
-
Fix Version/s: 1.0.0-incubating

> BucketRegionQueue size and keySet can become out of sync during 
> initialization and never recover
> 
>
> Key: GEODE-1819
> URL: https://issues.apache.org/jira/browse/GEODE-1819
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
> Fix For: 1.0.0-incubating
>
>
> This bug is the same as GemFire Trac 48049 - One event was left behind in 
> {{ParallelGatewaySenderQueue}} causing the test to hang.
> The issue occurs during {{BucketRegionQueue initialize}}. This method:
> - calls super initialize (which does GII)
> - loads events from temp queue
> - initializes eventSeqNumQueue
> If a destroy event occurs (from a {{ParallelQueueRemovalMessage}}) after the 
> {{super initialize}} call but before the {{BucketRegionQueue initialize}} 
> method completes, then it doesn't actually get removed from the 
> {{CustomEntryConcurrentHashMap}} of entries. Instead, it ends up in the 
> {{UnsharedImageState destroyedEntryKeys}} in {{DESTROYED}} state. The value 
> in the entry is {{Token.DESTROYED}}. This happens because 
> {{inTokenMode==true}} which is the case because {{AbstractBucketRegionQueue}} 
> overrides {{isInitialized}} to return a boolean field, and this field is set 
> to true at the end of {{BucketRegionQueue initialize}}. See 
> {{LocalRegion.mapDestroy}} and {{lockGII}}. So, in effect, the 
> {{BucketRegionQueue}} is not initialized until after the temp queue is 
> drained, and the {{eventSeqNumQueue}} is initialized. Events in this state 
> never get cleaned up, so the behavior is that size returns 1 but keySet 
> returns empty set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)