[jira] [Updated] (GEODE-4613) Gfsh's prints out error message after shutdown --include-locators
[ https://issues.apache.org/jira/browse/GEODE-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4613: -- Labels: pull-request-available (was: ) > Gfsh's prints out error message after shutdown --include-locators > - > > Key: GEODE-4613 > URL: https://issues.apache.org/jira/browse/GEODE-4613 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.4.0 >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > > Steps to reproduce: > gfsh>start locator --name=locator > gfsh>start server --name=server > gfsh>shutdown --include-locators > As a lot of data in memory will be lost, including possibly events in queues, > do you really want to shutdown the entire distributed system? (Y/n): y > Shutdown is triggered > Failed to restart: java.io.IOException: Failed to get a RMI stub: > javax.naming.CommunicationException [Root exception is > java.rmi.NoSuchObjectException: no such object in table] > gfsh> > No longer connected to 10.118.33.243[1099]. > Failed to call the method close():java.rmi.ConnectException: Connection > refused to host: 127.0.0.1; nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Failed to check connection: java.rmi.NoSuchObjectException: no such object in > table > stopping > Error In gfsh.log: > [severe 2018/02/06 13:53:33.931 PST JMX client heartbeat 2 tid=0x2d] > (msgTID=45 msgSN=11) No longer connected to 10.118.33.243[1099]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4635) Enable Extensibility for JSON PDX Serialization
[ https://issues.apache.org/jira/browse/GEODE-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gideon updated GEODE-4635: -- Description: Our ReflectionBasedAutoSerializer provides a way to customize serialization on a field-by-field basis. Implementing your own PDX Serializer of course provides full freedom to implement customized behavior. However, for JSON documents, there is no way currently to add custom serialization logic. The JSONFormatter class can't be extended or replaced with a different implementation. was: Our ReflectionBasedAutoSerializer provides a way to customize serialization on a field-by-field basis. Implementing your own PDX Serializer of course provides full freedom to implement customized behavior. However, for JSON documents, there is no way currently to add custom serialization logic. The JSONFormatter class can't be extended or replaced with a different implementation. > Enable Extensibility for JSON PDX Serialization > --- > > Key: GEODE-4635 > URL: https://issues.apache.org/jira/browse/GEODE-4635 > Project: Geode > Issue Type: New Feature > Components: serialization >Reporter: Gideon >Assignee: Brian Baynes >Priority: Major > > Our ReflectionBasedAutoSerializer provides a way to customize serialization > on a field-by-field basis. Implementing your own PDX Serializer of course > provides full freedom to implement customized behavior. > However, for JSON documents, there is no way currently to add custom > serialization logic. The JSONFormatter class can't be extended or replaced > with a different implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4598) Make LRUListWithAsyncSorting the default LRU list
[ https://issues.apache.org/jira/browse/GEODE-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Reich resolved GEODE-4598. --- Resolution: Fixed Fix Version/s: 1.5.0 > Make LRUListWithAsyncSorting the default LRU list > - > > Key: GEODE-4598 > URL: https://issues.apache.org/jira/browse/GEODE-4598 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Nick Reich >Assignee: Nick Reich >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1h > Remaining Estimate: 0h > > The new LRUListWithAsyncSorting should become the new default (replacing the > old algorithm) and the experimental tag should be removed from its properties. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4559) Remove singleton calls from product code in org.apache.geode.cache.util
[ https://issues.apache.org/jira/browse/GEODE-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4559: -- Labels: pull-request-available (was: ) > Remove singleton calls from product code in org.apache.geode.cache.util > --- > > Key: GEODE-4559 > URL: https://issues.apache.org/jira/browse/GEODE-4559 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > These product classes in org.apache.geode.cache.util invoke singleton getters. > GemFireCacheImpl.getInstance(): > * AutoBalancer$GeodeCacheFacade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4640) CI Failure: RemoveCommandDUnitTest can fail to find region
[
https://issues.apache.org/jira/browse/GEODE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4640:
--
Labels: pull-request-available (was: )
> CI Failure: RemoveCommandDUnitTest can fail to find region
> --
>
> Key: GEODE-4640
> URL: https://issues.apache.org/jira/browse/GEODE-4640
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
>
> The test has failed sporadically with
> {noformat}
> org.apache.geode.management.internal.cli.commands.RemoveCommandDUnitTest >
> removeAllFromPartitionedRegion FAILED
> org.junit.ComparisonFailure: [Region not found in
> any of the members
> {noformat}
> This may be to the test waiting only for one region to be ready before
> proceeding, resulting in a race condition between the testing VM and the
> server VMs.
> See
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/124
> http://files.apachegeode-ci.info/builds/1.5.0-build.409/test-results/distributedTest/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3540) unable to gfsh destroy gateway-sender
[
https://issues.apache.org/jira/browse/GEODE-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda resolved GEODE-3540.
Resolution: Fixed
Fix Version/s: 1.5.0
> unable to gfsh destroy gateway-sender
> -
>
> Key: GEODE-3540
> URL: https://issues.apache.org/jira/browse/GEODE-3540
> Project: Geode
> Issue Type: Bug
> Components: gfsh, wan
>Reporter: Raphaël Enrici
>Assignee: Sai Boorlagadda
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Dear all,
> while playing with wan setup we found that we are unable to destroy a
> declared sender configuration.
> You can reproduce this in a simple one node setup with apache geode 1.2.0:
> * start a locator
> * start a server
> * create a gateway-sender
> * destroy the gateway-sender => messages are ok
> * list gateways, the gateway-sender is still here although we just destroyed
> it
> * if you try to destroy it again, you get "ERROR: GateWaySender with Id
> sender not found"
> * if you list gateways again, the gateway is still here, you can even start
> and stop it although it is not functional anymore.
> * restarting the whole cluster does not change anything.
> Maybe we missed something concerning this, if the answer to this is a RTFM
> one, sorry for the noise.
> Keep up the good work.
> Best,
> Raphaël
> Here are shrinked outputs concerning this problem:
> {quote}
> gfsh> start locator --name=happylocator
> gfsh> start server --name=happyserver1
> gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2
>Member| Status
> |
> happyserver1 | GatewaySender "sender" created on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status | Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | GatewaySender "sender" destroyed on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status| Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Not Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | ERROR: GateWaySender with Id sender not found
> gfsh>start gateway-sender --id sender
> Member | Result | Message
> --- | -- |
> -
> 192.168.0.6(happyserver1:1689):1025 | OK | GatewaySender sender is
> started on member 192.168.0.6(happyserv..
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4640) CI Failure: RemoveCommandDUnitTest can fail to find region
[
https://issues.apache.org/jira/browse/GEODE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-4640:
---
Assignee: (was: Patrick Rhomberg)
> CI Failure: RemoveCommandDUnitTest can fail to find region
> --
>
> Key: GEODE-4640
> URL: https://issues.apache.org/jira/browse/GEODE-4640
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Priority: Major
>
> The test has failed sporadically with
> {noformat}
> org.apache.geode.management.internal.cli.commands.RemoveCommandDUnitTest >
> removeAllFromPartitionedRegion FAILED
> org.junit.ComparisonFailure: [Region not found in
> any of the members
> {noformat}
> This may be to the test waiting only for one region to be ready before
> proceeding, resulting in a race condition between the testing VM and the
> server VMs.
> See
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/124
> http://files.apachegeode-ci.info/builds/1.5.0-build.409/test-results/distributedTest/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4640) CI Failure: RemoveCommandDUnitTest can fail to find region
[
https://issues.apache.org/jira/browse/GEODE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-4640:
---
Assignee: Patrick Rhomberg
> CI Failure: RemoveCommandDUnitTest can fail to find region
> --
>
> Key: GEODE-4640
> URL: https://issues.apache.org/jira/browse/GEODE-4640
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> The test has failed sporadically with
> {noformat}
> org.apache.geode.management.internal.cli.commands.RemoveCommandDUnitTest >
> removeAllFromPartitionedRegion FAILED
> org.junit.ComparisonFailure: [Region not found in
> any of the members
> {noformat}
> This may be to the test waiting only for one region to be ready before
> proceeding, resulting in a race condition between the testing VM and the
> server VMs.
> See
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/124
> http://files.apachegeode-ci.info/builds/1.5.0-build.409/test-results/distributedTest/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3540) unable to gfsh destroy gateway-sender
[
https://issues.apache.org/jira/browse/GEODE-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357721#comment-16357721
]
ASF subversion and git services commented on GEODE-3540:
Commit bbea69a1e0c153e28f5958a58387b80f70fcdc89 in geode's branch
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bbea69a ]
GEODE-3540: unable to gfsh destroy gateway-sender (#1414)
GW sender bean is not unregistered during destroy command which
is why it appears when you list gateways after destroy. This fix is to
unregistered the MX bean from SystemManagementService
> unable to gfsh destroy gateway-sender
> -
>
> Key: GEODE-3540
> URL: https://issues.apache.org/jira/browse/GEODE-3540
> Project: Geode
> Issue Type: Bug
> Components: gfsh, wan
>Reporter: Raphaël Enrici
>Assignee: Sai Boorlagadda
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Dear all,
> while playing with wan setup we found that we are unable to destroy a
> declared sender configuration.
> You can reproduce this in a simple one node setup with apache geode 1.2.0:
> * start a locator
> * start a server
> * create a gateway-sender
> * destroy the gateway-sender => messages are ok
> * list gateways, the gateway-sender is still here although we just destroyed
> it
> * if you try to destroy it again, you get "ERROR: GateWaySender with Id
> sender not found"
> * if you list gateways again, the gateway is still here, you can even start
> and stop it although it is not functional anymore.
> * restarting the whole cluster does not change anything.
> Maybe we missed something concerning this, if the answer to this is a RTFM
> one, sorry for the noise.
> Keep up the good work.
> Best,
> Raphaël
> Here are shrinked outputs concerning this problem:
> {quote}
> gfsh> start locator --name=happylocator
> gfsh> start server --name=happyserver1
> gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2
>Member| Status
> |
> happyserver1 | GatewaySender "sender" created on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status | Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | GatewaySender "sender" destroyed on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status| Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Not Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | ERROR: GateWaySender with Id sender not found
> gfsh>start gateway-sender --id sender
> Member | Result | Message
> --- | -- |
> -
> 192.168.0.6(happyserver1:1689):1025 | OK | GatewaySender sender is
> started on member 192.168.0.6(happyserv..
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3643) Add function execution on specific member
[ https://issues.apache.org/jira/browse/GEODE-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357684#comment-16357684 ] ASF subversion and git services commented on GEODE-3643: Commit 40945432cb527511dfe03286d78fda26c4dd0187 in geode's branch refs/heads/feature/GEODE-3643 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4094543 ] GEODE-3643: Add function execution on specific member fixing a dumb test failure > Add function execution on specific member > - > > Key: GEODE-3643 > URL: https://issues.apache.org/jira/browse/GEODE-3643 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > > As a Geode developer using the new client/server protocol, I need the ability > to execute server-side functions against a specific member. > Add function execution targeting a specific member to the new protocol, > verifying users can execute functions and receive expected results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4643) Shutdown command should (optionally) wait for shutdown
Patrick Rhomberg created GEODE-4643:
---
Summary: Shutdown command should (optionally) wait for shutdown
Key: GEODE-4643
URL: https://issues.apache.org/jira/browse/GEODE-4643
Project: Geode
Issue Type: Bug
Components: gfsh, management
Reporter: Patrick Rhomberg
Shutdown of a member is asynchronous. The {{shutdown}} command will trigger
shutdown, but not guarantee it.
Beyond the obvious benefit of guaranteeing cluster state, this has also proven
problematic in the {{runAll}} task of the {{geode-examples}} repository, as
subsequent tests can begin before the previous test has finished tearing down.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-2569) Unhelpful log message
[ https://issues.apache.org/jira/browse/GEODE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dodge resolved GEODE-2569. -- Resolution: Fixed Fix Version/s: 1.5.0 > Unhelpful log message > - > > Key: GEODE-2569 > URL: https://issues.apache.org/jira/browse/GEODE-2569 > Project: Geode > Issue Type: Bug > Components: client/server, membership, messaging >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Trivial > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > I found this in a log file: > Unable to form a TCP/IP connection to null in over 31 seconds > Just prior to this the same thread logged this: > Unable to form a TCP/IP connection to 10.32.109.100(15954):48987 in over > 31 seconds > The member mentioned was being removed from the membership view in another > thread during this time and nothing malfunctioned, but it isn't useful to > print the message with "null" in it. We should supress that message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4642) PowerMock any() arguments in tests can fail intermittently
[
https://issues.apache.org/jira/browse/GEODE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4642:
--
Labels: pull-request-available (was: )
> PowerMock any() arguments in tests can fail intermittently
> --
>
> Key: GEODE-4642
> URL: https://issues.apache.org/jira/browse/GEODE-4642
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
>
> See the Travis failure of PR #1415:
> https://travis-ci.org/apache/geode/builds/339119584?utm_source=github_status_medium=notification
> {noformat}
> :geode-core:testPicked up _JAVA_OPTIONS: -Xmx1024m -Xms512m
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest >
> getRegionEntryTypeShouldReturnTheProperTypeImplementation FAILED
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Misplaced or misused argument matcher detected here:
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$7(TypeUtilsJUnitTest.java:441)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$8(TypeUtilsJUnitTest.java:444)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$9(TypeUtilsJUnitTest.java:447)
> You cannot use argument matchers outside of verification or stubbing.
> Examples of correct usage of argument matchers:
> when(mock.get(anyInt())).thenReturn(null);
> doThrow(new
> RuntimeException()).when(mock).someVoidMethod(anyObject());
> verify(mock).someMethod(contains("foo"))
> This message may appear after an NullPointerException if the last matcher
> is returning an object
> like any() but the stubbed method signature expect a primitive argument,
> in this case,
> use primitive alternatives.
> when(mock.get(any())); // bad use, will raise NPE
> when(mock.get(anyInt())); // correct usage use
> Also, this error might show up because you use argument matchers with
> methods that cannot be mocked.
> Following methods *cannot* be stubbed/verified:
> final/private/equals()/hashCode().
> Mocking methods declared on non-public parent classes is not supported.
> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.getRegionEntryTypeShouldReturnTheProperTypeImplementation(TypeUtilsJUnitTest.java:429)
> 4020 tests completed, 1 failed, 8 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4615) Deadlock shutting down client cache
[
https://issues.apache.org/jira/browse/GEODE-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4615:
--
Labels: pull-request-available (was: )
> Deadlock shutting down client cache
> ---
>
> Key: GEODE-4615
> URL: https://issues.apache.org/jira/browse/GEODE-4615
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.1.0
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A test became deadlocked when a thread executing a query was requesting a PDX
> type ID from its server at the same time another thread was closing the
> cache. I wrote a unit test to reproduce this problem. Here is the deadlock:
>
> {noformat}
> "ConnectionManagerJUnitTest thread":
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.internalDestroy(PooledConnection.java:76)
> - waiting to lock <0x00076bbc3d20> (a
> org.apache.geode.cache.client.internal.pooling.PooledConnection)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.internalClose(PooledConnection.java:101)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap.close(ConnectionManagerImpl.java:1164)
> - locked <0x00076b848f30> (a
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerJUnitTest$3.run(ConnectionManagerJUnitTest.java:613)
> "main":
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap.addConnection(ConnectionManagerImpl.java:1059)
> - waiting to lock <0x00076b848f30> (a
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.addConnection(ConnectionManagerImpl.java:463)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:245)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerJUnitTest.testThatMapCloseCausesCacheClosedException(ConnectionManagerJUnitTest.java:631)
> - locked <0x00076bbc3d20> (a
> org.apache.geode.cache.client.internal.pooling.PooledConnection)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.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.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}
> The "main" thread obtains a Connection and then, with its sync lock held,
> obtains another Connection to simulate the PDX registration.
> The background thread waits for the other thread to be ready and then closes
> the ConnectionMap.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3643) Add function execution on specific member
[ https://issues.apache.org/jira/browse/GEODE-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357631#comment-16357631 ] ASF subversion and git services commented on GEODE-3643: Commit 026c32604e932659c348a5f1078a972c98ef8ef9 in geode's branch refs/heads/feature/GEODE-3643 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=026c326 ] GEODE-3643: Add function execution on specific member fixups from review comments > Add function execution on specific member > - > > Key: GEODE-3643 > URL: https://issues.apache.org/jira/browse/GEODE-3643 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > > As a Geode developer using the new client/server protocol, I need the ability > to execute server-side functions against a specific member. > Add function execution targeting a specific member to the new protocol, > verifying users can execute functions and receive expected results. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4642) PowerMock any() arguments in tests can fail intermittently
[
https://issues.apache.org/jira/browse/GEODE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-4642:
---
Assignee: Patrick Rhomberg
> PowerMock any() arguments in tests can fail intermittently
> --
>
> Key: GEODE-4642
> URL: https://issues.apache.org/jira/browse/GEODE-4642
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> See the Travis failure of PR #1415:
> https://travis-ci.org/apache/geode/builds/339119584?utm_source=github_status_medium=notification
> {noformat}
> :geode-core:testPicked up _JAVA_OPTIONS: -Xmx1024m -Xms512m
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest >
> getRegionEntryTypeShouldReturnTheProperTypeImplementation FAILED
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Misplaced or misused argument matcher detected here:
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$7(TypeUtilsJUnitTest.java:441)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$8(TypeUtilsJUnitTest.java:444)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$9(TypeUtilsJUnitTest.java:447)
> You cannot use argument matchers outside of verification or stubbing.
> Examples of correct usage of argument matchers:
> when(mock.get(anyInt())).thenReturn(null);
> doThrow(new
> RuntimeException()).when(mock).someVoidMethod(anyObject());
> verify(mock).someMethod(contains("foo"))
> This message may appear after an NullPointerException if the last matcher
> is returning an object
> like any() but the stubbed method signature expect a primitive argument,
> in this case,
> use primitive alternatives.
> when(mock.get(any())); // bad use, will raise NPE
> when(mock.get(anyInt())); // correct usage use
> Also, this error might show up because you use argument matchers with
> methods that cannot be mocked.
> Following methods *cannot* be stubbed/verified:
> final/private/equals()/hashCode().
> Mocking methods declared on non-public parent classes is not supported.
> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.getRegionEntryTypeShouldReturnTheProperTypeImplementation(TypeUtilsJUnitTest.java:429)
> 4020 tests completed, 1 failed, 8 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4642) PowerMock any() arguments in tests can fail intermittently
Patrick Rhomberg created GEODE-4642:
---
Summary: PowerMock any() arguments in tests can fail intermittently
Key: GEODE-4642
URL: https://issues.apache.org/jira/browse/GEODE-4642
Project: Geode
Issue Type: Bug
Reporter: Patrick Rhomberg
See the Travis failure of PR #1415:
https://travis-ci.org/apache/geode/builds/339119584?utm_source=github_status_medium=notification
{noformat}
:geode-core:testPicked up _JAVA_OPTIONS: -Xmx1024m -Xms512m
org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest >
getRegionEntryTypeShouldReturnTheProperTypeImplementation FAILED
org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
Misplaced or misused argument matcher detected here:
-> at
org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$7(TypeUtilsJUnitTest.java:441)
-> at
org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$8(TypeUtilsJUnitTest.java:444)
-> at
org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$9(TypeUtilsJUnitTest.java:447)
You cannot use argument matchers outside of verification or stubbing.
Examples of correct usage of argument matchers:
when(mock.get(anyInt())).thenReturn(null);
doThrow(new RuntimeException()).when(mock).someVoidMethod(anyObject());
verify(mock).someMethod(contains("foo"))
This message may appear after an NullPointerException if the last matcher
is returning an object
like any() but the stubbed method signature expect a primitive argument, in
this case,
use primitive alternatives.
when(mock.get(any())); // bad use, will raise NPE
when(mock.get(anyInt())); // correct usage use
Also, this error might show up because you use argument matchers with
methods that cannot be mocked.
Following methods *cannot* be stubbed/verified:
final/private/equals()/hashCode().
Mocking methods declared on non-public parent classes is not supported.
at
org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.getRegionEntryTypeShouldReturnTheProperTypeImplementation(TypeUtilsJUnitTest.java:429)
4020 tests completed, 1 failed, 8 skipped
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-2569) Unhelpful log message
[ https://issues.apache.org/jira/browse/GEODE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357535#comment-16357535 ] ASF subversion and git services commented on GEODE-2569: Commit 17654b9be859c59a7d26362d4a53851d3515a3ef in geode's branch refs/heads/develop from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=17654b9 ] GEODE-2569: Avoid unhelpful log message via a null check. (#1404) - Since the default for "ack-severe-alert-threshold" is zero, there is a code path where the target member is null at the point of logging. So check for null. > Unhelpful log message > - > > Key: GEODE-2569 > URL: https://issues.apache.org/jira/browse/GEODE-2569 > Project: Geode > Issue Type: Bug > Components: client/server, membership, messaging >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Trivial > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > I found this in a log file: > Unable to form a TCP/IP connection to null in over 31 seconds > Just prior to this the same thread logged this: > Unable to form a TCP/IP connection to 10.32.109.100(15954):48987 in over > 31 seconds > The member mentioned was being removed from the membership view in another > thread during this time and nothing malfunctioned, but it isn't useful to > print the message with "null" in it. We should supress that message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4583) Remove singleton calls from product code in org.apache.geode.internal.shared
[ https://issues.apache.org/jira/browse/GEODE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-4583. - Resolution: Fixed Fix Version/s: 1.5.0 > Remove singleton calls from product code in org.apache.geode.internal.shared > > > Key: GEODE-4583 > URL: https://issues.apache.org/jira/browse/GEODE-4583 > Project: Geode > Issue Type: Sub-task > Components: core >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 20m > Remaining Estimate: 0h > > These product classes in org.apache.geode.internal.shared invoke singleton > getters. > InternalDistributedSystem.getAnyInstance(): > * NativeCallsJNAImpl > * NativeCallsJNAImpl$LinuxNativeCalls > * NativeCallsJNAImpl$POSIXNativeCalls -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4583) Remove singleton calls from product code in org.apache.geode.internal.shared
[ https://issues.apache.org/jira/browse/GEODE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357521#comment-16357521 ] ASF subversion and git services commented on GEODE-4583: Commit b1ba8fd5c94d6f97db7d80ebf7d557f8e720dbae in geode's branch refs/heads/develop from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b1ba8fd ] GEODE-4583: remove getAnyInstance calls (#1407) getAnyInstance was being used to get the old logger. Now the class declares a static log4j logger and uses it. > Remove singleton calls from product code in org.apache.geode.internal.shared > > > Key: GEODE-4583 > URL: https://issues.apache.org/jira/browse/GEODE-4583 > Project: Geode > Issue Type: Sub-task > Components: core >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > These product classes in org.apache.geode.internal.shared invoke singleton > getters. > InternalDistributedSystem.getAnyInstance(): > * NativeCallsJNAImpl > * NativeCallsJNAImpl$LinuxNativeCalls > * NativeCallsJNAImpl$POSIXNativeCalls -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4640) CI Failure: RemoveCommandDUnitTest can fail to find region
Patrick Rhomberg created GEODE-4640:
---
Summary: CI Failure: RemoveCommandDUnitTest can fail to find region
Key: GEODE-4640
URL: https://issues.apache.org/jira/browse/GEODE-4640
Project: Geode
Issue Type: Bug
Reporter: Patrick Rhomberg
The test has failed sporadically with
{noformat}
org.apache.geode.management.internal.cli.commands.RemoveCommandDUnitTest >
removeAllFromPartitionedRegion FAILED
org.junit.ComparisonFailure: [Region not found in any
of the members
{noformat}
This may be to the test waiting only for one region to be ready before
proceeding, resulting in a race condition between the testing VM and the server
VMs.
See
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/124
http://files.apachegeode-ci.info/builds/1.5.0-build.409/test-results/distributedTest/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4253) Create new geode-example about expiration
[ https://issues.apache.org/jira/browse/GEODE-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4253: -- Labels: pull-request-available (was: ) > Create new geode-example about expiration > - > > Key: GEODE-4253 > URL: https://issues.apache.org/jira/browse/GEODE-4253 > Project: Geode > Issue Type: New Feature > Components: examples >Reporter: Michael Dodge >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > > Create an example that demonstrates expiration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4428) Ensure that top-level README links to all examples
[ https://issues.apache.org/jira/browse/GEODE-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357502#comment-16357502 ] ASF subversion and git services commented on GEODE-4428: Commit 26b4f09e590b9f554340f41efd6a4fd5e1003db5 in geode-examples's branch refs/heads/develop from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=26b4f09 ] GEODE-4428: Fix links for queries and Lucene. (#47) > Ensure that top-level README links to all examples > -- > > Key: GEODE-4428 > URL: https://issues.apache.org/jira/browse/GEODE-4428 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Michael Dodge >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The top-level README is not linked to some of the examples, e.g., queries, > Lucene. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4253) Create new geode-example about expiration
[ https://issues.apache.org/jira/browse/GEODE-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357503#comment-16357503 ] ASF subversion and git services commented on GEODE-4253: Commit e28850ddd6cd6d77dfadac0719c8cab90d7900d1 in geode-examples's branch refs/heads/develop from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=e28850d ] GEODE-4253: Add an example for expiration. (#44) > Create new geode-example about expiration > - > > Key: GEODE-4253 > URL: https://issues.apache.org/jira/browse/GEODE-4253 > Project: Geode > Issue Type: New Feature > Components: examples >Reporter: Michael Dodge >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Create an example that demonstrates expiration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4507) Geode Native C++ Example (Put/get domain object using custom PdxSerializer)
[ https://issues.apache.org/jira/browse/GEODE-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357498#comment-16357498 ] ASF subversion and git services commented on GEODE-4507: Commit 28e47a8b4e041a4ad49212f486f0494c8c9c5fc3 in geode-native's branch refs/heads/develop from [~eburghardt] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=28e47a8 ] GEODE-4507: add whitespace after header. > Geode Native C++ Example (Put/get domain object using custom PdxSerializer) > --- > > Key: GEODE-4507 > URL: https://issues.apache.org/jira/browse/GEODE-4507 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ryan McMahon >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Create an example which puts/gets domain objects using a custom PdxSerializer -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4639) Remove Java PathFinder dependency
[ https://issues.apache.org/jira/browse/GEODE-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4639: -- Labels: pull-request-available (was: ) > Remove Java PathFinder dependency > - > > Key: GEODE-4639 > URL: https://issues.apache.org/jira/browse/GEODE-4639 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > > We added a dependency on Java PathFinder as part of Geode-3702 . > Unfortunately, I've been unable to get the JPF team to respond to requests to > merge fixes to JPF that are required to get JPF to really work with Geode > code - see > https://groups.google.com/forum/#!topic/java-pathfinder/Yb4JtrYLQg8. > At this point I think the best course of action is to remove JPF as a test > framework to execute on. This does not completely remove the capability to > write concurrency tests using the ConcurrentTestRunner, but tests will have > to use the less deterministic LoopRunner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4507) Geode Native C++ Example (Put/get domain object using custom PdxSerializer)
[ https://issues.apache.org/jira/browse/GEODE-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357475#comment-16357475 ] ASF subversion and git services commented on GEODE-4507: Commit d5b1876c31055d75feae549477be614f4ba6dd59 in geode-native's branch refs/heads/develop from [~eburghardt] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d5b1876 ] GEODE-4507: Add top level CMake file > Geode Native C++ Example (Put/get domain object using custom PdxSerializer) > --- > > Key: GEODE-4507 > URL: https://issues.apache.org/jira/browse/GEODE-4507 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ryan McMahon >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Create an example which puts/gets domain objects using a custom PdxSerializer -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4507) Geode Native C++ Example (Put/get domain object using custom PdxSerializer)
[ https://issues.apache.org/jira/browse/GEODE-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4507: -- Labels: pull-request-available (was: ) > Geode Native C++ Example (Put/get domain object using custom PdxSerializer) > --- > > Key: GEODE-4507 > URL: https://issues.apache.org/jira/browse/GEODE-4507 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Ryan McMahon >Priority: Major > Labels: pull-request-available > > Create an example which puts/gets domain objects using a custom PdxSerializer -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4588) Remove singleton calls from product code in org.apache.geode.internal.cache.locks
[ https://issues.apache.org/jira/browse/GEODE-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-4588. - Resolution: Fixed Fix Version/s: 1.5.0 > Remove singleton calls from product code in > org.apache.geode.internal.cache.locks > - > > Key: GEODE-4588 > URL: https://issues.apache.org/jira/browse/GEODE-4588 > Project: Geode > Issue Type: Sub-task > Components: transactions >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > These product classes in org.apache.geode.internal.cache.locks invoke > singleton getters. > InternalDistributedSystem.getAnyInstance(): > * TXLockServiceImpl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4588) Remove singleton calls from product code in org.apache.geode.internal.cache.locks
[ https://issues.apache.org/jira/browse/GEODE-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357445#comment-16357445 ] ASF subversion and git services commented on GEODE-4588: Commit f848621fe5258b87fcf04ceb4af7997359ed0330 in geode's branch refs/heads/develop from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f848621 ] GEODE-4588: remove call of getAnyInstance (#1394) Now an InternalDistributedSystem is passed in to the TXLockServiceImpl constructor. Note that this service depends on the distributed system instead of the cache. > Remove singleton calls from product code in > org.apache.geode.internal.cache.locks > - > > Key: GEODE-4588 > URL: https://issues.apache.org/jira/browse/GEODE-4588 > Project: Geode > Issue Type: Sub-task > Components: transactions >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > These product classes in org.apache.geode.internal.cache.locks invoke > singleton getters. > InternalDistributedSystem.getAnyInstance(): > * TXLockServiceImpl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4588) Remove singleton calls from product code in org.apache.geode.internal.cache.locks
[ https://issues.apache.org/jira/browse/GEODE-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4588: -- Labels: pull-request-available (was: ) > Remove singleton calls from product code in > org.apache.geode.internal.cache.locks > - > > Key: GEODE-4588 > URL: https://issues.apache.org/jira/browse/GEODE-4588 > Project: Geode > Issue Type: Sub-task > Components: transactions >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > These product classes in org.apache.geode.internal.cache.locks invoke > singleton getters. > InternalDistributedSystem.getAnyInstance(): > * TXLockServiceImpl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4629) CI Failure: DiskRegionDUnitTest.testNoFaults FAILED
[
https://issues.apache.org/jira/browse/GEODE-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357430#comment-16357430
]
ASF subversion and git services commented on GEODE-4629:
Commit 24601a6a97acc97083bfa46b2942f9c5a2f39b8a in geode's branch
refs/heads/develop from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=24601a6 ]
GEODE-4629: Ignore tests that assume non-approximate LRU (#1417)
> CI Failure: DiskRegionDUnitTest.testNoFaults FAILED
> ---
>
> Key: GEODE-4629
> URL: https://issues.apache.org/jira/browse/GEODE-4629
> Project: Geode
> Issue Type: Bug
> Components: eviction
>Reporter: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.cache30.DiskRegionDUnitTest > testNoFaults FAILED
> java.lang.AssertionError: Key 98 caused an eviction expected:<21> but
> was:<22>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.geode.cache30.DiskRegionDUnitTest.testNoFaults(DiskRegionDUnitTest.java:320)
> {noformat}
> This is possibly caused by we enabled the new LRU algorithm.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4639) Remove Java PathFinder dependency
[ https://issues.apache.org/jira/browse/GEODE-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-4639: - Description: We added a dependency on Java PathFinder as part of Geode-3702 . Unfortunately, I've been unable to get the JPF team to respond to requests to merge fixes to JPF that are required to get JPF to really work with Geode code - see https://groups.google.com/forum/#!topic/java-pathfinder/Yb4JtrYLQg8. At this point I think the best course of action is to remove JPF as a test framework to execute on. This does not completely remove the capability to write concurrency tests using the ConcurrentTestRunner, but tests will have to use the less deterministic LoopRunner. was: We added a dependency on Java PathFinder as part of Geode-3702. Unfortunately, I've been unable to get the JPF team to respond to requests to merge fixes to JPF that are required to get JPF to really work with Geode code. At this point I think the best course of action is to remove JPF as a test framework to execute on. This does not completely remove the capability to write concurrency tests using the ConcurrentTestRunner, but tests will have to use the less deterministic LoopRunner. > Remove Java PathFinder dependency > - > > Key: GEODE-4639 > URL: https://issues.apache.org/jira/browse/GEODE-4639 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.5.0 > > > We added a dependency on Java PathFinder as part of Geode-3702 . > Unfortunately, I've been unable to get the JPF team to respond to requests to > merge fixes to JPF that are required to get JPF to really work with Geode > code - see > https://groups.google.com/forum/#!topic/java-pathfinder/Yb4JtrYLQg8. > At this point I think the best course of action is to remove JPF as a test > framework to execute on. This does not completely remove the capability to > write concurrency tests using the ConcurrentTestRunner, but tests will have > to use the less deterministic LoopRunner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4639) Remove Java PathFinder dependency
Dan Smith created GEODE-4639: Summary: Remove Java PathFinder dependency Key: GEODE-4639 URL: https://issues.apache.org/jira/browse/GEODE-4639 Project: Geode Issue Type: Bug Components: tests Reporter: Dan Smith Fix For: 1.5.0 We added a dependency on Java PathFinder as part of Geode-3702. Unfortunately, I've been unable to get the JPF team to respond to requests to merge fixes to JPF that are required to get JPF to really work with Geode code. At this point I think the best course of action is to remove JPF as a test framework to execute on. This does not completely remove the capability to write concurrency tests using the ConcurrentTestRunner, but tests will have to use the less deterministic LoopRunner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4639) Remove Java PathFinder dependency
[ https://issues.apache.org/jira/browse/GEODE-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-4639: Assignee: Dan Smith > Remove Java PathFinder dependency > - > > Key: GEODE-4639 > URL: https://issues.apache.org/jira/browse/GEODE-4639 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.5.0 > > > We added a dependency on Java PathFinder as part of Geode-3702. > Unfortunately, I've been unable to get the JPF team to respond to requests to > merge fixes to JPF that are required to get JPF to really work with Geode > code. > At this point I think the best course of action is to remove JPF as a test > framework to execute on. This does not completely remove the capability to > write concurrency tests using the ConcurrentTestRunner, but tests will have > to use the less deterministic LoopRunner. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4629) CI Failure: DiskRegionDUnitTest.testNoFaults FAILED
[
https://issues.apache.org/jira/browse/GEODE-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4629:
--
Labels: pull-request-available (was: )
> CI Failure: DiskRegionDUnitTest.testNoFaults FAILED
> ---
>
> Key: GEODE-4629
> URL: https://issues.apache.org/jira/browse/GEODE-4629
> Project: Geode
> Issue Type: Bug
> Components: eviction
>Reporter: Eric Shu
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.cache30.DiskRegionDUnitTest > testNoFaults FAILED
> java.lang.AssertionError: Key 98 caused an eviction expected:<21> but
> was:<22>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at
> org.apache.geode.cache30.DiskRegionDUnitTest.testNoFaults(DiskRegionDUnitTest.java:320)
> {noformat}
> This is possibly caused by we enabled the new LRU algorithm.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4637) Geode Native uses GEODE rather than GEODE_HOME
Addison created GEODE-4637: -- Summary: Geode Native uses GEODE rather than GEODE_HOME Key: GEODE-4637 URL: https://issues.apache.org/jira/browse/GEODE-4637 Project: Geode Issue Type: Improvement Components: native client Reporter: Addison The java side of things uses GEODE_HOME to point to the Geode install directory containing the /bin. https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle Geode Native uses the env variable GEODE. https://github.com/apache/geode-native/blob/develop/BUILDING.md This is confusing. It would be best if we standardize on GEODE_HOME. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4638) review protobuf server error responses and logging for region-not-found
Bruce Schuchardt created GEODE-4638: --- Summary: review protobuf server error responses and logging for region-not-found Key: GEODE-4638 URL: https://issues.apache.org/jira/browse/GEODE-4638 Project: Geode Issue Type: Task Components: client/server Reporter: Bruce Schuchardt Some operation handlers log region-not-found problems at error level and some at warning level. Some return a SERVER_ERROR error code and some return an INVALID_REQUEST error code. These should probably all behave in the same way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4636) Spotless should not adjust block comments
[ https://issues.apache.org/jira/browse/GEODE-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4636: -- Labels: pull-request-available (was: ) > Spotless should not adjust block comments > - > > Key: GEODE-4636 > URL: https://issues.apache.org/jira/browse/GEODE-4636 > Project: Geode > Issue Type: Improvement >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4636) Spotless should not adjust block comments
Patrick Rhomberg created GEODE-4636: --- Summary: Spotless should not adjust block comments Key: GEODE-4636 URL: https://issues.apache.org/jira/browse/GEODE-4636 Project: Geode Issue Type: Improvement Reporter: Patrick Rhomberg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4320) AbstractConfig reproduces option redaction code
[
https://issues.apache.org/jira/browse/GEODE-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357362#comment-16357362
]
ASF subversion and git services commented on GEODE-4320:
Commit a39394e082029c0c2bfdd24bc77da8d2dc1afdf1 in geode's branch
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a39394e ]
GEODE-4320: Reconcile disparity between Banner and AbstractConfig
> AbstractConfig reproduces option redaction code
> ---
>
> Key: GEODE-4320
> URL: https://issues.apache.org/jira/browse/GEODE-4320
> Project: Geode
> Issue Type: Bug
> Components: logging, security
>Reporter: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> {{AbstractConfig}} handles its redaction differently than the
> {{ArgumentRedactor}}. This logic should be consolidated to reduce code
> duplication.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals
[ https://issues.apache.org/jira/browse/GEODE-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-4624: --- Component/s: docs > Add a new stat for AyncEventQueue/GatewaySender to track the processing of > queueRemovals > > > Key: GEODE-4624 > URL: https://issues.apache.org/jira/browse/GEODE-4624 > Project: Geode > Issue Type: Bug > Components: docs, wan >Affects Versions: 1.5.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > We currently track the number of events queues, queue size and > eventsDistributed ... but we don't track the number of events removed via > queue removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4435) DiskStoreImpl.FlusherThread.run() should increment queue size stat after writing to disk
[ https://issues.apache.org/jira/browse/GEODE-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lynn Gallinat resolved GEODE-4435. -- Resolution: Fixed > DiskStoreImpl.FlusherThread.run() should increment queue size stat after > writing to disk > > > Key: GEODE-4435 > URL: https://issues.apache.org/jira/browse/GEODE-4435 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Lynn Gallinat >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > com.gemstone.gemfire.internal.cache.DiskStoreImpl.FlusherThread.run() > should move this call: > stats.incQueueSize(-drainCount); > to the end of the while loop that drains the queue. It currently calls it at > the beginning before it actually writes to async ops to disk. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4628) Gfsh connect command should infer the value of use-ssl based on the url protocol
[ https://issues.apache.org/jira/browse/GEODE-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-4628: --- Component/s: docs > Gfsh connect command should infer the value of use-ssl based on the url > protocol > > > Key: GEODE-4628 > URL: https://issues.apache.org/jira/browse/GEODE-4628 > Project: Geode > Issue Type: Improvement > Components: docs, gfsh >Reporter: Jinmei Liao >Priority: Major > > when connecting to http service, the url (https or http) should have already > indicated whether it's use-ssl or not, in this case, we should infer the > value of use-ssl based on the protocol of the url. > Note: this is only for --use-http case. the --use-ssl should still need to be > specified for jmx connection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4633) un-deprecate peer-auth-init
[ https://issues.apache.org/jira/browse/GEODE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-4633: --- Component/s: docs > un-deprecate peer-auth-init > --- > > Key: GEODE-4633 > URL: https://issues.apache.org/jira/browse/GEODE-4633 > Project: Geode > Issue Type: Task > Components: docs, security >Reporter: Jinmei Liao >Priority: Major > > `peer-auth-init` is currently deprecated but allows the user to supply a > class that generates credentials for peer authentication (instead of reading > from cmd line or properties). This might be useful for integration with a > key management system like CredHub, and allow user not to save password in a > plain text format on file. > please make sure this property still works as expected. and un-deprecate it > in the docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4435) DiskStoreImpl.FlusherThread.run() should increment queue size stat after writing to disk
[ https://issues.apache.org/jira/browse/GEODE-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357339#comment-16357339 ] ASF subversion and git services commented on GEODE-4435: Commit ff215d4c8cb55f071f70553f4410df446aaec6d8 in geode's branch refs/heads/develop from lgallinat [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ff215d4 ] GEODE-4435 Move queueSize stat increment to after writing to disk. (#1397) * GEODE-4435 Move queueSize stat increment to after writing to disk. * Changes for review comments. > DiskStoreImpl.FlusherThread.run() should increment queue size stat after > writing to disk > > > Key: GEODE-4435 > URL: https://issues.apache.org/jira/browse/GEODE-4435 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Lynn Gallinat >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > com.gemstone.gemfire.internal.cache.DiskStoreImpl.FlusherThread.run() > should move this call: > stats.incQueueSize(-drainCount); > to the end of the while loop that drains the queue. It currently calls it at > the beginning before it actually writes to async ops to disk. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4435) DiskStoreImpl.FlusherThread.run() should increment queue size stat after writing to disk
[ https://issues.apache.org/jira/browse/GEODE-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357338#comment-16357338 ] ASF subversion and git services commented on GEODE-4435: Commit ff215d4c8cb55f071f70553f4410df446aaec6d8 in geode's branch refs/heads/develop from lgallinat [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ff215d4 ] GEODE-4435 Move queueSize stat increment to after writing to disk. (#1397) * GEODE-4435 Move queueSize stat increment to after writing to disk. * Changes for review comments. > DiskStoreImpl.FlusherThread.run() should increment queue size stat after > writing to disk > > > Key: GEODE-4435 > URL: https://issues.apache.org/jira/browse/GEODE-4435 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Lynn Gallinat >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > com.gemstone.gemfire.internal.cache.DiskStoreImpl.FlusherThread.run() > should move this call: > stats.incQueueSize(-drainCount); > to the end of the while loop that drains the queue. It currently calls it at > the beginning before it actually writes to async ops to disk. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3540) unable to gfsh destroy gateway-sender
[
https://issues.apache.org/jira/browse/GEODE-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-3540:
--
Labels: pull-request-available (was: )
> unable to gfsh destroy gateway-sender
> -
>
> Key: GEODE-3540
> URL: https://issues.apache.org/jira/browse/GEODE-3540
> Project: Geode
> Issue Type: Bug
> Components: gfsh, wan
>Reporter: Raphaël Enrici
>Assignee: Sai Boorlagadda
>Priority: Major
> Labels: pull-request-available
>
> Dear all,
> while playing with wan setup we found that we are unable to destroy a
> declared sender configuration.
> You can reproduce this in a simple one node setup with apache geode 1.2.0:
> * start a locator
> * start a server
> * create a gateway-sender
> * destroy the gateway-sender => messages are ok
> * list gateways, the gateway-sender is still here although we just destroyed
> it
> * if you try to destroy it again, you get "ERROR: GateWaySender with Id
> sender not found"
> * if you list gateways again, the gateway is still here, you can even start
> and stop it although it is not functional anymore.
> * restarting the whole cluster does not change anything.
> Maybe we missed something concerning this, if the answer to this is a RTFM
> one, sorry for the noise.
> Keep up the good work.
> Best,
> Raphaël
> Here are shrinked outputs concerning this problem:
> {quote}
> gfsh> start locator --name=happylocator
> gfsh> start server --name=happyserver1
> gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2
>Member| Status
> |
> happyserver1 | GatewaySender "sender" created on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status | Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | GatewaySender "sender" destroyed on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status| Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Not Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | ERROR: GateWaySender with Id sender not found
> gfsh>start gateway-sender --id sender
> Member | Result | Message
> --- | -- |
> -
> 192.168.0.6(happyserver1:1689):1025 | OK | GatewaySender sender is
> started on member 192.168.0.6(happyserv..
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4607) Get rid of Request and Response; renumber Protobuf fields
[ https://issues.apache.org/jira/browse/GEODE-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357280#comment-16357280 ] ASF subversion and git services commented on GEODE-4607: Commit fe3122782d947ed5db12e1c076de03f4d3ec2b9f in geode's branch refs/heads/develop from [~WireBaron] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fe31227 ] GEODE-4607: Remove protobuf Request and Response objects, renumber message types (#1389) > Get rid of Request and Response; renumber Protobuf fields > - > > Key: GEODE-4607 > URL: https://issues.apache.org/jira/browse/GEODE-4607 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Brian Rowe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Get in a few breaking changes to improve the protobuf protocol before we > remove the experimental tag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4621) CI Failure: OplogJUnitTest.testEntryAlreadyWrittenIsCorrectlyUnmarkedForOverflowOnly
[ https://issues.apache.org/jira/browse/GEODE-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Reich resolved GEODE-4621. --- Resolution: Fixed Fix Version/s: 1.5.0 > CI Failure: > OplogJUnitTest.testEntryAlreadyWrittenIsCorrectlyUnmarkedForOverflowOnly > > > Key: GEODE-4621 > URL: https://issues.apache.org/jira/browse/GEODE-4621 > Project: Geode > Issue Type: Bug > Components: eviction, persistence >Affects Versions: 1.5.0 >Reporter: Nick Reich >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > This test is intermittently failing due to an NPE. This test began to fail > with commit 69443dadad91c1fba548c5562267938bfbe53f6a (GEODE-4598). GEODE-4598 > turned on by default a new eviction algorithm which would now be used in all > tests that utilize eviction but do not manually set the system property to > choose an algorithm (such as this test). It needs to be determined why the > new algorithm causes this failure and to fix the issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4573) Query execution within a transaction (JTA) produces a ClassCastException in version 1.4.0
[
https://issues.apache.org/jira/browse/GEODE-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-4573.
-
Resolution: Fixed
Fix Version/s: 1.5.0
> Query execution within a transaction (JTA) produces a ClassCastException in
> version 1.4.0
> -
>
> Key: GEODE-4573
> URL: https://issues.apache.org/jira/browse/GEODE-4573
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.4.0
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The stack trace is like that:
> {code:java}
> Caused by: java.lang.ClassCastException:
> org.apache.geode.internal.cache.TXEntry cannot be cast to
> org.apache.geode.internal.cache.LocalRegion$NonTXEntry
> at
> org.apache.geode.internal.cache.EntriesSet$EntriesIterator.moveNext(EntriesSet.java:179)
> at
> org.apache.geode.internal.cache.EntriesSet$EntriesIterator.(EntriesSet.java:118)
> at org.apache.geode.internal.cache.EntriesSet.iterator(EntriesSet.java:83)
> at
> org.apache.geode.cache.query.internal.ResultsCollectionWrapper.iterator(ResultsCollectionWrapper.java:184)
> at org.apache.geode.cache.query.internal.QRegion.iterator(QRegion.java:244)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.doNestedIterations(CompiledSelect.java:834)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.doIterationEvaluate(CompiledSelect.java:701)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:545)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:55)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:557)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:384)
> {code}
> When property {{-Dgemfire.restoreSetOperationTransactionBehavior=true}} is
> set than everything works without errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4631) Travis builds failing due to issue in TypeUtilsJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaojian zhou resolved GEODE-4631.
--
Resolution: Fixed
Fix Version/s: 1.5.0
> Travis builds failing due to issue in TypeUtilsJUnitTest
>
>
> Key: GEODE-4631
> URL: https://issues.apache.org/jira/browse/GEODE-4631
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Nick Reich
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
>
> Seeing the follow failure in travis builds from github:
> {noformat}
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest >
> getRegionEntryTypeShouldReturnTheProperTypeImplementation FAILED
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Misplaced or misused argument matcher detected here:
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$7(TypeUtilsJUnitTest.java:441)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$8(TypeUtilsJUnitTest.java:444)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$9(TypeUtilsJUnitTest.java:447)
> You cannot use argument matchers outside of verification or stubbing.
> Examples of correct usage of argument matchers:
> when(mock.get(anyInt())).thenReturn(null);
> doThrow(new
> RuntimeException()).when(mock).someVoidMethod(anyObject());
> verify(mock).someMethod(contains("foo"))
> This message may appear after an NullPointerException if the last matcher
> is returning an object
> like any() but the stubbed method signature expect a primitive argument,
> in this case,
> use primitive alternatives.
> when(mock.get(any())); // bad use, will raise NPE
> when(mock.get(anyInt())); // correct usage use
> Also, this error might show up because you use argument matchers with
> methods that cannot be mocked.
> Following methods *cannot* be stubbed/verified:
> final/private/equals()/hashCode().
> Mocking methods declared on non-public parent classes is not supported.
> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.getRegionEntryTypeShouldReturnTheProperTypeImplementation(TypeUtilsJUnitTest.java:429){noformat}
> The issue does not reproduce locally however.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4631) Travis builds failing due to issue in TypeUtilsJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357227#comment-16357227
]
ASF subversion and git services commented on GEODE-4631:
Commit cd92f9a3d378f30eb7e93cbaa05be139bbbcefc6 in geode's branch
refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cd92f9a ]
GEODE-4631: need a public class to mock (#1413)
> Travis builds failing due to issue in TypeUtilsJUnitTest
>
>
> Key: GEODE-4631
> URL: https://issues.apache.org/jira/browse/GEODE-4631
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Nick Reich
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
>
> Seeing the follow failure in travis builds from github:
> {noformat}
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest >
> getRegionEntryTypeShouldReturnTheProperTypeImplementation FAILED
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Misplaced or misused argument matcher detected here:
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$7(TypeUtilsJUnitTest.java:441)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$8(TypeUtilsJUnitTest.java:444)
> -> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.lambda$booleanCompareShouldThrowExceptionIfValuesAreNotInstancesOfBoolean$9(TypeUtilsJUnitTest.java:447)
> You cannot use argument matchers outside of verification or stubbing.
> Examples of correct usage of argument matchers:
> when(mock.get(anyInt())).thenReturn(null);
> doThrow(new
> RuntimeException()).when(mock).someVoidMethod(anyObject());
> verify(mock).someMethod(contains("foo"))
> This message may appear after an NullPointerException if the last matcher
> is returning an object
> like any() but the stubbed method signature expect a primitive argument,
> in this case,
> use primitive alternatives.
> when(mock.get(any())); // bad use, will raise NPE
> when(mock.get(anyInt())); // correct usage use
> Also, this error might show up because you use argument matchers with
> methods that cannot be mocked.
> Following methods *cannot* be stubbed/verified:
> final/private/equals()/hashCode().
> Mocking methods declared on non-public parent classes is not supported.
> at
> org.apache.geode.cache.query.internal.types.TypeUtilsJUnitTest.getRegionEntryTypeShouldReturnTheProperTypeImplementation(TypeUtilsJUnitTest.java:429){noformat}
> The issue does not reproduce locally however.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4635) Enable Extensibility for JSON PDX Serialization
[ https://issues.apache.org/jira/browse/GEODE-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes reassigned GEODE-4635: --- Assignee: Brian Baynes > Enable Extensibility for JSON PDX Serialization > --- > > Key: GEODE-4635 > URL: https://issues.apache.org/jira/browse/GEODE-4635 > Project: Geode > Issue Type: New Feature > Components: serialization >Reporter: Gideon >Assignee: Brian Baynes >Priority: Major > > Our ReflectionBasedAutoSerializer provides a way to customize serialization > on a field-by-field basis. Implementing your own PDX Serializer of course > provides full freedom to implement customized behavior. > However, for JSON documents, there is no way currently to add custom > serialization logic. The JSONFormatter class can't be extended or replaced > with a different implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4627) Protobuf server operation handlers do not check for low-memory conditions
[
https://issues.apache.org/jira/browse/GEODE-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Baynes reassigned GEODE-4627:
---
Assignee: Brian Baynes
> Protobuf server operation handlers do not check for low-memory conditions
> -
>
> Key: GEODE-4627
> URL: https://issues.apache.org/jira/browse/GEODE-4627
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Brian Baynes
>Priority: Major
>
> The new Protobuf-based client/server operation handlers are not checking to
> see if memory is low. For instance, the Java client does this check in
> handling function execution requests:
> {code}
> HeapMemoryMonitor hmm =
> ((InternalResourceManager)
> cache.getResourceManager()).getHeapMonitor();
> if (functionObject.optimizeForWrite() && cache != null &&
> hmm.getState().isCritical()
> && !MemoryThresholds.isLowMemoryExceptionDisabled()) {
> Set sm =
> Collections.singleton((DistributedMember) cache.getMyId());
> Exception e = new LowMemoryException(
>
> LocalizedStrings.ResourceManager_LOW_MEMORY_FOR_0_FUNCEXEC_MEMBERS_1
> .toLocalizedString(new Object[] {functionObject.getId(),
> sm}),
> sm);
> sendException(hasResult, clientMessage, e.getMessage(),
> serverConnection, e);
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4615) Deadlock shutting down client cache
[
https://issues.apache.org/jira/browse/GEODE-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-4615:
Labels: (was: pull-request-available)
> Deadlock shutting down client cache
> ---
>
> Key: GEODE-4615
> URL: https://issues.apache.org/jira/browse/GEODE-4615
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.1.0
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A test became deadlocked when a thread executing a query was requesting a PDX
> type ID from its server at the same time another thread was closing the
> cache. I wrote a unit test to reproduce this problem. Here is the deadlock:
>
> {noformat}
> "ConnectionManagerJUnitTest thread":
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.internalDestroy(PooledConnection.java:76)
> - waiting to lock <0x00076bbc3d20> (a
> org.apache.geode.cache.client.internal.pooling.PooledConnection)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.internalClose(PooledConnection.java:101)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap.close(ConnectionManagerImpl.java:1164)
> - locked <0x00076b848f30> (a
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerJUnitTest$3.run(ConnectionManagerJUnitTest.java:613)
> "main":
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap.addConnection(ConnectionManagerImpl.java:1059)
> - waiting to lock <0x00076b848f30> (a
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl$ConnectionMap)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.addConnection(ConnectionManagerImpl.java:463)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:245)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerJUnitTest.testThatMapCloseCausesCacheClosedException(ConnectionManagerJUnitTest.java:631)
> - locked <0x00076bbc3d20> (a
> org.apache.geode.cache.client.internal.pooling.PooledConnection)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.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.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> {noformat}
> The "main" thread obtains a Connection and then, with its sync lock held,
> obtains another Connection to simulate the PDX registration.
> The background thread waits for the other thread to be ready and then closes
> the ConnectionMap.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4635) Enable Extensibility for JSON PDX Serialization
[ https://issues.apache.org/jira/browse/GEODE-4635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gideon updated GEODE-4635: -- Summary: Enable Extensibility for JSON PDX Serialization (was: Enable Pluggable Logic for JSON PDX Serialization) > Enable Extensibility for JSON PDX Serialization > --- > > Key: GEODE-4635 > URL: https://issues.apache.org/jira/browse/GEODE-4635 > Project: Geode > Issue Type: New Feature > Components: serialization >Reporter: Gideon >Priority: Major > > Our ReflectionBasedAutoSerializer provides a way to customize serialization > on a field-by-field basis. Implementing your own PDX Serializer of course > provides full freedom to implement customized behavior. > However, for JSON documents, there is no way currently to add custom > serialization logic. The JSONFormatter class can't be extended or replaced > with a different implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4635) Enable Pluggable Logic for JSON PDX Serialization
Gideon created GEODE-4635: - Summary: Enable Pluggable Logic for JSON PDX Serialization Key: GEODE-4635 URL: https://issues.apache.org/jira/browse/GEODE-4635 Project: Geode Issue Type: New Feature Components: serialization Reporter: Gideon Our ReflectionBasedAutoSerializer provides a way to customize serialization on a field-by-field basis. Implementing your own PDX Serializer of course provides full freedom to implement customized behavior. However, for JSON documents, there is no way currently to add custom serialization logic. The JSONFormatter class can't be extended or replaced with a different implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4632) Remove CacheableString from UserFunctionExecutionException
[ https://issues.apache.org/jira/browse/GEODE-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357141#comment-16357141 ] ASF subversion and git services commented on GEODE-4632: Commit 7edebdf0f613934e9c3e5c159576db98131ec468 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=7edebdf ] GEODE-4632: Fixes compile error on .NET. > Remove CacheableString from UserFunctionExecutionException > -- > > Key: GEODE-4632 > URL: https://issues.apache.org/jira/browse/GEODE-4632 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > UserFunctionExecutionException uses CacheableString to store the string > message from a user exception in function execution. We can store this is > std::string and simplify the interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4634) CI Failure: OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion
Eric Shu created GEODE-4634:
---
Summary: CI Failure:
OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion
Key: GEODE-4634
URL: https://issues.apache.org/jira/browse/GEODE-4634
Project: Geode
Issue Type: Bug
Components: eviction
Reporter: Eric Shu
{noformat}
org.apache.geode.internal.cache.OplogJUnitTest >
testHelperAPIsForOverflowOnlyRegion FAILED
java.lang.AssertionError: expected null, but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at
org.apache.geode.internal.cache.OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion(OplogJUnitTest.java:1240)
{noformat}
Possibly this has the same cause as GEODE-4621
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4633) un-deprecate peer-auth-init
Jinmei Liao created GEODE-4633: -- Summary: un-deprecate peer-auth-init Key: GEODE-4633 URL: https://issues.apache.org/jira/browse/GEODE-4633 Project: Geode Issue Type: Task Components: security Reporter: Jinmei Liao `peer-auth-init` is currently deprecated but allows the user to supply a class that generates credentials for peer authentication (instead of reading from cmd line or properties). This might be useful for integration with a key management system like CredHub, and allow user not to save password in a plain text format on file. please make sure this property still works as expected. and un-deprecate it in the docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4632) Remove CacheableString from UserFunctionExecutionException
[ https://issues.apache.org/jira/browse/GEODE-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357071#comment-16357071 ] ASF subversion and git services commented on GEODE-4632: Commit 5933abccf2b34fd73369af9ece498f2fdaf34ad4 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5933abc ] GEODE-4632: Replace CacheableString with std::string. (#215) > Remove CacheableString from UserFunctionExecutionException > -- > > Key: GEODE-4632 > URL: https://issues.apache.org/jira/browse/GEODE-4632 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > UserFunctionExecutionException uses CacheableString to store the string > message from a user exception in function execution. We can store this is > std::string and simplify the interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4425) Refactor Properties to use std::unordered map.
[ https://issues.apache.org/jira/browse/GEODE-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357052#comment-16357052 ] ASF subversion and git services commented on GEODE-4425: Commit 647ad26d38237f0ffa3360c89d76aa1da3579cac in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=647ad26 ] GEODE-4425: Replaces ACE map with std::unordered_map. (#214) > Refactor Properties to use std::unordered map. > -- > > Key: GEODE-4425 > URL: https://issues.apache.org/jira/browse/GEODE-4425 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > This will allow us to get further away from ACE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4619) Geode Native build fails on ClientHandShake
[
https://issues.apache.org/jira/browse/GEODE-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356910#comment-16356910
]
ASF subversion and git services commented on GEODE-4619:
Commit afb54f2a18681fc4070115d768ef2a49baa20e07 in geode-native's branch
refs/heads/develop from [~eburghardt]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=afb54f2 ]
GEODE-4619: removing strip components
> Geode Native build fails on ClientHandShake
> ---
>
> Key: GEODE-4619
> URL: https://issues.apache.org/jira/browse/GEODE-4619
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Addison
>Priority: Major
>
> {code}
> import org.apache.geode.internal.cache.tier.ClientHandShake;
>^
> symbol: class ClientHandShake
> location: package org.apache.geode.internal.cache.tier
> 1 error
> tests/javaobject/CMakeFiles/javaobject.dir/build.make:170: recipe for target
> 'tests/javaobject/CMakeFiles/javaobject.dir/java_compiled_javaobject' failed
> make[2]: ***
> [tests/javaobject/CMakeFiles/javaobject.dir/java_compiled_javaobject] Error 1
> make[2]: Leaving directory
> CMakeFiles/Makefile2:10506: recipe for target
> 'tests/javaobject/CMakeFiles/javaobject.dir/all' failed
> make[1]: *** [tests/javaobject/CMakeFiles/javaobject.dir/all] Error 2
> make[1]: Leaving directory'
> Makefile:151: recipe for target 'all' failed
> make: *** [all] Error 2
> {code}
> Most likely related to this change: GEODE-4439 refactor
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-3292) Embedded PULSE Connection Failure When jmx-manager-bind-address != localhost
[
https://issues.apache.org/jira/browse/GEODE-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella closed GEODE-3292.
---
> Embedded PULSE Connection Failure When jmx-manager-bind-address != localhost
>
>
> Key: GEODE-3292
> URL: https://issues.apache.org/jira/browse/GEODE-3292
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Minor
> Fix For: 1.3.0
>
>
> The PULSE webApp (embedded mode) fails to connect to the jmx-manager when a
> non-default {{jmx-manager-bind-address}} is configured. The app tries to
> connect by default to
> {{service:jmx:rmi://localhost/jndi/rmi://localhost:17991/jmxrmi}} whenever it
> detects it's running in embedded mode, instead of getting the local hostname
> through {{InetAddress.getLocalHost().getCanonicalHostName()}} as it used to
> do before.
> The problem was introduced by
> [GEODE-2927|https://issues.apache.org/jira/browse/GEODE-2927], commit
> [0f978a6df711d04e0c7c1926fb1e297d07c21aa3|https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0f978a6].
> Steps to reproduce:
> {code:none}
> $ export JAVA_ARGS="-Dgfsh.log-level=config -Dgfsh.log-dir=$(pwd)"
> $ gfsh start locator --name=locator1 --force=true --connect=false \
> --J=-Dpulse.Log-Level=debug --J=-Dpulse.Log-File-Name=pulse.log
> --J=-Dpulse.Log-FileLocation=$(pwd) \
> --J=-Dgemfire.jmx-manager=true --J=-Dgemfire.jmx-manager-start=true
> --J=-Dgemfire.jmx-manager-port=17991 \
> --J=-Dgemfire.jmx-manager-bind-address=$(ipconfig getifaddr en0)
> $ gfsh start pulse
> {code}
> At this point, and after a successful login to PULSE, the application doesn't
> show any cluster data and the exception can be seen (both in the logs and in
> the PULSE screen).
> The easiest solution would be to revert back some lines of the changes made
> by commit
> [0f978a6df711d04e0c7c1926fb1e297d07c21aa3|https://git-wip-us.apache.org/repos/asf?p=geode.git;h=0f978a6],
> as follows:
> {code:title=PulseAppListener.java|borderStyle=solid}
> @Override
> public void contextInitialized(ServletContextEvent event) {
> (...)
> boolean sysIsEmbedded =
> Boolean.getBoolean(PulseConstants.SYSTEM_PROPERTY_PULSE_EMBEDDED);
> if (sysIsEmbedded) {
> // jmx connection parameters
>
> logger.info(resourceBundle.getString("LOG_MSG_APP_RUNNING_EMBEDDED_MODE"));
> repository.setJmxUseLocator(false);
>
> //
> String sysPulseHost;
> try {
> // Get host name of machine running pulse in embedded mode
> sysPulseHost = InetAddress.getLocalHost().getCanonicalHostName();
> } catch (Exception e) {
>
> logger.debug(resourceBundle.getString("LOG_MSG_JMX_CONNECTION_UNKNOWN_HOST"),
> e);
> // Set default host name
> sysPulseHost = PulseConstants.GEMFIRE_DEFAULT_HOST;
> }
> repository.setHost(sysPulseHost);
>
> //
>
> repository.setPort(System.getProperty(PulseConstants.SYSTEM_PROPERTY_PULSE_PORT,
> PulseConstants.GEMFIRE_DEFAULT_PORT));
> // SSL, all the other system properties are already set in the embedded
> VM
> repository.setUseSSLManager(
>
> Boolean.valueOf(System.getProperty(PulseConstants.SYSTEM_PROPERTY_PULSE_USESSL_MANAGER)));
> repository.setUseSSLLocator(
>
> Boolean.valueOf(System.getProperty(PulseConstants.SYSTEM_PROPERTY_PULSE_USESSL_LOCATOR)));
> (...)
> }
> {code}
> I can make the changes and submit a PR if someone assigns me this ticket.
> Cheers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-1758) Refactor, test and clean up for TypeUtils
[ https://issues.apache.org/jira/browse/GEODE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan José Ramos Cassella resolved GEODE-1758. - Resolution: Fixed Fix Version/s: 1.5.0 Changes have been merged into develop branch. [CommitID|https://github.com/apache/geode/commit/952db5f1c46a293fe3d5bf01894a5be50effce1d]: 952db5f1c46a293fe3d5bf01894a5be50effce1d. > Refactor, test and clean up for TypeUtils > - > > Key: GEODE-1758 > URL: https://issues.apache.org/jira/browse/GEODE-1758 > Project: Geode > Issue Type: Improvement > Components: querying >Reporter: Jason Huynh >Assignee: Juan José Ramos Cassella >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > There are a few unused public static methods in this class that can probably > be cleaned up. > The compare() method can either be refactored or broken down into different > method calls > This class also needs more thorough unit tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4437) Delete unused methods and refactor TypeUtils
[ https://issues.apache.org/jira/browse/GEODE-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan José Ramos Cassella resolved GEODE-4437. - Resolution: Fixed Fix Version/s: 1.5.0 > Delete unused methods and refactor TypeUtils > > > Key: GEODE-4437 > URL: https://issues.apache.org/jira/browse/GEODE-4437 > Project: Geode > Issue Type: Sub-task >Reporter: Juan José Ramos Cassella >Assignee: Juan José Ramos Cassella >Priority: Major > Fix For: 1.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4436) Create thorough unit tests for TypeUtils class
[
https://issues.apache.org/jira/browse/GEODE-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella resolved GEODE-4436.
-
Resolution: Fixed
Fix Version/s: 1.5.0
> Create thorough unit tests for TypeUtils class
> --
>
> Key: GEODE-4436
> URL: https://issues.apache.org/jira/browse/GEODE-4436
> Project: Geode
> Issue Type: Sub-task
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Fix For: 1.5.0
>
>
> This sub-tasks should be completed before refactoring the {{TypeUtils}} class
> to make sure no new bugs are introduced with the refactoring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
