[jira] [Created] (GEODE-10339) The server fails to start because the .crf of the .drf file is missing
Jakov Varenina created GEODE-10339:
--
Summary: The server fails to start because the .crf of the .drf
file is missing
Key: GEODE-10339
URL: https://issues.apache.org/jira/browse/GEODE-10339
Project: Geode
Issue Type: Bug
Reporter: Jakov Varenina
{color:#0e101a}The server fail with following:{color}
{color:#0e101a}{"timestamp":"2022-05-16T08:25:35.708Z","severity":"error","message":"Cache
initialization for GemFireCache[id = 776315735; isClosing = false;
isShutDownAll = false; created = Mon May 16 08:25:33 UTC 2022; server = false;
copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
java.lang.IllegalStateException: {*}The following required files could not be
found: *.crf files with these ids:
[33].{*}","metadata":\{"function":"KVDB"},"version":"1.1.0","service_id":"eric-udr-kvdb-ag","extra_data":\{"thread_info":{"thread_name":"main","thread_id":"1"},"e":\{"exception":""}}}{color}
{color:#0e101a}As a last compaction step, the server deletes the compacted .crf
file. The deletion is done in the following way:{color}
# {color:#0e101a}Write delete operation (delete ".crf" file) in the ".if"
file. {color}
# {color:#0e101a}Delete .crf file{color}
{color:#0e101a}The problem with server startup happens in the following
scenario:{color}
# {color:#0e101a}The server writes the delete" operation (for .crf file) in
the ".if" file. The write is not immediately flushed to the ".if" file, but it
goes to the async write buffer.{color}
# {color:#0e101a}The server deletes the ".crf" file.{color}
# {color:#0e101a}The forceful restart happens before the async write buffer is
flushed to the ".if" file. This scenario leaves the ".if" file not updated, and
therefore server startup fails later on.{color}
{color:#0e101a}To avoid the above issue, we can use the existing parameter in a
geode that forces the server to write synchronously to the ".if" file:{color}
{code:java}
--J=-Dgemfire.syncMetaDataWrites=true
{code}
{color:#0e101a}This parameter is not mentioned anywhere in the documentation.
So it would be good to add it to the following document:{color}
{color:#0e101a}https://geode.apache.org/docs/guide/114/managing/disk_storage/managing_disk_buffer_flushes.html{color}
{color:#0e101a}Changing this parameter's default value to true would also be
good. {color}
{color:#0e101a}This parameter should not affect performance as the ".if" file
is not updated frequently.{color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10339) The server fails to start because the .crf of the .drf file is missing
[
https://issues.apache.org/jira/browse/GEODE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10339:
--
Labels: needsTriage (was: )
> The server fails to start because the .crf of the .drf file is missing
> --
>
> Key: GEODE-10339
> URL: https://issues.apache.org/jira/browse/GEODE-10339
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Priority: Major
> Labels: needsTriage
>
> {color:#0e101a}The server fail with following:{color}
>
> {color:#0e101a}{"timestamp":"2022-05-16T08:25:35.708Z","severity":"error","message":"Cache
> initialization for GemFireCache[id = 776315735; isClosing = false;
> isShutDownAll = false; created = Mon May 16 08:25:33 UTC 2022; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> java.lang.IllegalStateException: {*}The following required files could not be
> found: *.crf files with these ids:
> [33].{*}","metadata":\{"function":"KVDB"},"version":"1.1.0","service_id":"eric-udr-kvdb-ag","extra_data":\{"thread_info":{"thread_name":"main","thread_id":"1"},"e":\{"exception":""}}}{color}
>
> {color:#0e101a}As a last compaction step, the server deletes the compacted
> .crf file. The deletion is done in the following way:{color}
> # {color:#0e101a}Write delete operation (delete ".crf" file) in the ".if"
> file. {color}
> # {color:#0e101a}Delete .crf file{color}
>
> {color:#0e101a}The problem with server startup happens in the following
> scenario:{color}
> # {color:#0e101a}The server writes the delete" operation (for .crf file) in
> the ".if" file. The write is not immediately flushed to the ".if" file, but
> it goes to the async write buffer.{color}
> # {color:#0e101a}The server deletes the ".crf" file.{color}
> # {color:#0e101a}The forceful restart happens before the async write buffer
> is flushed to the ".if" file. This scenario leaves the ".if" file not
> updated, and therefore server startup fails later on.{color}
>
> {color:#0e101a}To avoid the above issue, we can use the existing parameter in
> a geode that forces the server to write synchronously to the ".if"
> file:{color}
>
> {code:java}
> --J=-Dgemfire.syncMetaDataWrites=true
> {code}
>
>
> {color:#0e101a}This parameter is not mentioned anywhere in the documentation.
> So it would be good to add it to the following document:{color}
>
> {color:#0e101a}https://geode.apache.org/docs/guide/114/managing/disk_storage/managing_disk_buffer_flushes.html{color}
>
> {color:#0e101a}Changing this parameter's default value to true would also be
> good. {color}
> {color:#0e101a}This parameter should not affect performance as the ".if" file
> is not updated frequently.{color}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10339) The server fails to start because the .crf of the .drf file is missing
[
https://issues.apache.org/jira/browse/GEODE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakov Varenina updated GEODE-10339:
---
Description:
{color:#0e101a}The server fails with following:{color}
{code:java}
{"timestamp":"2022-05-16T08:25:35.708Z","severity":"error","message":"Cache
initialization for GemFireCache[id = 776315735; isClosing = false;
isShutDownAll = false; created = Mon May 16 08:25:33 UTC 2022; server = false;
copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
java.lang.IllegalStateException: The following required files could not be
found: *.crf files with these ids:
[33].","metadata":{"function":"KVDB"},"version":"1.1.0","service_id":"eric-udr-kvdb-ag","extra_data":{"thread_info":{"thread_name":"main","thread_id":"1"},"e":{"exception":""}}}
{code}
{color:#0e101a}As a last compaction step, the server deletes the compacted .crf
file. The deletion is done in the following way:{color}
# {color:#0e101a}Write delete operation (delete ".crf" file) in the ".if"
file. {color}
# {color:#0e101a}Delete .crf file{color}
{color:#0e101a}The problem with server startup happens in the following
scenario:{color}
# {color:#0e101a}The server writes the delete operation (for .crf file) in the
".if" file. The write is not immediately flushed to the ".if" file, but it goes
to the async write buffer.{color}
# {color:#0e101a}The server deletes the ".crf" file.{color}
# {color:#0e101a}The forceful restart happens before the async write buffer is
flushed to the ".if" file. This scenario leaves the ".if" file not updated, and
therefore server startup fails later on.{color}
{color:#0e101a}To avoid the above issue, we can use the existing parameter in a
geode that forces the server to write synchronously to the ".if" file:{color}
{code:java}
--J=-Dgemfire.syncMetaDataWrites=true
{code}
{color:#0e101a}This parameter is not mentioned anywhere in the documentation.
So it would be good to add it to the following document:{color}
{color:#0e101a}[https://geode.apache.org/docs/guide/114/managing/disk_storage/managing_disk_buffer_flushes.html]{color}
{color:#0e101a}Changing this parameter's default value to true would also be
good. {color}{color:#0e101a}This parameter should not affect performance as the
".if" file is not updated frequently.{color}
was:
{color:#0e101a}The server fail with following:{color}
{color:#0e101a}{"timestamp":"2022-05-16T08:25:35.708Z","severity":"error","message":"Cache
initialization for GemFireCache[id = 776315735; isClosing = false;
isShutDownAll = false; created = Mon May 16 08:25:33 UTC 2022; server = false;
copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
java.lang.IllegalStateException: {*}The following required files could not be
found: *.crf files with these ids:
[33].{*}","metadata":\{"function":"KVDB"},"version":"1.1.0","service_id":"eric-udr-kvdb-ag","extra_data":\{"thread_info":{"thread_name":"main","thread_id":"1"},"e":\{"exception":""}}}{color}
{color:#0e101a}As a last compaction step, the server deletes the compacted .crf
file. The deletion is done in the following way:{color}
# {color:#0e101a}Write delete operation (delete ".crf" file) in the ".if"
file. {color}
# {color:#0e101a}Delete .crf file{color}
{color:#0e101a}The problem with server startup happens in the following
scenario:{color}
# {color:#0e101a}The server writes the delete" operation (for .crf file) in
the ".if" file. The write is not immediately flushed to the ".if" file, but it
goes to the async write buffer.{color}
# {color:#0e101a}The server deletes the ".crf" file.{color}
# {color:#0e101a}The forceful restart happens before the async write buffer is
flushed to the ".if" file. This scenario leaves the ".if" file not updated, and
therefore server startup fails later on.{color}
{color:#0e101a}To avoid the above issue, we can use the existing parameter in a
geode that forces the server to write synchronously to the ".if" file:{color}
{code:java}
--J=-Dgemfire.syncMetaDataWrites=true
{code}
{color:#0e101a}This parameter is not mentioned anywhere in the documentation.
So it would be good to add it to the following document:{color}
{color:#0e101a}https://geode.apache.org/docs/guide/114/managing/disk_storage/managing_disk_buffer_flushes.html{color}
{color:#0e101a}Changing this parameter's default value to true would also be
good. {color}
{color:#0e101a}This parameter should not affect performance as the ".if" file
is not updated frequently.{color}
> The server fails to start because the .crf of the .drf file is missing
> --
>
> Key: GEODE-10339
> URL: https://issues.apache.org/jira/browse/GEODE-10339
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Prior
[jira] [Updated] (GEODE-10339) The server fails to start because the .crf or the .drf file is missing
[
https://issues.apache.org/jira/browse/GEODE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakov Varenina updated GEODE-10339:
---
Summary: The server fails to start because the .crf or the .drf file is
missing (was: The server fails to start because the .crf of the .drf file is
missing)
> The server fails to start because the .crf or the .drf file is missing
> --
>
> Key: GEODE-10339
> URL: https://issues.apache.org/jira/browse/GEODE-10339
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Priority: Major
> Labels: needsTriage
>
> {color:#0e101a}The server fails with following:{color}
> {code:java}
> {"timestamp":"2022-05-16T08:25:35.708Z","severity":"error","message":"Cache
> initialization for GemFireCache[id = 776315735; isClosing = false;
> isShutDownAll = false; created = Mon May 16 08:25:33 UTC 2022; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> java.lang.IllegalStateException: The following required files could not be
> found: *.crf files with these ids:
> [33].","metadata":{"function":"KVDB"},"version":"1.1.0","service_id":"eric-udr-kvdb-ag","extra_data":{"thread_info":{"thread_name":"main","thread_id":"1"},"e":{"exception":""}}}
> {code}
>
> {color:#0e101a}As a last compaction step, the server deletes the compacted
> .crf file. The deletion is done in the following way:{color}
> # {color:#0e101a}Write delete operation (delete ".crf" file) in the ".if"
> file. {color}
> # {color:#0e101a}Delete .crf file{color}
> {color:#0e101a}The problem with server startup happens in the following
> scenario:{color}
> # {color:#0e101a}The server writes the delete operation (for .crf file) in
> the ".if" file. The write is not immediately flushed to the ".if" file, but
> it goes to the async write buffer.{color}
> # {color:#0e101a}The server deletes the ".crf" file.{color}
> # {color:#0e101a}The forceful restart happens before the async write buffer
> is flushed to the ".if" file. This scenario leaves the ".if" file not
> updated, and therefore server startup fails later on.{color}
>
> {color:#0e101a}To avoid the above issue, we can use the existing parameter in
> a geode that forces the server to write synchronously to the ".if"
> file:{color}
> {code:java}
> --J=-Dgemfire.syncMetaDataWrites=true
> {code}
> {color:#0e101a}This parameter is not mentioned anywhere in the documentation.
> So it would be good to add it to the following document:{color}
> {color:#0e101a}[https://geode.apache.org/docs/guide/114/managing/disk_storage/managing_disk_buffer_flushes.html]{color}
>
> {color:#0e101a}Changing this parameter's default value to true would also be
> good. {color}{color:#0e101a}This parameter should not affect performance as
> the ".if" file is not updated frequently.{color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (GEODE-10338) LogWriterAppender keeps a InternalDistributedSystem alive after disconnect
[
https://issues.apache.org/jira/browse/GEODE-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakov Varenina reassigned GEODE-10338:
--
Assignee: Jakov Varenina
> LogWriterAppender keeps a InternalDistributedSystem alive after disconnect
> --
>
> Key: GEODE-10338
> URL: https://issues.apache.org/jira/browse/GEODE-10338
> Project: Geode
> Issue Type: Bug
> Components: logging
>Reporter: Darrel Schneider
>Assignee: Jakov Varenina
>Priority: Major
> Labels: blocks-1.16.0
>
> The LogWriterAppender has a "logWriter" field that can be a ManagerLogWriter.
> When stopSession is called on the appender, it closes the ManagerLogWriter's
> files but does not release its reference to it and the LogWriterAppender
> instance is kept around after disconnect. So this ends up keeping the
> InternalDistributedSystem alive.
> To fix this change LogWriterAppender.stopSession like so:
> {code:java}
> public synchronized void stopSession() {
> LOGGER.info("Stopping session in {}.", this);
> if (logWriter == null) {
> // we are probably already paused but make sure we are
> pause();
> return;
> }
> logWriter.shuttingDown();
> pause();
> logWriter.closingLogFile();
> logWriter = null;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10338) LogWriterAppender keeps a InternalDistributedSystem alive after disconnect
[
https://issues.apache.org/jira/browse/GEODE-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10338:
---
Labels: blocks-1.16.0 pull-request-available (was: blocks-1.16.0)
> LogWriterAppender keeps a InternalDistributedSystem alive after disconnect
> --
>
> Key: GEODE-10338
> URL: https://issues.apache.org/jira/browse/GEODE-10338
> Project: Geode
> Issue Type: Bug
> Components: logging
>Reporter: Darrel Schneider
>Assignee: Jakov Varenina
>Priority: Major
> Labels: blocks-1.16.0, pull-request-available
>
> The LogWriterAppender has a "logWriter" field that can be a ManagerLogWriter.
> When stopSession is called on the appender, it closes the ManagerLogWriter's
> files but does not release its reference to it and the LogWriterAppender
> instance is kept around after disconnect. So this ends up keeping the
> InternalDistributedSystem alive.
> To fix this change LogWriterAppender.stopSession like so:
> {code:java}
> public synchronized void stopSession() {
> LOGGER.info("Stopping session in {}.", this);
> if (logWriter == null) {
> // we are probably already paused but make sure we are
> pause();
> return;
> }
> logWriter.shuttingDown();
> pause();
> logWriter.closingLogFile();
> logWriter = null;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (GEODE-10340) Add new DiskStoreMXBean JMX metrics
Alberto Gomez created GEODE-10340: - Summary: Add new DiskStoreMXBean JMX metrics Key: GEODE-10340 URL: https://issues.apache.org/jira/browse/GEODE-10340 Project: Geode Issue Type: New Feature Components: persistence, statistics Reporter: Alberto Gomez In order to be able to visualize the progress of oplog recovery at server startup it would be nice that the recoveredEntryCreates, recoveredEntryUpdates and recoveredEntryDestroys DiskStore stats are published via JMX. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10340) Add new DiskStoreMXBean JMX metrics
[ https://issues.apache.org/jira/browse/GEODE-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10340: --- Labels: pull-request-available (was: ) > Add new DiskStoreMXBean JMX metrics > --- > > Key: GEODE-10340 > URL: https://issues.apache.org/jira/browse/GEODE-10340 > Project: Geode > Issue Type: New Feature > Components: persistence, statistics >Reporter: Alberto Gomez >Priority: Major > Labels: pull-request-available > > In order to be able to visualize the progress of oplog recovery at server > startup it would be nice that the recoveredEntryCreates, > recoveredEntryUpdates and recoveredEntryDestroys DiskStore stats are > published via JMX. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10339) The server fails to start because the .crf or the .drf file is missing
[
https://issues.apache.org/jira/browse/GEODE-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10339:
--
Labels: (was: needsTriage)
> The server fails to start because the .crf or the .drf file is missing
> --
>
> Key: GEODE-10339
> URL: https://issues.apache.org/jira/browse/GEODE-10339
> Project: Geode
> Issue Type: Bug
>Reporter: Jakov Varenina
>Priority: Major
>
> {color:#0e101a}The server fails with following:{color}
> {code:java}
> {"timestamp":"2022-05-16T08:25:35.708Z","severity":"error","message":"Cache
> initialization for GemFireCache[id = 776315735; isClosing = false;
> isShutDownAll = false; created = Mon May 16 08:25:33 UTC 2022; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> java.lang.IllegalStateException: The following required files could not be
> found: *.crf files with these ids:
> [33].","metadata":{"function":"KVDB"},"version":"1.1.0","service_id":"eric-udr-kvdb-ag","extra_data":{"thread_info":{"thread_name":"main","thread_id":"1"},"e":{"exception":""}}}
> {code}
>
> {color:#0e101a}As a last compaction step, the server deletes the compacted
> .crf file. The deletion is done in the following way:{color}
> # {color:#0e101a}Write delete operation (delete ".crf" file) in the ".if"
> file. {color}
> # {color:#0e101a}Delete .crf file{color}
> {color:#0e101a}The problem with server startup happens in the following
> scenario:{color}
> # {color:#0e101a}The server writes the delete operation (for .crf file) in
> the ".if" file. The write is not immediately flushed to the ".if" file, but
> it goes to the async write buffer.{color}
> # {color:#0e101a}The server deletes the ".crf" file.{color}
> # {color:#0e101a}The forceful restart happens before the async write buffer
> is flushed to the ".if" file. This scenario leaves the ".if" file not
> updated, and therefore server startup fails later on.{color}
>
> {color:#0e101a}To avoid the above issue, we can use the existing parameter in
> a geode that forces the server to write synchronously to the ".if"
> file:{color}
> {code:java}
> --J=-Dgemfire.syncMetaDataWrites=true
> {code}
> {color:#0e101a}This parameter is not mentioned anywhere in the documentation.
> So it would be good to add it to the following document:{color}
> {color:#0e101a}[https://geode.apache.org/docs/guide/114/managing/disk_storage/managing_disk_buffer_flushes.html]{color}
>
> {color:#0e101a}Changing this parameter's default value to true would also be
> good. {color}{color:#0e101a}This parameter should not affect performance as
> the ".if" file is not updated frequently.{color}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10311) Intermittent CI failure in AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient
[
https://issues.apache.org/jira/browse/GEODE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10311:
---
Labels: needsTriage pull-request-available (was: needsTriage)
> Intermittent CI failure in
> AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient
> --
>
> Key: GEODE-10311
> URL: https://issues.apache.org/jira/browse/GEODE-10311
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Dale Emery
>Assignee: Jinmei Liao
>Priority: Major
> Labels: needsTriage, pull-request-available
> Attachments: auth-expiration-artifacts.tgz
>
>
> AuthExpirationBackwardCompatibleDUnitTest >
> registeredInterest_FailedReAuth_non_durableClient fails intermittently. I do
> not know whether this is a test problem or a product problem.
> I first saw the failure in a precheckin test run on JDK17:
> * [https://concourse.apachegeode-ci.info/builds/52805744]
> * Test results:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7686/test-results/upgradeTest/1652409122/]
> * Test artifacts:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7686/test-artifacts/1652409122/upgradetestfiles-geode-pr-7686.tgz]
> The failure also happens on the {{develop}} branch, which does not yet have
> my PR changes. The failure occured 3 times in 100 executions of this test
> method on JDK11 on the {{develop}} branch.
> Stack trace (from my PR precheckin):
> {noformat}
> java.lang.AssertionError:
> Expecting empty but was:
> [CacheClientProxy[identity(heavy-lifter-7d403877-c6e7-5ba6-80ed-0c1ed553c05a(117190:loner):42300:114bc2ba,connection=1;
> port=42332; primary=true; version=GEODE 1.15.0]]
> at
> org.apache.geode.security.AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient(AuthExpirationBackwardCompatibleDUnitTest.java:653)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:139)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.run
[jira] [Commented] (GEODE-10311) Intermittent CI failure in AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient
[
https://issues.apache.org/jira/browse/GEODE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542558#comment-17542558
]
ASF subversion and git services commented on GEODE-10311:
-
Commit 5c0d5238667302c6b3b3dcacc26775c25379316d in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5c0d523866 ]
GEODE-10311: fix a flaky test (#7709)
> Intermittent CI failure in
> AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient
> --
>
> Key: GEODE-10311
> URL: https://issues.apache.org/jira/browse/GEODE-10311
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Dale Emery
>Assignee: Jinmei Liao
>Priority: Major
> Labels: needsTriage, pull-request-available
> Attachments: auth-expiration-artifacts.tgz
>
>
> AuthExpirationBackwardCompatibleDUnitTest >
> registeredInterest_FailedReAuth_non_durableClient fails intermittently. I do
> not know whether this is a test problem or a product problem.
> I first saw the failure in a precheckin test run on JDK17:
> * [https://concourse.apachegeode-ci.info/builds/52805744]
> * Test results:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7686/test-results/upgradeTest/1652409122/]
> * Test artifacts:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7686/test-artifacts/1652409122/upgradetestfiles-geode-pr-7686.tgz]
> The failure also happens on the {{develop}} branch, which does not yet have
> my PR changes. The failure occured 3 times in 100 executions of this test
> method on JDK11 on the {{develop}} branch.
> Stack trace (from my PR precheckin):
> {noformat}
> java.lang.AssertionError:
> Expecting empty but was:
> [CacheClientProxy[identity(heavy-lifter-7d403877-c6e7-5ba6-80ed-0c1ed553c05a(117190:loner):42300:114bc2ba,connection=1;
> port=42332; primary=true; version=GEODE 1.15.0]]
> at
> org.apache.geode.security.AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient(AuthExpirationBackwardCompatibleDUnitTest.java:653)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:139)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:29
[jira] [Commented] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542560#comment-17542560
]
Geode Integration commented on GEODE-7016:
--
Seen in [windows-acceptance-test-openjdk8
#366|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-acceptance-test-openjdk8/builds/366]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0250/test-results/acceptanceTest/1653549252/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0250/test-artifacts/1653549252/windows-acceptancetestfiles-openjdk8-1.16.0-build.0250.tgz].
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0, 1.12.9, 1.13.8, 1.14.4
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz,
> acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (GEODE-10311) Intermittent CI failure in AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient
[
https://issues.apache.org/jira/browse/GEODE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-10311.
-
Fix Version/s: 1.16.0
Resolution: Fixed
> Intermittent CI failure in
> AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient
> --
>
> Key: GEODE-10311
> URL: https://issues.apache.org/jira/browse/GEODE-10311
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Dale Emery
>Assignee: Jinmei Liao
>Priority: Major
> Labels: needsTriage, pull-request-available
> Fix For: 1.16.0
>
> Attachments: auth-expiration-artifacts.tgz
>
>
> AuthExpirationBackwardCompatibleDUnitTest >
> registeredInterest_FailedReAuth_non_durableClient fails intermittently. I do
> not know whether this is a test problem or a product problem.
> I first saw the failure in a precheckin test run on JDK17:
> * [https://concourse.apachegeode-ci.info/builds/52805744]
> * Test results:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7686/test-results/upgradeTest/1652409122/]
> * Test artifacts:
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-7686/test-artifacts/1652409122/upgradetestfiles-geode-pr-7686.tgz]
> The failure also happens on the {{develop}} branch, which does not yet have
> my PR changes. The failure occured 3 times in 100 executions of this test
> method on JDK11 on the {{develop}} branch.
> Stack trace (from my PR precheckin):
> {noformat}
> java.lang.AssertionError:
> Expecting empty but was:
> [CacheClientProxy[identity(heavy-lifter-7d403877-c6e7-5ba6-80ed-0c1ed553c05a(117190:loner):42300:114bc2ba,connection=1;
> port=42332; primary=true; version=GEODE 1.15.0]]
> at
> org.apache.geode.security.AuthExpirationBackwardCompatibleDUnitTest.registeredInterest_FailedReAuth_non_durableClient(AuthExpirationBackwardCompatibleDUnitTest.java:653)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:568)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:139)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at o
[jira] [Commented] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542561#comment-17542561
]
Geode Integration commented on GEODE-7016:
--
Seen in [windows-acceptance-test-openjdk8
#367|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-acceptance-test-openjdk8/builds/367]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0258/test-results/acceptanceTest/1653553890/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0258/test-artifacts/1653553890/windows-acceptancetestfiles-openjdk8-1.16.0-build.0258.tgz].
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0, 1.12.9, 1.13.8, 1.14.4
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz,
> acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (GEODE-10106) CI Failure: CacheClientNotifierDUnitTest > testNormalClient2MultipleCacheServer
[
https://issues.apache.org/jira/browse/GEODE-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag reassigned GEODE-10106:
---
Assignee: Nabarun Nag
> CI Failure: CacheClientNotifierDUnitTest >
> testNormalClient2MultipleCacheServer
> ---
>
> Key: GEODE-10106
> URL: https://issues.apache.org/jira/browse/GEODE-10106
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Jens Deppe
>Assignee: Nabarun Nag
>Priority: Major
> Labels: blocks-1.15.0, pull-request-available
> Fix For: 1.15.0
>
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1382]
> {noformat}
> CacheClientNotifierDUnitTest > testNormalClient2MultipleCacheServer FAILED
> 11:49:39java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 11:49:39Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 11:49:39
> ---
> 11:49:39Found suspect string in 'dunit_suspect-vm4.log' at line 431
> 11:49:39
> 11:49:39[error 2022/03/05 19:49:36.075 UTC
> tid=55] Error in
> redundancy satisfier
> 11:49:39java.lang.NullPointerException
> 11:49:39 at
> org.apache.geode.cache.client.internal.QueueManagerImpl.recoverPrimary(QueueManagerImpl.java:856)
> 11:49:39 at
> org.apache.geode.cache.client.internal.QueueManagerImpl$RedundancySatisfierTask.run2(QueueManagerImpl.java:1454)
> 11:49:39 at
> org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1340)
> 11:49:39 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 11:49:39 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 11:49:39 at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> 11:49:39 at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 11:49:39 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 11:49:39 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 11:49:39 at java.lang.Thread.run(Thread.java:750)
> 11:49:39at org.junit.Assert.fail(Assert.java:89)
> 11:49:39at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:422)
> 11:49:39at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:438)
> 11:49:39at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:551)
> 11:49:39at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:498)
> 11:49:39at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:481)
> 11:49:39at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 11:49:39at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 11:49:39at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 11:49:39at java.lang.reflect.Method.invoke(Method.java:498)
> 11:49:39at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> 11:49:39at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 11:49:39at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> 11:49:39at
> org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
> 11:49:39at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> 11:49:39at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> 11:49:39at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 11:49:39at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> 11:49:39at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> 11:49:39at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> 11:49:39at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> 11:49:39at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> 11:49:39at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> 11:49:3
[jira] [Commented] (GEODE-10330) Resource issues lead to "MemberDisconnectedException: Member isn't responding to heartbeat requests"
[
https://issues.apache.org/jira/browse/GEODE-10330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542572#comment-17542572
]
Nabarun Nag commented on GEODE-10330:
-
The initial test is nuked and moved to the new test framework.
This is a simple test for creating a normal cluster, doing some puts and
checking stats. This test should be not be running out of memory.
The old framework had lot of issues while starting or stopping members
> Resource issues lead to "MemberDisconnectedException: Member isn't responding
> to heartbeat requests"
>
>
> Key: GEODE-10330
> URL: https://issues.apache.org/jira/browse/GEODE-10330
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Donal Evans
>Assignee: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> A failure was observed in
> DistributedMulticastRegionWithUDPSecurityDUnitTest >
> testMulticastAfterReconnect due to suspect strings with fatal-level logging
> of "Membership service failure: Member isn't responding to heartbeat
> requests".
> Investigating the logs showed all members reporting long statistics sampling
> wakeup delays, indicating resource issues:
> {code:java}
> [vm3] [warn 2022/05/21 07:28:16.251 UTC LocatorWithMcast
> tid=0xb8] Statistics sampling thread detected a wakeup delay of 4760 ms,
> indicating a possible resource issue. Check the GC, memory, and CPU
> statistics.
> ...
> [locator] [warn 2022/05/21 07:28:20.288 UTC tid=0x3b]
> Statistics sampling thread detected a wakeup delay of 12400 ms, indicating a
> possible resource issue. Check the GC, memory, and CPU statistics.
> ...
> [vm1] [warn 2022/05/21 07:28:20.969 UTC vm1 tid=0xda]
> Statistics sampling thread detected a wakeup delay of 13738 ms, indicating a
> possible resource issue. Check the GC, memory, and CPU statistics.
> ...
> [vm0] [warn 2022/05/21 07:28:22.226 UTC vm0 tid=0xa9]
> Statistics sampling thread detected a wakeup delay of 15110 ms, indicating a
> possible resource issue. Check the GC, memory, and CPU statistics. {code}
>
> After downloading the test artifacts and using the progress tool from the
> dev-tools directory in the Geode repository, the following tests were found
> to be running during the resource issues, possibly indicating that one or
> more of them are particularly resource-intensive:
> {noformat}
> $> progress -r '2022-05-21 07:28:16.251 -' | grep org | sort{noformat}
> {code:java}
> org.apache.geode.cache.PRCacheListenerWithInterestPolicyAllDistributedTest.afterUpdateIsInvokedInEveryMember[0:
> redundancy=0]
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK)
> [2]
> org.apache.geode.cache.query.cq.dunit.CqDataUsingPoolOptimizedExecuteDUnitTest.testCQHAWithState
>
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testPartitionedCqOnAccessorBridgeServer
> org.apache.geode.cache30.CallbackArgDUnitTest.testForCA
> org.apache.geode.cache30.DistributedMulticastRegionWithUDPSecurityDUnitTest.testMulticastAfterReconnect
>
> org.apache.geode.cache30.DistributedNoAckRegionCCEOffHeapDUnitTest.testDistributedInvalidate
> org.apache.geode.cache30.GlobalRegionOffHeapDUnitTest.testOrderedUpdates
> org.apache.geode.cache30.ReconnectWithClusterConfigurationDUnitTest.testReconnectAfterMeltdown
>
> org.apache.geode.distributed.internal.P2PMessagingConcurrencyDUnitTest.testP2PMessaging(true,
> false, 32768, 65536) [6]
> org.apache.geode.disttx.PRDistTXDUnitTest.testSimulaneousChildRegionCreation
> org.apache.geode.internal.cache.ClientServerTransactionCCEDUnitTest.testClientCommitFunctionWithFailure
>
> org.apache.geode.internal.cache.eviction.OffHeapEvictionStatsDUnitTest.testHeapLruCounter
>
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode
>
> org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDistributedTest.testParallelGatewaySenderStartOnAccessorNode
>
> org.apache.geode.internal.cache.wan.serial.SerialWANPropagation_PartitionedRegionDUnitTest.testPartitionedSerialPropagationHA
> org.apache.geode.internal.tcp.TCPConduitDUnitTest.basicAcceptConnection[0]
> org.apache.geode.management.internal.configuration.ClusterConfigImportDUnitTest.importFailWithExistingRegion
>
> org.apache.geode.rest.internal.web.controllers.RestAPIsOnGroupsFunctionExecutionDUnitTest.testBasicP2PFunctionSelectedGroup[1]
>
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.failureShouldStillAllowOtherContainersDataAccess
>
> org.apache.geode.session.tests.Tomcat8Clie
[jira] [Commented] (GEODE-10327) Tests that use GfshRule leave behind orphaned processes and do not save artifacts for debugging failures
[ https://issues.apache.org/jira/browse/GEODE-10327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542660#comment-17542660 ] ASF subversion and git services commented on GEODE-10327: - Commit c464ece1e161f5b6dd498d608a589a98749b9220 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c464ece1e1 ] Revert "GEODE-10327: Overhaul GfshRule to kill processes and save artifacts for failures (#7571)" (#7728) This reverts commit 774505e7c74cff8c572be1ec4f4bb2b0f3e1a091. > Tests that use GfshRule leave behind orphaned processes and do not save > artifacts for debugging failures > > > Key: GEODE-10327 > URL: https://issues.apache.org/jira/browse/GEODE-10327 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.15.0, 1.16.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: Java17, pull-request-available > > GfshRule needs to cleanup all processes it forks. It also needs to save off > all runtime artifacts such as logging, stats, pid files, diskstores to enable > debugging of test failures. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10327) Tests that use GfshRule leave behind orphaned processes and do not save artifacts for debugging failures
[ https://issues.apache.org/jira/browse/GEODE-10327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542662#comment-17542662 ] ASF subversion and git services commented on GEODE-10327: - Commit 2154636e855d27300a1d289d5b4a1a15f0247849 in geode's branch refs/heads/support/1.15 from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2154636e85 ] Revert "GEODE-10327: Overhaul GfshRule to kill processes and save artifacts for failures (#7571)" This reverts commit 431bc151e9d519c0b2d6873fa31e4a58f7ac42eb. (Cherry picked from commit c464ece1e161f5b6dd498d608a589a98749b9220) > Tests that use GfshRule leave behind orphaned processes and do not save > artifacts for debugging failures > > > Key: GEODE-10327 > URL: https://issues.apache.org/jira/browse/GEODE-10327 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.15.0, 1.16.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: Java17, pull-request-available > > GfshRule needs to cleanup all processes it forks. It also needs to save off > all runtime artifacts such as logging, stats, pid files, diskstores to enable > debugging of test failures. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10305) CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed
[
https://issues.apache.org/jira/browse/GEODE-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542670#comment-17542670
]
Jianxia Chen commented on GEODE-10305:
--
The standard output shows that there is some issue when starting the locator:
{code:java}
[info 2022/05/05 21:36:06.098 UTC tid=0x19] Executing command:
start locator --name=loc
--classpath=/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/*:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/bin/*
--port=25498 --dir=/tmp/junit439159077415808630/locator
Command result for :
?[34m_ __
/ _/ __/ __/ // /
/ / __/ /___ /_ / _ /
/ /__/ / / _/ / // /
/__/_/ /__/_//_/1.15.0-build.0
?[0m
?[36mMonitor and Manage Apache Geode?[0m
..
Locator in /tmp/junit439159077415808630/locator on
heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34.c.apachegeode-ci.internal[25498]
as loc is currently online.
Process ID: 228190
Uptime: 18 seconds
Geode Version: 1.15.0-build.0
Java Version: 1.8.0_332
Log File: /tmp/junit439159077415808630/locator/loc.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
Unable to auto-connect (Security Manager may be enabled). Please use "connect
--locator=heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34.c.apachegeode-ci.internal[25498]"
to connect Gfsh to the locator.
Failed to connect; unknown cause: Exception caused JMX Manager startup to fail
because: 'HTTP service failed to start'
{code}
Then immediately after that, starting server hitting ForcedDisconnectException:
{code:java}
[info 2022/05/05 21:36:24.636 UTC tid=0x19] Executing command:
start server --name=server --server-port=0
--classpath=/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/*:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/bin/*
--locators=localhost[25498] --dir=/tmp/junit439159077415808630/server
Command result for :
...The Cache Server process terminated unexpectedly with exit status 1.
Please refer to the log file in /tmp/junit439159077415808630/server for full
details.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/slf4j-jdk14-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/home/geode/geode/geode-assembly/build/install/apache-geode/lib/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
Exception in thread "main"
org.apache.geode.distributed.DistributedSystemDisconnectedException:
Distribution manager on
heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34(server:240126):41036
started at Thu May 05 21:36:30 UTC 2022: Member isn't responding to heartbeat
requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
responding to heartbeat requests
at
org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2899)
at
org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1183)
at
org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5201)
at
org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
at
org.apache.geode.cache.query.cq.internal.CqServiceImpl.(CqServiceImpl.java:166)
at
org.apache.geode.cache.query.cq.internal.CqServiceFactoryImpl.create(CqServiceFactoryImpl.java:59)
at
org.apache.geode.cache.query.internal.cq.CqServiceProvider.create(CqServiceProvider.java:63)
at
org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:1004)
at
org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:864)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
at
org.apache
[jira] [Commented] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542691#comment-17542691
]
Geode Integration commented on GEODE-7016:
--
Seen in [windows-acceptance-test-openjdk8
#368|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-acceptance-test-openjdk8/builds/368]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0259/test-results/acceptanceTest/1653594668/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0259/test-artifacts/1653594668/windows-acceptancetestfiles-openjdk8-1.16.0-build.0259.tgz].
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0, 1.12.9, 1.13.8, 1.14.4
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (1).tgz,
> acceptancetestfiles-OpenJDK11-1.14.0-build.0628 (2).tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (GEODE-10341) Add scope details to snapshot section in documentation
Max Hufnagel created GEODE-10341: Summary: Add scope details to snapshot section in documentation Key: GEODE-10341 URL: https://issues.apache.org/jira/browse/GEODE-10341 Project: Geode Issue Type: Improvement Components: docs Reporter: Max Hufnagel A customer was doing an upgrade with a complete cluster restart and the documentation is not clear on this part. The customer has a non-persistent region with overflow to disk and wanted to know if they needed to do a combination of export/import and diskstore backup to backup the region or if a snapshot would include both in-cache entries and overflowed entries. A test verified that all entries are included in the gfd file. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10341) Add scope details to snapshot section in documentation
[ https://issues.apache.org/jira/browse/GEODE-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Hufnagel updated GEODE-10341: - Affects Version/s: 1.14.4 > Add scope details to snapshot section in documentation > -- > > Key: GEODE-10341 > URL: https://issues.apache.org/jira/browse/GEODE-10341 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Priority: Major > > A customer was doing an upgrade with a complete cluster restart and the > documentation is not clear on this part. > The customer has a non-persistent region with overflow to disk and wanted to > know if they needed to do a combination of export/import and diskstore backup > to backup the region or if a snapshot would include both in-cache entries and > overflowed entries. > A test verified that all entries are included in the gfd file. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10341) Add scope details to snapshot section in documentation
[ https://issues.apache.org/jira/browse/GEODE-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Hufnagel reassigned GEODE-10341: Assignee: Max Hufnagel > Add scope details to snapshot section in documentation > -- > > Key: GEODE-10341 > URL: https://issues.apache.org/jira/browse/GEODE-10341 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Assignee: Max Hufnagel >Priority: Major > > A customer was doing an upgrade with a complete cluster restart and the > documentation is not clear on this part. > The customer has a non-persistent region with overflow to disk and wanted to > know if they needed to do a combination of export/import and diskstore backup > to backup the region or if a snapshot would include both in-cache entries and > overflowed entries. > A test verified that all entries are included in the gfd file. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10341) Add scope details to snapshot section in documentation
[ https://issues.apache.org/jira/browse/GEODE-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10341: --- Labels: pull-request-available (was: ) > Add scope details to snapshot section in documentation > -- > > Key: GEODE-10341 > URL: https://issues.apache.org/jira/browse/GEODE-10341 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > > A customer was doing an upgrade with a complete cluster restart and the > documentation is not clear on this part. > The customer has a non-persistent region with overflow to disk and wanted to > know if they needed to do a combination of export/import and diskstore backup > to backup the region or if a snapshot would include both in-cache entries and > overflowed entries. > A test verified that all entries are included in the gfd file. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10305) CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed
[
https://issues.apache.org/jira/browse/GEODE-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542713#comment-17542713
]
Jianxia Chen commented on GEODE-10305:
--
The artifacts at
[http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1153/test-artifacts/1651794753/upgradetestfiles-openjdk8-1.15.0-build.1153.tgz]
does not contain the failing server log. Because it is in a tmp directory
/tmp/junit439159077415808630/server and the test infrastructure does not
collect the logs to the final artifacts. So we are not sure why
The Cache Server process terminated unexpectedly with exit status 1.
Looking at the stack trace, the ServerLauncher is still in the process of
starting. And the startup process is incomplete. gfsh start server command does
not have all the output of a successful start. And because of this, there is no
further test running for this particular iteration. i.e. this test iteration
failed at the setup stage.
I ran this test locally on my machine. All passed. So it's something flaky on
the infrastructure I suspect.
> CI Failure:
> TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest
> failed
> -
>
> Key: GEODE-10305
> URL: https://issues.apache.org/jira/browse/GEODE-10305
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.16.0
>Reporter: Eric Shu
>Assignee: Jianxia Chen
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple Failures
> (2 failures)
> org.opentest4j.AssertionFailedError: [The Cache Server process
> terminated unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit439159077415808630/server for full details.
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/slf4j-jdk14-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/home/geode/geode/geode-assembly/build/install/apache-geode/lib/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
> {noformat}
> This is caused by ForcedDisconnectException during cache creation.
> {noformat}
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34(server:240126):41036
> started at Thu May 05 21:36:30 UTC 2022: Member isn't responding to heartbeat
> requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2899)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1183)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5201)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceImpl.(CqServiceImpl.java:166)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceFactoryImpl.create(CqServiceFactoryImpl.java:59)
> at
> org.apache.geode.cache.query.internal.cq.CqServiceProvider.create(CqServiceProvider.java:63)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:1004)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:864)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
> at
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:913)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:814)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:740)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:
[jira] [Created] (GEODE-10342) Update the HTTP Module for Tomcat instructions to include current required jars
Max Hufnagel created GEODE-10342:
Summary: Update the HTTP Module for Tomcat instructions to include
current required jars
Key: GEODE-10342
URL: https://issues.apache.org/jira/browse/GEODE-10342
Project: Geode
Issue Type: Improvement
Components: docs
Affects Versions: 1.14.4
Reporter: Max Hufnagel
Step 6 of the installation instructions tell the user to:
Copy the following jar files from the Tanzu GemFire {{lib}} subdirectory to the
{{lib}} subdirectory of your Tomcat server ({{{}$CATALINA_HOME/lib{}}}), adding
version numbers to the filenames as needed:
* commons-io jar
* commons-lang jar
* commons-validator jar
* fastutil jar
* geode-common jar
* geode-core jar
* geode-logging jar
* geode-management jar
* geode-membership jar
* geode-serialization jar
* geode-tcp-server jar
* javax.transaction-api jar
* jgroups jar
* log4j-api jar
* log4j-core jar
* log4j-jul jar
* micrometer-core jar
* shiro-core jar
This list is dated and does not include all the libraries that are mentioned as
dependancies of this jars. For instance, the manifest for geode-core lists many
jars as dependancies in it’s classpath that are not in the above list (e.g.
antlr-2.7.7.jar, snappy-0.4.jar, etc.):
{{
Manifest-Version: 1.0 2Automatic-Module-Name: io.pivotal.gemfire.core
3Organization: VMware, Inc. 4Dependent-Modules: geode-membership-9.10.14
geode-http-service-9.10.14 5 geode-management-9.10.14 geode-unsafe-9.10.14
6Module-Name: geode-core 7Class-Path: antlr-2.7.7.jar commons-io-2.6.jar
micrometer-core-1.6.3.j 8 ar javax.resource-api-1.7.1.jar shiro-core-1.8.0.jar
jaxb-api-2.3.1.j 9 ar jaxb-impl-2.3.2.jar commons-modeler-2.0.1.jar
javax.mail-api-1.6.2 10 .jar mx4j-3.0.2.jar mx4j-remote-3.0.2.jar
mx4j-tools-3.0.1.jar jna-pl 11 atform-5.5.0.jar jna-5.5.0.jar
jopt-simple-5.0.4.jar snappy-0.4.jar c 12 lassgraph-4.8.52.jar rmiio-2.1.2.jar
javax.activation-1.2.0.jar istac 13 k-commons-runtime-3.0.9.jar
swagger-annotations-1.5.23.jar shiro-conf 14 ig-ogdl-1.8.0.jar
shiro-cache-1.8.0.jar shiro-crypto-hash-1.8.0.jar s 15
hiro-crypto-cipher-1.8.0.jar shiro-config-core-1.8.0.jar shiro-event- 16
1.8.0.jar shiro-crypto-core-1.8.0.jar shiro-lang-1.8.0.jar slf4j-api- 17
1.7.28.jar javax.activation-api-1.2.0.jar HdrHistogram-2.1.12.jar Lat 18
encyUtils-2.0.3.jar javax.transaction-api-1.3.jar 19Title: geode 20Version:
9.10.14 21Created-By: root
}}and geode-common
{{
1Manifest-Version: 1.02Organization: VMware,
Inc.3Dependent-Modules:4Module-Name: geode-common5Class-Path:
jackson-databind-2.10.5.1.jar jackson-annotations-2.10.5.j6 ar
jackson-core-2.10.5.jar7Title: geode8Version: 9.10.149Created-By: root}}
A fully exhaustive list has not yet been determined and confirmed, but it
should be almost all the jars provided in the distribution’s “lib” directory
(the classpath of the geode-dependencies meta-jar gives, perhaps, the most
concise list).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10305) CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed
[
https://issues.apache.org/jira/browse/GEODE-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10305:
---
Labels: needsTriage pull-request-available (was: needsTriage)
> CI Failure:
> TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest
> failed
> -
>
> Key: GEODE-10305
> URL: https://issues.apache.org/jira/browse/GEODE-10305
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.16.0
>Reporter: Eric Shu
>Assignee: Jianxia Chen
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> {noformat}
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple Failures
> (2 failures)
> org.opentest4j.AssertionFailedError: [The Cache Server process
> terminated unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit439159077415808630/server for full details.
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/slf4j-jdk14-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/home/geode/geode/geode-assembly/build/install/apache-geode/lib/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
> {noformat}
> This is caused by ForcedDisconnectException during cache creation.
> {noformat}
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34(server:240126):41036
> started at Thu May 05 21:36:30 UTC 2022: Member isn't responding to heartbeat
> requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2899)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1183)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5201)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceImpl.(CqServiceImpl.java:166)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceFactoryImpl.create(CqServiceFactoryImpl.java:59)
> at
> org.apache.geode.cache.query.internal.cq.CqServiceProvider.create(CqServiceProvider.java:63)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:1004)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:864)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
> at
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:913)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:814)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:740)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:259)
> Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.DistributionImpl$LifecycleListenerImpl.forcedDisconnect(DistributionImpl.java:941)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1792)
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
> Artifacts can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/331
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (GEODE-10305) CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed
[
https://issues.apache.org/jira/browse/GEODE-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542720#comment-17542720
]
Jianxia Chen commented on GEODE-10305:
--
I don't think this should be a blocker for 1.15 release.
> CI Failure:
> TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest
> failed
> -
>
> Key: GEODE-10305
> URL: https://issues.apache.org/jira/browse/GEODE-10305
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.16.0
>Reporter: Eric Shu
>Assignee: Jianxia Chen
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> {noformat}
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple Failures
> (2 failures)
> org.opentest4j.AssertionFailedError: [The Cache Server process
> terminated unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit439159077415808630/server for full details.
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/slf4j-jdk14-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/home/geode/geode/geode-assembly/build/install/apache-geode/lib/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
> {noformat}
> This is caused by ForcedDisconnectException during cache creation.
> {noformat}
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34(server:240126):41036
> started at Thu May 05 21:36:30 UTC 2022: Member isn't responding to heartbeat
> requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2899)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1183)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5201)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceImpl.(CqServiceImpl.java:166)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceFactoryImpl.create(CqServiceFactoryImpl.java:59)
> at
> org.apache.geode.cache.query.internal.cq.CqServiceProvider.create(CqServiceProvider.java:63)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:1004)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:864)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
> at
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:913)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:814)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:740)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:259)
> Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.DistributionImpl$LifecycleListenerImpl.forcedDisconnect(DistributionImpl.java:941)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1792)
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
> Artifacts can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/331
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
