[jira] [Created] (GEODE-1462) Change tests with OS conditional early-outs to use org.junit.Assume

2016-05-26 Thread Kirk Lund (JIRA) 
Kirk Lund created GEODE-1462:


 Summary: Change tests with OS conditional early-outs to use 
org.junit.Assume
 Key: GEODE-1462
 URL: https://issues.apache.org/jira/browse/GEODE-1462
 Project: Geode
  Issue Type: Bug
  Components: ts, tests
Reporter: Kirk Lund


Example:
{noformat}
@Test
public void testWarning() throws Exception {
  if (!isLinux()) {
return;
  }
{noformat}
This should instead use:
{noformat}
@Test
public void testWarning() throws Exception {
  assumeTrue(SystemUtils.isLinux());
{noformat}




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

[jira] [Assigned] (GEODE-1462) Change tests with OS conditional early-outs to use org.junit.Assume

2016-05-26 Thread Kirk Lund (JIRA) 

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

Kirk Lund reassigned GEODE-1462:


Assignee: Kirk Lund

> Change tests with OS conditional early-outs to use org.junit.Assume
> ---
>
> Key: GEODE-1462
> URL: https://issues.apache.org/jira/browse/GEODE-1462
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> Example:
> {noformat}
> @Test
> public void testWarning() throws Exception {
>   if (!isLinux()) {
> return;
>   }
> {noformat}
> This should instead use:
> {noformat}
> @Test
> public void testWarning() throws Exception {
>   assumeTrue(SystemUtils.isLinux());
> {noformat}



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

[jira] [Created] (GEODE-1461) Introduce a new abstract class AbstractTransactionMessage so that duplicated methods in the implementation of TransactionMessage interface can be moved into it.

2016-05-26 Thread Eric Shu (JIRA) 
Eric Shu created GEODE-1461:
---

 Summary: Introduce a new abstract class AbstractTransactionMessage 
so that duplicated methods in the implementation of TransactionMessage 
interface can be moved into it.
 Key: GEODE-1461
 URL: https://issues.apache.org/jira/browse/GEODE-1461
 Project: Geode
  Issue Type: Bug
  Components: transactions
Reporter: Eric Shu


PartitionMessage and RemoteOperationMessage have a bunch of transaction related 
code in common, as they both implement the TransactionMessage interface.

Other messages implementing TransactionMessage may also need to be checked to 
see if can be refactored.



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

[jira] [Resolved] (GEODE-1456) CI Failure: GemFireCacheImplTest.checkThatAsyncEventListenersUseAllThreadsInPool

2016-05-26 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider resolved GEODE-1456.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3

> CI Failure: 
> GemFireCacheImplTest.checkThatAsyncEventListenersUseAllThreadsInPool
> 
>
> Key: GEODE-1456
> URL: https://issues.apache.org/jira/browse/GEODE-1456
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
> Fix For: 1.0.0-incubating.M3
>
>
> com.gemstone.gemfire.internal.cache.GemFireCacheImplTest > 
> checkThatAsyncEventListenersUseAllThreadsInPool FAILED
> com.jayway.awaitility.core.ConditionTimeoutException: Condition with 
> lambda expression in com.gemstone.gemfire.internal.cache.GemFireCacheImplTest 
> that uses java.util.concurrent.ThreadPoolExecutor, 
> java.util.concurrent.ThreadPoolExecutorint, intlong was not fulfilled within 
> 15 seconds.
> at 
> com.jayway.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:122)
> at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:764)
> at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:741)
> at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImplTest.checkThatAsyncEventListenersUseAllThreadsInPool(GemFireCacheImplTest.java:60)



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

[jira] [Commented] (GEODE-1456) CI Failure: GemFireCacheImplTest.checkThatAsyncEventListenersUseAllThreadsInPool

2016-05-26 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1456:


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

GEODE-1456: fix race in GemFireCacheImplTest

The race was caused by the GemFireCacheImpl constructor creating a real 
TypeRegistry.
The TypeRegistry creates a region which scheduled an async create region event 
with the
event pool. So when the test set "initialCount" this create region event might 
not have
completed so the initialCount would be zero. The test then scheduled 
MAX_THREADS tasks
and waits until that many complete. But the create region event could also 
complete causing
getCompletedTaskCount() to return a value 1 more than the test expected which 
caused it
to intermittently timeout.

The test now mocks the TypeRegistry so the only events scheduled with the pool 
come from
the unit test.


> CI Failure: 
> GemFireCacheImplTest.checkThatAsyncEventListenersUseAllThreadsInPool
> 
>
> Key: GEODE-1456
> URL: https://issues.apache.org/jira/browse/GEODE-1456
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> com.gemstone.gemfire.internal.cache.GemFireCacheImplTest > 
> checkThatAsyncEventListenersUseAllThreadsInPool FAILED
> com.jayway.awaitility.core.ConditionTimeoutException: Condition with 
> lambda expression in com.gemstone.gemfire.internal.cache.GemFireCacheImplTest 
> that uses java.util.concurrent.ThreadPoolExecutor, 
> java.util.concurrent.ThreadPoolExecutorint, intlong was not fulfilled within 
> 15 seconds.
> at 
> com.jayway.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:122)
> at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:764)
> at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:741)
> at 
> com.gemstone.gemfire.internal.cache.GemFireCacheImplTest.checkThatAsyncEventListenersUseAllThreadsInPool(GemFireCacheImplTest.java:60)



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

[jira] [Commented] (GEODE-523) PartitionListener requires tests and clean up

2016-05-26 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider commented on GEODE-523:


The comment on PartitionListenerAdapter is better:
 * Note : Please request help on the Geode developer mailing list
 * (d...@geode.incubator.apache.org) before using these APIs.
but should still be removed once we have unit test coverage of this interface.


> PartitionListener requires tests and clean up
> -
>
> Key: GEODE-523
> URL: https://issues.apache.org/jira/browse/GEODE-523
> Project: Geode
>  Issue Type: Test
>  Components: regions
>Reporter: Kirk Lund
>
> Many users are using PartitionListener. This API requires tests, proper 
> javadocs and general cleanup.
> See GEODE-390 and GEODE-72



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

[jira] [Commented] (GEODE-523) PartitionListener requires tests and clean up

2016-05-26 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider commented on GEODE-523:


The javadocs on this interface include an example that calls 
PartitionManager.createPrimaryBucket which no longer exists so this example 
should be removed.

Also the javadocs say to contact supp...@gemstone.com. This should be removed.

A dunit test for this interface does exist: PartitionListenerDUnitTest. It 
tests afterBucketCreated and afterBucketRemoved but it does not test 
afterPrimary nor afterRegionCreate.


> PartitionListener requires tests and clean up
> -
>
> Key: GEODE-523
> URL: https://issues.apache.org/jira/browse/GEODE-523
> Project: Geode
>  Issue Type: Test
>  Components: regions
>Reporter: Kirk Lund
>
> Many users are using PartitionListener. This API requires tests, proper 
> javadocs and general cleanup.
> See GEODE-390 and GEODE-72



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

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

2016-05-26 Thread ASF subversion and git services (JIRA) 

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

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

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

GEODE-17: when connecting to a secure manager, prompt for username and password

* refactor the connect command for better readability and retry handling
* throw AuthenticationFailedException for consistency


> Provide Integrated Security
> ---
>
> Key: GEODE-17
> URL: https://issues.apache.org/jira/browse/GEODE-17
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server, docs, security
>Reporter: Tushar Khairnar
>Assignee: Jens Deppe
>  Labels: security
>
> Integrated Security: Purpose of integrated security feature is to provide 
> uniform authentication and authorization capabilities for all Geode clients. 
> Geode distributed systems has different clients, some perform cache/region 
> operations, some perform management operations. In order to authenticate and 
> authorize these actions we need single consistent framework or interface. 
> Such interface should allow configuration of access levels from single place 
> and/or repository. 
> The key requirements being met here are
>  - Authentication of all clients from single plugin
>  - Authorization of cache/data operations (through cache-client and REST) and 
> managements (GFSH/JMX) operations from single plugin
>  - Extend existing Client-Server security framework



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

[jira] [Updated] (GEODE-523) PartitionListener requires tests and clean up

2016-05-26 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider updated GEODE-523:
---
Component/s: (was: core)
 regions

> PartitionListener requires tests and clean up
> -
>
> Key: GEODE-523
> URL: https://issues.apache.org/jira/browse/GEODE-523
> Project: Geode
>  Issue Type: Test
>  Components: regions
>Reporter: Kirk Lund
>
> Many users are using PartitionListener. This API requires tests, proper 
> javadocs and general cleanup.
> See GEODE-390 and GEODE-72



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

[jira] [Resolved] (GEODE-1451) OffheapRegionEntryHelper.decodeAddressToBytes method is confusing

2016-05-26 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider resolved GEODE-1451.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3

> OffheapRegionEntryHelper.decodeAddressToBytes method is confusing
> -
>
> Key: GEODE-1451
> URL: https://issues.apache.org/jira/browse/GEODE-1451
> Project: Geode
>  Issue Type: Improvement
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
> Fix For: 1.0.0-incubating.M3
>
>
> The OffheapRegionEntryHelper.decodeAddressToBytes method has two boolean 
> parameters that are confusing. It should be refactored so that the code is 
> easier to understand.



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

[jira] [Commented] (GEODE-1451) OffheapRegionEntryHelper.decodeAddressToBytes method is confusing

2016-05-26 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1451:


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

GEODE-1451: refactor decodeAddressToBytes into two methods

The boolean parameters have been removed and two
methods now exist:
1. decodeAddressToRawBytes(long)
2. decodeUncompressedAddressToBytes(long)


> OffheapRegionEntryHelper.decodeAddressToBytes method is confusing
> -
>
> Key: GEODE-1451
> URL: https://issues.apache.org/jira/browse/GEODE-1451
> Project: Geode
>  Issue Type: Improvement
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
> Fix For: 1.0.0-incubating.M3
>
>
> The OffheapRegionEntryHelper.decodeAddressToBytes method has two boolean 
> parameters that are confusing. It should be refactored so that the code is 
> easier to understand.



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

[jira] [Assigned] (GEODE-308) Separate hydra from dunit and junit tests in gemfire-core

2016-05-26 Thread Kevin Duling (JIRA) 

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

Kevin Duling reassigned GEODE-308:
--

Assignee: Kevin Duling  (was: Kirk Lund)

> Separate hydra from dunit and junit tests in gemfire-core
> -
>
> Key: GEODE-308
> URL: https://issues.apache.org/jira/browse/GEODE-308
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Assignee: Kevin Duling
>  Labels: hydra
>
> Usage of Hydra needs to be removed from dunit and junit tests in gemfire-core 
> and any other project.
> The following hydra classes in gemfire-core should be removed (and replaced 
> if needed by dunit/junit tests):
> src/test/java/hydra/GsRandom.java
> src/test/java/hydra/HydraRuntimeException.java
> src/test/java/hydra/Log.java
> src/test/java/hydra/LogVersionHelper.java
> src/test/java/hydra/MethExecutor.java
> src/test/java/hydra/MethExecutorResult.java
> src/test/java/hydra/SchedulingOrder.java
> src/test/java/hydra/log/AnyLogWriter.java
> src/test/java/hydra/log/CircularOutputStream.java
> The following are also not com.gemstone packages and should be removed if 
> they're specific to Hydra (or Hydra tests) or repackaged if they're actually 
> used in dunit/junit tests:
> src/test/java/batterytest/greplogs/ExpectedStrings.java
> src/test/java/batterytest/greplogs/LogConsumer.java
> src/test/java/cacheRunner/Portfolio.java
> src/test/java/cacheRunner/Position.java
> src/test/java/parReg/query/unittest/NewPortfolio.java
> src/test/java/parReg/query/unittest/Position.java
> src/test/java/perffmwk/Formatter.java
> src/test/java/templates/security/DummyAuthenticator.java
> src/test/java/templates/security/DummyAuthorization.java
> src/test/java/templates/security/FunctionSecurityPrmsHolder.java
> src/test/java/templates/security/LdapUserAuthenticator.java
> src/test/java/templates/security/PKCSAuthenticator.java
> src/test/java/templates/security/PKCSAuthInt.java
> src/test/java/templates/security/PKCSPrincipal.java
> src/test/java/templates/security/UsernamePrincipal.java
> src/test/java/templates.security/UserPasswordAuthInit.java
> src/test/java/templates.security/XmlAuthorization.java
> src/test/java/templates.security/XmlErrorHandler.java
> src/test/java/util/TestException.java
> The following are Hydra-related resources in src/test/resources that also 
> need to be removed:
> src/test/resources/jta/cachejta.xml
> src/test/resources/ssl/trusted.keystore
> src/test/resources/templates/security/authz5_5.dtd
> src/test/resources/templates/security/authz6_0.dtd



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

[jira] [Resolved] (GEODE-748) Unexpected version string returned from gfsh

2016-05-26 Thread Kevin Duling (JIRA) 

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

Kevin Duling resolved GEODE-748.

   Resolution: Resolved
Fix Version/s: 1.0.0-incubating.M3

> Unexpected version string returned from gfsh
> 
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is 
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.



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

[jira] [Assigned] (GEODE-1460) RemoveAll fails with NPE in com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.checkAndRemoveFromClientMsgsRegion()

2016-05-26 Thread Jianxia Chen (JIRA) 

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

Jianxia Chen reassigned GEODE-1460:
---

Assignee: Jianxia Chen

> RemoveAll fails with NPE in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.checkAndRemoveFromClientMsgsRegion()
> -
>
> Key: GEODE-1460
> URL: https://issues.apache.org/jira/browse/GEODE-1460
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>
> Source Revision: 3e8a610e99bc005bcc56c378e3d1e2274a3d468c
> Source Repository: develop
> Got unexpected exception java.lang.NullPointerException
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.checkAndRemoveFromClientMsgsRegion(CacheClientNotifier.java:1439)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.singletonRouteClientMessage(CacheClientNotifier.java:990)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.singletonNotifyClients(CacheClientNotifier.java:910)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.notifyClients(CacheClientNotifier.java:771)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegion.notifyBridgeClients(LocalRegion.java:6616)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:7377)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.BucketRegion.invokeDestroyCallbacks(BucketRegion.java:1642)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegion.postRemoveAllFireEvents(LocalRegion.java:10846)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.postRemoveAll(LocalRegionDataView.java:289)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.partitioned.RemoveAllPRMessage.doLocalRemoveAll(RemoveAllPRMessage.java:529)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.partitioned.RemoveAllPRMessage.operateOnPartitionedRegion(RemoveAllPRMessage.java:329)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:322)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:655)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionManager$8$1.run(DistributionManager.java:1072)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> java.lang.Thread.run(Thread.java:745)
> at 
> com.gemstone.gemfire.distributed.internal.ReplyException.handleAsUnexpected(ReplyException.java:83)
> at 
> com.gemstone.gemfire.internal.cache.partitioned.PartitionMessage$PartitionResponse.waitForCacheException(PartitionMessage.java:811)
> at 
>

[jira] [Commented] (GEODE-1460) RemoveAll fails with NPE in com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.checkAndRemoveFromClientMsgsRegion()

2016-05-26 Thread Jianxia Chen (JIRA) 

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

Jianxia Chen commented on GEODE-1460:
-

Threads are not properly synchronized. One thread just created the 
ccnSingleton, but before it created haContainer (haContainer is still null at 
this point), the other threads read the null haContainer, which resulted in a 
NPE.

> RemoveAll fails with NPE in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.checkAndRemoveFromClientMsgsRegion()
> -
>
> Key: GEODE-1460
> URL: https://issues.apache.org/jira/browse/GEODE-1460
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Jianxia Chen
>
> Source Revision: 3e8a610e99bc005bcc56c378e3d1e2274a3d468c
> Source Repository: develop
> Got unexpected exception java.lang.NullPointerException
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.checkAndRemoveFromClientMsgsRegion(CacheClientNotifier.java:1439)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.singletonRouteClientMessage(CacheClientNotifier.java:990)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.singletonNotifyClients(CacheClientNotifier.java:910)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.notifyClients(CacheClientNotifier.java:771)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegion.notifyBridgeClients(LocalRegion.java:6616)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:7377)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.BucketRegion.invokeDestroyCallbacks(BucketRegion.java:1642)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegion.postRemoveAllFireEvents(LocalRegion.java:10846)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.postRemoveAll(LocalRegionDataView.java:289)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.partitioned.RemoveAllPRMessage.doLocalRemoveAll(RemoveAllPRMessage.java:529)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.partitioned.RemoveAllPRMessage.operateOnPartitionedRegion(RemoveAllPRMessage.java:329)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:322)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:655)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> com.gemstone.gemfire.distributed.internal.DistributionManager$8$1.run(DistributionManager.java:1072)
> at Remote Member 
> 'sol11-bvt-10(bridgegemfire4_sol11-bvt-10_2565:2565):1031' in 
> java.lang.Thread.run(Thread.java:745)
> at 
> com.gemstone.gemfire.distributed.internal.ReplyException.handleAsUnexpected(ReplyException.java:83)
> at 
>

[jira] [Commented] (GEODE-748) Unexpected version string returned from gfsh

2016-05-26 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on GEODE-748:
--

Github user asfgit closed the pull request at:

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


> Unexpected version string returned from gfsh
> 
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is 
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.



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

[jira] [Commented] (GEODE-1331) gfsh.bat on Windows is incorrect

2016-05-26 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user kjduling opened a pull request:

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

GEODE-1331: gfsh.bat on Windows is incorrect

* Renamed internal variable from CLASSPATH to DEPENDENCIES.
* Verified @setlocal was not altering the System environment variables for 
the shell.
* Launch with -classpath param like the bash script does.
* Ensured command-line arguments match bash script's order of arguments.

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

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

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

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


commit 79842cbea7fd2c6c9e4e67d966b11ed379159375
Author: Kevin J. Duling 
Date:   2016-05-26T16:46:03Z

GEODE-1331: gfsh.bat on Windows is incorrect

* Renamed internal variable from CLASSPATH to DEPENDENCIES.
* Verified @setlocal was not altering the System environment variables for 
the shell.
* Launch with -classpath param like the bash script does.
* Ensured command-line arguments match bash script's order of arguments.




> gfsh.bat on Windows is incorrect
> 
>
> Key: GEODE-1331
> URL: https://issues.apache.org/jira/browse/GEODE-1331
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> Initial report:
> {noformat}
> I am doing testing in windows STS. I am not adding these dependencies jars, 
> gfsh.bat is what doing this.
>  
> C:\DEV\Pivotal\GemFire_v82014\bin\gfsh.bat has below code, which is setting 
> gemfire, antlr, gfsh-dependencies and pulse-dependencies jars in classpath.
> Line 26 to 29
> @set 
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> @if defined CLASSPATH (
> @set GEMFIRE_JARS=%GEMFIRE_JARS%;%CLASSPATH%
> )
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\antlr.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\pulse-dependencies.jar
>  
> Unix C:\DEV\Pivotal\GemFire_v82014\bin script, does not set these jars in 
> classpath.
>  
>  
> Another observation is that, if I pass --include-system-classpath to gfsh 
> start server command, then it is prepending
> gemfire.jar and gfsh-dependencies.jar to the system classpath and adding that 
> to the server, that is what is shown in logs
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar
> 
> ………..
> C:\Program Files\Java\jdk1.7.0_67\lib\tools.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>  
> start server \
> --name=${NAME} --server-port=${PORT} \
> --properties-file=${GEMFIRE_PWD}/resources/cache.properties \
> --J=-Dgemfire.distributed-system-id=${DISTRIBUTED_SYSTEM_ID} \
> --J=-Dgemfire.bind-address=${HOST_NAME} 
> --J=-Dgemfire.server-bind-address=${HOST_NAME} \
> --J=-Dgemfire.locators=${HOST_NAME}[${LOCATOR_PORT}] \
> --J=-Dgemfire.OSProcess.ENABLE_OUTPUT_REDIRECTION=true \
> --include-system-classpath
>  
> If I don’t pass this parameter, then it does not add gfsh-dependencies
>   Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>  
> I am trying to do testing without using –include-system-classpath instead add 
> jars in to the start server –classpath as a work around.
> {noformat}
> And a subsequent reply from John Blum:
> {noformat}
> My apologies.  I was not aware that you were launching your GemFire process 
> (e.g. Server) using Gfsh, and specifically with gfsh.bat on Windows.
> I just confirmed the line(s) you were looking at in gfsh.bat, and indeed the 
> BAT file is wrong!  Specifically, the classpath for the GemFire process 
> is being constructed from the following lines...
> @set 
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> ...
> @set GFSH_JARS=;%GEMFIRE%\lib\gfsh-dependencies.jar
> @set CLASSPATH=%GFSH_JARS%;%GEMFIRE_JARS%
> The Windows BAT file is also inconsistent with the Bash shell version (gfsh), 
> which rightfully only contains...
> GEMFIRE_JARS=$GEMFIRE/lib/gfsh-dependencies.jar
> if [ "x$CLASSPATH"

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

2016-05-26 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1452:


Commit 7bf73004432c13b8415f9cd5e34c82913b16d002 in incubator-geode's branch 
refs/heads/feature/GEODE-1452 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=7bf7300 ]

Merge remote-tracking branch 'origin/develop' into feature/GEODE-1452


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



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

[jira] [Commented] (GEODE-748) Unexpected version string returned from gfsh

2016-05-26 Thread ASF subversion and git services (JIRA) 

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

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

Commit 525cd811217a32895dee2518ad851a50a6499332 in incubator-geode's branch 
refs/heads/feature/GEODE-1452 from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=525cd81 ]

GEODE-748: Unexpected version string returned from gfsh


> Unexpected version string returned from gfsh
> 
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is 
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.



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

[jira] [Commented] (GEODE-1296) OffHeapStoredObject.getRawBytes should assert that it is not called on compressed data

2016-05-26 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1296:


Commit 6c626b7ebc134d85160ff2d253ed12762fe49728 in incubator-geode's branch 
refs/heads/feature/GEODE-1452 from [~khowe]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6c626b7 ]

GEODE-1296: change conditional in getRawBytes to assert


> OffHeapStoredObject.getRawBytes should assert that it is not called on 
> compressed data
> --
>
> Key: GEODE-1296
> URL: https://issues.apache.org/jira/browse/GEODE-1296
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Kenneth Howe
> Fix For: 1.0.0-incubating.M3
>
>
> The current code does this:
>   if (isCompressed()) {
> throw new UnsupportedOperationException();
>   }
> It would be more clear if it just did this:
>   assert !isCompressed();



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

[jira] [Assigned] (GEODE-1316) Update @since tags to include GemFire or Geode in the version name

2016-05-26 Thread Jason Huynh (JIRA) 

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

Jason Huynh reassigned GEODE-1316:
--

Assignee: Jason Huynh

> Update @since tags to include GemFire or Geode in the version name
> --
>
> Key: GEODE-1316
> URL: https://issues.apache.org/jira/browse/GEODE-1316
> Project: Geode
>  Issue Type: Task
>  Components: client queues, docs
>Reporter: Dan Smith
>Assignee: Jason Huynh
> Fix For: 1.0.0-incubating.M3
>
>
> Based on [this 
> discussion|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3CCAFh%2B7k1nPayKdS--rvqG4uvB%3DjKnTibNqHkfFJf0Kkiy9wQ7bw%40mail.gmail.com%3E]
>  on the mailing list, we want to update all of our \@since tags to be either 
> Geode x.y.z or GemFire x.y.z, depending on when the new method was added to 
> the public API.
> We need to go through all of the existing tags and update them to match this 
> standard. Almost all of them should become \@since GemFire x.y.z unless they 
> are 1.0 or 9.0, in which case they should probably be \@since Geode 1.0.0.



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

[jira] [Resolved] (GEODE-1453) if field value is null, creating index will fail with NPE

2016-05-26 Thread xiaojian zhou (JIRA) 

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

xiaojian zhou resolved GEODE-1453.
--
Resolution: Fixed

> if field value is null, creating index will fail with NPE
> -
>
> Key: GEODE-1453
> URL: https://issues.apache.org/jira/browse/GEODE-1453
> Project: Geode
>  Issue Type: Bug
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>




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