Review Request 55109: GEODE-1657 Remove silly ^M characters

2016-12-30 Thread Anthony Baker 

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

Review request for geode.


Repository: geode


Description
---

GEODE-1657 Remove silly ^M characters


Diffs
-

  KEYS cbc535478664984b81f349178325d91d86b68004 
  extensions/geode-modules-assembly/release/conf/cache-client.xml 
297b6a66c8f98bbefaeee2a3212bef146d03db66 
  extensions/geode-modules-assembly/release/conf/cache-peer.xml 
0480dcac59f5377bd4be7ab2464c569ed7534b20 
  extensions/geode-modules-assembly/release/conf/cache-server.xml 
d67b456839de66cc8bc5f492e862285d51454946 
  geode-assembly/src/main/dist/bin/gfsh.bat 
8206b6e7ab5c3e57f9557d87114fcb34b67fde6f 
  
geode-core/src/main/resources/org/apache/geode/distributed/internal/membership/gms/messenger/jgroups-config.xml
 a12e28983c02e550ec74153eb7e74b916daeee50 
  
geode-core/src/test/resources/org/apache/geode/codeAnalysis/sanctionedSerializables.txt
 03bb3ea9d4c388ea4a88d1f05d23c568d0ec87fd 
  
geode-core/src/test/resources/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventQueueValidationsJUnitTest.testParallelAsyncEventQueueConfiguredFromXmlUsesFilter.cache.xml
 bc834377f5d22df76896fda55e267a3cbd5720f2 
  
geode-core/src/test/resources/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventQueueValidationsJUnitTest.testSerialAsyncEventQueueConfiguredFromXmlUsesFilter.cache.xml
 7b823234615629b47f0d169b997ed0b962161eca 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/array.txt 
9209f95d39d6b22ad0cf5d46f2f952fad9fad4ef 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/attachment.txt 
c5e90628243facb1b1011ee3be14b9e35f60d27b 
  
geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/attachment2.txt 
a11ca0d52df25bb3beece9ed894754d99562f8f5 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/book.txt 
fc297eea0c8ddfdd0f146cec72a5e0f7058e6595 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/image.txt 
304f2e2624b8ada1595f3a6eb3fd9cfa560f103b 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json1.txt 
61892f65e9112d7a7e72fd88b6489c9d39147afe 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json10.txt 
471744a481a3c924d69b08aeaa02696af81fd6e3 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json11.txt 
ae91e50c97b6ed7de30edb159e4fc76fb1f11d8a 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json12.txt 
c1943f4ff91c55ffe97d9d12cb04fc645e81902e 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json13.txt 
06f5ab8b7405081a1e606f1cc98c7df0e92472c0 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json14.txt 
618a20632f4f5ec2f8b7626bc52860095c4be339 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json16.txt 
50e30d32e5575f8015d9892c7612d32405f4f5ae 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json16_2.txt 
06b43e7c8beae703eefea17f3143e0cdf1f3070e 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json17.txt 
a302da03d89e07be9a427b855c2cb9ce8e6c411a 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json18.txt 
82138f5beac4fc7351881288b56fff3b77bf608a 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json19.txt 
0b6e7f252e9ff595acdf286edf3475523e876cff 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json2.txt 
f8fa3338bea31b883a5f1d8a7ca91031812f1192 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json20.txt 
cfe5b555688d8141ba78b2590ffad0dea4b17acf 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json21.txt 
cfe5b555688d8141ba78b2590ffad0dea4b17acf 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json22.txt 
cfe5b555688d8141ba78b2590ffad0dea4b17acf 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json23.txt 
d48f5d2bef9f5a0bfa64371d420e33cdb8e17d2c 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json24.txt 
dc5bbca6dcfa57146f03dac01f4241b5fe2f354e 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json25.txt 
f7a12e3a03b0150a6aea23006a08b304bff17c86 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json26.txt 
a827405fe0af11aecfd389b3954adcefe3a282e5 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json27.txt 
6420a1e4a1a9bda847daaeffe83f144ddf2fd638 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json28.txt 
0b8d1aa98bf4abc8b2b750dcf1778347a13c8468 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json29.txt 
01547c5d30b359963d951374d3d19aa8fd3235fb 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json3.txt 
275cce18e58144a34e663eaa4481a8c9669fc5e4 
  geode-core/src/test/resources/org/apache/geode/pdx/jsonStrings/json31.txt 
83595b93fc36833795b8857a03c2276c4eb1052c 
  ge

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

2016-12-30 Thread Anthony Baker (JIRA) 

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

Anthony Baker reassigned GEODE-1657:


Assignee: Anthony Baker  (was: 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: Anthony Baker
>Priority: Minor
>
> 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)

Review Request 55108: GEODE-2016: change compile dependency to testCompile

2016-12-30 Thread Anthony Baker 

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

Review request for geode, Jason Huynh and Swapnil Bawaskar.


Repository: geode


Description
---

GEODE-2016: change compile dependency to testCompile


Diffs
-

  extensions/geode-modules-tomcat8/build.gradle 
df36ab320c2ceb1139b4ac10efcecf1b29b2931d 

Diff: https://reviews.apache.org/r/55108/diff/


Testing
---


Thanks,

Anthony Baker

Review Request 55106: GEODE-1580 ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

2016-12-30 Thread Bruce Schuchardt 

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

Review request for geode, Galen O'Sullivan, Hitesh Khamesra, and Udo Kohlmeyer.


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


Repository: geode


Description
---

Added a dunit blackboard to coordinate creation of a deadlock with the 
DistributedLockService.  Removed pauses and added use of Awaitility to wait for 
conditions.


Diffs
-

  
geode-core/src/main/java/org/apache/geode/distributed/internal/DistributionManager.java
 872016bdcfb564e9a30f54f416b6770599246dce 
  
geode-core/src/test/java/org/apache/geode/distributed/internal/deadlock/GemFireDeadlockDetectorDUnitTest.java
 17ec800517066b1a7564a91be10c7d659f24a8fb 
  geode-core/src/test/java/org/apache/geode/test/dunit/DUnitBlackboard.java 
PRE-CREATION 
  geode-core/src/test/java/org/apache/geode/test/dunit/DUnitBlackboardImpl.java 
PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/test/dunit/internal/JUnit4DistributedTestCase.java
 ebbb2fd5fffd5b4e1120a05c5103698b6be9e1f5 
  geode-core/src/test/java/org/apache/geode/test/dunit/standalone/ChildVM.java 
7a9d7f00ff2efcdb811217c5dd42baeebe862685 
  
geode-core/src/test/java/org/apache/geode/test/dunit/standalone/DUnitLauncher.java
 5a80a64f82ad0d7ed6e22c06e006e82d7d1e9d95 
  
geode-core/src/test/java/org/apache/geode/test/dunit/standalone/ProcessManager.java
 7852db5e01f14196777fabc4003295c26a61ef0f 

Diff: https://reviews.apache.org/r/55106/diff/


Testing
---

Running precheckin since some dunit infrastructure was modified


Thanks,

Bruce Schuchardt

[jira] [Assigned] (GEODE-1580) ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock

2016-12-30 Thread Bruce Schuchardt (JIRA) 

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

Bruce Schuchardt reassigned GEODE-1580:
---

Assignee: Bruce Schuchardt

> ci failure: GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock
> -
>
> Key: GEODE-1580
> URL: https://issues.apache.org/jira/browse/GEODE-1580
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Hitesh Khamesra
>Assignee: Bruce Schuchardt
>  Labels: CI, Flaky
>
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2969/testReport/com.gemstone.gemfire.distributed.internal.deadlock/GemFireDeadlockDetectorDUnitTest/testDistributedDeadlockWithDLock/
> Skip to content
> titletitle log in
> search
>  
> ENABLE AUTO REFRESH
> Jenkins
> Geode_develop_DistributedTests
> #2969
> Test Results
> com.gemstone.gemfire.distributed.internal.deadlock
> GemFireDeadlockDetectorDUnitTest
> testDistributedDeadlockWithDLock
>  Back to Project
>  Status
>  Changes
>  Console Output
>  View Build Information
>  History
>  Parameters
>  Metadata
>  Environment Variables
>  Git Build Data
>  Test Result
>  Changes since last success
>  Compare environment
>  JS Widgets
>  Previous Build
>  Next Build
> Regression
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock
> Failing for the past 1 build (Since Failed#2969 )
> Took 1 min 4 sec.
>  Failed 2 times in the last 22 runs. Stability: 90 %
> Error Message
> java.lang.AssertionError
> Stacktrace
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> com.gemstone.gemfire.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:177)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> 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 
>

[jira] [Assigned] (GEODE-2016) Dependency configuration for javax.security.auth.message-api incorrect

2016-12-30 Thread Anthony Baker (JIRA) 

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

Anthony Baker reassigned GEODE-2016:


Assignee: Anthony Baker

> Dependency configuration for javax.security.auth.message-api incorrect
> --
>
> Key: GEODE-2016
> URL: https://issues.apache.org/jira/browse/GEODE-2016
> Project: Geode
>  Issue Type: Bug
>  Components: http session
>Reporter: Swapnil Bawaskar
>Assignee: Anthony Baker
>
> The dependency {{javax.security.auth.message-api-1.1}} pulled in by 
> extensions is declared to be a compile dependency, but it is only used in 
> tests, so it should be made a {{testCompile}} dependency.
> The definition is here: 
> https://github.com/apache/incubator-geode/blob/8a6a46abde1a7f08fcf4605877f60ce9480fb296/extensions/geode-modules-tomcat8/build.gradle#L39



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

[jira] [Commented] (GEODE-2260) Move geode examples to new repo home

2016-12-30 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2260:


Commit 7aacbd04a3856b36d173dd1b427d1836454dff69 in geode's branch 
refs/heads/feature/testBranch from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=7aacbd0 ]

GEODE-2260 Add content from develop branch of Geode repo.


> Move geode examples to new repo home
> 
>
> Key: GEODE-2260
> URL: https://issues.apache.org/jira/browse/GEODE-2260
> Project: Geode
>  Issue Type: New Feature
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>
> Initialize new repository (https://github.com/apache/geode-examples) for 
> geode-examples module.
> Move current geode-examples module to the new repo.
> Revise instructions to work outside the geode repo. Verify the replicated 
> example works once moved.



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

[jira] [Resolved] (GEODE-2162) AsyncEventListenerDUnitTest testParallelAsyncEventQueueWithOneAccessor hang on tearDown

2016-12-30 Thread Bruce Schuchardt (JIRA) 

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

Bruce Schuchardt resolved GEODE-2162.
-
Resolution: Cannot Reproduce

> AsyncEventListenerDUnitTest testParallelAsyncEventQueueWithOneAccessor hang 
> on tearDown
> ---
>
> Key: GEODE-2162
> URL: https://issues.apache.org/jira/browse/GEODE-2162
> Project: Geode
>  Issue Type: Bug
>  Components: distributed lock service
>Reporter: Hitesh Khamesra
>Assignee: Bruce Schuchardt
>
> "RMI TCP Connection(10)-10.118.32.97" #27 daemon prio=5 os_prio=0 
> tid=0x7f4148001800 nid=0x753f waiting on condition [0x7f41ad02d000]
>java.lang.Thread.State: TIMED_WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0xe090e1b8> (a 
> java.util.concurrent.CountDownLatch$Sync)
>   at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
>   at 
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:716)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:793)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:769)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:856)
>   at 
> org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72)
>   at 
> org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.getElderStateWithTryLock(DistributionManager.java:3631)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.getElderState(DistributionManager.java:3581)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:240)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:349)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:329)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:320)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:850)
>   at 
> org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1226)
>   - locked <0xe09ee050> (a 
> org.apache.geode.distributed.internal.locks.DLockGrantor)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:640)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.basicDestroy(DLockService.java:2496)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.destroyAndRemove(DLockService.java:2415)
>   - locked <0xe0554e08> (a java.lang.Object)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.destroyServiceNamed(DLockService.java:2316)
>   at 
> org.apache.geode.distributed.DistributedLockService.destroy(DistributedLockService.java:84)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.destroyGatewaySenderLockService(GemFireCacheImpl.java:2053)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2196)
>   - locked <0xe0347638> (a java.lang.Class for 
> org.apache.geode.internal.cache.GemFireCacheImpl)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1973)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1969)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.closeCache(JUnit4DistributedTestCase.java:602)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownVM(JUnit4DistributedTestCase.java:563)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.lambda$cleanupAllVms$bb17a952$1(JUnit4DistributedTestCase.java:554)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase$$Lambda$23/2043837261.run(Unknown
>  Sourc

[jira] [Commented] (GEODE-2162) AsyncEventListenerDUnitTest testParallelAsyncEventQueueWithOneAccessor hang on tearDown

2016-12-30 Thread Bruce Schuchardt (JIRA) 

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

Bruce Schuchardt commented on GEODE-2162:
-

We really needed to know what the state of 10.118.32.97(6382):32774 was.  
It's odd that the output Hitesh put in his comment doesn't have the dunit VM of 
origin in the log messages.  When I run this test I see [vm_0], [vm+1], [vm_2] 
etc at the beginning of each log statement.  Nothing is run in the controller 
VM so there's nothing logged by it.

I've run this test over 1000 times with various prods to make sure that the 
member who takes over from the locator becomes the elder and lock grantor but 
I've been unable to reproduce this hang, or even a reply-wait timeout.  I added 
hooks in Elder initialization code to make sure that the same scenario was 
being run but it always worked as designed.

I'm closing this ticket.  If it happens again we need a more thorough 
collection of artifacts - at least the full log of the run including output 
from all of the VMs.

> AsyncEventListenerDUnitTest testParallelAsyncEventQueueWithOneAccessor hang 
> on tearDown
> ---
>
> Key: GEODE-2162
> URL: https://issues.apache.org/jira/browse/GEODE-2162
> Project: Geode
>  Issue Type: Bug
>  Components: distributed lock service
>Reporter: Hitesh Khamesra
>Assignee: Bruce Schuchardt
>
> "RMI TCP Connection(10)-10.118.32.97" #27 daemon prio=5 os_prio=0 
> tid=0x7f4148001800 nid=0x753f waiting on condition [0x7f41ad02d000]
>java.lang.Thread.State: TIMED_WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0xe090e1b8> (a 
> java.util.concurrent.CountDownLatch$Sync)
>   at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
>   at 
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:716)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:793)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:769)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:856)
>   at 
> org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72)
>   at 
> org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.getElderStateWithTryLock(DistributionManager.java:3631)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.getElderState(DistributionManager.java:3581)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:240)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:349)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:329)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:320)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:850)
>   at 
> org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1226)
>   - locked <0xe09ee050> (a 
> org.apache.geode.distributed.internal.locks.DLockGrantor)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:640)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.basicDestroy(DLockService.java:2496)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.destroyAndRemove(DLockService.java:2415)
>   - locked <0xe0554e08> (a java.lang.Object)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.destroyServiceNamed(DLockService.java:2316)
>   at 
> org.apache.geode.distributed.DistributedLockService.destroy(DistributedLockService.java:84)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.destroyGatewaySenderLockService(GemFireCacheImpl.java:2053)
>   at 
> o

[jira] [Assigned] (GEODE-2260) Move geode examples to new repo home

2016-12-30 Thread Karen Smoler Miller (JIRA) 

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

Karen Smoler Miller reassigned GEODE-2260:
--

Assignee: Karen Smoler Miller

> Move geode examples to new repo home
> 
>
> Key: GEODE-2260
> URL: https://issues.apache.org/jira/browse/GEODE-2260
> Project: Geode
>  Issue Type: New Feature
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>
> Initialize new repository (https://github.com/apache/geode-examples) for 
> geode-examples module.
> Move current geode-examples module to the new repo.
> Revise instructions to work outside the geode repo. Verify the replicated 
> example works once moved.



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

[jira] [Created] (GEODE-2260) Move geode examples to new repo home

2016-12-30 Thread Karen Smoler Miller (JIRA) 
Karen Smoler Miller created GEODE-2260:
--

 Summary: Move geode examples to new repo home
 Key: GEODE-2260
 URL: https://issues.apache.org/jira/browse/GEODE-2260
 Project: Geode
  Issue Type: New Feature
Reporter: Karen Smoler Miller


Initialize new repository (https://github.com/apache/geode-examples) for 
geode-examples module.

Move current geode-examples module to the new repo.

Revise instructions to work outside the geode repo. Verify the replicated 
example works once moved.



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

Re: Maven coordinates for 1.0.0-incubating release

2016-12-30 Thread Swapnil Bawaskar 
The examples repo has been configured to forward commits and GitHub
notifications. I am not sure about JIRA or reviewboard integration.

On Fri, Dec 30, 2016 at 7:08 AM, Anthony Baker  wrote:

> Swapnil, do you know if the geode-examples repo has been setup to:
>
> - Forward commits to comm...@geode.apache.org
> - Integrate commit messages with JIRA
> - Allow review requests on reviewboard
>
> Anthony
>
> On Dec 29, 2016, at 11:37 AM, Swapnil Bawaskar 
> wrote:
>
> I filed an INFRA issue for creating a new repository:
> https://issues.apache.org/jira/browse/INFRA-13198
> I have asked for "geode-examples" as the name of the repo.
>
> On Wed, Oct 26, 2016 at 5:48 PM, Jared Stewart 
> wrote:
>
>> +1
>>
>> On Oct 26, 2016 5:42 PM, "William Markito Oliveira" <
>> william.mark...@gmail.com> wrote:
>>
>>> +1
>>>
>>> Sent from my iPhone
>>>
>>> On Oct 26, 2016, at 4:51 PM, John D. Ament 
>>> wrote:
>>>
>>> +1
>>>
>>> On Oct 26, 2016 19:49, "Swapnil Bawaskar"  wrote:
>>>
 It would be really nice to not have to clone the entire geode repo,
 just to contribute/run the examples. Can the examples be moved to their own
 repo?

 On Wed, Oct 26, 2016 at 2:38 PM, Anthony Baker 
 wrote:

> Here are the maven coordinates for the 1.0.0-incubating release:
>
> Maven:
>
> 
> 
> org.apache.geode
> geode-core
> 1.0.0-incubating
> 
> 
>
> Gradle:
>
> dependencies {
> compile ‘org.apache.geode:geode-core:1.0.0-incubating’
> }
>
>
> If you’re building a Geode client application, the geode-core
> dependency contains the Java client that connects to a Geode cluster.
>
> We have begun creating examples [1] that succinctly demonstrate Geode
> features and usage.  If you are interested in helping out, this is a great
> way to begin contributing!
>
> Thanks,
> Anthony
>
> [1] https://github.com/apache/incubator-geode/tree/develop/geode
> -examples
>
>
>

>
>

[jira] [Commented] (GEODE-2216) PartitionedRegion.createIndexes ignores exceptions, resulting in corrupt indexes

2016-12-30 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2216:


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

GEODE-2216: Indexes no longer get removed but instead do not set populated flag


> PartitionedRegion.createIndexes ignores exceptions, resulting in corrupt 
> indexes
> 
>
> Key: GEODE-2216
> URL: https://issues.apache.org/jira/browse/GEODE-2216
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.1.0
>
>
> I tried to create an index on a region with objects that could not be 
> deserialized (it was a mistake in my code). I found that it actually 
> *allowed* me to create the index, but my values were not actually indexed.
> Looking at the code in PartitionedRegion.createIndexes, it has some 
> interesting code to maintain a boolean flag that an exception should be 
> thrown. However, it keeps losing the value of the flag. Here's some of the 
> code:
> {code}
> boolean throwException = false;
> ...
> throwException =
> createEmptyIndexes(indexDefinitions, remotelyOriginated, indexes, 
> exceptionsMap);
> ...
> //This overwrites the value of throwException
> if (unpopulatedIndexes != null && unpopulatedIndexes.size() > 0) {
>   throwException = populateEmptyIndexes(unpopulatedIndexes, 
> exceptionsMap);
> }
> //Same thing here 
> throwException =
> sendCreateIndexesMessage(remotelyOriginated, indexDefinitions, 
> indexes, exceptionsMap);
> {code}
> This method should always throw an exception if the index creation failed.



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

[jira] [Resolved] (GEODE-2258) fix doc typos for setting properties

2016-12-30 Thread Karen Smoler Miller (JIRA) 

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

Karen Smoler Miller resolved GEODE-2258.

Resolution: Fixed

> fix doc typos for setting properties
> 
>
> Key: GEODE-2258
> URL: https://issues.apache.org/jira/browse/GEODE-2258
> Project: Geode
>  Issue Type: Bug
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0
>
>
> In file 
> {{basic_config/gemfire_properties/setting_distributed_properties.html}}, this 
> text is wrong:
> {{System.setProperty("DgemfirePropertyFile", "gfTest");}}
> {{System.setProperty("Dgemfire.mcast-port", "10999");}}
> The capital D at the beginning of each property name should be deleted.
> In the same file, the reference to DistributedSystem javadocs should be 
> changed to refer to this class:
> {{org.apache.geode.distributed.ConfigurationProperties}}
> {{ConfigurationProperties}} also defines constants for each property name so 
> that applications can use them instead of embedding string constants in their 
> code.  This has the benefit of avoiding typing mistakes.



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

[jira] [Updated] (GEODE-2258) fix doc typos for setting properties

2016-12-30 Thread Karen Smoler Miller (JIRA) 

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

Karen Smoler Miller updated GEODE-2258:
---
Fix Version/s: 1.1.0

> fix doc typos for setting properties
> 
>
> Key: GEODE-2258
> URL: https://issues.apache.org/jira/browse/GEODE-2258
> Project: Geode
>  Issue Type: Bug
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
> Fix For: 1.1.0
>
>
> In file 
> {{basic_config/gemfire_properties/setting_distributed_properties.html}}, this 
> text is wrong:
> {{System.setProperty("DgemfirePropertyFile", "gfTest");}}
> {{System.setProperty("Dgemfire.mcast-port", "10999");}}
> The capital D at the beginning of each property name should be deleted.
> In the same file, the reference to DistributedSystem javadocs should be 
> changed to refer to this class:
> {{org.apache.geode.distributed.ConfigurationProperties}}
> {{ConfigurationProperties}} also defines constants for each property name so 
> that applications can use them instead of embedding string constants in their 
> code.  This has the benefit of avoiding typing mistakes.



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

[jira] [Assigned] (GEODE-2162) AsyncEventListenerDUnitTest testParallelAsyncEventQueueWithOneAccessor hang on tearDown

2016-12-30 Thread Bruce Schuchardt (JIRA) 

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

Bruce Schuchardt reassigned GEODE-2162:
---

Assignee: Bruce Schuchardt  (was: Hitesh Khamesra)

> AsyncEventListenerDUnitTest testParallelAsyncEventQueueWithOneAccessor hang 
> on tearDown
> ---
>
> Key: GEODE-2162
> URL: https://issues.apache.org/jira/browse/GEODE-2162
> Project: Geode
>  Issue Type: Bug
>  Components: distributed lock service
>Reporter: Hitesh Khamesra
>Assignee: Bruce Schuchardt
>
> "RMI TCP Connection(10)-10.118.32.97" #27 daemon prio=5 os_prio=0 
> tid=0x7f4148001800 nid=0x753f waiting on condition [0x7f41ad02d000]
>java.lang.Thread.State: TIMED_WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   - parking to wait for  <0xe090e1b8> (a 
> java.util.concurrent.CountDownLatch$Sync)
>   at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
>   at 
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:716)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:793)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:769)
>   at 
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:856)
>   at 
> org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72)
>   at 
> org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.getElderStateWithTryLock(DistributionManager.java:3631)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.getElderState(DistributionManager.java:3581)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:240)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:349)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:329)
>   at 
> org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:320)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:850)
>   at 
> org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1226)
>   - locked <0xe09ee050> (a 
> org.apache.geode.distributed.internal.locks.DLockGrantor)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:640)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.basicDestroy(DLockService.java:2496)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.destroyAndRemove(DLockService.java:2415)
>   - locked <0xe0554e08> (a java.lang.Object)
>   at 
> org.apache.geode.distributed.internal.locks.DLockService.destroyServiceNamed(DLockService.java:2316)
>   at 
> org.apache.geode.distributed.DistributedLockService.destroy(DistributedLockService.java:84)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.destroyGatewaySenderLockService(GemFireCacheImpl.java:2053)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2196)
>   - locked <0xe0347638> (a java.lang.Class for 
> org.apache.geode.internal.cache.GemFireCacheImpl)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1973)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1969)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.closeCache(JUnit4DistributedTestCase.java:602)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownVM(JUnit4DistributedTestCase.java:563)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.lambda$cleanupAllVms$bb17a952$1(JUnit4DistributedTestCase.java:554)
>   at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase$$Lambda$23/2043

[jira] [Commented] (GEODE-2258) fix doc typos for setting properties

2016-12-30 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2258:


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

GEODE-2258 fix doc typos in section on setting properties


> fix doc typos for setting properties
> 
>
> Key: GEODE-2258
> URL: https://issues.apache.org/jira/browse/GEODE-2258
> Project: Geode
>  Issue Type: Bug
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>
> In file 
> {{basic_config/gemfire_properties/setting_distributed_properties.html}}, this 
> text is wrong:
> {{System.setProperty("DgemfirePropertyFile", "gfTest");}}
> {{System.setProperty("Dgemfire.mcast-port", "10999");}}
> The capital D at the beginning of each property name should be deleted.
> In the same file, the reference to DistributedSystem javadocs should be 
> changed to refer to this class:
> {{org.apache.geode.distributed.ConfigurationProperties}}
> {{ConfigurationProperties}} also defines constants for each property name so 
> that applications can use them instead of embedding string constants in their 
> code.  This has the benefit of avoiding typing mistakes.



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

[jira] [Resolved] (GEODE-2257) Client configured to use locator with addPoolServer fails to connect

2016-12-30 Thread Bruce Schuchardt (JIRA) 

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

Bruce Schuchardt resolved GEODE-2257.
-
Resolution: Fixed
  Assignee: Bruce Schuchardt

> Client configured to use locator with addPoolServer fails to connect
> 
>
> Key: GEODE-2257
> URL: https://issues.apache.org/jira/browse/GEODE-2257
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> If a client cache is incorrectly configured to use a locator address with 
> ClientConnectionFactory.addPoolServer() instead of addPoolLocator() it is 
> very difficult to figure out why it's unable to connect.  The locator rejects 
> all attempts to contact it because the client tries to perform a 
> server-handshake with it and the locator just closes the connection without a 
> response.  The client ends up having an empty connection pool and is unable 
> to find any of the available servers.



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

[jira] [Commented] (GEODE-2257) Client configured to use locator with addPoolServer fails to connect

2016-12-30 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2257:


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

GEODE-2257 Client configured to use locator with addPoolServer fails to connect

The first byte that a client sends is a connection-type that is >= 100.
The first bytes expected by a locator are the 4 bytes of an integer
indicating the protocol version.  I've changed the locator to read
the first byte and, if it's >= 100 send a reply byte back to the client
telling it that it's trying to contact a locator using a client/server
handshake.

The client has a new reply code that the locator is now using.  If the
client sees this reply code it will throw a GemFireConfigException.  Some
of these exceptions will be thrown in the background and get logged but
the thread initiating cache creation will also get this exception when
it invokes ClientCacheFactory.create().

The client-side error message will be in this form:
_Improperly configured client detected. Server at 10.154.30.28 is actually
a locator.  Use addPoolLocator to configure locators_.

The locator will also log a warning in this form so that alerts will be
raised:
_Unable to process request from 10.118.33.195 exception=Improperly
configured client detected - use addPoolLocator to configure its
locators instead of addPoolServer_.


> Client configured to use locator with addPoolServer fails to connect
> 
>
> Key: GEODE-2257
> URL: https://issues.apache.org/jira/browse/GEODE-2257
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> If a client cache is incorrectly configured to use a locator address with 
> ClientConnectionFactory.addPoolServer() instead of addPoolLocator() it is 
> very difficult to figure out why it's unable to connect.  The locator rejects 
> all attempts to contact it because the client tries to perform a 
> server-handshake with it and the locator just closes the connection without a 
> response.  The client ends up having an empty connection pool and is unable 
> to find any of the available servers.



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

Jenkins build is back to normal : Geode-nightly #701

2016-12-30 Thread Apache Jenkins Server 
See

Re: Review Request 55093: GEODE-2258 fix doc typos in section on setting properties

2016-12-30 Thread Bruce Schuchardt 

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


Ship it!




Ship It!

- Bruce Schuchardt


On Dec. 29, 2016, 11:58 p.m., Karen Miller wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55093/
> ---
> 
> (Updated Dec. 29, 2016, 11:58 p.m.)
> 
> 
> Review request for geode, Bruce Schuchardt, Dave Barnes, and Joey McAllister.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> GEODE-2258 fix doc typos in section on setting properties
> 
> 
> Diffs
> -
> 
>   
> geode-docs/basic_config/gemfire_properties/setting_distributed_properties.html.md.erb
>  22e373abccfdb89438f7ee5677578193c764c98b 
> 
> Diff: https://reviews.apache.org/r/55093/diff/
> 
> 
> Testing
> ---
> 
> gradle rat check passes
> 
> 
> Thanks,
> 
> Karen Miller
> 
>

Re: Maven coordinates for 1.0.0-incubating release

2016-12-30 Thread Anthony Baker 
Swapnil, do you know if the geode-examples repo has been setup to:

- Forward commits to comm...@geode.apache.org
- Integrate commit messages with JIRA
- Allow review requests on reviewboard

Anthony

> On Dec 29, 2016, at 11:37 AM, Swapnil Bawaskar  wrote:
> 
> I filed an INFRA issue for creating a new repository: 
> https://issues.apache.org/jira/browse/INFRA-13198 
> 
> I have asked for "geode-examples" as the name of the repo.
> 
> On Wed, Oct 26, 2016 at 5:48 PM, Jared Stewart  > wrote:
> +1
> 
> 
> On Oct 26, 2016 5:42 PM, "William Markito Oliveira" 
> mailto:william.mark...@gmail.com>> wrote:
> +1  
> 
> Sent from my iPhone
> 
> On Oct 26, 2016, at 4:51 PM, John D. Ament  > wrote:
> 
>> +1
>> 
>> 
>> On Oct 26, 2016 19:49, "Swapnil Bawaskar" > > wrote:
>> It would be really nice to not have to clone the entire geode repo, just to 
>> contribute/run the examples. Can the examples be moved to their own repo?
>> 
>> On Wed, Oct 26, 2016 at 2:38 PM, Anthony Baker > > wrote:
>> Here are the maven coordinates for the 1.0.0-incubating release:
>> 
>> Maven:
>> 
>> 
>> 
>> org.apache.geode
>> geode-core
>> 1.0.0-incubating
>> 
>> 
>> 
>> Gradle:
>> 
>> dependencies {
>> compile ‘org.apache.geode:geode-core:1.0.0-incubating’
>> }
>> 
>> 
>> If you’re building a Geode client application, the geode-core dependency 
>> contains the Java client that connects to a Geode cluster.
>> 
>> We have begun creating examples [1] that succinctly demonstrate Geode 
>> features and usage.  If you are interested in helping out, this is a great 
>> way to begin contributing!
>> 
>> Thanks,
>> Anthony
>> 
>> [1] https://github.com/apache/incubator-geode/tree/develop/geode-examples 
>> 
>> 
>> 
>> 
>