[jira] [Created] (GEODE-1657) Source files should not contain Windows linefeeds

2016-07-11 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-1657:


 Summary: Source files should not contain Windows linefeeds
 Key: GEODE-1657
 URL: https://issues.apache.org/jira/browse/GEODE-1657
 Project: Geode
  Issue Type: Bug
  Components: general
Reporter: Kirk Lund


geode-pulse/src/test/java/com/vmware/gemfire/tools/pulse/tests/Server.java 
contains ^M (Windows linefeeds).



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


[jira] [Assigned] (GEODE-1657) Source files should not contain Windows linefeeds

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-1657:


Assignee: Kirk Lund

> Source files should not contain Windows linefeeds
> -
>
> Key: GEODE-1657
> URL: https://issues.apache.org/jira/browse/GEODE-1657
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> geode-pulse/src/test/java/com/vmware/gemfire/tools/pulse/tests/Server.java 
> contains ^M (Windows linefeeds).



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


[jira] [Created] (GEODE-1656) Fix compilation warnings

2016-07-11 Thread Grace Meilen (JIRA)
Grace Meilen created GEODE-1656:
---

 Summary: Fix compilation warnings
 Key: GEODE-1656
 URL: https://issues.apache.org/jira/browse/GEODE-1656
 Project: Geode
  Issue Type: Bug
  Components: general
Reporter: Grace Meilen


* Note: 
/Users/gmeilen/Desktop/open/extensions/geode-modules-session/src/test/java/com/gemstone/gemfire/modules/session/internal/filter/SessionReplicationIntegrationJUnitTest.java
 uses unchecked or unsafe operations.

* Note: 
/Users/gmeilen/Desktop/open/extensions/geode-modules-session/src/main/java/com/gemstone/gemfire/modules/session/installer/JarClassLoader.java
 uses or overrides a deprecated API.

* Note: 
/Users/gmeilen/Desktop/open/extensions/geode-modules-session-internal/src/main/java/com/gemstone/gemfire/modules/session/internal/filter/GemfireHttpSession.java
 uses or overrides a deprecated API.




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


[jira] [Assigned] (GEODE-1656) Fix compilation warnings

2016-07-11 Thread Grace Meilen (JIRA)

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

Grace Meilen reassigned GEODE-1656:
---

Assignee: Grace Meilen

> Fix compilation warnings
> 
>
> Key: GEODE-1656
> URL: https://issues.apache.org/jira/browse/GEODE-1656
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Grace Meilen
>Assignee: Grace Meilen
>
> * Note: 
> /Users/gmeilen/Desktop/open/extensions/geode-modules-session/src/test/java/com/gemstone/gemfire/modules/session/internal/filter/SessionReplicationIntegrationJUnitTest.java
>  uses unchecked or unsafe operations.
> * Note: 
> /Users/gmeilen/Desktop/open/extensions/geode-modules-session/src/main/java/com/gemstone/gemfire/modules/session/installer/JarClassLoader.java
>  uses or overrides a deprecated API.
> * Note: 
> /Users/gmeilen/Desktop/open/extensions/geode-modules-session-internal/src/main/java/com/gemstone/gemfire/modules/session/internal/filter/GemfireHttpSession.java
>  uses or overrides a deprecated API.



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


[jira] [Updated] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-1654:
-
Description: 
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
 warning - @return tag has no arguments.
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
 warning - @return tag has no arguments.
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
 warning - @return tag has no arguments.



  was:
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
 warning - @return tag has no arguments.
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
 warning - @return tag has no arguments.
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
 warning - @return tag has no arguments.
* geode-core/src/main/java/com/gemstone/gemfire/security/PostProcessor.java:44: 
warning - @return tag has no arguments.



> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>Priority: Trivial
>
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
>  warning - @return tag has no arguments.



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


[jira] [Updated] (GEODE-1655) CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener

2016-07-11 Thread Bruce Schuchardt (JIRA)

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

Bruce Schuchardt updated GEODE-1655:

Labels: ci  (was: )

> CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener
> --
>
> Key: GEODE-1655
> URL: https://issues.apache.org/jira/browse/GEODE-1655
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>  Labels: ci
>
> Failed 1 times in the last 30 runs. Stability: 96 %
> Error Message
> java.lang.AssertionError: expected:<1> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<0>
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:645)
>   at org.junit.Assert.assertEquals(Assert.java:631)
>   at 
> com.gemstone.gemfire.cache.client.internal.AutoConnectionSourceDUnitTest.testClientMembershipListener(AutoConnectionSourceDUnitTest.java:390)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> 

[jira] [Created] (GEODE-1655) CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener

2016-07-11 Thread Bruce Schuchardt (JIRA)
Bruce Schuchardt created GEODE-1655:
---

 Summary: CI failure: 
AutoConnectionSourceDUnitTest.testClientMembershipListener
 Key: GEODE-1655
 URL: https://issues.apache.org/jira/browse/GEODE-1655
 Project: Geode
  Issue Type: Bug
  Components: client/server
Reporter: Bruce Schuchardt


Failed 1 times in the last 30 runs. Stability: 96 %
Error Message

java.lang.AssertionError: expected:<1> but was:<0>

Stacktrace

java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at 
com.gemstone.gemfire.cache.client.internal.AutoConnectionSourceDUnitTest.testClientMembershipListener(AutoConnectionSourceDUnitTest.java:390)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at 

[jira] [Updated] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-1654:
-
Description: 
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
 warning - @return tag has no arguments.
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
 warning - @return tag has no arguments.
* 
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
 warning - @return tag has no arguments.
* geode-core/src/main/java/com/gemstone/gemfire/security/PostProcessor.java:44: 
warning - @return tag has no arguments.


  was:
* 
/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
 warning - @return tag has no arguments.
* 
/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
 warning - @return tag has no arguments.
* 
/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
 warning - @return tag has no arguments.
*/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/security/PostProcessor.java:44:
 warning - @return tag has no arguments.



> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>Priority: Trivial
>
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/security/PostProcessor.java:44: 
> warning - @return tag has no arguments.



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


[jira] [Updated] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-1654:
-
Description: 
* 
/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
 warning - @return tag has no arguments.
* 
/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
 warning - @return tag has no arguments.
* 
/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
 warning - @return tag has no arguments.
*/Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/security/PostProcessor.java:44:
 warning - @return tag has no arguments.


> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>Priority: Trivial
>
> * 
> /Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
>  warning - @return tag has no arguments.
> * 
> /Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
>  warning - @return tag has no arguments.
> * 
> /Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
>  warning - @return tag has no arguments.
> */Users/klund/dev/geode/geode-core/src/main/java/com/gemstone/gemfire/security/PostProcessor.java:44:
>  warning - @return tag has no arguments.



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


[jira] [Commented] (GEODE-1571) Client security should be able to use Resource:Operation permissions

2016-07-11 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-1571:


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

GEODE-1571: documentation and code cleanup


> Client security should be able to use Resource:Operation permissions
> 
>
> Key: GEODE-1571
> URL: https://issues.apache.org/jira/browse/GEODE-1571
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>
> While providing role based access control for JMX and CLI, noun-verby 
> permission of the form of RESOURCE:OPERATION[:REGION] have been introduced. 
> Please refer to the wiki for more details: 
> https://cwiki.apache.org/confluence/display/GEODE/How+to+secure+JMX+and+GFSH
> We now need to provide a new interface so that client-server security can 
> also use these noun-verby permissions.
> To make Geode security "integrated", users will only have to provide an 
> implementation of this new interface and it will work for JMX, gfsh and 
> client-server.
> {{com.gemstone.gemfire.security.AccessControl}} should be deprecated once we 
> have this new interface.



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


[jira] [Updated] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)

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

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

> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Priority: Trivial
>




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


[jira] [Created] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-1654:


 Summary: Fix javadoc warnings
 Key: GEODE-1654
 URL: https://issues.apache.org/jira/browse/GEODE-1654
 Project: Geode
  Issue Type: Bug
  Components: general
Reporter: Kirk Lund






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


[jira] [Updated] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)

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

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

> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Priority: Trivial
>




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


[jira] [Assigned] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message

2016-07-11 Thread Kevin Duling (JIRA)

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

Kevin Duling reassigned GEODE-746:
--

Assignee: Kevin Duling

> When starting a locator using --bind-address, gfsh prints incorrect connect 
> message
> ---
>
> Key: GEODE-746
> URL: https://issues.apache.org/jira/browse/GEODE-746
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1 
> --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like 
> this:
> {noformat}
> ..
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 
> is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
> -Dgemfire.load-cluster-configuration-from-dir=false 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the 
> locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind 
> address.



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


[jira] [Updated] (GEODE-1654) Fix javadoc warnings

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-1654:
-
Assignee: Grace Meilen

> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>Priority: Trivial
>




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


[jira] [Created] (GEODE-1653) Executing a fire-and-forget function on all servers doesn't actually execute on all servers

2016-07-11 Thread Barry Oglesby (JIRA)
Barry Oglesby created GEODE-1653:


 Summary: Executing a fire-and-forget function on all servers 
doesn't actually execute on all servers
 Key: GEODE-1653
 URL: https://issues.apache.org/jira/browse/GEODE-1653
 Project: Geode
  Issue Type: Bug
  Components: functions
Reporter: Barry Oglesby


Executing a fire-and-forget function on all servers only executes on the ones 
the client is currently connected to.

The two {{ExecuteFunctionNoAckOp execute}} methods get the servers to execute 
against using code like:
{noformat}
pool.getCurrentServers();
{noformat}
This method just gets all the {{EndpointManager's endpointMap's 
ServerLocations}}.

What should be done is more like what the {{ExecuteFunctionOp execute}} methods 
do:
{noformat}
private static List getAllServers(PoolImpl pool) {
  List servers = null;
  if (pool.getLocators() == null || pool.getLocators().isEmpty()) {
servers = ((ExplicitConnectionSourceImpl) 
pool.getConnectionSource()).getAllServers();
  } else {
servers = ((AutoConnectionSourceImpl) 
pool.getConnectionSource()).findAllServers(); // n/w call on locator
  }
  return servers;
}
{noformat}




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


[jira] [Resolved] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

2016-07-11 Thread Kevin Duling (JIRA)

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

Kevin Duling resolved GEODE-1617.
-
Resolution: Fixed

Added a test at creation for valid characters in region names for all 
non-internal regions.

> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



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


[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

2016-07-11 Thread ASF GitHub Bot (JIRA)

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

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

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/196
  
+1 This change causes Geode to enforce what the techpubs docs already say 
about Region names.



> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



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


[jira] [Commented] (GEODE-1598) gfsh auto-complete removes previously typed options

2016-07-11 Thread ASF GitHub Bot (JIRA)

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

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

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/195
  
+1 I started running tests against this change


> gfsh auto-complete removes previously typed options
> ---
>
> Key: GEODE-1598
> URL: https://issues.apache.org/jira/browse/GEODE-1598
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Swapnil Bawaskar
>Assignee: Grace Meilen
>
> This may also be related to fixing GEODE-835.
> When one starts typing in a gfsh command like:
> {noformat}
> gfsh>start server --name=serv1 --se
> {noformat}
> and then hit {{tab}} for autocompletion, the previously completed --name 
> option disappears and all I am left with is:
> {noformat}
> gfsh>start server --se
> {noformat}



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


[jira] [Commented] (GEODE-11) Lucene Integration

2016-07-11 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-11: GFSH commands for Lucene

Signed-off-by: Aparna Dharmakkan 

GEODE-11: Implementing GFSH command for listing lucene indexes.

Added the LuceneIndexCommands class that implements the list lucene index 
functionality in GFSH and the LuceneListIndexFunction class
that gets the information about lucene indexes from the cache. Also added a 
test to verify this functionality. The
org.springframework.shell.core.CommandMarker file is required to register the 
lucene commands in GFSH.

Signed-off-by: Gester Zhou 

GEODE-11: Adding JUnit test for LuceneIndexCommands

Added a JUnit test for getIndexListing()
Signed-off-by: Gester Zhou 

Adding a unit test for list lucene indexes gfsh command
Signed-off-by: Gester Zhou 

GEODE-11 Adding lucene create index gfsh command

Added lucene create index command and dunit tests.

Signed-off-by: Aparna Dharmakkan 

GEODE-11: Create lucene index gfsh command

Added a GFSH command to create a lucene index. Added DUnit and JUnit tests. 
Also added JUnit test for LucenListIndexFunction.
Made changes according to review comments.

Signed-off-by: Gester Zhou 

GEODE-1652: merge pull request 190, fix the conflicts

This closes #190


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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


[jira] [Commented] (GEODE-11) Lucene Integration

2016-07-11 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-11: GFSH commands for Lucene

Signed-off-by: Aparna Dharmakkan 

GEODE-11: Implementing GFSH command for listing lucene indexes.

Added the LuceneIndexCommands class that implements the list lucene index 
functionality in GFSH and the LuceneListIndexFunction class
that gets the information about lucene indexes from the cache. Also added a 
test to verify this functionality. The
org.springframework.shell.core.CommandMarker file is required to register the 
lucene commands in GFSH.

Signed-off-by: Gester Zhou 

GEODE-11: Adding JUnit test for LuceneIndexCommands

Added a JUnit test for getIndexListing()
Signed-off-by: Gester Zhou 

Adding a unit test for list lucene indexes gfsh command
Signed-off-by: Gester Zhou 

GEODE-11 Adding lucene create index gfsh command

Added lucene create index command and dunit tests.

Signed-off-by: Aparna Dharmakkan 

GEODE-11: Create lucene index gfsh command

Added a GFSH command to create a lucene index. Added DUnit and JUnit tests. 
Also added JUnit test for LucenListIndexFunction.
Made changes according to review comments.

Signed-off-by: Gester Zhou 

GEODE-1652: merge pull request 190, fix the conflicts

This closes #190


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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


[jira] [Assigned] (GEODE-1652) commit pull request 190 into develop

2016-07-11 Thread xiaojian zhou (JIRA)

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

xiaojian zhou reassigned GEODE-1652:


Assignee: xiaojian zhou

> commit pull request 190 into develop
> 
>
> Key: GEODE-1652
> URL: https://issues.apache.org/jira/browse/GEODE-1652
> Project: Geode
>  Issue Type: New Feature
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>
> The pull request contains gfsh command lucene list index and create index, 
> including dunit tests and junit tests. 



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


[jira] [Created] (GEODE-1652) commit pull request 190 into develop

2016-07-11 Thread xiaojian zhou (JIRA)
xiaojian zhou created GEODE-1652:


 Summary: commit pull request 190 into develop
 Key: GEODE-1652
 URL: https://issues.apache.org/jira/browse/GEODE-1652
 Project: Geode
  Issue Type: New Feature
Reporter: xiaojian zhou


The pull request contains gfsh command lucene list index and create index, 
including dunit tests and junit tests. 



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


[jira] [Updated] (GEODE-1598) gfsh auto-complete removes previously typed options

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-1598:
-
Fix Version/s: (was: 1.0.0-incubating.M3)

> gfsh auto-complete removes previously typed options
> ---
>
> Key: GEODE-1598
> URL: https://issues.apache.org/jira/browse/GEODE-1598
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Swapnil Bawaskar
>Assignee: Grace Meilen
>
> This may also be related to fixing GEODE-835.
> When one starts typing in a gfsh command like:
> {noformat}
> gfsh>start server --name=serv1 --se
> {noformat}
> and then hit {{tab}} for autocompletion, the previously completed --name 
> option disappears and all I am left with is:
> {noformat}
> gfsh>start server --se
> {noformat}



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


[jira] [Reopened] (GEODE-1598) gfsh auto-complete removes previously typed options

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund reopened GEODE-1598:
--

Some commands are misbehaving and deleting specified options when hitting tab 
for auto-complete.

gfsh> put --key="key1" --

becomes

gfsh> put --

The get command behaves similarly.


> gfsh auto-complete removes previously typed options
> ---
>
> Key: GEODE-1598
> URL: https://issues.apache.org/jira/browse/GEODE-1598
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Swapnil Bawaskar
>Assignee: Grace Meilen
> Fix For: 1.0.0-incubating.M3
>
>
> This may also be related to fixing GEODE-835.
> When one starts typing in a gfsh command like:
> {noformat}
> gfsh>start server --name=serv1 --se
> {noformat}
> and then hit {{tab}} for autocompletion, the previously completed --name 
> option disappears and all I am left with is:
> {noformat}
> gfsh>start server --se
> {noformat}



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


[jira] [Updated] (GEODE-1598) gfsh auto-complete removes previously typed options

2016-07-11 Thread Kirk Lund (JIRA)

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

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

> gfsh auto-complete removes previously typed options
> ---
>
> Key: GEODE-1598
> URL: https://issues.apache.org/jira/browse/GEODE-1598
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Swapnil Bawaskar
>Assignee: Grace Meilen
> Fix For: 1.0.0-incubating.M3
>
>
> This may also be related to fixing GEODE-835.
> When one starts typing in a gfsh command like:
> {noformat}
> gfsh>start server --name=serv1 --se
> {noformat}
> and then hit {{tab}} for autocompletion, the previously completed --name 
> option disappears and all I am left with is:
> {noformat}
> gfsh>start server --se
> {noformat}



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


[jira] [Resolved] (GEODE-1452) Annotate disabled test methods with @Ignore

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-1452.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> Annotate disabled test methods with @Ignore
> ---
>
> Key: GEODE-1452
> URL: https://issues.apache.org/jira/browse/GEODE-1452
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Grace Meilen
> Fix For: 1.0.0-incubating
>
>
> Some of the older tests have test methods which were disabled by renaming the 
> test method from JUnit 3 syntax to something like "public void _testMethod" 
> or "public void disabled_testMethod".
> Most of these tests were then updated to JUnit 4, but the disabled tests 
> remain without @Ignore or @Test annotations.
> We should annotate these test methods with @Ignore and @Test so they are 
> correctly counted as skipped tests. Tickets should then be filed to analyze 
> whether these tests should be fixed or deleted.



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


[jira] [Updated] (GEODE-1452) Annotate disabled test methods with @Ignore

2016-07-11 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-1452:
-
Assignee: Grace Meilen  (was: Kirk Lund)

> Annotate disabled test methods with @Ignore
> ---
>
> Key: GEODE-1452
> URL: https://issues.apache.org/jira/browse/GEODE-1452
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Grace Meilen
> Fix For: 1.0.0-incubating
>
>
> Some of the older tests have test methods which were disabled by renaming the 
> test method from JUnit 3 syntax to something like "public void _testMethod" 
> or "public void disabled_testMethod".
> Most of these tests were then updated to JUnit 4, but the disabled tests 
> remain without @Ignore or @Test annotations.
> We should annotate these test methods with @Ignore and @Test so they are 
> correctly counted as skipped tests. Tickets should then be filed to analyze 
> whether these tests should be fixed or deleted.



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


[jira] [Commented] (GEODE-1452) Annotate disabled test methods with @Ignore

2016-07-11 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-1452:


Commit 48f6e6ec56184eb92ddc4ccd75275dcb6fedecd7 in incubator-geode's branch 
refs/heads/develop from gmeilen
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=48f6e6e ]

GEODE-1452: annotate disabled tests with @Ignore and rename

This closes #184


> Annotate disabled test methods with @Ignore
> ---
>
> Key: GEODE-1452
> URL: https://issues.apache.org/jira/browse/GEODE-1452
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Some of the older tests have test methods which were disabled by renaming the 
> test method from JUnit 3 syntax to something like "public void _testMethod" 
> or "public void disabled_testMethod".
> Most of these tests were then updated to JUnit 4, but the disabled tests 
> remain without @Ignore or @Test annotations.
> We should annotate these test methods with @Ignore and @Test so they are 
> correctly counted as skipped tests. Tickets should then be filed to analyze 
> whether these tests should be fixed or deleted.



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


[jira] [Commented] (GEODE-1452) Annotate disabled test methods with @Ignore

2016-07-11 Thread ASF GitHub Bot (JIRA)

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

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

Github user asfgit closed the pull request at:

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


> Annotate disabled test methods with @Ignore
> ---
>
> Key: GEODE-1452
> URL: https://issues.apache.org/jira/browse/GEODE-1452
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Some of the older tests have test methods which were disabled by renaming the 
> test method from JUnit 3 syntax to something like "public void _testMethod" 
> or "public void disabled_testMethod".
> Most of these tests were then updated to JUnit 4, but the disabled tests 
> remain without @Ignore or @Test annotations.
> We should annotate these test methods with @Ignore and @Test so they are 
> correctly counted as skipped tests. Tickets should then be filed to analyze 
> whether these tests should be fixed or deleted.



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


[jira] [Commented] (GEODE-1646) Repackage New Security Classes Under org.apache.geode

2016-07-11 Thread ASF GitHub Bot (JIRA)

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

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

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/193
  
+1 Running tests on this PR.


> Repackage New Security Classes Under org.apache.geode
> -
>
> Key: GEODE-1646
> URL: https://issues.apache.org/jira/browse/GEODE-1646
> Project: Geode
>  Issue Type: Wish
>  Components: security
>Reporter: Grace Meilen
>Assignee: Grace Meilen
>
> Repackage New Security Classes Under org.apache.geode



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


[jira] [Assigned] (GEODE-1644) ClassCastException is thrown with in queries against a map index

2016-07-11 Thread Jason Huynh (JIRA)

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

Jason Huynh reassigned GEODE-1644:
--

Assignee: Jason Huynh

> ClassCastException is thrown with in queries against a map index
> 
>
> Key: GEODE-1644
> URL: https://issues.apache.org/jira/browse/GEODE-1644
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> When a query with an in clause is used and queries against a map index, a 
> ClassCastException is thrown.  A map index expects an array where the first 
> key is the index key and the second value is the map index key.



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


[jira] [Commented] (GEODE-1588) Starting and stopping wan sender can cause OOME

2016-07-11 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-1588:


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

GEODE-1588: AckReader and Dispatching thread are shut down before sending 
gateway sender close connection messages

* There was an issue where the gateway sender thread was reading off the same 
socket as the ack reader.
Instead, we force the ack reader thread to stop first, and close the 
inputstream to prevent reading garbled data
* Another issue was the ack reader thread was being spun up after being shut 
down.  Now we prevent the dispatching thread
from doing so by checking to see if it is being shut down.


> Starting and stopping wan sender can cause OOME 
> 
>
> Key: GEODE-1588
> URL: https://issues.apache.org/jira/browse/GEODE-1588
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> The following test will more than likely cause an OOME due to a timing issue 
> in stopping the gateway sender.
> {noformat}
> public void 
> closingSenderWhileBatchOperationsAreProcessingShouldNotHaveMultipleThreadsReadFromSameStream()
>  throws Exception {
> Integer lnPort = (Integer)vm0.invoke(() -> 
> WANTestBase.createFirstLocatorWithDSId( 1 ));
> Integer nyPort = (Integer)vm1.invoke(() -> 
> WANTestBase.createFirstRemoteLocator( 2, lnPort ));
> createCacheInVMs(nyPort, vm2);
> createReceiverInVMs(vm2);
> createCacheInVMs(lnPort, vm4);
> //keep the maxQueueMemory low enough to trigger eviction
> vm4.invoke(() -> WANTestBase.createConcurrentSender( "ln", 2,
>   false, 100, 101, false, false, null, true, 3, OrderPolicy.KEY ));
> vm2.invoke(() -> WANTestBase.createPartitionedRegion(
>   getTestMethodName() + "_RR", null, 0, 10, isOffHeap() ));
> //vm2.invoke(() -> WANTestBase.createPartitionedRegion(
> //  getTestMethodName() + "_RR", null, 0, 10, isOffHeap() ));
> startSenderInVMs("ln", vm4);
> vm2.invoke(() -> addListenerToSleepAfterCreateEvent(10, 
> getTestMethodName() + "_RR"));
> //vm4.invoke(() -> WANTestBase.createPartitionedRegion(
> //  getTestMethodName() + "_RR", null, 0, 10, isOffHeap() ));
> vm4.invoke(() -> WANTestBase.createReplicatedRegion(
>   getTestMethodName() + "_RR", "ln", isOffHeap() ));
> vm4.invoke(() -> addListenerToSleepAfterCreateEvent(1, 
> getTestMethodName() + "_RR"));
> vm4.invokeAsync(() -> WANTestBase.doPutsAfter300(
>   getTestMethodName() + "_RR", 100 ));
> Thread.sleep(5000);
> stopSenderInVMsAsync("ln", vm4);
> Thread.sleep(1);
> for (int i = 0; i < 100; i++) {
>   startSenderInVMs("ln", vm4);
>   Thread.sleep(1);
>   stopSenderInVMs("ln", vm4);
>   Thread.sleep(5000);
> }
> //
> //stopSenderInVMsAsync("ln", vm4);
> //Thread.sleep(1000);
> //startSenderInVMs("ln", vm4);
> //Thread.sleep(1000);
> vm2.invoke(() -> WANTestBase.validateRegionSize(
>   getTestMethodName() + "_RR", 1, 24));
>   }
> {noformat}
> Due to the way this test is written, I wouldn't necessarily want it checked 
> in as it is very time based and possibly flakey.  It will run into the OOME 
> eventually but it's all based on timing.
> The issue is that the ack reader thread is reading off the same socket as the 
> gateway sender closing thread, which causes the stream to be corrupted.



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


[jira] [Commented] (GEODE-1639) testStartGatewayReceiver_MultipleGroup setting same port number to two different receivers

2016-07-11 Thread ASF GitHub Bot (JIRA)

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

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

GitHub user nabarunnag opened a pull request:

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

GEODE-1639: Receivers selects a different port if the selected port is in 
use.



* If the selected port is in use then the receiver will select another 
port between 20001 and 2

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

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

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

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


commit 4f27c5736996c42b64dd93f5139fc68d22b646e9
Author: nabarun 
Date:   2016-07-06T23:34:03Z

GEODE-1639: Receivers selects a different port if the selected port is in 
use.

* If the selected port is in use then the receiver will select another 
port between 20001 and 2




> testStartGatewayReceiver_MultipleGroup setting same port number to two 
> different receivers
> --
>
> Key: GEODE-1639
> URL: https://issues.apache.org/jira/browse/GEODE-1639
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>
> {noformat}
> [info 2016/07/01 06:40:34.375 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.375 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.376 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.376 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.377 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.377 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.378 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.378 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.378 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.379 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.379 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.379 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.380 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.380 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.381 UTC  
> tid=0x13] Received method: com.gemstone.gemfire.test.dunit.NamedRunnable.run 
> with 0 args on object: runnable(setupVM)
> [info 2016/07/01 06:40:34.381 UTC  
> tid=0x13] Got result: null
>  from com.gemstone.gemfire.test.dunit.NamedRunnable.run with 0 args on 
> object: runnable(setupVM) (took 0 ms)
> [info 2016/07/01 06:40:34.385 UTC  
> tid=0x13] Received method: 
> com.gemstone.gemfire.internal.cache.wan.wancommand.WANCommandTestBase$1.run 
> with 0 args on object: "Enable Management"
> [info 2016/07/01 06:40:34.385 UTC  
> tid=0x13] Got result: null
>  from 
> com.gemstone.gemfire.internal.cache.wan.wancommand.WANCommandTestBase$1.run 
> with 0 args on object: "Enable Management" (took 0 ms)
> [info 2016/07/01 06:40:34.389 UTC  
> tid=0x13] Received method: 
> 

[jira] [Commented] (GEODE-1571) Client security should be able to use Resource:Operation permissions

2016-07-11 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on GEODE-1571:


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

GEODE-1571: security code tidy up.

* add close method in post processor
* have GeodeSecurityUtil.close close more resources.
* deprecate the old security api
* Ignore internal message tests


> Client security should be able to use Resource:Operation permissions
> 
>
> Key: GEODE-1571
> URL: https://issues.apache.org/jira/browse/GEODE-1571
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>
> While providing role based access control for JMX and CLI, noun-verby 
> permission of the form of RESOURCE:OPERATION[:REGION] have been introduced. 
> Please refer to the wiki for more details: 
> https://cwiki.apache.org/confluence/display/GEODE/How+to+secure+JMX+and+GFSH
> We now need to provide a new interface so that client-server security can 
> also use these noun-verby permissions.
> To make Geode security "integrated", users will only have to provide an 
> implementation of this new interface and it will work for JMX, gfsh and 
> client-server.
> {{com.gemstone.gemfire.security.AccessControl}} should be deprecated once we 
> have this new interface.



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


[jira] [Updated] (GEODE-1651) CI Failure: IntegratedClientSizeAuthDistributedTest.testSize

2016-07-11 Thread Kenneth Howe (JIRA)

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

Kenneth Howe updated GEODE-1651:

Labels: ci  (was: )

> CI Failure: IntegratedClientSizeAuthDistributedTest.testSize
> 
>
> Key: GEODE-1651
> URL: https://issues.apache.org/jira/browse/GEODE-1651
> Project: Geode
>  Issue Type: Bug
>  Components: security
>Reporter: Kenneth Howe
>  Labels: ci
>
> From Geode_develop_DistributedTests Jenkins build #3221
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155)
>   at 
> com.gemstone.gemfire.security.IntegratedClientSizeAuthDistributedTest.testSize(IntegratedClientSizeAuthDistributedTest.java:48)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.GeneratedMethodAccessor265.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:109)
>   at sun.reflect.GeneratedMethodAccessor264.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> 

[jira] [Updated] (GEODE-1649) CI Failure: TXManagerImplTest.testTxStateWithCommittedTx

2016-07-11 Thread Kenneth Howe (JIRA)

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

Kenneth Howe updated GEODE-1649:

Description: 
>From Geode-nightly Jenkins build 525:

java.lang.IllegalStateException: TXLockService cannot be created until 
connected to distributed system.
at 
com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.(TXLockServiceImpl.java:81)
at 
com.gemstone.gemfire.internal.cache.locks.TXLockService.createDTLS(TXLockService.java:54)
at 
com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:97)
at 
com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:126)
at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:790)
at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:479)
at 
com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:248)
at 
com.gemstone.gemfire.internal.cache.TXManagerImplTest.testTxStateWithCommittedTx(TXManagerImplTest.java:255)
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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor5.invoke(Unknown Source)
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 
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
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 
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at 
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


  was:
>From Geode-nightly build 525:


[jira] [Updated] (GEODE-1650) CI Failure: TXManagerImplTest.getLockAfterTXStateCommitted

2016-07-11 Thread Kenneth Howe (JIRA)

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

Kenneth Howe updated GEODE-1650:

Labels: ci  (was: )

> CI Failure: TXManagerImplTest.getLockAfterTXStateCommitted
> --
>
> Key: GEODE-1650
> URL: https://issues.apache.org/jira/browse/GEODE-1650
> Project: Geode
>  Issue Type: Bug
>Reporter: Kenneth Howe
>  Labels: ci
>
> From Geode-nightly Jenkins build 525
> java.lang.AssertionError: expected null, but was: txId:TXId: null:0 realDeal:class 
> com.gemstone.gemfire.internal.cache.TXState@492526634 
> onBehalfOfRemoteStub:true isJTA:false>
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotNull(Assert.java:755)
>   at org.junit.Assert.assertNull(Assert.java:737)
>   at org.junit.Assert.assertNull(Assert.java:747)
>   at 
> com.gemstone.gemfire.internal.cache.TXManagerImplTest.getLockAfterTXStateCommitted(TXManagerImplTest.java:186)
>   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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor5.invoke(Unknown Source)
>   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 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>   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 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 

[jira] [Created] (GEODE-1650) CI Failure: TXManagerImplTest.getLockAfterTXStateCommitted

2016-07-11 Thread Kenneth Howe (JIRA)
Kenneth Howe created GEODE-1650:
---

 Summary: CI Failure: TXManagerImplTest.getLockAfterTXStateCommitted
 Key: GEODE-1650
 URL: https://issues.apache.org/jira/browse/GEODE-1650
 Project: Geode
  Issue Type: Bug
Reporter: Kenneth Howe


>From Geode-nightly Jenkins build 525

java.lang.AssertionError: expected null, but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at 
com.gemstone.gemfire.internal.cache.TXManagerImplTest.getLockAfterTXStateCommitted(TXManagerImplTest.java:186)
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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor5.invoke(Unknown Source)
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 
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
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 
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at 
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)




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


[jira] [Created] (GEODE-1649) CI Failure: TXManagerImplTest.testTxStateWithCommittedTx

2016-07-11 Thread Kenneth Howe (JIRA)
Kenneth Howe created GEODE-1649:
---

 Summary: CI Failure: TXManagerImplTest.testTxStateWithCommittedTx
 Key: GEODE-1649
 URL: https://issues.apache.org/jira/browse/GEODE-1649
 Project: Geode
  Issue Type: Bug
  Components: transactions
Reporter: Kenneth Howe


>From Geode-nightly build 525:

java.lang.IllegalStateException: TXLockService cannot be created until 
connected to distributed system.
at 
com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.(TXLockServiceImpl.java:81)
at 
com.gemstone.gemfire.internal.cache.locks.TXLockService.createDTLS(TXLockService.java:54)
at 
com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:97)
at 
com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:126)
at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:790)
at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:479)
at 
com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:248)
at 
com.gemstone.gemfire.internal.cache.TXManagerImplTest.testTxStateWithCommittedTx(TXManagerImplTest.java:255)
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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor5.invoke(Unknown Source)
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 
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
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 
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] [Updated] (GEODE-1649) CI Failure: TXManagerImplTest.testTxStateWithCommittedTx

2016-07-11 Thread Kenneth Howe (JIRA)

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

Kenneth Howe updated GEODE-1649:

Labels: ci  (was: )

> CI Failure: TXManagerImplTest.testTxStateWithCommittedTx
> 
>
> Key: GEODE-1649
> URL: https://issues.apache.org/jira/browse/GEODE-1649
> Project: Geode
>  Issue Type: Bug
>  Components: transactions
>Reporter: Kenneth Howe
>  Labels: ci
>
> From Geode-nightly build 525:
> java.lang.IllegalStateException: TXLockService cannot be created until 
> connected to distributed system.
>   at 
> com.gemstone.gemfire.internal.cache.locks.TXLockServiceImpl.(TXLockServiceImpl.java:81)
>   at 
> com.gemstone.gemfire.internal.cache.locks.TXLockService.createDTLS(TXLockService.java:54)
>   at 
> com.gemstone.gemfire.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:97)
>   at 
> com.gemstone.gemfire.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:126)
>   at com.gemstone.gemfire.internal.cache.TXState.cleanup(TXState.java:790)
>   at com.gemstone.gemfire.internal.cache.TXState.commit(TXState.java:479)
>   at 
> com.gemstone.gemfire.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:248)
>   at 
> com.gemstone.gemfire.internal.cache.TXManagerImplTest.testTxStateWithCommittedTx(TXManagerImplTest.java:255)
>   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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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.GeneratedMethodAccessor5.invoke(Unknown Source)
>   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 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>   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 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> 

[jira] [Updated] (GEODE-1643) The new SecurityManager need to authenticate the gateway sender/receiver as well.

2016-07-11 Thread Swapnil Bawaskar (JIRA)

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

Swapnil Bawaskar updated GEODE-1643:

Issue Type: Sub-task  (was: New Feature)
Parent: GEODE-17

> The new SecurityManager need to authenticate the gateway sender/receiver as 
> well.
> -
>
> Key: GEODE-1643
> URL: https://issues.apache.org/jira/browse/GEODE-1643
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Jinmei Liao
>




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