You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Juan Ramos (Jira)" <ji...@apache.org> on 2019/11/12 15:51:00 UTC
[jira] [Assigned] (GEODE-7442) IllegalStateException: Attempting to
use localMaxMemory for off-heap but value is not yet known
[ https://issues.apache.org/jira/browse/GEODE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juan Ramos reassigned GEODE-7442:
---------------------------------
Assignee: Juan Ramos
> IllegalStateException: Attempting to use localMaxMemory for off-heap but value is not yet known
> -----------------------------------------------------------------------------------------------
>
> Key: GEODE-7442
> URL: https://issues.apache.org/jira/browse/GEODE-7442
> Project: Geode
> Issue Type: Bug
> Components: configuration, regions
> Reporter: Juan Ramos
> Assignee: Juan Ramos
> Priority: Major
> Labels: GeodeCommons
>
> The fix for GEODE-7162 introduced an internal regression: the {{CacheXmlGenerator}} might throw an exception whenever we use it to generate a {{cache.xml}} using a declarative approach with a partitioned region configured with {{off-heap}} and no {{local-max-memory}}.
> The issue is that we're overriding ({{partitionAttributes.setOffHeap(offHeap)}}) the {{off-heap}} value after cloning and merging the original partition attributes, causing a problem when using a declarative approach as we can't automatically detect the default {{local-max-memory}} if the member has not been started yet (not JVM to query).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)