[jira] [Resolved] (GEODE-180) SnapshotDUnitTest intermittently fails because of a cache left over from a previous test

[ https://issues.apache.org/jira/browse/GEODE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-180. Resolution: Fixed This issue was resolved by when the earlier test was fixed

[jira] [Resolved] (GEODE-163) testPoolLoadAndPeer Cannot create region with ack because no-ack already exists

[ https://issues.apache.org/jira/browse/GEODE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-163. Resolution: Fixed The other test was fixed which resolved this issue testPoolLoadAndPeer

[jira] [Updated] (GEODE-164) launcher junit tests failing because working directory does not exist

[ https://issues.apache.org/jira/browse/GEODE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-164: --- Component/s: tests launcher junit tests failing because working directory does not exist

[jira] [Updated] (GEODE-163) testPoolLoadAndPeer Cannot create region with ack because no-ack already exists

[ https://issues.apache.org/jira/browse/GEODE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-163: --- Component/s: tests testPoolLoadAndPeer Cannot create region with ack because no-ack already

[jira] [Commented] (GEODE-17) Provide Integrated Security

[ https://issues.apache.org/jira/browse/GEODE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693928#comment-14693928 ] Nilkanth Patel commented on GEODE-17: - is requirement for this feature changed..? I

[jira] [Created] (GEODE-212) ResourceManager implementation impacts off-heap performance

Darrel Schneider created GEODE-212: -- Summary: ResourceManager implementation impacts off-heap performance Key: GEODE-212 URL: https://issues.apache.org/jira/browse/GEODE-212 Project: Geode

[jira] [Resolved] (GEODE-211) ConcurrentRegionOperationsJUnitTest takes too long to run

[ https://issues.apache.org/jira/browse/GEODE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-211. Resolution: Fixed ConcurrentRegionOperationsJUnitTest takes too long to run

[jira] [Updated] (GEODE-209) FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is not stable

[ https://issues.apache.org/jira/browse/GEODE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashvin updated GEODE-209: - Assignee: Kirk Lund FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is

[jira] [Commented] (GEODE-211) ConcurrentRegionOperationsJUnitTest takes too long to run

[ https://issues.apache.org/jira/browse/GEODE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693913#comment-14693913 ] ASF subversion and git services commented on GEODE-211: --- Commit