date:20191022



 [ 
https://issues.apache.org/jira/browse/GEODE-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Lindsey updated GEODE-7326:
-
Description: 
h3. Why
Users want to understand the performance of their operations within the server.

h3. Acceptance Criteria
Type: timer
Name: geode.cache.gets
Tags: region, result=hit/miss
Lifecycle of meter: The hit/miss meter for each region is created when the 
region is created. The meter(s) are removed when the region is destroyed/closed.
Description for meter: The total time and count for GET requests from clients.
Thing to measure : A count and total time for GET operations that didn't error, 
by this specific Server (1 or many cacheservers) in the geode cluster from when 
the server receives the request to when it sends the response.

Business Rule for this measurement: This meter records any operation sent 
through a CacheServer

h3. Scenarios

*Scenario: Java client hits*
Given a cluster with a Server1 and a Locator1 with time statistics enabled
When the oldest supported java client issues 5 get operations using the 
region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java client misses*
Given a cluster with a Server1 and a Locator1 with time statistics enabled
When the oldest supported java client issues 5 get operations where the user is 
getting a key that doesn't exist in the region using the region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=miss

*Scenario: Java client hits with time stats disabled*
Given a cluster with a Server1 and a Locator1 with time statistics disabled
When a java client issues a get operation using the region.get(key) command 
where the key exists
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 1
- Total Time = 0
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java client error response*
Given a cluster with a Server1
And a RegionA exists with NO entry with a Key="1"
And the client is unauthorized for Key="1"
When the client issues a region.get(1) request
Then no meter on Server1 should exist like:
- Meter Name = 'geode.cache.gets'
- Tag: region = RegionA


  was:
h3. Why
Users want to understand the performance of their operations within the server.

h3. Acceptance Criteria
Type: timer
Name: geode.cache.gets
Tags: region, result=hit/miss
Lifecycle of meter: The hit/miss meter for each region is created when the 
region is created. The meter(s) are removed when the region is destroyed/closed.
Description for meter: The total time and count for GET requests from clients.
Thing to measure : A count and total time for GET operations that didn't error, 
by this specific Server (1 or many cacheservers) in the geode cluster from when 
the server receives the request to when it sends the response.

Business Rule for this measurement: This meter records any operation sent 
through a CacheServer

h3. Scenarios

*Scenario: Java Client Hits*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations using the 
region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java Client Misses*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations where the user is 
getting a key that doesn't exist in the region using the region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=miss

*Scenario: Java client error response*
Given a cluster with a Server1
And a RegionA exists with NO entry with a Key="1"
And the client is unauthorized for Key="1"
When the client issues a region.get(1) request
Then no meter on Server1 should exist like:
- Meter Name = 'geode.cache.gets'
- Tag: region = RegionA



> Add cache gets timers
> -
>
> Key: GEODE-7326
> URL: https://issues.apache.org/jira/browse/GEODE-7326
> Project: Geode
>  Issue Type: Improvement
>Reporter: Aaron Lindsey
>

[jira] [Updated] (GEODE-7326) Add cache gets timers



 [ 
https://issues.apache.org/jira/browse/GEODE-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Lindsey updated GEODE-7326:
-
Description: 
h3. Why
Users want to understand the performance of their operations within the server.

h3. Acceptance Criteria
Type: timer
Name: geode.cache.gets
Tags: region, result=hit/miss
Lifecycle of meter: The hit/miss meter for each region is created when the 
region is created. The meter(s) are removed when the region is destroyed/closed.
Description for meter: The total time and count for GET requests from clients.
Thing to measure : A count and total time for GET operations that didn't error, 
by this specific Server (1 or many cacheservers) in the geode cluster from when 
the server receives the request to when it sends the response.

Business Rule for this measurement: This meter records any operation sent 
through a CacheServer

h3. Scenarios

*Scenario: Java Client Hits*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations using the 
region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java Client Misses*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations where the user is 
getting a key that doesn't exist in the region using the region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=miss

*Scenario: Java client error response*
Given a cluster with a Server1
And a RegionA exists with NO entry with a Key="1"
And a CacheLoader that throws an exception when invoked
When the client issues a region.get(1) request
Then no meter on Server1 should exist like:
- Meter Name = 'geode.cache.gets'
- Tag: region = RegionA


  was:
h3. Why
Users want to understand the performance of their operations within the server.

h3. Acceptance Criteria
Type: timer
Name: geode.cache.gets
Tags: region, result=hit/miss
Lifecycle of meter: The hit/miss meter for each region is created when the 
first GET on that user region happens. The meter(s) are only removed when the 
cache is closed.
Description for meter: The total time and count for GET requests from clients.
Thing to measure : A count and total time for GET operations that didn't error, 
by this specific Server (1 or many cacheservers) in the geode cluster from when 
the server receives the request to when it sends the response.

Business Rule for this measurement: This meter records any operation sent 
through a CacheServer

h3. Scenarios

*Scenario: Java Client Hits*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations using the 
region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java Client Misses*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations where the user is 
getting a key that doesn't exist in the region using the region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=miss

*Scenario: Java client error response*
Given a cluster with a Server1
And a RegionA exists with NO entry with a Key="1"
And a CacheLoader that throws an exception when invoked
When the client issues a region.get(1) request
Then no meter on Server1 should exist like:
- Meter Name = 'geode.cache.gets'
- Tag: region = RegionA



> Add cache gets timers
> -
>
> Key: GEODE-7326
> URL: https://issues.apache.org/jira/browse/GEODE-7326
> Project: Geode
>  Issue Type: Improvement
>Reporter: Aaron Lindsey
>Assignee: Aaron Lindsey
>Priority: Major
>
> h3. Why
> Users want to understand the performance of their operations within the 
> server.
> h3. Acceptance Criteria
> Type: timer
> Name: geode.cache.gets
> Tags: region, result=hit/miss
> Lifecycle of meter: The hit/miss meter for each region is created when the 
> region is created. The meter(s) are removed when the region is 
> destroyed/closed.
> Description

[jira] [Updated] (GEODE-7326) Add cache gets timers



 [ 
https://issues.apache.org/jira/browse/GEODE-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Lindsey updated GEODE-7326:
-
Description: 
h3. Why
Users want to understand the performance of their operations within the server.

h3. Acceptance Criteria
Type: timer
Name: geode.cache.gets
Tags: region, result=hit/miss
Lifecycle of meter: The hit/miss meter for each region is created when the 
region is created. The meter(s) are removed when the region is destroyed/closed.
Description for meter: The total time and count for GET requests from clients.
Thing to measure : A count and total time for GET operations that didn't error, 
by this specific Server (1 or many cacheservers) in the geode cluster from when 
the server receives the request to when it sends the response.

Business Rule for this measurement: This meter records any operation sent 
through a CacheServer

h3. Scenarios

*Scenario: Java Client Hits*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations using the 
region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java Client Misses*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations where the user is 
getting a key that doesn't exist in the region using the region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=miss

*Scenario: Java client error response*
Given a cluster with a Server1
And a RegionA exists with NO entry with a Key="1"
And the client is unauthorized for Key="1"
When the client issues a region.get(1) request
Then no meter on Server1 should exist like:
- Meter Name = 'geode.cache.gets'
- Tag: region = RegionA


  was:
h3. Why
Users want to understand the performance of their operations within the server.

h3. Acceptance Criteria
Type: timer
Name: geode.cache.gets
Tags: region, result=hit/miss
Lifecycle of meter: The hit/miss meter for each region is created when the 
region is created. The meter(s) are removed when the region is destroyed/closed.
Description for meter: The total time and count for GET requests from clients.
Thing to measure : A count and total time for GET operations that didn't error, 
by this specific Server (1 or many cacheservers) in the geode cluster from when 
the server receives the request to when it sends the response.

Business Rule for this measurement: This meter records any operation sent 
through a CacheServer

h3. Scenarios

*Scenario: Java Client Hits*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations using the 
region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=hit

*Scenario: Java Client Misses*
Given a cluster with a Server1 and a Locator1 
When the oldest supported java client issues 5 get operations where the user is 
getting a key that doesn't exist in the region using the region.get(key) command
Then a meter on Server1 exists such that:
- Meter Name = 'geode.cache.gets'
- Count = 5
- Total Time = total time spent from received request to response to client for 
these 5 requests
- Tag: region = region that the 'get' method was called against
- Tag: result=miss

*Scenario: Java client error response*
Given a cluster with a Server1
And a RegionA exists with NO entry with a Key="1"
And a CacheLoader that throws an exception when invoked
When the client issues a region.get(1) request
Then no meter on Server1 should exist like:
- Meter Name = 'geode.cache.gets'
- Tag: region = RegionA



> Add cache gets timers
> -
>
> Key: GEODE-7326
> URL: https://issues.apache.org/jira/browse/GEODE-7326
> Project: Geode
>  Issue Type: Improvement
>Reporter: Aaron Lindsey
>Assignee: Aaron Lindsey
>Priority: Major
>
> h3. Why
> Users want to understand the performance of their operations within the 
> server.
> h3. Acceptance Criteria
> Type: timer
> Name: geode.cache.gets
> Tags: region, result=hit/miss
> Lifecycle of meter: The hit/miss meter for each region is created when the 
> region is created. The meter(s) are removed when the region is 
> destroyed/closed.
> Description for meter: The total time and

[jira] [Resolved] (GEODE-6153) Geode incorrectly parses the 'locators' property throwing a NullPointerException

2019-10-22 Thread Ernest Burghardt (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ernest Burghardt resolved GEODE-6153.
-
Fix Version/s: 1.11.0
   Resolution: Duplicate

> Geode incorrectly parses the 'locators' property throwing a 
> NullPointerException
> 
>
> Key: GEODE-6153
> URL: https://issues.apache.org/jira/browse/GEODE-6153
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: John Blum
>Assignee: Dan Smith
>Priority: Major
>  Labels: affects-spring
> Fix For: 1.11.0
>
>
> When defining Geode Properties and using the API to start a Geode Server 
> connecting to an existing Locator, if the {{hostname}} of the Locator is 
> incorrectly typed, Geode will throw a {{NullPointerException}}.
> For instance, if I define Geode Properties using...
> {code:java}
> ...
>   private static Properties gemfireProperties() {
> Properties gemfireProperties = new Properties();
> gemfireProperties.setProperty("name", "SessionGeodeServer");
> gemfireProperties.setProperty("log-level", LOG_LEVEL);
> gemfireProperties.setProperty("locators", "loclhost[10334]");
> gemfireProperties.setProperty("jmx-manager", "true");
> gemfireProperties.setProperty("jmx-manager-start", "true");
> gemfireProperties.setProperty("start-locator", "localhost[10334]");
> return gemfireProperties;
>   }
>   private static Cache gemfireCache(Properties gemfireProperties) {
> return new CacheFactory(gemfireProperties).create();
>   }
> ...
> {code}
> And, as you can see, I mistyped "localhost" as "loclhost" in 
> {{gemfireProperties.setProperty("locators", "loclhost[10334]");}}, this 
> results in...
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSUtil.parseLocators(GMSUtil.java:91)
>   at 
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.(GMSLocator.java:109)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newLocatorHandler(GMSMemberFactory.java:125)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newLocatorHandler(MemberFactory.java:100)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:537)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:867)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:749)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> example.tests.geode.SessionGeodeServer.gemfireCache(SessionGeodeServer.java:70)
>   at 
> example.tests.geode.SessionGeodeServer.main(SessionGeodeServer.java:52)
> {code}
> Even worse, if I had not set my {{log-level}} to at least "warn" (e.g. 
> suppose I set the {{log-level}} to "error") I would possibly never have seen 
> these warning messages...
> {code:java}
> [warn 2018/12/06 10:14:34.365 PST  tid=0x1] Unknown locator host: 
> loclhost
> [warn 2018/12/06 10:14:34.367 PST  tid=0x1] Unknown locator host: 
> loclhost
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7167) Geode incorrectly parses the 'locators' property throwing a NullPointerException

2019-10-22 Thread Ernest Burghardt (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ernest Burghardt resolved GEODE-7167.
-
Fix Version/s: 1.11.0
   Resolution: Fixed

> Geode incorrectly parses the 'locators' property throwing a 
> NullPointerException
> 
>
> Key: GEODE-7167
> URL: https://issues.apache.org/jira/browse/GEODE-7167
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Bill Burcham
>Assignee: Bill Burcham
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When defining Geode Properties and using the API to start a Geode Server 
> connecting to an existing Locator, if the {{hostname}} of the Locator is 
> incorrectly typed, Geode will throw a {{NullPointerException}}.
> For instance, if I define Geode Properties using...
> {code:java}
> ...
>   private static Properties gemfireProperties() {
> Properties gemfireProperties = new Properties();
> gemfireProperties.setProperty("name", "SessionGeodeServer");
> gemfireProperties.setProperty("log-level", LOG_LEVEL);
> gemfireProperties.setProperty("locators", "loclhost[10334]");
> gemfireProperties.setProperty("jmx-manager", "true");
> gemfireProperties.setProperty("jmx-manager-start", "true");
> gemfireProperties.setProperty("start-locator", "localhost[10334]");
> return gemfireProperties;
>   }
>   private static Cache gemfireCache(Properties gemfireProperties) {
> return new CacheFactory(gemfireProperties).create();
>   }
> ...
> {code}
> And, as you can see, I mistyped "localhost" as "loclhost" in 
> {{gemfireProperties.setProperty("locators", "loclhost[10334]");}}, this 
> results in...
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSUtil.parseLocators(GMSUtil.java:91)
>   at 
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.(GMSLocator.java:109)
>   at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newLocatorHandler(GMSMemberFactory.java:125)
>   at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newLocatorHandler(MemberFactory.java:100)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:537)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:867)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:749)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:343)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:219)
>   at 
> example.tests.geode.SessionGeodeServer.gemfireCache(SessionGeodeServer.java:70)
>   at 
> example.tests.geode.SessionGeodeServer.main(SessionGeodeServer.java:52)
> {code}
> Even worse, if I had not set my {{log-level}} to at least "warn" (e.g. 
> suppose I set the {{log-level}} to "error") I would possibly never have seen 
> these warning messages...
> {code:java}
> [warn 2018/12/06 10:14:34.365 PST  tid=0x1] Unknown locator host: 
> loclhost
> [warn 2018/12/06 10:14:34.367 PST  tid=0x1] Unknown locator host: 
> loclhost
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-7326) Add cache gets timers



 [ 
https://issues.apache.org/jira/browse/GEODE-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Lindsey updated GEODE-7326:
-
Summary: Add cache gets timers  (was: Add cache gets timer)

> Add cache gets timers
> -
>
> Key: GEODE-7326
> URL: https://issues.apache.org/jira/browse/GEODE-7326
> Project: Geode
>  Issue Type: Improvement
>Reporter: Aaron Lindsey
>Priority: Major
>
> h3. Why
> Users want to understand the performance of their operations within the 
> server.
> h3. Acceptance Criteria
> Type: timer
> Name: geode.cache.gets
> Tags: region, result=hit/miss
> Lifecycle of meter: The hit/miss meter for each region is created when the 
> first GET on that user region happens. The meter(s) are only removed when the 
> cache is closed.
> Description for meter: The total time and count for GET requests from clients.
> Thing to measure : A count and total time for GET operations that didn't 
> error, by this specific Server (1 or many cacheservers) in the geode cluster 
> from when the server receives the request to when it sends the response.
> Business Rule for this measurement: This meter records any operation sent 
> through a CacheServer
> h3. Scenarios
> *Scenario: Java Client Hits*
> Given a cluster with a Server1 and a Locator1 
> When the oldest supported java client issues 5 get operations using the 
> region.get(key) command
> Then a meter on Server1 exists such that:
> - Meter Name = 'geode.cache.gets'
> - Count = 5
> - Total Time = total time spent from received request to response to client 
> for these 5 requests
> - Tag: region = region that the 'get' method was called against
> - Tag: result=hit
> *Scenario: Java Client Misses*
> Given a cluster with a Server1 and a Locator1 
> When the oldest supported java client issues 5 get operations where the user 
> is getting a key that doesn't exist in the region using the region.get(key) 
> command
> Then a meter on Server1 exists such that:
> - Meter Name = 'geode.cache.gets'
> - Count = 5
> - Total Time = total time spent from received request to response to client 
> for these 5 requests
> - Tag: region = region that the 'get' method was called against
> - Tag: result=miss
> *Scenario: Java client error response*
> Given a cluster with a Server1
> And a RegionA exists with NO entry with a Key="1"
> And a CacheLoader that throws an exception when invoked
> When the client issues a region.get(1) request
> Then no meter on Server1 should exist like:
> - Meter Name = 'geode.cache.gets'
> - Tag: region = RegionA



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7326) Add cache gets timers

2019-10-22 Thread ASF subversion and git services (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aaron Lindsey reassigned GEODE-7326:


Assignee: Aaron Lindsey

> Add cache gets timers
> -
>
> Key: GEODE-7326
> URL: https://issues.apache.org/jira/browse/GEODE-7326
> Project: Geode
>  Issue Type: Improvement
>Reporter: Aaron Lindsey
>Assignee: Aaron Lindsey
>Priority: Major
>
> h3. Why
> Users want to understand the performance of their operations within the 
> server.
> h3. Acceptance Criteria
> Type: timer
> Name: geode.cache.gets
> Tags: region, result=hit/miss
> Lifecycle of meter: The hit/miss meter for each region is created when the 
> first GET on that user region happens. The meter(s) are only removed when the 
> cache is closed.
> Description for meter: The total time and count for GET requests from clients.
> Thing to measure : A count and total time for GET operations that didn't 
> error, by this specific Server (1 or many cacheservers) in the geode cluster 
> from when the server receives the request to when it sends the response.
> Business Rule for this measurement: This meter records any operation sent 
> through a CacheServer
> h3. Scenarios
> *Scenario: Java Client Hits*
> Given a cluster with a Server1 and a Locator1 
> When the oldest supported java client issues 5 get operations using the 
> region.get(key) command
> Then a meter on Server1 exists such that:
> - Meter Name = 'geode.cache.gets'
> - Count = 5
> - Total Time = total time spent from received request to response to client 
> for these 5 requests
> - Tag: region = region that the 'get' method was called against
> - Tag: result=hit
> *Scenario: Java Client Misses*
> Given a cluster with a Server1 and a Locator1 
> When the oldest supported java client issues 5 get operations where the user 
> is getting a key that doesn't exist in the region using the region.get(key) 
> command
> Then a meter on Server1 exists such that:
> - Meter Name = 'geode.cache.gets'
> - Count = 5
> - Total Time = total time spent from received request to response to client 
> for these 5 requests
> - Tag: region = region that the 'get' method was called against
> - Tag: result=miss
> *Scenario: Java client error response*
> Given a cluster with a Server1
> And a RegionA exists with NO entry with a Key="1"
> And a CacheLoader that throws an exception when invoked
> When the client issues a region.get(1) request
> Then no meter on Server1 should exist like:
> - Meter Name = 'geode.cache.gets'
> - Tag: region = RegionA



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7331) Improve docs on logging (with optional Log4j)

2019-10-22 Thread Karen Smoler Miller (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7331.

Fix Version/s: 1.11.0
   Resolution: Fixed

> Improve docs on logging (with optional Log4j)
> -
>
> Key: GEODE-7331
> URL: https://issues.apache.org/jira/browse/GEODE-7331
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Log4j is in its own module.  Update the docs to reflect changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7281) Ensure that UpdatePassingTokens only moves forward in Git



[ 
https://issues.apache.org/jira/browse/GEODE-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957346#comment-16957346
 ] 

ASF subversion and git services commented on GEODE-7281:


Commit addaebcb799b926a2a088202ad07a74367095453 in geode's branch 
refs/heads/develop from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=addaebc ]

GEODE-7281: UpdatePassingTokens only moves git sha forward. (#4134)

* GEODE-7281: UpdatePassingTokens only moves git sha forward.

Use `git merge-base --is-ancestor  ` to check that the SHA we
publish as 'passing' is moving forward in git history.

* force git behavior in attach-sha-to-branch


> Ensure that UpdatePassingTokens only moves forward in Git
> -
>
> Key: GEODE-7281
> URL: https://issues.apache.org/jira/browse/GEODE-7281
> Project: Geode
>  Issue Type: Task
>  Components: ci
>Reporter: Robert Houghton
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> During concourse migration, or during a fan-in from parallel tasks, it may 
> happen that Geode SHAs get through the pipeline out-of-order. Ensure that we 
> do not 'move backwards' in git history when this occurs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7281) Ensure that UpdatePassingTokens only moves forward in Git

2019-10-22 Thread ASF subversion and git services (Jira)



[ 
https://issues.apache.org/jira/browse/GEODE-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957345#comment-16957345
 ] 

ASF subversion and git services commented on GEODE-7281:


Commit addaebcb799b926a2a088202ad07a74367095453 in geode's branch 
refs/heads/develop from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=addaebc ]

GEODE-7281: UpdatePassingTokens only moves git sha forward. (#4134)

* GEODE-7281: UpdatePassingTokens only moves git sha forward.

Use `git merge-base --is-ancestor  ` to check that the SHA we
publish as 'passing' is moving forward in git history.

* force git behavior in attach-sha-to-branch


> Ensure that UpdatePassingTokens only moves forward in Git
> -
>
> Key: GEODE-7281
> URL: https://issues.apache.org/jira/browse/GEODE-7281
> Project: Geode
>  Issue Type: Task
>  Components: ci
>Reporter: Robert Houghton
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> During concourse migration, or during a fan-in from parallel tasks, it may 
> happen that Geode SHAs get through the pipeline out-of-order. Ensure that we 
> do not 'move backwards' in git history when this occurs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7135) Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED

2019-10-22 Thread ASF subversion and git services (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Hanson reassigned GEODE-7135:
--

Assignee: Mark Hanson

> Tomcat8SessionsDUnitTest > testSessionExpiration1 FAILED
> 
>
> Key: GEODE-7135
> URL: https://issues.apache.org/jira/browse/GEODE-7135
> Project: Geode
>  Issue Type: Bug
>Reporter: Murtuza Boxwala
>Assignee: Mark Hanson
>Priority: Major
>
> {code:java}
> org.apache.geode.modules.session.Tomcat8SessionsDUnitTest > 
> testSessionExpiration1 FAILED
> java.net.ConnectException: Connection refused (Connection refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7331) Improve docs on logging (with optional Log4j)



[ 
https://issues.apache.org/jira/browse/GEODE-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957273#comment-16957273
 ] 

ASF subversion and git services commented on GEODE-7331:


Commit 882985e907c231a01fe21bd9ab141f35148b243f in geode's branch 
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=882985e ]

GEODE-7331 Improve docs on loggin (Log4j is optional) (#4195)



> Improve docs on logging (with optional Log4j)
> -
>
> Key: GEODE-7331
> URL: https://issues.apache.org/jira/browse/GEODE-7331
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Log4j is in its own module.  Update the docs to reflect changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-6897) Create a REST v2 endpoint to do rebalance

2019-10-22 Thread Dick Cavender (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dick Cavender updated GEODE-6897:
-
Summary: Create a REST v2 endpoint to do rebalance  (was: Create a REST v2 
endpoint to do rebanlance)

> Create a REST v2 endpoint to do rebalance
> -
>
> Key: GEODE-6897
> URL: https://issues.apache.org/jira/browse/GEODE-6897
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>Reporter: Jinmei Liao
>Assignee: Owen Nichols
>Priority: Major
> Fix For: 1.10.0
>
>  Time Spent: 35h
>  Remaining Estimate: 0h
>
> For the first iteration, we are:
> 1. make it an async request
> 2. have an endpoint to check status of this request
> 3. keep the rebalance operation status in memory only
> 4. Can do one rebalance at a time, ignore the concurrent rebalance request
> 5. do not implement cancel operation yet.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7335) CI failure: TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails with ContainerException: Server port 22617 did not shutdown within the timeout



 [ 
https://issues.apache.org/jira/browse/GEODE-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Hanson reassigned GEODE-7335:
--

Assignee: Mark Hanson

> CI failure: 
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
> with ContainerException: Server port 22617 did not shutdown within the 
> timeout period
> ---
>
> Key: GEODE-7335
> URL: https://issues.apache.org/jira/browse/GEODE-7335
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Mark Hanson
>Priority: Major
>  Labels: CI, Flaky
>
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 
> 7.x container. Check the 
> [/home/geode/geode/geode-assembly/build/upgradeTest54/cargo_logs/TOMCAT7_client-server_test0_1_8b40f4f1-1c3c-4c78-9e8e-dc934c7ce7aa/container.log]
>  file containing the container logs for more details.
>   at 
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:305)
>   at 
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:233)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
>   at 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:173)
>   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.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
>

[jira] [Assigned] (GEODE-7336) UpgradeTestOpenJDK8/11 failing in PR and CI



 [ 
https://issues.apache.org/jira/browse/GEODE-7336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Hanson reassigned GEODE-7336:
--

Assignee: Mark Hanson

> UpgradeTestOpenJDK8/11 failing in PR and CI
> ---
>
> Key: GEODE-7336
> URL: https://issues.apache.org/jira/browse/GEODE-7336
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Mark Hanson
>Assignee: Mark Hanson
>Priority: Major
>
> Looks like gradle is exiting for some reason. Here is just one example It 
> does not appear to correlate to a checkin so looking at it the checkin might 
> be a red herring.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4557]
>  
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4555|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4555#L5d9758d6:713:713]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4552]
>  
> {noformat}
> > Task :geode-assembly:docs
> 09:15:31> Task :geode-assembly:installDist
> 09:15:31> Task :geode-assembly:compileUpgradeTestJava
> 09:15:56> Task :geode-assembly:upgradeTestClasses
> 09:15:57> Task :geode-lucene:upgradeTest
> 09:15:57> Task :geode-wan:upgradeTest
> 09:16:01> Task :geode-core:upgradeTest
> 09:25:12> Task :geode-assembly:upgradeTest
> 09:25:12
> 09:25:12The message received from the daemon indicates that the daemon has 
> disappeared.
> 09:25:12Build request sent: Build{id=001d3438-086b-4d20-b08c-d57006b0f947, 
> currentDir=/home/geode/geode}
> 09:25:13Attempting to read last messages from the daemon log...
> 09:25:13Daemon pid: 5359
> 09:25:13  log file: /home/geode/.gradle/daemon/5.4/daemon-5359.out.log
> 09:25:13- Last  20 lines from daemon log file - daemon-5359.out.log -
> 09:25:13Note: Recompile with -Xlint:unchecked for details.
> 09:25:13Note: Some input files use or override a deprecated API.
> 09:25:13Note: Recompile with -Xlint:deprecation for details.
> 09:25:13Note: Some input files use unchecked or unsafe operations.
> 09:25:13Note: Recompile with -Xlint:unchecked for details.
> 09:25:13Note: Some input files use or override a deprecated API.
> 09:25:13Note: Recompile with -Xlint:deprecation for details.
> 09:25:13Note: Some input files use or override a deprecated API.
> 09:25:13Note: Recompile with -Xlint:deprecation for details.
> 09:25:13Note: 
> /home/geode/geode/geode-lucene/src/upgradeTest/java/org/apache/geode/cache/lucene/LuceneSearchWithRollingUpgradeDUnit.java
>  uses unchecked or unsafe operations.
> 09:25:13Note: Recompile with -Xlint:unchecked for details.
> 09:25:13Note: Some input files use or override a deprecated API.
> 09:25:13Note: Recompile with -Xlint:deprecation for details.
> 09:25:13Note: Some input files use unchecked or unsafe operations.
> 09:25:13Note: Recompile with -Xlint:unchecked for details.
> 09:25:13Do not allow more than 48 test workers
> 09:25:13Note: Some input files use or override a deprecated API.
> 09:25:13Note: Recompile with -Xlint:deprecation for details.
> 09:25:13Note: Some input files use unchecked or unsafe operations.
> 09:25:13Note: Recompile with -Xlint:unchecked for details.
> 09:25:13- End of the daemon log -
> 09:25:13
> 09:25:13
> 09:25:13FAILURE: Build failed with an exception.
> 09:25:13
> 09:25:13* What went wrong:
> 09:25:13Gradle build daemon disappeared unexpectedly (it may have been killed 
> or may have crashed)
> 09:25:13
> 09:25:13* Try:
> 09:25:13Run with --stacktrace option to get the stack trace. Run with --info 
> or --debug option to get more log output. Run with --scan to get full 
> insights.
> 09:25:13
> 09:25:13* Get more help at https://help.gradle.org {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7336) UpgradeTestOpenJDK8/11 failing in PR and CI

Mark Hanson created GEODE-7336:
--

Summary: UpgradeTestOpenJDK8/11 failing in PR and CI
Key: GEODE-7336
URL: https://issues.apache.org/jira/browse/GEODE-7336
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Mark Hanson

Looks like gradle is exiting for some reason. Here is just one example It
does not appear to correlate to a checkin so looking at it the checkin might be
a red herring.

[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4557]

[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4555|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4555#L5d9758d6:713:713]

[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK11/builds/4552]

{noformat}
> Task :geode-assembly:docs
09:15:31> Task :geode-assembly:installDist
09:15:31> Task :geode-assembly:compileUpgradeTestJava
09:15:56> Task :geode-assembly:upgradeTestClasses
09:15:57> Task :geode-lucene:upgradeTest
09:15:57> Task :geode-wan:upgradeTest
09:16:01> Task :geode-core:upgradeTest
09:25:12> Task :geode-assembly:upgradeTest
09:25:12
09:25:12The message received from the daemon indicates that the daemon has
disappeared.
09:25:12Build request sent: Build{id=001d3438-086b-4d20-b08c-d57006b0f947,
currentDir=/home/geode/geode}
09:25:13Attempting to read last messages from the daemon log...
09:25:13Daemon pid: 5359
09:25:13 log file: /home/geode/.gradle/daemon/5.4/daemon-5359.out.log
09:25:13- Last 20 lines from daemon log file - daemon-5359.out.log -
09:25:13Note: Recompile with -Xlint:unchecked for details.
09:25:13Note: Some input files use or override a deprecated API.
09:25:13Note: Recompile with -Xlint:deprecation for details.
09:25:13Note: Some input files use unchecked or unsafe operations.
09:25:13Note: Recompile with -Xlint:unchecked for details.
09:25:13Note: Some input files use or override a deprecated API.
09:25:13Note: Recompile with -Xlint:deprecation for details.
09:25:13Note: Some input files use or override a deprecated API.
09:25:13Note: Recompile with -Xlint:deprecation for details.
09:25:13Note:
/home/geode/geode/geode-lucene/src/upgradeTest/java/org/apache/geode/cache/lucene/LuceneSearchWithRollingUpgradeDUnit.java
uses unchecked or unsafe operations.
09:25:13Note: Recompile with -Xlint:unchecked for details.
09:25:13Note: Some input files use or override a deprecated API.
09:25:13Note: Recompile with -Xlint:deprecation for details.
09:25:13Note: Some input files use unchecked or unsafe operations.
09:25:13Note: Recompile with -Xlint:unchecked for details.
09:25:13Do not allow more than 48 test workers
09:25:13Note: Some input files use or override a deprecated API.
09:25:13Note: Recompile with -Xlint:deprecation for details.
09:25:13Note: Some input files use unchecked or unsafe operations.
09:25:13Note: Recompile with -Xlint:unchecked for details.
09:25:13- End of the daemon log -
09:25:13
09:25:13
09:25:13FAILURE: Build failed with an exception.
09:25:13
09:25:13* What went wrong:
09:25:13Gradle build daemon disappeared unexpectedly (it may have been killed
or may have crashed)
09:25:13
09:25:13* Try:
09:25:13Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output. Run with --scan to get full insights.
09:25:13
09:25:13* Get more help at https://help.gradle.org {noformat}

--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7335) CI failure: TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails with ContainerException: Server port 22617 did not shutdown within the timeout



[ 
https://issues.apache.org/jira/browse/GEODE-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957227#comment-16957227
 ] 

Kirk Lund commented on GEODE-7335:
--

See: 
http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0239/test-results/upgradeTest/1571699665/

> CI failure: 
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
> with ContainerException: Server port 22617 did not shutdown within the 
> timeout period
> ---
>
> Key: GEODE-7335
> URL: https://issues.apache.org/jira/browse/GEODE-7335
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
>
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 
> 7.x container. Check the 
> [/home/geode/geode/geode-assembly/build/upgradeTest54/cargo_logs/TOMCAT7_client-server_test0_1_8b40f4f1-1c3c-4c78-9e8e-dc934c7ce7aa/container.log]
>  file containing the container logs for more details.
>   at 
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:305)
>   at 
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:233)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
>   at 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:173)
>   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.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at

[jira] [Updated] (GEODE-7335) CI failure: TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails with ContainerException: Server port 22617 did not shutdown within the timeout p



 [ 
https://issues.apache.org/jira/browse/GEODE-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund updated GEODE-7335:
-
Summary: CI failure: 
TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
with ContainerException: Server port 22617 did not shutdown within the timeout 
period  (was: 
TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
with ContainerException: Server port 22617 did not shutdown within the timeout 
period)

> CI failure: 
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
> with ContainerException: Server port 22617 did not shutdown within the 
> timeout period
> ---
>
> Key: GEODE-7335
> URL: https://issues.apache.org/jira/browse/GEODE-7335
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
>
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 
> 7.x container. Check the 
> [/home/geode/geode/geode-assembly/build/upgradeTest54/cargo_logs/TOMCAT7_client-server_test0_1_8b40f4f1-1c3c-4c78-9e8e-dc934c7ce7aa/container.log]
>  file containing the container logs for more details.
>   at 
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:305)
>   at 
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:233)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
>   at 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:173)
>   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.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
>

[jira] [Created] (GEODE-7335) TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails with ContainerException: Server port 22617 did not shutdown within the timeout period

Kirk Lund created GEODE-7335:


 Summary: 
TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
with ContainerException: Server port 22617 did not shutdown within the timeout 
period
 Key: GEODE-7335
 URL: https://issues.apache.org/jira/browse/GEODE-7335
 Project: Geode
  Issue Type: Improvement
  Components: tests
Reporter: Kirk Lund


{noformat}
org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 7.x 
container. Check the 
[/home/geode/geode/geode-assembly/build/upgradeTest54/cargo_logs/TOMCAT7_client-server_test0_1_8b40f4f1-1c3c-4c78-9e8e-dc934c7ce7aa/container.log]
 file containing the container logs for more details.
at 
org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:305)
at 
org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:233)
at 
org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
at 
org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
at 
org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
at 
org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:173)
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.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at 
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at

[jira] [Updated] (GEODE-7335) TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails with ContainerException: Server port 22617 did not shutdown within the timeout period



 [ 
https://issues.apache.org/jira/browse/GEODE-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund updated GEODE-7335:
-
Labels: CI Flaky  (was: )

> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
> with ContainerException: Server port 22617 did not shutdown within the 
> timeout period
> ---
>
> Key: GEODE-7335
> URL: https://issues.apache.org/jira/browse/GEODE-7335
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
>
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 
> 7.x container. Check the 
> [/home/geode/geode/geode-assembly/build/upgradeTest54/cargo_logs/TOMCAT7_client-server_test0_1_8b40f4f1-1c3c-4c78-9e8e-dc934c7ce7aa/container.log]
>  file containing the container logs for more details.
>   at 
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:305)
>   at 
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:233)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
>   at 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:173)
>   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.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
>

[jira] [Updated] (GEODE-7335) TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails with ContainerException: Server port 22617 did not shutdown within the timeout period



 [ 
https://issues.apache.org/jira/browse/GEODE-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund updated GEODE-7335:
-
Issue Type: Bug  (was: Improvement)

> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest fails 
> with ContainerException: Server port 22617 did not shutdown within the 
> timeout period
> ---
>
> Key: GEODE-7335
> URL: https://issues.apache.org/jira/browse/GEODE-7335
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Priority: Major
>
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Tomcat 
> 7.x container. Check the 
> [/home/geode/geode/geode-assembly/build/upgradeTest54/cargo_logs/TOMCAT7_client-server_test0_1_8b40f4f1-1c3c-4c78-9e8e-dc934c7ce7aa/container.log]
>  file containing the container logs for more details.
>   at 
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:305)
>   at 
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:233)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
>   at 
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
>   at 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:173)
>   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.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>   at 
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
>

[jira] [Commented] (GEODE-7183) CI Failure: ClientServerFunctionExecutionDUnitTest > testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] failed with AssertionError

2019-10-22 Thread ASF subversion and git services (Jira)



[ 
https://issues.apache.org/jira/browse/GEODE-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957224#comment-16957224
 ] 

Kirk Lund commented on GEODE-7183:
--

This test continues to fail: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1211


> CI Failure: ClientServerFunctionExecutionDUnitTest > 
> testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] failed 
> with AssertionError
> --
>
> Key: GEODE-7183
> URL: https://issues.apache.org/jira/browse/GEODE-7183
> Project: Geode
>  Issue Type: Bug
>  Components: functions
>Reporter: Barrett Oglesby
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest
>  > testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] 
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest$$Lambda$68/1900027546.run
>  in VM 3 running on Host 6c6dc0c2627c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.testServerExecution_SocketTimeOut_WithoutRegister(ClientServerFunctionExecutionDUnitTest.java:339)
> Caused by:
> java.lang.AssertionError: Test failed after the execute operation
> at org.junit.Assert.fail(Assert.java:88)
> at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.allServerExecution(ClientServerFunctionExecutionDUnitTest.java:891)
> at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.lambda$testServerExecution_SocketTimeOut_WithoutRegister$bb17a952$2(ClientServerFunctionExecutionDUnitTest.java:339)
> {noformat}
> The test logs this exception right before the failure:
> {noformat}
> [vm3] [info 2019/09/09 18:00:10.793 GMT RMI TCP 
> Connection(26)-172.17.0.19 tid=0xb1] Exception : 
> [vm3] org.apache.geode.cache.client.ServerConnectivityException: Pool 
> unexpected SocketException connection=Pooled Connection to 
> 6c6dc0c2627c:25980: Connection[DESTROYED]). Server unreachable: could not 
> connect after 1 attempts
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:331)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:300)
> [vm3] at 
> org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:814)
> [vm3] at 
> org.apache.geode.cache.client.internal.SingleHopOperationCallable.call(SingleHopOperationCallable.java:52)
> [vm3] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [vm3] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm3] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> [vm3] Caused by: java.net.SocketException: Socket is closed
> [vm3] at java.net.Socket.setSoTimeout(Socket.java:1137)
> [vm3] at 
> org.apache.geode.cache.client.internal.AbstractOpWithTimeout.attempt(AbstractOpWithTimeout.java:48)
> [vm3] at 
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263)
> [vm3] at 
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329)
> [vm3] ... 7 more
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK8/builds/952
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0101/test-results/distributedTest/1568054303/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
>

[jira] [Resolved] (GEODE-7322) generate wiki page of Cluster Management Service from Swagger page

2019-10-22 Thread Owen Nichols (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Owen Nichols resolved GEODE-7322.
-
Fix Version/s: 1.11.0
   Resolution: Fixed

> generate wiki page of Cluster Management Service from Swagger page
> --
>
> Key: GEODE-7322
> URL: https://issues.apache.org/jira/browse/GEODE-7322
> Project: Geode
>  Issue Type: Bug
>  Components: management, rest (admin)
>Reporter: Gang Yan
>Assignee: Owen Nichols
>Priority: Major
> Fix For: 1.11.0
>
>
> #WHY
> we want to get the latest update of restapi, and update wiki page 
> automatically
> #WHAT
> find a programming way to update wiki page
> And sync the latest update of Swagger to wiki
> related:
> GEODE-7205 : https://issues.apache.org/jira/browse/GEODE-7205



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7205) sync wiki page of Cluster Management Service with Swagger page

2019-10-22 Thread Owen Nichols (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Owen Nichols resolved GEODE-7205.
-
Fix Version/s: 1.11.0
   Resolution: Fixed

> sync wiki page of Cluster Management Service with Swagger page
> --
>
> Key: GEODE-7205
> URL: https://issues.apache.org/jira/browse/GEODE-7205
> Project: Geode
>  Issue Type: Improvement
>  Components: management, rest (admin)
>Reporter: Gang Yan
>Assignee: Owen Nichols
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
>  
> #WHY
> there are a lot of stuff need to sync-up from Swagger page to wiki,  
> Including but not limited to :
> - class
>  - config --> configuration
>  - links
>  - group & groups
>  - experies
> And we do not want to update the wiki page again and again, and also the more 
> we delivered , the more update we need to publish on wiki page, so we need to 
> find a way to generate wiki page from Swagger page in programming way.
> #WHAT
> there is a Swagger page and api-docs, everything is there, so we need to find 
> a way to parse the swagger page to generate Wiki page.
>  1. find input
>  2. find output format on wiki 
>  3. parse the input to output format



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (GEODE-7205) sync wiki page of Cluster Management Service with Swagger page



[ 
https://issues.apache.org/jira/browse/GEODE-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957209#comment-16957209
 ] 

ASF subversion and git services commented on GEODE-7205:


Commit ccbb5deb5675312f4a2bfda1f9171de6b90bb63e in geode's branch 
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ccbb5de ]

GEODE-7205: add script to auto-generate wiki docs for management REST API 
(#4194)

[skip ci]

Co-authored-by: Joris Melchior 

> sync wiki page of Cluster Management Service with Swagger page
> --
>
> Key: GEODE-7205
> URL: https://issues.apache.org/jira/browse/GEODE-7205
> Project: Geode
>  Issue Type: Improvement
>  Components: management, rest (admin)
>Reporter: Gang Yan
>Assignee: Owen Nichols
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
>  
> #WHY
> there are a lot of stuff need to sync-up from Swagger page to wiki,  
> Including but not limited to :
> - class
>  - config --> configuration
>  - links
>  - group & groups
>  - experies
> And we do not want to update the wiki page again and again, and also the more 
> we delivered , the more update we need to publish on wiki page, so we need to 
> find a way to generate wiki page from Swagger page in programming way.
> #WHAT
> there is a Swagger page and api-docs, everything is there, so we need to find 
> a way to parse the swagger page to generate Wiki page.
>  1. find input
>  2. find output format on wiki 
>  3. parse the input to output format



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (GEODE-7332) Add OQL Aggregates link in docs

2019-10-22 Thread Karen Smoler Miller (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7332.

Fix Version/s: 1.11.0
 Assignee: Karen Smoler Miller
   Resolution: Fixed

> Add OQL Aggregates link in docs
> ---
>
> Key: GEODE-7332
> URL: https://issues.apache.org/jira/browse/GEODE-7332
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.11.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Small change, but useful. File 
> developing/querying_basics/what_is_a_query_string.html has a list of useful 
> query string building blocks.  Add a link to the descriptions of the OQL 
> aggregates to the list.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-7334) dev rest api failed to start when a JodaModel jar exists in the classpath

2019-10-22 Thread Jinmei Liao (Jira)



 [ 
https://issues.apache.org/jira/browse/GEODE-7334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao updated GEODE-7334:
---
Attachment: jackson-datatype-joda-2.9.8.jar
joda-time-2.1.jar

> dev rest api failed to start when a JodaModel jar exists in the classpath
> -
>
> Key: GEODE-7334
> URL: https://issues.apache.org/jira/browse/GEODE-7334
> Project: Geode
>  Issue Type: Bug
>  Components: rest (dev)
>Reporter: Jinmei Liao
>Priority: Major
> Attachments: jackson-datatype-joda-2.9.8.jar, joda-time-2.1.jar
>
>
> Steps to reproduce
> 1. Add jackson-datatype-joda-2.9.8.jarand joda-time-2.1.jar in the 
> server classpath
> 2. start the server with rest api started
> 3. examine the server log shows the following exception:
> [error 2019/09/13 05:43:21.681 BST rd1-server  tid=0x1] Context 
> initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 
> 'org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter':
>  Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter]:
>  Constructor threw exception; nested exception is 
> java.lang.ClassCastException: com.fasterxml.jackson.datatype.joda.JodaModule 
> cannot be cast to com.fasterxml.jackson.databind.Module
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1163)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1107)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
> at 
> org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:668)
> at 
> org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:634)
> at 
> org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:682)
> at 
> org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:553)
> at 
> org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:494)
> at 
> org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:171)
> at javax.servlet.GenericServlet.init(GenericServlet.java:244)
> at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:670)
> at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:427)
> at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:760)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:374)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:847)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287)
> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138)
> at 
>

[jira] [Created] (GEODE-7334) dev rest api failed to start when a JodaModel jar exists in the classpath

2019-10-22 Thread Jinmei Liao (Jira)

Jinmei Liao created GEODE-7334:
--

 Summary: dev rest api failed to start when a JodaModel jar exists 
in the classpath
 Key: GEODE-7334
 URL: https://issues.apache.org/jira/browse/GEODE-7334
 Project: Geode
  Issue Type: Bug
  Components: rest (dev)
Reporter: Jinmei Liao


Steps to reproduce

1. Add jackson-datatype-joda-2.9.8.jar  and joda-time-2.1.jar in the server 
classpath
2. start the server with rest api started
3. examine the server log shows the following exception:

[error 2019/09/13 05:43:21.681 BST rd1-server  tid=0x1] Context 
initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 
'org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter':
 Instantiation of bean failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to instantiate 
[org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter]:
 Constructor threw exception; nested exception is java.lang.ClassCastException: 
com.fasterxml.jackson.datatype.joda.JodaModule cannot be cast to 
com.fasterxml.jackson.databind.Module
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1163)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1107)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
at 
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at 
org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:668)
at 
org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:634)
at 
org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:682)
at 
org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:553)
at 
org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:494)
at 
org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:171)
at javax.servlet.GenericServlet.init(GenericServlet.java:244)
at 
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:670)
at 
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:427)
at 
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:760)
at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:374)
at 
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:847)
at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138)
at org.eclipse.jetty.server.Server.start(Server.java:416)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108)
at

[jira] [Commented] (GEODE-7332) Add OQL Aggregates link in docs

2019-10-22 Thread ASF subversion and git services (Jira)



[ 
https://issues.apache.org/jira/browse/GEODE-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957180#comment-16957180
 ] 

ASF subversion and git services commented on GEODE-7332:


Commit 4363c489aafafb1de6e07d37a8d2f2c0a4079c67 in geode's branch 
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4363c48 ]

GEODE-7332 Add link in docs to OQL aggregates subsection (#4197)



> Add OQL Aggregates link in docs
> ---
>
> Key: GEODE-7332
> URL: https://issues.apache.org/jira/browse/GEODE-7332
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Small change, but useful. File 
> developing/querying_basics/what_is_a_query_string.html has a list of useful 
> query string building blocks.  Add a link to the descriptions of the OQL 
> aggregates to the list.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-7333) Option "--classpath" missing in "start locator" documentation



 [ 
https://issues.apache.org/jira/browse/GEODE-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alberto Bustamante Reyes updated GEODE-7333:

Labels: pull-request-available  (was: )

> Option "--classpath" missing in "start locator" documentation
> -
>
> Key: GEODE-7333
> URL: https://issues.apache.org/jira/browse/GEODE-7333
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Documentation of "start locator" command ( 
> geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb ) does not 
> include the "--classpath" option.
> This option is used, for example, when [adding a custom metrics publishing 
> service|https://cwiki.apache.org/confluence/display/GEODE/Publishing+Geode+Metrics+to+External+Monitoring+Systems].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (GEODE-7333) Option "--classpath" missing in "start locator" documentation



 [ 
https://issues.apache.org/jira/browse/GEODE-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alberto Bustamante Reyes updated GEODE-7333:

Priority: Minor  (was: Major)

> Option "--classpath" missing in "start locator" documentation
> -
>
> Key: GEODE-7333
> URL: https://issues.apache.org/jira/browse/GEODE-7333
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Documentation of "start locator" command ( 
> geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb ) does not 
> include the "--classpath" option.
> This option is used, for example, when [adding a custom metrics publishing 
> service|https://cwiki.apache.org/confluence/display/GEODE/Publishing+Geode+Metrics+to+External+Monitoring+Systems].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (GEODE-7333) Option "--classpath" missing in "start locator" documentation



 [ 
https://issues.apache.org/jira/browse/GEODE-7333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alberto Bustamante Reyes reassigned GEODE-7333:
---

Assignee: Alberto Bustamante Reyes

> Option "--classpath" missing in "start locator" documentation
> -
>
> Key: GEODE-7333
> URL: https://issues.apache.org/jira/browse/GEODE-7333
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Documentation of "start locator" command ( 
> geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb ) does not 
> include the "--classpath" option.
> This option is used, for example, when [adding a custom metrics publishing 
> service|https://cwiki.apache.org/confluence/display/GEODE/Publishing+Geode+Metrics+to+External+Monitoring+Systems].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GEODE-7333) Option "--classpath" missing in "start locator" documentation