[
https://issues.apache.org/jira/browse/GEODE-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981742#comment-16981742
]
ASF subversion and git services commented on GEODE-7442:
--------------------------------------------------------
Commit d000cb8a9af140382da66745e18c49dbcef6f9ff in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d000cb8 ]
GEODE-7442: Fix RegionAttributesCreation (#4317)
- Do not automatically override the 'off-heap' property when
configuring the 'PartitionAttributes' declaratively.
> 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
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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)
