[jira] [Commented] (GEODE-6918) Log an INFO level message when all actions performed for a cache server startup are completed
[ https://issues.apache.org/jira/browse/GEODE-6918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891489#comment-16891489 ] ASF subversion and git services commented on GEODE-6918: Commit f9686809fdb95dbd22fee00165e874685df8024e in geode's branch refs/heads/develop from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f968680 ] GEODE-6918: Adding log message to denote end of startup (#3824) Added a log message to InternalResourceManager to denote the end of startup Added new test class to test the message occurs. Co-authored-by: Kirk Lund Co-authored-by: Aaron Lindsey Co-authored-by: Michael Oleske Co-authored-by: Dale Emery > Log an INFO level message when all actions performed for a cache server > startup are completed > - > > Key: GEODE-6918 > URL: https://issues.apache.org/jira/browse/GEODE-6918 > Project: Geode > Issue Type: Wish > Components: logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Time Spent: 5h > Remaining Estimate: 0h > > Log an INFO level message when all actions performed for a cache server > startup are completed. > Below is a complete list of all actions performed for a cache server startup: > * Start logging to gemfire log file > * Load and init DistributedSystemServices > * [Optional] Initialize DataSerializers and optional filter > * [Optional] Create off heap storage > * [Optional] Lock memory > * [Optional] Start embedded locator > * Create thread pools and join membership > * Start statistics sampling > * Start alerting service > * Wire up metrics publishing > * [Optional] Request cluster config from locator > * Start creating cache > * Create HTTP service > * [Optional] Deploy JARs from cluster config > * Create MemberMXBean > * Initialize cache services > * [Optional] Create regions from cache xml cluster config > * [Optional] Create regions from cache xml file and PDX region > * [Async] [Optional] Begin redundancy recovery > * [Async] [Optional] Begin recovery of values from disk > * [Optional] Create OQL indices > * [Optional] Complete get initial image (GII) > * [Optional] Create RegionMXBean > * [Optional] Start client/server acceptor > * [Optional] Create CacheServerMXBean > * [Optional] Assign buckets > * [Async] [Optional] Rebalance buckets -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (GEODE-6947) geode-managment should create its own set of configuration objects for PdxConfiguration
[ https://issues.apache.org/jira/browse/GEODE-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6947. - Resolution: Fixed Fix Version/s: 1.10.0 > geode-managment should create its own set of configuration objects for > PdxConfiguration > > > Key: GEODE-6947 > URL: https://issues.apache.org/jira/browse/GEODE-6947 > Project: Geode > Issue Type: Sub-task > Components: management >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.10.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > PdxConfiguration > only add the supported attributes > modify the implementation of ConfigurationManager to do the bridging between > the configuration objects and xml domain objects -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (GEODE-7002) Remove gemfire.enable-experimental-cluster-management-service feature flag
[ https://issues.apache.org/jira/browse/GEODE-7002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7002. Resolution: Fixed Fix Version/s: 1.10.0 > Remove gemfire.enable-experimental-cluster-management-service feature flag > -- > > Key: GEODE-7002 > URL: https://issues.apache.org/jira/browse/GEODE-7002 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Fix For: 1.10.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > Use a geode property: enable-management-rest-service > and change /v2 to /experimental -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (GEODE-7008) Function execution by ID does not properly handle bucket filters
[ https://issues.apache.org/jira/browse/GEODE-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-7008: --- Assignee: Jacob S. Barrett > Function execution by ID does not properly handle bucket filters > > > Key: GEODE-7008 > URL: https://issues.apache.org/jira/browse/GEODE-7008 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > Function execution by ID does not handle bucket filters consistent with > function execution by object. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (GEODE-7008) Function execution by ID does not properly handle bucket filters
Jacob S. Barrett created GEODE-7008: --- Summary: Function execution by ID does not properly handle bucket filters Key: GEODE-7008 URL: https://issues.apache.org/jira/browse/GEODE-7008 Project: Geode Issue Type: Bug Components: functions Reporter: Jacob S. Barrett Function execution by ID does not handle bucket filters consistent with function execution by object. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (GEODE-7007) Alter gfsh put docs to state prohibition on PDX objects
[
https://issues.apache.org/jira/browse/GEODE-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller resolved GEODE-7007.
Resolution: Fixed
Fix Version/s: 1.10.0
> Alter gfsh put docs to state prohibition on PDX objects
> ---
>
> Key: GEODE-7007
> URL: https://issues.apache.org/jira/browse/GEODE-7007
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> You cannot use PDX objects with puts in gfsh.
> Example of a put command that will not work:
> gfsh>put --region=/CashflowGroupMap --key="Closure Margin"
> --value="('cashFlowType':'Closure Margin',
> 'cashFlowTypeGroup':'CMAR','activeIndicator':'A',
> 'updateDateTime':'2013-06-06 05:37:00.0')"
> --value-class=org.apache.geode.pdx.internal.PdxInstanceImpl
>
> Add this restriction in the docs. A good place to add it is in the gfsh
> command reference page.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (GEODE-7002) Remove gemfire.enable-experimental-cluster-management-service feature flag
[ https://issues.apache.org/jira/browse/GEODE-7002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891325#comment-16891325 ] ASF subversion and git services commented on GEODE-7002: Commit f54e0ded1e1e4a8b29203d46f278cf293db6459d in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f54e0de ] GEODE-7002: use enable-management-rest-service property to enable/disable CMS (#3827) * change /v2 to /experimental > Remove gemfire.enable-experimental-cluster-management-service feature flag > -- > > Key: GEODE-7002 > URL: https://issues.apache.org/jira/browse/GEODE-7002 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Time Spent: 2h 40m > Remaining Estimate: 0h > > Use a geode property: enable-management-rest-service > and change /v2 to /experimental -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-7007) Alter gfsh put docs to state prohibition on PDX objects
[
https://issues.apache.org/jira/browse/GEODE-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891309#comment-16891309
]
ASF subversion and git services commented on GEODE-7007:
Commit 152418750c4f1b6d5c10ddbe64b641a584da029a in geode's branch
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1524187 ]
GEODE-7007: Alter gfsh put docs to prohibit PDX type (#3833)
- removed a duplicate sentence
- improved the formatting of table items to not split hyphens from the start
of option names
> Alter gfsh put docs to state prohibition on PDX objects
> ---
>
> Key: GEODE-7007
> URL: https://issues.apache.org/jira/browse/GEODE-7007
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> You cannot use PDX objects with puts in gfsh.
> Example of a put command that will not work:
> gfsh>put --region=/CashflowGroupMap --key="Closure Margin"
> --value="('cashFlowType':'Closure Margin',
> 'cashFlowTypeGroup':'CMAR','activeIndicator':'A',
> 'updateDateTime':'2013-06-06 05:37:00.0')"
> --value-class=org.apache.geode.pdx.internal.PdxInstanceImpl
>
> Add this restriction in the docs. A good place to add it is in the gfsh
> command reference page.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (GEODE-6999) NPE When Using disk-usage-warning-percentage property
[
https://issues.apache.org/jira/browse/GEODE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella resolved GEODE-6999.
-
Resolution: Fixed
Fix Version/s: 1.10.0
> NPE When Using disk-usage-warning-percentage property
> -
>
> Key: GEODE-6999
> URL: https://issues.apache.org/jira/browse/GEODE-6999
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Parsing the {{cache.xml}} or {{cluster.xml}} file causes the startup to fail
> with a {{NullPointerException}}:
> {noformat}
> While parsing XML
> , caused by java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1408)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1243)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:219)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:171)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParserJUnitTest.cacheXmlParserShouldCorrectlyHandleDiskUsageWarningPercentage(CacheXmlParserJUnitTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.NullPointerException
> at
> sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1838)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.parseFloat(CacheXmlParser.java:314)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.startDiskStore(CacheXmlParser.java:1019)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.startElement(CacheXmlParser.java:2664)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser$DefaultHandlerDelegate.startElement(CacheXmlParser.java:3431)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
> Source)
> at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
> Source)
> at
>
[jira] [Commented] (GEODE-6999) NPE When Using disk-usage-warning-percentage property
[
https://issues.apache.org/jira/browse/GEODE-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891256#comment-16891256
]
ASF subversion and git services commented on GEODE-6999:
Commit 8718171b749552709876fa3f5cd74cdc1851941c in geode's branch
refs/heads/develop from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8718171 ]
GEODE-6999: Fix XML attribute parsing (#3823)
- Fixed parsing of the 'attribute disk-usage-warning-percentage'
attribute.
> NPE When Using disk-usage-warning-percentage property
> -
>
> Key: GEODE-6999
> URL: https://issues.apache.org/jira/browse/GEODE-6999
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: GeodeCommons
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Parsing the {{cache.xml}} or {{cluster.xml}} file causes the startup to fail
> with a {{NullPointerException}}:
> {noformat}
> While parsing XML
> , caused by java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initializeDeclarativeCache(GemFireCacheImpl.java:1408)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1243)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:219)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:171)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParserJUnitTest.cacheXmlParserShouldCorrectlyHandleDiskUsageWarningPercentage(CacheXmlParserJUnitTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.NullPointerException
> at
> sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1838)
> at sun.misc.FloatingDecimal.parseFloat(FloatingDecimal.java:122)
> at java.lang.Float.parseFloat(Float.java:451)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.parseFloat(CacheXmlParser.java:314)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.startDiskStore(CacheXmlParser.java:1019)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser.startElement(CacheXmlParser.java:2664)
> at
> org.apache.geode.internal.cache.xmlcache.CacheXmlParser$DefaultHandlerDelegate.startElement(CacheXmlParser.java:3431)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
> Source)
> at
[jira] [Comment Edited] (GEODE-7003) CI failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingRegisterTranxConnection failed with java.sql.SQLNonTransientConnectionException: No cu
[
https://issues.apache.org/jira/browse/GEODE-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891227#comment-16891227
]
Aaron Lindsey edited comment on GEODE-7003 at 7/23/19 5:26 PM:
---
There is a race condition within the test. When the test calls
dataSource.getConnection(), that method will throw an (expected) exception and
expire the connection from the connection pool. There is a background thread
which goes through all the expired connections and calls Connection.close(). If
this background thread calls close() while the main thread is in the middle of
calling BrokeredConnection.isClosed(), the method isClosed() can throw a
SQLNonTransientConnectionException.
was (Author: aaronlindsey):
There is a race condition within the test. When the test calls
dataSource.getConnection(), that method will throw an (expected) exception and
expire the connection from the connection pool. There is a background thread
which goes through all the expired connections and calls Connection.close(). If
this background thread calls close() while the main thread is in the middle of
calling BrokeredConnection.isClosed(), the method isClosed() will throw a
SQLNonTransientConnectionException.
> CI failure:
> GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingRegisterTranxConnection
> failed with java.sql.SQLNonTransientConnectionException: No current
> connection.
>
>
> Key: GEODE-7003
> URL: https://issues.apache.org/jira/browse/GEODE-7003
> Project: Geode
> Issue Type: Bug
>Reporter: Aaron Lindsey
>Priority: Major
>
> Failed on Windows JDK 8 run on 7/22/19:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK8/builds/147]
> Archive results:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0468/test-results/integrationTest/1563834111/]
> Stack trace:
> {{org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest
> > testExceptionHandlingRegisterTranxConnection FAILED}}
> {{java.sql.SQLNonTransientConnectionException: No current connection.}}
> {{at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)}}
> {{at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)}}
> {{at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)}}
> {{at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)}}
> {{at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown
> Source)}}
> {{at org.apache.derby.jdbc.EmbedPooledConnection.checkActive(Unknown
> Source)}}
> {{at
> org.apache.derby.jdbc.EmbedPooledConnection.getRealConnection(Unknown
> Source)}}
> {{at
> org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)}}
> {{at
> org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown
> Source)}}
> {{at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown
> Source)}}
> {{at
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.lambda$testExceptionHandlingRegisterTranxConnection$1(GemFireTransactionDataSourceIntegrationTest.java:103)}}
> {{Caused by:}}
> {{ERROR 08003: No current connection.}}
> {{at
> org.apache.derby.iapi.error.StandardException.newException(Unknown Source)}}
> {{at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown
> Source)}}
> {{... 11 more}}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (GEODE-7003) CI failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingRegisterTranxConnection failed with java.sql.SQLNonTransientConnectionException: No current
[
https://issues.apache.org/jira/browse/GEODE-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891227#comment-16891227
]
Aaron Lindsey commented on GEODE-7003:
--
There is a race condition within the test. When the test calls
dataSource.getConnection(), that method will throw an (expected) exception and
expire the connection from the connection pool. There is a background thread
which goes through all the expired connections and calls Connection.close(). If
this background thread calls close() while the main thread is in the middle of
calling BrokeredConnection.isClosed(), the method isClosed() will throw a
SQLNonTransientConnectionException.
> CI failure:
> GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingRegisterTranxConnection
> failed with java.sql.SQLNonTransientConnectionException: No current
> connection.
>
>
> Key: GEODE-7003
> URL: https://issues.apache.org/jira/browse/GEODE-7003
> Project: Geode
> Issue Type: Bug
>Reporter: Aaron Lindsey
>Priority: Major
>
> Failed on Windows JDK 8 run on 7/22/19:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK8/builds/147]
> Archive results:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0468/test-results/integrationTest/1563834111/]
> Stack trace:
> {{org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest
> > testExceptionHandlingRegisterTranxConnection FAILED}}
> {{java.sql.SQLNonTransientConnectionException: No current connection.}}
> {{at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)}}
> {{at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)}}
> {{at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)}}
> {{at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)}}
> {{at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown
> Source)}}
> {{at org.apache.derby.jdbc.EmbedPooledConnection.checkActive(Unknown
> Source)}}
> {{at
> org.apache.derby.jdbc.EmbedPooledConnection.getRealConnection(Unknown
> Source)}}
> {{at
> org.apache.derby.jdbc.EmbedXAConnection.getRealConnection(Unknown Source)}}
> {{at
> org.apache.derby.iapi.jdbc.BrokeredConnection.getRealConnection(Unknown
> Source)}}
> {{at org.apache.derby.iapi.jdbc.BrokeredConnection.isClosed(Unknown
> Source)}}
> {{at
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.lambda$testExceptionHandlingRegisterTranxConnection$1(GemFireTransactionDataSourceIntegrationTest.java:103)}}
> {{Caused by:}}
> {{ERROR 08003: No current connection.}}
> {{at
> org.apache.derby.iapi.error.StandardException.newException(Unknown Source)}}
> {{at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown
> Source)}}
> {{... 11 more}}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (GEODE-7007) Alter gfsh put docs to state prohibition on PDX objects
[
https://issues.apache.org/jira/browse/GEODE-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller reassigned GEODE-7007:
--
Assignee: Karen Smoler Miller
> Alter gfsh put docs to state prohibition on PDX objects
> ---
>
> Key: GEODE-7007
> URL: https://issues.apache.org/jira/browse/GEODE-7007
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> You cannot use PDX objects with puts in gfsh.
> Example of a put command that will not work:
> gfsh>put --region=/CashflowGroupMap --key="Closure Margin"
> --value="('cashFlowType':'Closure Margin',
> 'cashFlowTypeGroup':'CMAR','activeIndicator':'A',
> 'updateDateTime':'2013-06-06 05:37:00.0')"
> --value-class=org.apache.geode.pdx.internal.PdxInstanceImpl
>
> Add this restriction in the docs. A good place to add it is in the gfsh
> command reference page.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (GEODE-7007) Alter gfsh put docs to state prohibition on PDX objects
Karen Smoler Miller created GEODE-7007:
--
Summary: Alter gfsh put docs to state prohibition on PDX objects
Key: GEODE-7007
URL: https://issues.apache.org/jira/browse/GEODE-7007
Project: Geode
Issue Type: Improvement
Components: docs
Reporter: Karen Smoler Miller
You cannot use PDX objects with puts in gfsh.
Example of a put command that will not work:
gfsh>put --region=/CashflowGroupMap --key="Closure Margin"
--value="('cashFlowType':'Closure Margin',
'cashFlowTypeGroup':'CMAR','activeIndicator':'A', 'updateDateTime':'2013-06-06
05:37:00.0')" --value-class=org.apache.geode.pdx.internal.PdxInstanceImpl
Add this restriction in the docs. A good place to add it is in the gfsh command
reference page.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (GEODE-7001) Add a gauge to track region entry count
[ https://issues.apache.org/jira/browse/GEODE-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891204#comment-16891204 ] ASF subversion and git services commented on GEODE-7001: Commit 4e8ce22292c399f2754404eb473bc32dfad4d451 in geode's branch refs/heads/GEODE-7001-region-entry-count from Michael Oleske [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e8ce22 ] GEODE-7001: Use LongAdder instead of AtomicLong Co-authored-by: Michael Oleske Co-authored-by: Dale Emery > Add a gauge to track region entry count > --- > > Key: GEODE-7001 > URL: https://issues.apache.org/jira/browse/GEODE-7001 > Project: Geode > Issue Type: New Feature > Components: statistics >Reporter: Dale Emery >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Add a gauge to RegionPerfStats to track the entry count. > As part of understanding system state and health, knowing what regions exist > with how much data in them is an often asked question of a data store. The > underlying metric is the CachePerfStats.entries value. This is only a piece > of the information that customers need as it does not expose the region or > region type to the users which is critical to understanding how things are > setup. > Scenario: REPLICATE region > Given a cluster with the following servers: > - server1 > - server2 > And the cluster has a "REPLICATE" region named X > And the user has put 10 entries with distinct keys into region X > Then server1's meter registry has the following meter > - meter name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = REPLICATE > - value: 10 > Then server2's meter registry has the following meter > - name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = REPLICATE > - value: 10 > Scenario: PARTITION region with no redundancy > Given a cluster with the following servers: > - server1 > - server2 > And the cluster has a "PARTITION" region named X > And the user has put 10 entries with distinct keys into region X > Then server1's meter registry has the following meter > - meter name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = PARTITION > - value: between 0 and 10 > Then server2's meter registry has the following meter > - name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = PARTITION > - value: between 0 and 10 > And the values of those meters add up to 10 > Scenario: PARTITIONED REDUNDANT > Given a cluster with the following servers: > - server1 > - server2 > - server3 > And the cluster has a "PARTITION_REDUNDANT" region named X > And the redundancy level is set to 1 copy (2 total copies of each key should > exist) > And the user has put 10 entries with distinct keys into region X > Then server1's meter registry has the following meter > - meter name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = PARTITION > - value: between 0 and 10 > Then server2's meter registry has the following meter > - name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = PARTITION > - value: between 0 and 10 > Then server3's meter registry has the following meter > - name: member.region.entries > - tag: region_name = X > - tag: > - tag: data_policy = PARTITION > - value: between 0 and 10 > And the values of those meters add up to 20 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-4263) CI Failure: ResourceManagerWithQueryMonitorDUnitTest. testRMAndTimeoutSet
[
https://issues.apache.org/jira/browse/GEODE-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891198#comment-16891198
]
Aaron Lindsey commented on GEODE-4263:
--
Failed again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/907]
{code:java}
org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest >
testRMButDisabledQueryMonitorForLowMemAndNoTimeoutSet FAILED
java.lang.AssertionError: queryExecution.getResult() threw Exception
java.lang.AssertionError: An exception occurred during asynchronous invocation.
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doTestCriticalHeapAndQueryTimeout(ResourceManagerWithQueryMonitorDUnitTest.java:848)
at
org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doCriticalMemoryHitTest(ResourceManagerWithQueryMonitorDUnitTest.java:321)
at
org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.testRMButDisabledQueryMonitorForLowMemAndNoTimeoutSet(ResourceManagerWithQueryMonitorDUnitTest.java:165)
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 1546
[fatal 2019/07/22 23:54:50.904 GMT tid=1561] Server connection from
[identity(172.17.0.9(245:loner):36934:30d91b1c,connection=1; port=36938] :
Unexpected Error on server
java.lang.AssertionError: query was never unlatched
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest$PauseTestHook.doTestHook(ResourceManagerWithQueryMonitorDUnitTest.java:1306)
at
org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:428)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:265)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:197)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQueryUsingParams(BaseCommandQuery.java:122)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQuery(BaseCommandQuery.java:68)
at
org.apache.geode.internal.cache.tier.sockets.command.Query.cmdExecute(Query.java:94)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:848)
at
org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1212)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:665)
at
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
at java.lang.Thread.run(Thread.java:748)
{code}
> CI Failure: ResourceManagerWithQueryMonitorDUnitTest. testRMAndTimeoutSet
> -
>
> Key: GEODE-4263
> URL: https://issues.apache.org/jira/browse/GEODE-4263
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: nabarun
>Priority: Major
>
> {noformat}
> java.lang.AssertionError: queryExecution.getResult() threw Exception
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doTestCriticalHeapAndQueryTimeout(ResourceManagerWithQueryMonitorDUnitTest.java:738)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doCriticalMemoryHitTest(ResourceManagerWithQueryMonitorDUnitTest.java:321)
> at
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.testRMAndTimeoutSet(ResourceManagerWithQueryMonitorDUnitTest.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
>
[jira] [Created] (GEODE-7006) Function execution by ID does not have fix for GEODE-6016
Jacob S. Barrett created GEODE-7006: --- Summary: Function execution by ID does not have fix for GEODE-6016 Key: GEODE-7006 URL: https://issues.apache.org/jira/browse/GEODE-7006 Project: Geode Issue Type: Bug Components: functions, transactions Reporter: Jacob S. Barrett Function execution by function ID did not get the fix for GEODE-6016 that function execution by function object did. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (GEODE-7006) Function execution by ID does not have fix for GEODE-6016
[ https://issues.apache.org/jira/browse/GEODE-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-7006: --- Assignee: Jacob S. Barrett > Function execution by ID does not have fix for GEODE-6016 > - > > Key: GEODE-7006 > URL: https://issues.apache.org/jira/browse/GEODE-7006 > Project: Geode > Issue Type: Bug > Components: functions, transactions >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > Function execution by function ID did not get the fix for GEODE-6016 that > function execution by function object did. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-6883) Move the membership code into a separate gradle sub-project
[ https://issues.apache.org/jira/browse/GEODE-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891105#comment-16891105 ] ASF subversion and git services commented on GEODE-6883: Commit 196adda940db7ea1a629eb6c62902500cfcafefe in geode's branch refs/heads/feature/remove-InternalDistributedMember-GEODE-6883 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=196adda ] GEODE-6883 Move the membership code into a separate gradle sub-project This PR narrows the effort of GEODE-6883 to focus only on the "gms" package and its subpackages. Other membership classes in org.apache.geode.distributed.internal.membership are Geode interfaces, adapters and factories. Classes in "gms" are membership classes/interfaces that should not refer to anything outside of "gms" (though they still do). This PR is otherwise focused on removing references to InternalDistributedMember and DistributionMessage from "gms". GMS classes only refer to GMSMember GMS classes use GMSMembershipView. NetView is now an interface GMS classes do not refer to DistributionMessage. JGroupsMessenger expects GMSMessage instances. Geode messages to be sent over UDP are wrapped in a GMSMessageAdapter. "gms" messages extend AbstractGMSMessage which implements GMSMessage GMSMembershipManager has an inner class that implements the GMS Manager interface and is now in the "adapter" package GMSMembershipManager translates GMSMembershipView into a MembershipView for the rest of Geode to use (this is the old NetView class) GMS instantiation allows us to inject the Manager into the new Services instance. Other adapter classes have been added to translate between Geode and GMS. GMSUtil has new methods for marshalling/unmarshalling InternalDistributedMember instances for backward-compatibility. GMSMember now has the same on-wire form as InternalDistributedMember. This allows the GMS classes to deserialize a message from a pre-1.10 member whose code writes InternalDistributedMembers when serializing something like a JoinRequest. > Move the membership code into a separate gradle sub-project > --- > > Key: GEODE-6883 > URL: https://issues.apache.org/jira/browse/GEODE-6883 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Priority: Major > Time Spent: 3.5h > Remaining Estimate: 0h > > In order to make membership more testable, we want to move the membership > code out of geode-core and into a new geode-membership gradle sub-project. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-3718) The InternalResourceManager fails to shutdown if a redundancy recovery task is scheduled but hasn't fired yet
[
https://issues.apache.org/jira/browse/GEODE-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891104#comment-16891104
]
ASF subversion and git services commented on GEODE-3718:
Commit 336c1a288641a0587fbbfa38a5818ca9382e25e4 in geode's branch
refs/heads/feature/remove-InternalDistributedMember-GEODE-6883 from Jason Huynh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=336c1a2 ]
GEODE-3718: shutdownNow should also interrupt non executing runnables (#3821)
> The InternalResourceManager fails to shutdown if a redundancy recovery task
> is scheduled but hasn't fired yet
> -
>
> Key: GEODE-3718
> URL: https://issues.apache.org/jira/browse/GEODE-3718
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Barry Oglesby
>Assignee: Mario Ivanac
>Priority: Major
> Labels: needs-review, pull-request-available, recovery
> Time Spent: 2h
> Remaining Estimate: 0h
>
> This happens with recovery-delay or startup-recovery-delay > 0.
> The thread gets stuck here:
> {noformat}
> "Thread-20" #133 prio=10 os_prio=31 tid=0x7fa85b886000 nid=0x890b waiting
> on condition [0x70001269e000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0007bc408900> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> at
> java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1465)
> at
> org.apache.geode.internal.cache.control.InternalResourceManager.stopExecutor(InternalResourceManager.java:375)
> at
> org.apache.geode.internal.cache.control.InternalResourceManager.close(InternalResourceManager.java:187)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2161)
> - locked <0x0007bc0bc520> (a java.lang.Class for
> org.apache.geode.internal.cache.GemFireCacheImpl)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1367)
> - locked <0x0007bc0bc520> (a java.lang.Class for
> org.apache.geode.internal.cache.GemFireCacheImpl)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1017)
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge$1.run(MemberMBeanBridge.java:986)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> The InternalResourceManager is waiting for the termination of its
> scheduledExecutor.
> The PRHARedundancyProvider initializes its recoveryExecutor using the
> InternalResourceManager's scheduledExecutor:
> {noformat}
> recoveryExecutor = new OneTaskOnlyExecutor(resourceManager.getExecutor(),
> new OneTaskOnlyExecutor.ConflatedTaskListener() {
> public void taskDropped() {
> InternalResourceManager.getResourceObserver().recoveryConflated(region);
> }
> });
> {noformat}
> The scheduleRedundancyRecovery method schedules a RecoveryRunnable if
> necessary.
> If that task hasn't fired yet, the InternalResourceManager doesn't close, and
> the JVM stays up.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (GEODE-6883) Move the membership code into a separate gradle sub-project
[ https://issues.apache.org/jira/browse/GEODE-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891106#comment-16891106 ] ASF subversion and git services commented on GEODE-6883: Commit 196adda940db7ea1a629eb6c62902500cfcafefe in geode's branch refs/heads/feature/remove-InternalDistributedMember-GEODE-6883 from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=196adda ] GEODE-6883 Move the membership code into a separate gradle sub-project This PR narrows the effort of GEODE-6883 to focus only on the "gms" package and its subpackages. Other membership classes in org.apache.geode.distributed.internal.membership are Geode interfaces, adapters and factories. Classes in "gms" are membership classes/interfaces that should not refer to anything outside of "gms" (though they still do). This PR is otherwise focused on removing references to InternalDistributedMember and DistributionMessage from "gms". GMS classes only refer to GMSMember GMS classes use GMSMembershipView. NetView is now an interface GMS classes do not refer to DistributionMessage. JGroupsMessenger expects GMSMessage instances. Geode messages to be sent over UDP are wrapped in a GMSMessageAdapter. "gms" messages extend AbstractGMSMessage which implements GMSMessage GMSMembershipManager has an inner class that implements the GMS Manager interface and is now in the "adapter" package GMSMembershipManager translates GMSMembershipView into a MembershipView for the rest of Geode to use (this is the old NetView class) GMS instantiation allows us to inject the Manager into the new Services instance. Other adapter classes have been added to translate between Geode and GMS. GMSUtil has new methods for marshalling/unmarshalling InternalDistributedMember instances for backward-compatibility. GMSMember now has the same on-wire form as InternalDistributedMember. This allows the GMS classes to deserialize a message from a pre-1.10 member whose code writes InternalDistributedMembers when serializing something like a JoinRequest. > Move the membership code into a separate gradle sub-project > --- > > Key: GEODE-6883 > URL: https://issues.apache.org/jira/browse/GEODE-6883 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Priority: Major > Time Spent: 3.5h > Remaining Estimate: 0h > > In order to make membership more testable, we want to move the membership > code out of geode-core and into a new geode-membership gradle sub-project. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-7005) CI failure: LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
[
https://issues.apache.org/jira/browse/GEODE-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891068#comment-16891068
]
Juan José Ramos Cassella commented on GEODE-7005:
-
There's a race condition within the test.
We search for a daemon thread with *ID* {{LocatorsDistributorThread}} and wait
until it finishes to start the assertions, but the thread might have not
started yet at the time we search for it and, as such, the assertions fail.
> CI failure:
> LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
> ---
>
> Key: GEODE-7005
> URL: https://issues.apache.org/jira/browse/GEODE-7005
> Project: Geode
> Issue Type: Bug
>Reporter: Aaron Lindsey
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: GeodeCommons
>
> Failing job:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK8/builds/903]
> Archived results:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0469/test-results/test/1563836162/]
> Stack trace:
> {{org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest
> >
> locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
> FAILED}}
> {{Wanted but not invoked:}}
> {{tcpClient.requestToServer(}}
> {{localhost/127.0.0.1:10103,}}
> {{LocatorJoinMessage\{distributedSystemId=1 locators=localhost[10102]
> Source Locator : localhost[10101]},}}
> {{5000,}}
> {{false}}
> {{);}}
> {{-> at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.verifyMessagesSentBothWays(LocatorMembershipListenerTest.java:85)}}
> {{Actually, there were zero interactions with this mock.}}
> {{at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.verifyMessagesSentBothWays(LocatorMembershipListenerTest.java:85)}}
> {{at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators(LocatorMembershipListenerTest.java:253)}}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (GEODE-7005) CI failure: LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
[
https://issues.apache.org/jira/browse/GEODE-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella reassigned GEODE-7005:
---
Assignee: Juan José Ramos Cassella
> CI failure:
> LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
> ---
>
> Key: GEODE-7005
> URL: https://issues.apache.org/jira/browse/GEODE-7005
> Project: Geode
> Issue Type: Bug
>Reporter: Aaron Lindsey
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: GeodeCommons
>
> Failing job:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK8/builds/903]
> Archived results:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0469/test-results/test/1563836162/]
> Stack trace:
> {{org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest
> >
> locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
> FAILED}}
> {{Wanted but not invoked:}}
> {{tcpClient.requestToServer(}}
> {{localhost/127.0.0.1:10103,}}
> {{LocatorJoinMessage\{distributedSystemId=1 locators=localhost[10102]
> Source Locator : localhost[10101]},}}
> {{5000,}}
> {{false}}
> {{);}}
> {{-> at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.verifyMessagesSentBothWays(LocatorMembershipListenerTest.java:85)}}
> {{Actually, there were zero interactions with this mock.}}
> {{at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.verifyMessagesSentBothWays(LocatorMembershipListenerTest.java:85)}}
> {{at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators(LocatorMembershipListenerTest.java:253)}}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (GEODE-7005) CI failure: LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
[
https://issues.apache.org/jira/browse/GEODE-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella updated GEODE-7005:
Labels: GeodeCommons (was: )
> CI failure:
> LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
> ---
>
> Key: GEODE-7005
> URL: https://issues.apache.org/jira/browse/GEODE-7005
> Project: Geode
> Issue Type: Bug
>Reporter: Aaron Lindsey
>Priority: Major
> Labels: GeodeCommons
>
> Failing job:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK8/builds/903]
> Archived results:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0469/test-results/test/1563836162/]
> Stack trace:
> {{org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest
> >
> locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators
> FAILED}}
> {{Wanted but not invoked:}}
> {{tcpClient.requestToServer(}}
> {{localhost/127.0.0.1:10103,}}
> {{LocatorJoinMessage\{distributedSystemId=1 locators=localhost[10102]
> Source Locator : localhost[10101]},}}
> {{5000,}}
> {{false}}
> {{);}}
> {{-> at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.verifyMessagesSentBothWays(LocatorMembershipListenerTest.java:85)}}
> {{Actually, there were zero interactions with this mock.}}
> {{at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.verifyMessagesSentBothWays(LocatorMembershipListenerTest.java:85)}}
> {{at
> org.apache.geode.cache.client.internal.locator.wan.LocatorMembershipListenerTest.locatorJoinedShouldNotifyEveryKnownLocatorAboutTheJoiningLocatorAndJoiningLocatorAboutAllTheKnownLocators(LocatorMembershipListenerTest.java:253)}}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (GEODE-6954) GatewaySenderMXBean wrongly reports state
[
https://issues.apache.org/jira/browse/GEODE-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Kevo updated GEODE-6954:
--
Labels: needs-review pull-request-available (was: )
> GatewaySenderMXBean wrongly reports state
> -
>
> Key: GEODE-6954
> URL: https://issues.apache.org/jira/browse/GEODE-6954
> Project: Geode
> Issue Type: Bug
> Components: jmx, wan
>Reporter: Mario Kevo
>Assignee: Mario Kevo
>Priority: Major
> Labels: needs-review, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After creating gateways senders and receivers between two geode clusters
> replications is established. After restart gateway receiver, _list gateways_
> command shows that everything is connected and replication works.
> But when checking gateway sender state over JMX with GatewaySenderMXBean and
> checking _isConnected()_ I got _false,_ but should be _true_ as it is
> connected.
> Steps to reproduce issue:
> # create two sites
> ([geode-examples/wan|https://github.com/apache/geode-examples/tree/master/wan])
> # check GW sender stats with jconsole (Connected = *true*)
> # stop GW receiver on the remote site (Connected = *false*)
> # put some entry (it will be in the queue waiting for connection)
> # start GW receiver on the remote site (Connected = *false*)
> # replication is established, the event is processed to the remote site
> (Connected = *{color:#d04437}false{color}*, should be
> {color:#8eb021}*true*{color})
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
