[jira] [Created] (GEODE-8111) Fix create gateway-receiver --manual-start doc
Alberto Bustamante Reyes created GEODE-8111: --- Summary: Fix create gateway-receiver --manual-start doc Key: GEODE-8111 URL: https://issues.apache.org/jira/browse/GEODE-8111 Project: Geode Issue Type: Improvement Components: docs Reporter: Alberto Bustamante Reyes Documentation of "--manual-start" option of "create gateway-receiver" gfsh command wrongly states that the default option is "true". But taking a look at the code it can be verified that the default option is false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8111) Fix create gateway-receiver --manual-start doc
[ https://issues.apache.org/jira/browse/GEODE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-8111: Priority: Minor (was: Major) > Fix create gateway-receiver --manual-start doc > -- > > Key: GEODE-8111 > URL: https://issues.apache.org/jira/browse/GEODE-8111 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Priority: Minor > > Documentation of "--manual-start" option of "create gateway-receiver" gfsh > command wrongly states that the default option is "true". > But taking a look at the code it can be verified that the default option is > false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8111) Fix create gateway-receiver --manual-start doc
[ https://issues.apache.org/jira/browse/GEODE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-8111: --- Assignee: Alberto Bustamante Reyes > Fix create gateway-receiver --manual-start doc > -- > > Key: GEODE-8111 > URL: https://issues.apache.org/jira/browse/GEODE-8111 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > > Documentation of "--manual-start" option of "create gateway-receiver" gfsh > command wrongly states that the default option is "true". > But taking a look at the code it can be verified that the default option is > false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8111) Fix create gateway-receiver --manual-start doc
[ https://issues.apache.org/jira/browse/GEODE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-8111: Labels: pull-request-available (was: ) > Fix create gateway-receiver --manual-start doc > -- > > Key: GEODE-8111 > URL: https://issues.apache.org/jira/browse/GEODE-8111 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > > Documentation of "--manual-start" option of "create gateway-receiver" gfsh > command wrongly states that the default option is "true". > But taking a look at the code it can be verified that the default option is > false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8111) Fix create gateway-receiver --manual-start doc
[ https://issues.apache.org/jira/browse/GEODE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105553#comment-17105553 ] Alberto Bustamante Reyes commented on GEODE-8111: - PR link was not created automatically, Im adding the link > Fix create gateway-receiver --manual-start doc > -- > > Key: GEODE-8111 > URL: https://issues.apache.org/jira/browse/GEODE-8111 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > > Documentation of "--manual-start" option of "create gateway-receiver" gfsh > command wrongly states that the default option is "true". > But taking a look at the code it can be verified that the default option is > false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8091) AuthenticationRequiredException: Failed to find the authenticated user" at startup when trying to start locator
[ https://issues.apache.org/jira/browse/GEODE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105557#comment-17105557 ] ASF subversion and git services commented on GEODE-8091: Commit 36b2f397e2a72fe9f9a27b30e6a9be9b3d5049c1 in geode's branch refs/heads/support/1.12 from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=36b2f39 ] GEODE-8091: fix AuthenticationRequiredException when starting a locat… (#5071) (cherry picked from commit 4c5788d3b1b37bd284e93fdda4b78486aad7c9b8) > AuthenticationRequiredException: Failed to find the authenticated user" at > startup when trying to start locator > --- > > Key: GEODE-8091 > URL: https://issues.apache.org/jira/browse/GEODE-8091 > Project: Geode > Issue Type: Bug > Components: configuration >Affects Versions: 1.12.0 >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.13.0 > > > when starting up a locator using --dir (the dir would have a cluster_config > directory that would have some jars deployed) and > --load-cluster-configuration-from-dir=true, and the locator has a security > manager, you get the following exception: > gfsh>start locator --name=locator --dir=locator > --load-cluster-configuration-from-dir=true > --properties-file=locator.properties > Starting a Geode Locator in /Users/jiliao/my_geode/tmp/locator.1.10... > The Locator process terminated unexpectedly with exit status 1. Please refer > to the log file in /Users/jiliao/my_geode/tmp/locator.1.10 for full details. > Exception in thread "main" > org.apache.geode.security.AuthenticationRequiredException: Failed to find the > authenticated user. > at > org.apache.geode.internal.security.IntegratedSecurityService.getSubject(IntegratedSecurityService.java:122) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.getDeployedBy(InternalConfigurationPersistenceService.java:853) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.readConfiguration(InternalConfigurationPersistenceService.java:845) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.loadSharedConfigurationFromDir(InternalConfigurationPersistenceService.java:721) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.initSharedConfiguration(InternalConfigurationPersistenceService.java:483) > at > org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1380) > at > org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:779) > at > org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:774) > at > org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:755) > at > org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:386) > at > org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:714) > at > org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:621) > at > org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:215) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8110) CI failure: JMXMBeanReconnectDUnitTest > serverMXBeansAreRestoredOnBothLocatorsAfterCrashedServerReturns failed with IOException
[
https://issues.apache.org/jira/browse/GEODE-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-8110:
Assignee: Kirk Lund
> CI failure: JMXMBeanReconnectDUnitTest >
> serverMXBeansAreRestoredOnBothLocatorsAfterCrashedServerReturns failed with
> IOException
>
>
> Key: GEODE-8110
> URL: https://issues.apache.org/jira/browse/GEODE-8110
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Reporter: Barrett Oglesby
>Assignee: Kirk Lund
>Priority: Major
>
> DistributedTestOpenJDK8 build 158:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/158
> Failed with:
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> serverMXBeansAreRestoredOnBothLocatorsAfterCrashedServerReturns FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 2903
> org.apache.geode.alerting.internal.spi.AlertingIOException:
> java.io.IOException: Cannot form connection to alert listener
> 172.17.0.6(locator2:1:locator):41002
> at
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:881)
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:451)
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:268)
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:182)
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:510)
> at
> org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346)
> at
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2058)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1986)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2023)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083)
> at
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103)
> at
> org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34)
> at
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.IOException: Cannot form connection to alert listener
> 172.17.0.6(locator2:1:locator):41002
> at
> org.apache.geode.internal.tcp.Connection.createSender(Connection.java:978)
> at
> org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:288)
> at
> org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:392)
> at
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:571)
> at
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:800)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-1793) Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
[
https://issues.apache.org/jira/browse/GEODE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105611#comment-17105611
]
Kirk Lund commented on GEODE-1793:
--
Failing intermittently with:
{noformat}
java.io.EOFException: Locator at HostAndPort[d5676dfc4e21:24193] did not
respond. This is normal if the locator was shutdown. If it wasn't check its log
for exceptions.
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:202)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.findCoordinator(GMSJoinLeave.java:1145)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:331)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership.join(GMSMembership.java:573)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership.access$1300(GMSMembership.java:71)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.joinDistributedSystem(GMSMembership.java:1972)
at
org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:242)
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership.start(GMSMembership.java:1851)
at
org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:171)
at
org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
at
org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3033)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
at
org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:743)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:388)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:338)
at org.apache.geode.distributed.Locator.startLocator(Locator.java:252)
at
org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139)
at
org.apache.geode.distributed.LocatorDUnitTest.startLocatorWithPortAndProperties(LocatorDUnitTest.java:1507)
at
org.apache.geode.distributed.LocatorDUnitTest.lambda$startVerifyAndStopLocator$e21733f2$1(LocatorDUnitTest.java:1539)
at
org.apache.geode.test.dunit.internal.IdentifiableRunnable.run(IdentifiableRunnable.java:41)
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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
at
org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EO
[jira] [Commented] (GEODE-8107) GCE instance resource does not sort return values
[ https://issues.apache.org/jira/browse/GEODE-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105619#comment-17105619 ] ASF subversion and git services commented on GEODE-8107: Commit 7ed7caf178339ebf6d43867e7c740c40198f5128 in geode's branch refs/heads/develop from Robert Houghton [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7ed7caf ] GEODE-8107: Sort GCE instances by creationTimestamp for concourse (#5094) Authored-by: Robert Houghton > GCE instance resource does not sort return values > - > > Key: GEODE-8107 > URL: https://issues.apache.org/jira/browse/GEODE-8107 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Robert Houghton >Priority: Major > > The unsorted nature of the `check` script makes the resource not usable in > concourse `check: every` scenario, which we use to stop orphaned/errored GCP > instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8107) GCE instance resource does not sort return values
[ https://issues.apache.org/jira/browse/GEODE-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Houghton resolved GEODE-8107. Fix Version/s: 1.14.0 Resolution: Fixed > GCE instance resource does not sort return values > - > > Key: GEODE-8107 > URL: https://issues.apache.org/jira/browse/GEODE-8107 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Robert Houghton >Priority: Major > Fix For: 1.14.0 > > > The unsorted nature of the `check` script makes the resource not usable in > concourse `check: every` scenario, which we use to stop orphaned/errored GCP > instances. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-1793) Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
[ https://issues.apache.org/jira/browse/GEODE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-1793: - Component/s: membership > Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL > --- > > Key: GEODE-1793 > URL: https://issues.apache.org/jira/browse/GEODE-1793 > Project: Geode > Issue Type: Bug > Components: locator, membership >Reporter: Udo Kohlmeyer >Priority: Minor > > This test fails due to something not cleaning itself properly. Undetermined > what the problem is, but it will run perfectly by itself everytime, but once > run inside of the TestClass it fails -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8112) Need to add a member option in query command
Eric Shu created GEODE-8112: --- Summary: Need to add a member option in query command Key: GEODE-8112 URL: https://issues.apache.org/jira/browse/GEODE-8112 Project: Geode Issue Type: Bug Components: gfsh, querying Reporter: Eric Shu When gfsh query running on replicate proxy region, it will return 0 results as no data stored on the proxy region. To help solving this issue, gfsh querying can add a member option so that query can route to a particular data host member to get the needed results. User can use "describe region" to find out which data host, then use it in the query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8090) Implement function/delta for redis Hash operations used by Spring Session
[ https://issues.apache.org/jira/browse/GEODE-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-8090. - Fix Version/s: 1.14.0 Resolution: Fixed > Implement function/delta for redis Hash operations used by Spring Session > - > > Key: GEODE-8090 > URL: https://issues.apache.org/jira/browse/GEODE-8090 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.14.0 > > > Hash functions needed for Spring session: > * "HGETALL" > * "HMSET" > * "HSET" > * "DEL" (for hashes) > *A.C.* > * hash operations above are making use of functions with delta propagation > * Hash operations _not_ on the above list are minimally functional and > passing tests (performance not important) > * hash operations are passing all existing tests including any Dunit tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8090) Implement function/delta for redis Hash operations used by Spring Session
[ https://issues.apache.org/jira/browse/GEODE-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105639#comment-17105639 ] ASF subversion and git services commented on GEODE-8090: Commit 904a08a6bf64d9ddca6c3f750ffab1e50d6dac14 in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=904a08a ] GEODE-8090: implement function/delta for redis Hash ops (#5085) The hash ops that use function delta now are: HDEL DEL HSET HMSET HSETNX HGETALL > Implement function/delta for redis Hash operations used by Spring Session > - > > Key: GEODE-8090 > URL: https://issues.apache.org/jira/browse/GEODE-8090 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > Hash functions needed for Spring session: > * "HGETALL" > * "HMSET" > * "HSET" > * "DEL" (for hashes) > *A.C.* > * hash operations above are making use of functions with delta propagation > * Hash operations _not_ on the above list are minimally functional and > passing tests (performance not important) > * hash operations are passing all existing tests including any Dunit tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8112) Need to add a member option in query command
[ https://issues.apache.org/jira/browse/GEODE-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-8112: Labels: caching-applications (was: ) > Need to add a member option in query command > > > Key: GEODE-8112 > URL: https://issues.apache.org/jira/browse/GEODE-8112 > Project: Geode > Issue Type: Bug > Components: gfsh, querying >Reporter: Eric Shu >Priority: Major > Labels: caching-applications > > When gfsh query running on replicate proxy region, it will return 0 results > as no data stored on the proxy region. > To help solving this issue, gfsh querying can add a member option so that > query can route to a particular data host member to get the needed results. > User can use "describe region" to find out which data host, then use it in > the query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8112) Need to add a member option in query command
[ https://issues.apache.org/jira/browse/GEODE-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-8112: --- Assignee: Eric Shu > Need to add a member option in query command > > > Key: GEODE-8112 > URL: https://issues.apache.org/jira/browse/GEODE-8112 > Project: Geode > Issue Type: Bug > Components: gfsh, querying >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: caching-applications > > When gfsh query running on replicate proxy region, it will return 0 results > as no data stored on the proxy region. > To help solving this issue, gfsh querying can add a member option so that > query can route to a particular data host member to get the needed results. > User can use "describe region" to find out which data host, then use it in > the query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8091) AuthenticationRequiredException: Failed to find the authenticated user" at startup when trying to start locator
[ https://issues.apache.org/jira/browse/GEODE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105685#comment-17105685 ] ASF subversion and git services commented on GEODE-8091: Commit 15df6a83e315fc9acb73a117b3c74b08eca7b82d in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=15df6a8 ] GEODE-8091: fix AuthenticationRequiredException when starting a locator (#5098) * additional review changes > AuthenticationRequiredException: Failed to find the authenticated user" at > startup when trying to start locator > --- > > Key: GEODE-8091 > URL: https://issues.apache.org/jira/browse/GEODE-8091 > Project: Geode > Issue Type: Bug > Components: configuration >Affects Versions: 1.12.0 >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.13.0 > > > when starting up a locator using --dir (the dir would have a cluster_config > directory that would have some jars deployed) and > --load-cluster-configuration-from-dir=true, and the locator has a security > manager, you get the following exception: > gfsh>start locator --name=locator --dir=locator > --load-cluster-configuration-from-dir=true > --properties-file=locator.properties > Starting a Geode Locator in /Users/jiliao/my_geode/tmp/locator.1.10... > The Locator process terminated unexpectedly with exit status 1. Please refer > to the log file in /Users/jiliao/my_geode/tmp/locator.1.10 for full details. > Exception in thread "main" > org.apache.geode.security.AuthenticationRequiredException: Failed to find the > authenticated user. > at > org.apache.geode.internal.security.IntegratedSecurityService.getSubject(IntegratedSecurityService.java:122) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.getDeployedBy(InternalConfigurationPersistenceService.java:853) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.readConfiguration(InternalConfigurationPersistenceService.java:845) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.loadSharedConfigurationFromDir(InternalConfigurationPersistenceService.java:721) > at > org.apache.geode.distributed.internal.InternalConfigurationPersistenceService.initSharedConfiguration(InternalConfigurationPersistenceService.java:483) > at > org.apache.geode.distributed.internal.InternalLocator.startConfigurationPersistenceService(InternalLocator.java:1380) > at > org.apache.geode.distributed.internal.InternalLocator.startClusterManagementService(InternalLocator.java:779) > at > org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:774) > at > org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:755) > at > org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:386) > at > org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:714) > at > org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:621) > at > org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:215) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8113) Redis: getMap never returns null
Murtuza Boxwala created GEODE-8113: -- Summary: Redis: getMap never returns null Key: GEODE-8113 URL: https://issues.apache.org/jira/browse/GEODE-8113 Project: Geode Issue Type: Improvement Reporter: Murtuza Boxwala We can remove a bunch of null checks because the method `getMap` is guaranteed to not return `null.` -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8114) Redis: refactor set classes to implement RedisSetCommands
Murtuza Boxwala created GEODE-8114: -- Summary: Redis: refactor set classes to implement RedisSetCommands Key: GEODE-8114 URL: https://issues.apache.org/jira/browse/GEODE-8114 Project: Geode Issue Type: Improvement Reporter: Murtuza Boxwala -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-923) CI failure: ConnectionManagerJUnitTest.testIdleExpiration
[
https://issues.apache.org/jira/browse/GEODE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-923:
---
Assignee: (was: Hitesh Khamesra)
> CI failure: ConnectionManagerJUnitTest.testIdleExpiration
> -
>
> Key: GEODE-923
> URL: https://issues.apache.org/jira/browse/GEODE-923
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: CI, Flaky
>
> {noformat}
> Error Message
> java.lang.AssertionError: Elapsed 238 is less than idle timeout 300
> Stacktrace
> java.lang.AssertionError: Elapsed 238 is less than idle timeout 300
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerJUnitTest.testIdleExpiration(ConnectionManagerJUnitTest.java:282)
> 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:497)
> 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.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> 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:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> 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:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
[jira] [Updated] (GEODE-923) CI failure: ConnectionManagerJUnitTest.testIdleExpiration
[
https://issues.apache.org/jira/browse/GEODE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-923:
Fix Version/s: (was: 1.0.0-incubating.M3)
> CI failure: ConnectionManagerJUnitTest.testIdleExpiration
> -
>
> Key: GEODE-923
> URL: https://issues.apache.org/jira/browse/GEODE-923
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Sai Boorlagadda
>Assignee: Hitesh Khamesra
>Priority: Major
> Labels: CI, Flaky
>
> {noformat}
> Error Message
> java.lang.AssertionError: Elapsed 238 is less than idle timeout 300
> Stacktrace
> java.lang.AssertionError: Elapsed 238 is less than idle timeout 300
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at
> com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerJUnitTest.testIdleExpiration(ConnectionManagerJUnitTest.java:282)
> 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:497)
> 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.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> 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:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> 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:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(St
[jira] [Commented] (GEODE-8112) Need to add a member option in query command
[ https://issues.apache.org/jira/browse/GEODE-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105758#comment-17105758 ] ASF subversion and git services commented on GEODE-8112: Commit a75125115eaef071d0b537b40c69425aaca5e653 in geode's branch refs/heads/feature/GEODE-8112 from Eric Shu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a751251 ] GEODE-8112: Add --member option in query command. > Need to add a member option in query command > > > Key: GEODE-8112 > URL: https://issues.apache.org/jira/browse/GEODE-8112 > Project: Geode > Issue Type: Bug > Components: gfsh, querying >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: caching-applications > > When gfsh query running on replicate proxy region, it will return 0 results > as no data stored on the proxy region. > To help solving this issue, gfsh querying can add a member option so that > query can route to a particular data host member to get the needed results. > User can use "describe region" to find out which data host, then use it in > the query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8112) Need to add a member option in query command
[ https://issues.apache.org/jira/browse/GEODE-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag resolved GEODE-8112. Resolution: Fixed > Need to add a member option in query command > > > Key: GEODE-8112 > URL: https://issues.apache.org/jira/browse/GEODE-8112 > Project: Geode > Issue Type: Bug > Components: gfsh, querying >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: caching-applications > > When gfsh query running on replicate proxy region, it will return 0 results > as no data stored on the proxy region. > To help solving this issue, gfsh querying can add a member option so that > query can route to a particular data host member to get the needed results. > User can use "describe region" to find out which data host, then use it in > the query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8115) Transactions failing
Sarah Abbey created GEODE-8115:
--
Summary: Transactions failing
Key: GEODE-8115
URL: https://issues.apache.org/jira/browse/GEODE-8115
Project: Geode
Issue Type: Bug
Components: redis
Reporter: Sarah Abbey
Between these two shas:
7ee1042a8393563b4d7655b8bc2d4a77564b91b5 (test passes)
and
15df6a83e315fc9acb73a117b3c74b08eca7b82d (test fails)
test:
{code:java}
/*
* Supported Transaction commands - DISCARD, EXEC, MULTI
*/
protected void checkTransactionCommands() throws ExecutionException,
InterruptedException {
RedisAsyncCommands asyncCommands = connection.async();
asyncCommands.multi();RedisFuture result1 =
asyncCommands.set("key1", "value1");
RedisFuture result2 = asyncCommands.set("key2", "value2");
RedisFuture result3 = asyncCommands.set("key3", "value3");
Log.getLogWriter().info("exec multiple commands as a transaction: " +
asyncCommands);
RedisFuture execResult = asyncCommands.exec();
TransactionResult transactionResult = execResult.get();
Log.getLogWriter().info("completed exec multiple commands as a transaction:
" + asyncCommands);String firstResult = transactionResult.get(0);
Log.getLogWriter().info("firstResult = " + firstResult);String
secondResult = transactionResult.get(0);
Log.getLogWriter().info("secondResult = " + secondResult);String
thirdResult = transactionResult.get(0);
Log.getLogWriter().info("thirdResult = " + thirdResult);
}
{code}
{code:java}
Unexpected exception java.util.concurrent.ExecutionException:
io.lettuce.core.RedisCommandExecutionException: ERR Cannot resume transaction,
current thread has an active transaction in threadGroup redisClient {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8116) Heritage .NET integration tests can't run in parallel
Jacob Barrett created GEODE-8116: Summary: Heritage .NET integration tests can't run in parallel Key: GEODE-8116 URL: https://issues.apache.org/jira/browse/GEODE-8116 Project: Geode Issue Type: Bug Reporter: Jacob Barrett The heritage .NET integration test framework does not set the JMX manager port for locators in a cluster so when running in parallel the locators join a common JMX manager. When that locator is stopped at the end of its tests it can hang the other clusters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8116) Heritage .NET integration tests can't run in parallel
[ https://issues.apache.org/jira/browse/GEODE-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett reassigned GEODE-8116: Assignee: Jacob Barrett > Heritage .NET integration tests can't run in parallel > - > > Key: GEODE-8116 > URL: https://issues.apache.org/jira/browse/GEODE-8116 > Project: Geode > Issue Type: Bug >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > > The heritage .NET integration test framework does not set the JMX manager > port for locators in a cluster so when running in parallel the locators join > a common JMX manager. When that locator is stopped at the end of its tests it > can hang the other clusters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-7680) Partitioned region clear operations must be successful while interacting with rebalance
[ https://issues.apache.org/jira/browse/GEODE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag reopened GEODE-7680: > Partitioned region clear operations must be successful while interacting with > rebalance > > > Key: GEODE-7680 > URL: https://issues.apache.org/jira/browse/GEODE-7680 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Nabarun Nag >Assignee: Donal Evans >Priority: Major > Labels: GeodeCommons, caching-applications > > Clear operations are successful and while rebalance operations are ongoing. > Acceptance : > * DUnit tests validating the above behavior. > * Test coverage to when a member departs in this scenario > * Test coverage to when a member restarts in this scenario > * Unit tests with complete code coverage for the newly written code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8111) Fix create gateway-receiver --manual-start doc
[ https://issues.apache.org/jira/browse/GEODE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105843#comment-17105843 ] ASF subversion and git services commented on GEODE-8111: Commit 9e90aeebc091831d37b93f86747e99191ecab227 in geode's branch refs/heads/develop from Alberto Bustamante Reyes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9e90aee ] GEODE-8111: Fix create gw receiver --manual-start doc (#5097) > Fix create gateway-receiver --manual-start doc > -- > > Key: GEODE-8111 > URL: https://issues.apache.org/jira/browse/GEODE-8111 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > > Documentation of "--manual-start" option of "create gateway-receiver" gfsh > command wrongly states that the default option is "true". > But taking a look at the code it can be verified that the default option is > false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8111) Fix create gateway-receiver --manual-start doc
[ https://issues.apache.org/jira/browse/GEODE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-8111. Fix Version/s: 1.14.0 Resolution: Fixed > Fix create gateway-receiver --manual-start doc > -- > > Key: GEODE-8111 > URL: https://issues.apache.org/jira/browse/GEODE-8111 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.14.0 > > > Documentation of "--manual-start" option of "create gateway-receiver" gfsh > command wrongly states that the default option is "true". > But taking a look at the code it can be verified that the default option is > false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8117) ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails intermittently
Kirk Lund created GEODE-8117: Summary: ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails intermittently Key: GEODE-8117 URL: https://issues.apache.org/jira/browse/GEODE-8117 Project: Geode Issue Type: Bug Components: tests Reporter: Kirk Lund org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase expected:<[online]> but was:<[not responding]> 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.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:211) at org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:190) at org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:201) at org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:131) at org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:127) at org.apache.geode.distributed.ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile(ServerLauncherRemoteIntegrationTest.java:91) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) 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.junit.rules.Verifier$1.evaluate(Verifier.java:35) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) 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) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dis
[jira] [Assigned] (GEODE-8117) ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-8117:
Assignee: Kirk Lund
> ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails
> intermittently
>
>
> Key: GEODE-8117
> URL: https://issues.apache.org/jira/browse/GEODE-8117
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase
> expected:<[online]> but was:<[not responding]> 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.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:211)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:190)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:201)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:131)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:127)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile(ServerLauncherRemoteIntegrationTest.java:91)
> Caused by: org.junit.ComparisonFailure: expected:<[online]> but was:<[not
> responding]>
> at
> jdk.internal.reflect.GeneratedConstructorAccessor25.newInstance(Unknown
> Source)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:213)
> at
> org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:222)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:209)
> at java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ... 1 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8117) ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-8117:
-
Description:
{noformat}
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a
lambda expression in
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase
expected:<[online]> but was:<[not responding]> 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.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:211)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:190)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:201)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:131)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:127)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile(ServerLauncherRemoteIntegrationTest.java:91)
Caused by: org.junit.ComparisonFailure: expected:<[online]> but was:<[not
responding]>
at
jdk.internal.reflect.GeneratedConstructorAccessor25.newInstance(Unknown Source)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:213)
at
org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
at
org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:222)
at
org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:209)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
... 1 more
{noformat}
was:
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a
lambda expression in
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase
expected:<[online]> but was:<[not responding]> 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.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:211)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:190)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:201)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:131)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:127)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile(ServerLauncherRemoteIntegrationTest.java:91)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
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
[jira] [Commented] (GEODE-8116) Heritage .NET integration tests can't run in parallel
[ https://issues.apache.org/jira/browse/GEODE-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105853#comment-17105853 ] ASF subversion and git services commented on GEODE-8116: Commit 9bc3e0a930fab6d7a58c684bffcb47c9325ba575 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=9bc3e0a ] GEODE-8116: Set JMX manager port. (#600) > Heritage .NET integration tests can't run in parallel > - > > Key: GEODE-8116 > URL: https://issues.apache.org/jira/browse/GEODE-8116 > Project: Geode > Issue Type: Bug >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > > The heritage .NET integration test framework does not set the JMX manager > port for locators in a cluster so when running in parallel the locators join > a common JMX manager. When that locator is stopped at the end of its tests it > can hang the other clusters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8116) Heritage .NET integration tests can't run in parallel
[ https://issues.apache.org/jira/browse/GEODE-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Barrett resolved GEODE-8116. -- Fix Version/s: 1.14.0 Resolution: Fixed > Heritage .NET integration tests can't run in parallel > - > > Key: GEODE-8116 > URL: https://issues.apache.org/jira/browse/GEODE-8116 > Project: Geode > Issue Type: Bug >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Fix For: 1.14.0 > > > The heritage .NET integration test framework does not set the JMX manager > port for locators in a cluster so when running in parallel the locators join > a common JMX manager. When that locator is stopped at the end of its tests it > can hang the other clusters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8068) Revert GEODE-8033 and GEODE-8044
[ https://issues.apache.org/jira/browse/GEODE-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105902#comment-17105902 ] ASF subversion and git services commented on GEODE-8068: Commit 8ec8049d466a375261132e240b6e05480e3ae699 in geode's branch refs/heads/support/1.13 from Udo Kohlmeyer [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8ec8049 ] GEODE-8068 - Revert GEODE-8044 and GEODE-8033. (#5045) (#5104) Co-authored-by: Patrick Johnson > Revert GEODE-8033 and GEODE-8044 > > > Key: GEODE-8068 > URL: https://issues.apache.org/jira/browse/GEODE-8068 > Project: Geode > Issue Type: New Feature >Reporter: Patrick Johnsn >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8033) Create ModuleService Interface
[ https://issues.apache.org/jira/browse/GEODE-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105904#comment-17105904 ] ASF subversion and git services commented on GEODE-8033: Commit 8ec8049d466a375261132e240b6e05480e3ae699 in geode's branch refs/heads/support/1.13 from Udo Kohlmeyer [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8ec8049 ] GEODE-8068 - Revert GEODE-8044 and GEODE-8033. (#5045) (#5104) Co-authored-by: Patrick Johnson > Create ModuleService Interface > -- > > Key: GEODE-8033 > URL: https://issues.apache.org/jira/browse/GEODE-8033 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Johnsn >Assignee: Patrick Johnsn >Priority: Major > > Introduce a new Gradle sub-project called `geode-module` and create a > ModuleService interface within it. This interface will be used to load/unload > modules and services in a classloader-isolated way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8044) Move services related to classloader-isolation to geode-common-services.
[ https://issues.apache.org/jira/browse/GEODE-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105903#comment-17105903 ] ASF subversion and git services commented on GEODE-8044: Commit 8ec8049d466a375261132e240b6e05480e3ae699 in geode's branch refs/heads/support/1.13 from Udo Kohlmeyer [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8ec8049 ] GEODE-8068 - Revert GEODE-8044 and GEODE-8033. (#5045) (#5104) Co-authored-by: Patrick Johnson > Move services related to classloader-isolation to geode-common-services. > > > Key: GEODE-8044 > URL: https://issues.apache.org/jira/browse/GEODE-8044 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Johnsn >Assignee: Patrick Johnsn >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8118) Certificate based authorization
Jakov Varenina created GEODE-8118: - Summary: Certificate based authorization Key: GEODE-8118 URL: https://issues.apache.org/jira/browse/GEODE-8118 Project: Geode Issue Type: New Feature Reporter: Jakov Varenina For more details of the implementation and design please refer to the RFC document https://cwiki.apache.org/confluence/display/GEODE/Certificate+Based+Authorization -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8118) Certificate based authorization
[ https://issues.apache.org/jira/browse/GEODE-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakov Varenina reassigned GEODE-8118: - Assignee: Jakov Varenina > Certificate based authorization > --- > > Key: GEODE-8118 > URL: https://issues.apache.org/jira/browse/GEODE-8118 > Project: Geode > Issue Type: New Feature >Reporter: Jakov Varenina >Assignee: Jakov Varenina >Priority: Major > > For more details of the implementation and design please refer to the RFC > document > https://cwiki.apache.org/confluence/display/GEODE/Certificate+Based+Authorization -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8118) Certificate based authorization
[ https://issues.apache.org/jira/browse/GEODE-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakov Varenina updated GEODE-8118: -- Description: For more details of the implementation and design please refer to the RFC document [https://cwiki.apache.org/confluence/display/GEODE/Certificate+Based+Authorization] This ticket will act as a parent Jira under which all the subsequent sub-JIRAs will be created. This ticket will be closed once all the sub jiras are implemented. was:For more details of the implementation and design please refer to the RFC document https://cwiki.apache.org/confluence/display/GEODE/Certificate+Based+Authorization > Certificate based authorization > --- > > Key: GEODE-8118 > URL: https://issues.apache.org/jira/browse/GEODE-8118 > Project: Geode > Issue Type: New Feature >Reporter: Jakov Varenina >Assignee: Jakov Varenina >Priority: Major > > For more details of the implementation and design please refer to the RFC > document > [https://cwiki.apache.org/confluence/display/GEODE/Certificate+Based+Authorization] > This ticket will act as a parent Jira under which all the subsequent > sub-JIRAs will be created. This ticket will be closed once all the sub jiras > are implemented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8119) Threads are not properly closed when offline disk-store commands are invoked
[ https://issues.apache.org/jira/browse/GEODE-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Kevo reassigned GEODE-8119: - Assignee: Mario Kevo > Threads are not properly closed when offline disk-store commands are invoked > > > Key: GEODE-8119 > URL: https://issues.apache.org/jira/browse/GEODE-8119 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Mario Kevo >Assignee: Mario Kevo >Priority: Major > > Threads can be opened when you are online and offline, but close only when > you are online. Once some offline command started thread it cannot be closed > and after some time if there is a bigger number of this threads it can lead > to OOM exception. > Also the problem is that its validating only disk-dirs but not diskStore > name. So thread can be created but there is no diskStore with that name and > it will also hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8119) Threads are not properly closed when offline disk-store commands are invoked
Mario Kevo created GEODE-8119: - Summary: Threads are not properly closed when offline disk-store commands are invoked Key: GEODE-8119 URL: https://issues.apache.org/jira/browse/GEODE-8119 Project: Geode Issue Type: Bug Components: gfsh Reporter: Mario Kevo Threads can be opened when you are online and offline, but close only when you are online. Once some offline command started thread it cannot be closed and after some time if there is a bigger number of this threads it can lead to OOM exception. Also the problem is that its validating only disk-dirs but not diskStore name. So thread can be created but there is no diskStore with that name and it will also hang. -- This message was sent by Atlassian Jira (v8.3.4#803005)
