[jira] [Updated] (GEODE-7638) CI: org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest > testRetriedPutIfAbsent FAILED
[ https://issues.apache.org/jira/browse/GEODE-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7638: --- Component/s: core > CI: org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest > > testRetriedPutIfAbsent FAILED > > > Key: GEODE-7638 > URL: https://issues.apache.org/jira/browse/GEODE-7638 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Jinmei Liao >Priority: Major > > org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest > > testRetriedPutIfAbsent FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest$10.run in VM 0 > running on Host 1c94b3f57df5 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.pdx.ClientsWithVersioningRetryDUnitTest.doRetriedTest(ClientsWithVersioningRetryDUnitTest.java:343) > at > org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest.testRetriedPutIfAbsent(ClientsWithVersioningRetryDUnitTest.java:228) > Caused by: > 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.pdx.ClientsWithVersioningRetryDUnitTest$10.run(ClientsWithVersioningRetryDUnitTest.java:347) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7638) CI: org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest > testRetriedPutIfAbsent FAILED
Jinmei Liao created GEODE-7638: -- Summary: CI: org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest > testRetriedPutIfAbsent FAILED Key: GEODE-7638 URL: https://issues.apache.org/jira/browse/GEODE-7638 Project: Geode Issue Type: Bug Reporter: Jinmei Liao org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest > testRetriedPutIfAbsent FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest$10.run in VM 0 running on Host 1c94b3f57df5 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.pdx.ClientsWithVersioningRetryDUnitTest.doRetriedTest(ClientsWithVersioningRetryDUnitTest.java:343) at org.apache.geode.pdx.ClientsWithVersioningRetryDUnitTest.testRetriedPutIfAbsent(ClientsWithVersioningRetryDUnitTest.java:228) Caused by: 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.pdx.ClientsWithVersioningRetryDUnitTest$10.run(ClientsWithVersioningRetryDUnitTest.java:347) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7639) allow tests to turn on management request/response logging
Jinmei Liao created GEODE-7639: -- Summary: allow tests to turn on management request/response logging Key: GEODE-7639 URL: https://issues.apache.org/jira/browse/GEODE-7639 Project: Geode Issue Type: Test Components: management Reporter: Jinmei Liao request/response logging is by default in the debug level. It would be helpful for tests to display them on info level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7640) allow tests to turn on management request/response logging
Jinmei Liao created GEODE-7640: -- Summary: allow tests to turn on management request/response logging Key: GEODE-7640 URL: https://issues.apache.org/jira/browse/GEODE-7640 Project: Geode Issue Type: Test Components: management Reporter: Jinmei Liao request/response logging is by default in the debug level. It would be helpful for tests to display them on info level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7640) allow tests to turn on management request/response logging
[ https://issues.apache.org/jira/browse/GEODE-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-7640: -- Assignee: Jinmei Liao > allow tests to turn on management request/response logging > -- > > Key: GEODE-7640 > URL: https://issues.apache.org/jira/browse/GEODE-7640 > Project: Geode > Issue Type: Test > Components: management >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > > request/response logging is by default in the debug level. It would be > helpful for tests to display them on info level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7642) Reduce compiler warnings
Jinmei Liao created GEODE-7642:
--
Summary: Reduce compiler warnings
Key: GEODE-7642
URL: https://issues.apache.org/jira/browse/GEODE-7642
Project: Geode
Issue Type: Improvement
Components: management
Reporter: Jinmei Liao
/Users/echobravo/Developer/gemfire/geode/geode-core/src/main/java/org/apache/geode/management/internal/BlockMBeanCreationController.java:19:
warning: MBeanServerAccessController is internal proprietary API and may be
removed in a future release
import com.sun.jmx.remote.security.MBeanServerAccessController;
^
warning: unknown enum constant When.MAYBE
reason: class file for javax.annotation.meta.When not found
warning: unknown enum constant AccessMode.READ_ONLY
reason: class file for io.swagger.annotations.ApiModelProperty$AccessMode not
found
warning: unknown enum constant AccessMode.READ_ONLY
/Users/echobravo/Developer/gemfire/geode/geode-core/src/main/java/org/apache/geode/management/internal/BlockMBeanCreationController.java:19:
warning: MBeanServerAccessController is internal proprietary API and may be
removed in a future release
import com.sun.jmx.remote.security.MBeanServerAccessController;
^
warning: unknown enum constant When.MAYBE
reason: class file for javax.annotation.meta.When not found
warning: unknown enum constant AccessMode.READ_ONLY
reason: class file for io.swagger.annotations.ApiModelProperty$AccessMode not
found
warning: unknown enum constant AccessMode.READ_ONLY
/Users/echobravo/Developer/gemfire/geode/geode-core/src/main/java/org/apache/geode/management/internal/BlockMBeanCreationController.java:19:
warning: MBeanServerAccessController is internal proprietary API and may be
removed in a future release
import com.sun.jmx.remote.security.MBeanServerAccessController;
^
warning: unknown enum constant When.MAYBE
reason: class file for javax.annotation.meta.When not found
warning: unknown enum constant AccessMode.READ_ONLY
reason: class file for io.swagger.annotations.ApiModelProperty$AccessMode not
found
warning: unknown enum constant AccessMode.READ_ONLY
/Users/echobravo/Developer/gemfire/geode/geode-core/src/main/java/org/apache/geode/management/internal/BlockMBeanCreationController.java:21:
warning: MBeanServerAccessController is internal proprietary API and may be
removed in a future release
public class BlockMBeanCreationController extends MBeanServerAccessController {
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7699) when a region belongs to multiple groups, cms.get(regionA) throws an exception
Jinmei Liao created GEODE-7699: -- Summary: when a region belongs to multiple groups, cms.get(regionA) throws an exception Key: GEODE-7699 URL: https://issues.apache.org/jira/browse/GEODE-7699 Project: Geode Issue Type: Improvement Components: management Reporter: Jinmei Liao scenario: 1. create regionA in group1 2. create regionA in group2 3. do a cms.get(regionA), I would expect the result contains a list of configurations on both groups, instead, it throws an exception saying "only one is expected". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7711) gfsh command over http failed when command has url encoded patterns in it.
Jinmei Liao created GEODE-7711: -- Summary: gfsh command over http failed when command has url encoded patterns in it. Key: GEODE-7711 URL: https://issues.apache.org/jira/browse/GEODE-7711 Project: Geode Issue Type: Bug Components: gfsh Reporter: Jinmei Liao when using gfsh connect over http, the following command would fail: create async-event-queue --id=myAEQ --listener=myApp.myListener --listener-param=db_url#host,username#db_user,password#abdfg012%dgadf The issue is related to % in the password. Removing % from password solved the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7711) gfsh command over http failed when command has url encoded patterns in it.
[ https://issues.apache.org/jira/browse/GEODE-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7711: --- Affects Version/s: 1.11.0 > gfsh command over http failed when command has url encoded patterns in it. > -- > > Key: GEODE-7711 > URL: https://issues.apache.org/jira/browse/GEODE-7711 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Jinmei Liao >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > when using gfsh connect over http, the following command would fail: > create async-event-queue --id=myAEQ --listener=myApp.myListener > --listener-param=db_url#host,username#db_user,password#abdfg012%dgadf > The issue is related to % in the password. Removing % from password solved > the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7717) ClusterManagementListResult should contain a list ConfigurationInfo (config per id)
[ https://issues.apache.org/jira/browse/GEODE-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7717: --- Labels: tech-debt technical_debt (was: ) > ClusterManagementListResult should contain a list ConfigurationInfo (config > per id) > --- > > Key: GEODE-7717 > URL: https://issues.apache.org/jira/browse/GEODE-7717 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Priority: Major > Labels: tech-debt, technical_debt > > Currently ClusterManagementListResult contains a list > ConfigurationResult(config per group), those configs are not grouped by id, > so a region that belongs to multiple groups might be dispersed in the list. > Since ClsuterManagementGetResult contains a single ConfigurationInfo, it > seems to make sense to have the ListResult contains a list of > ConfigurationInfo. > Also, after the ClusterManagementListResult contains the list grouped by id, > it would be good for us to display "links" in the ConfigurationInfo level > instead of ConfigurationResult level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7717) ClusterManagementListResult should contain a list ConfigurationInfo (config per id)
[ https://issues.apache.org/jira/browse/GEODE-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7717: --- Component/s: management > ClusterManagementListResult should contain a list ConfigurationInfo (config > per id) > --- > > Key: GEODE-7717 > URL: https://issues.apache.org/jira/browse/GEODE-7717 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Priority: Major > > Currently ClusterManagementListResult contains a list > ConfigurationResult(config per group), those configs are not grouped by id, > so a region that belongs to multiple groups might be dispersed in the list. > Since ClsuterManagementGetResult contains a single ConfigurationInfo, it > seems to make sense to have the ListResult contains a list of > ConfigurationInfo. > Also, after the ClusterManagementListResult contains the list grouped by id, > it would be good for us to display "links" in the ConfigurationInfo level > instead of ConfigurationResult level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7717) ClusterManagementListResult should contain a list ConfigurationInfo (config per id)
Jinmei Liao created GEODE-7717: -- Summary: ClusterManagementListResult should contain a list ConfigurationInfo (config per id) Key: GEODE-7717 URL: https://issues.apache.org/jira/browse/GEODE-7717 Project: Geode Issue Type: Improvement Reporter: Jinmei Liao Currently ClusterManagementListResult contains a list ConfigurationResult(config per group), those configs are not grouped by id, so a region that belongs to multiple groups might be dispersed in the list. Since ClsuterManagementGetResult contains a single ConfigurationInfo, it seems to make sense to have the ListResult contains a list of ConfigurationInfo. Also, after the ClusterManagementListResult contains the list grouped by id, it would be good for us to display "links" in the ConfigurationInfo level instead of ConfigurationResult level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7024) CMS Java API on locator and client should have similar error handling
[ https://issues.apache.org/jira/browse/GEODE-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-7024: -- Assignee: Jinmei Liao (was: Owen Nichols) > CMS Java API on locator and client should have similar error handling > - > > Key: GEODE-7024 > URL: https://issues.apache.org/jira/browse/GEODE-7024 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Owen Nichols >Assignee: Jinmei Liao >Priority: Major > Fix For: 1.10.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > The two implementations of ClusterManagementService should behave similarly > in how errors are handled. Currently calls to ClientClusterManagementService > return a ClusterManagementResult bearing the status of the call, while calls > to LocatorClusterManagementService are declared to return the same status > wrapper, but in fact may often throw a Java exception instead. > The goal is to be able to code to the ClusterManagementService interface. > Therefore to be consistent, ClientClusterManagementService should be changed > to raise error statuses as Java exceptions, just as a Java developer would > expect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7718) CMS java client API raises exception in failure makes it harder for user to use
Jinmei Liao created GEODE-7718:
--
Summary: CMS java client API raises exception in failure makes it
harder for user to use
Key: GEODE-7718
URL: https://issues.apache.org/jira/browse/GEODE-7718
Project: Geode
Issue Type: Improvement
Components: management
Reporter: Jinmei Liao
Currently, client code needs to do:
ClusterManagementResult result;
try{
result = cms.create(config);
}
catch (ClusterManagementException e) {
// do error handling
}
would be nice user doesn't have to do try catch.
ClusterManagementResult result = cms.create(config)
if (!result.isSuccessful) {
// do error handling
}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7718) CMS java client API raises exception in failure makes it harder for user to use
[
https://issues.apache.org/jira/browse/GEODE-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-7718:
---
Labels: tech-debt technical_debt (was: )
> CMS java client API raises exception in failure makes it harder for user to
> use
> ---
>
> Key: GEODE-7718
> URL: https://issues.apache.org/jira/browse/GEODE-7718
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Jinmei Liao
>Priority: Major
> Labels: tech-debt, technical_debt
>
> Currently, client code needs to do:
> ClusterManagementResult result;
> try{
> result = cms.create(config);
> }
> catch (ClusterManagementException e) {
> // do error handling
> }
> would be nice user doesn't have to do try catch.
> ClusterManagementResult result = cms.create(config)
> if (!result.isSuccessful) {
> // do error handling
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7711) gfsh command over http failed when command has url encoded patterns in it.
[ https://issues.apache.org/jira/browse/GEODE-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7711. Fix Version/s: 1.12.0 Resolution: Fixed > gfsh command over http failed when command has url encoded patterns in it. > -- > > Key: GEODE-7711 > URL: https://issues.apache.org/jira/browse/GEODE-7711 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.11.0 >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.12.0 > > Time Spent: 40m > Remaining Estimate: 0h > > when using gfsh connect over http, the following command would fail: > create async-event-queue --id=myAEQ --listener=myApp.myListener > --listener-param=db_url#host,username#db_user,password#abdfg012%dgadf > The issue is related to % in the password. Removing % from password solved > the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Deleted] (GEODE-7718) CMS java client API raises exception in failure makes it harder for user to use
[
https://issues.apache.org/jira/browse/GEODE-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao deleted GEODE-7718:
---
> CMS java client API raises exception in failure makes it harder for user to
> use
> ---
>
> Key: GEODE-7718
> URL: https://issues.apache.org/jira/browse/GEODE-7718
> Project: Geode
> Issue Type: Improvement
>Reporter: Jinmei Liao
>Priority: Major
> Labels: tech-debt, technical_debt
>
> Currently, client code needs to do:
> ClusterManagementResult result;
> try{
> result = cms.create(config);
> }
> catch (ClusterManagementException e) {
> // do error handling
> }
> would be nice user doesn't have to do try catch.
> ClusterManagementResult result = cms.create(config)
> if (!result.isSuccessful) {
> // do error handling
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7724) Management Rest API, rename classes
Jinmei Liao created GEODE-7724: -- Summary: Management Rest API, rename classes Key: GEODE-7724 URL: https://issues.apache.org/jira/browse/GEODE-7724 Project: Geode Issue Type: Improvement Components: management Reporter: Jinmei Liao rename ConfigurationInfo to EntityInfo rename ConfigurationResult to EntityGroupInfo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7724) Management Rest API, rename classes
[ https://issues.apache.org/jira/browse/GEODE-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7724: --- Labels: tech-debt technical_debt (was: ) > Management Rest API, rename classes > --- > > Key: GEODE-7724 > URL: https://issues.apache.org/jira/browse/GEODE-7724 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Priority: Major > Labels: tech-debt, technical_debt > > rename ConfigurationInfo to EntityInfo > rename ConfigurationResult to EntityGroupInfo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7754) Pulse should show gatewaysender's running state instead of connected state
Jinmei Liao created GEODE-7754: -- Summary: Pulse should show gatewaysender's running state instead of connected state Key: GEODE-7754 URL: https://issues.apache.org/jira/browse/GEODE-7754 Project: Geode Issue Type: Improvement Reporter: Jinmei Liao Pulse is showing gateway sender's "connected" state, while ListGatewayCommand in gfsh is showing gatewaySender's "running" state, this poses a discrepancy between the two monitors. Need to make them in sync. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7754) Pulse should show gatewaysender's running state instead of connected state
[ https://issues.apache.org/jira/browse/GEODE-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7754. Fix Version/s: 1.12.0 Resolution: Fixed > Pulse should show gatewaysender's running state instead of connected state > -- > > Key: GEODE-7754 > URL: https://issues.apache.org/jira/browse/GEODE-7754 > Project: Geode > Issue Type: Improvement >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Pulse is showing gateway sender's "connected" state, while ListGatewayCommand > in gfsh is showing gatewaySender's "running" state, this poses a discrepancy > between the two monitors. Need to make them in sync. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7757) list gateway command should also show the gateway sender's connected state
Jinmei Liao created GEODE-7757: -- Summary: list gateway command should also show the gateway sender's connected state Key: GEODE-7757 URL: https://issues.apache.org/jira/browse/GEODE-7757 Project: Geode Issue Type: Improvement Components: gfsh Reporter: Jinmei Liao Pulse shows the gateway sender's connected state, but gfsh list gateways sender command only shows the running state. Sometimes, these two states are not the same, so it provides a confusing view to the users. It would be nice for the command to also show the connected state of gateway senders as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7757) list gateway command should also show the gateway sender's connected state
[
https://issues.apache.org/jira/browse/GEODE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-7757:
---
Description:
Pulse shows the gateway sender's connected state, but gfsh list gateways sender
command only shows the running/paused/stopping state, and user needs to infer
the "connected" state by the information in the "Receiver Location" column.
Here is the output sample of list gateways:
{noformat}
GatewaySender Id | Member | Remote Cluster Id |
Type | Status | Queued Events | Receiver Location
| - | - |
-- | --- | - | -
gws2 | 192.168.86.30(server:72557):41001 | 2 |
Serial | Running | 0 |
{noformat}
It would be nice for the gfsh command to spell out if the gateway sender is
"connected" or not. Maybe the Status column should show those state: "running,
not connected", "running and connected" .
was:Pulse shows the gateway sender's connected state, but gfsh list gateways
sender command only shows the running state. Sometimes, these two states are
not the same, so it provides a confusing view to the users. It would be nice
for the command to also show the connected state of gateway senders as well.
> list gateway command should also show the gateway sender's connected state
> --
>
> Key: GEODE-7757
> URL: https://issues.apache.org/jira/browse/GEODE-7757
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jinmei Liao
>Priority: Major
>
> Pulse shows the gateway sender's connected state, but gfsh list gateways
> sender command only shows the running/paused/stopping state, and user needs
> to infer the "connected" state by the information in the "Receiver Location"
> column.
> Here is the output sample of list gateways:
> {noformat}
> GatewaySender Id | Member | Remote Cluster Id
> | Type | Status | Queued Events | Receiver Location
> | - | -
> | -- | --- | - | -
> gws2 | 192.168.86.30(server:72557):41001 | 2
> | Serial | Running | 0 |
> {noformat}
>
> It would be nice for the gfsh command to spell out if the gateway sender is
> "connected" or not. Maybe the Status column should show those state:
> "running, not connected", "running and connected" .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7409) Ability: get latest PDX configuration of cluster in REST API for Management
[
https://issues.apache.org/jira/browse/GEODE-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7409.
Fix Version/s: 1.12.0
Resolution: Fixed
> Ability: get latest PDX configuration of cluster in REST API for Management
>
>
> Key: GEODE-7409
> URL: https://issues.apache.org/jira/browse/GEODE-7409
> Project: Geode
> Issue Type: New Feature
> Components: management, rest (admin)
>Reporter: Gang Yan
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> ### WHY
> 1. need to show the latest PDX configuration to customer for check and
> validation
> 1. need to know the latest PDX configuration, as an input for next updates
> ### WHAT
> 1. endpoint: `management/v1/configurations/pdx`
> ### Acceptance Criteria
> - Scenario: show default config, configuration equals to runtimeInfo
> - Scenario: show latest config, configuration does **NOT** equal to
> runtimeInfo
> ```gherkin
> Scenario: show default config, configuration equals to runtimeInfo
> Given REST API for Management is turned on on a cluster
> AND A&A
> AND a customer has permission of `CLUSTER:READ`
> When the customer run [get] `management/v1/configurations/pdx`
> Then he can find the latest configuration
> ```
> ```gherkin
> Scenario: show latest config, configuration does **NOT** equal to
> runtimeInfo
> Given REST API for Management is turned on on a cluster
> AND A&A
> AND a customer has permission of `CLUSTER:READ`
> When the customer run [get] `management/v1/configurations/pdx`
> Then he can find the latest configuration, even it does not equals to
> runtimeInfo
> ```
> **Notes:**
> 1. response body:
> ```JSON
> {
> "statusCode": "OK",
> "result": [
> {
> "configuration": {
> "diskStoreName": "name1",
> "ignoreUnreadFields": true,
> "pdxSerializer": "fullpath.className1",
> "persistent": true,
> "readSerialized": true
> },
> "runtimeInfo": {
> "diskStoreName": "name2",
> "ignoreUnreadFields": true,
> "pdxSerializer": "fullpath.className2",
> "persistent": true,
> "readSerialized": true
> },
> "links": {
> "self":
> "http://127.0.0.1:7070/management/v1/configurations/pdx";
> }
> }
> ]
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7425) Ability: can delete index in RESTAPI for Management
[ https://issues.apache.org/jira/browse/GEODE-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7425. Fix Version/s: 1.12.0 Resolution: Fixed > Ability: can delete index in RESTAPI for Management > --- > > Key: GEODE-7425 > URL: https://issues.apache.org/jira/browse/GEODE-7425 > Project: Geode > Issue Type: New Feature > Components: management, rest (admin) >Reporter: Gang Yan >Priority: Major > Fix For: 1.12.0 > > Time Spent: 3h > Remaining Estimate: 0h > > # WHAT > 1. endpoint: [DELETE] `management/v1/indexes` > 1. parameter: "name", "region", "group" > 1. expected result: delete index as specified parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7424) Ability: can create index in RESTAPI for Management
[
https://issues.apache.org/jira/browse/GEODE-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7424.
Fix Version/s: 1.12.0
Resolution: Fixed
> Ability: can create index in RESTAPI for Management
> ---
>
> Key: GEODE-7424
> URL: https://issues.apache.org/jira/browse/GEODE-7424
> Project: Geode
> Issue Type: New Feature
> Components: management, rest (admin)
>Reporter: Gang Yan
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> # WHAT
> 1. endpoint: [POST] `management/v1/indexes`
> 1. parameter: "name(indexID)", "expression", "region", "type", "group"
> 1. expected result: create index by specified parameters
> 1. type: default is "range"
> 1. region is required
> 1. name(indexID) is required
> 1. expression is required
> 1. "hash" type is not supported.
> ### Note
> 1. request body
> ```JSON
> {
> "name": "Foo6name3",
> "expression": "name3",
> "regionPath": "/Foo6",
> “group”：“”，
> “type”：“” range|key
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7436) Ability: can recognize version part when deploy function jar in GFSH
[
https://issues.apache.org/jira/browse/GEODE-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7436.
Fix Version/s: 1.12.0
Resolution: Fixed
> Ability: can recognize version part when deploy function jar in GFSH
>
>
> Key: GEODE-7436
> URL: https://issues.apache.org/jira/browse/GEODE-7436
> Project: Geode
> Issue Type: Improvement
> Components: gfsh, management
>Reporter: Gang Yan
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> # WHAT
> 1. recognize version part of file name, for the file to be deployed
> 1. can recognize version pattern. "filename-version[label].jar" .
> filename=[a-zA-Z/-]+, not single "-", not end with "-"
> version=[0-9/.]*, not single ".", not end with "."
> label=[-/.]{1}[a-zA-Z0-9]*
> such as:
> -is a later version of
> , will deploy.
> -is a same version of
> , the later wins
> -is a same version of
> , the later wins
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7498) support type in list indexes of REST API for Management
[ https://issues.apache.org/jira/browse/GEODE-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7498. Fix Version/s: 1.12.0 Resolution: Fixed > support type in list indexes of REST API for Management > --- > > Key: GEODE-7498 > URL: https://issues.apache.org/jira/browse/GEODE-7498 > Project: Geode > Issue Type: Improvement > Components: management, rest (admin) >Reporter: Gang Yan >Priority: Major > Fix For: 1.12.0 > > Time Spent: 50m > Remaining Estimate: 0h > > WHAT: > need to show "type" in [GET]"/management/v1/indexes" > three types: > - range( default) > - key > - hash (deprecated) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7570) RemoteGfManagerAgentTest > removeAgentAndDisconnectWouldNotThrowNPE failes with NPE
[
https://issues.apache.org/jira/browse/GEODE-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7570.
Fix Version/s: 1.12.0
Resolution: Fixed
> RemoteGfManagerAgentTest > removeAgentAndDisconnectWouldNotThrowNPE failes
> with NPE
> ---
>
> Key: GEODE-7570
> URL: https://issues.apache.org/jira/browse/GEODE-7570
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Darrel Schneider
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/1374
> {noformat}
> org.apache.geode.internal.admin.remote.RemoteGfManagerAgentTest >
> removeAgentAndDisconnectWouldNotThrowNPE FAILED
> java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.geode.internal.admin.remote.RemoteGfManagerAgentTest.removeAgentAndDisconnectWouldNotThrowNPE(RemoteGfManagerAgentTest.java:80)
> Caused by:
> java.lang.NullPointerException
> at
> org.apache.geode.internal.admin.remote.RemoteGfManagerAgent.disconnect(RemoteGfManagerAgent.java:388)
> at
> org.apache.geode.internal.admin.remote.RemoteGfManagerAgentTest.lambda$removeAgentAndDisconnectWouldNotThrowNPE$1(RemoteGfManagerAgentTest.java:76)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7583) "status locator --name/--dir" is not working properly when locator ssl is enabled
[
https://issues.apache.org/jira/browse/GEODE-7583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7583.
Fix Version/s: 1.12.0
Resolution: Fixed
> "status locator --name/--dir" is not working properly when locator ssl is
> enabled
> -
>
> Key: GEODE-7583
> URL: https://issues.apache.org/jira/browse/GEODE-7583
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Affects Versions: 1.8.0, 1.9.0, 1.10.0, 1.11.0
>Reporter: Jinmei Liao
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> in 1.8:
> 1. start a locator with ssl enabled
> 2. "status locator --dir" or "status locator --name" would trigger such error
> messages in the locator log:
> {quote}[info 2019/12/16 08:57:39.958 PST locator
> tid=0x23] Exception in processing request from 10.118.20.75
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
> at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at
> org.apache.geode.internal.net.SocketCreator.handshakeIfSocketIsSSL(SocketCreator.java:981)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:346)
> 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)
> {quote}
> In develop branch: the gfsh output would be a strange ClassCastException.
> It's definitely broken on develop
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7579) improvement: list indexes in REST API need to show all the runtime index info
[
https://issues.apache.org/jira/browse/GEODE-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7579.
Fix Version/s: 1.12.0
Resolution: Fixed
> improvement: list indexes in REST API need to show all the runtime index info
> -
>
> Key: GEODE-7579
> URL: https://issues.apache.org/jira/browse/GEODE-7579
> Project: Geode
> Issue Type: Improvement
> Components: management, rest (admin)
>Reporter: Gang Yan
>Priority: Minor
> Fix For: 1.12.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> # Steps to reproduce
> gfsh commands:
> start server --server-port=0 --group=g5 --name=g5-s5
> start server --server-port=0 --group=g6 --name=g6-s6
> create region --name=/regionTest --type=PARTITION --group=g5
> create region --name=/regionTest --type=PARTITION_PROXY --group=g6
> create index --name=regionTest.name1 --expression=name --region=/regionTest
> --group=g5
> create index --name=regionTest.name1 --expression=name2 --region=/regionTest
> --group=g6
> create index --name=regionTest.name2 --expression=name --region=/regionTest
> --group=g6
> and then run "list indexes", we will find there are 4 indexes
> gfsh>list indexes
> Member Name | Member ID | Region Path | Name |
> Type | Indexed Expression | From Clause | Valid Index
> --- | - | --- | |
> - | -- | --- | ---
> g5-s5 | 10.118.20.154(g5-s5:967.. | /regionTest | regionTest.name1 |
> RANGE | name | /regionTest | true
> g5-s5 | 10.118.20.154(g5-s5:967.. | /regionTest | regionTest.name2 |
> RANGE | name | /regionTest | true
> g6-s6 | 10.118.20.154(g6-s6:967.. | /regionTest | regionTest.name1 |
> RANGE | name2 | /regionTest | false
> g6-s6 | 10.118.20.154(g6-s6:967.. | /regionTest | regionTest.name2 |
> RANGE | name | /regionTest | false
> but in REST API, [GET]"/management/v1/indexes", there are only 3 indexes:
> {
> "statusCode": "OK",
> "result": [
> {
> "configuration": {
> "group": "g6",
> "name": "regionTest.name1",
> "expression": "name2",
> "regionPath": "/regionTest",
> "indexType": "RANGE"
> },
> "runtimeInfo": [
> {
> "memberName": "g6-s6"
> }
> ],
> "links": {
> "self":
> "http://127.0.0.1:7070/management/v1/regions/regionTest/indexes/regionTest.name1";,
> "list":
> "http://127.0.0.1:7070/management/v1/regions/regionTest/indexes";,
> "region":
> "http://127.0.0.1:7070/management/v1/regions/regionTest";
> }
> },
> {
> "configuration": {
> "group": "g6",
> "name": "regionTest.name2",
> "expression": "name",
> "regionPath": "/regionTest",
> "indexType": "RANGE"
> },
> "runtimeInfo": [
> {
> "memberName": "g6-s6"
> }
> ],
> "links": {
> "self":
> "http://127.0.0.1:7070/management/v1/regions/regionTest/indexes/regionTest.name2";,
> "list":
> "http://127.0.0.1:7070/management/v1/regions/regionTest/indexes";,
> "region":
> "http://127.0.0.1:7070/management/v1/regions/regionTest";
> }
> },
> {
> "configuration": {
> "group": "g5",
> "name": "regionTest.name1",
> "expression": "name",
> "regionPath": "/regionTest",
> "indexType": "RANGE"
> },
> "runtimeInfo": [
> {
> "memberName": "g5-s5"
> }
> ],
> "links": {
> "self":
> "http://127.0.0.1:7070/management/v1/regions/regionTest/indexes/regionTest.name1";,
> "list":
> "http://127.0.0.1:7070/management/v1/regions/regionTest/indexes";,
> "region":
> "http://127.0.0.1:7070/management/v1/regions/regionTest";
> }
> }
> ]
> }
> in REST AP [GET]"/management/v1/indexes", the users can not find "g5-s5
> | 10.118.20.154(g5-s5:967.. | /regionTest | regionTest.name2 | RANGE | name
> | /regionTest | true"
> need to show this in REST API [GET]"/management/v1/indexes".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7640) allow tests to turn on management request/response logging
[ https://issues.apache.org/jira/browse/GEODE-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7640. Fix Version/s: 1.12.0 Resolution: Fixed > allow tests to turn on management request/response logging > -- > > Key: GEODE-7640 > URL: https://issues.apache.org/jira/browse/GEODE-7640 > Project: Geode > Issue Type: Test > Components: management >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Fix For: 1.12.0 > > Time Spent: 50m > Remaining Estimate: 0h > > request/response logging is by default in the debug level. It would be > helpful for tests to display them on info level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7724) Management Rest API, rename classes
[ https://issues.apache.org/jira/browse/GEODE-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7724. Fix Version/s: 1.12.0 Resolution: Fixed > Management Rest API, rename classes > --- > > Key: GEODE-7724 > URL: https://issues.apache.org/jira/browse/GEODE-7724 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Priority: Major > Labels: tech-debt, technical_debt > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > rename ConfigurationInfo to EntityInfo > rename ConfigurationResult to EntityGroupInfo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7775) Locator should not continue to start up if any exception happens
[ https://issues.apache.org/jira/browse/GEODE-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7775: --- Issue Type: Bug (was: Improvement) > Locator should not continue to start up if any exception happens > - > > Key: GEODE-7775 > URL: https://issues.apache.org/jira/browse/GEODE-7775 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jinmei Liao >Priority: Major > > this is related to GEODE-7760, locator was forced out of the cluster and > then threw an NPE when it was reconnecting, hence the services are not > started up properly but the locator appears to be up, this would leads to > corrupt state since some services are not up and running. We should prevent > this locator from starting up if exception happens. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7775) Locator should not continue to start up if any exception happens
Jinmei Liao created GEODE-7775: -- Summary: Locator should not continue to start up if any exception happens Key: GEODE-7775 URL: https://issues.apache.org/jira/browse/GEODE-7775 Project: Geode Issue Type: Improvement Components: management Reporter: Jinmei Liao this is related to GEODE-7760, locator was forced out of the cluster and then threw an NPE when it was reconnecting, hence the services are not started up properly but the locator appears to be up, this would leads to corrupt state since some services are not up and running. We should prevent this locator from starting up if exception happens. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-7754) Pulse should show gatewaysender's running state instead of connected state
[ https://issues.apache.org/jira/browse/GEODE-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reopened GEODE-7754: Assignee: Jinmei Liao > Pulse should show gatewaysender's running state instead of connected state > -- > > Key: GEODE-7754 > URL: https://issues.apache.org/jira/browse/GEODE-7754 > Project: Geode > Issue Type: Improvement >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Fix For: 1.12.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Pulse is showing gateway sender's "connected" state, while ListGatewayCommand > in gfsh is showing gatewaySender's "running" state, this poses a discrepancy > between the two monitors. Need to make them in sync. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7754) Pulse should show gatewaysender's running state instead of connected state
[ https://issues.apache.org/jira/browse/GEODE-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7754. Fix Version/s: (was: 1.12.0) Resolution: Won't Fix It's actually helpful for this to show the "connected" state. Will leave Pulse to stay the same. > Pulse should show gatewaysender's running state instead of connected state > -- > > Key: GEODE-7754 > URL: https://issues.apache.org/jira/browse/GEODE-7754 > Project: Geode > Issue Type: Improvement >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > Pulse is showing gateway sender's "connected" state, while ListGatewayCommand > in gfsh is showing gatewaySender's "running" state, this poses a discrepancy > between the two monitors. Need to make them in sync. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7717) ClusterManagementListResult should contain a list ConfigurationInfo (config per id)
[ https://issues.apache.org/jira/browse/GEODE-7717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7717. Fix Version/s: 1.12.0 Resolution: Fixed > ClusterManagementListResult should contain a list ConfigurationInfo (config > per id) > --- > > Key: GEODE-7717 > URL: https://issues.apache.org/jira/browse/GEODE-7717 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Jinmei Liao >Priority: Major > Labels: tech-debt, technical_debt > Fix For: 1.12.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Currently ClusterManagementListResult contains a list > ConfigurationResult(config per group), those configs are not grouped by id, > so a region that belongs to multiple groups might be dispersed in the list. > Since ClsuterManagementGetResult contains a single ConfigurationInfo, it > seems to make sense to have the ListResult contains a list of > ConfigurationInfo. > Also, after the ClusterManagementListResult contains the list grouped by id, > it would be good for us to display "links" in the ConfigurationInfo level > instead of ConfigurationResult level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7757) list gateway command should also show the gateway sender's connected state
[
https://issues.apache.org/jira/browse/GEODE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7757.
Fix Version/s: 1.13.0
Resolution: Fixed
> list gateway command should also show the gateway sender's connected state
> --
>
> Key: GEODE-7757
> URL: https://issues.apache.org/jira/browse/GEODE-7757
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jinmei Liao
>Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Pulse shows the gateway sender's connected state, but gfsh list gateways
> sender command only shows the running/paused/stopping state, and user needs
> to infer the "connected" state by the information in the "Receiver Location"
> column.
> Here is the output sample of list gateways:
> {noformat}
> GatewaySender Id | Member | Remote Cluster Id
> | Type | Status | Queued Events | Receiver Location
> | - | -
> | -- | --- | - | -
> gws2 | 192.168.86.30(server:72557):41001 | 2
> | Serial | Running | 0 |
> {noformat}
>
> It would be nice for the gfsh command to spell out if the gateway sender is
> "connected" or not. Maybe the Status column should show those state:
> "running, not connected", "running and connected" .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7795) CI: org.apache.geode.internal.cache.ClientServerTransactionDUnitTest > testTXInvalidate FAILED
Jinmei Liao created GEODE-7795: -- Summary: CI: org.apache.geode.internal.cache.ClientServerTransactionDUnitTest > testTXInvalidate FAILED Key: GEODE-7795 URL: https://issues.apache.org/jira/browse/GEODE-7795 Project: Geode Issue Type: Bug Components: transactions Reporter: Jinmei Liao https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1566 org.apache.geode.internal.cache.ClientServerTransactionDUnitTest > testTXInvalidate FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.RemoteTransactionDUnitTest$23.call in VM 2 running on Host 23c4cc3723bd 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 23c4cc3723bd with 4 VMs Caused by: java.lang.AssertionError: Event never occurred after 3 ms: -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7796) CI: org.apache.geode.distributed.LocatorDUnitTest testCrashLocatorMultipleTimes hung
Jinmei Liao created GEODE-7796: -- Summary: CI: org.apache.geode.distributed.LocatorDUnitTest testCrashLocatorMultipleTimes hung Key: GEODE-7796 URL: https://issues.apache.org/jira/browse/GEODE-7796 Project: Geode Issue Type: Bug Components: membership Reporter: Jinmei Liao https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1563 in the artifacts callbacks/dunit-hang.txt, Started @ 2020-02-11 00:30:32.499 + 2020-02-11 01:07:59.054 + org.apache.geode.distributed.LocatorDUnitTest testCrashLocatorMultipleTimes Ended @ 2020-02-11 02:05:31.891 + and the stacktraces shows thread gets blocked for a long time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7796) CI: org.apache.geode.distributed.LocatorDUnitTest testCrashLocatorMultipleTimes hung
[ https://issues.apache.org/jira/browse/GEODE-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-7796: -- Assignee: Bruce J Schuchardt > CI: org.apache.geode.distributed.LocatorDUnitTest > testCrashLocatorMultipleTimes hung > > > Key: GEODE-7796 > URL: https://issues.apache.org/jira/browse/GEODE-7796 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jinmei Liao >Assignee: Bruce J Schuchardt >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1563 > in the artifacts callbacks/dunit-hang.txt, > Started @ 2020-02-11 00:30:32.499 + > 2020-02-11 01:07:59.054 + org.apache.geode.distributed.LocatorDUnitTest > testCrashLocatorMultipleTimes > Ended @ 2020-02-11 02:05:31.891 + > and the stacktraces shows thread gets blocked for a long time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7796) CI: org.apache.geode.distributed.LocatorDUnitTest testCrashLocatorMultipleTimes hung
[ https://issues.apache.org/jira/browse/GEODE-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-7796: -- Assignee: (was: Bruce J Schuchardt) > CI: org.apache.geode.distributed.LocatorDUnitTest > testCrashLocatorMultipleTimes hung > > > Key: GEODE-7796 > URL: https://issues.apache.org/jira/browse/GEODE-7796 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jinmei Liao >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1563 > in the artifacts callbacks/dunit-hang.txt, > Started @ 2020-02-11 00:30:32.499 + > 2020-02-11 01:07:59.054 + org.apache.geode.distributed.LocatorDUnitTest > testCrashLocatorMultipleTimes > Ended @ 2020-02-11 02:05:31.891 + > and the stacktraces shows thread gets blocked for a long time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7524) CI failure: hang in FreeListOffHeapRegionJUnitTest.testPersistentCompressorChange
[
https://issues.apache.org/jira/browse/GEODE-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035639#comment-17035639
]
Jinmei Liao commented on GEODE-7524:
this happens again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/1521
> CI failure: hang in
> FreeListOffHeapRegionJUnitTest.testPersistentCompressorChange
> -
>
> Key: GEODE-7524
> URL: https://issues.apache.org/jira/browse/GEODE-7524
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Bruce J Schuchardt
>Priority: Major
>
> This test hung in
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK11/builds/1317]
> The test is stuck waiting for background persistence tasks to complete but
> there are no background tasks in the thread dumps for the run. Here's one
> thread dump:
> {noformat}
> Container: quizzical_lamarr
> * Dumping stack for process 1:
> 2019-12-03 00:03:04
> Full thread dump OpenJDK 64-Bit Server VM
> (11.0.4+11-post-Ubuntu-1ubuntu218.04.3 mixed mode, sharing):
> Threads class SMR info:
> _java_thread_list=0x7f1d7c001eb0, length=20, elements={
> 0x7f1dc8016800, 0x7f1dc83e0800, 0x7f1dc83e2800,
> 0x7f1dc83ea000,
> 0x7f1dc83ec800, 0x7f1dc83f6800, 0x7f1dc83f8800,
> 0x7f1dc844,
> 0x7f1dc844b000, 0x7f1dc8b2a000, 0x7f1dc8b4f000,
> 0x7f1dc8b4a000,
> 0x7f1d54fc0800, 0x7f1d55347000, 0x7f1d54f94800,
> 0x7f1d54fbf000,
> 0x7f1d54d73000, 0x7f1d54ffe000, 0x7f1d54fff800, 0x7f1d7c001000
> }
> "main" #1 prio=5 os_prio=0 cpu=762.76ms elapsed=1216.50s
> tid=0x7f1dc8016800 nid=0x6 waiting on condition [0x7f1dd068b000]
>java.lang.Thread.State: WAITING (parking)
> at jdk.internal.misc.Unsafe.park(java.base@11.0.4/Native Method)
> - parking to wait for <0xd058e378> (a
> java.util.concurrent.CountDownLatch$Sync)
> at
> java.util.concurrent.locks.LockSupport.park(java.base@11.0.4/LockSupport.java:194)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.4/AbstractQueuedSynchronizer.java:885)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(java.base@11.0.4/AbstractQueuedSynchronizer.java:1039)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(java.base@11.0.4/AbstractQueuedSynchronizer.java:1345)
> at
> java.util.concurrent.CountDownLatch.await(java.base@11.0.4/CountDownLatch.java:232)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:72)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:46)
> at
> org.gradle.process.internal.worker.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:93)
> at
> org.gradle.process.internal.worker.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:36)
> at
> org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:125)
> at
> org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:68)
> at
> worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:62)
> at
> worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:67)
>Locked ownable synchronizers:
> - None
> "Reference Handler" #2 daemon prio=10 os_prio=0 cpu=4.10ms elapsed=1216.45s
> tid=0x7f1dc83e0800 nid=0xd waiting on condition [0x7f1d9c3c7000]
>java.lang.Thread.State: RUNNABLE
> at
> java.lang.ref.Reference.waitForReferencePendingList(java.base@11.0.4/Native
> Method)
> at
> java.lang.ref.Reference.processPendingReferences(java.base@11.0.4/Reference.java:241)
> at
> java.lang.ref.Reference$ReferenceHandler.run(java.base@11.0.4/Reference.java:213)
>Locked ownable synchronizers:
> - None
> "Finalizer" #3 daemon prio=8 os_prio=0 cpu=2.97ms elapsed=1216.45s
> tid=0x7f1dc83e2800 nid=0xe in Object.wait() [0x7f1d9c2c6000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(java.base@11.0.4/Native Method)
> - waiting on
> at
> java.lang.ref.ReferenceQueue.remove(java.base@11.0.4/ReferenceQueue.java:155)
> - waiting to re-lock in wait() <0xd05927b0> (a
> java.lang.ref.ReferenceQueue$Lock)
> at
> java.lang.ref.ReferenceQueue.remove(java.base@11.0.4/ReferenceQueue.java:176)
> at
> java.lang.ref.Finalizer$FinalizerT
[jira] [Created] (GEODE-7798) CI: org.apache.geode.redis.PubSubTest failed intermittently on Windows
Jinmei Liao created GEODE-7798: -- Summary: CI: org.apache.geode.redis.PubSubTest failed intermittently on Windows Key: GEODE-7798 URL: https://issues.apache.org/jira/browse/GEODE-7798 Project: Geode Issue Type: Bug Reporter: Jinmei Liao https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1240 https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1242 org.apache.geode.redis.PubSubTest > testTwoSubscribersOneChannel FAILED org.junit.ComparisonFailure: expected:<[2]L> but was:<[1]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testTwoSubscribersOneChannel(PubSubTest.java:163) org.apache.geode.redis.PubSubTest > testOneSubscriberSubscribingToTwoChannels FAILED org.junit.ComparisonFailure: expected:<[1]L> but was:<[2]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testOneSubscriberSubscribingToTwoChannels(PubSubTest.java:124) org.apache.geode.redis.PubSubTest > testDeadSubscriber FAILED org.junit.ComparisonFailure: expected:<[0]L> but was:<[2]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testDeadSubscriber(PubSubTest.java:250) org.apache.geode.redis.PubSubTest > testOneSubscriberOneChannelTwoTimes FAILED org.junit.ComparisonFailure: expected:<[1]L> but was:<[3]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.PubSubTest.testOneSubscriberOneChannelTwoTimes(PubSubTest.java:210) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6284) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test[from_v1X0, with reindex=false]
[
https://issues.apache.org/jira/browse/GEODE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036648#comment-17036648
]
Jinmei Liao commented on GEODE-6284:
Additional failures:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK8/builds/1531
org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> test[from_v1.11.0, with reindex=false, singleHopEnabled=true] 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 9067
java.io.EOFException: Locator at /172.17.0.25:27318 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:232)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:202)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:192)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:274)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.access$200(AutoConnectionSourceImpl.java:63)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl$UpdateLocatorListTask.run2(AutoConnectionSourceImpl.java:477)
at
org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1305)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
org.apache.geode.internal.ScheduledThreadPoolExecutorWithKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWithKeepAlive.java:276)
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.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:267)
at
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2616)
at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:227)
... 12 more
> CI Failure:
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test[from_v1X0,
> with reindex=false]
>
>
> Key: GEODE-6284
> URL: https://issues.apache.org/jira/browse/GEODE-6284
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0
>Reporter: Ryan McMahon
>Priority: Major
>
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host
> 34bae3263b09 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:537)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:352)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:57)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:496)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:484)
> 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.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRu
[jira] [Resolved] (GEODE-7791) MergeLogsDistributedTest fails with extra log files
[ https://issues.apache.org/jira/browse/GEODE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7791. Fix Version/s: 1.13.0 Resolution: Fixed > MergeLogsDistributedTest fails with extra log files > --- > > Key: GEODE-7791 > URL: https://issues.apache.org/jira/browse/GEODE-7791 > Project: Geode > Issue Type: Bug >Reporter: Jianxia Chen >Priority: Major > Labels: Windows > Fix For: 1.13.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Note: these failures are on Windows with Open JDK 8 and 11 > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK8/builds/1288] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/1297] > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest > > testExportInNewProcess FAILED > java.lang.AssertionError: > Expected size:<4> but was:<5> in: > > <[C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\locator\locator56675views.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator-0.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator56791views.log, > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm1\server-1.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm2\server-2.log]> > at > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest.testExportInNewProcess(MergeLogsDistributedTest.java:97) > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest > > testExportInProcess FAILED > java.lang.AssertionError: > Expected size:<4> but was:<5> in: > > <[C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\locator\locator56675views.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator-0.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm0\locator56821views.log, > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm1\server-1.log, > > C:\Users\geode\geode\geode-gfsh\build\distributedTest\dunit\vm2\server-2.log]> > at > org.apache.geode.management.internal.cli.util.MergeLogsDistributedTest.testExportInProcess(MergeLogsDistributedTest.java:85) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7421) Ability: can deploy jar by REST API for Management
[ https://issues.apache.org/jira/browse/GEODE-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7421. Fix Version/s: 1.13.0 Resolution: Fixed > Ability: can deploy jar by REST API for Management > -- > > Key: GEODE-7421 > URL: https://issues.apache.org/jira/browse/GEODE-7421 > Project: Geode > Issue Type: New Feature > Components: management, rest (admin) >Reporter: Gang Yan >Priority: Major > Fix For: 1.13.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > # WHAT > 1. can deploy jar file by REST API > 2. from feature point , it will cover current 'gfsh deploy' > 3. if two files have same file name, the later wins > 4. can recognize version pattern. "filename-version[-label].jar" . > filename=[a-zA-Z/-]+, not single "-", not end with "-" > version=[0-9/.]*, not single ".", not end with "." > label=[a-zA-Z0-9]* > such as: > -is a later version of > , will deploy. > -is a same version of > , the later wins > -is a same version of > , the later wins > -is an earlier version of > , will block it. > 5. if there is a version part in the file name, we will deploy them > without append "#1" part to the file name > 6. can accept "group" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7851) Pulse should support OAuth2 authorization code flow
Jinmei Liao created GEODE-7851: -- Summary: Pulse should support OAuth2 authorization code flow Key: GEODE-7851 URL: https://issues.apache.org/jira/browse/GEODE-7851 Project: Geode Issue Type: New Feature Components: pulse Reporter: Jinmei Liao Instead of using username/password to log in to pulse, pulse should redirect to a configured authentication provider to get access token to login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7856) Make it easier to configure pulse custom security
Jinmei Liao created GEODE-7856:
--
Summary: Make it easier to configure pulse custom security
Key: GEODE-7856
URL: https://issues.apache.org/jira/browse/GEODE-7856
Project: Geode
Issue Type: New Feature
Components: pulse
Reporter: Jinmei Liao
There are several scenarios in the past on which our users complained about the
fact that they need to either uncompress/recompress the pulse war file or add
the pulse-authentication-custom.xml file within the application container's
classpath in order for it to be picked up by Pulse. It would make sense to make
this configurable via system properties or something similar
(@Value("${custom.spring.security.file}"))?.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7851) Pulse should support OAuth2 authorization code flow
[ https://issues.apache.org/jira/browse/GEODE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-7851: -- Assignee: Jinmei Liao > Pulse should support OAuth2 authorization code flow > --- > > Key: GEODE-7851 > URL: https://issues.apache.org/jira/browse/GEODE-7851 > Project: Geode > Issue Type: New Feature > Components: pulse >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Instead of using username/password to log in to pulse, pulse should redirect > to a configured authentication provider to get access token to login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7851) Pulse should support OAuth2 authorization code flow
[ https://issues.apache.org/jira/browse/GEODE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-7851: -- Assignee: Dale Emery (was: Jinmei Liao) > Pulse should support OAuth2 authorization code flow > --- > > Key: GEODE-7851 > URL: https://issues.apache.org/jira/browse/GEODE-7851 > Project: Geode > Issue Type: New Feature > Components: pulse >Reporter: Jinmei Liao >Assignee: Dale Emery >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > Instead of using username/password to log in to pulse, pulse should redirect > to a configured authentication provider to get access token to login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7851) Pulse should support OAuth2 authorization code flow
[ https://issues.apache.org/jira/browse/GEODE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-7851: --- Component/s: docs > Pulse should support OAuth2 authorization code flow > --- > > Key: GEODE-7851 > URL: https://issues.apache.org/jira/browse/GEODE-7851 > Project: Geode > Issue Type: New Feature > Components: docs, pulse >Reporter: Jinmei Liao >Assignee: Dale Emery >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > Instead of using username/password to log in to pulse, pulse should redirect > to a configured authentication provider to get access token to login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7902) CI Failure: DeploymentManagementRedployDUnitTest.redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators Assertion Failure
[
https://issues.apache.org/jira/browse/GEODE-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7902.
Fix Version/s: 1.13.0
Resolution: Fixed
> CI Failure:
> DeploymentManagementRedployDUnitTest.redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators
> Assertion Failure
>
>
> Key: GEODE-7902
> URL: https://issues.apache.org/jira/browse/GEODE-7902
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Four failures occurred in recent runs of the new test:
> {code:java}
> org.apache.geode.management.internal.rest.DeploymentManagementRedployDUnitTest
> > redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.rest.DeploymentManagementRedployDUnitTest$$Lambda$109/1334041298.run
> in VM 1 running on Host 58d73054f62c 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.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> at
> org.apache.geode.management.internal.rest.DeploymentManagementRedployDUnitTest.redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators(DeploymentManagementRedployDUnitTest.java:148)
> Caused by:
> org.junit.ComparisonFailure: expected:<"Version[2]"> but
> was:<"Version[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.management.internal.rest.DeploymentManagementRedployDUnitTest.assertThatFunctionHasVersion(DeploymentManagementRedployDUnitTest.java:222)
> at
> org.apache.geode.management.internal.rest.DeploymentManagementRedployDUnitTest.lambda$redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators$bb17a952$6(DeploymentManagementRedployDUnitTest.java:148)
> {code}
> redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1496
> redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1459
> redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1453
> redeployJarsWithNewVersionsOfFunctionsAndMultipleLocators
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1435]
> Test class and filename also look like they have a typo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7924) Upgrade Connect2id Nimbus JOSE+JWT library used by Pulse oAuth work
Jinmei Liao created GEODE-7924: -- Summary: Upgrade Connect2id Nimbus JOSE+JWT library used by Pulse oAuth work Key: GEODE-7924 URL: https://issues.apache.org/jira/browse/GEODE-7924 Project: Geode Issue Type: Improvement Components: pulse Reporter: Jinmei Liao use Connect2id Nimbus JOSE+JWT greater than v7.9 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7924) Upgrade Connect2id Nimbus JOSE+JWT library used by Pulse oAuth work
[ https://issues.apache.org/jira/browse/GEODE-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7924. Fix Version/s: 1.13.0 Resolution: Fixed fixed by this PR: https://github.com/apache/geode/pull/4851 > Upgrade Connect2id Nimbus JOSE+JWT library used by Pulse oAuth work > --- > > Key: GEODE-7924 > URL: https://issues.apache.org/jira/browse/GEODE-7924 > Project: Geode > Issue Type: Improvement > Components: pulse >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.13.0 > > > use Connect2id Nimbus JOSE+JWT greater than v7.9 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7710) JMXMBeanReconnectDUnitTest 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&focusedCommentId=17076689#comment-17076689
]
Jinmei Liao commented on GEODE-7710:
this failed again today:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/22#A
> JMXMBeanReconnectDUnitTest 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
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
> 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}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7960) CI: SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion FAILED on Windows
Jinmei Liao created GEODE-7960: -- Summary: CI: SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion FAILED on Windows Key: GEODE-7960 URL: https://issues.apache.org/jira/browse/GEODE-7960 Project: Geode Issue Type: Bug Components: logging Reporter: Jinmei Liao Looks like a flaky test on windows: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/21 org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest > logsMissingChildRegionUntilCompletion FAILED org.mockito.exceptions.verification.NoInteractionsWanted: No interactions wanted here: -> at org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion(SingleThreadColocationLoggerTest.java:180) But found this interaction on mock 'consumer': -> at org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229) *** For your reference, here is the list of all invocations ([?] - means unverified). 1. -> at org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229) 2. [?]-> at org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLogger.logMissingRegions(SingleThreadColocationLogger.java:229) at org.apache.geode.internal.cache.partitioned.colocation.SingleThreadColocationLoggerTest.logsMissingChildRegionUntilCompletion(SingleThreadColocationLoggerTest.java:180) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7976) make the "config" param not required when deploy a jar using management rest api
Jinmei Liao created GEODE-7976:
--
Summary: make the "config" param not required when deploy a jar
using management rest api
Key: GEODE-7976
URL: https://issues.apache.org/jira/browse/GEODE-7976
Project: Geode
Issue Type: Improvement
Reporter: Jinmei Liao
Currently user has to pass in a "config" param when deploy a jar using the rest
api, even though most of the time it's just an empty json "{}" if user just
want to deploy to the "cluster" group. make this parameter optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7976) make the "config" param not required when deploy a jar using management rest api
[
https://issues.apache.org/jira/browse/GEODE-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-7976:
---
Component/s: management
> make the "config" param not required when deploy a jar using management rest
> api
>
>
> Key: GEODE-7976
> URL: https://issues.apache.org/jira/browse/GEODE-7976
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Jinmei Liao
>Priority: Major
>
> Currently user has to pass in a "config" param when deploy a jar using the
> rest api, even though most of the time it's just an empty json "{}" if user
> just want to deploy to the "cluster" group. make this parameter optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7976) make the "config" param not required when deploy a jar using management rest api
[
https://issues.apache.org/jira/browse/GEODE-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao reassigned GEODE-7976:
--
Assignee: Jinmei Liao
> make the "config" param not required when deploy a jar using management rest
> api
>
>
> Key: GEODE-7976
> URL: https://issues.apache.org/jira/browse/GEODE-7976
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>
> Currently user has to pass in a "config" param when deploy a jar using the
> rest api, even though most of the time it's just an empty json "{}" if user
> just want to deploy to the "cluster" group. make this parameter optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7976) make the "config" param not required when deploy a jar using management rest api
[
https://issues.apache.org/jira/browse/GEODE-7976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7976.
Fix Version/s: 1.13.0
Resolution: Fixed
> make the "config" param not required when deploy a jar using management rest
> api
>
>
> Key: GEODE-7976
> URL: https://issues.apache.org/jira/browse/GEODE-7976
> Project: Geode
> Issue Type: Improvement
> Components: management
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently user has to pass in a "config" param when deploy a jar using the
> rest api, even though most of the time it's just an empty json "{}" if user
> just want to deploy to the "cluster" group. make this parameter optional
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7664) CI Failure: ClientClusterManagementServiceDUnitTest > deleteRegionOnSpecificGroup
[
https://issues.apache.org/jira/browse/GEODE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-7664.
Fix Version/s: 1.13.0
Resolution: Fixed
> CI Failure: ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup
> -
>
> Key: GEODE-7664
> URL: https://issues.apache.org/jira/browse/GEODE-7664
> Project: Geode
> Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Jinmei Liao
>Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1454]
>
> {code:java}
> org.apache.geode.management.client.ClientClusterManagementServiceDUnitTest >
> deleteRegionOnSpecificGroup FAILEDjava.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 1874 [error 2020/01/09 18:52:37.224 GMT
> tid=353]
> org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> org.apache.geode.cache.RegionDestroyedException:org.apache.geode.internal.cache.DistributedRegion[path='/region2';scope=DISTRIBUTED_ACK';dataPolicy=REPLICATE;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
> at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:307)
> at
> org.apache.geode.management.internal.configuration.realizers.RegionConfigRealizer.get(RegionConfigRealizer.java:48)
>
> at
> org.apache.geode.management.internal.configuration.realizers.ConfigurationRealizer.exists(ConfigurationRealizer.java:35)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.executeUpdate(CacheRealizationFunction.java:130)
> at
> org.apache.geode.management.internal.functions.CacheRealizationFunction.execute(CacheRealizationFunction.java:79)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:394)
>
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:458)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:449)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:379)
> at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7851) Pulse should support OAuth2 authorization code flow
[ https://issues.apache.org/jira/browse/GEODE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-7851. Fix Version/s: 1.13.0 Resolution: Fixed > Pulse should support OAuth2 authorization code flow > --- > > Key: GEODE-7851 > URL: https://issues.apache.org/jira/browse/GEODE-7851 > Project: Geode > Issue Type: New Feature > Components: docs, pulse >Reporter: Jinmei Liao >Assignee: Dale Emery >Priority: Major > Fix For: 1.13.0 > > Time Spent: 11h 10m > Remaining Estimate: 0h > > Instead of using username/password to log in to pulse, pulse should redirect > to a configured authentication provider to get access token to login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-7851) Pulse should support OAuth2 authorization code flow
[ https://issues.apache.org/jira/browse/GEODE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reopened GEODE-7851: I believe there is still the last piece undone: log out to invalidate the token > Pulse should support OAuth2 authorization code flow > --- > > Key: GEODE-7851 > URL: https://issues.apache.org/jira/browse/GEODE-7851 > Project: Geode > Issue Type: New Feature > Components: docs, pulse >Reporter: Jinmei Liao >Assignee: Dale Emery >Priority: Major > Fix For: 1.13.0 > > Time Spent: 11h 10m > Remaining Estimate: 0h > > Instead of using username/password to log in to pulse, pulse should redirect > to a configured authentication provider to get access token to login. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8009) CI failure: tanzu-gemfire-management-cf-plugin is failing with unsupported protocol scheme
[
https://issues.apache.org/jira/browse/GEODE-8009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-8009.
Fix Version/s: 1.12.1
Resolution: Fixed
> CI failure: tanzu-gemfire-management-cf-plugin is failing with unsupported
> protocol scheme
> --
>
> Key: GEODE-8009
> URL: https://issues.apache.org/jira/browse/GEODE-8009
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Barrett Oglesby
>Priority: Major
> Fix For: 1.12.1
>
>
> The tanzu-gemfire-management-cf-plugin in both
> test-cloudcache-management-cf-pcc-1.10 and
> test-cloudcache-management-cf-pcc-1.11 is failing with unsupported protocol
> scheme.
> https://concourse.gemfire-ci.info/teams/main/pipelines/tanzu-gemfire-management-cf-plugin/jobs/test-cloudcache-management-cf-pcc-1.11/builds/9
> https://concourse.gemfire-ci.info/teams/main/pipelines/tanzu-gemfire-management-cf-plugin/jobs/test-cloudcache-management-cf-pcc-1.10/builds/11
> The plugin-test in both is show logging like:
> {noformat}
> Plugin gemfire 1.0.5 successfully installed.
> + cf='cf gemfire test'
> + ci/smoke-test.bash
> + service_instance_name=test
> + cf gemfire test commands
> Unable to reach 45201/management/. Error: Get "45201/management/":
> unsupported protocol scheme ""
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7523) Cannot add an index to a region that has a dot in its name
[ https://issues.apache.org/jira/browse/GEODE-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17096810#comment-17096810 ] Jinmei Liao commented on GEODE-7523: "CreateIndexConmmand" will catch this early and fail when looking for the wrong region -- if the region exists is A.B, it will look for region A instead of A.B. Even if it passes this step, the same error would occur if trying to create the index on the server. > Cannot add an index to a region that has a dot in its name > -- > > Key: GEODE-7523 > URL: https://issues.apache.org/jira/browse/GEODE-7523 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Dale Emery >Priority: Major > > It is not possible to add an index to a region that has a dot in its name. > Geode currently accepts dots in region names (though the documentation says > it does not). > To create an index via GFSH, the user specifies the region name using the > `--region` parameter. GFSH passes the region name to the query service as a > "from clause." > The query service uses OQL parsers in several places to extract the region > name from the given "from clause." The OQL parser's grammar does not > recognize a dot as being part of a region name, and so truncates the given > "from clause" at the first dot. When a region name contains a dot, this has > the effect of truncating the region name at the first dot. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8055) can not create index on sub regions
Jinmei Liao created GEODE-8055: -- Summary: can not create index on sub regions Key: GEODE-8055 URL: https://issues.apache.org/jira/browse/GEODE-8055 Project: Geode Issue Type: Bug Components: gfsh Reporter: Jinmei Liao When trying to use "create index" command in gfsh to create index on sub regions, we get the following message: "Sub-regions are unsupported" Pre-1.6, we were able to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8055) can not create index on sub regions
[ https://issues.apache.org/jira/browse/GEODE-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8055: --- Affects Version/s: 1.7.0 1.8.0 1.10.0 1.9.2 1.11.0 1.12.0 > can not create index on sub regions > --- > > Key: GEODE-8055 > URL: https://issues.apache.org/jira/browse/GEODE-8055 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.7.0, 1.8.0, 1.10.0, 1.9.2, 1.11.0, 1.12.0 >Reporter: Jinmei Liao >Priority: Major > > When trying to use "create index" command in gfsh to create index on sub > regions, we get the following message: > "Sub-regions are unsupported" > Pre-1.6, we were able to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8056) CI: ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED
Jinmei Liao created GEODE-8056: -- Summary: CI: ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED Key: GEODE-8056 URL: https://issues.apache.org/jira/browse/GEODE-8056 Project: Geode Issue Type: Bug Components: regions Reporter: Jinmei Liao 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-8056) CI: ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED
[ https://issues.apache.org/jira/browse/GEODE-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8056: --- Affects Version/s: 1.12.0 > 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 > > 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-8056) CI: ReplicateEntryIdleExpirationDistributedTest.readsInOtherMemberShouldPreventExpirationWhenEvictionEnabled FAILED
[ https://issues.apache.org/jira/browse/GEODE-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8056: --- Description: 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) was: 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) > 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$a3
[jira] [Updated] (GEODE-8057) CI: SRemIntegrationTest > testConcurrentSRems FAILED on windows
[ https://issues.apache.org/jira/browse/GEODE-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8057: --- Affects Version/s: 1.12.0 > CI: SRemIntegrationTest > testConcurrentSRems FAILED on windows > --- > > Key: GEODE-8057 > URL: https://issues.apache.org/jira/browse/GEODE-8057 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.12.0 >Reporter: Jinmei Liao >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/107 > org.apache.geode.redis.sets.SRemIntegrationTest > testConcurrentSRems FAILED > org.junit.ComparisonFailure: expected:<100[0]L> but was:<100[1]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.redis.sets.SRemIntegrationTest.testConcurrentSRems(SRemIntegrationTest.java:289) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8057) CI: SRemIntegrationTest > testConcurrentSRems FAILED on windows
[ https://issues.apache.org/jira/browse/GEODE-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8057: --- Affects Version/s: (was: 1.12.0) 1.13.0 > CI: SRemIntegrationTest > testConcurrentSRems FAILED on windows > --- > > Key: GEODE-8057 > URL: https://issues.apache.org/jira/browse/GEODE-8057 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.13.0 >Reporter: Jinmei Liao >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/107 > org.apache.geode.redis.sets.SRemIntegrationTest > testConcurrentSRems FAILED > org.junit.ComparisonFailure: expected:<100[0]L> but was:<100[1]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.redis.sets.SRemIntegrationTest.testConcurrentSRems(SRemIntegrationTest.java:289) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8057) CI: SRemIntegrationTest > testConcurrentSRems FAILED on windows
Jinmei Liao created GEODE-8057: -- Summary: CI: SRemIntegrationTest > testConcurrentSRems FAILED on windows Key: GEODE-8057 URL: https://issues.apache.org/jira/browse/GEODE-8057 Project: Geode Issue Type: Bug Components: redis Reporter: Jinmei Liao https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/107 org.apache.geode.redis.sets.SRemIntegrationTest > testConcurrentSRems FAILED org.junit.ComparisonFailure: expected:<100[0]L> but was:<100[1]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.redis.sets.SRemIntegrationTest.testConcurrentSRems(SRemIntegrationTest.java:289) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8055) can not create index on sub regions
[ https://issues.apache.org/jira/browse/GEODE-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-8055. Fix Version/s: 1.13.0 Resolution: Fixed > can not create index on sub regions > --- > > Key: GEODE-8055 > URL: https://issues.apache.org/jira/browse/GEODE-8055 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.7.0, 1.8.0, 1.10.0, 1.9.2, 1.11.0, 1.12.0 >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.13.0 > > > When trying to use "create index" command in gfsh to create index on sub > regions, we get the following message: > "Sub-regions are unsupported" > Pre-1.6, we were able to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8055) can not create index on sub regions
[ https://issues.apache.org/jira/browse/GEODE-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8055: --- Fix Version/s: 1.12.1 > can not create index on sub regions > --- > > Key: GEODE-8055 > URL: https://issues.apache.org/jira/browse/GEODE-8055 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.7.0, 1.8.0, 1.10.0, 1.9.2, 1.11.0, 1.12.0 >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When trying to use "create index" command in gfsh to create index on sub > regions, we get the following message: > "Sub-regions are unsupported" > Pre-1.6, we were able to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8055) can not create index on sub regions
[ https://issues.apache.org/jira/browse/GEODE-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-8055: --- Labels: GeodeOperationAPI (was: ) > can not create index on sub regions > --- > > Key: GEODE-8055 > URL: https://issues.apache.org/jira/browse/GEODE-8055 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.7.0, 1.8.0, 1.10.0, 1.9.2, 1.11.0, 1.12.0 >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.12.1, 1.13.0, 1.14.0 > > > When trying to use "create index" command in gfsh to create index on sub > regions, we get the following message: > "Sub-regions are unsupported" > Pre-1.6, we were able to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8078) Exceptions in locator logs when hitting members REST endpoint
[
https://issues.apache.org/jira/browse/GEODE-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-8078:
---
Labels: GeodeOperationAPI (was: )
> Exceptions in locator logs when hitting members REST endpoint
> -
>
> Key: GEODE-8078
> URL: https://issues.apache.org/jira/browse/GEODE-8078
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Aaron Lindsey
>Priority: Major
> Labels: GeodeOperationAPI
>
> I'm seeing the following exceptions in locator logs when I try to hit the
> REST endpoint /management/v1/members/\{id} before the member has finished
> starting up. The reason I need to do this is because I have a program that is
> polling that endpoint to wait until the member is online. Ideally these
> errors would not show up in logs, but instead be reflected in the status code
> of the REST response.
> {quote}[error 2020/04/06 22:05:59.086 UTC tid=0x31] class
> org.apache.geode.cache.CacheClosedException cannot be cast to class
> org.apache.geode.management.runtime.RuntimeInfo
> (org.apache.geode.cache.CacheClosedException and
> org.apache.geode.management.runtime.RuntimeInfo are in unnamed module of
> loader 'app')
> java.lang.ClassCastException: class
> org.apache.geode.cache.CacheClosedException cannot be cast to class
> org.apache.geode.management.runtime.RuntimeInfo
> (org.apache.geode.cache.CacheClosedException and
> org.apache.geode.management.runtime.RuntimeInfo are in unnamed module of
> loader 'app')
> at
> org.apache.geode.management.internal.api.LocatorClusterManagementService.list(LocatorClusterManagementService.java:417)
> at
> org.apache.geode.management.internal.api.LocatorClusterManagementService.get(LocatorClusterManagementService.java:434)
> at
> org.apache.geode.management.internal.rest.controllers.MemberManagementController.getMember(MemberManagementController.java:50)
> at
> org.apache.geode.management.internal.rest.controllers.MemberManagementController$$FastClassBySpringCGLIB$$3634e452.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:769)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747)
> at
> org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:69)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689)
> at
> org.apache.geode.management.internal.rest.controllers.MemberManagementController$$EnhancerBySpringCGLIB$$2893b195.getMember()
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:106)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:888)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:793)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
> at
> org.springframework.web.servlet.FrameworkSe
[jira] [Created] (GEODE-8091) AuthenticationRequiredException: Failed to find the authenticated user" at startup when trying to start locator
Jinmei Liao created GEODE-8091: -- Summary: 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 Reporter: Jinmei Liao 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] [Updated] (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:all-tabpanel ] Jinmei Liao updated GEODE-8091: --- Affects Version/s: 1.12.0 > 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 > > 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-9521) Add test to cover multi-servers scenario for re-authentication
Jinmei Liao created GEODE-9521: -- Summary: Add test to cover multi-servers scenario for re-authentication Key: GEODE-9521 URL: https://issues.apache.org/jira/browse/GEODE-9521 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9453) The server, once a user expires, should clean the user attributes from the server.
[ https://issues.apache.org/jira/browse/GEODE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9453: --- Description: ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. make sure to include tests in multi-server cases was:ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. > The server, once a user expires, should clean the user attributes from the > server. > -- > > Key: GEODE-9453 > URL: https://issues.apache.org/jira/browse/GEODE-9453 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > ClientUserAuths maintains a map of clientID to its user attributes (the > logged in shiro subject etc), when user expires, we need to remove that entry > from that map and log the shiro subject out to avoid resource leak. > > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9453) The server, once a user expires, should clean the user attributes from the server.
[ https://issues.apache.org/jira/browse/GEODE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9453: --- Description: ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. make sure to include tests in multi-server cases was: ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. make sure to include tests in multi-server cases > The server, once a user expires, should clean the user attributes from the > server. > -- > > Key: GEODE-9453 > URL: https://issues.apache.org/jira/browse/GEODE-9453 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > ClientUserAuths maintains a map of clientID to its user attributes (the > logged in shiro subject etc), when user expires, we need to remove that entry > from that map and log the shiro subject out to avoid resource leak. > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9458) Add tests for functions executions on servers when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9458: --- Description: and make sure the behavior matches expectation. make sure to include tests in multi-server cases was:and make sure the behavior matches expection. > Add tests for functions executions on servers when authentication expires > - > > Key: GEODE-9458 > URL: https://issues.apache.org/jira/browse/GEODE-9458 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > and make sure the behavior matches expectation. > > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9457) Investigate the behavior of CQ and registered interests when authentication expires.
[ https://issues.apache.org/jira/browse/GEODE-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9457: --- Description: We need to find out what's the current behavior of cq and registered interests when authentication expires and see if the behavior matches the expectation make sure to include tests in multi-server cases was:We need to find out what's the current behavior of cq and registered interests when authentication expires and see if the behavior matches the expectation > Investigate the behavior of CQ and registered interests when authentication > expires. > > > Key: GEODE-9457 > URL: https://issues.apache.org/jira/browse/GEODE-9457 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > We need to find out what's the current behavior of cq and registered > interests when authentication expires and see if the behavior matches the > expectation > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9460) add tests for multi-user mode when one user expires
[ https://issues.apache.org/jira/browse/GEODE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9460: --- Description: make sure the behavior matches expectations make sure to include tests in multi-server cases was:make sure the behavior matches expections > add tests for multi-user mode when one user expires > --- > > Key: GEODE-9460 > URL: https://issues.apache.org/jira/browse/GEODE-9460 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > make sure the behavior matches expectations > > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9521) Add test to cover multi-servers scenario for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9521: --- Labels: GeodeOperationAPI security (was: ) > Add test to cover multi-servers scenario for re-authentication > -- > > Key: GEODE-9521 > URL: https://issues.apache.org/jira/browse/GEODE-9521 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, security > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9534) Add tests to verify peer communication when auth expired
Jinmei Liao created GEODE-9534: -- Summary: Add tests to verify peer communication when auth expired Key: GEODE-9534 URL: https://issues.apache.org/jira/browse/GEODE-9534 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao When a server joins the cluster, it needs to provide credentials, when network issue happens, the sever disconnects and reconnects back, what happens when the credential expired? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9534) Add tests to verify peer communication when auth expired
[ https://issues.apache.org/jira/browse/GEODE-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9534: --- Labels: GeodeOperationAPI security (was: ) > Add tests to verify peer communication when auth expired > > > Key: GEODE-9534 > URL: https://issues.apache.org/jira/browse/GEODE-9534 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, security > > When a server joins the cluster, it needs to provide credentials, when > network issue happens, the sever disconnects and reconnects back, what > happens when the credential expired? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-9456. Resolution: Fixed > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-9456: -- Assignee: Jinmei Liao > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9452) The older version client should receive the AuthenticationRequiredException when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-9452: -- Assignee: Jinmei Liao > The older version client should receive the AuthenticationRequiredException > when authentication expires > --- > > Key: GEODE-9452 > URL: https://issues.apache.org/jira/browse/GEODE-9452 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > Currently, for older client, it's receiving a ClassNotFoundException, we need > to add the serialization code to convert the AuthenticationExpiredException > into this old exception type that the older clients can understand. > > Note: when converting the exception, if we have the message to match what the > older client expects, it can do re-authentication automatically, but we lost > the original message that server has thrown. (Need to consult the PM on what > kind of behavior they want). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reopened GEODE-9456: > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9540) verify client bulk operations like putAll and getAll and succeed after authentication expires
Jinmei Liao created GEODE-9540: -- Summary: verify client bulk operations like putAll and getAll and succeed after authentication expires Key: GEODE-9540 URL: https://issues.apache.org/jira/browse/GEODE-9540 Project: Geode Issue Type: Sub-task Components: security Reporter: Jinmei Liao -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9458) Add tests for functions executions on servers when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9458: --- Description: and make sure the behavior matches expectation. make sure to include tests in multi-server cases test onServer, onServers, onRegions was: and make sure the behavior matches expectation. make sure to include tests in multi-server cases > Add tests for functions executions on servers when authentication expires > - > > Key: GEODE-9458 > URL: https://issues.apache.org/jira/browse/GEODE-9458 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > and make sure the behavior matches expectation. > > make sure to include tests in multi-server cases > > test onServer, onServers, onRegions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-9456. Fix Version/s: 1.15.0 Resolution: Fixed > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9521) Add test to cover multi-servers scenario for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-9521. Fix Version/s: 1.15.0 Resolution: Fixed > Add test to cover multi-servers scenario for re-authentication > -- > > Key: GEODE-9521 > URL: https://issues.apache.org/jira/browse/GEODE-9521 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available, security > Fix For: 1.15.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9452) The older version client should receive the AuthenticationRequiredException when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-9452. Fix Version/s: 1.15.0 Resolution: Fixed > The older version client should receive the AuthenticationRequiredException > when authentication expires > --- > > Key: GEODE-9452 > URL: https://issues.apache.org/jira/browse/GEODE-9452 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > Fix For: 1.15.0 > > > Currently, for older client, it's receiving a ClassNotFoundException, we need > to add the serialization code to convert the AuthenticationExpiredException > into this old exception type that the older clients can understand. > > Note: when converting the exception, if we have the message to match what the > older client expects, it can do re-authentication automatically, but we lost > the original message that server has thrown. (Need to consult the PM on what > kind of behavior they want). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9458) Add tests for functions executions on servers when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-9458: -- Assignee: Joris Melchior > Add tests for functions executions on servers when authentication expires > - > > Key: GEODE-9458 > URL: https://issues.apache.org/jira/browse/GEODE-9458 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Assignee: Joris Melchior >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > and make sure the behavior matches expectation. > > make sure to include tests in multi-server cases > > test onServer, onServers, onRegions -- This message was sent by Atlassian Jira (v8.3.4#803005)
