[jira] [Assigned] (GEODE-6683) java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/GEODE-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Lindsey reassigned GEODE-6683: Assignee: Aaron Lindsey (was: Kirk Lund) > java.lang.NullPointerException > -- > > Key: GEODE-6683 > URL: https://issues.apache.org/jira/browse/GEODE-6683 > Project: Geode > Issue Type: Bug > Components: pulse >Affects Versions: 1.6.0 >Reporter: YE LIN >Assignee: Aaron Lindsey >Priority: Major > Labels: observability > > *Context:* > when Pulse is ran without embedded mode in Locator, throw NullPointException > during running code : repository.getJavaSslProperties().stringPropertyNames() > look like repository.javaSslProperties is null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6711) Please delete old releases from mirroring system
Sebb created GEODE-6711:
---
Summary: Please delete old releases from mirroring system
Key: GEODE-6711
URL: https://issues.apache.org/jira/browse/GEODE-6711
Project: Geode
Issue Type: Task
Reporter: Sebb
{color:#22}To reduce the load on the ASF mirrors, projects are required to
delete old releases [1]{color}
{color:#22}Please can you remove all non-current releases?{color}
{color:#22}It's unfair to expect the 3rd party mirrors to carry old
releases.{color}
{color:#22}However you can still link to the archives for historic
releases.{color}
{color:#22}Please also update your release procedures (if relevant) to
ensure superseded releases are archived once the new release has been published
and announced.{color}
{color:#22}Thanks!{color}
{color:#22}[1]
{color}[http://www.apache.org/dev/release.html#when-to-archive]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6683) java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/GEODE-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826482#comment-16826482 ] Kirk Lund commented on GEODE-6683: -- Here is the Apache Geode documentation on hosting Pulse in a Web Application Server. The bug would then require SSL to be configured. I'm guessing Geode has no tests for this mode of operation. > java.lang.NullPointerException > -- > > Key: GEODE-6683 > URL: https://issues.apache.org/jira/browse/GEODE-6683 > Project: Geode > Issue Type: Bug > Components: pulse >Affects Versions: 1.6.0 >Reporter: YE LIN >Assignee: Kirk Lund >Priority: Major > Labels: observability > > *Context:* > when Pulse is ran without embedded mode in Locator, throw NullPointException > during running code : repository.getJavaSslProperties().stringPropertyNames() > look like repository.javaSslProperties is null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6710) ConcurrentWANPropagation_1_DUnitTest > testReplicatedSerialPropagation_withoutRemoteSite FAILED
[
https://issues.apache.org/jira/browse/GEODE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-6710:
--
Assignee: Owen Nichols
> ConcurrentWANPropagation_1_DUnitTest >
> testReplicatedSerialPropagation_withoutRemoteSite FAILED
> ---
>
> Key: GEODE-6710
> URL: https://issues.apache.org/jira/browse/GEODE-6710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Owen Nichols
>Priority: Major
> Attachments: mhanson-findfailures-04-25-2019-13-36-10-logs.tgz
>
>
> CI failure.
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/659
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0219/test-results/distributedTest/1556223516/
>
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 5213
> [error 2019/04/25 19:34:30.869 UTC 172.17.0.10(655):41003 shared ordered uid=55 port=42296> tid=765]
> Exception occurred in CacheListener
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@7386490b
> rejected from java.util.concurrent.ThreadPoolExecutor@40491cec[Shutting
> down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks =
> 310]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:602)
> at
> org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
> at
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:178)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8350)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:7050)
> at
> org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6858)
> at
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2407)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:164)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6799)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:414)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:244)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:152)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:980)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6587)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6561)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:58)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6512)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1641)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1197)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2278)
> at
> org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:948)
> at
> org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:119)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1201)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1101)
> at
>
[jira] [Updated] (GEODE-6710) ConcurrentWANPropagation_1_DUnitTest > testReplicatedSerialPropagation_withoutRemoteSite FAILED
[
https://issues.apache.org/jira/browse/GEODE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson updated GEODE-6710:
---
Attachment: mhanson-findfailures-04-25-2019-13-36-10-logs.tgz
> ConcurrentWANPropagation_1_DUnitTest >
> testReplicatedSerialPropagation_withoutRemoteSite FAILED
> ---
>
> Key: GEODE-6710
> URL: https://issues.apache.org/jira/browse/GEODE-6710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
> Attachments: mhanson-findfailures-04-25-2019-13-36-10-logs.tgz
>
>
> CI failure.
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/659
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0219/test-results/distributedTest/1556223516/
>
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 5213
> [error 2019/04/25 19:34:30.869 UTC 172.17.0.10(655):41003 shared ordered uid=55 port=42296> tid=765]
> Exception occurred in CacheListener
> java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@7386490b
> rejected from java.util.concurrent.ThreadPoolExecutor@40491cec[Shutting
> down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks =
> 310]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:602)
> at
> org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
> at
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:178)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8350)
> at
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:7050)
> at
> org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6858)
> at
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2407)
> at
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:164)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6799)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:414)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:244)
> at
> org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:152)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:980)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6587)
> at
> org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6561)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:58)
> at
> org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6512)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1641)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1197)
> at
> org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2278)
> at
> org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:948)
> at
> org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:119)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1201)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1101)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:369)
>
[jira] [Created] (GEODE-6710) ConcurrentWANPropagation_1_DUnitTest > testReplicatedSerialPropagation_withoutRemoteSite FAILED
Mark Hanson created GEODE-6710:
--
Summary: ConcurrentWANPropagation_1_DUnitTest >
testReplicatedSerialPropagation_withoutRemoteSite FAILED
Key: GEODE-6710
URL: https://issues.apache.org/jira/browse/GEODE-6710
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Mark Hanson
CI failure.
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/659
http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0219/test-results/distributedTest/1556223516/
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 5213
[error 2019/04/25 19:34:30.869 UTC :41003 shared ordered uid=55 port=42296> tid=765] Exception
occurred in CacheListener
java.util.concurrent.RejectedExecutionException: Task
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@7386490b
rejected from java.util.concurrent.ThreadPoolExecutor@40491cec[Shutting down,
pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 310]
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
at
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:602)
at
org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91)
at
org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:178)
at
org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8350)
at
org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:7050)
at
org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6858)
at
org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2407)
at
org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:164)
at
org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6799)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:414)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:244)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:152)
at
org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:980)
at
org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6587)
at
org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6561)
at
org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:58)
at
org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6512)
at
org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1641)
at
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1197)
at
org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2278)
at
org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:948)
at
org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:119)
at
org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1201)
at
org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1101)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:369)
at
org.apache.geode.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:426)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.scheduleIncomingMessage(ClusterDistributionManager.java:2865)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.handleIncomingDMsg(ClusterDistributionManager.java:2552)
at
[jira] [Created] (GEODE-6709) Locators should not start when ClusterConfigurationService is on but JMX Manager is off
Peter Tran created GEODE-6709: - Summary: Locators should not start when ClusterConfigurationService is on but JMX Manager is off Key: GEODE-6709 URL: https://issues.apache.org/jira/browse/GEODE-6709 Project: Geode Issue Type: Improvement Components: management Reporter: Peter Tran ClusterConfigurationService provides the ability for deployed jars to be shared between members. When JMX Manager is off this is not possible. Locators should not start with the misconfiguration of ClusterManagement on and JMX Manager off. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6642) CacheAttributes header was left in the public header collection
[
https://issues.apache.org/jira/browse/GEODE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826305#comment-16826305
]
ASF subversion and git services commented on GEODE-6642:
Commit 38a6c8b6b32da8baca118287019ba035d124c870 in geode-native's branch
refs/heads/master from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=38a6c8b ]
GEODE-6642: Remove CacheAttributes (#475)
* GEODE-6642: Remove CacheAttributes
CacheAttributes based Cache creation was removed but the header was
accidently left in the public header location. Removal does not effect
public API or ABI. All methods to construct or use it on the public API
had already been removed.
Removes code dependent on CacheAttributes
Cleans up ownership of heap objects
> CacheAttributes header was left in the public header collection
> ---
>
> Key: GEODE-6642
> URL: https://issues.apache.org/jira/browse/GEODE-6642
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{CacheAttributes}} is not longer necessary and was inadvertently left in the
> public headers. The factory, {{CacheAttributesFactory}} was removed prior to
> the first release. All public APIs using {{CacheAttributes}} were removed
> prior to the first release.
> It should be safe to remove the header completely and cleanup internal usage
> of this class without effecting the public API and ABI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6650) Update to Boost 1.70.0
[ https://issues.apache.org/jira/browse/GEODE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826302#comment-16826302 ] ASF subversion and git services commented on GEODE-6650: Commit 77e9a1c8cdc71c8f0e4548fad8d84cf7b9970c86 in geode-native's branch refs/heads/master from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=77e9a1c ] GEODE-6650: Update to Boost 1.70.0 > Update to Boost 1.70.0 > -- > > Key: GEODE-6650 > URL: https://issues.apache.org/jira/browse/GEODE-6650 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6210) Geode Native C++ Example (Transaction with Retry)
[ https://issues.apache.org/jira/browse/GEODE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826300#comment-16826300 ] ASF subversion and git services commented on GEODE-6210: Commit 131ab14f75ae63e462b24936e52e00df9d5a3c20 in geode-native's branch refs/heads/master from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=131ab14 ] GEODE-6210: Native Client User Guide - document transaction examples (reviewer corrections) > Geode Native C++ Example (Transaction with Retry) > - > > Key: GEODE-6210 > URL: https://issues.apache.org/jira/browse/GEODE-6210 > Project: Geode > Issue Type: Sub-task > Components: examples, native client >Reporter: Charlie Black >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > As an end user, I would like to see an example of how to handle a common > exception thrown by Geode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6635) Native Client API docs: Use a 3-part version header
[ https://issues.apache.org/jira/browse/GEODE-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826301#comment-16826301 ] ASF subversion and git services commented on GEODE-6635: Commit e880e0a35b9fc0982f74e988427b3f0a9b32bbe6 in geode-native's branch refs/heads/master from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e880e0a ] GEODE-6635: Native Client API docs: Use a 3-part version header (#474) > Native Client API docs: Use a 3-part version header > --- > > Key: GEODE-6635 > URL: https://issues.apache.org/jira/browse/GEODE-6635 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.10.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Generate the C++ and .NET api docs with a 3-part version header > (major.minor.patch) instead of the current 2-part version header > (major.minor). > The 3-part header would be consistent with the current Geode convention, and > provides more precise information for the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6650) Update to Boost 1.70.0
[ https://issues.apache.org/jira/browse/GEODE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826303#comment-16826303 ] ASF subversion and git services commented on GEODE-6650: Commit bc5c08d3fe4261f64c0909fb61fe35e85bd68997 in geode-native's branch refs/heads/master from Blake Bender [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=bc5c08d ] Revert "GEODE-6650: Update to Boost 1.70.0" This reverts commit 77e9a1c8cdc71c8f0e4548fad8d84cf7b9970c86. - Fixes Windows build break due to new warnings introduced in v17 boost headers > Update to Boost 1.70.0 > -- > > Key: GEODE-6650 > URL: https://issues.apache.org/jira/browse/GEODE-6650 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6642) CacheAttributes header was left in the public header collection
[
https://issues.apache.org/jira/browse/GEODE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826304#comment-16826304
]
ASF subversion and git services commented on GEODE-6642:
Commit 38a6c8b6b32da8baca118287019ba035d124c870 in geode-native's branch
refs/heads/master from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=38a6c8b ]
GEODE-6642: Remove CacheAttributes (#475)
* GEODE-6642: Remove CacheAttributes
CacheAttributes based Cache creation was removed but the header was
accidently left in the public header location. Removal does not effect
public API or ABI. All methods to construct or use it on the public API
had already been removed.
Removes code dependent on CacheAttributes
Cleans up ownership of heap objects
> CacheAttributes header was left in the public header collection
> ---
>
> Key: GEODE-6642
> URL: https://issues.apache.org/jira/browse/GEODE-6642
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{CacheAttributes}} is not longer necessary and was inadvertently left in the
> public headers. The factory, {{CacheAttributesFactory}} was removed prior to
> the first release. All public APIs using {{CacheAttributes}} were removed
> prior to the first release.
> It should be safe to remove the header completely and cleanup internal usage
> of this class without effecting the public API and ABI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6120) CI Failure: TestExamples failing due to missing org.apache.commons.lang package
[
https://issues.apache.org/jira/browse/GEODE-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826290#comment-16826290
]
ASF subversion and git services commented on GEODE-6120:
Commit 469382985e21edc53a0d8040e25d1de5ba75ea97 in geode-examples's branch
refs/heads/master from Alexander Murmann
[ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=4693829 ]
GEODE-6120 - Fix missing commons-lang
The examples repo has been making use of the apache.commons-lang package
provided by the main Geode repo. In version 3 of commons-lang the
package was renamed to "commons-lang3". Since Geode updated its
dependency to that version we need to use the same package name in our
examples.
> CI Failure: TestExamples failing due to missing org.apache.commons.lang
> package
> ---
>
> Key: GEODE-6120
> URL: https://issues.apache.org/jira/browse/GEODE-6120
> Project: Geode
> Issue Type: Bug
> Components: examples
>Reporter: Ryan McMahon
>Assignee: Alexander Murmann
>Priority: Major
>
> {{clientSecurity verifyNoMembersRunning step seems to be failing due to
> inability to find package org.apache.commons.lang.}}
> *Error details:*
> {{3. Executing - shutdown --include-locators=true}}{{Shutdown is
> triggered}}{{:async:waitForExitingMembers}}
> {{Waiting at most 120 seconds for all members to shut down...}}
> {{...}}
> {{:async:runAll}}
> {{:clientSecurity:verifyNoMembersRunning}}
> {{Looking for existing member processes...}}
> {{:clientSecurity:compileJava/home/geode/geode/clientSecurity/src/main/java/org/apache/geode_examples/clientSecurity/Example.java:19:
> error: package org.apache.commons.lang does not exist}}
> {{import org.apache.commons.lang.Validate;}}{{1 error}}
> {{ FAILED}}
> *Failing build:*
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/TestExamples/builds/43]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5964) Examples should be runnable with Java 11
[ https://issues.apache.org/jira/browse/GEODE-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826291#comment-16826291 ] ASF subversion and git services commented on GEODE-5964: Commit e78ce032ac95db8dddb51dc8fc630cd0f7a91efc in geode-examples's branch refs/heads/master from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=e78ce03 ] GEODE-5964 run geode-examples with java11 (#70) * updates to gradle5 to support Java 11 (4.10.2 does not work) * update mockito to support Java 11 * fix classpath due to directory layout change in newer gradle * update examples to gradle 5.0 Co-authored-by: Jacob Barrett Co-authored-by: Owen Nichols > Examples should be runnable with Java 11 > > > Key: GEODE-5964 > URL: https://issues.apache.org/jira/browse/GEODE-5964 > Project: Geode > Issue Type: Sub-task > Components: examples >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > When geode-examples are pointed to a version of Geode that officially > supports Java 11, but the examples themselves should be able to compile and > run with Java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6648) wrong import of assertEquals in geode-example/functions
[ https://issues.apache.org/jira/browse/GEODE-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826295#comment-16826295 ] ASF subversion and git services commented on GEODE-6648: Commit 251d35e2759f76303df97d3585d09a758a5f0e01 in geode-examples's branch refs/heads/master from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=251d35e ] GEODE-6648: use org.junit.Assert.assertEquals org.jgroups.util.Util.assertEquals was wrongly imported instead of org.junit.Assert.assertEquals > wrong import of assertEquals in geode-example/functions > --- > > Key: GEODE-6648 > URL: https://issues.apache.org/jira/browse/GEODE-6648 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Fix For: 1.10.0 > > > It was wrongly imported to use org.jgroups.util.Util.assertEquals > -import static org.jgroups.util.Util.assertEquals; > +import static org.junit.Assert.assertEquals; > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5806) Create new example for durable client subscriptions
[ https://issues.apache.org/jira/browse/GEODE-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826293#comment-16826293 ] ASF subversion and git services commented on GEODE-5806: Commit a2b7afada61030e3d05f76be90687e673c0c8e03 in geode-examples's branch refs/heads/master from Ryan McMahon [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=a2b7afa ] GEODE-5806: Adding example for durable messaging in client subscriptions (#69) > Create new example for durable client subscriptions > --- > > Key: GEODE-5806 > URL: https://issues.apache.org/jira/browse/GEODE-5806 > Project: Geode > Issue Type: New Feature > Components: examples >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Create a new example for durable messaging with client subscriptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6060) CacheListener example in Geode Examples does not properly register listener
[ https://issues.apache.org/jira/browse/GEODE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826292#comment-16826292 ] ASF subversion and git services commented on GEODE-6060: Commit 15f5264a11a9c89c53e5c0d6410e532b6168733e in geode-examples's branch refs/heads/master from Ryan McMahon [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=15f5264 ] GEODE-6060: Properly registering example cache listener > CacheListener example in Geode Examples does not properly register listener > --- > > Key: GEODE-6060 > URL: https://issues.apache.org/jira/browse/GEODE-6060 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The CacheListener example does not actually register the > ExampleCacheListener() so the callback methods are not invoked which print to > the console. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6463) Use storage.googleapis.com for snapshots in the geode-examples build
[ https://issues.apache.org/jira/browse/GEODE-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826294#comment-16826294 ] ASF subversion and git services commented on GEODE-6463: Commit a6d6e709e424b078a110b66ceb87508f3e6e3ed7 in geode-examples's branch refs/heads/master from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=a6d6e70 ] GEODE-6463: Use https://storage.googleapis.com for maven snapshots Point directly at the gcloud bucket for nightly snapshots of geode. > Use storage.googleapis.com for snapshots in the geode-examples build > > > Key: GEODE-6463 > URL: https://issues.apache.org/jira/browse/GEODE-6463 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > One develop of geode-examples, we are getting nightly snapshots for geode > from maven.apachegeode-ci.info, which doesn't support https. We should switch > that to point directly at the google storage bucket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6423) availability checks sometimes immediately initiate removal
[
https://issues.apache.org/jira/browse/GEODE-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826242#comment-16826242
]
ASF subversion and git services commented on GEODE-6423:
Commit 0fea07ad0eb4cc23220e482967c2734f8835e982 in geode's branch
refs/heads/master from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0fea07a ]
GEODE-6423 availability checks sometimes immediately initiate removal
Do not loop in trying to form a tcp/ip connection to a suspect unless
the next step is to remove the suspect from membership. In this case
there will be another invocation of the same method that will take the
removal step next.
(cherry picked from commit 2e0a893f0587bdcec560960a6b283b5465d5897f)
> availability checks sometimes immediately initiate removal
> --
>
> Key: GEODE-6423
> URL: https://issues.apache.org/jira/browse/GEODE-6423
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> If the network goes down the JGroupsMessenger service initiates suspect
> processing when it tries to send messages. In 1.8 this seems to initiate
> immediate removal of the suspect.
> ioexception sending udp message initiates suspicion
> suspect processing initiates a final check
> the final check fails immediately (it's using a timed Socket.connect() which
> fails immediately)
> the member is declared dead
> {noformat}
> [info 2019/02/13 17:44:59.366 CST perf157-130-167-server1 Detection thread 3> tid=0xc2] received suspect message from myself for
> 192.168.130.167(perf157-130-167-locator1:225065:locator):41000:
> Unable to send messages to this member via JGroups
> [info 2019/02/13 17:44:59.368 CST perf157-130-167-server1 Detection thread 4> tid=0xc3] Performing final check for suspect member
> 192.168.130.167(perf157-130-167-locator1:225065:locator):41000
> reason=Unable to send messages to this member via JGroups
> [info 2019/02/13 17:44:59.368 CST perf157-130-167-server1 Detection thread 5> tid=0xc4] Performing final check for suspect member
> 192.168.130.167(perf157-130-167-worker1:225794):16202 reason=Unable to
> send messages to this member via JGroups
> [info 2019/02/13 17:44:59.368 CST perf157-130-167-server1 Detection thread 4> tid=0xc3] Failure detection is now watching
> 192.168.130.167(perf157-130-167-server1:225263):16200
> [info 2019/02/13 17:44:59.368 CST perf157-130-167-server1 Detection thread 5> tid=0xc4] Failure detection is now watching
> 192.168.130.167(perf157-130-167-locator1:225065:locator):41000
> [info 2019/02/13 17:44:59.368 CST perf157-130-167-server1 Detection thread 3> tid=0xc2] received suspect message from myself for
> 192.168.130.167(perf157-130-167-server2:225522):16201: Unable to send
> messages to this member via JGroups
> [info 2019/02/13 17:44:59.369 CST perf157-130-167-server1 Detection thread 6> tid=0xc5] Performing final check for suspect member
> 192.168.130.167(perf157-130-167-server2:225522):16201 reason=Unable to
> send messages to this member via JGroups
> [info 2019/02/13 17:44:59.369 CST perf157-130-167-server1 Detection thread 6> tid=0xc5] Failure detection is now watching
> 192.168.130.167(perf157-130-167-server1:225263):16200
> [info 2019/02/13 17:44:59.371 CST perf157-130-167-server1 Detection thread 5> tid=0xc4] Final check failed for member
> 192.168.130.167(perf157-130-167-worker1:225794):16202
> [info 2019/02/13 17:44:59.371 CST perf157-130-167-server1 Detection thread 5> tid=0xc4] Requesting removal of suspect member
> 192.168.130.167(perf157-130-167-worker1:225794):16202
> [info 2019/02/13 17:44:59.371 CST perf157-130-167-server1 Detection thread 4> tid=0xc3] Final check failed for member
> 192.168.130.167(perf157-130-167-locator1:225065:locator):41000
> [info 2019/02/13 17:44:59.371 CST perf157-130-167-server1 Detection thread 4> tid=0xc3] Requesting removal of suspect member
> 192.168.130.167(perf157-130-167-locator1:225065:locator):41000
> [info 2019/02/13 17:44:59.371 CST perf157-130-167-server1 Detection thread 4> tid=0xc3] This member is becoming the membership
> coordinator with address
> 192.168.130.167(perf157-130-167-server1:225263):16200
> [info 2019/02/13 17:44:59.371 CST perf157-130-167-server1 Detection thread 6> tid=0xc5] Final check failed for member
> 192.168.130.167(perf157-130-167-server2:225522):16201
> [info 2019/02/13 17:44:59.373 CST perf157-130-167-server1 Detection thread 6> tid=0xc5] Requesting removal of suspect member
> 192.168.130.167(perf157-130-167-server2:225522):16201
> [info 2019/02/13 17:44:59.376 CST perf157-130-167-server1 Detection thread 4> tid=0xc3]
[jira] [Commented] (GEODE-6630) RedundancyLogger might throw NPE
[
https://issues.apache.org/jira/browse/GEODE-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826243#comment-16826243
]
ASF subversion and git services commented on GEODE-6630:
Commit 7d7f8f18d352b66a51ac735843213046b6b1cb26 in geode's branch
refs/heads/master from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7d7f8f1 ]
GEODE-6630: move allBucketsRecoveredFromDisk count down latch (#3477)
* Rename RedundancyLogger to PersistentBucketRecoverer
* Move allBucketsRecoveredFromDisk count down latch from PRHARedundancyProvider
to PersistentBucketRecoverer.
* Provide utility methods for using the count down latch.
> RedundancyLogger might throw NPE
>
>
> Key: GEODE-6630
> URL: https://issues.apache.org/jira/browse/GEODE-6630
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0
>Reporter: xiaojian zhou
>Assignee: Eric Shu
>Priority: Major
> Labels: SmallFeature
> Fix For: 1.9.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> {noformat}
> I noticed in some tests with following error logged in debug level:
> [debug 2019/04/10 11:25:52.904 PDT
> tid=0x55] Unexpected exception in PR redundancy recovery
> java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.partitioned.RedundancyLogger.run2(RedundancyLogger.java:154)
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:59)
> at java.lang.Thread.run(Thread.java:748)
> Then I looked at the code that it's using:
> (this.allBucketsRecoveredFromDisk.getCount() > 0) in more than one places.
> The allBucketsRecoveredFromDisk is referecing to the object in
> PRHARedundancyProvider.
> But in PRHARedundancyProvider, it is using:
> public boolean isPersistentRecoveryComplete() {
> if (!ColocationHelper.checkMembersColocation(this.prRegion,
> this.prRegion.getMyId())) {
> return false;
> }
> if (allBucketsRecoveredFromDisk != null &&
> allBucketsRecoveredFromDisk.getCount() > 0) {
> return false;
> }
> So allBucketsRecoveredFromDisk could be null. We should alway use
> "(allBucketsRecoveredFromDisk != null &&
> allBucketsRecoveredFromDisk.getCount() > 0) " instead of
> "(this.allBucketsRecoveredFromDisk.getCount() > 0)"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6708) Possible NPE if two cache client initialization threads are active for the same client ID
[ https://issues.apache.org/jira/browse/GEODE-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McMahon updated GEODE-6708: Affects Version/s: 1.10.0 Fix Version/s: (was: 1.10.0) Component/s: client queues > Possible NPE if two cache client initialization threads are active for the > same client ID > - > > Key: GEODE-6708 > URL: https://issues.apache.org/jira/browse/GEODE-6708 > Project: Geode > Issue Type: Bug > Components: client queues >Affects Versions: 1.10.0 >Reporter: Ryan McMahon >Priority: Major > > There are scenarios where a client will have several cache client > initialization threads active (for instance, if the first thread blocked for > a significant amount of time waiting for a lock). In that scenario, it is > possible for two threads to create their own registration queues and only one > "wins", then upon draining the queue the first thread to remove the queue can > cause an NPE in the second thread because it was assumed the queue was still > present. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6708) Possible NPE if two cache client initialization threads are active for the same client ID
[ https://issues.apache.org/jira/browse/GEODE-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McMahon reassigned GEODE-6708: --- Assignee: Ryan McMahon > Possible NPE if two cache client initialization threads are active for the > same client ID > - > > Key: GEODE-6708 > URL: https://issues.apache.org/jira/browse/GEODE-6708 > Project: Geode > Issue Type: Bug > Components: client queues >Affects Versions: 1.10.0 >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > > There are scenarios where a client will have several cache client > initialization threads active (for instance, if the first thread blocked for > a significant amount of time waiting for a lock). In that scenario, it is > possible for two threads to create their own registration queues and only one > "wins", then upon draining the queue the first thread to remove the queue can > cause an NPE in the second thread because it was assumed the queue was still > present. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6708) Possible NPE if two cache client initialization threads are active for the same client ID
Ryan McMahon created GEODE-6708: --- Summary: Possible NPE if two cache client initialization threads are active for the same client ID Key: GEODE-6708 URL: https://issues.apache.org/jira/browse/GEODE-6708 Project: Geode Issue Type: Bug Reporter: Ryan McMahon Fix For: 1.10.0 There are scenarios where a client will have several cache client initialization threads active (for instance, if the first thread blocked for a significant amount of time waiting for a lock). In that scenario, it is possible for two threads to create their own registration queues and only one "wins", then upon draining the queue the first thread to remove the queue can cause an NPE in the second thread because it was assumed the queue was still present. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5971) Refactor gfsh commands to extend SingleGfshCommand and return ResultModel
[ https://issues.apache.org/jira/browse/GEODE-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826145#comment-16826145 ] ASF subversion and git services commented on GEODE-5971: Commit 96466c95cc233111db2d57b5d97ea52864fee875 in geode's branch refs/heads/develop from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=96466c9 ] GEODE-5971: delete LegacyCommandResult and rename ModelResultModel to… (#3497) > Refactor gfsh commands to extend SingleGfshCommand and return ResultModel > - > > Key: GEODE-5971 > URL: https://issues.apache.org/jira/browse/GEODE-5971 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 41h 10m > Remaining Estimate: 0h > > This list will eventually include the following commands: > - AlterAsyncEventQueueCommand > - AlterOfflineDiskStoreCommand > - AlterRegionCommand > - AlterRuntimeConfigCommand > - BackupDiskStoreCommand > - ChangeLogLevelCommand > - ClearDefinedIndexesCommand > - CloseDurableCQsCommand > - CloseDurableClientCommand > - CompactDiskStoreCommand > - CompactOfflineDiskStoreCommand > - ConnectCommand > - CountDurableCQEventsCommand > - CreateGatewaySenderCommand > - CreateRegionCommand > - DebugCommand > - DefineIndexCommand > - DeployCommand > - DescribeClientCommand > - DescribeConfigCommand > - DescribeConnectionCommand > - DescribeDiskStoreCommand > - DescribeJndiBindingCommand > - DescribeMemberCommand > - DescribeOfflineDiskStoreCommand > - DescribeRegionCommand > - DestroyAsyncEventQueueCommand > - DestroyFunctionCommand > - DestroyGatewaySenderCommand > - DestroyRegionCommand > - DisconnectCommand > - EchoCommand > - ExecuteFunctionCommand > - ExecuteScriptCommand > - ExitCommand > - ExportClusterConfigurationCommand > - ExportConfigCommand > - ExportDataCommand > - ExportLogsCommand > - ExportOfflineDiskStoreCommand > - ExportStackTraceCommand > - GCCommand > - GetCommand > - GfshHelpCommand > - GfshHintCommand > - HistoryCommand > - ImportClusterConfigurationCommand > - ImportDataCommand > - ListAsyncEventQueuesCommand > - ListClientCommand > - ListDeployedCommand > - ListDiskStoresCommand > - ListDurableClientCQsCommand > - ListFunctionCommand > - ListGatewayCommand > - ListIndexCommand > - ListJndiBindingCommand > - ListMembersCommand > - ListRegionCommand > - LoadBalanceGatewaySenderCommand > - LocateEntryCommand > - NetstatCommand > - PDXRenameCommand > - PauseGatewaySenderCommand > - PutCommand > - QueryCommand > - RebalanceCommand > - RemoveCommand > - ResumeGatewaySenderCommand > - RevokeMissingDiskStoreCommand > - SetVariableCommand > - ShCommand > - ShowDeadlockCommand > - ShowLogCommand > - ShowMetricsCommand > - ShowMissingDiskStoreCommand > - ShutdownCommand > - SleepCommand > - StartGatewayReceiverCommand > - StartGatewaySenderCommand > - StartLocatorCommand > - StartServerCommand > - StatusClusterConfigServiceCommand > - StatusGatewayReceiverCommand > - StatusGatewaySenderCommand > - StopGatewayReceiverCommand > - StopGatewaySenderCommand > - UndeployCommand > - UpgradeOfflineDiskStoreCommand > - ValidateDiskStoreCommand > - VersionCommand > - StartJConsoleCommand > - StartJVisualVMCommand > - StartPulseCommand > - StartVsdCommand > - StatusLocatorCommand > - StatusServerCommand > - StopLocatorCommand > - StopServerCommand > - LuceneIndexCommands -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6707) gfsh export logs does not export rolled over GC logs
Srikanth Manvi created GEODE-6707: - Summary: gfsh export logs does not export rolled over GC logs Key: GEODE-6707 URL: https://issues.apache.org/jira/browse/GEODE-6707 Project: Geode Issue Type: Improvement Components: gfsh Reporter: Srikanth Manvi If GC logs are configured to land in the same directory as Geode server logs then the current GC log is exported when we run gfsh>export logs. However if the rolled over GC logs are not exported. This happens because the rolled over GC logs are of the form server_gc.log.16 and gfsh export command logs for files ending with *.log however GC log rolling causes the files to end with a file number. Note: If GC logs are written a directory other than where server logs end up, then even the latest GC log doesn't get exported. GEODE-6706 talks about that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6706) gfsh export logs should export GC logs as well
Srikanth Manvi created GEODE-6706:
-
Summary: gfsh export logs should export GC logs as well
Key: GEODE-6706
URL: https://issues.apache.org/jira/browse/GEODE-6706
Project: Geode
Issue Type: Improvement
Components: gfsh
Reporter: Srikanth Manvi
If GC logs are not written to the same directory as geode server logs, then GC
logs are not exported when we run gfsh>export logs
GC log can be configured something like the below
{noformat}
gfsh> start server --name=server1
--J=-Xloggc:/tmp/server1/server1_gc.log{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets
[
https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Kevo updated GEODE-6472:
--
Fix Version/s: 1.10.0
> cachePerfStats:gets is double incremented on partitioned region gets
>
>
> Key: GEODE-6472
> URL: https://issues.apache.org/jira/browse/GEODE-6472
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Jacob S. Barrett
>Assignee: Mario Kevo
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The cache level stats, cachePerfStats, shows double the gets for portioned
> region stats.
> If a client does 1000 gets/second on a partitioned region and you examine the
> servers stats archive you will see {{cachePerfStats:gets}} will show 2000
> (and change) gets/second while {{RegionStats-partitioned:gets}} will show
> 1000 gets/second.
> Other region/cache stats, like put, may also be effected similarly.
> May effect versions older than 1.8.
> A test should be written to assert that region and cache stats are relatively
> the same for cases where only one region is being accessed on the cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
