[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334431#comment-17334431
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#169|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/169]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0167/test-results/distributedTest/1619566473/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0167/test-artifacts/1619566473/distributedtestfiles-OpenJDK8-1.15.0-build.0167.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9104) REST query output displays non-ASCII characters using escapes
[
https://issues.apache.org/jira/browse/GEODE-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334370#comment-17334370
]
ASF subversion and git services commented on GEODE-9104:
Commit f4769eba6b7aff4bebe4b3b514f53dd021eb4b33 in geode's branch
refs/heads/feature/GEODE-9104 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f4769eb ]
GEODE-9104: Removed ESCAPE_NON_ASCII so non-ASCII characters are displayed
> REST query output displays non-ASCII characters using escapes
> -
>
> Key: GEODE-9104
> URL: https://issues.apache.org/jira/browse/GEODE-9104
> Project: Geode
> Issue Type: Bug
> Components: rest (dev)
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
>
> For example, if JSON containing Chinese characters is put:
> {noformat}
> curl -X PUT -H "Content-Type: application/json"
> localhost:8081/geode/v1/customers/1 -d '{"id": "1", "firstName": "名",
> "lastName": "姓"}'
> {noformat}
> The results of getting the entry are correct:
> {noformat}
> curl localhost:8081/geode/v1/customers/1
> {
> "id" : "1",
> "firstName" : "名",
> "lastName" : "姓"
> }
> {noformat}
> The results of querying the entry show the field values escaped:
> {noformat}
> curl -G http://localhost:8081/gemfire-api/v1/queries/adhoc --data-urlencode
> "q=SELECT * FROM /customers where id='1'"
> [ {
> "id" : "1",
> "firstName" : "\u540D",
> "lastName" : "\u59D3"
> } ]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9138) Add warning in server logs when data event is ignored as a duplicate
[ https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334373#comment-17334373 ] ASF subversion and git services commented on GEODE-9138: Commit 1f4c812f42caba9bb2bdae7c0a61305021988bf0 in geode's branch refs/heads/feature/GEODE-9138 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1f4c812 ] GEODE-9138: Updated test > Add warning in server logs when data event is ignored as a duplicate > > > Key: GEODE-9138 > URL: https://issues.apache.org/jira/browse/GEODE-9138 > Project: Geode > Issue Type: Bug > Components: client/server, logging >Reporter: Diane Hardman >Priority: Major > Labels: pull-request-available > > Under certain rare conditions, a client may send or resend a data event with > an eventId that causes the server to interpret it as a duplicate event and > discard it. > It is currently impossible to trace when this happens without extra logging > added. > From Barry: > No, if the server thinks it has seen the event, it silently eats it. See > DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it. > The log message that tracks this behavior in the server needs to be added > permanently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334371#comment-17334371 ] ASF subversion and git services commented on GEODE-4709: Commit 02d3f88c2dd6f419c77448e20572f7c59037c144 in geode's branch refs/heads/develop from Alberto Bustamante Reyes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=02d3f88 ] GEODE-4709: Add list gateways output sample in UG (#6372) * GEODE-4709: Add list gateways output sample in UG > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9200) Leaked message used to signal "all endpoints disconnected"
[ https://issues.apache.org/jira/browse/GEODE-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9200: -- Labels: pull-request-available (was: ) > Leaked message used to signal "all endpoints disconnected" > -- > > Key: GEODE-9200 > URL: https://issues.apache.org/jira/browse/GEODE-9200 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > > Geode native uses a "blank" reply message to signal to regions that all > endpoints have disconnected, i.e. they can shut down. This message is > allocated on the heap into a static pointer in the function > `TcrMessage::getAllEPDisMess`, but is never deleted. This should be a > dynamically allocated message, so it can be cleaned up via `delete` in the > region like all other messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9200) Leaked message used to signal "all endpoints disconnected"
[ https://issues.apache.org/jira/browse/GEODE-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334378#comment-17334378 ] ASF GitHub Bot commented on GEODE-9200: --- pdxcodemonkey opened a new pull request #793: URL: https://github.com/apache/geode-native/pull/793 - Remove static endpoint disconnected message - use dynamically allocated message for this, a la other messages - no longer leak an instance at shutdown, no more special case code for this message when deleting messages. - Remove some really unfortunate abbreviations in a couple of function and variable names. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Leaked message used to signal "all endpoints disconnected" > -- > > Key: GEODE-9200 > URL: https://issues.apache.org/jira/browse/GEODE-9200 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > > Geode native uses a "blank" reply message to signal to regions that all > endpoints have disconnected, i.e. they can shut down. This message is > allocated on the heap into a static pointer in the function > `TcrMessage::getAllEPDisMess`, but is never deleted. This should be a > dynamically allocated message, so it can be cleaned up via `delete` in the > region like all other messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334372#comment-17334372 ] ASF subversion and git services commented on GEODE-4709: Commit 02d3f88c2dd6f419c77448e20572f7c59037c144 in geode's branch refs/heads/develop from Alberto Bustamante Reyes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=02d3f88 ] GEODE-4709: Add list gateways output sample in UG (#6372) * GEODE-4709: Add list gateways output sample in UG > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333870#comment-17333870
]
Geode Integration commented on GEODE-7710:
--
Seen in [DistributedTestOpenJDK11
#169|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/169]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0165/test-results/distributedTest/1619559739/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0165/test-artifacts/1619559739/distributedtestfiles-OpenJDK11-1.15.0-build.0165.tgz].
> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-4709. - Fix Version/s: 1.15.0 Resolution: Fixed > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333557#comment-17333557
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#167|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/167]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0165/test-results/distributedTest/1619559104/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0165/test-artifacts/1619559104/distributedtestfiles-OpenJDK8-1.15.0-build.0165.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333553#comment-17333553
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#73.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/73.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0771/test-results/distributedTest/1619516349/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0771/test-artifacts/1619516349/distributedtestfiles-OpenJDK8-1.14.0-build.0771.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9203) Implement NUMSUB Subcommand
Wayne created GEODE-9203: Summary: Implement NUMSUB Subcommand Key: GEODE-9203 URL: https://issues.apache.org/jira/browse/GEODE-9203 Project: Geode Issue Type: Sub-task Components: redis Reporter: Wayne Implement the [NUMSUB|https://redis.io/commands/pubsub#codepubsub-numsub-channel-1--channel-ncode] subcommand. +Acceptance Criteria+ The NUMSUB subcommand has been implemented along with unit tests to assert that the subcommand correctly returns the number of subscribers (not counting clients subscribed to patterns) for the specified channels. h5. Return value [Array reply|https://redis.io/topics/protocol#array-reply]: a list of channels and number of subscribers for every channel. The format is channel, count, channel, count, ..., so the list is flat. The order in which the channels are listed is the same as the order of the channels specified in the command call. Note that it is valid to call this command without channels. In this case it will just return an empty list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333546#comment-17333546
]
ASF subversion and git services commented on GEODE-9139:
Commit 55921a4d7b66a51279e71d1a665dc797fcc8ca6f in geode's branch
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=55921a4 ]
GEODE-9139 SSLException in starting up a Locator (#6308)
* GEODE-9139 SSLException in starting up a Locator
Preserve the bind-address string specified by the user for cluster
communications
Also enable use of host names in member identifiers if endpoint
validation is enabled.
* retain the bind address string or bind address InetAddress in a HostAddress
HostAndPort could not be used because there will be a port set but there
may not be a bindAddress set. That class requires a host name.
* fixed NPE
* fixing a few problems with HostAddress
* spA
* fixed lgtm issue
* more lgtm issues fixed
* addressing Kamilla's comments
* typo
* simplify HostAndPort & HostAddress by creating a common superclass to hold
their InetSocketAddress.
Cache the result of attempting to resolve the host name, as suggested by
Bill.
* retain the string passed in as the hostname to avoid things like 127.0.0.1
being converted to localhost
* added comments about retention of the hostName parameter
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333547#comment-17333547
]
ASF subversion and git services commented on GEODE-9139:
Commit 55921a4d7b66a51279e71d1a665dc797fcc8ca6f in geode's branch
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=55921a4 ]
GEODE-9139 SSLException in starting up a Locator (#6308)
* GEODE-9139 SSLException in starting up a Locator
Preserve the bind-address string specified by the user for cluster
communications
Also enable use of host names in member identifiers if endpoint
validation is enabled.
* retain the bind address string or bind address InetAddress in a HostAddress
HostAndPort could not be used because there will be a port set but there
may not be a bindAddress set. That class requires a host name.
* fixed NPE
* fixing a few problems with HostAddress
* spA
* fixed lgtm issue
* more lgtm issues fixed
* addressing Kamilla's comments
* typo
* simplify HostAndPort & HostAddress by creating a common superclass to hold
their InetSocketAddress.
Cache the result of attempting to resolve the host name, as suggested by
Bill.
* retain the string passed in as the hostname to avoid things like 127.0.0.1
being converted to localhost
* added comments about retention of the hostName parameter
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9139) SSLException in starting up a Locator
[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-9139:
--
Fix Version/s: 1.15.0
> SSLException in starting up a Locator
> -
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching.If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9201) Implement PUBSUB Command
[ https://issues.apache.org/jira/browse/GEODE-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9201: - Description: Implement the [PUBSUB|https://redis.io/commands/pubsub] command and the three associated subcommands represented by subtasks. (was: Implement the [PUBSUB|https://redis.io/commands/pubsub] command and the three associated subcommands.) > Implement PUBSUB Command > > > Key: GEODE-9201 > URL: https://issues.apache.org/jira/browse/GEODE-9201 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > > Implement the [PUBSUB|https://redis.io/commands/pubsub] command and the three > associated subcommands represented by subtasks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9202) Implement PUBSUB CHANNELS Subcommand
Wayne created GEODE-9202:
Summary: Implement PUBSUB CHANNELS Subcommand
Key: GEODE-9202
URL: https://issues.apache.org/jira/browse/GEODE-9202
Project: Geode
Issue Type: Sub-task
Components: redis
Reporter: Wayne
Implement the
[CHANNELS|https://redis.io/commands/pubsub#pubsub-channels-pattern] subcommand
of the PUBSUB command.
+Acceptance Criteria+
The CHANNELS subcommand is correctly implemented and unit tests are developed
to ensure that the command lists the currently _active channels_. An active
channel is a Pub/Sub channel with one or more subscribers (not including
clients subscribed to patterns).
If no {{pattern}} is specified, all the channels are listed, otherwise if
pattern is specified only channels matching the specified glob-style pattern
are listed.
h5. Return value
[Array reply|https://redis.io/topics/protocol#array-reply]: a list of active
channels, optionally matching the specified pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333541#comment-17333541
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#73.4|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/73.4]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0771/test-results/distributedTest/1619555011/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0771/test-artifacts/1619555011/distributedtestfiles-OpenJDK8-1.14.0-build.0771.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9201) Implement PUBSUB Command
Wayne created GEODE-9201: Summary: Implement PUBSUB Command Key: GEODE-9201 URL: https://issues.apache.org/jira/browse/GEODE-9201 Project: Geode Issue Type: New Feature Components: redis Reporter: Wayne Implement the [PUBSUB|https://redis.io/commands/pubsub] command and the three associated subcommands. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9200) Leaked message used to signal "all endpoints disconnected"
Blake Bender created GEODE-9200: --- Summary: Leaked message used to signal "all endpoints disconnected" Key: GEODE-9200 URL: https://issues.apache.org/jira/browse/GEODE-9200 Project: Geode Issue Type: Bug Components: native client Reporter: Blake Bender Geode native uses a "blank" reply message to signal to regions that all endpoints have disconnected, i.e. they can shut down. This message is allocated on the heap into a static pointer in the function `TcrMessage::getAllEPDisMess`, but is never deleted. This should be a dynamically allocated message, so it can be cleaned up via `delete` in the region like all other messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9200) Leaked message used to signal "all endpoints disconnected"
[ https://issues.apache.org/jira/browse/GEODE-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender reassigned GEODE-9200: --- Assignee: Blake Bender > Leaked message used to signal "all endpoints disconnected" > -- > > Key: GEODE-9200 > URL: https://issues.apache.org/jira/browse/GEODE-9200 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > > Geode native uses a "blank" reply message to signal to regions that all > endpoints have disconnected, i.e. they can shut down. This message is > allocated on the heap into a static pointer in the function > `TcrMessage::getAllEPDisMess`, but is never deleted. This should be a > dynamically allocated message, so it can be cleaned up via `delete` in the > region like all other messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9155) increase wait interval on PassiveExpirationManager
[ https://issues.apache.org/jira/browse/GEODE-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333523#comment-17333523 ] ASF subversion and git services commented on GEODE-9155: Commit 85183489c8c47de7f356e1ae55eaf31b9658276c in geode's branch refs/heads/develop from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8518348 ] GEODE-9155: change frequency of passive expiration (#6325) GEODE-9155: change frequency of passive expiration - increase the time between checks for keys to expire. this reduces the cpu utilization but causes longer collections when they do collect. - fix patch file; all tcl tests pass locally Co-authored-by: Ray Ingles > increase wait interval on PassiveExpirationManager > -- > > Key: GEODE-9155 > URL: https://issues.apache.org/jira/browse/GEODE-9155 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > > currently this class is running through all keys every second and is > consuming a lot of cpu cycles. Business needs do not seem to require keys to > be removed from memory this quickly. This ticket will increase interval to > every 30 minutes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9155) increase wait interval on PassiveExpirationManager
[ https://issues.apache.org/jira/browse/GEODE-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333524#comment-17333524 ] ASF subversion and git services commented on GEODE-9155: Commit 85183489c8c47de7f356e1ae55eaf31b9658276c in geode's branch refs/heads/develop from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8518348 ] GEODE-9155: change frequency of passive expiration (#6325) GEODE-9155: change frequency of passive expiration - increase the time between checks for keys to expire. this reduces the cpu utilization but causes longer collections when they do collect. - fix patch file; all tcl tests pass locally Co-authored-by: Ray Ingles > increase wait interval on PassiveExpirationManager > -- > > Key: GEODE-9155 > URL: https://issues.apache.org/jira/browse/GEODE-9155 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: Hale Bales >Priority: Major > Labels: pull-request-available > > currently this class is running through all keys every second and is > consuming a lot of cpu cycles. Business needs do not seem to require keys to > be removed from memory this quickly. This ticket will increase interval to > every 30 minutes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6489) CI Failures with testDistributedDeadlock
[
https://issues.apache.org/jira/browse/GEODE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333501#comment-17333501
]
John Hutchison commented on GEODE-6489:
---
this seems to be the same issue as
https://issues.apache.org/jira/browse/GEODE-6222.
> CI Failures with testDistributedDeadlock
>
>
> Key: GEODE-6489
> URL: https://issues.apache.org/jira/browse/GEODE-6489
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Lynn Hughes-Godfrey
>Assignee: Jinmei Liao
>Priority: Major
> Labels: flaky
>
> In an single CI run, we see 3 failures all related to testDistributedDeadlock:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> 137 tests completed, 2 failed
> > Task :geode-web:distributedTest FAILED
> > Task :geode-core:distributedTest
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6222) CI Failure: GemFireDeadlockDetectorDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333498#comment-17333498
]
Geode Integration commented on GEODE-6222:
--
Seen in [DistributedTestOpenJDK8
#166|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/166]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0164/test-results/distributedTest/1619549928/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0164/test-artifacts/1619549928/distributedtestfiles-OpenJDK8-1.15.0-build.0164.tgz].
> CI Failure: GemFireDeadlockDetectorDUnitTest
>
>
> Key: GEODE-6222
> URL: https://issues.apache.org/jira/browse/GEODE-6222
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
>Affects Versions: 1.9.0
>Reporter: Ken Howe
>Priority: Major
> Labels: flaky
>
> Flaky test failure in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/247]
> {code:java}
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:199)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333497#comment-17333497
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#165|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/165]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0163/test-results/distributedTest/1619549466/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0163/test-artifacts/1619549466/distributedtestfiles-OpenJDK8-1.15.0-build.0163.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reopened GEODE-8990:
---
test failure occurred agin in ci run:
org.apache.geode.session.tests.Jetty9CachingClientServerTest >
shouldCacheSessionOnClient FAILED
org.junit.ComparisonFailure: expected:<"[Foo]"> but was:<"[bogus]">
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.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:70)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0163/test-results/distributedTest/1619549466/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0163/test-artifacts/1619549466/distributedtestfiles-OpenJDK8-1.15.0-build.0163.tgz
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9161) No gradle 7 deprecation warnings [PERMANENT]
[ https://issues.apache.org/jira/browse/GEODE-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333484#comment-17333484 ] ASF subversion and git services commented on GEODE-9161: Commit 1ce8170e2413f24969bbba37dc60a061dd3e6a65 in geode's branch refs/heads/develop from M. Oleske [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ce8170 ] GEODE-9161: Fix some more gradle 7 warnings (#6369) - use non deprecated naming of properties Authored-by: M. Oleske > No gradle 7 deprecation warnings [PERMANENT] > > > Key: GEODE-9161 > URL: https://issues.apache.org/jira/browse/GEODE-9161 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Michael Oleske >Priority: Major > Labels: pull-request-available > > Why this is important: At some point this project will update to gradle 7, > and it is better to stay on top of things then behind > Given I have cloned the geode repository > When I run ./gradlew build --warning-mode=all > Then I see no output about "This will fail in gradle 7.0" or "This is > scheduled to be removed in Gradle 7.0" > Notes: > Not all warnings appear at first, you'll likely have to run with several > times as you clean up > There are some gradle 8.0 warnings. If you happen to clean those up nice! > Otherwise ok to skip for now. > There's some oddities with properties being hardcoded in other places to > their deprecated name which probably requires real work. > The following types of errors are in the project > The testRuntime configuration has been deprecated for dependency declaration. > This will fail with an error in Gradle 7.0. Please use the testRuntimeOnly > configuration instead. Consult the upgrading guide for further information: > https://docs.gradle.org/6.8.3/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations > The compile configuration has been deprecated for dependency declaration. > This will fail with an error in Gradle 7.0. Please use the implementation or > api configuration instead. Consult the upgrading guide for further > information: > https://docs.gradle.org/6.8.3/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations > The AbstractArchiveTask.baseName property has been deprecated. This is > scheduled to be removed in Gradle 7.0. Please use the archiveBaseName > property instead. See > https://docs.gradle.org/6.8.3/dsl/org.gradle.api.tasks.bundling.AbstractArchiveTask.html#org.gradle.api.tasks.bundling.AbstractArchiveTask:baseName > for more details. > The configuration :extensions:geode-modules:compileOnly was resolved without > accessing the project in a safe manner. This may happen when a configuration > is resolved from a different project. This behaviour has been deprecated and > is scheduled to be removed in Gradle 7.0. See > https://docs.gradle.org/6.8.3/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors > for more details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7917) Problem forming SSL connection in multisite setup
[ https://issues.apache.org/jira/browse/GEODE-7917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333482#comment-17333482 ] Geode Integration commented on GEODE-7917: -- Seen on support/1.14 in [DistributedTestOpenJDK11 #67|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/67] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-results/distributedTest/1619237075/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-artifacts/1619237075/distributedtestfiles-OpenJDK11-1.14.0-build.0770.tgz]. > Problem forming SSL connection in multisite setup > - > > Key: GEODE-7917 > URL: https://issues.apache.org/jira/browse/GEODE-7917 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Fix For: 1.13.0 > > Attachments: javax_net_debug.log > > Time Spent: 50m > Remaining Estimate: 0h > > We are installing two sites, with one locator in each site, and TLS enabled. > Problem appears when locators on both sides are started at same time. In that > case, on both locators, immediately after they are started, > IllegalStateException is caught, and connections are never reestablished. > > javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake > at > java.base/sun.security.ssl.SSLSocketImpl.handleEOF(SSLSocketImpl.java:1320) > at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1159) > at > java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1062) > at > java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:402) > at > org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:1112) > at > org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:879) > at > org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:841) > at > org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:830) > at > org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:208) > at > org.apache.geode.cache.client.internal.locator.wan.LocatorDiscovery.exchangeRemoteLocators(LocatorDiscovery.java:195) > at > org.apache.geode.cache.client.internal.locator.wan.LocatorDiscovery$RemoteLocatorDiscovery.run(LocatorDiscovery.java:121) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Suppressed: java.net.SocketException: Broken pipe (Write failed) > at java.base/java.net.SocketOutputStream.socketWrite0(Native Method) > at > java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110) > at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:150) > at > java.base/sun.security.ssl.SSLSocketOutputRecord.encodeAlert(SSLSocketOutputRecord.java:81) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:351) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:263) > at > java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:405) > ... 10 more > Caused by: java.io.EOFException: SSL peer shut down incorrectly > at > java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:167) > at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:108) > at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1151) > ... 12 more > > If locators are restarted one by one, everything is OK. > Added log of the fault with set javax.net.debug=all. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9199) Restructure dunit tests to work with compatible with Redis cluster mode
[ https://issues.apache.org/jira/browse/GEODE-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reassigned GEODE-9199: - Assignee: John Hutchison > Restructure dunit tests to work with compatible with Redis cluster mode > > > Key: GEODE-9199 > URL: https://issues.apache.org/jira/browse/GEODE-9199 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Assignee: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333478#comment-17333478
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#65.8|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/65.8]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-results/distributedTest/1619173930/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-artifacts/1619173930/distributedtestfiles-OpenJDK11-1.14.0-build.0766.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6413) CI Failure: Bind Exception during ClusterCommunicationsDUnitTest.performARollingUpgrade
[
https://issues.apache.org/jira/browse/GEODE-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-6413:
--
Component/s: membership
> CI Failure: Bind Exception during
> ClusterCommunicationsDUnitTest.performARollingUpgrade
> ---
>
> Key: GEODE-6413
> URL: https://issues.apache.org/jira/browse/GEODE-6413
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Reporter: Benjamin P Ross
>Priority: Major
> Fix For: 1.9.0
>
>
> Stack Trace:
> {noformat}
> org.apache.geode.ClusterCommunicationsDUnitTest >
> performARollingUpgrade[SHARED_CONNECTIONS] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> c4dd6cb2c206 with 3 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at
> org.apache.geode.ClusterCommunicationsDUnitTest.performARollingUpgrade(ClusterCommunicationsDUnitTest.java:214)
> Caused by:
> java.net.BindException: Failed to create server socket on
> c4dd6cb2c206/172.17.0.16[43969]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:756)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:714)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:680)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.initializeServerSocket(TcpServer.java:225)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.startServerThread(TcpServer.java:215)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:210)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:501)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:557)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:340)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:252)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139)
> at
> org.apache.geode.ClusterCommunicationsDUnitTest.lambda$null$1(ClusterCommunicationsDUnitTest.java:220)
> Caused by:
> java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:753)
> ... 11 more
> {noformat}
> This test may be fixed with a longer await() timeout.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6489) CI Failures with testDistributedDeadlock
[
https://issues.apache.org/jira/browse/GEODE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333477#comment-17333477
]
Geode Integration commented on GEODE-6489:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#65.7|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/65.7]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-results/distributedTest/1619162123/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-artifacts/1619162123/distributedtestfiles-OpenJDK11-1.14.0-build.0766.tgz].
> CI Failures with testDistributedDeadlock
>
>
> Key: GEODE-6489
> URL: https://issues.apache.org/jira/browse/GEODE-6489
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Lynn Hughes-Godfrey
>Assignee: Jinmei Liao
>Priority: Major
> Labels: flaky
>
> In an single CI run, we see 3 failures all related to testDistributedDeadlock:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testDistributedDeadlockWithFunction FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest
> > testNoDeadlock FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run
> in VM 1 running on Host ceb4d948b5be with 4 VMs
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with
> org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase
> was not fulfilled within 300 seconds.
> 137 tests completed, 2 failed
> > Task :geode-web:distributedTest FAILED
> > Task :geode-core:distributedTest
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest
> > testDistributedDeadlockWithDLock FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333475#comment-17333475
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#65.4|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/65.4]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-results/distributedTest/1619118850/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-artifacts/1619118850/distributedtestfiles-OpenJDK11-1.14.0-build.0766.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333474#comment-17333474
]
Geode Integration commented on GEODE-9069:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#70.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/70.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0767/test-results/distributedTest/1619078851/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0767/test-artifacts/1619078851/distributedtestfiles-OpenJDK8-1.14.0-build.0767.tgz].
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
>
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333472#comment-17333472
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#65.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/65.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-results/distributedTest/1619071366/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-artifacts/1619071366/distributedtestfiles-OpenJDK11-1.14.0-build.0766.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333470#comment-17333470
]
Geode Integration commented on GEODE-9070:
--
Seen in [DistributedTestOpenJDK8
#163.3|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/163.3]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-results/distributedTest/1619547582/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-artifacts/1619547582/distributedtestfiles-OpenJDK8-1.15.0-build.0161.tgz].
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Reporter: Jens Deppe
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333471#comment-17333471
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#70|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/70]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0767/test-results/distributedTest/1619065040/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0767/test-artifacts/1619065040/distributedtestfiles-OpenJDK8-1.14.0-build.0767.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9106) CI Failure: Client Server Session Cache fails infrequently with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin P Ross resolved GEODE-9106. Resolution: Duplicate > CI Failure: Client Server Session Cache fails infrequently with > ConditionTimeoutException > - > > Key: GEODE-9106 > URL: https://issues.apache.org/jira/browse/GEODE-9106 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > > preCreatedRegionIsNotCopiedToNewlyStartedServers FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$52/487544699.run > in VM 1 running on Host a1dde695db62 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) > at org.apache.geode.test.dunit.VM.invoke(VM.java:448) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.preCreatedRegionIsNotCopiedToNewlyStartedServers(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > Expected size: 1 but was: 0 in: > [] within 5 minutes. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$preCreatedRegionIsNotCopiedToNewlyStartedServers$bb17a952$1(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > java.lang.AssertionError: > Expected size: 1 but was: 0 in: > [] > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258) > This issue seems to be specific to the method validateBootstrapped(). In this > method we attempt to verify that the BootstrappingFunction is being > registered as a Listener within the Distribution Manager (which is a part of > setting up the ClientServerSessionCache) however in some situations it seems > that we are unable to verify this. This issue does not seem to reproduce > locally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9106) CI Failure: Client Server Session Cache fails infrequently with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333467#comment-17333467 ] Geode Integration commented on GEODE-9106: -- Seen in [DistributedTestOpenJDK8 #163.3|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/163.3] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-results/distributedTest/1619547582/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-artifacts/1619547582/distributedtestfiles-OpenJDK8-1.15.0-build.0161.tgz]. > CI Failure: Client Server Session Cache fails infrequently with > ConditionTimeoutException > - > > Key: GEODE-9106 > URL: https://issues.apache.org/jira/browse/GEODE-9106 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > > preCreatedRegionIsNotCopiedToNewlyStartedServers FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$52/487544699.run > in VM 1 running on Host a1dde695db62 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) > at org.apache.geode.test.dunit.VM.invoke(VM.java:448) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.preCreatedRegionIsNotCopiedToNewlyStartedServers(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > Expected size: 1 but was: 0 in: > [] within 5 minutes. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$preCreatedRegionIsNotCopiedToNewlyStartedServers$bb17a952$1(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > java.lang.AssertionError: > Expected size: 1 but was: 0 in: > [] > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258) > This issue seems to be specific to the method validateBootstrapped(). In this > method we attempt to verify that the BootstrappingFunction is being > registered as a Listener within the Distribution Manager (which is a part of > setting up the ClientServerSessionCache) however in some situations it seems > that we are unable to verify this. This issue does not seem to reproduce > locally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-9106) CI Failure: Client Server Session Cache fails infrequently with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reopened GEODE-9106: --- test failure in CI run org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > preCreatedRegionIsNotCopiedToNewlyStartedServers FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$52/2029192492.run in VM 1 running on Host e243b2a9bcec with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) at org.apache.geode.test.dunit.VM.invoke(VM.java:448) at org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.preCreatedRegionIsNotCopiedToNewlyStartedServers(ClientServerSessionCacheDUnitTest.java:144) Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest Expected size: 1 but was: 0 in: [] within 5 minutes. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895) at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679) at org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$preCreatedRegionIsNotCopiedToNewlyStartedServers$bb17a952$1(ClientServerSessionCacheDUnitTest.java:144) Caused by: java.lang.AssertionError: Expected size: 1 but was: 0 in: [] =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-results/distributedTest/1619547582/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-artifacts/1619547582/distributedtestfiles-OpenJDK8-1.15.0-build.0161.tgz > CI Failure: Client Server Session Cache fails infrequently with > ConditionTimeoutException > - > > Key: GEODE-9106 > URL: https://issues.apache.org/jira/browse/GEODE-9106 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > > preCreatedRegionIsNotCopiedToNewlyStartedServers FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$52/487544699.run > in VM 1 running on Host a1dde695db62 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631) > at org.apache.geode.test.dunit.VM.invoke(VM.java:448) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.preCreatedRegionIsNotCopiedToNewlyStartedServers(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest > Expected size: 1 but was: 0 in: > [] within 5 minutes. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679) > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$preCreatedRegionIsNotCopiedToNewlyStartedServers$bb17a952$1(ClientServerSessionCacheDUnitTest.java:144) > Caused by: > java.lang.AssertionError: > Expected size: 1 but was: 0 in: > [] > at > org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258) > This issue seems to be specific to the method validateBootstrapped(). In this > method we attempt to verify that the BootstrappingFunction is being > registered as a Listener within the Distribution Manager (which is a part of > setting up the
[jira] [Commented] (GEODE-7455) CI Failure: AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean Failed
[
https://issues.apache.org/jira/browse/GEODE-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333465#comment-17333465
]
Geode Integration commented on GEODE-7455:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#65|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/65]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-results/distributedTest/1619048260/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-artifacts/1619048260/distributedtestfiles-OpenJDK11-1.14.0-build.0766.tgz].
> CI Failure:
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> Failed
> --
>
> Key: GEODE-7455
> URL: https://issues.apache.org/jira/browse/GEODE-7455
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: flaky
>
> AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean
> failed in DistributedTestOpenJDK11 below are the relevant details.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1280]
>
> {noformat}
> 13:30:08
> org.apache.geode.management.AEQManagementDUnitTest >
> testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean FAILED
> 13:30:08
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.AEQManagementDUnitTest$$Lambda$200/0x0008407dec40.run
> in VM 0 running on Host 0e592392f6db with 4 VMs
> 13:30:08
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> 13:30:08
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> 13:30:08
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean(AEQManagementDUnitTest.java:245)
> 13:30:0813:30:08
> Caused by:
> 13:30:08
> org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 13:30:08
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 13:30:08
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 13:30:08
> at
> org.apache.geode.management.AEQManagementDUnitTest.lambda$testCreateAEQWithDispatcherInPausedStateAndResumeAndVerifyUsingMBean$d4d42c35$1(AEQManagementDUnitTest.java:250)
> 14:10:3714:10:37
> 793 tests completed, 1 failed, 61 skipped {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-results/distributedTest/1573687903/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0013/test-artifacts/1573687903/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0013.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7445) A public interface method should not return an instance of an "internal" class
[
https://issues.apache.org/jira/browse/GEODE-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333464#comment-17333464
]
Geode Integration commented on GEODE-7445:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#65|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/65]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-results/distributedTest/1619048260/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0766/test-artifacts/1619048260/distributedtestfiles-OpenJDK11-1.14.0-build.0766.tgz].
> A public interface method should not return an instance of an "internal" class
> --
>
> Key: GEODE-7445
> URL: https://issues.apache.org/jira/browse/GEODE-7445
> Project: Geode
> Issue Type: Bug
>Reporter: John Blum
>Assignee: Ernest Burghardt
>Priority: Minor
> Fix For: 1.12.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{org.apache.geode.cache.TransactionId}} class's {{getMemberId()}} method
> returns an instance of
> {{org.apache.geode.distriburted.internal.InternalDistributedMember}}.
> See here:
> https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/TransactionId.html#getMemberId--
> If anything, the getMemberId methods should return and "ID" and not (even) a
> {{DistributedMember}}, but, if it must, then it should adhere to the "public"
> API by return an instance of
> [{{org.apache.geode.distributed.DistributedMember}}|https://geode.apache.org/releases/latest/javadoc/org/apache/geode/distributed/DistributedMember.html]!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9192) test-container docker image is unstable due to dependencies
[ https://issues.apache.org/jira/browse/GEODE-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333461#comment-17333461 ] ASF subversion and git services commented on GEODE-9192: Commit 67b7c95dccd7a4cd5cfa7082dbda626387583e66 in geode's branch refs/heads/support/1.12 from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=67b7c95 ] GEODE-9192: test-container fixes (#6381) * Use ubuntu as the base * Install packages we got from the old base * Install ca-certificates with the initial batch * Adjust test-container build job (cherry picked from commit 0b3eb0494e130b4b0781b774c47d04bac05df7f8) > test-container docker image is unstable due to dependencies > --- > > Key: GEODE-9192 > URL: https://issues.apache.org/jira/browse/GEODE-9192 > Project: Geode > Issue Type: Bug > Components: ci >Affects Versions: 1.12.2, 1.13.2 >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > buildpack-scm, a docker image that our test container relies on, has become > unstable. This has caused problems for mass-test. Replace the base image with > ubuntu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9192) test-container docker image is unstable due to dependencies
[ https://issues.apache.org/jira/browse/GEODE-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333460#comment-17333460 ] ASF subversion and git services commented on GEODE-9192: Commit c671f2e4fca47ff69ffb04c96d12df2b25b19958 in geode's branch refs/heads/support/1.13 from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c671f2e ] GEODE-9192: test-container fixes (#6381) * Use ubuntu as the base * Install packages we got from the old base * Install ca-certificates with the initial batch * Adjust test-container build job (cherry picked from commit 0b3eb0494e130b4b0781b774c47d04bac05df7f8) > test-container docker image is unstable due to dependencies > --- > > Key: GEODE-9192 > URL: https://issues.apache.org/jira/browse/GEODE-9192 > Project: Geode > Issue Type: Bug > Components: ci >Affects Versions: 1.12.2, 1.13.2 >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > buildpack-scm, a docker image that our test container relies on, has become > unstable. This has caused problems for mass-test. Replace the base image with > ubuntu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9192) test-container docker image is unstable due to dependencies
[ https://issues.apache.org/jira/browse/GEODE-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333458#comment-17333458 ] ASF subversion and git services commented on GEODE-9192: Commit 7322395d50aa0205ef63d6fce98863dff8f1f47e in geode's branch refs/heads/support/1.14 from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7322395 ] GEODE-9192: test-container fixes (#6381) * Use ubuntu as the base * Install packages we got from the old base * Install ca-certificates with the initial batch * Adjust test-container build job (cherry picked from commit 0b3eb0494e130b4b0781b774c47d04bac05df7f8) > test-container docker image is unstable due to dependencies > --- > > Key: GEODE-9192 > URL: https://issues.apache.org/jira/browse/GEODE-9192 > Project: Geode > Issue Type: Bug > Components: ci >Affects Versions: 1.12.2, 1.13.2 >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > buildpack-scm, a docker image that our test container relies on, has become > unstable. This has caused problems for mass-test. Replace the base image with > ubuntu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333454#comment-17333454
]
Geode Integration commented on GEODE-9069:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#63.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/63.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0759/test-results/distributedTest/1618944646/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0759/test-artifacts/1618944646/distributedtestfiles-OpenJDK8-1.14.0-build.0759.tgz].
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
>
[jira] [Commented] (GEODE-9192) test-container docker image is unstable due to dependencies
[ https://issues.apache.org/jira/browse/GEODE-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333453#comment-17333453 ] ASF subversion and git services commented on GEODE-9192: Commit 0b3eb0494e130b4b0781b774c47d04bac05df7f8 in geode's branch refs/heads/develop from Sean Goller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0b3eb04 ] GEODE-9192: test-container fixes (#6381) * Use ubuntu as the base * Install packages we got from the old base * Install ca-certificates with the initial batch * Adjust test-container build job > test-container docker image is unstable due to dependencies > --- > > Key: GEODE-9192 > URL: https://issues.apache.org/jira/browse/GEODE-9192 > Project: Geode > Issue Type: Bug > Components: ci >Affects Versions: 1.12.2, 1.13.2 >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > buildpack-scm, a docker image that our test container relies on, has become > unstable. This has caused problems for mass-test. Replace the base image with > ubuntu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6337) Rolling upgrade test fails on JDK11 in CI (sometimes)
[
https://issues.apache.org/jira/browse/GEODE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333450#comment-17333450
]
Geode Integration commented on GEODE-6337:
--
Seen on support/1.14 in [UpgradeTestOpenJDK8
#59|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/UpgradeTestOpenJDK8/builds/59]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0759/test-results/upgradeTest/1618883973/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0759/test-artifacts/1618883973/upgradetestfiles-OpenJDK8-1.14.0-build.0759.tgz].
> Rolling upgrade test fails on JDK11 in CI (sometimes)
> -
>
> Key: GEODE-6337
> URL: https://issues.apache.org/jira/browse/GEODE-6337
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.9.0
>Reporter: Bill Burcham
>Priority: Major
> Labels: flaky, jdk11
>
> In this build:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/333
> {{RollingUpgradeRollLocatorsWithOldServer.testRollLocatorsWithOldServer()}}
> fails, apparently trying to start up Geode version 1.3.0.
> Have a look at the first two errors in the test output:
> {noformat}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollLocatorsWithOldServer
> > testRollLocatorsWithOldServer[from_v130] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.VM$$Lambda$157/0x000840246c40.run in VM 1
> running on Host f634ce7e984c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:537)
> at org.apache.geode.test.dunit.VM.bounce(VM.java:497)
> at org.apache.geode.test.dunit.VM.bounce(VM.java:476)
> at
> org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:85)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollLocatorsWithOldServer.testRollLocatorsWithOldServer(RollingUpgradeRollLocatorsWithOldServer.java:39)
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161)
> at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source)
> at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:530)
> ... 4 more
> Caused by:
> java.io.EOFException
> at java.io.DataInputStream.readByte(DataInputStream.java:272)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222)
> ... 9 more
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host
> f634ce7e984c with 4 VMs
> Caused by:
> java.lang.IllegalStateException: VM not available: VM 1 running on
> Host f634ce7e984c with 4 VMs
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollLocatorsWithOldServer
> > testRollLocatorsWithOldServer[from_v150] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.VM$$Lambda$156/0x000840247040.call in VM 1
> running on Host f634ce7e984c with 4 VMs
> Caused by:
> java.rmi.ConnectException: Connection refused to host: 172.17.0.4;
> nested exception is:
> java.net.ConnectException: Connection refused (Connection
> refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host
> f634ce7e984c with 4 VMs
> Caused by:
> java.rmi.ConnectException: Connection refused to host: 172.17.0.4;
> nested exception is:
> java.net.ConnectException: Connection refused (Connection
> refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> {noformat}
> Notice that the first exception is caused by an EOF whereas the second one is
> "connection refused".
> Dunno what version of Geode was running on that JVM when the attempt to
> bounce to 1.3.0 was made. But you can see in
[jira] [Commented] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333445#comment-17333445
]
Geode Integration commented on GEODE-9071:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#46|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/46]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0733/test-results/distributedTest/1617144407/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0733/test-artifacts/1617144407/distributedtestfiles-OpenJDK8-1.14.0-build.0733.tgz].
> CI Failure: PartitionedRegionCqQueryDUnitTest >
> testRemoveAllWithCQLocalDestroy
> ---
>
> Key: GEODE-9071
> URL: https://issues.apache.org/jira/browse/GEODE-9071
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: Jens Deppe
>Priority: Major
>
> {noformat}
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest >
> testRemoveAllWithCQLocalDestroy FAILED
> 10:10:22org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest$$Lambda$87/434016892.run
> in VM 2 running on Host bb8c1d338b8b with 4 VMs
> 10:10:22at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 10:10:22at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 10:10:22at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testRemoveAllWithCQLocalDestroy(PartitionedRegionCqQueryDUnitTest.java:243)
> 10:10:22
> 10:10:22Caused by:
> 10:10:22org.junit.ComparisonFailure: expected:<[999]> but was:<[645]>
> 10:10:22at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 10:10:22at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 10:10:22at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 10:10:22at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.lambda$testRemoveAllWithCQLocalDestroy$c93719d5$3(PartitionedRegionCqQueryDUnitTest.java:251)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-results/distributedTest/1616696789/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-artifacts/1616696789/distributedtestfiles-OpenJDK8-1.15.0-build.0082.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333438#comment-17333438
]
Geode Integration commented on GEODE-9069:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#35|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/35]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0720/test-results/distributedTest/1616473924/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0720/test-artifacts/1616473924/distributedtestfiles-OpenJDK8-1.14.0-build.0720.tgz].
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
>
[jira] [Updated] (GEODE-9192) test-container docker image is unstable due to dependencies
[ https://issues.apache.org/jira/browse/GEODE-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9192: -- Labels: pull-request-available (was: ) > test-container docker image is unstable due to dependencies > --- > > Key: GEODE-9192 > URL: https://issues.apache.org/jira/browse/GEODE-9192 > Project: Geode > Issue Type: Bug > Components: ci >Affects Versions: 1.12.2, 1.13.2 >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > buildpack-scm, a docker image that our test container relies on, has become > unstable. This has caused problems for mass-test. Replace the base image with > ubuntu. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6413) CI Failure: Bind Exception during ClusterCommunicationsDUnitTest.performARollingUpgrade
[
https://issues.apache.org/jira/browse/GEODE-6413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333434#comment-17333434
]
Geode Integration commented on GEODE-6413:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#27|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/27]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0711/test-results/distributedTest/1615916275/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0711/test-artifacts/1615916275/distributedtestfiles-OpenJDK8-1.14.0-build.0711.tgz].
> CI Failure: Bind Exception during
> ClusterCommunicationsDUnitTest.performARollingUpgrade
> ---
>
> Key: GEODE-6413
> URL: https://issues.apache.org/jira/browse/GEODE-6413
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Benjamin P Ross
>Priority: Major
> Fix For: 1.9.0
>
>
> Stack Trace:
> {noformat}
> org.apache.geode.ClusterCommunicationsDUnitTest >
> performARollingUpgrade[SHARED_CONNECTIONS] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> c4dd6cb2c206 with 3 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at
> org.apache.geode.ClusterCommunicationsDUnitTest.performARollingUpgrade(ClusterCommunicationsDUnitTest.java:214)
> Caused by:
> java.net.BindException: Failed to create server socket on
> c4dd6cb2c206/172.17.0.16[43969]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:756)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:714)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:680)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.initializeServerSocket(TcpServer.java:225)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.startServerThread(TcpServer.java:215)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:210)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:501)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:557)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:340)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:252)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139)
> at
> org.apache.geode.ClusterCommunicationsDUnitTest.lambda$null$1(ClusterCommunicationsDUnitTest.java:220)
> Caused by:
> java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:753)
> ... 11 more
> {noformat}
> This test may be fixed with a longer await() timeout.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8907) CI Failure: ClientServerTransactionCCEDUnitTest.testTxRemoveAll
[
https://issues.apache.org/jira/browse/GEODE-8907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333432#comment-17333432
]
Geode Integration commented on GEODE-8907:
--
Seen on support/1.14 in [DistributedTestOpenJDK11
#23|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK11/builds/23]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0711/test-results/distributedTest/1615915936/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0711/test-artifacts/1615915936/distributedtestfiles-OpenJDK11-1.14.0-build.0711.tgz].
> CI Failure: ClientServerTransactionCCEDUnitTest.testTxRemoveAll
> ---
>
> Key: GEODE-8907
> URL: https://issues.apache.org/jira/browse/GEODE-8907
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Assignee: Louis R. Jacome
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/794]
> reported a test failure
>
> {noformat}
> org.apache.geode.internal.cache.ClientServerTransactionCCEDUnitTest >
> testTxRemoveAll FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$34.call in VM 2
> running on Host c44a375b0bbd with 4 VMs
> Caused by:
> java.lang.IllegalStateException: Thread does not have an active
> transaction
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$2.call in VM 0
> running on Host c44a375b0bbd with 4 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 3 ms:
> {noformat}
>
> Logs available at
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0655/test-results/distributedTest/1612232803/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0655/test-artifacts/1612232803/distributedtestfiles-OpenJDK8-1.14.0-build.0655.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9198) Keystore/truststore file watcher does not follow symbolic links
[ https://issues.apache.org/jira/browse/GEODE-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9198: -- Labels: pull-request-available (was: ) > Keystore/truststore file watcher does not follow symbolic links > --- > > Key: GEODE-9198 > URL: https://issues.apache.org/jira/browse/GEODE-9198 > Project: Geode > Issue Type: Bug >Reporter: Aaron Lindsey >Priority: Major > Labels: pull-request-available > > GEODE-9017 introduced a file watching key/trust manager to automatically > reload the key and trust store upon change. However, the file watcher was > configured to not follow symbolic links. Some environments such as Kubernetes > use symbolic links to mount files inside a container file system. In cases > like this (where the key and trust store are represented using symbolic > links) the file watcher should follow these links and reload the key and > trust store when the underlying target file changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333431#comment-17333431
]
Geode Integration commented on GEODE-7017:
--
Seen on support/1.14 in [AcceptanceTestOpenJDK8
#23|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/AcceptanceTestOpenJDK8/builds/23]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0711/test-results/acceptanceTest/1615913454/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0711/test-artifacts/1615913454/acceptancetestfiles-OpenJDK8-1.14.0-build.0711.tgz].
> CI failure:
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored
> ---
>
> Key: GEODE-7017
> URL: https://issues.apache.org/jira/browse/GEODE-7017
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Mark Hanson
>Priority: Major
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628.tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> 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.ServerStartupValueRecoveryNotificationTest.persistentRegionThatRequiresValueRecovery(ServerStartupValueRecoveryNotificationTest.java:120)
> {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.3.4#803005)
[jira] [Commented] (GEODE-8400) NullPointerException in AbstractCommitSessionValve.commitSession
[
https://issues.apache.org/jira/browse/GEODE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333430#comment-17333430
]
Geode Integration commented on GEODE-8400:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#21|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/21]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0705/test-results/distributedTest/1615487352/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0705/test-artifacts/1615487352/distributedtestfiles-OpenJDK8-1.14.0-build.0705.tgz].
> NullPointerException in AbstractCommitSessionValve.commitSession
>
>
> Key: GEODE-8400
> URL: https://issues.apache.org/jira/browse/GEODE-8400
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Eric Shu
>Priority: Major
>
> {noformat}
> java.lang.RuntimeException:
> /home/geode/geode/geode-assembly/build/distributedTest329/cargo_logs/TOMCAT8_client-server_attributesCanBeReplaced_0_d46a2c34-8a55-4c2f-9789-01bd35afb728/container.log
> contains java.lang.NullPointerException
> at
> org.apache.geode.session.tests.LogChecker.checkLogs(LogChecker.java:87)
> at
> org.apache.geode.session.tests.LogChecker.checkLogs(LogChecker.java:44)
> at
> org.apache.geode.session.tests.CargoTestBase.checkLogs(CargoTestBase.java:412)
> at
> org.apache.geode.session.tests.CargoTestBase.attributesCanBeReplaced(CargoTestBase.java:406)
> 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.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:138)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> 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)
> {noformat}
> The NPE occurs here:
> {noformat}
> Aug 02, 2020 4:45:10 AM org.apache.coyote.http11.Http11Processor service
> SEVERE: Error processing request
> java.lang.NullPointerException
> at
> org.apache.geode.modules.session.catalina.AbstractCommitSessionValve.commitSession(AbstractCommitSessionValve.java:61)
> at
> org.apache.geode.modules.session.catalina.Tomcat8CommitSessionValve.lambda$wrapResponse$0(Tomcat8CommitSessionValve.java:45)
> at
> org.apache.geode.modules.session.catalina.Tomcat8CommitSessionOutputBuffer.doWrite(Tomcat8CommitSessionOutputBuffer.java:48)
> at org.apache.coyote.Response.doWrite(Response.java:600)
> at
> org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:360)
> at
> org.apache.catalina.connector.OutputBuffer.flushByteBuffer(OutputBuffer.java:841)
> at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)
> at
> org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:272)
> at
> org.apache.catalina.connector.Response.finishResponse(Response.java:444)
> at
>
[jira] [Commented] (GEODE-8907) CI Failure: ClientServerTransactionCCEDUnitTest.testTxRemoveAll
[
https://issues.apache.org/jira/browse/GEODE-8907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333428#comment-17333428
]
Geode Integration commented on GEODE-8907:
--
Seen on support/1.14 in [DistributedTestOpenJDK8
#18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/18]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0703/test-results/distributedTest/1615235826/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0703/test-artifacts/1615235826/distributedtestfiles-OpenJDK8-1.14.0-build.0703.tgz].
> CI Failure: ClientServerTransactionCCEDUnitTest.testTxRemoveAll
> ---
>
> Key: GEODE-8907
> URL: https://issues.apache.org/jira/browse/GEODE-8907
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Assignee: Louis R. Jacome
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/794]
> reported a test failure
>
> {noformat}
> org.apache.geode.internal.cache.ClientServerTransactionCCEDUnitTest >
> testTxRemoveAll FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$34.call in VM 2
> running on Host c44a375b0bbd with 4 VMs
> Caused by:
> java.lang.IllegalStateException: Thread does not have an active
> transaction
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.RemoteTransactionDUnitTest$2.call in VM 0
> running on Host c44a375b0bbd with 4 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 3 ms:
> {noformat}
>
> Logs available at
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0655/test-results/distributedTest/1612232803/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0655/test-artifacts/1612232803/distributedtestfiles-OpenJDK8-1.14.0-build.0655.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8056) CI: ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED
[ https://issues.apache.org/jira/browse/GEODE-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333426#comment-17333426 ] Geode Integration commented on GEODE-8056: -- Seen on support/1.14 in [DistributedTestOpenJDK8 #16|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/16] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0702/test-results/distributedTest/1615064388/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0702/test-artifacts/1615064388/distributedtestfiles-OpenJDK8-1.14.0-build.0702.tgz]. > CI: > ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled > FAILED > --- > > Key: GEODE-8056 > URL: https://issues.apache.org/jira/browse/GEODE-8056 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.12.0 >Reporter: Jinmei Liao >Priority: Major > > Happened once: > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/111#A > org.apache.geode.internal.cache.ReplicateEntryIdleExpirationDistributedTest > > readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ReplicateEntryIdleExpirationDistributedTest$$Lambda$55/10096754.run > in VM 0 running on Host debd6ade8357 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610) > at org.apache.geode.test.dunit.VM.invoke(VM.java:437) > at > org.apache.geode.internal.cache.ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled(ReplicateEntryIdleExpirationDistributedTest.java:197) > Caused by: > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > 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.internal.cache.ReplicateEntryIdleExpirationDistributedTest.lambda$readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled$a3e1e98a$5(ReplicateEntryIdleExpirationDistributedTest.java:207) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8056) CI: ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED
[ https://issues.apache.org/jira/browse/GEODE-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333425#comment-17333425 ] Geode Integration commented on GEODE-8056: -- Seen on support/1.14 in [DistributedTestOpenJDK8 #13|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/DistributedTestOpenJDK8/builds/13] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0699/test-results/distributedTest/1614904569/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0699/test-artifacts/1614904569/distributedtestfiles-OpenJDK8-1.14.0-build.0699.tgz]. > CI: > ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled > FAILED > --- > > Key: GEODE-8056 > URL: https://issues.apache.org/jira/browse/GEODE-8056 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.12.0 >Reporter: Jinmei Liao >Priority: Major > > Happened once: > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/111#A > org.apache.geode.internal.cache.ReplicateEntryIdleExpirationDistributedTest > > readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ReplicateEntryIdleExpirationDistributedTest$$Lambda$55/10096754.run > in VM 0 running on Host debd6ade8357 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610) > at org.apache.geode.test.dunit.VM.invoke(VM.java:437) > at > org.apache.geode.internal.cache.ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled(ReplicateEntryIdleExpirationDistributedTest.java:197) > Caused by: > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > 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.internal.cache.ReplicateEntryIdleExpirationDistributedTest.lambda$readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled$a3e1e98a$5(ReplicateEntryIdleExpirationDistributedTest.java:207) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9199) Restructure dunit tests to work with compatible with Redis cluster mode
[ https://issues.apache.org/jira/browse/GEODE-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison updated GEODE-9199: -- Summary: Restructure dunit tests to work with compatible with Redis cluster mode (was: restructure Dunit Tests to work with Compatible with Redis Cluster Mode ) > Restructure dunit tests to work with compatible with Redis cluster mode > > > Key: GEODE-9199 > URL: https://issues.apache.org/jira/browse/GEODE-9199 > Project: Geode > Issue Type: Task > Components: redis >Reporter: John Hutchison >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9199) restructure Dunit Tests to work with Compatible with Redis Cluster Mode
John Hutchison created GEODE-9199: - Summary: restructure Dunit Tests to work with Compatible with Redis Cluster Mode Key: GEODE-9199 URL: https://issues.apache.org/jira/browse/GEODE-9199 Project: Geode Issue Type: Task Components: redis Reporter: John Hutchison -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9198) Keystore/truststore file watcher does not follow symbolic links
Aaron Lindsey created GEODE-9198: Summary: Keystore/truststore file watcher does not follow symbolic links Key: GEODE-9198 URL: https://issues.apache.org/jira/browse/GEODE-9198 Project: Geode Issue Type: Bug Reporter: Aaron Lindsey GEODE-9017 introduced a file watching key/trust manager to automatically reload the key and trust store upon change. However, the file watcher was configured to not follow symbolic links. Some environments such as Kubernetes use symbolic links to mount files inside a container file system. In cases like this (where the key and trust store are represented using symbolic links) the file watcher should follow these links and reload the key and trust store when the underlying target file changes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin P Ross resolved GEODE-8990.
Fix Version/s: 1.15.0
Resolution: Fixed
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9195) Remove redundant local locking from PartitionedRegionClear
[
https://issues.apache.org/jira/browse/GEODE-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-9195:
Assignee: Kirk Lund
> Remove redundant local locking from PartitionedRegionClear
> --
>
> Key: GEODE-9195
> URL: https://issues.apache.org/jira/browse/GEODE-9195
> Project: Geode
> Issue Type: Improvement
> Components: regions
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI
>
> Existing behavior:
> PR clear unconditionally acquires a global lock and also acquires local locks
> on all buckets before doing clear.
> Expected behavior:
> Now that PR clear acquires a global lock, it no longer needs to acquire local
> locks on all buckets before doing clear.
> Solution:
> Remove the logic taking lock in individual nodes in:
> {noformat}
> DistributedRegion.obtainWriteLocksForClear()
> {noformat}
> Remove:
> {noformat}
> if (!localLockedAlready) {
> lockLocallyForClear(getDistributionManager(), getMyId(), regionEvent);
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9193) PING message "leaked" at shutdown due to bad singleton implementation
[
https://issues.apache.org/jira/browse/GEODE-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1771#comment-1771
]
ASF GitHub Bot commented on GEODE-9193:
---
pdxcodemonkey commented on pull request #792:
URL: https://github.com/apache/geode-native/pull/792#issuecomment-827748183
Converting to draft for the moment, trying to nail down what's going on with
CI failures.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> PING message "leaked" at shutdown due to bad singleton implementation
> -
>
> Key: GEODE-9193
> URL: https://issues.apache.org/jira/browse/GEODE-9193
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Assignee: Blake Bender
>Priority: Major
> Labels: pull-request-available
>
> There is a micro-optimization in the native client to prevent creating and
> tearing down PING messages multiple times, since this message always has the
> same format. Unfortunately, the implementation uses a pointer, rather than a
> reference, so exactly one instance of TcrMessagePing is allocated on the
> heap, and the object is never deleted, making it appear as a leak in any
> leak-tracking tool.
> {code:java}
> TcrMessagePing* TcrMessage::getPingMessage(CacheImpl* cacheImpl) {
> static auto pingMsg = new TcrMessagePing(new
> DataOutput(cacheImpl->createDataOutput()), true);
> return pingMsg;
> } {code}
> Changing this from a pointer to a const reference will allow the object to be
> destructed properly at shutdown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9172) Add Junit rule to start docker-based redis cluster
[ https://issues.apache.org/jira/browse/GEODE-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1764#comment-1764 ] ASF subversion and git services commented on GEODE-9172: Commit 3daa950def82d1b27ba6b2122680614af2bdc410 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3daa950 ] GEODE-9172: Add Junit rule to start docker-based redis cluster (#6379) The fun part here is that some redis commands will respond with internal IP addresses which need to be rewritten so that clients are able to make use of them. Currently CLUSTER SLOTS and CLUSTER NODES are implemented with this functionality. > Add Junit rule to start docker-based redis cluster > -- > > Key: GEODE-9172 > URL: https://issues.apache.org/jira/browse/GEODE-9172 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9138) Add warning in server logs when data event is ignored as a duplicate
[ https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1759#comment-1759 ] ASF subversion and git services commented on GEODE-9138: Commit bdfa217667a9b8af6bef50ad602e3fb73e8ca7b7 in geode's branch refs/heads/feature/GEODE-9138 from Barry Oglesby [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bdfa217 ] GEODE-9138: Modified hasSeenEvent to log the message if necessary and increment a stat > Add warning in server logs when data event is ignored as a duplicate > > > Key: GEODE-9138 > URL: https://issues.apache.org/jira/browse/GEODE-9138 > Project: Geode > Issue Type: Bug > Components: client/server, logging >Reporter: Diane Hardman >Priority: Major > Labels: pull-request-available > > Under certain rare conditions, a client may send or resend a data event with > an eventId that causes the server to interpret it as a duplicate event and > discard it. > It is currently impossible to trace when this happens without extra logging > added. > From Barry: > No, if the server thinks it has seen the event, it silently eats it. See > DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it. > The log message that tracks this behavior in the server needs to be added > permanently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1753#comment-1753
]
ASF subversion and git services commented on GEODE-8990:
Commit 3d12601a2b02db89591e64400a728aa6fd734efd in geode's branch
refs/heads/develop from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3d12601 ]
GEODE-8990: Add await logic to prevent CargoTestBase tests from running before
members (#6355)
* GEODE-8990: Cleaning up a flaky DUnit test.
Co-authored-by: Mark Hanson
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1752#comment-1752
]
ASF subversion and git services commented on GEODE-8990:
Commit 3d12601a2b02db89591e64400a728aa6fd734efd in geode's branch
refs/heads/develop from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3d12601 ]
GEODE-8990: Add await logic to prevent CargoTestBase tests from running before
members (#6355)
* GEODE-8990: Cleaning up a flaky DUnit test.
Co-authored-by: Mark Hanson
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8971) Batches with incomplete transactions when stopping the gateway sender
[ https://issues.apache.org/jira/browse/GEODE-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1716#comment-1716 ] Geode Integration commented on GEODE-8971: -- Seen in [DistributedTestOpenJDK8 #151.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz]. > Batches with incomplete transactions when stopping the gateway sender > - > > Key: GEODE-8971 > URL: https://issues.apache.org/jira/browse/GEODE-8971 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.14.0 >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When the gateway sender is stopped there is a high probability that batches > with incomplete transactions are sent even if group-transaction-events is > enabled. > The reason is that once the stop command reaches the gateway sender, it > immediately stops queueing events, and this could happen in the middle of > receiving events for the same transaction. If this is the case, some events > for the transaction may have reached the queue right before the stop command > was received and the rest of events for that transaction would not make it to > the queue (they would be dropped) because they arrived right after the stop > command was received at the gateway sender. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-8971) Batches with incomplete transactions when stopping the gateway sender
[ https://issues.apache.org/jira/browse/GEODE-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1717#comment-1717 ] John Hutchison edited comment on GEODE-8971 at 4/27/21, 2:51 PM: - test failure seen again in run https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1 (unclear if this is reoccurrence of same issue or a new bug) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz was (Author: john hutch): test failure seen again in run https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz > Batches with incomplete transactions when stopping the gateway sender > - > > Key: GEODE-8971 > URL: https://issues.apache.org/jira/browse/GEODE-8971 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.14.0 >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When the gateway sender is stopped there is a high probability that batches > with incomplete transactions are sent even if group-transaction-events is > enabled. > The reason is that once the stop command reaches the gateway sender, it > immediately stops queueing events, and this could happen in the middle of > receiving events for the same transaction. If this is the case, some events > for the transaction may have reached the queue right before the stop command > was received and the rest of events for that transaction would not make it to > the queue (they would be dropped) because they arrived right after the stop > command was received at the gateway sender. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-8971) Batches with incomplete transactions when stopping the gateway sender
[ https://issues.apache.org/jira/browse/GEODE-8971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison reopened GEODE-8971: --- test failure seen again in run https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.1 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618550176/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618550176/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz > Batches with incomplete transactions when stopping the gateway sender > - > > Key: GEODE-8971 > URL: https://issues.apache.org/jira/browse/GEODE-8971 > Project: Geode > Issue Type: Improvement > Components: wan >Affects Versions: 1.14.0 >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When the gateway sender is stopped there is a high probability that batches > with incomplete transactions are sent even if group-transaction-events is > enabled. > The reason is that once the stop command reaches the gateway sender, it > immediately stops queueing events, and this could happen in the middle of > receiving events for the same transaction. If this is the case, some events > for the transaction may have reached the queue right before the stop command > was received and the rest of events for that transaction would not make it to > the queue (they would be dropped) because they arrived right after the stop > command was received at the gateway sender. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1711#comment-1711
]
Geode Integration commented on GEODE-9070:
--
Seen in [DistributedTestOpenJDK8
#161.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/161.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0160/test-results/distributedTest/1619490122/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0160/test-artifacts/1619490122/distributedtestfiles-OpenJDK8-1.15.0-build.0160.tgz].
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Reporter: Jens Deppe
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1708#comment-1708
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#163.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/163.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-results/distributedTest/1619495125/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-artifacts/1619495125/distributedtestfiles-OpenJDK8-1.15.0-build.0161.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1707#comment-1707
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#161.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/161.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0160/test-results/distributedTest/1619490122/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0160/test-artifacts/1619490122/distributedtestfiles-OpenJDK8-1.15.0-build.0160.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1706#comment-1706
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#151.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/151.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-results/distributedTest/1618560377/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0145/test-artifacts/1618560377/distributedtestfiles-OpenJDK8-1.15.0-build.0145.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8990) CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
[
https://issues.apache.org/jira/browse/GEODE-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1703#comment-1703
]
Geode Integration commented on GEODE-8990:
--
Seen in [DistributedTestOpenJDK8
#163.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/163.2]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-results/distributedTest/1619518305/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0161/test-artifacts/1619518305/distributedtestfiles-OpenJDK8-1.15.0-build.0161.tgz].
> CI Failure: Jetty9CachingClientServerTest.shouldCacheSessionOnClient
>
>
> Key: GEODE-8990
> URL: https://issues.apache.org/jira/browse/GEODE-8990
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {noformat}
> org.apache.geode.session.tests.Jetty9CachingClientServerTest >
> shouldCacheSessionOnClient FAILED
> org.junit.ComparisonFailure: expected:<[Foo]> but was:<[bogus]>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.geode.session.tests.Jetty9CachingClientServerTest.shouldCacheSessionOnClient(Jetty9CachingClientServerTest.java:65)
> 371 tests completed, 1 failed
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-results/distributedTest/1614646829/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0023/test-artifacts/1614646829/distributedtestfiles-OpenJDK8-1.15.0-build.0023.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-5337) Geode1.5 end-port is not exclusive when creating a gateway-receiver
[
https://issues.apache.org/jira/browse/GEODE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-5337.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> Geode1.5 end-port is not exclusive when creating a gateway-receiver
>
>
> Key: GEODE-5337
> URL: https://issues.apache.org/jira/browse/GEODE-5337
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Cui Chenxiao
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> When created, a gateway-receiver shall be assign a range of port to use.
> In document
> [http://geode.apache.org/docs/guide/16/tools_modules/gfsh/command-pages/create.html#topic_a4x_pb1_dk],
> the description for --end-port says "The {{ENDPORT}} value is exclusive
> while the {{STARTPORT}} value is inclusive. ".
>
> However, sometimes, the port number of endport is also assigned to receiver
> anyway. Besides, in code for gatewayreceiver, the endport will be randomly
> assigned to receiver.
>
> I supposed this shall be a document bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-5337) Geode1.5 end-port is not exclusive when creating a gateway-receiver
[
https://issues.apache.org/jira/browse/GEODE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333004#comment-17333004
]
ASF subversion and git services commented on GEODE-5337:
Commit 9d577cfa1abd3936140077196c9dcec37d70d445 in geode's branch
refs/heads/develop from Alberto Bustamante Reyes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9d577cf ]
GEODE-5337: End-port is not exclusive when creating a gw receiver (#6370)
> Geode1.5 end-port is not exclusive when creating a gateway-receiver
>
>
> Key: GEODE-5337
> URL: https://issues.apache.org/jira/browse/GEODE-5337
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Cui Chenxiao
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
>
> When created, a gateway-receiver shall be assign a range of port to use.
> In document
> [http://geode.apache.org/docs/guide/16/tools_modules/gfsh/command-pages/create.html#topic_a4x_pb1_dk],
> the description for --end-port says "The {{ENDPORT}} value is exclusive
> while the {{STARTPORT}} value is inclusive. ".
>
> However, sometimes, the port number of endport is also assigned to receiver
> anyway. Besides, in code for gatewayreceiver, the endport will be randomly
> assigned to receiver.
>
> I supposed this shall be a document bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
