[jira] [Resolved] (GEODE-10444) Difference Between Pivotal Gemfire and Apache Geode
[ https://issues.apache.org/jira/browse/GEODE-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bretl resolved GEODE-10444. Assignee: Mark Bretl Resolution: Done Hi [~rhajvijay] , excellent question, however, I do not think a Jira is the right place to answer this. I would highly recommend emailing the Geode User group, u...@geode.apache.org, this question so it can be seen by all and archived on the list for later viewing. Please let me know if you have any issues emailing the distribution list. --Mark > Difference Between Pivotal Gemfire and Apache Geode > --- > > Key: GEODE-10444 > URL: https://issues.apache.org/jira/browse/GEODE-10444 > Project: Geode > Issue Type: New Feature >Reporter: Rhajvijay Manoharan >Assignee: Mark Bretl >Priority: Major > > Hi Team, > I had worked on Pivotal Gemfire. And I'm convinced to use Apache Geode as its > open source. I would like to know the differences between the both. And want > to know the features which are in Gemfire that are not available with Geode. > Thanks, > Rhaj Vijay Manoharan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GEODE-5049) Add Geode Image To https://www.apache.org/img/
Mark Bretl created GEODE-5049: - Summary: Add Geode Image To https://www.apache.org/img/ Key: GEODE-5049 URL: https://issues.apache.org/jira/browse/GEODE-5049 Project: Geode Issue Type: Task Components: website Reporter: Mark Bretl As part of the Apache Website check ([https://whimsy.apache.org/site/check/),] the Geode image is missing from [https://www.apache.org/img/] and causing the image check to be 'red'. Task is to add a Geode image to [https://www.apache.org/img/], with the name geode.jpg. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2708) Update Gradle Wrapper to Gradle 3
[
https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bretl resolved GEODE-2708.
---
Resolution: Fixed
Gradle wrapper is now set for 3.5.1
> Update Gradle Wrapper to Gradle 3
> -
>
> Key: GEODE-2708
> URL: https://issues.apache.org/jira/browse/GEODE-2708
> Project: Geode
> Issue Type: Task
> Components: build
>Reporter: Galen O'Sullivan
>Assignee: Mark Bretl
>
> It looks like we're still running on a very old version of Gradle. This may
> be related to incremental builds not working properly.
> {code}
> $ ./gradlew --version
>
> Gradle 2.14.1
>
> Build time: 2016-07-18 06:38:37 UTC
> Revision: d9e2113d9fb05a5caabba61798bdb8dfdca83719
> Groovy: 2.4.4
> Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM: 1.8.0_111 (Oracle Corporation 25.111-b14)
> OS: Mac OS X 10.12.3 x86_64
> $ gradle --version
>
> Gradle 3.4.1
>
> Build time: 2017-03-03 19:45:41 UTC
> Revision: 9eb76efdd3d034dc506c719dac2955efb5ff9a93
> Groovy: 2.4.7
> Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM: 1.8.0_111 (Oracle Corporation 25.111-b14)
> OS: Mac OS X 10.12.3 x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (GEODE-3509) Update Gradle Docker Plugin To Work With Gradle 3.X
[ https://issues.apache.org/jira/browse/GEODE-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bretl resolved GEODE-3509. --- Resolution: Duplicate > Update Gradle Docker Plugin To Work With Gradle 3.X > --- > > Key: GEODE-3509 > URL: https://issues.apache.org/jira/browse/GEODE-3509 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Mark Bretl > > After updating the Gradle wrapper to 3.5.1, the Docker plugin now fails with > the error: > Could not find matching constructor for: > org.gradle.process.internal.worker.DefaultWorkerProcessFactory(org.gradle.api.logging.LogLevel, > com.pedjak.gradle.plugins.dockerizedtest.DockerizedTestPlugin$MessageServer, > org.gradle.api.internal.DefaultClassPathRegistry, > org.gradle.internal.id.LongIdGenerator, java.io.File, > org.gradle.api.internal.file.TmpDirTemporaryFileProvider, > com.sun.proxy.$Proxy73) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-3509) Update Gradle Docker Plugin To Work With Gradle 3.X
Mark Bretl created GEODE-3509: - Summary: Update Gradle Docker Plugin To Work With Gradle 3.X Key: GEODE-3509 URL: https://issues.apache.org/jira/browse/GEODE-3509 Project: Geode Issue Type: Bug Components: build Reporter: Mark Bretl After updating the Gradle wrapper to 3.5.1, the Docker plugin now fails with the error: Could not find matching constructor for: org.gradle.process.internal.worker.DefaultWorkerProcessFactory(org.gradle.api.logging.LogLevel, com.pedjak.gradle.plugins.dockerizedtest.DockerizedTestPlugin$MessageServer, org.gradle.api.internal.DefaultClassPathRegistry, org.gradle.internal.id.LongIdGenerator, java.io.File, org.gradle.api.internal.file.TmpDirTemporaryFileProvider, com.sun.proxy.$Proxy73) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3174) Use of multiple cache configuration (xml) can alter/impact cache setting during restart.
[ https://issues.apache.org/jira/browse/GEODE-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078611#comment-16078611 ] Mark Bretl commented on GEODE-3174: --- Hi [~agingade], What version are you running? Would you be able to select 'Affect Version' JIRA field? Thanks, --Mark > Use of multiple cache configuration (xml) can alter/impact cache setting > during restart. > > > Key: GEODE-3174 > URL: https://issues.apache.org/jira/browse/GEODE-3174 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Anilkumar Gingade > > When system is configured using multiple cache configuration xml, the cache > setting could differ during restart. > When a geode node is configured using, cluster configuration and its own > cache.xml; during re-start the cache.xml settings are applied only after > cluster-configuration xml is parsed which leads to cache getting > created/initialized using partial configuration details. > One of the problem encountered is with pdx persistent setting. The pdx > persistent setting was done using node's cache.xml. And persistent regions > are created using cluster configuration. When the node was re-started, the > system parses the cluster-configuration file, and while creating the > persistent region throws exception saying pdx is not persisted, as the pdx > persistent setting is defined in cache.xml; which is processed later. > While code walk through, noticed one more issue with pdx-type registry, which > could get created as non-persistent region when the node is re-started. > One solution would be to merge all the xml (cluster-configuration, > server-group and cache.xml) before cache creation is invoked. > Steps to reproduce: > Start locator. > Start server1 with its own cache.xml with pdx-persistance set (make sure > use-cluster configuration is set to true) > Start server2 with its own cache.xml with pdx-persistance set (make sure > use-cluster configuration is set to true) > create non-persistent-partition region. Add pdx entries to it. > create persistent-partition region. > stop server2 > re-start server2 > it fails with: > Exception in thread "main" org.apache.geode.pdx.PdxInitializationException: > The PDX metadata must be persistent in a member that has persistent data. See > CacheFactory.setPdxPersistent. > at > org.apache.geode.pdx.internal.PeerTypeRegistration.checkAllowed(PeerTypeRegistration.java:535) > at > org.apache.geode.pdx.internal.PeerTypeRegistration.creatingPersistentRegion(PeerTypeRegistration.java:483) > at > org.apache.geode.pdx.internal.TypeRegistry.creatingPersistentRegion(TypeRegistry.java:276) > at > org.apache.geode.internal.cache.LocalRegion.findDiskStore(LocalRegion.java:7800) > at > org.apache.geode.internal.cache.PartitionedRegion.findDiskStore(PartitionedRegion.java:9378) > at > org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:600) > at > org.apache.geode.internal.cache.PartitionedRegion.(PartitionedRegion.java:614) > at > org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3260) > at > org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3199) > at > org.apache.geode.internal.cache.xmlcache.RegionCreation.createRoot(RegionCreation.java:255) > at > org.apache.geode.internal.cache.xmlcache.CacheCreation.initializeRegions(CacheCreation.java:544) > at > org.apache.geode.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:495) > at > org.apache.geode.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:343) > at > org.apache.geode.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4483) > at > org.apache.geode.internal.cache.ClusterConfigurationLoader.applyClusterXmlConfiguration(ClusterConfigurationLoader.java:129) > at > org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1245) > at > org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:796) > at > org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:783) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:179) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at >
[jira] [Comment Edited] (GEODE-2708) Update Gradle Wrapper to Gradle 3
[ https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049526#comment-16049526 ] Mark Bretl edited comment on GEODE-2708 at 6/14/17 10:48 PM: - I did some research on this. It is the ANTLR plugin which is causing this issue to break in eclipse. I have tracked the issue back to Gradle version 3.2, 3.1 and 3.0 seem to work. Need to understand what changed in Gradle 3.2 Here is the stacktrace for importing our Gradle build into Eclipse using the Buildship 2.0.2 plugin: Synchronize Gradle projects with workspace failed due to an error connecting to the Gradle build. The supplied build action failed with an exception. Cannot change dependencies of configuration ':geode-core:antlr' after it has been included in dependency resolution. org.gradle.tooling.BuildActionFailureException: The supplied build action failed with an exception. at org.gradle.tooling.internal.consumer.connection.CancellableConsumerConnection$CancellableActionRunner.run(CancellableConsumerConnection.java:104) at org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:62) at org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:53) at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter$1.run(DefaultBuildActionExecuter.java:71) at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:84) at org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45) at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58) at org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38) at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46) 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) at org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46) at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter.run(DefaultBuildActionExecuter.java:60) at com.gradleware.tooling.toolingclient.internal.DefaultToolingClient.executeAndWait(DefaultToolingClient.java:106) at com.gradleware.tooling.toolingclient.internal.DefaultBuildActionRequest.executeAndWait(DefaultBuildActionRequest.java:51) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository$13.get(DefaultModelRepository.java:287) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.executeAndWait(DefaultModelRepository.java:355) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.access$100(DefaultModelRepository.java:49) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository$14.call(DefaultModelRepository.java:313) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4724) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3522) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2315) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2278) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2193) at com.google.common.cache.LocalCache.get(LocalCache.java:3932) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4721) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.getFromCache(DefaultModelRepository.java:330) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.executeRequest(DefaultModelRepository.java:309) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.executeRequest(DefaultModelRepository.java:280) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.fetchEclipseGradleProjects(DefaultModelRepository.java:238) at
[jira] [Commented] (GEODE-2708) Update Gradle Wrapper to Gradle 3
[ https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16049526#comment-16049526 ] Mark Bretl commented on GEODE-2708: --- I did some research on this. It is the ANTLR plugin which is causing this issue to break in eclipse. I have tracked to Gradle version 3.0. Here is the stacktrace for importing our Gradle build into Eclipse using the Buildship 2.0.2 plugin: Synchronize Gradle projects with workspace failed due to an error connecting to the Gradle build. The supplied build action failed with an exception. Cannot change dependencies of configuration ':geode-core:antlr' after it has been included in dependency resolution. org.gradle.tooling.BuildActionFailureException: The supplied build action failed with an exception. at org.gradle.tooling.internal.consumer.connection.CancellableConsumerConnection$CancellableActionRunner.run(CancellableConsumerConnection.java:104) at org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:62) at org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:53) at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter$1.run(DefaultBuildActionExecuter.java:71) at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:84) at org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45) at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58) at org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38) at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46) 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) at org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46) at org.gradle.tooling.internal.consumer.DefaultBuildActionExecuter.run(DefaultBuildActionExecuter.java:60) at com.gradleware.tooling.toolingclient.internal.DefaultToolingClient.executeAndWait(DefaultToolingClient.java:106) at com.gradleware.tooling.toolingclient.internal.DefaultBuildActionRequest.executeAndWait(DefaultBuildActionRequest.java:51) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository$13.get(DefaultModelRepository.java:287) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.executeAndWait(DefaultModelRepository.java:355) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.access$100(DefaultModelRepository.java:49) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository$14.call(DefaultModelRepository.java:313) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4724) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3522) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2315) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2278) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2193) at com.google.common.cache.LocalCache.get(LocalCache.java:3932) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4721) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.getFromCache(DefaultModelRepository.java:330) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.executeRequest(DefaultModelRepository.java:309) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.executeRequest(DefaultModelRepository.java:280) at com.gradleware.tooling.toolingmodel.repository.internal.DefaultModelRepository.fetchEclipseGradleProjects(DefaultModelRepository.java:238) at org.eclipse.buildship.core.workspace.internal.DefaultModelProvider.fetchEclipseGradleProjects(DefaultModelProvider.java:66) at
[jira] [Updated] (GEODE-2708) Update Gradle Wrapper to Gradle 3
[
https://issues.apache.org/jira/browse/GEODE-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bretl updated GEODE-2708:
--
Fix Version/s: (was: 1.2.0)
> Update Gradle Wrapper to Gradle 3
> -
>
> Key: GEODE-2708
> URL: https://issues.apache.org/jira/browse/GEODE-2708
> Project: Geode
> Issue Type: Task
> Components: build
>Reporter: Galen O'Sullivan
>Assignee: Mark Bretl
>
> It looks like we're still running on a very old version of Gradle. This may
> be related to incremental builds not working properly.
> {code}
> $ ./gradlew --version
>
> Gradle 2.14.1
>
> Build time: 2016-07-18 06:38:37 UTC
> Revision: d9e2113d9fb05a5caabba61798bdb8dfdca83719
> Groovy: 2.4.4
> Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM: 1.8.0_111 (Oracle Corporation 25.111-b14)
> OS: Mac OS X 10.12.3 x86_64
> $ gradle --version
>
> Gradle 3.4.1
>
> Build time: 2017-03-03 19:45:41 UTC
> Revision: 9eb76efdd3d034dc506c719dac2955efb5ff9a93
> Groovy: 2.4.7
> Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
> JVM: 1.8.0_111 (Oracle Corporation 25.111-b14)
> OS: Mac OS X 10.12.3 x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
