[jira] [Commented] (GEODE-8616) ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with "Pool unexpected socket timed out on client"

2020-10-18 Thread Geode Integration (Jira) 


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

Geode Integration commented on GEODE-8616:
--

Seen in [DistributedTestOpenJDK8 
#3|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/DistributedTestOpenJDK8/builds/3].

> ClientServerCacheOperationDUnitTest > 
> largeObjectPutWithReadTimeoutThrowsException fails with "Pool unexpected 
> socket timed out on client"
> --
>
> Key: GEODE-8616
> URL: https://issues.apache.org/jira/browse/GEODE-8616
> Project: Geode
>  Issue Type: Bug
>Affects Versions: 1.12.1
>Reporter: Donal Evans
>Priority: Major
>  Labels: flaky-test
>
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest > 
> largeObjectPutWithReadTimeoutThrowsException FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x000100b52040.run
>  in VM 2 running on Host c1346ab7b3e3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at 
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Pool 
> unexpected socket timed out on client connection=Pooled Connection to 
> c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not 
> connect after 1 attempts
> at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
> at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
> at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
> at 
> org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
> at 
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
> at 
> org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
> at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
> at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
> at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
> at 
> org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz
> This is a flaky failure.



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

[jira] [Commented] (GEODE-8584) Message transmission fails with IllegalStateException in socket i/o code

2020-10-18 Thread ASF GitHub Bot (Jira) 


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

ASF GitHub Bot commented on GEODE-8584:
---

Bill opened a new pull request #5638:
URL: https://github.com/apache/geode/pull/5638


   A third attempt at fixing GEODE-8584 locking granularity.
   
   This is a refinement of the [Finer-Grained Locking 
PR](https://github.com/apache/geode/pull/5632). That PR split the single lock 
into two.  With that other PR, client code in e.g. .`MsgReader` had to do all 
this ceremony:
   
   ```
   synchronized (ioFilter.getInputSyncObject()) {
 ioFilter.setInputInUse(true);
 try {
   ByteBuffer unwrappedBuffer = readAtLeast(Connection.MSG_HEADER_BYTES);
   
   // do stuff with unwrappedBuffer
   
 } finally {
ioFilter.setInputInUse(false);
 }
   }
   ```
   
   @dschneider-pivotal noticed that this followed the `AutoCloseable` pattern. 
So this PR makes good on that observation and introduces the auto-closeable 
`ByteBufferSharing`. We now return a `ByteBufferSharing` from methods that used 
to return the input `ByteBuffer`. Callers acquire it in a try-with-resources 
and rely on the `AutoCloseable` protocol to take care of lock closing and 
reference counting (decrement).
   
   With this PR that same `MsgReader` code looks like this:
   
   ```
   try (final ByteBufferSharing sharedBuffer = ioFilter
   .readAtLeast(conn.getSocket().getChannel(), Connection.MSG_HEADER_BYTES, 
peerNetData)) {
 ByteBuffer unwrappedBuffer = sharedBuffer.getBuffer();
   
 // do stuff with unwrappedBuffer
 
   }
   ```  
   
   - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?
   
   - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically `develop`)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [ ] Does `gradlew build` run cleanly?
   
   - [ ] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Note:
   Please ensure that once the PR is submitted, check Concourse for build 
issues and
   submit an update to your PR as soon as possible. If you need help, please 
send an
   email to d...@geode.apache.org.
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Message transmission fails with IllegalStateException in socket i/o code
> 
>
> Key: GEODE-8584
> URL: https://issues.apache.org/jira/browse/GEODE-8584
> Project: Geode
>  Issue Type: Bug
>  Components: membership, messaging
>Affects Versions: 1.12.0, 1.13.0, 1.14.0
>Reporter: Bruce J Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.12.1, 1.14.0, 1.13.1
>
>
> Transmission of an update operation failed with a toData exception caused by 
> an IllegalStateException in socket i/o code.  It shouldn't be possible for 
> this exception to happen unless multiple threads are using the buffer at the 
> same time.
>  
> {noformat}
> org.apache.geode.ToDataException: toData failed on dsfid=71 msg:null
>   at 
> org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1509)
>   at 
> org.apache.geode.internal.tcp.MsgStreamer.writeMessage(MsgStreamer.java:249)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:306)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:182)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:511)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionMan

[jira] [Commented] (GEODE-226) JSON seems to lose time portion on getObject

2020-10-18 Thread rickberon (Jira) 


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

rickberon commented on GEODE-226:
-

The JSON specification does not specify a format for exchanging dates which is 
why there are so many different ways to do it. The problem with dates in JSON 
and JavaScript in general – is that there's no equivalent literal 
representation for dates. In 
JavaScript/[jQuery|http://net-informations.com/jq/iq/jdate.htm] following Date 
constructor straight away converts the milliseconds since 1970 to Date as 
follows:
 
var jsonDate = new Date(1297246301973);

Then let's convert it to js format:

var date = new Date(parseInt(jsonDate.substr(6)));

The substr() function takes out the /Date( part, and the parseInt() function 
gets the integer and ignores the )/ at the end. The resulting number is passed 
into the Date constructor .

For ISO-8601 formatted JSON dates, just pass the string into the Date 
constructor:

var date = new Date(jsonDate);

 

> JSON seems to lose time portion on getObject
> 
>
> Key: GEODE-226
> URL: https://issues.apache.org/jira/browse/GEODE-226
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Konstantin Ignatyev
>Assignee: Hitesh Khamesra
>Priority: Major
>  Labels: SmallFeature
>
> com.gemstone.gemfire.pdx.internal.PdxInstanceImpl#getObject
> Date format, in the JSON land it is pretty much settled to be ISO 8661
> https://weblog.west-wind.com/posts/2014/Jan/06/JavaScript-JSON-Date-Parsing-and-real-Dates
>  
> It would  be nice to be able to have Geode’s JSON standard compliant, or have 
> this configurable. Otherwise the we will be loosing time portion of date-s
> public Object getObject() {
>   if (getPdxType().getNoDomainClass()) { 
> //In case of Developer Rest APIs, All PdxInstances converted from Json 
> will have a className =__GEMFIRE_JSON.
> //Following code added to convert Json/PdxInstance into the Java object.
> if(this.getClassName().equals("__GEMFIRE_JSON")){
>   
>   //introspect the JSON, does the @type meta-data exist.
>   String className = extractTypeMetaData();
>   
>   if(StringUtils.hasText(className)) {
> try {
>   ObjectMapper mapper = new ObjectMapper();
>   mapper.setDateFormat(new SimpleDateFormat("MM/dd/"));
>   mapper.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, 
> false);
>   
> mapper.configure(com.fasterxml.jackson.core.JsonParser.Feature.ALLOW_UNQUOTED_FIELD_NAMES,
>  true);
>   String JSON = JSONFormatter.toJSON(this);
>   Object classInstance = mapper.readValue(JSON, 
> ClassPathLoader.getLatest().forName(className));
>   return classInstance;
> }catch(Exception e){
>   throw new PdxSerializationException("Could not deserialize as java 
> class type could not resolved", e);
> }
>   }
> }
> return this;
>   }
> Also this method is not that performant, please see #225 



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

[jira] [Created] (GEODE-8627) Redis not correctly unsubscribing and punsubscribing correctly when no channel/pattern provided

2020-10-18 Thread Sarah Abbey (Jira) 
Sarah Abbey created GEODE-8627:
--

 Summary: Redis not correctly unsubscribing and punsubscribing 
correctly when no channel/pattern provided
 Key: GEODE-8627
 URL: https://issues.apache.org/jira/browse/GEODE-8627
 Project: Geode
  Issue Type: Bug
  Components: redis
Reporter: Sarah Abbey


Geode Redis should unsubscribe from all channels (not including patterns) when 
no channel is provided and punsubscribe from all patterns (not including 
channels) when no pattern is provided.



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

[jira] [Assigned] (GEODE-8627) Redis not correctly unsubscribing and punsubscribing correctly when no channel/pattern provided

2020-10-18 Thread Sarah Abbey (Jira) 


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

Sarah Abbey reassigned GEODE-8627:
--

Assignee: Sarah Abbey

> Redis not correctly unsubscribing and punsubscribing correctly when no 
> channel/pattern provided
> ---
>
> Key: GEODE-8627
> URL: https://issues.apache.org/jira/browse/GEODE-8627
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Major
>
> Geode Redis should unsubscribe from all channels (not including patterns) 
> when no channel is provided and punsubscribe from all patterns (not including 
> channels) when no pattern is provided.



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

[jira] [Updated] (GEODE-8627) Redis not unsubscribing and punsubscribing correctly when no channel/pattern provided

2020-10-18 Thread Sarah Abbey (Jira) 


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

Sarah Abbey updated GEODE-8627:
---
Summary: Redis not unsubscribing and punsubscribing correctly when no 
channel/pattern provided  (was: Redis not correctly unsubscribing and 
punsubscribing correctly when no channel/pattern provided)

> Redis not unsubscribing and punsubscribing correctly when no channel/pattern 
> provided
> -
>
> Key: GEODE-8627
> URL: https://issues.apache.org/jira/browse/GEODE-8627
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Major
>
> Geode Redis should unsubscribe from all channels (not including patterns) 
> when no channel is provided and punsubscribe from all patterns (not including 
> channels) when no pattern is provided.



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

[jira] [Commented] (GEODE-8627) Redis not unsubscribing and punsubscribing correctly when no channel/pattern provided

2020-10-18 Thread ASF GitHub Bot (Jira) 


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

ASF GitHub Bot commented on GEODE-8627:
---

sabbey37 opened a new pull request #5639:
URL: https://github.com/apache/geode/pull/5639


   Geode Redis should unsubscribe from all channels (not including patterns) 
when no channel is provided and punsubscribe from all patterns (not including 
channels) when no pattern is provided.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Redis not unsubscribing and punsubscribing correctly when no channel/pattern 
> provided
> -
>
> Key: GEODE-8627
> URL: https://issues.apache.org/jira/browse/GEODE-8627
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Major
>
> Geode Redis should unsubscribe from all channels (not including patterns) 
> when no channel is provided and punsubscribe from all patterns (not including 
> channels) when no pattern is provided.



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

[jira] [Updated] (GEODE-8627) Redis not unsubscribing and punsubscribing correctly when no channel/pattern provided

2020-10-18 Thread ASF GitHub Bot (Jira) 


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

ASF GitHub Bot updated GEODE-8627:
--
Labels: pull-request-available  (was: )

> Redis not unsubscribing and punsubscribing correctly when no channel/pattern 
> provided
> -
>
> Key: GEODE-8627
> URL: https://issues.apache.org/jira/browse/GEODE-8627
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Major
>  Labels: pull-request-available
>
> Geode Redis should unsubscribe from all channels (not including patterns) 
> when no channel is provided and punsubscribe from all patterns (not including 
> channels) when no pattern is provided.



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

[jira] [Commented] (GEODE-8627) Redis not unsubscribing and punsubscribing correctly when no channel/pattern provided

2020-10-18 Thread ASF GitHub Bot (Jira) 


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

ASF GitHub Bot commented on GEODE-8627:
---

sabbey37 commented on a change in pull request #5639:
URL: https://github.com/apache/geode/pull/5639#discussion_r507474516



##
File path: 
geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/pubsub/AbstractSubscriptionsIntegrationTest.java
##
@@ -88,18 +111,91 @@ public void multiSubscribe() {
 .untilAsserted(() -> 
assertThat(mockSubscriber.getReceivedPMessages()).hasSize(1));
 assertThat(mockSubscriber.getReceivedEvents()).containsExactly("message", 
"pmessage");
 mockSubscriber.unsubscribe();
-client.close();
   }
 
   @Test
-  public void unallowedCommandsWhileSubscribed() {
-Jedis client = new Jedis("localhost", getPort());
+  public void 
unsubscribingImplicitlyFromAllChannels_doesNotUnsubscribeFromPatterns() {

Review comment:
   It might make sense to move these test to 
`AbstractPubSubIntegrationTest.java` once 
[8577](https://issues.apache.org/jira/projects/GEODE/issues/GEODE-8577?filter=allopenissues)
 is resolved.

##
File path: 
geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/pubsub/AbstractSubscriptionsIntegrationTest.java
##
@@ -88,18 +111,91 @@ public void multiSubscribe() {
 .untilAsserted(() -> 
assertThat(mockSubscriber.getReceivedPMessages()).hasSize(1));
 assertThat(mockSubscriber.getReceivedEvents()).containsExactly("message", 
"pmessage");
 mockSubscriber.unsubscribe();
-client.close();
   }
 
   @Test
-  public void unallowedCommandsWhileSubscribed() {
-Jedis client = new Jedis("localhost", getPort());
+  public void 
unsubscribingImplicitlyFromAllChannels_doesNotUnsubscribeFromPatterns() {

Review comment:
   It might make sense to move these tests to 
`AbstractPubSubIntegrationTest.java` once 
[8577](https://issues.apache.org/jira/projects/GEODE/issues/GEODE-8577?filter=allopenissues)
 is resolved.





This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Redis not unsubscribing and punsubscribing correctly when no channel/pattern 
> provided
> -
>
> Key: GEODE-8627
> URL: https://issues.apache.org/jira/browse/GEODE-8627
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Sarah Abbey
>Assignee: Sarah Abbey
>Priority: Major
>  Labels: pull-request-available
>
> Geode Redis should unsubscribe from all channels (not including patterns) 
> when no channel is provided and punsubscribe from all patterns (not including 
> channels) when no pattern is provided.



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

[jira] [Resolved] (GEODE-8497) Get heap memory occupied by GW senders queue events

2020-10-18 Thread Mario Ivanac (Jira) 


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

Mario Ivanac resolved GEODE-8497.
-
Resolution: Fixed

> Get heap memory occupied by GW senders queue events
> ---
>
> Key: GEODE-8497
> URL: https://issues.apache.org/jira/browse/GEODE-8497
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
>
> Extract exact heap memory occupied by GW senders queue.



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

[jira] [Commented] (GEODE-8497) Get heap memory occupied by GW senders queue events

2020-10-18 Thread ASF GitHub Bot (Jira) 


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

ASF GitHub Bot commented on GEODE-8497:
---

mivanac merged pull request #5514:
URL: https://github.com/apache/geode/pull/5514


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Get heap memory occupied by GW senders queue events
> ---
>
> Key: GEODE-8497
> URL: https://issues.apache.org/jira/browse/GEODE-8497
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
>
> Extract exact heap memory occupied by GW senders queue.



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

[jira] [Commented] (GEODE-8497) Get heap memory occupied by GW senders queue events

2020-10-18 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on GEODE-8497:


Commit c362f77591fa83e5f87a056fe221d1241de87348 in geode's branch 
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c362f77 ]

GEODE-8497: added getTotalQueueSizeBytesInUse (#5514)

* GEODE-8497: added getTotalQueueSizeBytesInUse

* GEODE-8497: updated UT

* GEODE-8497: fix fail statistics after restart

> Get heap memory occupied by GW senders queue events
> ---
>
> Key: GEODE-8497
> URL: https://issues.apache.org/jira/browse/GEODE-8497
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
>
> Extract exact heap memory occupied by GW senders queue.



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

[jira] [Commented] (GEODE-8497) Get heap memory occupied by GW senders queue events

2020-10-18 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on GEODE-8497:


Commit c362f77591fa83e5f87a056fe221d1241de87348 in geode's branch 
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c362f77 ]

GEODE-8497: added getTotalQueueSizeBytesInUse (#5514)

* GEODE-8497: added getTotalQueueSizeBytesInUse

* GEODE-8497: updated UT

* GEODE-8497: fix fail statistics after restart

> Get heap memory occupied by GW senders queue events
> ---
>
> Key: GEODE-8497
> URL: https://issues.apache.org/jira/browse/GEODE-8497
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
>
> Extract exact heap memory occupied by GW senders queue.



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

[jira] [Commented] (GEODE-8497) Get heap memory occupied by GW senders queue events

2020-10-18 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on GEODE-8497:


Commit c362f77591fa83e5f87a056fe221d1241de87348 in geode's branch 
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c362f77 ]

GEODE-8497: added getTotalQueueSizeBytesInUse (#5514)

* GEODE-8497: added getTotalQueueSizeBytesInUse

* GEODE-8497: updated UT

* GEODE-8497: fix fail statistics after restart

> Get heap memory occupied by GW senders queue events
> ---
>
> Key: GEODE-8497
> URL: https://issues.apache.org/jira/browse/GEODE-8497
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
>
> Extract exact heap memory occupied by GW senders queue.



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

[jira] [Commented] (GEODE-8497) Get heap memory occupied by GW senders queue events

2020-10-18 Thread ASF subversion and git services (Jira) 


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

ASF subversion and git services commented on GEODE-8497:


Commit c362f77591fa83e5f87a056fe221d1241de87348 in geode's branch 
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c362f77 ]

GEODE-8497: added getTotalQueueSizeBytesInUse (#5514)

* GEODE-8497: added getTotalQueueSizeBytesInUse

* GEODE-8497: updated UT

* GEODE-8497: fix fail statistics after restart

> Get heap memory occupied by GW senders queue events
> ---
>
> Key: GEODE-8497
> URL: https://issues.apache.org/jira/browse/GEODE-8497
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, wan
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
>  Labels: pull-request-available
>
> Extract exact heap memory occupied by GW senders queue.



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