[
https://issues.apache.org/jira/browse/GEODE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088227#comment-15088227
]
Jianxia Chen commented on GEODE-382:
------------------------------------
>From Barry:
Each of these tests has a setUp or init method to create a cache. Then later,
they use com.gemstone.gemfire.cache.query.CacheUtils to do something which
attempts to create another cache in a static block. If the caches don't match,
a message like this is logged which causes the suspect strings:
java.lang.IllegalStateException: A connection to a distributed system already
exists in this VM. It has the following configuration:
...
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.validateSameProperties(InternalDistributedSystem.java:2984)
at
com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1641)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:227)
at com.gemstone.gemfire.cache.query.CacheUtils.init(CacheUtils.java:60)
at
com.gemstone.gemfire.cache.query.CacheUtils.<clinit>(CacheUtils.java:48)
at
com.gemstone.gemfire.cache.query.transaction.QueryAndJtaTest.testAllIndexesOnCommitForPut(QueryAndJtaTest.java:363)
> CacheUtils static initializer of cache conflicts with certain query tests
> -------------------------------------------------------------------------
>
> Key: GEODE-382
> URL: https://issues.apache.org/jira/browse/GEODE-382
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Jason Huynh
> Assignee: Jianxia Chen
> Priority: Minor
>
> Modify cache utils to not statically create a cache. Tests that relied on
> this behavior need to be modified to explicitly initialize the cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
