[jira] [Resolved] (GEODE-2005) gradle javadoc is reporting warnings

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-2005.
--
   Resolution: Fixed
Fix Version/s: 1.1.0-incubating

> gradle javadoc is reporting warnings
> 
>
> Key: GEODE-2005
> URL: https://issues.apache.org/jira/browse/GEODE-2005
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
> Fix For: 1.1.0-incubating
>
>
> Latest warning:
> :geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
>  warning - @return tag has no arguments.



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

[jira] [Resolved] (GEODE-2007) gradle build generates warnings for "uses unchecked or unsafe operations"

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-2007.
--
   Resolution: Fixed
Fix Version/s: 1.1.0-incubating

> gradle build generates warnings for "uses unchecked or unsafe operations"
> -
>
> Key: GEODE-2007
> URL: https://issues.apache.org/jira/browse/GEODE-2007
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
> Fix For: 1.1.0-incubating
>
>
> :extensions/geode-modules-tomcat7:compileJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat7/src/main/java/org/apache/geode/modules/session/catalina/DeltaSession7.java
>  uses unchecked or unsafe operations.
> :extensions/geode-modules-tomcat8:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat8/src/test/java/org/apache/geode/modules/session/Tomcat8SessionsClientServerDUnitTest.java
>  uses unchecked or unsafe operations.
> :geode-old-client-support:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/geode-old-client-support/src/test/java/org/apache/geode/OldClientSupportDUnitTest.java
>  uses unchecked or unsafe operations.
> These warnings interfere with the goal of having a clean build without 
> warnings and these warnings are easy to fix.



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

[jira] [Commented] (GEODE-2005) gradle javadoc is reporting warnings

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2005:


Commit 3d173b1852facd50bc6396521bf862dd442bfa46 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=3d173b1 ]

GEODE-2005: fix javadoc warning and format


> gradle javadoc is reporting warnings
> 
>
> Key: GEODE-2005
> URL: https://issues.apache.org/jira/browse/GEODE-2005
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Latest warning:
> :geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
>  warning - @return tag has no arguments.



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

[jira] [Commented] (GEODE-2007) gradle build generates warnings for "uses unchecked or unsafe operations"

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2007:


Commit a53c4b1509867a1847b8a21ef8b926911f874bb1 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=a53c4b1 ]

GEODE-2007: fix unchecked warnings


> gradle build generates warnings for "uses unchecked or unsafe operations"
> -
>
> Key: GEODE-2007
> URL: https://issues.apache.org/jira/browse/GEODE-2007
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> :extensions/geode-modules-tomcat7:compileJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat7/src/main/java/org/apache/geode/modules/session/catalina/DeltaSession7.java
>  uses unchecked or unsafe operations.
> :extensions/geode-modules-tomcat8:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat8/src/test/java/org/apache/geode/modules/session/Tomcat8SessionsClientServerDUnitTest.java
>  uses unchecked or unsafe operations.
> :geode-old-client-support:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/geode-old-client-support/src/test/java/org/apache/geode/OldClientSupportDUnitTest.java
>  uses unchecked or unsafe operations.
> These warnings interfere with the goal of having a clean build without 
> warnings and these warnings are easy to fix.



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

[jira] [Commented] (GEODE-2006) CI Failure: GemfireDataCommandsDUnitTest.testSelectCommand

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2006:


Commit 474ff41e9ff4f357baaea27e6b4da7d4328f2231 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=474ff41 ]

GEODE-2006: add FlakyTest category to testSelectCommand

Also, remove unused serial id.


> CI Failure: GemfireDataCommandsDUnitTest.testSelectCommand
> --
>
> Key: GEODE-2006
> URL: https://issues.apache.org/jira/browse/GEODE-2006
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: CI, Flaky
>
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest
>  > testSelectCommand FAILED
> java.lang.AssertionError: Expected CompositeResult Returned Result Type 
> error
> at org.junit.Assert.fail(Assert.java:88)
> at 
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.validateSelectResult(GemfireDataCommandsDUnitTest.java:831)
> at 
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.doTestSelectProjectionWithNestedField(GemfireDataCommandsDUnitTest.java:474)
> at 
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testSelectCommand(GemfireDataCommandsDUnitTest.java:534)



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

[jira] [Commented] (GEODE-2011) CI Failure: PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt commented on GEODE-2011:
-

The test sets a system property that is picked up in a static-final-boolean in 
AutoSerializableManager.  If that class has already been initialized it isn't 
going to honor the system property setting.  There might be other tests doing 
the same thing.  They all need to be changed to effect the desired behavior in 
a different way.

> CI Failure: 
> PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer
> -
>
> Key: GEODE-2011
> URL: https://issues.apache.org/jira/browse/GEODE-2011
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Kirk Lund
>  Labels: CI, Flaky
>
> org.apache.geode.pdx.PdxClientServerDUnitTest > 
> testNonPersistentServerRestartAutoSerializer FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.pdx.PdxClientServerDUnitTest$12.call in VM 2 running on Host 
> 5c320afe with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
> at 
> org.apache.geode.pdx.PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer(PdxClientServerDUnitTest.java:255)
> Caused by:
> java.lang.ClassCastException: 
> org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType1 cannot be cast to 
> org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType2



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

[jira] [Commented] (GEODE-388) DynamicRegionFactory should be deprecated

[Dan Smith (JIRA)]

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

Dan Smith commented on GEODE-388:
-

Based on this discussion on the mailing list, we're going to go forward with 
deprecating this class without waiting on GEODE-215.

http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201610.mbox/%3ccafh+7k1jlopkycfwppsu5npuk9vdha0nducw_dckqgtqzzi...@mail.gmail.com%3e

> DynamicRegionFactory should be deprecated
> -
>
> Key: GEODE-388
> URL: https://issues.apache.org/jira/browse/GEODE-388
> Project: Geode
>  Issue Type: Wish
>  Components: docs, regions
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> DynamicRegionFactory should be deprecated.
> See GEODE-72 and GEODE-215.



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

[jira] [Assigned] (GEODE-388) DynamicRegionFactory should be deprecated

[Dan Smith (JIRA)]

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

Dan Smith reassigned GEODE-388:
---

Assignee: Dan Smith

> DynamicRegionFactory should be deprecated
> -
>
> Key: GEODE-388
> URL: https://issues.apache.org/jira/browse/GEODE-388
> Project: Geode
>  Issue Type: Wish
>  Components: docs, regions
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> DynamicRegionFactory should be deprecated.
> See GEODE-72 and GEODE-215.



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

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

[Karen Smoler Miller (JIRA)]

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

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

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, management
>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] [Commented] (GEODE-706) CI failure: DiskDistributedNoAckAsyncRegionDUnitTest.testEntryIdleDestroy

[ASF subversion and git services (JIRA)]

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

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

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

GEODE-706 Fixed race condition between expiry thread and put thread.

There was possibility that expiry thread destroying the entry and
another thread doing update on same key. In this case expiry thread
cancel's existing task and update thread adds expiry task. But this
tasks are refer by regionEntry, which is same for both the threads.
So in this case if expiry thread cancel's task after update thread
then that entry will never expire.


> CI failure: DiskDistributedNoAckAsyncRegionDUnitTest.testEntryIdleDestroy
> -
>
> Key: GEODE-706
> URL: https://issues.apache.org/jira/browse/GEODE-706
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.0.0-incubating
>Reporter: Jens Deppe
>Assignee: Hitesh Khamesra
>  Labels: CI, Flaky
>
> git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
> {noformat}
> Error Message
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> Stacktrace
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
>   at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
>   at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
>   at 
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
>   at 
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
>   at 
> com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
>   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.GeneratedMethodAccessor73.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.GeneratedMethodAccessor72.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 
> 

[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=15583282#comment-15583282
 ] 

ASF subversion and git services commented on GEODE-1883:


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

GEODE-1883 AuthInitializer should be made optional

Documentation of how a cache client may set its credentials
for authentication is revised to no longer state that the
client can set the two security properties. When this
bug is fixed, the documentation should be revised again.


> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>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] [Commented] (GEODE-2011) CI Failure: PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer

[Kirk Lund (JIRA)]

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

Kirk Lund commented on GEODE-2011:
--

I saw this fail in a couple CI builds. Passes for me, so I'm marking it Flaky.

> CI Failure: 
> PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer
> -
>
> Key: GEODE-2011
> URL: https://issues.apache.org/jira/browse/GEODE-2011
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Kirk Lund
>  Labels: CI, Flaky
>
> org.apache.geode.pdx.PdxClientServerDUnitTest > 
> testNonPersistentServerRestartAutoSerializer FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.pdx.PdxClientServerDUnitTest$12.call in VM 2 running on Host 
> 5c320afe with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
> at 
> org.apache.geode.pdx.PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer(PdxClientServerDUnitTest.java:255)
> Caused by:
> java.lang.ClassCastException: 
> org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType1 cannot be cast to 
> org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType2



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

[jira] [Updated] (GEODE-2011) CI Failure: PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2011:
-
Labels: CI Flaky  (was: )

> CI Failure: 
> PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer
> -
>
> Key: GEODE-2011
> URL: https://issues.apache.org/jira/browse/GEODE-2011
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Kirk Lund
>  Labels: CI, Flaky
>
> org.apache.geode.pdx.PdxClientServerDUnitTest > 
> testNonPersistentServerRestartAutoSerializer FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.pdx.PdxClientServerDUnitTest$12.call in VM 2 running on Host 
> 5c320afe with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
> at 
> org.apache.geode.pdx.PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer(PdxClientServerDUnitTest.java:255)
> Caused by:
> java.lang.ClassCastException: 
> org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType1 cannot be cast to 
> org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType2



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

[jira] [Created] (GEODE-2011) CI Failure: PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2011:


 Summary: CI Failure: 
PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer
 Key: GEODE-2011
 URL: https://issues.apache.org/jira/browse/GEODE-2011
 Project: Geode
  Issue Type: Bug
  Components: serialization
Reporter: Kirk Lund


org.apache.geode.pdx.PdxClientServerDUnitTest > 
testNonPersistentServerRestartAutoSerializer FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.pdx.PdxClientServerDUnitTest$12.call in VM 2 running on Host 
5c320afe with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
at 
org.apache.geode.pdx.PdxClientServerDUnitTest.testNonPersistentServerRestartAutoSerializer(PdxClientServerDUnitTest.java:255)

Caused by:
java.lang.ClassCastException: 
org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType1 cannot be cast to 
org.apache.geode.pdx.PdxClientServerDUnitTest$AutoPdxType2




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

[jira] [Updated] (GEODE-1976) CI Failure: QueueCommandsDUnitTest.testCreateUpdatesSharedConfig

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1976:
-
Labels: CI Flaky  (was: )

> CI Failure: QueueCommandsDUnitTest.testCreateUpdatesSharedConfig
> 
>
> Key: GEODE-1976
> URL: https://issues.apache.org/jira/browse/GEODE-1976
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Barry Oglesby
>  Labels: CI, Flaky
>
> Geode_develop_DistributedTests
> Private Build #4134
> Revision: abef045179e5d805cb04bc55a77a82798becdaae
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.internal.cli.commands.QueueCommandsDUnitTest$7.run
>  in VM 1 running on Host cc1-co.gemstone.com with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
>   at 
> org.apache.geode.management.internal.cli.commands.QueueCommandsDUnitTest.testCreateUpdatesSharedConfig(QueueCommandsDUnitTest.java:355)
>   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.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 

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

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller edited comment on GEODE-1883 at 10/17/16 7:37 PM:
--

There should be an update in the newly-added documentation about the client 
setting of the properties. I will do this in the {{develop}} branch, and if 
there must be a third Geode release candidate for 1.0.0-incubating, this change 
should be cherry picked into the new release candidate.

Also, the documentation should be updated again if/when this bug is fixed.


was (Author: karensmolermiller):
There should be an update in the newly-added documentation about the client 
setting of the properties. I will do this in the {{release/1.0.0-incubating}} 
branch, so it goes into the next Geode release candidate.

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>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] [Updated] (GEODE-2010) GFSH DistributedTests are in need overhauling

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2010:
-
Description: 
Many of these tests write to the disk without using TemporaryFolder so you end 
up with RAT failures after running a test in an IDE unless you remember to 
search for the output from the test to delete it.

These tests also use HeadlessGfsh or TestableGfsh. Both are very buggy, eat 
exceptions, have strange timeouts and can cause flaky test failures.

List of tests that are known to leave behind testing artifacts on disk:
* CreateAlterDestroyRegionCommandsDUnitTest


  was:
Many of these tests write to the disk without using TemporaryFolder so you end 
up with RAT failures after running a test in an IDE unless you remember to 
search for the output from the test to delete it.

These tests also use HeadlessGfsh or TestableGfsh. Both are very buggy, eat 
exceptions, have strange timeouts and can cause flaky test failures.



> GFSH DistributedTests are in need overhauling
> -
>
> Key: GEODE-2010
> URL: https://issues.apache.org/jira/browse/GEODE-2010
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Many of these tests write to the disk without using TemporaryFolder so you 
> end up with RAT failures after running a test in an IDE unless you remember 
> to search for the output from the test to delete it.
> These tests also use HeadlessGfsh or TestableGfsh. Both are very buggy, eat 
> exceptions, have strange timeouts and can cause flaky test failures.
> List of tests that are known to leave behind testing artifacts on disk:
> * CreateAlterDestroyRegionCommandsDUnitTest



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

[jira] [Assigned] (GEODE-2010) GFSH DistributedTests are in need overhauling

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-2010:


Assignee: Kirk Lund

> GFSH DistributedTests are in need overhauling
> -
>
> Key: GEODE-2010
> URL: https://issues.apache.org/jira/browse/GEODE-2010
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Many of these tests write to the disk without using TemporaryFolder so you 
> end up with RAT failures after running a test in an IDE unless you remember 
> to search for the output from the test to delete it.
> These tests also use HeadlessGfsh or TestableGfsh. Both are very buggy, eat 
> exceptions, have strange timeouts and can cause flaky test failures.



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

[jira] [Assigned] (GEODE-288) Remove deprecated Admin API

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-288:
---

Assignee: Kirk Lund

> Remove deprecated Admin API
> ---
>
> Key: GEODE-288
> URL: https://issues.apache.org/jira/browse/GEODE-288
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> The Admin API (com.gemstone.gemfire.admin) and old JMX Agent have been 
> deprecated since GemFire 7.0. The Admin API was retired in favor of using the 
> new Management JMX API (com.gemstone.gemfire.management) and GFSH.
> #1) move some Admin classes used internally by non-Admin code:
> move com.gemstone.gemfire.admin.BackupStatus
> move com.gemstone.gemfire.admin.OperationCancelledException
> move com.gemstone.gemfire.admin.RegionNotFoundException
> move 
> com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.backupAllMembers
> move 
> com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.compactAllDiskStores
> move com.gemstone.gemfire.admin.internal.FinishBackupRequest
> move com.gemstone.gemfire.admin.internal.FlushToDiskRequest
> move com.gemstone.gemfire.admin.internal.InetAddressUtil
> move com.gemstone.gemfire.admin.internal.PrepareBackupRequest
> #2) move com.gemstone.gemfire.admin to 
> com.gemstone.gemfire.internal.admin.api (temporarily)
> #3) remove com.gemstone.gemfire.cache.* usage of admin
> #4) remove com.gemstone.gemfire.distributed.* usage of admin
> #5) remove com.gemstone.gemfire.internal.* usage of admin (except for 
> internal.admin.*)
> #6) remove com.gemstone.gemfire.management.* usage of admin
> #7) remove com.gemstone.gemfire.internal.admin.api if possible
> #8) remove unused classes from com.gemstone.gemfire.internal.admin.*
> Breakdown by package and class:
> com.gemstone.gemfire
>   --change DataSerializer to use moved RegionNotFoundException
> com.gemstone.gemfire.cache
> com.gemstone.gemfire.cache.persistence
> com.gemstone.gemfire.cache.util
>   --remove com.gemstone.gemfire.cache.util.UniversalMembershipListenerAdapter
> com.gemstone.gemfire.distributed
>   --remove Admin API from javadocs in Locator and DistributedSystem
> com.gemstone.gemfire.distributed.internal
>   --remove 
> com.gemstone.gemfire.distributed.internal.DistributionManager.createHealthMonitor
>   --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitor
>   --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitorImpl
>   --change 
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.hasAlertListenerFor
>  to not use AlertLevel
> com.gemstone.gemfire.internal
>   --remove DSFIDFactory support for admin messages
>   --remove com.gemstone.gemfire.admin.jmx.internal.AgentLauncher from 
> GemFireUtilLauncher
>   --change MigrationServer to use moved InetAddressUtil
>   --change SocketCreator to use moved InetAddressUtil
>   --remove SystemAdmin.backup
>   --remove SystemAdmin.compactAllDiskStores
>   --remove SystemAdmin.shutDownAll
>   --remove SystemAdmin.listMissingDiskStores
>   --remove SystemAdmin.revokeMissingDiskStores
> com.gemstone.gemfire.internal.cache
>   --replace use of com.gemstone.gemfire.admin.OperationCancelledException
>   --remove use of 
> com.gemstone.gemfire.admin.internal.SystemMemberCacheEventProcessor
> com.gemstone.gemfire.internal.cache.partitioned
>   --replace use of com.gemstone.gemfire.admin.OperationCancelledException
> com.gemstone.gemfire.internal.cache.snapshot
>   --replace use of com.gemstone.gemfire.admin.RegionNotFoundException
> com.gemstone.gemfire.internal.tools.gfsh.app.command.task
>   --reimplement PartitionedRegionAttributeTask
> com.gemstone.gemfire.internal.tools.gfsh.util
>   --reimplement RegionUtil
> com.gemstone.gemfire.management.internal.beans
>   --change DistributedSystemBridge to use moved classes
> com.gemstone.gemfire.management.internal.cli.commands
>   --change DiskStoreCommands to use moved classes
>   



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

[jira] [Created] (GEODE-2009) CI Failure: CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2009:


 Summary: CI Failure: 
CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig
 Key: GEODE-2009
 URL: https://issues.apache.org/jira/browse/GEODE-2009
 Project: Geode
  Issue Type: Bug
  Components: management, tests
Reporter: Kirk Lund


org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest
 > testCreateAlterDestroyUpdatesSharedConfig FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest$$Lambda$33/604398710.run
 in VM 1 running on Host fa2d3f616251 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
at 
org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig(CreateAlterDestroyRegionCommandsDUnitTest.java:856)

Caused by:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:712)
at org.junit.Assert.assertNotNull(Assert.java:722)
at 
org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.lambda$testCreateAlterDestroyUpdatesSharedConfig$1e53591e$3(CreateAlterDestroyRegionCommandsDUnitTest.java:871)



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

[jira] [Updated] (GEODE-2009) CI Failure: CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2009:
-
Labels: CI Flaky  (was: )

> CI Failure: 
> CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig
> ---
>
> Key: GEODE-2009
> URL: https://issues.apache.org/jira/browse/GEODE-2009
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>  Labels: CI, Flaky
>
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest
>  > testCreateAlterDestroyUpdatesSharedConfig FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest$$Lambda$33/604398710.run
>  in VM 1 running on Host fa2d3f616251 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
> at 
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig(CreateAlterDestroyRegionCommandsDUnitTest.java:856)
> Caused by:
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:712)
> at org.junit.Assert.assertNotNull(Assert.java:722)
> at 
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.lambda$testCreateAlterDestroyUpdatesSharedConfig$1e53591e$3(CreateAlterDestroyRegionCommandsDUnitTest.java:871)



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

[jira] [Created] (GEODE-2008) CI Failure: CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2008:


 Summary: CI Failure: 
CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig
 Key: GEODE-2008
 URL: https://issues.apache.org/jira/browse/GEODE-2008
 Project: Geode
  Issue Type: Bug
  Components: management, tests
Reporter: Kirk Lund


org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest
 > testCreateAlterDestroyUpdatesSharedConfig FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest$$Lambda$33/604398710.run
 in VM 1 running on Host fa2d3f616251 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
at 
org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig(CreateAlterDestroyRegionCommandsDUnitTest.java:856)

Caused by:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:712)
at org.junit.Assert.assertNotNull(Assert.java:722)
at 
org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.lambda$testCreateAlterDestroyUpdatesSharedConfig$1e53591e$3(CreateAlterDestroyRegionCommandsDUnitTest.java:871)



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

[jira] [Updated] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[Kevin Duling (JIRA)]

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

Kevin Duling updated GEODE-2004:

Fix Version/s: 1.0.0-incubating

> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Affects Versions: 1.0.0-incubating
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating
>
>




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

[jira] [Updated] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[Kevin Duling (JIRA)]

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

Kevin Duling updated GEODE-2004:

Affects Version/s: 1.0.0-incubating

> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Affects Versions: 1.0.0-incubating
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating
>
>




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

[jira] [Resolved] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[Jinmei Liao (JIRA)]

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

Jinmei Liao resolved GEODE-2004.

Resolution: Fixed

> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
>




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

[jira] [Commented] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2004:


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

GEODE-2004: Create/update/delete query through rest api should require 
DATA:READ instead of DATA:WRITE

* This closes #262


> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
>




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

[jira] [Commented] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
>




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

[jira] [Assigned] (GEODE-2007) gradle build generates warnings for "uses unchecked or unsafe operations"

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-2007:


Assignee: Kirk Lund

> gradle build generates warnings for "uses unchecked or unsafe operations"
> -
>
> Key: GEODE-2007
> URL: https://issues.apache.org/jira/browse/GEODE-2007
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> :extensions/geode-modules-tomcat7:compileJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat7/src/main/java/org/apache/geode/modules/session/catalina/DeltaSession7.java
>  uses unchecked or unsafe operations.
> :extensions/geode-modules-tomcat8:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat8/src/test/java/org/apache/geode/modules/session/Tomcat8SessionsClientServerDUnitTest.java
>  uses unchecked or unsafe operations.
> :geode-old-client-support:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/geode-old-client-support/src/test/java/org/apache/geode/OldClientSupportDUnitTest.java
>  uses unchecked or unsafe operations.
> These warnings interfere with the goal of having a clean build without 
> warnings and these warnings are easy to fix.



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

[jira] [Created] (GEODE-2007) gradle build generates warnings for "uses unchecked or unsafe operations"

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2007:


 Summary: gradle build generates warnings for "uses unchecked or 
unsafe operations"
 Key: GEODE-2007
 URL: https://issues.apache.org/jira/browse/GEODE-2007
 Project: Geode
  Issue Type: Bug
  Components: build
Reporter: Kirk Lund


:extensions/geode-modules-tomcat7:compileJavaNote: 
/tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat7/src/main/java/org/apache/geode/modules/session/catalina/DeltaSession7.java
 uses unchecked or unsafe operations.

:extensions/geode-modules-tomcat8:compileTestJavaNote: 
/tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat8/src/test/java/org/apache/geode/modules/session/Tomcat8SessionsClientServerDUnitTest.java
 uses unchecked or unsafe operations.

:geode-old-client-support:compileTestJavaNote: 
/tmp/build/ae3c03f4/geode/geode-old-client-support/src/test/java/org/apache/geode/OldClientSupportDUnitTest.java
 uses unchecked or unsafe operations.

These warnings interfere with the goal of having a clean build without warnings 
and these warnings are easy to fix.




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

[jira] [Commented] (GEODE-1993) value returned through /region/key rest service needs to be post processed

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1993:


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

GEODE-1993: allow LocatorServerStartupRule to save server's ports as well.

* added more tetss


> value returned through /region/key rest service needs to be post processed
> --
>
> Key: GEODE-1993
> URL: https://issues.apache.org/jira/browse/GEODE-1993
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>Reporter: Jinmei Liao
>
> The new rest security did not use post processor before returning the value 
> back to the client.



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

[jira] [Updated] (GEODE-2007) gradle build generates warnings for "uses unchecked or unsafe operations"

[Kirk Lund (JIRA)]

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

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

> gradle build generates warnings for "uses unchecked or unsafe operations"
> -
>
> Key: GEODE-2007
> URL: https://issues.apache.org/jira/browse/GEODE-2007
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> :extensions/geode-modules-tomcat7:compileJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat7/src/main/java/org/apache/geode/modules/session/catalina/DeltaSession7.java
>  uses unchecked or unsafe operations.
> :extensions/geode-modules-tomcat8:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/extensions/geode-modules-tomcat8/src/test/java/org/apache/geode/modules/session/Tomcat8SessionsClientServerDUnitTest.java
>  uses unchecked or unsafe operations.
> :geode-old-client-support:compileTestJavaNote: 
> /tmp/build/ae3c03f4/geode/geode-old-client-support/src/test/java/org/apache/geode/OldClientSupportDUnitTest.java
>  uses unchecked or unsafe operations.
> These warnings interfere with the goal of having a clean build without 
> warnings and these warnings are easy to fix.



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

[jira] [Commented] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[ASF GitHub Bot (JIRA)]

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

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

GitHub user kjduling opened a pull request:

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

GEODE-2004: Create/update/delete query through rest api should requir…

…e DATA:READ instead of DATA:WRITE

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

$ git pull https://github.com/kjduling/incubator-geode feature/GEODE-2004

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

https://github.com/apache/incubator-geode/pull/262.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 #262


commit 08745c9084c7cbfb4229bb0e9edcced1363224bd
Author: Kevin Duling 
Date:   2016-10-17T18:02:54Z

GEODE-2004: Create/update/delete query through rest api should require 
DATA:READ instead of DATA:WRITE




> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
>




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

[jira] [Created] (GEODE-2006) CI Failure: GemfireDataCommandsDUnitTest.testSelectCommand

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2006:


 Summary: CI Failure: GemfireDataCommandsDUnitTest.testSelectCommand
 Key: GEODE-2006
 URL: https://issues.apache.org/jira/browse/GEODE-2006
 Project: Geode
  Issue Type: Bug
  Components: management, tests
Reporter: Kirk Lund


org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest 
> testSelectCommand FAILED
java.lang.AssertionError: Expected CompositeResult Returned Result Type 
error
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.validateSelectResult(GemfireDataCommandsDUnitTest.java:831)
at 
org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.doTestSelectProjectionWithNestedField(GemfireDataCommandsDUnitTest.java:474)
at 
org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testSelectCommand(GemfireDataCommandsDUnitTest.java:534)




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

[jira] [Updated] (GEODE-2006) CI Failure: GemfireDataCommandsDUnitTest.testSelectCommand

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2006:
-
Labels: CI Flaky  (was: )

> CI Failure: GemfireDataCommandsDUnitTest.testSelectCommand
> --
>
> Key: GEODE-2006
> URL: https://issues.apache.org/jira/browse/GEODE-2006
> Project: Geode
>  Issue Type: Bug
>  Components: management, tests
>Reporter: Kirk Lund
>  Labels: CI, Flaky
>
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest
>  > testSelectCommand FAILED
> java.lang.AssertionError: Expected CompositeResult Returned Result Type 
> error
> at org.junit.Assert.fail(Assert.java:88)
> at 
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.validateSelectResult(GemfireDataCommandsDUnitTest.java:831)
> at 
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.doTestSelectProjectionWithNestedField(GemfireDataCommandsDUnitTest.java:474)
> at 
> org.apache.geode.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testSelectCommand(GemfireDataCommandsDUnitTest.java:534)



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

[jira] [Updated] (GEODE-1249) CI failure: GemfireDataCommandsDUnitTest.testSimplePutIfAbsentCommand

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1249:
-
Labels: CI Flaky  (was: CI)

> CI failure: GemfireDataCommandsDUnitTest.testSimplePutIfAbsentCommand
> -
>
> Key: GEODE-1249
> URL: https://issues.apache.org/jira/browse/GEODE-1249
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Jens Deppe
>  Labels: CI, Flaky
>
> Build # 2279
> {noformat}
> Error Message
> java.lang.AssertionError: expected: but was:
> Stacktrace
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testSimplePutIfAbsentCommand(GemfireDataCommandsDUnitTest.java:867)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.GeneratedMethodAccessor7.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.GeneratedMethodAccessor6.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 
> 

[jira] [Updated] (GEODE-1487) CI Failure: GemfireDataCommandsDUnitTest.testRebalanceForEntireDS

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1487:
-
Labels: CI Flaky  (was: CI)

> CI Failure: GemfireDataCommandsDUnitTest.testRebalanceForEntireDS
> -
>
> Key: GEODE-1487
> URL: https://issues.apache.org/jira/browse/GEODE-1487
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Udo Kohlmeyer
>  Labels: CI, Flaky
>
> Build #482 (May 28, 2016 3:42:00 AM)
> Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097
> https://builds.apache.org/job/Geode-nightly/482/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testRebalanceForEntireDS/
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host 
> asf902.gq1.ygridcore.net with 4 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:126)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:115)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:106)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.setupTestRebalanceForEntireDS(GemfireDataCommandsDUnitTest.java:1882)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testRebalanceForEntireDS(GemfireDataCommandsDUnitTest.java:1862)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> 

[jira] [Updated] (GEODE-2005) gradle javadoc is reporting warnings

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2005:
-
Description: 
Latest warning:

:geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
 warning - @return tag has no arguments.


  was:
Latest warning:
{noformat}
:geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
 warning - @return tag has no arguments.
{noformat}



> gradle javadoc is reporting warnings
> 
>
> Key: GEODE-2005
> URL: https://issues.apache.org/jira/browse/GEODE-2005
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>
> Latest warning:
> :geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
>  warning - @return tag has no arguments.



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

[jira] [Assigned] (GEODE-2005) gradle javadoc is reporting warnings

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-2005:


Assignee: Kirk Lund

> gradle javadoc is reporting warnings
> 
>
> Key: GEODE-2005
> URL: https://issues.apache.org/jira/browse/GEODE-2005
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Latest warning:
> :geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
>  warning - @return tag has no arguments.



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

[jira] [Created] (GEODE-2005) gradle javadoc is reporting warnings

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2005:


 Summary: gradle javadoc is reporting warnings
 Key: GEODE-2005
 URL: https://issues.apache.org/jira/browse/GEODE-2005
 Project: Geode
  Issue Type: Bug
  Components: build
Reporter: Kirk Lund


Latest warning:
{noformat}
:geode-web-api:javadoc/tmp/build/ae3c03f4/geode/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/controllers/CommonCrudController.java:196:
 warning - @return tag has no arguments.
{noformat}




--
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:
-
Fix Version/s: (was: 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
>Priority: Trivial
> Fix For: 1.0.0-incubating
>
>
> 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-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 resolved GEODE-1898.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
   1.0.0-incubating

> 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
> Fix For: 1.0.0-incubating, 1.0.0-incubating.M3
>
>
> 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] [Assigned] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[Kevin Duling (JIRA)]

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

Kevin Duling reassigned GEODE-2004:
---

Assignee: Kevin Duling

> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
>




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

[jira] [Updated] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-2004:
---
Summary: Create/update/delete query through rest api should require 
DATA:READ instead of DATA:WRITE  (was: Create/update/delete query through rest 
api should require DATA:MANAGE instead of DATA:READ.)

> Create/update/delete query through rest api should require DATA:READ instead 
> of DATA:WRITE
> --
>
> Key: GEODE-2004
> URL: https://issues.apache.org/jira/browse/GEODE-2004
> Project: Geode
>  Issue Type: Bug
>  Components: management, security
>Reporter: Jinmei Liao
>




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

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

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller commented on GEODE-1883:


There should be an update in the newly-added documentation about the client 
setting of the properties. I will do this in the {{release/1.0.0-incubating}} 
branch, so it goes into the next Geode release candidate.

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>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] [Created] (GEODE-2004) Create/update/delete query through rest api should require DATA:MANAGE instead of DATA:READ.

[Jinmei Liao (JIRA)]

Jinmei Liao created GEODE-2004:
--

 Summary: Create/update/delete query through rest api should 
require DATA:MANAGE instead of DATA:READ.
 Key: GEODE-2004
 URL: https://issues.apache.org/jira/browse/GEODE-2004
 Project: Geode
  Issue Type: Bug
  Components: management, security
Reporter: Jinmei Liao






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

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

[Jinmei Liao (JIRA)]

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

Jinmei Liao commented on GEODE-1883:


Currently in peer to peer communication, security-auth-init is optional. But in 
client-server, it is still required. It's going to be a very involved change on 
the client side to make it optional in the current state of java client.

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>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] [Commented] (GEODE-538) PersistentColocatedPartitionedRegionDUnitTest.testRebalanceWithOfflineChildRegion failed if do not wait on getResult

[Kenneth Howe (JIRA)]

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

Kenneth Howe commented on GEODE-538:


Queries on a persistent colocated PR can also cause this problem.

> PersistentColocatedPartitionedRegionDUnitTest.testRebalanceWithOfflineChildRegion
>  failed if do not wait on getResult
> 
>
> Key: GEODE-538
> URL: https://issues.apache.org/jira/browse/GEODE-538
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Jinmei Liao
>Assignee: Kenneth Howe
> Attachments: logs.zip
>
>
> While attempting to work on GEODE-506, I commented out line s1538-1540 like 
> the following
> async1 = vm1.invokeAsync(createChildPR);
> async0 = vm0.invokeAsync(createChildPR);
> AsyncInvocation async2 = vm2.invokeAsync(createChildPR);
> //async0.getResult(MAX_WAIT);  -- line 1538
> //async1.getResult(MAX_WAIT);  -- line 1539
> //async2.getResult(MAX_WAIT);  -- line 1540
> This will reproduce the error similar to the one reported in GEODE506, but it 
> failed on checking the data on parent region instead of the child region. Log 
> files attached.
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionTestBase$5.run
>  in VM 0 running on Host localhost with 4 VMs
>   at dunit.VM.invoke(VM.java:368)
>   at dunit.VM.invoke(VM.java:312)
>   at dunit.VM.invoke(VM.java:266)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionTestBase.checkData(PersistentPartitionedRegionTestBase.java:182)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionTestBase.checkData(PersistentPartitionedRegionTestBase.java:165)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.rebalanceWithOfflineChildRegion(PersistentColocatedPartitionedRegionDUnitTest.java:1543)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testRebalanceWithOfflineChildRegion(PersistentColocatedPartitionedRegionDUnitTest.java:1223)
>   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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>   at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: junit.framework.AssertionFailedError: For key 1 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.internal.cache.partitioned.PersistentPartitionedRegionTestBase$5.run(PersistentPartitionedRegionTestBase.java:177)
>   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 hydra.MethExecutor.executeObject(MethExecutor.java:267)
>   at 
> dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:77)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 

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

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1883:
---
Component/s: (was: security)

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: Improvement
>  Components: management
>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] [Updated] (GEODE-1883) AuthInitializer should be made optional

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1883:
---
Issue Type: New Feature  (was: Improvement)

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>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] [Updated] (GEODE-1883) AuthInitializer should be made optional

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1883:
---
Assignee: (was: Jinmei Liao)

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: Improvement
>  Components: management, 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] [Updated] (GEODE-1883) AuthInitializer should be made optional

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1883:
---
Component/s: management

> AuthInitializer should be made optional
> ---
>
> Key: GEODE-1883
> URL: https://issues.apache.org/jira/browse/GEODE-1883
> Project: Geode
>  Issue Type: Improvement
>  Components: management, security
>Reporter: Swapnil Bawaskar
>Assignee: Jinmei Liao
>
> {{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)