[jira] [Commented] (GEODE-610) Review Geode's LICENSE & NOTICE File(s)

2016-01-20 Thread Niall Pemberton (JIRA)

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

Niall Pemberton commented on GEODE-610:
---

OK, sounds good.

> Review Geode's LICENSE & NOTICE File(s)
> ---
>
> Key: GEODE-610
> URL: https://issues.apache.org/jira/browse/GEODE-610
> Project: Geode
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.0.0-incubating
>Reporter: Niall Pemberton
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
> Attachments: Geode-Dependency-License-Review-2015-11-28.csv, 
> Geode-Source-License-Review-2015-11-28.csv, netty-4.0.33.Final-NOTICE.txt, 
> spring-core-3.2.12.RELEASE-notice.txt
>
>
> Need to review Geode's LICENSE & NOTICE File(s).
> Guide on these files is available here:
>   - http://www.apache.org/dev/licensing-howto.html



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


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

2016-01-20 Thread Jens Deppe (JIRA)

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

Jens Deppe commented on GEODE-746:
--

Actually, there are two things wrong here. The first is simply the incorrect 
text being displayed.

The second is the message stating {{Failed to connect; unknown cause: 
Connection refused}}.

I believe what's happening is that the locator is connecting back to itself to 
check it's status. The problem becomes more evident when we bind the jmx 
manager to an address. At that point, gfsh will not be able to successfully 
connect to the JMX manager and will get an error like:
{noformat}
Connecting to Locator at [host=localhost, port=19991] ..
Connecting to Manager at [host=localhost, port=1099] ..
Connection refused to host: 192.168.1.28; nested exception is:
java.net.ConnectException: Connection refused
{noformat}
This can be resolved by setting  {{java.rmi.server.hostname=127.0.0.1}} on the 
locator. We should consider setting {{java.rmi.server.hostname}} when using 
{{jmx-manager-bind-address}} (or just {{bind-address}}).

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



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


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

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-805:

Component/s: general

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




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


[jira] [Resolved] (GEODE-806) Fix javadoc warnings in management packages

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-806.
-
Resolution: Fixed

> Fix javadoc warnings in management packages
> ---
>
> Key: GEODE-806
> URL: https://issues.apache.org/jira/browse/GEODE-806
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> admin pkg:
> {noformat}
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminConfig.java:46:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystem.java:43:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystemFactory.java:39:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminException.java:31:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminXmlException.java:29:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\Alert.java:29:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertLevel.java:30:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertListener.java:24:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\BackupStatus.java:33:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheDoesNotExistException.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheHealthConfig.java:70:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVm.java:33:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVmConfig.java:29:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ConfigurationParameter.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemConfig.java:62:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemHealthConfig.java:54:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocator.java:32:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocatorConfig.java:45:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealth.java:48:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealthConfig.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireMemberStatus.java:58:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntity.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntityConfig.java:32:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\MemberHealthConfig.java:53:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\OperationCancelledException.java:30:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfi

[jira] [Commented] (GEODE-805) Fix javadoc warnings

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

Commit 942b89e0b1591a6ccf9cefa4c0e3f5dba8bad34b in incubator-geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=942b89e ]

GEODE-805: Fix javadoc warnings in management packages


> Fix javadoc warnings
> 
>
> Key: GEODE-805
> URL: https://issues.apache.org/jira/browse/GEODE-805
> Project: Geode
>  Issue Type: Bug
>Reporter: Kirk Lund
>Priority: Trivial
>




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


[jira] [Commented] (GEODE-818) RC Feedback: Fix Maven & pom dependencies

2016-01-20 Thread Dan Smith (JIRA)

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

Dan Smith commented on GEODE-818:
-

The HDFS API has been disabled (see GEODE-10). It seems like any dependencies 
on HDFS should be pulled out - hbase, hadoop, commons-logging, ??

> RC Feedback: Fix Maven & pom dependencies
> -
>
> Key: GEODE-818
> URL: https://issues.apache.org/jira/browse/GEODE-818
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>
> Maven and POM dependencies are too many for simple
> From [~niall.pember...@btinternet.com]:
> If I'm building a gemfire client and depend on gemfire-core, do I really need 
> all those dependencies? Do I always need them for a gemfire member? Looks to 
> me like some of them should be "optional" or "provided" - especially some of 
> the logging stuff.
> * Spring Framework only referenced in CLI & Web, except XmlEntity (uses 
> org.springframework.util.Assert) and PdxInstanceImpl (uses 
> org.springframework.util.StringUtils)
> * SequenceFile only class to directly reference commons-logging
> * commons-lang only used in hdfs & CLI
> * javax.mail only used in MailManager
> * Jetty only referenced by ManagementAgent & RestAgent, except for 
> CumulativeNonDistinctResults
> * Netty only referenced in the redis package
> * Can't find any reference to slf4j



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


[jira] [Commented] (GEODE-631) CI failure: PRQueryRegionDestroyedDUnitTest.testPRWithRegionDestroyInOneDatastoreWithDelay

2016-01-20 Thread Jason Huynh (JIRA)

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

Jason Huynh commented on GEODE-631:
---

This test creates a pr across 2 nodes and then asynchronously executes a list 
of queries.  The main thread sleeps for 5 milliseconds and kicks off another 
asynch task that does a region close in one of the randomly chosen nodes but 
soon after closing, will recreate the region.

The test expects the thread executing the list of queries to hit a 
ForceReattemptException.  Based on this, it looks like this test could be 
running into a race condition where the query is executing after the region has 
been destroyed before query compilation.  

Due to the way this test is written, the original test would have probably 
always failed intermittently.  We can add a RegionNotFoundException to the 
check but in the long run we should figure out a way to write a better test for 
this scenario.

> CI failure: 
> PRQueryRegionDestroyedDUnitTest.testPRWithRegionDestroyInOneDatastoreWithDelay
> --
>
> Key: GEODE-631
> URL: https://issues.apache.org/jira/browse/GEODE-631
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Darrel Schneider
>Assignee: Jason Huynh
>  Labels: CI
>
> git rev 9283282c64076c5f8e599f3d47895f3c48e205e8 build #815:
> junit.framework.AssertionFailedError: Unexpected exception during query: 
> util.TestException: 
> PRQueryDUnitHelper#getCacheSerializableRunnableForPRQueryAndCompareResults: 
> Caught unexpected query exception
>   at 
> com.gemstone.gemfire.cache.query.partitioned.PRQueryDUnitHelper$13.run2(PRQueryDUnitHelper.java:758)
>   
> Caused by: com.gemstone.gemfire.cache.query.RegionNotFoundException: Region 
> not found:  /Portfolios
>   at 
> com.gemstone.gemfire.cache.query.internal.CompiledRegion.evaluate(CompiledRegion.java:88)
>   at 
> com.gemstone.gemfire.cache.query.internal.CompiledIteratorDef.evaluateCollection(CompiledIteratorDef.java:164)
>   at 
> com.gemstone.gemfire.cache.query.internal.RuntimeIterator.evaluateCollection(RuntimeIterator.java:111)
>   at 
> com.gemstone.gemfire.cache.query.internal.CompiledIteratorDef.getRuntimeIterator(CompiledIteratorDef.java:108)
>   at 
> com.gemstone.gemfire.cache.query.internal.CompiledSelect.computeDependencies(CompiledSelect.java:185)
>   at 
> com.gemstone.gemfire.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:568)
>   at 
> com.gemstone.gemfire.internal.cache.PRQueryProcessor.executeQueryOnBuckets(PRQueryProcessor.java:398)
>   at 
> com.gemstone.gemfire.internal.cache.PRQueryProcessor.executeSequentially(PRQueryProcessor.java:361)
>   at 
> com.gemstone.gemfire.internal.cache.PRQueryProcessor.executeQuery(PRQueryProcessor.java:147)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.QueryMessage.operateOnPartitionedRegion(QueryMessage.java:199)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:323)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451)



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


[jira] [Assigned] (GEODE-825) A client with subscriptions enabled receives an additional event when invoking get with a CacheLoader

2016-01-20 Thread Barry Oglesby (JIRA)

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

Barry Oglesby reassigned GEODE-825:
---

Assignee: Barry Oglesby

> A client with subscriptions enabled receives an additional event when 
> invoking get with a CacheLoader
> -
>
> Key: GEODE-825
> URL: https://issues.apache.org/jira/browse/GEODE-825
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>
> If a client with subscriptions enabled invokes get on a server that causes a 
> CacheLoader to be invoked, the client receives two events, namely a 
> {{LOCAL_LOAD_CREATE}} from the local put and a {{CREATE}} or {{INVALIDATE}} 
> from the subscription channel. It should not receive the subscription channel 
> event.
> Here is an example of the events for a single client get:
> {noformat}
> Cache Client Updater Thread  on mymac(59131):1026 port 60830: 
> TestListener received INVALIDATE (1) for: 99
> main: TestListener received LOCAL_LOAD_CREATE (2) for: 99->Trade[id=99; 
> cusip=VMW; shares=100; price=95.0]
> {noformat}



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


[jira] [Created] (GEODE-825) A client with subscriptions enabled receives an additional event when invoking get with a CacheLoader

2016-01-20 Thread Barry Oglesby (JIRA)
Barry Oglesby created GEODE-825:
---

 Summary: A client with subscriptions enabled receives an 
additional event when invoking get with a CacheLoader
 Key: GEODE-825
 URL: https://issues.apache.org/jira/browse/GEODE-825
 Project: Geode
  Issue Type: Bug
  Components: client/server
Reporter: Barry Oglesby


If a client with subscriptions enabled invokes get on a server that causes a 
CacheLoader to be invoked, the client receives two events, namely a 
{{LOCAL_LOAD_CREATE}} from the local put and a {{CREATE}} or {{INVALIDATE}} 
from the subscription channel. It should not receive the subscription channel 
event.

Here is an example of the events for a single client get:
{noformat}
Cache Client Updater Thread  on mymac(59131):1026 port 60830: 
TestListener received INVALIDATE (1) for: 99
main: TestListener received LOCAL_LOAD_CREATE (2) for: 99->Trade[id=99; 
cusip=VMW; shares=100; price=95.0]
{noformat}



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


[jira] [Resolved] (GEODE-822) Remove unused imports that cause build warnings

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund resolved GEODE-822.
-
Resolution: Fixed

> Remove unused imports that cause build warnings
> ---
>
> Key: GEODE-822
> URL: https://issues.apache.org/jira/browse/GEODE-822
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> Remove unused imports for anything causing a build warning. Ex: 
> MemLRUEvictionControllerDUnitTest has an unused import of sun.misc.Unsafe 
> which causes warnings during build.
> C:\dev\geode\gemfire-core\src\test\java\com\gemstone\gemfire\cache30\MemLRUEvictionControllerDUnitTest.java:22:
>  warning: Unsafe is internal proprietary API and may be removed in a future 
> release
> import sun.misc.Unsafe;
>^



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


[jira] [Commented] (GEODE-822) Remove unused imports that cause build warnings

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

Commit d6a9ac10226df9e10256acac83683f4d2c1405e4 in incubator-geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=d6a9ac1 ]

GEODE-822: Remove unused imports that cause build warnings


> Remove unused imports that cause build warnings
> ---
>
> Key: GEODE-822
> URL: https://issues.apache.org/jira/browse/GEODE-822
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> Remove unused imports for anything causing a build warning. Ex: 
> MemLRUEvictionControllerDUnitTest has an unused import of sun.misc.Unsafe 
> which causes warnings during build.
> C:\dev\geode\gemfire-core\src\test\java\com\gemstone\gemfire\cache30\MemLRUEvictionControllerDUnitTest.java:22:
>  warning: Unsafe is internal proprietary API and may be removed in a future 
> release
> import sun.misc.Unsafe;
>^



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


[jira] [Resolved] (GEODE-771) CI Failure: PdxGroupByPartitionedQueryDUnitTest.testCompactRangeIndex failed with AssertionFailedError

2016-01-20 Thread Jason Huynh (JIRA)

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

Jason Huynh resolved GEODE-771.
---
Resolution: Fixed

Have not seen a reoccurrence since fix was checked in.

> CI Failure: PdxGroupByPartitionedQueryDUnitTest.testCompactRangeIndex failed 
> with AssertionFailedError
> --
>
> Key: GEODE-771
> URL: https://issues.apache.org/jira/browse/GEODE-771
> Project: Geode
>  Issue Type: Bug
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> This was reproduced in a private run.
> junit.framework.AssertionFailedError: Order of results was not the same, 
> match not found for :YHOO compared with:SAP; failed query=select pos.secId 
> from  /portfolio  p, p.positions.values pos where NOT (pos.secId IN 
> SET('SUN', 'ORCL')) ; element unmatched =YHOO;p1 class=class java.lang.String 
> compared with SAP;p2 class=class java.lang.StringcurrentIndex:108
> r1:[YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, 
> YHOO, YHOO, YHOO, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, DELL, DELL, 
> DELL, DELL, DELL, DELL, DELL, IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, 
> IBM, IBM, IBM, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, APPL, APPL, APPL, 
> APPL, APPL, APPL, HP, HP, HP, HP, HP, HP, HP, HP, RHAT, RHAT, RHAT, RHAT, 
> RHAT, RHAT, RHAT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, NOVL, 
> NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, 
> GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, 
> YHOO, YHOO, YHOO, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, 
> DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, IBM, IBM, 
> IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, AOL, AOL, AOL, AOL, AOL, AOL, 
> AOL, AOL, AOL, AOL, AOL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, 
> APPL, APPL, APPL, APPL, APPL, APPL, APPL, HP, HP, HP, HP, HP, HP, HP, HP, HP, 
> HP, HP, HP, HP, HP, HP, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, 
> RHAT, RHAT, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, 
> NOVL, NOVL, NOVL, NOVL, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, 
> MSFT, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, YHOO, YHOO, 
> YHOO, YHOO, YHOO, YHOO, YHOO, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, 
> SAP, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, 
> DELL, IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, AOL, AOL, AOL, AOL, AOL, AOL, 
> AOL, AOL, AOL, AOL, AOL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, 
> APPL, HP, HP, HP, HP, HP, HP, HP, HP, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, 
> RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, 
> NOVL, NOVL, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, 
> GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG]
> r2:[YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, 
> YHOO, YHOO, YHOO, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, DELL, DELL, 
> DELL, DELL, DELL, DELL, DELL, IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, IBM, 
> IBM, IBM, IBM, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, APPL, APPL, APPL, 
> APPL, APPL, APPL, HP, HP, HP, HP, HP, HP, HP, HP, RHAT, RHAT, RHAT, RHAT, 
> RHAT, RHAT, RHAT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, NOVL, 
> NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, 
> GOOG, GOOG, GOOG, GOOG, GOOG, GOOG, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, 
> SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, DELL, DELL, DELL, DELL, 
> DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, IBM, IBM, IBM, IBM, 
> IBM, IBM, IBM, IBM, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, 
> APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, HP, HP, HP, HP, HP, HP, 
> HP, HP, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, 
> RHAT, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, MSFT, MSFT, MSFT, 
> MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, GOOG, GOOG, GOOG, GOOG, GOOG, 
> GOOG, GOOG, GOOG, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, YHOO, 
> SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, SAP, DELL, DELL, DELL, 
> DELL, DELL, DELL, DELL, DELL, DELL, DELL, DELL, IBM, IBM, IBM, IBM, IBM, IBM, 
> IBM, IBM, IBM, IBM, IBM, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, AOL, 
> AOL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, APPL, 
> APPL, APPL, APPL, HP, HP, HP, HP, HP, HP, HP, HP, HP, HP, HP, HP, HP, HP, HP, 
> RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, RHAT, NOVL, NOVL, 
> NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, NOVL, 
> MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, MSFT, GOOG, GOOG, GOOG, 
> GOOG, 

[jira] [Commented] (GEODE-393) FunctionContext should provide a Cache

2016-01-20 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on GEODE-393:
--

Github user upthewaterspout commented on the pull request:

https://github.com/apache/incubator-geode/pull/74#issuecomment-173369343
  
This is GEODE-393. I discussed this with Shreedhar, these changes need some 
tests and then they should be good to merge. I'll pick this up.


> FunctionContext should provide a Cache
> --
>
> Key: GEODE-393
> URL: https://issues.apache.org/jira/browse/GEODE-393
> Project: Geode
>  Issue Type: Improvement
>  Components: functions
>Reporter: Dan Smith
>Assignee: Dan Smith
>  Labels: starter
>
> FunctionContext has methods to get the arguments to the function and the 
> result sender, but there is no way to get the Cache or DistributedSystem.
> This means pretty much any function will need to statically look up the cache 
> using CacheFactory.getAnyInstance(). While that works, it makes it impossible 
> to write unit tests for functions by passing in a mock cache.
> Note that onRegion functions are provided a RegionFunctionContext, which does 
> provide these functions with a means to look up the cache, but not all 
> functions are applied to a region.



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


[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest

2016-01-20 Thread Dan Smith (JIRA)

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

Dan Smith updated GEODE-824:

Labels: ci  (was: )

> Failure from JGroupsMessengerJUnitTest.testMulticastTest
> 
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
>  Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
>  Labels: ci
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this 
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}



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


[jira] [Created] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest

2016-01-20 Thread Dan Smith (JIRA)
Dan Smith created GEODE-824:
---

 Summary: Failure from JGroupsMessengerJUnitTest.testMulticastTest
 Key: GEODE-824
 URL: https://issues.apache.org/jira/browse/GEODE-824
 Project: Geode
  Issue Type: Bug
Reporter: Dan Smith


This test fails consistently on my ubuntu 15.10 machine. It looks like this was 
introduced in b826b4b0077dc159cbcee68775cc197b025d5586

I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
{noformat}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
{noformat}



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


[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest

2016-01-20 Thread Dan Smith (JIRA)

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

Dan Smith updated GEODE-824:

Assignee: Bruce Schuchardt

> Failure from JGroupsMessengerJUnitTest.testMulticastTest
> 
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
>  Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
>  Labels: ci
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this 
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}



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


[jira] [Updated] (GEODE-823) RC Feedback: Fix build artifacts

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba updated GEODE-823:
--
Description: 
>From [~niall.pember...@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR 
>SEPARATE ISSUES:

* The ASF frowns upon distributing other open source projects without their 
consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns

* Also not re-packaging it means users could face a dependency issue if they 
also use joptsimple

* Lastly, "gemfire-joptsimple" could violate someone elses mark
More specific feedback:
* pom dependencies look like an issue - see GEODE-818
* It would be better if the maven artifacts were named "geode" rather than 
"gemfire"
* pom files don't have the license header
* The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to not 
create this maven artifact
* The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)

  was:
>From [~niall.pember...@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR 
>SEPARATE ISSUES:

* The ASF frowns upon distributing other open source projects without their 
consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns.

Also not re-packaging it means users could face a dependency issue if they also 
use joptsimple. 

Lastly, "gemfire-joptsimple" could violate someone elses mark.
* pom dependencies look like an issue - see below
* It would be better if the maven artifacts were named "geode" rather than 
"gemfire"
* pom files don't have the license header
* The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to not 
create this maven artifact
* The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)


> RC Feedback: Fix build artifacts
> 
>
> Key: GEODE-823
> URL: https://issues.apache.org/jira/browse/GEODE-823
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>
> From [~niall.pember...@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR 
> SEPARATE ISSUES:
> * The ASF frowns upon distributing other open source projects without their 
> consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns
> * Also not re-packaging it means users could face a dependency issue if they 
> also use joptsimple
> * Lastly, "gemfire-joptsimple" could violate someone elses mark
> More specific feedback:
> * pom dependencies look like an issue - see GEODE-818
> * It would be better if the maven artifacts were named "geode" rather than 
> "gemfire"
> * pom files don't have the license header
> * The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to 
> not create this maven artifact
> * The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)



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


[jira] [Updated] (GEODE-823) RC Feedback: Fix build artifacts

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba updated GEODE-823:
--
Description: 
>From [~niall.pember...@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR 
>SEPARATE ISSUES:

* The ASF frowns upon distributing other open source projects without their 
consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns.

Also not re-packaging it means users could face a dependency issue if they also 
use joptsimple. 

Lastly, "gemfire-joptsimple" could violate someone elses mark.
* pom dependencies look like an issue - see below
* It would be better if the maven artifacts were named "geode" rather than 
"gemfire"
* pom files don't have the license header
* The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to not 
create this maven artifact
* The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)

> RC Feedback: Fix build artifacts
> 
>
> Key: GEODE-823
> URL: https://issues.apache.org/jira/browse/GEODE-823
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>
> From [~niall.pember...@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR 
> SEPARATE ISSUES:
> * The ASF frowns upon distributing other open source projects without their 
> consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns.
> Also not re-packaging it means users could face a dependency issue if they 
> also use joptsimple. 
> Lastly, "gemfire-joptsimple" could violate someone elses mark.
> * pom dependencies look like an issue - see below
> * It would be better if the maven artifacts were named "geode" rather than 
> "gemfire"
> * pom files don't have the license header
> * The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to 
> not create this maven artifact
> * The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)



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


[jira] [Updated] (GEODE-823) RC Feedback: Fix build artifacts

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba updated GEODE-823:
--
Affects Version/s: 1.0.0-incubating.M1

> RC Feedback: Fix build artifacts
> 
>
> Key: GEODE-823
> URL: https://issues.apache.org/jira/browse/GEODE-823
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>




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


[jira] [Updated] (GEODE-818) RC Feedback: Fix Maven & pom dependencies

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba updated GEODE-818:
--
Description: 
Maven and POM dependencies are too many for simple

>From [~niall.pember...@btinternet.com]:

If I'm building a gemfire client and depend on gemfire-core, do I really need 
all those dependencies? Do I always need them for a gemfire member? Looks to me 
like some of them should be "optional" or "provided" - especially some of the 
logging stuff.

* Spring Framework only referenced in CLI & Web, except XmlEntity (uses 
org.springframework.util.Assert) and PdxInstanceImpl (uses 
org.springframework.util.StringUtils)
* SequenceFile only class to directly reference commons-logging
* commons-lang only used in hdfs & CLI
* javax.mail only used in MailManager
* Jetty only referenced by ManagementAgent & RestAgent, except for 
CumulativeNonDistinctResults
* Netty only referenced in the redis package
* Can't find any reference to slf4j



> RC Feedback: Fix Maven & pom dependencies
> -
>
> Key: GEODE-818
> URL: https://issues.apache.org/jira/browse/GEODE-818
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>
> Maven and POM dependencies are too many for simple
> From [~niall.pember...@btinternet.com]:
> If I'm building a gemfire client and depend on gemfire-core, do I really need 
> all those dependencies? Do I always need them for a gemfire member? Looks to 
> me like some of them should be "optional" or "provided" - especially some of 
> the logging stuff.
> * Spring Framework only referenced in CLI & Web, except XmlEntity (uses 
> org.springframework.util.Assert) and PdxInstanceImpl (uses 
> org.springframework.util.StringUtils)
> * SequenceFile only class to directly reference commons-logging
> * commons-lang only used in hdfs & CLI
> * javax.mail only used in MailManager
> * Jetty only referenced by ManagementAgent & RestAgent, except for 
> CumulativeNonDistinctResults
> * Netty only referenced in the redis package
> * Can't find any reference to slf4j



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


[jira] [Created] (GEODE-823) RC Feedback: Fix build artifacts

2016-01-20 Thread Nitin Lamba (JIRA)
Nitin Lamba created GEODE-823:
-

 Summary: RC Feedback: Fix build artifacts
 Key: GEODE-823
 URL: https://issues.apache.org/jira/browse/GEODE-823
 Project: Geode
  Issue Type: Task
Reporter: Nitin Lamba






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


[jira] [Assigned] (GEODE-806) Fix javadoc warnings in management packages

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-806:
---

Assignee: Kirk Lund

> Fix javadoc warnings in management packages
> ---
>
> Key: GEODE-806
> URL: https://issues.apache.org/jira/browse/GEODE-806
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> admin pkg:
> {noformat}
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminConfig.java:46:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystem.java:43:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystemFactory.java:39:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminException.java:31:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminXmlException.java:29:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\Alert.java:29:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertLevel.java:30:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertListener.java:24:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\BackupStatus.java:33:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheDoesNotExistException.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheHealthConfig.java:70:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVm.java:33:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVmConfig.java:29:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ConfigurationParameter.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemConfig.java:62:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemHealthConfig.java:54:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocator.java:32:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocatorConfig.java:45:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealth.java:48:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealthConfig.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireMemberStatus.java:58:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntity.java:28:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntityConfig.java:32:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\MemberHealthConfig.java:53:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\OperationCancelledException.java:30:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemston

[jira] [Created] (GEODE-822) Remove unused imports that cause build warnings

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-822:
---

 Summary: Remove unused imports that cause build warnings
 Key: GEODE-822
 URL: https://issues.apache.org/jira/browse/GEODE-822
 Project: Geode
  Issue Type: Bug
  Components: general
Reporter: Kirk Lund


Remove unused imports for anything causing a build warning. Ex: 
MemLRUEvictionControllerDUnitTest has an unused import of sun.misc.Unsafe which 
causes warnings during build.

C:\dev\geode\gemfire-core\src\test\java\com\gemstone\gemfire\cache30\MemLRUEvictionControllerDUnitTest.java:22:
 warning: Unsafe is internal proprietary API and may be removed in a future 
release
import sun.misc.Unsafe;
   ^




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


[jira] [Updated] (GEODE-822) Remove unused imports that cause build warnings

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-822:

Priority: Trivial  (was: Major)

> Remove unused imports that cause build warnings
> ---
>
> Key: GEODE-822
> URL: https://issues.apache.org/jira/browse/GEODE-822
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Kirk Lund
>Priority: Trivial
>
> Remove unused imports for anything causing a build warning. Ex: 
> MemLRUEvictionControllerDUnitTest has an unused import of sun.misc.Unsafe 
> which causes warnings during build.
> C:\dev\geode\gemfire-core\src\test\java\com\gemstone\gemfire\cache30\MemLRUEvictionControllerDUnitTest.java:22:
>  warning: Unsafe is internal proprietary API and may be removed in a future 
> release
> import sun.misc.Unsafe;
>^



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


[jira] [Assigned] (GEODE-822) Remove unused imports that cause build warnings

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-822:
---

Assignee: Kirk Lund

> Remove unused imports that cause build warnings
> ---
>
> Key: GEODE-822
> URL: https://issues.apache.org/jira/browse/GEODE-822
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> Remove unused imports for anything causing a build warning. Ex: 
> MemLRUEvictionControllerDUnitTest has an unused import of sun.misc.Unsafe 
> which causes warnings during build.
> C:\dev\geode\gemfire-core\src\test\java\com\gemstone\gemfire\cache30\MemLRUEvictionControllerDUnitTest.java:22:
>  warning: Unsafe is internal proprietary API and may be removed in a future 
> release
> import sun.misc.Unsafe;
>^



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


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

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-805:

Priority: Trivial  (was: Major)

> Fix javadoc warnings
> 
>
> Key: GEODE-805
> URL: https://issues.apache.org/jira/browse/GEODE-805
> Project: Geode
>  Issue Type: Bug
>Reporter: Kirk Lund
>Priority: Trivial
>




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


[jira] [Assigned] (GEODE-773) Extract static methods from DistributedTestCase

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-773:
---

Assignee: Kirk Lund

> Extract static methods from DistributedTestCase
> ---
>
> Key: GEODE-773
> URL: https://issues.apache.org/jira/browse/GEODE-773
> Project: Geode
>  Issue Type: Sub-task
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> This is a sub-task to merge changes incrementally from feature/GEODE-217.
> Extract static methods from DistributedTestCase to new classes with better 
> defined responsibilities. One purpose is to mirror the classes in JUnit with 
> methods that can be statically imported into tests.
> com.gemstone.gemfire.test.dunit
> Assert
> AsyncInvocation
> DebuggerSupport
> DUnitEnv
> ExpectedExceptionString
> Host
> Invoke
> Jitter
> NetworkSupport
> RepeatableRunnable
> RMIException
> SerializableCallable
> SerializableRunnable
> StoppableWaitCriterion
> Threads
> VM
> Wait
> WaitCriterion
> Deprecate the classes in dunit package and modify dunit.DistributedTestCase 
> to invoke the methods in the new classes.



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


[jira] [Assigned] (GEODE-820) Define new DistributedTestRule to replace DistributedTestCase

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-820:
---

Assignee: Kirk Lund

> Define new DistributedTestRule to replace DistributedTestCase
> -
>
> Key: GEODE-820
> URL: https://issues.apache.org/jira/browse/GEODE-820
> Project: Geode
>  Issue Type: Sub-task
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Reorganize DistributedTestCase (JUnit 3.8.x) as DistributedTestRule (JUnit 
> 4.x). DistributedTestCase will then be deprecated. New dunit tests should 
> then be written using DistributedTestRule. 
> After this task is complete, there will then be an ongoing, low-priority 
> effort to migrate all older dunit tests to use DistributedTestRule instead of 
> extending DistributedTestCase.
> This sub-task describes one piece of work originally committed to 
> feature/GEODE-217.



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


[jira] [Assigned] (GEODE-819) Move dunit to com.gemstone.gemfire.test.dunit

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-819:
---

Assignee: Kirk Lund

> Move dunit to com.gemstone.gemfire.test.dunit
> -
>
> Key: GEODE-819
> URL: https://issues.apache.org/jira/browse/GEODE-819
> Project: Geode
>  Issue Type: Sub-task
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Move these classes from dunit to com.gemstone.gemfire.test.dunit:
> {noformat}
> AsyncInvocation.java
> DistributedTestCase.java
> DUnitEnv.java
> Host.java
> RepeateableRunnable.java
> RMIException.java
> SerializableCallable.java
> SerializableRunnable.java
> VM.java
> {noformat}
> This package will then be ready for future repackaging under org.apache.
> This sub-task describes one piece of work originally committed to 
> feature/GEODE-217.



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


[jira] [Assigned] (GEODE-821) Define new CacheTestRule to replace CacheTestCase

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund reassigned GEODE-821:
---

Assignee: Kirk Lund

> Define new CacheTestRule to replace CacheTestCase
> -
>
> Key: GEODE-821
> URL: https://issues.apache.org/jira/browse/GEODE-821
> Project: Geode
>  Issue Type: Sub-task
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Reorganize CacheTestCase (JUnit 3.8.x) as CacheTestRule (JUnit 4.x). 
> CacheTestCase will then be deprecated. New dunit tests should then be written 
> using CacheTestRule.
> After this task is complete, there will then be an ongoing, low-priority 
> effort to migrate all older dunit tests to use CacheTestRule instead of 
> extending CacheTestCase.
> This sub-task describes one piece of work originally committed to 
> feature/GEODE-217.



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


[jira] [Created] (GEODE-821) Define new CacheTestRule to replace CacheTestCase

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-821:
---

 Summary: Define new CacheTestRule to replace CacheTestCase
 Key: GEODE-821
 URL: https://issues.apache.org/jira/browse/GEODE-821
 Project: Geode
  Issue Type: Sub-task
  Components: tests
Reporter: Kirk Lund


Reorganize CacheTestCase (JUnit 3.8.x) as CacheTestRule (JUnit 4.x). 
CacheTestCase will then be deprecated. New dunit tests should then be written 
using CacheTestRule.

After this task is complete, there will then be an ongoing, low-priority effort 
to migrate all older dunit tests to use CacheTestRule instead of extending 
CacheTestCase.

This sub-task describes one piece of work originally committed to 
feature/GEODE-217.



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


[jira] [Updated] (GEODE-820) Define new DistributedTestRule to replace DistributedTestCase

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-820:

Summary: Define new DistributedTestRule to replace DistributedTestCase  
(was: Define new DistributedTestRule to replace for DistributedTestCase)

> Define new DistributedTestRule to replace DistributedTestCase
> -
>
> Key: GEODE-820
> URL: https://issues.apache.org/jira/browse/GEODE-820
> Project: Geode
>  Issue Type: Sub-task
>  Components: tests
>Reporter: Kirk Lund
>
> Reorganize DistributedTestCase (JUnit 3.8.x) as DistributedTestRule (JUnit 
> 4.x). DistributedTestCase will then be deprecated. New dunit tests should 
> then be written using DistributedTestRule. 
> After this task is complete, there will then be an ongoing, low-priority 
> effort to migrate all older dunit tests to use DistributedTestRule instead of 
> extending DistributedTestCase.
> This sub-task describes one piece of work originally committed to 
> feature/GEODE-217.



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


[jira] [Created] (GEODE-820) Define new DistributedTestRule to replace for DistributedTestCase

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-820:
---

 Summary: Define new DistributedTestRule to replace for 
DistributedTestCase
 Key: GEODE-820
 URL: https://issues.apache.org/jira/browse/GEODE-820
 Project: Geode
  Issue Type: Sub-task
  Components: tests
Reporter: Kirk Lund


Reorganize DistributedTestCase (JUnit 3.8.x) as DistributedTestRule (JUnit 
4.x). DistributedTestCase will then be deprecated. New dunit tests should then 
be written using DistributedTestRule. 

After this task is complete, there will then be an ongoing, low-priority effort 
to migrate all older dunit tests to use DistributedTestRule instead of 
extending DistributedTestCase.

This sub-task describes one piece of work originally committed to 
feature/GEODE-217.



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


[jira] [Commented] (GEODE-815) RC Feedback: Fix LICENSE and NOTICE files

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba commented on GEODE-815:
---

Sample NOTICE files needed for binary artifacts are attached to GEODE-610.

> RC Feedback: Fix LICENSE and NOTICE files
> -
>
> Key: GEODE-815
> URL: https://issues.apache.org/jira/browse/GEODE-815
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>




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


[jira] [Resolved] (GEODE-374) Upgrade Geode to use Log4j 2.4

2016-01-20 Thread Jinmei Liao (JIRA)

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

Jinmei Liao resolved GEODE-374.
---
Resolution: Fixed

> Upgrade Geode to use Log4j 2.4
> --
>
> Key: GEODE-374
> URL: https://issues.apache.org/jira/browse/GEODE-374
> Project: Geode
>  Issue Type: Improvement
>Reporter: Kirk Lund
>Assignee: Jinmei Liao
>  Labels: logging
>
> From annou...@apache.org:
> {noformat}
> The Apache Log4j 2 team is pleased to announce the Log4j 2.4 release!
> Apache log4j is a well known framework for logging application behavior. 
> Log4j 2 is an upgrade to
> Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
> and provides
> many other modern features such as support for Markers, property substitution 
> using Lookups, and asynchronous
> Loggers. In addition, Log4j 2 will not lose events while reconfiguring.
> This is the eighth GA release. It contains several bugfixes and new features. 
> As of this release
> Log4j now requires a minimum of Java 7.
> GA Release 2.4
> Changes in this version include:
> New features:
> o LOG4J2-635:  Add support for configuration via Properties. 
> o LOG4J2-952:  Add ConfigurationBuilder. 
> o LOG4J2-599:  Added support for Java 8 lambda expressions to lazily 
> construct a log message only if
>   the requested log level is enabled. 
> o LOG4J2-1118:  Updated Logger wrapper generator tool to add Java 8 lambda 
> support for custom log levels. 
> o LOG4J2-1107:  New Appender for Apache Kafka. Thanks to Mikael Ståldal. 
> o LOG4J2-1113:  New publisher Appender for ZeroMQ (using JeroMQ). Thanks to 
> Gary Gregory. 
> o LOG4J2-1088:  Add Comma Separated Value (CSV) layouts for parameter and 
> event logging. Thanks to Gary Gregory. 
> o LOG4J2-1090:  Add Core Configurator APIs to change a logger's level. 
> o LOG4J2-1105:  Add API org.apache.logging.log4j.Level.isInRange(Level, 
> Level). Thanks to Gary Gregory. 
> o LOG4J2-1106:  Add a LevelRangeFilter class. Thanks to Gary Gregory. 
> o LOG4J2-1076:  Added support for system nanosecond time in pattern layout. 
> o LOG4J2-1075:  Added support for compressing to bzip2 format on file 
> rollover. 
> o LOG4J2-1077:  Support additional Apache Commons Compress compression 
> formats on rollover: Deflate, Pack200, XY. 
> o LOG4J2-767:  New module for Liquibase integration. Thanks to Mikael 
> Ståldal. 
> o LOG4J2-1023:  New RewritePolicy for changing level of a log event. Thanks 
> to Mikael Ståldal. 
> o LOG4J2-1015:  Add a way to route messages based on the %marker in Layout 
> for RoutingAppender. Thanks to Daniel Marcotte. 
> o LOG4J2-1050:  Add a Log4jLookup class to help write log files relative to 
> log4j2.xml. Thanks to Adam Retter. 
> o LOG4J2-1057:  Add API 
> org.apache.logging.log4j.LogManager.getFormatterLogger(). 
> o LOG4J2-1066:  Expose Log4jContextFactory's ShutdownCallbackRegistry. Thanks 
> to Charles Allen. 
> Fixed Bugs:
> o LOG4J2-1121:  Fixed potential race condition on reconfiguration. Introduced 
> ReliabilityStrategy to facilitate
> switching between different mechanisms for preventing log events from 
> being dropped on reconfiguration. 
> o LOG4J2-1123:  Core Configurator.initialize(String, ClassLoader, String) 
> fails to work when config location is a file path. Thanks to Gary Gregory. 
> o LOG4J2-1117:  OutputStreamManager in ConsoleAppender leaking managers. 
> Thanks to Marcus Thiesen. 
> o LOG4J2-1044:  Write pending events to Flume when the appender is stopped. 
> o LOG4J2-1108:  NullPointerException when passing null to 
> java.util.logging.Logger.setLevel(). Thanks to Mikael Ståldal. 
> o LOG4J2-1110:  org.apache.logging.log4j.jul.CoreLogger.setLevel() checks for 
> security permission too late. 
> o LOG4J2-1084:  Misleading StatusLogger WARN event in LogManager with 
> java.util.Map. Thanks to Philipp Schneider. 
> o LOG4J2-1051:  NoClassDefFoundError when starting app on Google App Engine. 
> Thanks to Lukasz Lenart. 
> o LOG4J2-684:  ExtendedThrowablePatternConverter does not print suppressed 
> exceptions. Thanks to Joern Huxhorn, Mauro Molinari. 
> o LOG4J2-1069:  Improper handling of JSON escape chars when deserializing 
> JSON log events. Thanks to Sam Braam. 
> o LOG4J2-1068:  Exceptions not logged when using TcpSocketServer + 
> SerializedLayout. Thanks to Andy McMullan. 
> o LOG4J2-1067:  ThrowableProxy getExtendedStackTraceAsString throws NPE on 
> deserialized nested exceptions. Thanks to Sam Braam. 
> o LOG4J2-1049:  AsyncAppender now resets the thread interrupted flag after 
> catching InterruptedException. Thanks to Robert Schaft. 
> o LOG4J2-1048:  FileConfigurationMonitor unnecessarily calls 
> System.currentTimeMillis() causing high CPU usage. Thanks to Nikhil. 
> o LOG4J2-1037:  Backward compatibility issue in log4j-1.2-api NDC p

[jira] [Created] (GEODE-819) Move dunit to com.gemstone.gemfire.test.dunit

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-819:
---

 Summary: Move dunit to com.gemstone.gemfire.test.dunit
 Key: GEODE-819
 URL: https://issues.apache.org/jira/browse/GEODE-819
 Project: Geode
  Issue Type: Sub-task
  Components: tests
Reporter: Kirk Lund


Move these classes from dunit to com.gemstone.gemfire.test.dunit:
{noformat}
AsyncInvocation.java
DistributedTestCase.java
DUnitEnv.java
Host.java
RepeateableRunnable.java
RMIException.java
SerializableCallable.java
SerializableRunnable.java
VM.java
{noformat}
This package will then be ready for future repackaging under org.apache.

This sub-task describes one piece of work originally committed to 
feature/GEODE-217.




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


[jira] [Updated] (GEODE-815) RC Feedback: Fix LICENSE and NOTICE files

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba updated GEODE-815:
--
Affects Version/s: 1.0.0-incubating.M1

> RC Feedback: Fix LICENSE and NOTICE files
> -
>
> Key: GEODE-815
> URL: https://issues.apache.org/jira/browse/GEODE-815
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>




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


[jira] [Updated] (GEODE-818) RC Feedback: Fix Maven & pom dependencies

2016-01-20 Thread Nitin Lamba (JIRA)

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

Nitin Lamba updated GEODE-818:
--
Affects Version/s: 1.0.0-incubating.M1

> RC Feedback: Fix Maven & pom dependencies
> -
>
> Key: GEODE-818
> URL: https://issues.apache.org/jira/browse/GEODE-818
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>




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


[jira] [Created] (GEODE-818) RC Feedback: Fix Maven & pom dependencies

2016-01-20 Thread Nitin Lamba (JIRA)
Nitin Lamba created GEODE-818:
-

 Summary: RC Feedback: Fix Maven & pom dependencies
 Key: GEODE-818
 URL: https://issues.apache.org/jira/browse/GEODE-818
 Project: Geode
  Issue Type: Task
Reporter: Nitin Lamba






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


[jira] [Created] (GEODE-817) Binary distribution NOTICE needs update

2016-01-20 Thread Nitin Lamba (JIRA)
Nitin Lamba created GEODE-817:
-

 Summary: Binary distribution NOTICE needs update
 Key: GEODE-817
 URL: https://issues.apache.org/jira/browse/GEODE-817
 Project: Geode
  Issue Type: Sub-task
Reporter: Nitin Lamba


- Copyright should be updated to '2015-16'.
- include any NOTICES from Apache Licensed dependencies; examples - Spring, 
Netty & Snappy



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


[jira] [Created] (GEODE-816) Source Distribution NOTICE needs updates

2016-01-20 Thread Nitin Lamba (JIRA)
Nitin Lamba created GEODE-816:
-

 Summary: Source Distribution NOTICE needs updates
 Key: GEODE-816
 URL: https://issues.apache.org/jira/browse/GEODE-816
 Project: Geode
  Issue Type: Sub-task
Reporter: Nitin Lamba


Copyright year should be updated to '2015-16'.



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


[jira] [Resolved] (GEODE-649) CI failure: ServerLauncherRemoteJUnitTest.testStartUsingDisableDefaultServerLeavesPortFree

2016-01-20 Thread Jinmei Liao (JIRA)

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

Jinmei Liao resolved GEODE-649.
---
Resolution: Cannot Reproduce

Will close this for now. Waiting for it to fail again with more messages.

> CI failure: 
> ServerLauncherRemoteJUnitTest.testStartUsingDisableDefaultServerLeavesPortFree
> --
>
> Key: GEODE-649
> URL: https://issues.apache.org/jira/browse/GEODE-649
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Darrel Schneider
>Assignee: Jinmei Liao
>  Labels: CI
>
> git rev 1f193af7016e125059022e76d7cd053339bc309a  build #926
> java.lang.AssertionError: waiting for local Server to start: Server in 
> /tmp/junit6083509114268149978 on null is currently not responding.
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at 
> com.gemstone.gemfire.distributed.AbstractLauncherJUnitTestCase.assertEventuallyTrue(AbstractLauncherJUnitTestCase.java:238)
>   at 
> com.gemstone.gemfire.distributed.ServerLauncherRemoteJUnitTest.waitForServerToStart(ServerLauncherRemoteJUnitTest.java:1336)
>   at 
> com.gemstone.gemfire.distributed.ServerLauncherRemoteJUnitTest.testStartUsingDisableDefaultServerLeavesPortFree(ServerLauncherRemoteJUnitTest.java:433)



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


[jira] [Assigned] (GEODE-735) OffHeapHelper needs unit test

2016-01-20 Thread Kenneth Howe (JIRA)

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

Kenneth Howe reassigned GEODE-735:
--

Assignee: Kenneth Howe

> OffHeapHelper needs unit test
> -
>
> Key: GEODE-735
> URL: https://issues.apache.org/jira/browse/GEODE-735
> Project: Geode
>  Issue Type: Sub-task
>  Components: offheap
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>
> OffHeapHelper currently has 30% test coverage and there are no unit tests



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


[jira] [Created] (GEODE-815) RC Feedback: Fix LICENSE and NOTICE files

2016-01-20 Thread Nitin Lamba (JIRA)
Nitin Lamba created GEODE-815:
-

 Summary: RC Feedback: Fix LICENSE and NOTICE files
 Key: GEODE-815
 URL: https://issues.apache.org/jira/browse/GEODE-815
 Project: Geode
  Issue Type: Task
Reporter: Nitin Lamba






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


[jira] [Assigned] (GEODE-814) DisconnectingOutOfOffHeapMemoryListener needs unit test

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider reassigned GEODE-814:
--

Assignee: Darrel Schneider

> DisconnectingOutOfOffHeapMemoryListener needs unit test
> ---
>
> Key: GEODE-814
> URL: https://issues.apache.org/jira/browse/GEODE-814
> Project: Geode
>  Issue Type: Sub-task
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>
> Also this class should be moved to its own class file.



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


[jira] [Created] (GEODE-814) DisconnectingOutOfOffHeapMemoryListener needs unit test

2016-01-20 Thread Darrel Schneider (JIRA)
Darrel Schneider created GEODE-814:
--

 Summary: DisconnectingOutOfOffHeapMemoryListener needs unit test
 Key: GEODE-814
 URL: https://issues.apache.org/jira/browse/GEODE-814
 Project: Geode
  Issue Type: Sub-task
  Components: offheap
Reporter: Darrel Schneider


Also this class should be moved to its own class file.




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


[jira] [Resolved] (GEODE-798) OffHeapStorageJUnitTest.testCreateOffHeapStorage should not create a real cache

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider resolved GEODE-798.

Resolution: Fixed

> OffHeapStorageJUnitTest.testCreateOffHeapStorage should not create a real 
> cache
> ---
>
> Key: GEODE-798
> URL: https://issues.apache.org/jira/browse/GEODE-798
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>
> The OffHeapStorageJUnitTest testCreateOffHeapStorage method creates a real 
> cache that is then used to obtain a StatisticsFactory and DistributedSystem 
> to pass to createOffHeapStorage. 
> It should instead create a mocked StatisticsFactory and DistributedSystem.



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


[jira] [Commented] (GEODE-798) OffHeapStorageJUnitTest.testCreateOffHeapStorage should not create a real cache

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-798: change unit test to not create a real cache

testCreateOffHeapStorage now uses mocks.
Also a LocalStatisticsFactory can now be created without starting a sampler.
This allows it to be used as a light weight StatisticsFactory compared to 
InternalDistributedSystem.
The nice thing compared to a mocked StatisticsFactory is it will still create 
functional Statistics instances.


> OffHeapStorageJUnitTest.testCreateOffHeapStorage should not create a real 
> cache
> ---
>
> Key: GEODE-798
> URL: https://issues.apache.org/jira/browse/GEODE-798
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>
> The OffHeapStorageJUnitTest testCreateOffHeapStorage method creates a real 
> cache that is then used to obtain a StatisticsFactory and DistributedSystem 
> to pass to createOffHeapStorage. 
> It should instead create a mocked StatisticsFactory and DistributedSystem.



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


[jira] [Resolved] (GEODE-793) CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterCreate

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider resolved GEODE-793.

Resolution: Fixed

> CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterCreate
> 
>
> Key: GEODE-793
> URL: https://issues.apache.org/jira/browse/GEODE-793
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.closeAndFree(LifecycleListenerJUnitTest.java:147)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.testCallbacksAreCalledAfterCreate(LifecycleListenerJUnitTest.java:89)
> line 147: assertEquals(false, 
> Boolean.getBoolean(SimpleMemoryAllocatorImpl.FREE_OFF_HEAP_MEMORY_PROPERTY));



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


[jira] [Resolved] (GEODE-792) CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuseWithFreeTrue

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider resolved GEODE-792.

Resolution: Fixed

> CI failure: 
> LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuseWithFreeTrue
> ---
>
> Key: GEODE-792
> URL: https://issues.apache.org/jira/browse/GEODE-792
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.closeAndFree(LifecycleListenerJUnitTest.java:147)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuseWithFreeTrue(LifecycleListenerJUnitTest.java:168)
> line 147: assertEquals(false, 
> Boolean.getBoolean(SimpleMemoryAllocatorImpl.FREE_OFF_HEAP_MEMORY_PROPERTY));



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


[jira] [Resolved] (GEODE-791) CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuse

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider resolved GEODE-791.

Resolution: Fixed

> CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuse
> ---
>
> Key: GEODE-791
> URL: https://issues.apache.org/jira/browse/GEODE-791
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuse(LifecycleListenerJUnitTest.java:103)
> line 103: assertEquals(false, 
> Boolean.getBoolean(SimpleMemoryAllocatorImpl.FREE_OFF_HEAP_MEMORY_PROPERTY));



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


[jira] [Resolved] (GEODE-712) CI failure: SimpleMemoryAllocatorJUnitTest.testCreate

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider resolved GEODE-712.


> CI failure: SimpleMemoryAllocatorJUnitTest.testCreate
> -
>
> Key: GEODE-712
> URL: https://issues.apache.org/jira/browse/GEODE-712
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Bruce Schuchardt
>Assignee: Darrel Schneider
>  Labels: CI
> Fix For: 1.0.0-incubating.M1
>
>
> failed 1 time in the last 16 runs
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.internal.offheap.SimpleMemoryAllocatorJUnitTest.testCreate(SimpleMemoryAllocatorJUnitTest.java:223)
>   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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   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:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)



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


[jira] [Resolved] (GEODE-701) CI failure: SimpleMemoryAllocatorJUnitTest.testClose

2016-01-20 Thread Darrel Schneider (JIRA)

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

Darrel Schneider resolved GEODE-701.

Resolution: Fixed

> CI failure: SimpleMemoryAllocatorJUnitTest.testClose
> 
>
> Key: GEODE-701
> URL: https://issues.apache.org/jira/browse/GEODE-701
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Sai Boorlagadda
>Assignee: Darrel Schneider
>  Labels: CI
>
> This JUnit test fails intermittently and crashes with a "double free" error 
> while releasing the unsafe memory twice.
> Investigate on why the tests fails intermittently and fix it.



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


[jira] [Updated] (GEODE-813) Fix javadoc warnings in cache packages

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-813:

Description: 
cache pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\Cache.java:254:
 warning - Tag @see: reference not found: com.gemstone.gemfire.cache.server
{noformat}
cache.control pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\control\RebalanceOperation.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.cache GemFire 
Cache
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\control\ResourceManager.java:44:
 warning - Tag @link: reference not found: com.gemstone.gemfire.cache GemFire 
Cache
{noformat}
cache.hdfs pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\hdfs\HDFSStoreFactory.java:36:
 warning - Tag @link: can't find createHDFSStoreFactory in 
com.gemstone.gemfire.cache.Cache
{noformat}
internal.cache pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:512:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:533:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:554:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\CacheObserver.java:190:
 warning - @param argument "emptyOplog" is not a parameter name.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXRollbackMessage.java:262:
 warning - Tag @link: reference not found: 
DistTXRollbackMessage.DistTXCommitReplyMessage
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXState.java:352:
 warning - @return tag has no arguments.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXState.java:441:
 warning - End Delimiter } missing for possible See Tag in comment string: 
"Apply the individual tx op on secondary
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXState.java:352:
 warning - @param argument "txStateProxy" is not a parameter name.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\EventTracker.java:67:
 warning - Tag @link: reference not found: EventSeqnoHolder
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\IdentityArrayList.java:66:
 warning - Tag @link: reference not found: java.util
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\InitialImageOperation.java:2242:
 warning - Tag @link: reference not found: ImageProcessor
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\InitialImageOperation.java:1571:
 warning - Tag @link: reference not found: ImageProcessor
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\InitialImageOperation.java:2504:
 warning - Tag @link: reference not found: ImageProcessor
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\PartitionedRegion.java:412:
 warning - @guarded.By is an unknown tag.
{noformat}

  was:
cache pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\Cache.java:254:
 warning - Tag @see: reference not found: com.gemstone.gemfire.cache.server
{noformat}
cache.control pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\control\RebalanceOperation.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.cache GemFire 
Cache
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\control\ResourceManager.java:44:
 warning - Tag @link: reference not found: com.gemstone.gemfire.cache GemFire 
Cache
{noformat}
hdfs packages:
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\hdfs\HDFSStoreFactory.java:36:
 warning - Tag @link: can't find createHDFSStoreFactory in 
com.gemstone.gemfire.cache.Cache
{noformat}
internal.cache pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:512:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:533:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:554:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\CacheObserver.java:190:
 warning - @param argument "emptyOplog" is not a parameter name.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXRollbackMessage.java:262:
 warning - Tag @link: reference not found: 
DistTXRollbackMessage.DistTXCommitReplyMessa

[jira] [Created] (GEODE-813) Fix javadoc warnings in cache packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-813:
---

 Summary: Fix javadoc warnings in cache packages
 Key: GEODE-813
 URL: https://issues.apache.org/jira/browse/GEODE-813
 Project: Geode
  Issue Type: Sub-task
  Components: core
Reporter: Kirk Lund


cache pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\Cache.java:254:
 warning - Tag @see: reference not found: com.gemstone.gemfire.cache.server
{noformat}
cache.control pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\control\RebalanceOperation.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.cache GemFire 
Cache
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\control\ResourceManager.java:44:
 warning - Tag @link: reference not found: com.gemstone.gemfire.cache GemFire 
Cache
{noformat}
hdfs packages:
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\hdfs\HDFSStoreFactory.java:36:
 warning - Tag @link: can't find createHDFSStoreFactory in 
com.gemstone.gemfire.cache.Cache
{noformat}
internal.cache pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:512:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:533:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\BucketAdvisor.java:554:
 warning - @guarded.By is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\CacheObserver.java:190:
 warning - @param argument "emptyOplog" is not a parameter name.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXRollbackMessage.java:262:
 warning - Tag @link: reference not found: 
DistTXRollbackMessage.DistTXCommitReplyMessage
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXState.java:352:
 warning - @return tag has no arguments.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXState.java:441:
 warning - End Delimiter } missing for possible See Tag in comment string: 
"Apply the individual tx op on secondary
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\DistTXState.java:352:
 warning - @param argument "txStateProxy" is not a parameter name.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\EventTracker.java:67:
 warning - Tag @link: reference not found: EventSeqnoHolder
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\IdentityArrayList.java:66:
 warning - Tag @link: reference not found: java.util
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\InitialImageOperation.java:2242:
 warning - Tag @link: reference not found: ImageProcessor
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\InitialImageOperation.java:1571:
 warning - Tag @link: reference not found: ImageProcessor
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\InitialImageOperation.java:2504:
 warning - Tag @link: reference not found: ImageProcessor
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\cache\PartitionedRegion.java:412:
 warning - @guarded.By is an unknown tag.
{noformat}



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


[jira] [Assigned] (GEODE-749) Improve detection of *.war files

2016-01-20 Thread Jinmei Liao (JIRA)

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

Jinmei Liao reassigned GEODE-749:
-

Assignee: Jinmei Liao

> Improve detection of *.war files
> 
>
> Key: GEODE-749
> URL: https://issues.apache.org/jira/browse/GEODE-749
> Project: Geode
>  Issue Type: Improvement
>  Components: management
>Reporter: Jens Deppe
>Assignee: Jinmei Liao
>
> Currently we require a GEMFIRE environment variable to be set in order to 
> detect the location of the pulse.war (and newly) the gemfire.war file.
> I believe this requirement could be avoided by looking for the relevant war 
> file as a resource on the classpath.
> If a user is building a self-contained (possibly executable) application jar, 
> containing all the relevant gemfire jars, they would still need to provide an 
> external pulse.war file as well as set the env variable during execution. 



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


[jira] [Created] (GEODE-812) Fix javadoc warnings in transaction packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-812:
---

 Summary: Fix javadoc warnings in transaction packages
 Key: GEODE-812
 URL: https://issues.apache.org/jira/browse/GEODE-812
 Project: Geode
  Issue Type: Sub-task
  Components: core
Reporter: Kirk Lund


internal.jta package:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\jta\GlobalTransaction.java:148:
 warning - @.concurrency is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\jta\GlobalTransaction.java:254:
 warning - @.concurrency is an unknown tag.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\jta\GlobalTransaction.java:350:
 warning - @.concurrency is an unknown tag.
{noformat}




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


[jira] [Created] (GEODE-810) Fix javadoc warnings in redis packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-810:
---

 Summary: Fix javadoc warnings in redis packages
 Key: GEODE-810
 URL: https://issues.apache.org/jira/browse/GEODE-810
 Project: Geode
  Issue Type: Sub-task
  Components: extensions
Reporter: Kirk Lund


redis packages:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\redis\executor\AbstractExecutor.java:101:
 warning - Tag @link: reference not found: QueryType
{noformat}



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


[jira] [Created] (GEODE-811) Fix javadoc warnings in querying packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-811:
---

 Summary: Fix javadoc warnings in querying packages
 Key: GEODE-811
 URL: https://issues.apache.org/jira/browse/GEODE-811
 Project: Geode
  Issue Type: Sub-task
  Components: querying
Reporter: Kirk Lund


query.internal.index package:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\cache\query\internal\index\PartitionedIndex.java:433:
 warning - Tag @link: reference not found: PartitionedIndexStatistics
{noformat}



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


[jira] [Created] (GEODE-809) Fix javadoc warnings in distributed and membership packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-809:
---

 Summary: Fix javadoc warnings in distributed and membership 
packages
 Key: GEODE-809
 URL: https://issues.apache.org/jira/browse/GEODE-809
 Project: Geode
  Issue Type: Sub-task
  Components: membership
Reporter: Kirk Lund


membership packages:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\membership\InternalDistributedMember.java:451:
 warning - Tag @see: can't find getDistributionManagerType in 
com.gemstone.gemfire.distributed.internal.DistributionManager
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\membership\MemberServices.java:79:
 warning - @param argument "stopper" is not a parameter name.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\membership\gms\interfaces\HealthMonitor.java:51:
 warning - @return tag has no arguments.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\membership\gms\locator\FindCoordinatorResponse.java:90:
 warning - @return tag has no arguments.
{noformat}
distributed packages:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\deadlock\DeadlockDetector.java:113:
 warning - @arg is an unknown tag.
{noformat}



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


[jira] [Created] (GEODE-808) Fix javadoc warnings in AutoBalancer

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-808:
---

 Summary: Fix javadoc warnings in AutoBalancer
 Key: GEODE-808
 URL: https://issues.apache.org/jira/browse/GEODE-808
 Project: Geode
  Issue Type: Sub-task
  Components: core
Reporter: Kirk Lund


cache.util pkg:
{noformat}
C:\dev\geode\gemfire-rebalancer\src\main\java\com\gemstone\gemfire\cache\util\AutoBalancer.java:103:
 warning - AutoBalancer#DEFAULT_SIZE_THRESHOLD_PERCENT (referenced by @value 
tag) is an unknown reference.
C:\dev\geode\gemfire-rebalancer\src\main\java\com\gemstone\gemfire\cache\util\AutoBalancer.java:121:
 warning - AutoBalancer#DEFAULT_MINIMUM_SIZE (referenced by @value tag) is an 
unknown reference.
{noformat}




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


[jira] [Created] (GEODE-807) Fix javadoc warnings in lucene packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-807:
---

 Summary: Fix javadoc warnings in lucene packages
 Key: GEODE-807
 URL: https://issues.apache.org/jira/browse/GEODE-807
 Project: Geode
  Issue Type: Sub-task
  Components: extensions
Reporter: Kirk Lund


cache.lucene pkg:
{noformat}
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryFactory.java:85:
 warning - @param argument "K" is not a parameter name.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryFactory.java:85:
 warning - @param argument "V" is not a parameter name.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryFactory.java:100:
 warning - Tag @link: reference not found: QueryDeserializer
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryFactory.java:100:
 warning - @param argument "K" is not a parameter name.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryFactory.java:100:
 warning - @param argument "V" is not a parameter name.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryProvider.java:44:
 warning - @param argument "The" is not a parameter name.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneService.java:72:
 warning - Tag @link: can't find getLuceneService() in 
com.gemstone.gemfire.cache.GemFireCache
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneService.java:82:
 warning - @return tag cannot be used in method with void return type.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneService.java:94:
 warning - @return tag cannot be used in method with void return type.
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\LuceneQueryFactory.java:100:
 warning - Tag @link: reference not found: QueryDeserializer
{noformat}
cache.lucene.internal.repository pkg:
{noformat}
C:\dev\geode\gemfire-lucene\src\main\java\com\gemstone\gemfire\cache\lucene\internal\repository\RepositoryManager.java:44:
 warning - @param argument "localDataSet" is not a parameter name.
{noformat}




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


[jira] [Commented] (GEODE-793) CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterCreate

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-701: fix tests using FREE_OFF_HEAP_MEMORY_PROPERTY

Fixes: GEODE-701, GEODE-712, GEODE-791, GEODE-792, GEODE-793.
Tests that change the FREE_OFF_HEAP_MEMORY_PROPERTY system property
now use the RestoreSystemProperties rule to ensure that the properties
are restored to their original values.


> CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterCreate
> 
>
> Key: GEODE-793
> URL: https://issues.apache.org/jira/browse/GEODE-793
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.closeAndFree(LifecycleListenerJUnitTest.java:147)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.testCallbacksAreCalledAfterCreate(LifecycleListenerJUnitTest.java:89)
> line 147: assertEquals(false, 
> Boolean.getBoolean(SimpleMemoryAllocatorImpl.FREE_OFF_HEAP_MEMORY_PROPERTY));



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


[jira] [Commented] (GEODE-791) CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuse

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-701: fix tests using FREE_OFF_HEAP_MEMORY_PROPERTY

Fixes: GEODE-701, GEODE-712, GEODE-791, GEODE-792, GEODE-793.
Tests that change the FREE_OFF_HEAP_MEMORY_PROPERTY system property
now use the RestoreSystemProperties rule to ensure that the properties
are restored to their original values.


> CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuse
> ---
>
> Key: GEODE-791
> URL: https://issues.apache.org/jira/browse/GEODE-791
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuse(LifecycleListenerJUnitTest.java:103)
> line 103: assertEquals(false, 
> Boolean.getBoolean(SimpleMemoryAllocatorImpl.FREE_OFF_HEAP_MEMORY_PROPERTY));



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


[jira] [Commented] (GEODE-712) CI failure: SimpleMemoryAllocatorJUnitTest.testCreate

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-701: fix tests using FREE_OFF_HEAP_MEMORY_PROPERTY

Fixes: GEODE-701, GEODE-712, GEODE-791, GEODE-792, GEODE-793.
Tests that change the FREE_OFF_HEAP_MEMORY_PROPERTY system property
now use the RestoreSystemProperties rule to ensure that the properties
are restored to their original values.


> CI failure: SimpleMemoryAllocatorJUnitTest.testCreate
> -
>
> Key: GEODE-712
> URL: https://issues.apache.org/jira/browse/GEODE-712
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Bruce Schuchardt
>Assignee: Darrel Schneider
>  Labels: CI
> Fix For: 1.0.0-incubating.M1
>
>
> failed 1 time in the last 16 runs
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.internal.offheap.SimpleMemoryAllocatorJUnitTest.testCreate(SimpleMemoryAllocatorJUnitTest.java:223)
>   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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   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:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concu

[jira] [Commented] (GEODE-792) CI failure: LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuseWithFreeTrue

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-701: fix tests using FREE_OFF_HEAP_MEMORY_PROPERTY

Fixes: GEODE-701, GEODE-712, GEODE-791, GEODE-792, GEODE-793.
Tests that change the FREE_OFF_HEAP_MEMORY_PROPERTY system property
now use the RestoreSystemProperties rule to ensure that the properties
are restored to their original values.


> CI failure: 
> LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuseWithFreeTrue
> ---
>
> Key: GEODE-792
> URL: https://issues.apache.org/jira/browse/GEODE-792
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>  Labels: CI
>
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.closeAndFree(LifecycleListenerJUnitTest.java:147)
>   at 
> com.gemstone.gemfire.internal.offheap.LifecycleListenerJUnitTest.testCallbacksAreCalledAfterReuseWithFreeTrue(LifecycleListenerJUnitTest.java:168)
> line 147: assertEquals(false, 
> Boolean.getBoolean(SimpleMemoryAllocatorImpl.FREE_OFF_HEAP_MEMORY_PROPERTY));



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


[jira] [Commented] (GEODE-701) CI failure: SimpleMemoryAllocatorJUnitTest.testClose

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-701: fix tests using FREE_OFF_HEAP_MEMORY_PROPERTY

Fixes: GEODE-701, GEODE-712, GEODE-791, GEODE-792, GEODE-793.
Tests that change the FREE_OFF_HEAP_MEMORY_PROPERTY system property
now use the RestoreSystemProperties rule to ensure that the properties
are restored to their original values.


> CI failure: SimpleMemoryAllocatorJUnitTest.testClose
> 
>
> Key: GEODE-701
> URL: https://issues.apache.org/jira/browse/GEODE-701
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Sai Boorlagadda
>Assignee: Darrel Schneider
>  Labels: CI
>
> This JUnit test fails intermittently and crashes with a "double free" error 
> while releasing the unsafe memory twice.
> Investigate on why the tests fails intermittently and fix it.



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


[jira] [Updated] (GEODE-806) Fix javadoc warnings in management packages

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-806:

Description: 
admin pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminConfig.java:46:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystem.java:43:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystemFactory.java:39:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminException.java:31:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminXmlException.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\Alert.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertLevel.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertListener.java:24:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\BackupStatus.java:33:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheDoesNotExistException.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheHealthConfig.java:70:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVm.java:33:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVmConfig.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ConfigurationParameter.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemConfig.java:62:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemHealthConfig.java:54:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocator.java:32:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocatorConfig.java:45:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealth.java:48:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealthConfig.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireMemberStatus.java:58:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntity.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntityConfig.java:32:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\MemberHealthConfig.java:53:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\OperationCancelledException.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\RegionNotFoundException.java:32:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\RegionSubRegionSnapshot.java:42:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\RuntimeAdminException.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\ge

[jira] [Commented] (GEODE-701) CI failure: SimpleMemoryAllocatorJUnitTest.testClose

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-701: fix tests using FREE_OFF_HEAP_MEMORY_PROPERTY

Fixes: GEODE-701, GEODE-712, GEODE-791, GEODE-792, GEODE-793.
Tests that change the FREE_OFF_HEAP_MEMORY_PROPERTY system property
now use the RestoreSystemProperties rule to ensure that the properties
are restored to their original values.


> CI failure: SimpleMemoryAllocatorJUnitTest.testClose
> 
>
> Key: GEODE-701
> URL: https://issues.apache.org/jira/browse/GEODE-701
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Sai Boorlagadda
>Assignee: Darrel Schneider
>  Labels: CI
>
> This JUnit test fails intermittently and crashes with a "double free" error 
> while releasing the unsafe memory twice.
> Investigate on why the tests fails intermittently and fix it.



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


[jira] [Updated] (GEODE-806) Fix javadoc warnings in management packages

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-806:

Description: 
admin pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\Agent.java:73:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentConfig.java:279:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentFactory.java:31:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
{noformat}
internal.logging pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:129:
 warning - Tag @see: reference not found: Sorter#mergeLogFiles
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:159:
 warning - Tag @see: reference not found: Sorter#mergeLogFiles
{noformat}
internal.admin pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\admin\StatAlertsManager.java:80:
 warning - @guarded.By is an unknown tag.
{noformat}

  was:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\membership\gms\interfaces\HealthMonitor.java:51:
 warning - @return tag has no arguments.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\Agent.java:73:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentConfig.java:279:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentFactory.java:31:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management

C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:129:
 warning - Tag @see: reference not found: Sorter#mergeLogFiles
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:159:
 warning - Tag @see: reference not found: Sorter#mergeLogFiles

C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\admin\StatAlertsManager.java:80:
 warning - @guarded.By is an unknown tag.
{noformat}


> Fix javadoc warnings in management packages
> ---
>
> Key: GEODE-806
> URL: https://issues.apache.org/jira/browse/GEODE-806
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Kirk Lund
>
> admin pkg:
> {noformat}
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\Agent.java:73:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentConfig.java:279:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentFactory.java:31:
>  warning - Tag @link: reference not found: com.gemstone.gemfire.management
> {noformat}
> internal.logging pkg:
> {noformat}
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:129:
>  warning - Tag @see: reference not found: Sorter#mergeLogFiles
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:159:
>  warning - Tag @see: reference not found: Sorter#mergeLogFiles
> {noformat}
> internal.admin pkg:
> {noformat}
> C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\admin\StatAlertsManager.java:80:
>  warning - @guarded.By is an unknown tag.
> {noformat}



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


[jira] [Updated] (GEODE-806) Fix javadoc warnings in management packages

2016-01-20 Thread Kirk Lund (JIRA)

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

Kirk Lund updated GEODE-806:

Description: 
admin pkg:
{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminConfig.java:46:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystem.java:43:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminDistributedSystemFactory.java:39:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminException.java:31:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AdminXmlException.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\Alert.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertLevel.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\AlertListener.java:24:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\BackupStatus.java:33:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheDoesNotExistException.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheHealthConfig.java:70:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVm.java:33:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\CacheVmConfig.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ConfigurationParameter.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemConfig.java:62:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributedSystemHealthConfig.java:54:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocator.java:32:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\DistributionLocatorConfig.java:45:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealth.java:48:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireHealthConfig.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\GemFireMemberStatus.java:58:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntity.java:28:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\ManagedEntityConfig.java:32:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\MemberHealthConfig.java:53:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\OperationCancelledException.java:30:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\RegionNotFoundException.java:32:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\RegionSubRegionSnapshot.java:42:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\RuntimeAdminException.java:29:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\ge

[jira] [Created] (GEODE-806) Fix javadoc warnings in management packages

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-806:
---

 Summary: Fix javadoc warnings in management packages
 Key: GEODE-806
 URL: https://issues.apache.org/jira/browse/GEODE-806
 Project: Geode
  Issue Type: Sub-task
  Components: management
Reporter: Kirk Lund


{noformat}
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\distributed\internal\membership\gms\interfaces\HealthMonitor.java:51:
 warning - @return tag has no arguments.
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\Agent.java:73:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentConfig.java:279:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\admin\jmx\AgentFactory.java:31:
 warning - Tag @link: reference not found: com.gemstone.gemfire.management

C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:129:
 warning - Tag @see: reference not found: Sorter#mergeLogFiles
C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\logging\MergeLogFiles.java:159:
 warning - Tag @see: reference not found: Sorter#mergeLogFiles

C:\dev\geode\gemfire-core\src\main\java\com\gemstone\gemfire\internal\admin\StatAlertsManager.java:80:
 warning - @guarded.By is an unknown tag.
{noformat}



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


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

2016-01-20 Thread Kirk Lund (JIRA)
Kirk Lund created GEODE-805:
---

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






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


[jira] [Created] (GEODE-804) Apply additional changes from pivotal to WAN and CQ

2016-01-20 Thread Dan Smith (JIRA)
Dan Smith created GEODE-804:
---

 Summary: Apply additional changes from pivotal to WAN and CQ
 Key: GEODE-804
 URL: https://issues.apache.org/jira/browse/GEODE-804
 Project: Geode
  Issue Type: Sub-task
Reporter: Dan Smith


There are a few changes that have been made to the WAN and CQ modules since the 
initial grant. These changes should be applied to the wan_cq_donation branch.



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


[jira] [Resolved] (GEODE-785) Refactor repetitive comparison/loop code in CompiledIn.evaluate

2016-01-20 Thread Jason Huynh (JIRA)

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

Jason Huynh resolved GEODE-785.
---
Resolution: Fixed

> Refactor repetitive comparison/loop code in CompiledIn.evaluate
> ---
>
> Key: GEODE-785
> URL: https://issues.apache.org/jira/browse/GEODE-785
> Project: Geode
>  Issue Type: Improvement
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> In CompiledIn.evaluate we can see repetitive loops, each one differing only 
> in the cast to a specific array type.  For example:
>  // handle each type of primitive array
> if (evalColln instanceof long[]) {
>   long[] a = (long[])evalColln;
>   for (int i = 0; i < a.length; i++) {
> Object e = Long.valueOf(a[i]);
> if (TypeUtils.compare(evalElm, e, TOK_EQ).equals(Boolean.TRUE)) {
>   return Boolean.TRUE;
> }
>   }
>   return Boolean.FALSE;
> }
> 
> if (evalColln instanceof double[]) {
>   double[] a = (double[])evalColln;
>   for (int i = 0; i < a.length; i++) {
> Object e = Double.valueOf(a[i]);
> if (TypeUtils.compare(evalElm, e, TOK_EQ).equals(Boolean.TRUE)) {
>   return Boolean.TRUE;
> }
>   }
>   return Boolean.FALSE;
> }
> We should be able to write a test to exercise this code and then write a 
> single loop that handles all object thypes as the comparison is actually done 
> by the TypeUtils.compare() method.



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


[jira] [Created] (GEODE-803) Add apache headers to gemfire-wan and gemfire-cq modules

2016-01-20 Thread Dan Smith (JIRA)
Dan Smith created GEODE-803:
---

 Summary: Add apache headers to gemfire-wan and gemfire-cq modules
 Key: GEODE-803
 URL: https://issues.apache.org/jira/browse/GEODE-803
 Project: Geode
  Issue Type: Sub-task
Reporter: Dan Smith


This code currently has pivotal headers. The headers should be replaced with 
apache headers and RAT should run cleanly.



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


[jira] [Created] (GEODE-802) Integrate WAN and CQ gradle modules with with the gradle build

2016-01-20 Thread Dan Smith (JIRA)
Dan Smith created GEODE-802:
---

 Summary: Integrate WAN and CQ gradle modules with with the gradle 
build
 Key: GEODE-802
 URL: https://issues.apache.org/jira/browse/GEODE-802
 Project: Geode
  Issue Type: Sub-task
Reporter: Dan Smith


These modules need to be integrated with the top level build. This may just a 
matter of adding them to settings.gradle.



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


[jira] [Created] (GEODE-801) Integrate WAN and CQ Donations

2016-01-20 Thread Dan Smith (JIRA)
Dan Smith created GEODE-801:
---

 Summary: Integrate WAN and CQ Donations
 Key: GEODE-801
 URL: https://issues.apache.org/jira/browse/GEODE-801
 Project: Geode
  Issue Type: New Feature
Reporter: Dan Smith


Two new modules have been donated to apache geode from pivotal - WAN 
connectivity and continuous query. These modules are sitting on the 
wan_cq_donation branch.

The details of the donated code are described on this mailing list thread.

http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201601.mbox/%3C9767655A-1A66-4E66-BF39-3DA031E16219%40pivotal.io%3E

This JIRA tracks the work that needs to happen to these modules before they can 
be merged to develop



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


[jira] [Commented] (GEODE-785) Refactor repetitive comparison/loop code in CompiledIn.evaluate

2016-01-20 Thread ASF subversion and git services (JIRA)

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

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

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

GEODE-785: Refactor repetitive comparison/loop code in CompiledIn.evaluate

Collapsed multiple primitive array loops into a single one
Added CompiledInJUnitTest


> Refactor repetitive comparison/loop code in CompiledIn.evaluate
> ---
>
> Key: GEODE-785
> URL: https://issues.apache.org/jira/browse/GEODE-785
> Project: Geode
>  Issue Type: Improvement
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> In CompiledIn.evaluate we can see repetitive loops, each one differing only 
> in the cast to a specific array type.  For example:
>  // handle each type of primitive array
> if (evalColln instanceof long[]) {
>   long[] a = (long[])evalColln;
>   for (int i = 0; i < a.length; i++) {
> Object e = Long.valueOf(a[i]);
> if (TypeUtils.compare(evalElm, e, TOK_EQ).equals(Boolean.TRUE)) {
>   return Boolean.TRUE;
> }
>   }
>   return Boolean.FALSE;
> }
> 
> if (evalColln instanceof double[]) {
>   double[] a = (double[])evalColln;
>   for (int i = 0; i < a.length; i++) {
> Object e = Double.valueOf(a[i]);
> if (TypeUtils.compare(evalElm, e, TOK_EQ).equals(Boolean.TRUE)) {
>   return Boolean.TRUE;
> }
>   }
>   return Boolean.FALSE;
> }
> We should be able to write a test to exercise this code and then write a 
> single loop that handles all object thypes as the comparison is actually done 
> by the TypeUtils.compare() method.



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


[jira] [Created] (GEODE-800) Geode's classloading mechanism is unable to resolve classes found within nested jars

2016-01-20 Thread Jens Deppe (JIRA)
Jens Deppe created GEODE-800:


 Summary: Geode's classloading mechanism is unable to resolve 
classes found within nested jars
 Key: GEODE-800
 URL: https://issues.apache.org/jira/browse/GEODE-800
 Project: Geode
  Issue Type: Bug
  Components: management
Reporter: Jens Deppe


This issue is particularly evident when using Geode in a Spring Boot app which 
creates an 'über' jar containing all dependent jars.

When Geode is launched in this context, the following errors can be seen:
{noformat}
[warn 2016/01/20 08:53:29.431 PST  tid=0xd] (tid=13 msgId=0) Required 
Commands classes were not loaded. Check logs for errors.
java.lang.IllegalStateException: Required Commands classes were not loaded. 
Check logs for errors.
at 
com.gemstone.gemfire.management.internal.cli.CommandManager.raiseExceptionIfEmpty(CommandManager.java:249)
at 
com.gemstone.gemfire.management.internal.cli.CommandManager.loadCommands(CommandManager.java:188)
at 
com.gemstone.gemfire.management.internal.cli.CommandManager.(CommandManager.java:86)
at 
com.gemstone.gemfire.management.internal.cli.CommandManager.getInstance(CommandManager.java:278)
at 
com.gemstone.gemfire.management.internal.cli.CommandManager.getInstance(CommandManager.java:258)
at 
com.gemstone.gemfire.management.internal.cli.remote.CommandProcessor.(CommandProcessor.java:58)
...
{noformat}

The problem here is in {{ClasspathScanLoadHelper.getClasses()}}. In this method 
we call:
{noformat}
Enumeration resources = 
ClassPathLoader.getLatest().getResources(packagePath);
{noformat}
However {{getResources()}} doesn't just work against the 'latest' classloader, 
but also considers the thread context classloader. In the case of a Spring Boot 
app, Spring does provide such a classloader and {{getResources}} is able to 
find the necessary resources {{CommandMarker}} classes. (These classes are 
found within a nested jar. For ex. 
{{jar:file:/Users/jdeppe/src/woddrive/WodDrive-GF-Server/target/WodDriveGFServer.jar!/lib/gemfire-core-1.0.0-incubating-SNAPSHOT.jar!/com/gemstone/gemfire/management/internal/cli/commands}}).
 This is all fine, but subsequent code doesn't consider classes (or packages) 
within nested jars, and in addition, when classes actually get resolved, the 
thread context classloader (where those resources might have come from) is not 
considered.



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


[jira] [Commented] (GEODE-369) CI failure: RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut fails intermittently with assertion

2016-01-20 Thread Bruce Schuchardt (JIRA)

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

Bruce Schuchardt commented on GEODE-369:


The current line numbers for this failure are

{noformat}
RedundancyLevelPart1DUnitTest
  doPuts();
  verifyDeadServers(1);
  verifyRedundantServersContain(SERVER3);   -- line 514

and

RedundancyLevelTestBase
DistributedTestCase.waitForCriterion(wc, 60 * 1000, 2000, true);  -- line 
275
{noformat}


> CI failure: 
> RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut
>  fails intermittently with assertion
> 
>
> Key: GEODE-369
> URL: https://issues.apache.org/jira/browse/GEODE-369
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Darrel Schneider
>Assignee: Anilkumar Gingade
>  Labels: CI
>
> failed on a private build of git rev :
> {code}
> junit.framework.AssertionFailedError: Event never occurred after 6 ms: 
> Redundant servers ([doomtwo.gemstone.com29009]) does not contain 
> doomtwo.gemstone.com27615
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.TestCase.fail(TestCase.java:227)
>   at 
> dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1162)
>   at 
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelTestBase.verifyRedundantServersContain(RedundancyLevelTestBase.java:267)
>   at 
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut(RedundancyLevelPart1DUnitTest.java:505)
> {code}



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


[jira] [Created] (GEODE-799) Update Spring dependencies to 4.x

2016-01-20 Thread Jens Deppe (JIRA)
Jens Deppe created GEODE-799:


 Summary: Update Spring dependencies to 4.x 
 Key: GEODE-799
 URL: https://issues.apache.org/jira/browse/GEODE-799
 Project: Geode
  Issue Type: Improvement
  Components: management
Reporter: Jens Deppe


The latest Spring release is {{4.2.4.RELEASE}}.



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