Build failed in Jenkins: Geode-nightly-flaky #37

2017-06-16 Thread Apache Jenkins Server
See 


Changes:

[eshu] GEODE-2301: Deprecate JTA transaction manager from Geode

[boglesby] GEODE-3072: Changed getMembershipId to use the client version

[jiliao] GEODE-2632: consolidate different types of SecurityService

[kmiller] GEODE-2301 Doc note to deprecate Geode JTA trans mgr

[boglesby] GEODE-3072: Ignore dunit test

[boglesby] GEODE-3072: Ignore dunit test

[dbarnes] GEODE-2854: GEODE REST API Docs Missing Authentication This closes 
#583

--
[...truncated 96.68 KB...]
:geode-core:signArchives SKIPPED
:geode-core:webJar
:geode-cq:jar
:geode-cq:javadoc
:geode-cq:javadocJar
:geode-cq:sourcesJar
:geode-cq:signArchives SKIPPED
:geode-json:javadocJar
:geode-json:sourcesJar
:geode-json:signArchives SKIPPED
:geode-lucene:jar
:geode-lucene:javadoc
:geode-lucene:javadocJar
:geode-lucene:sourcesJar
:geode-lucene:signArchives SKIPPED
:geode-old-client-support:jar
:geode-old-client-support:javadoc
:geode-old-client-support:javadocJar
:geode-old-client-support:sourcesJar
:geode-old-client-support:signArchives SKIPPED
:geode-pulse:javadoc
:geode-pulse:javadocJar
:geode-pulse:sourcesJar
:geode-pulse:war
:geode-pulse:signArchives SKIPPED
:geode-rebalancer:jar
:geode-rebalancer:javadoc
:geode-rebalancer:javadocJar
:geode-rebalancer:sourcesJar
:geode-rebalancer:signArchives SKIPPED
:geode-wan:jar
:geode-wan:javadoc
:geode-wan:javadocJar
:geode-wan:sourcesJar
:geode-wan:signArchives SKIPPED
:geode-web:javadoc UP-TO-DATE
:geode-web:javadocJar
:geode-web:sourcesJar
:geode-web:war
:geode-web:signArchives SKIPPED
:geode-web-api:javadoc
:geode-web-api:javadocJar
:geode-web-api:sourcesJar
:geode-web-api:war
:geode-web-api:signArchives SKIPPED
:geode-assembly:installDist
:geode-pulse:jar
:geode-assembly:compileTestJavaNote: Some input files use or override a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-assembly:processTestResources
:geode-assembly:testClasses
:geode-assembly:flakyTest

org.apache.geode.management.internal.configuration.ClusterConfigurationServiceEndToEndDUnitTest
 > testStartServerAndExecuteCommands FAILED
java.lang.AssertionError: Suspicious strings were written to the log during 
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1979

[error 2017/06/17 03:52:22.497 UTC  tid=62] The disk 
volume ds1 for disk store ds1 has exceeded the critical usage threshold and is 
93% full

---
Found suspect string in log4j at line 1981

[error 2017/06/17 03:52:22.498 UTC  tid=62] A 
DiskAccessException has occurred while writing to the disk for disk store ds1. 
The cache will be closed.
org.apache.geode.cache.DiskAccessException: For DiskStore: ds1: Critical 
disk usage threshold exceeded for volume 
:
 93% full
at 
org.apache.geode.internal.cache.DiskStoreMonitor$DirectoryHolderUsage.handleStateChange(DiskStoreMonitor.java:388)
at 
org.apache.geode.internal.cache.DiskStoreMonitor$DiskUsage.update(DiskStoreMonitor.java:297)
at 
org.apache.geode.internal.cache.DiskStoreMonitor.checkUsage(DiskStoreMonitor.java:201)
at 
org.apache.geode.internal.cache.DiskStoreMonitor.access$000(DiskStoreMonitor.java:39)
at 
org.apache.geode.internal.cache.DiskStoreMonitor$2.run(DiskStoreMonitor.java:135)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
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:748)

1 test completed, 1 failed
:geode-assembly:flakyTest FAILED
:geode-benchmarks:compileTestJava UP-TO-DATE
:geode-benchmarks:processTestResources UP-TO-DATE
:geode-benchmarks:testClasses UP-TO-DATE
:geode-benchmarks:flakyTest UP-TO-DATE
:geode-common:compileTestJava
:geode-common:processTestResources UP-TO-DATE
:geode-common:testClasses
:geode-common:flakyTest
:geode-core:flakyTest

org.apache.geode.distributed.LocatorUDPSecurityDUnitTest > testStartTwoLocators 
FAILED
org.apache.geode.test.dunit.RMIException: While invoking 

Build failed in Jenkins: Geode-nightly #868

2017-06-16 Thread Apache Jenkins Server
See 


Changes:

[eshu] GEODE-2301: Deprecate JTA transaction manager from Geode

[boglesby] GEODE-3072: Changed getMembershipId to use the client version

[jiliao] GEODE-2632: consolidate different types of SecurityService

--
[...truncated 53.05 KB...]
:extensions/geode-modules-session:spotlessJavaCheck
:extensions/geode-modules-session:spotlessCheck
:extensions/geode-modules-session:test
:extensions/geode-modules-session:check
:extensions/geode-modules-session:build
:extensions/geode-modules-session:distributedTest
:extensions/geode-modules-session:integrationTest
:extensions/geode-modules-session-internal:javadocJar
:extensions/geode-modules-session-internal:sourcesJar
:extensions/geode-modules-session-internal:signArchives SKIPPED
:extensions/geode-modules-session-internal:assemble
:extensions/geode-modules-session-internal:compileTestJava UP-TO-DATE
:extensions/geode-modules-session-internal:processTestResources UP-TO-DATE
:extensions/geode-modules-session-internal:testClasses UP-TO-DATE
:extensions/geode-modules-session-internal:checkMissedTests UP-TO-DATE
:extensions/geode-modules-session-internal:spotlessJavaCheck
:extensions/geode-modules-session-internal:spotlessCheck
:extensions/geode-modules-session-internal:test UP-TO-DATE
:extensions/geode-modules-session-internal:check
:extensions/geode-modules-session-internal:build
:extensions/geode-modules-session-internal:distributedTest UP-TO-DATE
:extensions/geode-modules-session-internal:integrationTest UP-TO-DATE
:extensions/geode-modules-tomcat7:compileTestJava
:extensions/geode-modules-tomcat7:processTestResources
:extensions/geode-modules-tomcat7:testClasses
:extensions/geode-modules-tomcat7:checkMissedTests
:extensions/geode-modules-tomcat7:spotlessJavaCheck
:extensions/geode-modules-tomcat7:spotlessCheck
:extensions/geode-modules-tomcat7:test
:extensions/geode-modules-tomcat7:check
:extensions/geode-modules-tomcat7:build
:extensions/geode-modules-tomcat7:distributedTest
:extensions/geode-modules-tomcat7:integrationTest
:extensions/geode-modules-tomcat8:compileTestJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

:extensions/geode-modules-tomcat8:processTestResources
:extensions/geode-modules-tomcat8:testClasses
:extensions/geode-modules-tomcat8:checkMissedTests
:extensions/geode-modules-tomcat8:spotlessJavaCheck
:extensions/geode-modules-tomcat8:spotlessCheck
:extensions/geode-modules-tomcat8:test
:extensions/geode-modules-tomcat8:check
:extensions/geode-modules-tomcat8:build
:extensions/geode-modules-tomcat8:distributedTest
:extensions/geode-modules-tomcat8:integrationTest
:geode-assembly:compileJava UP-TO-DATE
:geode-assembly:processResources UP-TO-DATE
:geode-assembly:classes UP-TO-DATE
:geode-assembly:defaultCacheConfig
:geode-assembly:defaultDistributionConfig
:geode-assembly:depsJar
:geode-benchmarks:compileJava UP-TO-DATE
:geode-benchmarks:processResources UP-TO-DATE
:geode-benchmarks:classes UP-TO-DATE
:geode-cq:compileJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-cq:processResources
:geode-cq:classes
:geode-lucene:compileJavaNote: Some input files use or override a deprecated 
API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-lucene:processResources
:geode-lucene:classes
:geode-old-client-support:compileJavaNote: Some input files use or override a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.

:geode-old-client-support:processResources
:geode-old-client-support:classes
:geode-pulse:compileJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-pulse:copyGemFireVersionFile
:geode-pulse:processResources
:geode-pulse:classes
:geode-rebalancer:compileJava
:geode-rebalancer:processResources UP-TO-DATE
:geode-rebalancer:classes
:geode-wan:compileJava
:geode-wan:processResources
:geode-wan:classes
:geode-web:compileJava UP-TO-DATE
:geode-web:processResources UP-TO-DATE
:geode-web:classes UP-TO-DATE
:geode-web-api:compileJavaNote: Some input files use unchecked or unsafe 
operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-web-api:processResources
:geode-web-api:classes
:geode-assembly:docs
:geode-assembly:gfshDepsJar
:geode-common:javadocJar
:geode-common:sourcesJar
:geode-common:signArchives SKIPPED

[GitHub] geode pull request #591: GEODE-3073: Renamed OrderByComparatorUnmapped to Or...

2017-06-16 Thread YehEmily
GitHub user YehEmily opened a pull request:

https://github.com/apache/geode/pull/591

GEODE-3073: Renamed OrderByComparatorUnmapped to OrderByComparatorMapped

[View the JIRA ticket 
here.](https://issues.apache.org/jira/browse/GEODE-3073)

`OrderByComparatorUnmapped.java` actually uses mapping, which is why it 
should really be called `OrderByComparatorMapped.java`. Some refactoring was 
also done (similar to the refactoring done in [pull request 
#580](https://github.com/apache/geode/pull/580), although to a lesser extent).

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [ ] Does `gradlew build` run cleanly?

- [ ] Have you written or updated unit tests to verify your changes?

- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to dev@geode.apache.org.


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

$ git pull https://github.com/YehEmily/geode GEODE-3073-2

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

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


commit b915804d857fd3efd7fefe6af45a6a8c44745bed
Author: YehEmily 
Date:   2017-06-16T20:41:21Z

GEODE-3073: Renamed OrderByComparatorUnmapped to OrderByComparatorMapped 
and refactored the code a bit.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode issue #589: GEODE-393: Providing cache for FunctionContext

2017-06-16 Thread DivineEnder
Github user DivineEnder commented on the issue:

https://github.com/apache/geode/pull/589
  
@ladyVader @nabarunnag @boglesby @jhuynh1 @upthewaterspout @gesterzhou 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode pull request #589: GEODE-393: Providing cache for FunctionContext

2017-06-16 Thread DivineEnder
GitHub user DivineEnder opened a pull request:

https://github.com/apache/geode/pull/589

GEODE-393: Providing cache for FunctionContext

Added the ability to pass a Cache to a function context as well as tests to 
check for this.

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [ ] Does `gradlew build` run cleanly?

- [ ] Have you written or updated unit tests to verify your changes?

- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to dev@geode.apache.org.


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

$ git pull https://github.com/DivineEnder/geode feature/GEODE-393

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

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


commit ec1047c56ebc9f92e7b521bd765286fbed09af59
Author: David Anuta 
Date:   2017-06-16T23:05:24Z

GEODE-393: Providing cache for FunctionContext

Added the ability to pass a Cache to a function context as well as tests to 
check for this.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode pull request #590: GEODE-3090: Fixing gfsh help message (and a lot of ...

2017-06-16 Thread YehEmily
GitHub user YehEmily opened a pull request:

https://github.com/apache/geode/pull/590

GEODE-3090: Fixing gfsh help message (and a lot of other typos)

[View the original JIRA ticket 
here.](https://issues.apache.org/jira/browse/GEODE-3090)

The original ticket called for fixing a typo in `CliStrings.java`, and in 
the process, other typos were fixed.

**_Precheckin status: in progress_**

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [ ] Does `gradlew build` run cleanly?

- [ ] Have you written or updated unit tests to verify your changes?

- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to dev@geode.apache.org.


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

$ git pull https://github.com/YehEmily/geode GEODE-3090

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

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


commit b40874852c47c38b4b5c790f6eef6c1df53a04d1
Author: YehEmily 
Date:   2017-06-16T22:49:53Z

GEODE-3090: Fixing gfsh help message (and a lot of other typos)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Broken: apache/geode#2906 (develop - 4bf80a6)

2017-06-16 Thread Travis CI
Build Update for apache/geode
-

Build: #2906
Status: Broken

Duration: 9 minutes and 59 seconds
Commit: 4bf80a6 (develop)
Author: Barry Oglesby
Message: GEODE-3072: Ignore dunit test

View the changeset: 
https://github.com/apache/geode/compare/42350f1ac3a5...4bf80a6a9236

View the full build log and details: 
https://travis-ci.org/apache/geode/builds/243830129?utm_source=email_medium=notification

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications



[GitHub] geode pull request #583: GEODE-2854: GEODE REST API Docs Missing Authenticat...

2017-06-16 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/geode/pull/583


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #587 was SUCCESSFUL (with 1868 tests)

2017-06-16 Thread Spring CI

---
Spring Data GemFire > Nightly-ApacheGeode > #587 was successful.
---
Scheduled
1870 tests in total.

https://build.spring.io/browse/SGF-NAG-587/





--
This message is automatically generated by Atlassian Bamboo

Re: Error running category tests due to RawLuceneRepositoryManagerJUnitTest

2017-06-16 Thread Kirk Lund
Or something like this for "Project compiler output" so that IntelliJ isn't
defaulting to overwriting the same class files as command-line gradle is:

File -> Project Structure -> Project -> Project compiler output:
/Users/klund/dev/geode/build-intellij/classes

Having IntelliJ output classes to "build" didn't work well for me.

On Fri, Jun 16, 2017 at 3:31 PM, Kirk Lund  wrote:

> I haven't seen this exact problem, but I've seen weird behavior if the
> command-line gradle build terminated before completing. I suggest
> completing a clean build on the command-line, then restart IntelliJ and
> maybe also edit Project Structure to tell IntelliJ to output classes to a
> different location than the gradle build:
>
> File -> Project Structure -> Project -> Project compiler
> output: /Users/klund/dev/gemfire/closed/build-intellij/classes (or
> whatever works for you)
>
> And then rebuild:
>
> Build -> Rebuild Project
>
> On Fri, Jun 16, 2017 at 2:03 PM, Bruce Schuchardt 
> wrote:
>
>> Has anyone else seen this in IntelliJ?
>>
>>
>> Exception in thread "main" java.lang.VerifyError: Bad type on operand
>> stack
>> Exception Details:
>>   Location:
>> org/apache/geode/cache/lucene/internal/RawLuceneRepositoryMa
>> nagerJUnitTest.createIndexAndRepoManager()V @7: putstatic
>>   Reason:
>> Type 'org/apache/geode/cache/lucene/internal/LuceneRawIndexFactory'
>> (current frame, stack[0]) is not assignable to
>> 'org/apache/geode/cache/lucene/internal/LuceneIndexImplFactory'
>>   Current Frame:
>> bci: @7
>> flags: { }
>> locals: { 'org/apache/geode/cache/lucene
>> /internal/RawLuceneRepositoryManagerJUnitTest' }
>> stack: { 'org/apache/geode/cache/lucene/internal/LuceneRawIndexFactory'
>> }
>>   Bytecode:
>> 0x000: bb00 1b59 b700 1cb3 001d 2a12 1eb8 0008
>> 0x010: c000 1eb5 001f 2a12 20b8 0008 c000 21b5
>> 0x020: 0022 2ab4 0022 b600 23b8 000d 2ab4 001f
>> 0x030: b900 0e02 0057 2ab4 0022 b600 24b8 000d
>> 0x040: bb00 2559 b700 26b9 000e 0200 572a b400
>> 0x050: 22b6 0027 b800 0d2a b400 06b9 000e 0200
>> 0x060: 572a b400 22b6 0028 b800 0d12 0fb9 000e
>> 0x070: 0200 572a b400 22b6 0029 b800 2ab8 000d
>> 0x080: 04b8 002a b900 0e02 0057 2abb 0019 592a
>> 0x090: b400 222a b400 16b7 002b b500 182a b400
>> 0x0a0: 18b6 002c 2ab4 0018 b600 2db1
>>
>> at java.lang.Class.getDeclaredMethods0(Native Method)
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>> at java.lang.Class.getMethod0(Class.java:3018)
>> at java.lang.Class.getMethod(Class.java:1784)
>> at org.junit.internal.builders.SuiteMethodBuilder.hasSuiteMetho
>> d(SuiteMethodBuilder.java:18)
>> at com.intellij.junit4.JUnit46ClassesRequestBuilder.collectWrap
>> pedRunners(JUnit46ClassesRequestBuilder.java:79)
>> at com.intellij.junit4.JUnit46ClassesRequestBuilder.getClassesR
>> equest(JUnit46ClassesRequestBuilder.java:51)
>> at com.intellij.junit4.JUnit4TestRunnerUtil.buildRequest(JUnit4
>> TestRunnerUtil.java:87)
>> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs
>> (JUnit4IdeaTestRunner.java:46)
>> at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.star
>> tRunnerWithArgs(IdeaTestRunner.java:51)
>> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsA
>> ndStart(JUnitStarter.java:242)
>> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStart
>> er.java:70)
>>
>>
>


Re: Error running category tests due to RawLuceneRepositoryManagerJUnitTest

2017-06-16 Thread Kirk Lund
I haven't seen this exact problem, but I've seen weird behavior if the
command-line gradle build terminated before completing. I suggest
completing a clean build on the command-line, then restart IntelliJ and
maybe also edit Project Structure to tell IntelliJ to output classes to a
different location than the gradle build:

File -> Project Structure -> Project -> Project compiler
output: /Users/klund/dev/gemfire/closed/build-intellij/classes (or whatever
works for you)

And then rebuild:

Build -> Rebuild Project

On Fri, Jun 16, 2017 at 2:03 PM, Bruce Schuchardt 
wrote:

> Has anyone else seen this in IntelliJ?
>
>
> Exception in thread "main" java.lang.VerifyError: Bad type on operand stack
> Exception Details:
>   Location:
> org/apache/geode/cache/lucene/internal/RawLuceneRepositoryMa
> nagerJUnitTest.createIndexAndRepoManager()V @7: putstatic
>   Reason:
> Type 'org/apache/geode/cache/lucene/internal/LuceneRawIndexFactory'
> (current frame, stack[0]) is not assignable to
> 'org/apache/geode/cache/lucene/internal/LuceneIndexImplFactory'
>   Current Frame:
> bci: @7
> flags: { }
> locals: { 
> 'org/apache/geode/cache/lucene/internal/RawLuceneRepositoryManagerJUnitTest'
> }
> stack: { 'org/apache/geode/cache/lucene/internal/LuceneRawIndexFactory'
> }
>   Bytecode:
> 0x000: bb00 1b59 b700 1cb3 001d 2a12 1eb8 0008
> 0x010: c000 1eb5 001f 2a12 20b8 0008 c000 21b5
> 0x020: 0022 2ab4 0022 b600 23b8 000d 2ab4 001f
> 0x030: b900 0e02 0057 2ab4 0022 b600 24b8 000d
> 0x040: bb00 2559 b700 26b9 000e 0200 572a b400
> 0x050: 22b6 0027 b800 0d2a b400 06b9 000e 0200
> 0x060: 572a b400 22b6 0028 b800 0d12 0fb9 000e
> 0x070: 0200 572a b400 22b6 0029 b800 2ab8 000d
> 0x080: 04b8 002a b900 0e02 0057 2abb 0019 592a
> 0x090: b400 222a b400 16b7 002b b500 182a b400
> 0x0a0: 18b6 002c 2ab4 0018 b600 2db1
>
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> at java.lang.Class.getMethod0(Class.java:3018)
> at java.lang.Class.getMethod(Class.java:1784)
> at org.junit.internal.builders.SuiteMethodBuilder.hasSuiteMetho
> d(SuiteMethodBuilder.java:18)
> at com.intellij.junit4.JUnit46ClassesRequestBuilder.collectWrap
> pedRunners(JUnit46ClassesRequestBuilder.java:79)
> at com.intellij.junit4.JUnit46ClassesRequestBuilder.getClassesR
> equest(JUnit46ClassesRequestBuilder.java:51)
> at com.intellij.junit4.JUnit4TestRunnerUtil.buildRequest(JUnit4
> TestRunnerUtil.java:87)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs
> (JUnit4IdeaTestRunner.java:46)
> at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.star
> tRunnerWithArgs(IdeaTestRunner.java:51)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsA
> ndStart(JUnitStarter.java:242)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStart
> er.java:70)
>
>


Error running category tests due to RawLuceneRepositoryManagerJUnitTest

2017-06-16 Thread Bruce Schuchardt

Has anyone else seen this in IntelliJ?


Exception in thread "main" java.lang.VerifyError: Bad type on operand stack
Exception Details:
  Location:
org/apache/geode/cache/lucene/internal/RawLuceneRepositoryManagerJUnitTest.createIndexAndRepoManager()V 
@7: putstatic

  Reason:
Type 'org/apache/geode/cache/lucene/internal/LuceneRawIndexFactory' 
(current frame, stack[0]) is not assignable to 
'org/apache/geode/cache/lucene/internal/LuceneIndexImplFactory'

  Current Frame:
bci: @7
flags: { }
locals: { 
'org/apache/geode/cache/lucene/internal/RawLuceneRepositoryManagerJUnitTest' 
}
stack: { 
'org/apache/geode/cache/lucene/internal/LuceneRawIndexFactory' }

  Bytecode:
0x000: bb00 1b59 b700 1cb3 001d 2a12 1eb8 0008
0x010: c000 1eb5 001f 2a12 20b8 0008 c000 21b5
0x020: 0022 2ab4 0022 b600 23b8 000d 2ab4 001f
0x030: b900 0e02 0057 2ab4 0022 b600 24b8 000d
0x040: bb00 2559 b700 26b9 000e 0200 572a b400
0x050: 22b6 0027 b800 0d2a b400 06b9 000e 0200
0x060: 572a b400 22b6 0028 b800 0d12 0fb9 000e
0x070: 0200 572a b400 22b6 0029 b800 2ab8 000d
0x080: 04b8 002a b900 0e02 0057 2abb 0019 592a
0x090: b400 222a b400 16b7 002b b500 182a b400
0x0a0: 18b6 002c 2ab4 0018 b600 2db1

at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
at java.lang.Class.getMethod0(Class.java:3018)
at java.lang.Class.getMethod(Class.java:1784)
at 
org.junit.internal.builders.SuiteMethodBuilder.hasSuiteMethod(SuiteMethodBuilder.java:18)
at 
com.intellij.junit4.JUnit46ClassesRequestBuilder.collectWrappedRunners(JUnit46ClassesRequestBuilder.java:79)
at 
com.intellij.junit4.JUnit46ClassesRequestBuilder.getClassesRequest(JUnit46ClassesRequestBuilder.java:51)
at 
com.intellij.junit4.JUnit4TestRunnerUtil.buildRequest(JUnit4TestRunnerUtil.java:87)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:46)
at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:51)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)




Re: Query for JMX "Async Event Queue properties"

2017-06-16 Thread Barry Oglesby
The AsynceEventQueueMBean is monitoring the AsyncEventQueueStats not the
PartitionedRegionStats. And, actually, the only stat being monitored by
that MBean is the eventQueueSize stat. The parallel AsyncEventQueue creates
a colocated PartitionedRegion under the covers, and the stats for that PR
are the PartitionedRegionStats you referenced. There isn't currently any
JMX support for those PartitionedRegionStats.

Are you looking to add support for those PartitionedRegionStats to the
AsynceEventQueueMBean? If so, I guess there are a few ways to do. The first
would be to find the underlying PartitionedRegion for the parallel
AsyncEventQueue, add its PartitionedRegionStats to the
AsyncEventQueueMBeanBridge's monitor and reference the appropriate one(s)
(in your case dataStoreBytesInUse). Another would be to actually create an
MBean for that internal PartitionedRegion.

Both of these would only be applicable for a parallel AsyncEventQueue.
Serial AsyncEventQueues don't create a PartitionedRegion.


Thanks,
Barry Oglesby


On Fri, Jun 16, 2017 at 5:38 AM, Dinesh Akhand  wrote:

> Hi Team
>
> Regarding the following metrics:
>
> /AsyncEventQueue_XYZ_PARALLEL_GATEWAY_SENDER_QUEUE:PartitionedRegionStats.
> dataStoreEntryCount
> /AsyncEventQueue_XYZ_PARALLEL_GATEWAY_SENDER_QUEUE:PartitionedRegionStats.
> dataStoreBytesInUse
>
>
> I found only count for async queue in JMX , it called here EventQueueSize
> = PartitionedRegionStats.dataStoreEntryCount
>
> /** AsyncEventQueue Stats **/
>   public static final String ASYNCEVENTQUEUE_EVENTS_QUEUE_SIZE =
> "eventQueueSize"
>
> we having Missing  PartitionedRegionStats.dataStoreBytesInUse in JMX for
> Async Qeueue.
>
> Can you help me , which property I need to map for it.
>
> Thanks,
> Dinesh Akhand
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>


[GitHub] geode pull request #588: GEODE-2820: Added awaitlity clause to wait for the ...

2017-06-16 Thread nabarunnag
GitHub user nabarunnag opened a pull request:

https://github.com/apache/geode/pull/588

GEODE-2820: Added awaitlity clause to wait for the region size to be …

…correct

* Added awaitility clause to wait for all the regions to have all the 
entries
* This is done to make sure that the queries are executed.
* This may not solve the issue of queries being executed before async 
index is updated
* However this shortens the window of failure happening.


Potential reviewers
@jhuynh1 

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [ ] Does `gradlew build` run cleanly?

- [ ] Have you written or updated unit tests to verify your changes?

- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to dev@geode.apache.org.


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

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

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

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


commit 61ebad2b6d8f2b06a69f1de669e1be49008b6136
Author: nabarun 
Date:   2017-06-15T23:32:46Z

GEODE-2820: Added awaitlity clause to wait for the region size to be correct

* Added awaitility clause to wait for all the regions to have all the 
entries
* This is done to make sure that the queries are executed.
* This may not solve the issue of queries being executed before async 
index is updated
* However this shortens the window of failure happening.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode issue #587: GEODE-2018: Added instantiators to SessionCachingFilter in...

2017-06-16 Thread DivineEnder
Github user DivineEnder commented on the issue:

https://github.com/apache/geode/pull/587
  
@ladyVader @nabarunnag @boglesby @jhuynh1 @upthewaterspout @gesterzhou 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode pull request #587: GEODE-2018: Added instantiators to SessionCachingFi...

2017-06-16 Thread DivineEnder
GitHub user DivineEnder opened a pull request:

https://github.com/apache/geode/pull/587

GEODE-2018: Added instantiators to SessionCachingFilter init method

Also removed unused registerInstantiator methods from 
GatewayDeltaCreateEvent,
GatewayDeltaDestroyEvent, and DeltaSessionDestroyAttrbiuteEvent classes.

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [ ] Does `gradlew build` run cleanly?

- [ ] Have you written or updated unit tests to verify your changes?

- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to dev@geode.apache.org.


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

$ git pull https://github.com/DivineEnder/geode feature/GEODE-2018

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

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


commit 917487bd593ed96d4135d6a057a1f172bd7e188e
Author: David Anuta 
Date:   2017-06-16T17:44:05Z

GEODE-2018: Added instantiators to SessionCachingFilter init method

Also removed unused registerInstantiator methods from 
GatewayDeltaCreateEvent,
GatewayDeltaDestroyEvent, and DeltaSessionDestroyAttrbiuteEvent classes.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Review Request 60157: GEODE-3075: initial work for feature flag and creation of a new subclass of `ServerConnection`.

2017-06-16 Thread Galen O'Sullivan

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60157/
---

Review request for geode, Alexander Murmann, Bruce Schuchardt, Hitesh Khamesra, 
Udo Kohlmeyer, and Brian Rowe.


Repository: geode


Description
---

Create `ServerConnectionFactory`, which creates either instances of 
`LegacyServerConnection` (identical in functionality to the old 
`ServerConnection`) or `NewProtocolServerConnection` (which is currently 
basically a stub, but will never get called unless a feature flag is set).

This is the initial work for GEODE-3074, and will allow us to continue to work 
on further tasks for that project.

An explicit goal with this PR is to not disturb any existing functionality. 
Unless a feature flag is set and a connection with a certain magic byte is 
received, server connections will work as before. If you see something that you 
think may break, please let me know.

Have a nice day!


Diffs
-

  
geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
 85f914637 
  
geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java 
5eaa5a4bd 
  geode-core/src/main/java/org/apache/geode/internal/cache/tier/Acceptor.java 
9a3241b05 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/AcceptorImpl.java
 2a8818cef 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/ClientHealthMonitor.java
 e0b5ab8b6 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/ClientProtocolMessageHandler.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/LegacyServerConnection.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/NewProtocolServerConnection.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/ServerConnection.java
 947b83652 
  
geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/ServerConnectionFactory.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/security/CallbackInstantiator.java
 2cb8d0817 
  
geode-core/src/main/java/org/apache/geode/internal/security/CustomSecurityService.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/security/DisabledSecurityService.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/security/IntegratedSecurityService.java
 171cfb71a 
  
geode-core/src/main/java/org/apache/geode/internal/security/LegacySecurityService.java
 c594bf932 
  
geode-core/src/main/java/org/apache/geode/internal/security/SecurityService.java
 feea8995d 
  
geode-core/src/main/java/org/apache/geode/internal/security/SecurityServiceFactory.java
 2e0ad956c 
  
geode-core/src/main/java/org/apache/geode/internal/security/SecurityServiceType.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/security/shiro/ConfigInitializer.java
 PRE-CREATION 
  
geode-core/src/main/java/org/apache/geode/internal/security/shiro/CustomAuthRealm.java
 0e5029bd0 
  
geode-core/src/main/java/org/apache/geode/internal/security/shiro/SecurityManagerProvider.java
 ad8e66e0c 
  
geode-core/src/test/java/org/apache/geode/distributed/internal/membership/MembershipJUnitTest.java
 b0e20d9b3 
  
geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/ServerConnectionFactoryIntegrationTest.java
 PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/ServerConnectionFactoryTest.java
 PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/internal/cache/tier/sockets/ServerConnectionTest.java
 794c61097 
  
geode-core/src/test/java/org/apache/geode/internal/security/DisabledSecurityServiceTest.java
 PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/internal/security/FakePostProcessor.java
 PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/internal/security/FakeSecurityManager.java
 PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/internal/security/IntegratedSecurityServiceConstructorTest.java
 afa007f31 
  
geode-core/src/test/java/org/apache/geode/internal/security/IntegratedSecurityServiceTest.java
 daaf18d3f 
  
geode-core/src/test/java/org/apache/geode/internal/security/LegacySecurityServiceTest.java
 bac79ec0e 
  
geode-core/src/test/java/org/apache/geode/internal/security/SecurityServiceFactoryShiroIntegrationTest.java
 e8548ed86 
  
geode-core/src/test/java/org/apache/geode/internal/security/SecurityServiceFactoryTest.java
 fc4447bb0 
  
geode-core/src/test/java/org/apache/geode/internal/security/SecurityServiceTest.java
 4b7bbfc5a 
  
geode-core/src/test/java/org/apache/geode/internal/security/shiro/ConfigInitializerIntegrationTest.java
 PRE-CREATION 
  

[GitHub] geode pull request #586: GEODE-3075: initial flow adding the new client prot...

2017-06-16 Thread galen-pivotal
GitHub user galen-pivotal opened a pull request:

https://github.com/apache/geode/pull/586

GEODE-3075: initial flow adding the new client protocol to core.

Create `ServerConnectionFactory`, which creates either instances of 
LegacyServerConnection (identical in functionality to the old 
`ServerConnection`) or `NewProtocolServerConnection` (which is currently 
basically a stub, but will never get called unless a feature flag is set).

This is the initial work for GEODE-3074, and will allow us to continue to 
work on further tasks for that project.

An explicit goal with this PR is to not disturb any existing functionality. 
Unless a feature flag is set *and* a connection with a certain magic byte is 
received, server connections will work as before. If you see something that you 
think may break, please let me know.

Have a nice day!


Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?

- [ ] Is your initial contribution a single, squashed commit?

- [x] Does `gradlew build` run cleanly?

- [x] Have you written or updated unit tests to verify your changes?

- [n/a] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and
submit an update to your PR as soon as possible. If you need help, please 
send an
email to dev@geode.apache.org.


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

$ git pull https://github.com/galen-pivotal/geode feature/GEODE-3075

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

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


commit 61b2c2746ea7128a5aafec7469c23fc6417f283a
Author: Galen OSullivan 
Date:   2017-06-12T16:33:35Z

GEODE-3075: Initial refactor adding NewProtocolServerConnection

subclassing `ServerConnection`.

The new code is broken but it won't be called under normal operation,
since it's gated on a system property, "geode.feature-protobuf-protocol"

Further refactoring and feature work to come.

commit 649f4d31fd78d5301c13d29f7cd10481fda824b2
Author: Galen OSullivan 
Date:   2017-06-16T16:59:11Z

GEODE-3075: Add an integration test for the ServerConnectionFactory

the current implementation is bogus, but does test that the flow works.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode pull request #585: GEODE-3091: remove empty method

2017-06-16 Thread nreich
GitHub user nreich opened a pull request:

https://github.com/apache/geode/pull/585

GEODE-3091: remove empty method



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

$ git pull https://github.com/nreich/geode feature/GEODE-3091

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

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


commit dd181aff5d33226865361a91af1c3ad8d5aecb78
Author: Nick Reich 
Date:   2017-06-15T22:59:50Z

GEODE-3091: remove empty method




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode pull request #581: GEODE-2301 Doc note to deprecate Geode JTA trans mg...

2017-06-16 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/geode/pull/581


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Review Request 60125: GEODE-3062: replace SecurityService after loading cluster config [FIXED]

2017-06-16 Thread Jinmei Liao

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60125/#review178114
---


Ship it!




Ship It!

- Jinmei Liao


On June 16, 2017, 4:23 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60125/
> ---
> 
> (Updated June 16, 2017, 4:23 p.m.)
> 
> 
> Review request for geode, Emily Yeh, Jinmei Liao, Jared Stewart, Ken Howe, 
> and Patrick Rhomberg.
> 
> 
> Bugs: GEODE-3062
> https://issues.apache.org/jira/browse/GEODE-3062
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Fixes:
> a) moved deployment of cluster config jars back to initalize after 
> ClassPathLoader
> b) added DistributedSystem#disconnect to ServerStarterRule "after" (tests 
> which fail during Cache create have no GemFireCacheImpl singleton but they do 
> have a InternalDistributedSystem singleton)
> 
> Add new test to ClusterConfigWithSecurityDUnitTest that fails due to bug 
> GEODE-3062.
> 
> Remove unused Cache param from applyClusterPropertiesConfiguration so it can 
> be called during Cache construction.
> 
> Move cluster config request to Cache construction and handle jars and 
> properties there. Create new SecurityService in constructor and overwrite the 
> SecurityService in InternalDistributedSystem.
> 
> NOTE: We will later have to fix GEODE-3061 by moving cluster config request 
> from Cache to InternalDistributedSystem construction so that IDS can be 
> created with gemfire.properties from cluster config. At that time we would 
> rip out both cluster config request and creation of security service from 
> Cache construction and pass both into Cache construction.
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
>  22edb6f06c7791929cc9a033ca1a1bfed5751a47 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/ClusterConfigurationLoader.java
>  4f4881fe39116faa505bc2fbec74efd669efe0ef 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
>  40df0c7dcac8827a381c268c1f90e6acfb97a7f1 
>   
> geode-core/src/test/java/org/apache/geode/management/internal/configuration/ClusterConfigWithSecurityDUnitTest.java
>  c551ca9104a85dcf54c0bebbc4178fce4114a416 
>   
> geode-core/src/test/java/org/apache/geode/test/dunit/rules/MemberStarterRule.java
>  e5e598edd60de730d43b15b015ce94457309d41a 
>   
> geode-core/src/test/java/org/apache/geode/test/dunit/rules/ServerStarterRule.java
>  fa3e8c0f0bb2fdbf55724e1ba78de7babb5f01b8 
> 
> 
> Diff: https://reviews.apache.org/r/60125/diff/2/
> 
> 
> Testing
> ---
> 
> precheckin in progress
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>



[GitHub] geode issue #581: GEODE-2301 Doc note to deprecate Geode JTA trans mgr

2017-06-16 Thread joeymcallister
Github user joeymcallister commented on the issue:

https://github.com/apache/geode/pull/581
  
+1 LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] geode issue #584: GEODE-2901: Adding integration tests of session replicatio...

2017-06-16 Thread upthewaterspout
Github user upthewaterspout commented on the issue:

https://github.com/apache/geode/pull/584
  
+1 - Looks good to me!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Review Request 60125: GEODE-3062: replace SecurityService after loading cluster config [FIXED]

2017-06-16 Thread Kirk Lund

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60125/
---

(Updated June 16, 2017, 4:23 p.m.)


Review request for geode, Emily Yeh, Jinmei Liao, Jared Stewart, Ken Howe, and 
Patrick Rhomberg.


Changes
---

Address review issues from Jinmei.


Bugs: GEODE-3062
https://issues.apache.org/jira/browse/GEODE-3062


Repository: geode


Description
---

Fixes:
a) moved deployment of cluster config jars back to initalize after 
ClassPathLoader
b) added DistributedSystem#disconnect to ServerStarterRule "after" (tests which 
fail during Cache create have no GemFireCacheImpl singleton but they do have a 
InternalDistributedSystem singleton)

Add new test to ClusterConfigWithSecurityDUnitTest that fails due to bug 
GEODE-3062.

Remove unused Cache param from applyClusterPropertiesConfiguration so it can be 
called during Cache construction.

Move cluster config request to Cache construction and handle jars and 
properties there. Create new SecurityService in constructor and overwrite the 
SecurityService in InternalDistributedSystem.

NOTE: We will later have to fix GEODE-3061 by moving cluster config request 
from Cache to InternalDistributedSystem construction so that IDS can be created 
with gemfire.properties from cluster config. At that time we would rip out both 
cluster config request and creation of security service from Cache construction 
and pass both into Cache construction.


Diffs (updated)
-

  
geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
 22edb6f06c7791929cc9a033ca1a1bfed5751a47 
  
geode-core/src/main/java/org/apache/geode/internal/cache/ClusterConfigurationLoader.java
 4f4881fe39116faa505bc2fbec74efd669efe0ef 
  
geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java 
40df0c7dcac8827a381c268c1f90e6acfb97a7f1 
  
geode-core/src/test/java/org/apache/geode/management/internal/configuration/ClusterConfigWithSecurityDUnitTest.java
 c551ca9104a85dcf54c0bebbc4178fce4114a416 
  
geode-core/src/test/java/org/apache/geode/test/dunit/rules/MemberStarterRule.java
 e5e598edd60de730d43b15b015ce94457309d41a 
  
geode-core/src/test/java/org/apache/geode/test/dunit/rules/ServerStarterRule.java
 fa3e8c0f0bb2fdbf55724e1ba78de7babb5f01b8 


Diff: https://reviews.apache.org/r/60125/diff/2/

Changes: https://reviews.apache.org/r/60125/diff/1-2/


Testing
---

precheckin in progress


Thanks,

Kirk Lund



[GitHub] geode pull request #582: GEODE-2601: Fix banner being logged twice

2017-06-16 Thread YehEmily
Github user YehEmily commented on a diff in the pull request:

https://github.com/apache/geode/pull/582#discussion_r122476764
  
--- Diff: 
geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
 ---
@@ -2167,7 +2191,7 @@ private static void 
notifyReconnectListeners(InternalDistributedSystem oldsys,
   private void notifyResourceEventListeners(ResourceEvent event, Object 
resource) {
 for (Iterator iter = 
resourceListeners.iterator(); iter.hasNext();) {
--- End diff --

How nice! Thank you, I'll edit this and update the PR!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Review Request 60125: GEODE-3062: replace SecurityService after loading cluster config [FIXED]

2017-06-16 Thread Kirk Lund


> On June 15, 2017, 11:47 p.m., Jinmei Liao wrote:
> > geode-core/src/test/java/org/apache/geode/test/dunit/rules/ServerStarterRule.java
> > Lines 132 (patched)
> > 
> >
> > I am surprised that server.stop() does not call this ds.stop().
> > 
> > would this also apply to LocatorStarterRule as well? If so, we should 
> > add this block to the parent's class(MemberStarterRule)'s stop() method.

CacheServer.stop() only stops a CacheServer instance. The Cache and 
DistributedSystem both remain open.


- Kirk


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60125/#review178065
---


On June 15, 2017, 11:44 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60125/
> ---
> 
> (Updated June 15, 2017, 11:44 p.m.)
> 
> 
> Review request for geode, Emily Yeh, Jinmei Liao, Jared Stewart, Ken Howe, 
> and Patrick Rhomberg.
> 
> 
> Bugs: GEODE-3062
> https://issues.apache.org/jira/browse/GEODE-3062
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Fixes:
> a) moved deployment of cluster config jars back to initalize after 
> ClassPathLoader
> b) added DistributedSystem#disconnect to ServerStarterRule "after" (tests 
> which fail during Cache create have no GemFireCacheImpl singleton but they do 
> have a InternalDistributedSystem singleton)
> 
> Add new test to ClusterConfigWithSecurityDUnitTest that fails due to bug 
> GEODE-3062.
> 
> Remove unused Cache param from applyClusterPropertiesConfiguration so it can 
> be called during Cache construction.
> 
> Move cluster config request to Cache construction and handle jars and 
> properties there. Create new SecurityService in constructor and overwrite the 
> SecurityService in InternalDistributedSystem.
> 
> NOTE: We will later have to fix GEODE-3061 by moving cluster config request 
> from Cache to InternalDistributedSystem construction so that IDS can be 
> created with gemfire.properties from cluster config. At that time we would 
> rip out both cluster config request and creation of security service from 
> Cache construction and pass both into Cache construction.
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
>  22edb6f06c7791929cc9a033ca1a1bfed5751a47 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/ClusterConfigurationLoader.java
>  4f4881fe39116faa505bc2fbec74efd669efe0ef 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
>  40df0c7dcac8827a381c268c1f90e6acfb97a7f1 
>   
> geode-core/src/test/java/org/apache/geode/management/internal/configuration/ClusterConfigWithSecurityDUnitTest.java
>  c551ca9104a85dcf54c0bebbc4178fce4114a416 
>   
> geode-core/src/test/java/org/apache/geode/test/dunit/rules/ServerStarterRule.java
>  fa3e8c0f0bb2fdbf55724e1ba78de7babb5f01b8 
> 
> 
> Diff: https://reviews.apache.org/r/60125/diff/1/
> 
> 
> Testing
> ---
> 
> precheckin in progress
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>



Re: Review Request 60142: GEODE-3071: Provide capability to parallelize distributedTests

2017-06-16 Thread Jens Deppe

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60142/
---

(Updated June 16, 2017, 3:07 p.m.)


Review request for geode, Anthony Baker, Mark Bretl, and Dan Smith.


Changes
---

Added Apache license header


Repository: geode


Description
---

Herewith the ability to leverage Gradle's parallel test execution
capability to run dunits in parallel. This is combined with launching
tests in Docker containers to provide process, network and filesystem
isolation. Depending on the size of your system, this can speed up
running the distributedTest task 2-5 times.

The capability is enabled by launching gradle with '-PparallelDunit'

Tunables, enabled as gradle parametrs (-P option) are:

- dunitDockerImage: The docker image which will be used to launch
  tests. The image must have the JAVA_HOME environment variable set. The
  image must be pulled locally before starting the tests.
- dunitParallelForks: The number of parallel docker containers to be
  launched.
- dunitDockerUser: The docker user which will run the tests. Because of
  the way that the containers map the build directory into them, the
  test artifacts, will be written with this user id. By default this is
  'root'.

Remove debug println

NOTE: There are problems running this on MacOS which will require a bit more 
work.


Diffs (updated)
-

  build.gradle ec6b920c825491030120e99d288067d476d1fdcb 
  gradle.properties ca79a3816bffa56e412d82dd570f1e0e445592be 
  gradle/docker.gradle PRE-CREATION 


Diff: https://reviews.apache.org/r/60142/diff/2/

Changes: https://reviews.apache.org/r/60142/diff/1-2/


Testing
---

Manual test on linux


Thanks,

Jens Deppe



Query for JMX "Async Event Queue properties"

2017-06-16 Thread Dinesh Akhand
Hi Team

Regarding the following metrics:

/AsyncEventQueue_XYZ_PARALLEL_GATEWAY_SENDER_QUEUE:PartitionedRegionStats.dataStoreEntryCount
/AsyncEventQueue_XYZ_PARALLEL_GATEWAY_SENDER_QUEUE:PartitionedRegionStats.dataStoreBytesInUse


I found only count for async queue in JMX , it called here EventQueueSize = 
PartitionedRegionStats.dataStoreEntryCount

/** AsyncEventQueue Stats **/
  public static final String ASYNCEVENTQUEUE_EVENTS_QUEUE_SIZE = 
"eventQueueSize"

we having Missing  PartitionedRegionStats.dataStoreBytesInUse in JMX for Async 
Qeueue.

Can you help me , which property I need to map for it.

Thanks,
Dinesh Akhand


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 



Re: Review Request 60142: GEODE-3071: Provide capability to parallelize distributedTests

2017-06-16 Thread Mark Bretl

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60142/#review178086
---


Ship it!




Excellent work Jens! Only issue I see is to add Apache license to docker.gradle.

- Mark Bretl


On June 15, 2017, 5:59 p.m., Jens Deppe wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/60142/
> ---
> 
> (Updated June 15, 2017, 5:59 p.m.)
> 
> 
> Review request for geode, Anthony Baker, Mark Bretl, and Dan Smith.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Herewith the ability to leverage Gradle's parallel test execution
> capability to run dunits in parallel. This is combined with launching
> tests in Docker containers to provide process, network and filesystem
> isolation. Depending on the size of your system, this can speed up
> running the distributedTest task 2-5 times.
> 
> The capability is enabled by launching gradle with '-PparallelDunit'
> 
> Tunables, enabled as gradle parametrs (-P option) are:
> 
> - dunitDockerImage: The docker image which will be used to launch
>   tests. The image must have the JAVA_HOME environment variable set. The
>   image must be pulled locally before starting the tests.
> - dunitParallelForks: The number of parallel docker containers to be
>   launched.
> - dunitDockerUser: The docker user which will run the tests. Because of
>   the way that the containers map the build directory into them, the
>   test artifacts, will be written with this user id. By default this is
>   'root'.
> 
> Remove debug println
> 
> NOTE: There are problems running this on MacOS which will require a bit more 
> work.
> 
> 
> Diffs
> -
> 
>   build.gradle ec6b920c825491030120e99d288067d476d1fdcb 
>   gradle.properties ca79a3816bffa56e412d82dd570f1e0e445592be 
>   gradle/docker.gradle PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/60142/diff/1/
> 
> 
> Testing
> ---
> 
> Manual test on linux
> 
> 
> Thanks,
> 
> Jens Deppe
> 
>