[jira] [Created] (GEODE-4277) gfsh doc correction: Lucene search default limit is 100, not -1
Diane Hardman created GEODE-4277: Summary: gfsh doc correction: Lucene search default limit is 100, not -1 Key: GEODE-4277 URL: https://issues.apache.org/jira/browse/GEODE-4277 Project: Geode Issue Type: Bug Components: docs Reporter: Diane Hardman In the following gfsh ref page for Lucene search is an error: http://gemfire.docs.pivotal.io/geode/tools_modules/gfsh/command-pages/search.html#search_lucene"; In the table of command options it states that the default limit is -1. This will result in Lucene throwing an exception. The actual default limit is 100. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GEODE-3813) Region registerInterest API usage of type parameters is broken
[
https://issues.apache.org/jira/browse/GEODE-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-3813:
-
Component/s: docs
> Region registerInterest API usage of type parameters is broken
> --
>
> Key: GEODE-3813
> URL: https://issues.apache.org/jira/browse/GEODE-3813
> Project: Geode
> Issue Type: Bug
> Components: client queues, docs
>Reporter: Kirk Lund
>Assignee: Jason Huynh
>Priority: Major
>
> The registerInterest API works for single key registration but is broken for
> all other types of registration if the Region is declared with type
> parameters:
> Single key (works):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1);
> {noformat}
> ALL_KEYS token is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest("ALL_KEYS");
> {noformat}
> List of keys is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> List listOfKeys = new ArrayList<>();
> listOfKeys.add(1);
> listOfKeys.add(2);
> region.registerInterest(listOfKeys);
> {noformat}
> When this ticket is fixed and the API is updated, we should consider adding
> support for var args:
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1, 2, 3);
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-3813) Region registerInterest API usage of type parameters is broken
[
https://issues.apache.org/jira/browse/GEODE-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-3813:
-
Component/s: (was: docs)
> Region registerInterest API usage of type parameters is broken
> --
>
> Key: GEODE-3813
> URL: https://issues.apache.org/jira/browse/GEODE-3813
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Kirk Lund
>Assignee: Jason Huynh
>Priority: Major
>
> The registerInterest API works for single key registration but is broken for
> all other types of registration if the Region is declared with type
> parameters:
> Single key (works):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1);
> {noformat}
> ALL_KEYS token is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest("ALL_KEYS");
> {noformat}
> List of keys is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> List listOfKeys = new ArrayList<>();
> listOfKeys.add(1);
> listOfKeys.add(2);
> region.registerInterest(listOfKeys);
> {noformat}
> When this ticket is fixed and the API is updated, we should consider adding
> support for var args:
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1, 2, 3);
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4250) Users would like a command to re-establish redundancy without rebalancing
[ https://issues.apache.org/jira/browse/GEODE-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345952#comment-16345952 ] Diane Hardman commented on GEODE-4250: -- For related request see GEODE-4434 > Users would like a command to re-establish redundancy without rebalancing > - > > Key: GEODE-4250 > URL: https://issues.apache.org/jira/browse/GEODE-4250 > Project: Geode > Issue Type: Improvement > Components: docs, regions >Reporter: Fred Krone >Priority: Major > > Acceptance criteria: > -- There is a way for a user to detect that redundancy is restored > -- There is a way to check current redundancy > -- Can set moveBuckets and movePrimary to false and run rebalance > > Command would only succeed when the system is fully redundant. > Re-establishing Redundancy after the loss of a peer node is typically far > more urgent and important than achieving better balance. The operational > impact of rebalancing is also much higher, forcing impacted buckets' updates > to be distributed to _redundancy-copies + 1_ peer processes and potentially > spiking p2p connections/threads (and thus load) far beyond normal operations. > If the system is already close to exhausting available capacity for some > hardware component, this can be enough to push it over-the-edge (and may > force the original fault to recur). This problem is exacerbated when the > cluster's overall capacity has been reduced due to the loss of a physical > server. Without the ability to separate the operational tasks of > re-establishing full data redundancy and rebalancing bucket partitions (that > are already safely redundant), system administrators may be forced to > provision replacement capacity _before_ they can restore full service, thus > increasing downtime unnecessarily. > For these reasons, we must add the option to execute these operational tasks > separately. > It still makes sense for _rebalancing_ ops to first re-establish redundancy, > so we can keep the existing GFSH command/behavior (it would still be useful > to clearly log completion of one step before the next one begins). We need a > new GFSH command/ResourceManager API to execute re-establishment of > redundancy _without_ rebalancing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4451) When a gateway sender is created using gfsh and fails to connect due to AuthenticationFailedException, it is left in an inconsistent state
[
https://issues.apache.org/jira/browse/GEODE-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350828#comment-16350828
]
Diane Hardman commented on GEODE-4451:
--
If the gateway sender fails authentication with the receiver, the exception
should be thrown and the gateway sender should be destroyed.
> When a gateway sender is created using gfsh and fails to connect due to
> AuthenticationFailedException, it is left in an inconsistent state
> --
>
> Key: GEODE-4451
> URL: https://issues.apache.org/jira/browse/GEODE-4451
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Priority: Major
>
> If I attempt to create a gateway sender with invalid credentials using gfsh,
> it fails like:
> {noformat}
> (2) Executing - create gateway-sender --remote-distributed-system-id=1
> --id=ny --dispatcher-threads=1 --parallel=true
> Member | Status
> -- |
> --
> ln-1 | ERROR: Could not start a gateway sender ny because of exception Could
> not start a gateway sender 84 because of exception
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials.
> {noformat}
> The 84 should be the gateway sender id; instead its the thread id (from
> \{{ConcurrentParallelGatewaySenderEventProcessor.waitForRunningStatus}}.
> In the server log, I see 5 AuthenticationFailedException stacks like (one per
> dispatcher-thread):
> {noformat}
> [severe 2018/01/31 16:13:12.638 PST ln-1 GatewaySender_ny_0> tid=0x55] Message dispatch failed due to unexpected
> exception..
> org.apache.geode.internal.cache.wan.GatewaySenderException:
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials., caused by
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials.
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:432)
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:75)
> at
> org.apache.geode.internal.cache.wan.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:74)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1078)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1050)
> Caused by: org.apache.geode.security.AuthenticationFailedException:
> Authentication error. Please check your credentials.
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.readMessage(HandShake.java:1397)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.handshakeWithServer(HandShake.java:1253)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:118)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:136)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:259)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:206)
> at
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:902)
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:388)
> ... 4 more
> {noformat}
> A thread dump shows the Event Processor threads are gone, but 5
> BatchRemovalThreads like this exist:
> {noformat}
> "BatchRemovalThread" #96 daemon prio=10 os_prio=31 tid=0x7fc1dd009000
> nid=0xcb03 waiting on condition [0x7e245000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0007a04043c8> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2163)
> at
> org.apache.geode.internal.util.concurrent.StoppableCondition.await(StoppableCondition.java:61)
> at
> org.apache.geode.
[jira] [Commented] (GEODE-2667) Need API to destroy gateway receiver
[
https://issues.apache.org/jira/browse/GEODE-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366492#comment-16366492
]
Diane Hardman commented on GEODE-2667:
--
For docs: Even though it is mentioned in the javadoc, it is worth noting that
the receiver must be stopped (via the stop method) before calling destroy.
> Need API to destroy gateway receiver
> -
>
> Key: GEODE-2667
> URL: https://issues.apache.org/jira/browse/GEODE-2667
> Project: Geode
> Issue Type: Bug
> Components: docs, wan
>Reporter: Swapnil Bawaskar
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A {{GatewayReceiver}} can be created from {{GatewayReceiverFactory}},
> however, there is no API for destroying the {{GatewayReceiver}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-3813) Region registerInterest API usage of type parameters is broken
[
https://issues.apache.org/jira/browse/GEODE-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-3813:
-
Fix Version/s: 1.5.0
> Region registerInterest API usage of type parameters is broken
> --
>
> Key: GEODE-3813
> URL: https://issues.apache.org/jira/browse/GEODE-3813
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Kirk Lund
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> The registerInterest API works for single key registration but is broken for
> all other types of registration if the Region is declared with type
> parameters:
> Single key (works):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1);
> {noformat}
> ALL_KEYS token is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest("ALL_KEYS");
> {noformat}
> List of keys is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> List listOfKeys = new ArrayList<>();
> listOfKeys.add(1);
> listOfKeys.add(2);
> region.registerInterest(listOfKeys);
> {noformat}
> When this ticket is fixed and the API is updated, we should consider adding
> support for var args:
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1, 2, 3);
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-3813) Region registerInterest API usage of type parameters is broken
[
https://issues.apache.org/jira/browse/GEODE-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-3813:
-
Component/s: docs
> Region registerInterest API usage of type parameters is broken
> --
>
> Key: GEODE-3813
> URL: https://issues.apache.org/jira/browse/GEODE-3813
> Project: Geode
> Issue Type: Bug
> Components: client queues, docs
>Reporter: Kirk Lund
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The registerInterest API works for single key registration but is broken for
> all other types of registration if the Region is declared with type
> parameters:
> Single key (works):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1);
> {noformat}
> ALL_KEYS token is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest("ALL_KEYS");
> {noformat}
> List of keys is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> List listOfKeys = new ArrayList<>();
> listOfKeys.add(1);
> listOfKeys.add(2);
> region.registerInterest(listOfKeys);
> {noformat}
> When this ticket is fixed and the API is updated, we should consider adding
> support for var args:
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1, 2, 3);
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
Diane Hardman created GEODE-4709: Summary: Sample output missing in gfsh docs for 'list gateways' Key: GEODE-4709 URL: https://issues.apache.org/jira/browse/GEODE-4709 Project: Geode Issue Type: Bug Components: docs Reporter: Diane Hardman It looks like all other 'list' commands have both Example commands and Sample Output except for 'list gateways'. Please add. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370786#comment-16370786 ] Diane Hardman commented on GEODE-4709: -- An example output of 'list gateways' can be found at the bottom of the following page: https://geode.apache.org/docs/guide/12/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Priority: Major > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4251) [CI Failure]Class org.apache.geode.internal.cache.tier.sockets.RegisterInterestKeysPRDUnitTest --- testRegisterCreatesInvalidEntry
[
https://issues.apache.org/jira/browse/GEODE-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-4251:
-
Fix Version/s: (was: 1.5.0)
> [CI Failure]Class
> org.apache.geode.internal.cache.tier.sockets.RegisterInterestKeysPRDUnitTest
> --- testRegisterCreatesInvalidEntry
>
>
> Key: GEODE-4251
> URL: https://issues.apache.org/jira/browse/GEODE-4251
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.RegisterInterestKeysDUnitTest$$Lambda$28/1575286050.run
> in VM 3 running on Host ea663fe20602 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
> at
> org.apache.geode.internal.cache.tier.sockets.RegisterInterestKeysDUnitTest.testRegisterCreatesInvalidEntry(RegisterInterestKeysDUnitTest.java:135)
> 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> 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.gr
[jira] [Updated] (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
]
Diane Hardman updated GEODE-4631:
-
Fix Version/s: (was: 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
> 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] [Resolved] (GEODE-2905) CI failure: org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > searchWithoutIndexShouldReturnError
[
https://issues.apache.org/jira/browse/GEODE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman resolved GEODE-2905.
--
Resolution: Cannot Reproduce
> CI failure:
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest >
> searchWithoutIndexShouldReturnError
> --
>
> Key: GEODE-2905
> URL: https://issues.apache.org/jira/browse/GEODE-2905
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: nabarun
>Priority: Major
>
> This test failed in Apache Jenkins build #830.
> {noformat}
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest >
> searchWithoutIndexShouldReturnError FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.searchWithoutIndexShouldReturnError(LuceneIndexCommandsDUnitTest.java:462)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4144) CI failure: org.apache.geode.internal.cache.ha.PutAllDUnitTest > testPutAll FAILED
[
https://issues.apache.org/jira/browse/GEODE-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-4144:
-
Fix Version/s: 1.4.0
> CI failure: org.apache.geode.internal.cache.ha.PutAllDUnitTest > testPutAll
> FAILED
> --
>
> Key: GEODE-4144
> URL: https://issues.apache.org/jira/browse/GEODE-4144
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Affects Versions: 1.4.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
> Attachments: geode-4144.logs
>
>
> {noformat}
> org.apache.geode.internal.cache.ha.PutAllDUnitTest > testPutAll FAILED
> java.lang.AssertionError: expected:
> org.apache.geode.internal.cache.EventID
> but was:
> org.apache.geode.internal.cache.EventID
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.geode.internal.cache.ha.PutAllDUnitTest.testPutAll(PutAllDUnitTest.java:372)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4742) OQL operator '/' without surrounding spaces generates syntax error
Diane Hardman created GEODE-4742:
Summary: OQL operator '/' without surrounding spaces generates
syntax error
Key: GEODE-4742
URL: https://issues.apache.org/jira/browse/GEODE-4742
Project: Geode
Issue Type: Bug
Components: querying
Reporter: Diane Hardman
The following query will generate a syntax error:
gfsh>query --query="select * from /example-region x where x.salary/2080 > 30"
Result : false
Message : Query is invalid due for error :
If I add surrounding spaces, the query is successful:
gfsh>query --query="select * from /example-region x where x.salary / 2080 > 30"
Result : true
Limit : 100
Rows : 11
email | emplNumber | firstName | hoursPerWeek | lastName |
salary
-- | -- | - | | |
--
frankie.fo...@example.com | 10010 | Frankie | 30 | Forth |
10
kris.c...@example.com | 10003 | Kris | 40 | Call |
75000
bertie.b...@example.com | 10001 | Bertie | 40 | Bell |
8
morgan.min...@example.com | 10021 | Morgan | 40 | Minnow |
8
ricky.relia...@example.com | 10036 | Ricky | 40 | Reliable |
9
ryan.r...@example.com | 10078 | Ryan | 40 | Redo |
75000
skyler.s...@example.com | 10091 | Skyler | 40 | Skip |
9
dale.dri...@example.com | 10006 | Dale | 40 | Driver |
9
pat.p...@example.com | 10028 | Pat | 40 | Puts |
75000
jessie@example.com | 10066 | Jessie | 20 | Jam |
8
taylor.t...@example.com | 10045 | Taylor | 40 | Tack |
10
I tested the other operators ('+', '-', '*', '%') which all seem to work
correctly with or without surrounding spaces.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4742) OQL operator '/' without surrounding spaces generates syntax error
[
https://issues.apache.org/jira/browse/GEODE-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-4742:
-
Component/s: docs
> OQL operator '/' without surrounding spaces generates syntax error
> --
>
> Key: GEODE-4742
> URL: https://issues.apache.org/jira/browse/GEODE-4742
> Project: Geode
> Issue Type: Bug
> Components: docs, querying
>Reporter: Diane Hardman
>Priority: Major
>
> The following query will generate a syntax error:
> gfsh>query --query="select * from /example-region x where x.salary/2080 > 30"
> Result : false
> Message : Query is invalid due for error : unexpected token: salary>
> If I add surrounding spaces, the query is successful:
> gfsh>query --query="select * from /example-region x where x.salary / 2080 >
> 30"
> Result : true
> Limit : 100
> Rows : 11
>
> email | emplNumber | firstName | hoursPerWeek | lastName
> | salary
> -- | -- | - | |
> | --
> frankie.fo...@example.com | 10010 | Frankie | 30 | Forth
> | 10
> kris.c...@example.com | 10003 | Kris | 40 | Call
> | 75000
> bertie.b...@example.com | 10001 | Bertie | 40 | Bell
> | 8
> morgan.min...@example.com | 10021 | Morgan | 40 | Minnow
> | 8
> ricky.relia...@example.com | 10036 | Ricky | 40 | Reliable
> | 9
> ryan.r...@example.com | 10078 | Ryan | 40 | Redo
> | 75000
> skyler.s...@example.com | 10091 | Skyler | 40 | Skip
> | 9
> dale.dri...@example.com | 10006 | Dale | 40 | Driver
> | 9
> pat.p...@example.com | 10028 | Pat | 40 | Puts
> | 75000
> jessie@example.com | 10066 | Jessie | 20 | Jam
> | 8
> taylor.t...@example.com | 10045 | Taylor | 40 | Tack
> | 10
> I tested the other operators ('+', '-', '*', '%') which all seem to work
> correctly with or without surrounding spaces.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4742) OQL operator '/' without surrounding spaces generates syntax error
[
https://issues.apache.org/jira/browse/GEODE-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379627#comment-16379627
]
Diane Hardman commented on GEODE-4742:
--
The fix for this involves significant changes to the OQL parser which will take
longer to implement and test.
In the meantime, please add to the documentation on using operators in the
WHERE clause to surround them with a space character.
> OQL operator '/' without surrounding spaces generates syntax error
> --
>
> Key: GEODE-4742
> URL: https://issues.apache.org/jira/browse/GEODE-4742
> Project: Geode
> Issue Type: Bug
> Components: docs, querying
>Reporter: Diane Hardman
>Priority: Major
>
> The following query will generate a syntax error:
> gfsh>query --query="select * from /example-region x where x.salary/2080 > 30"
> Result : false
> Message : Query is invalid due for error : unexpected token: salary>
> If I add surrounding spaces, the query is successful:
> gfsh>query --query="select * from /example-region x where x.salary / 2080 >
> 30"
> Result : true
> Limit : 100
> Rows : 11
>
> email | emplNumber | firstName | hoursPerWeek | lastName
> | salary
> -- | -- | - | |
> | --
> frankie.fo...@example.com | 10010 | Frankie | 30 | Forth
> | 10
> kris.c...@example.com | 10003 | Kris | 40 | Call
> | 75000
> bertie.b...@example.com | 10001 | Bertie | 40 | Bell
> | 8
> morgan.min...@example.com | 10021 | Morgan | 40 | Minnow
> | 8
> ricky.relia...@example.com | 10036 | Ricky | 40 | Reliable
> | 9
> ryan.r...@example.com | 10078 | Ryan | 40 | Redo
> | 75000
> skyler.s...@example.com | 10091 | Skyler | 40 | Skip
> | 9
> dale.dri...@example.com | 10006 | Dale | 40 | Driver
> | 9
> pat.p...@example.com | 10028 | Pat | 40 | Puts
> | 75000
> jessie@example.com | 10066 | Jessie | 20 | Jam
> | 8
> taylor.t...@example.com | 10045 | Taylor | 40 | Tack
> | 10
> I tested the other operators ('+', '-', '*', '%') which all seem to work
> correctly with or without surrounding spaces.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4451) When a gateway sender is created using gfsh and fails to connect due to AuthenticationFailedException, it is left in an inconsistent state
[
https://issues.apache.org/jira/browse/GEODE-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350828#comment-16350828
]
Diane Hardman edited comment on GEODE-4451 at 2/28/18 7:35 PM:
---
If the gateway sender fails authentication with the receiver, the exception
should be thrown and the gateway sender should retry to connection.
was (Author: dhardman):
If the gateway sender fails authentication with the receiver, the exception
should be thrown and the gateway sender should be destroyed.
> When a gateway sender is created using gfsh and fails to connect due to
> AuthenticationFailedException, it is left in an inconsistent state
> --
>
> Key: GEODE-4451
> URL: https://issues.apache.org/jira/browse/GEODE-4451
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Priority: Major
>
> If I attempt to create a gateway sender with invalid credentials using gfsh,
> it fails like:
> {noformat}
> (2) Executing - create gateway-sender --remote-distributed-system-id=1
> --id=ny --dispatcher-threads=1 --parallel=true
> Member | Status
> -- |
> --
> ln-1 | ERROR: Could not start a gateway sender ny because of exception Could
> not start a gateway sender 84 because of exception
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials.
> {noformat}
> The 84 should be the gateway sender id; instead its the thread id (from
> \{{ConcurrentParallelGatewaySenderEventProcessor.waitForRunningStatus}}.
> In the server log, I see 5 AuthenticationFailedException stacks like (one per
> dispatcher-thread):
> {noformat}
> [severe 2018/01/31 16:13:12.638 PST ln-1 GatewaySender_ny_0> tid=0x55] Message dispatch failed due to unexpected
> exception..
> org.apache.geode.internal.cache.wan.GatewaySenderException:
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials., caused by
> org.apache.geode.security.AuthenticationFailedException: Authentication
> error. Please check your credentials.
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:432)
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:75)
> at
> org.apache.geode.internal.cache.wan.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:74)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1078)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1050)
> Caused by: org.apache.geode.security.AuthenticationFailedException:
> Authentication error. Please check your credentials.
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.readMessage(HandShake.java:1397)
> at
> org.apache.geode.internal.cache.tier.sockets.HandShake.handshakeWithServer(HandShake.java:1253)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:118)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:136)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:259)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:206)
> at
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:902)
> at
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:388)
> ... 4 more
> {noformat}
> A thread dump shows the Event Processor threads are gone, but 5
> BatchRemovalThreads like this exist:
> {noformat}
> "BatchRemovalThread" #96 daemon prio=10 os_prio=31 tid=0x7fc1dd009000
> nid=0xcb03 waiting on condition [0x7e245000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0007a04043c8> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.loc
[jira] [Commented] (GEODE-4770) Destroying an unstarted GatewayReceiver throws an NPE
[
https://issues.apache.org/jira/browse/GEODE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388597#comment-16388597
]
Diane Hardman commented on GEODE-4770:
--
Ken,
Is this fix needed in the Geode 1.5.0 release branch?
> Destroying an unstarted GatewayReceiver throws an NPE
> -
>
> Key: GEODE-4770
> URL: https://issues.apache.org/jira/browse/GEODE-4770
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Found while writing tests for a new Gfsh command to destroy a GatewayReceiver:
> Create a GatewayReceiver with manualStart = true
> {{create gateway-receiver --manual-start==true ...}}
> NPE is thrown by the {{destroy()}} in the Function that implements the new
> {{destroy gateway-receiver}} command.
> {code:java}
> if (receiver.isRunning()) {
> receiver.stop();
> }
> receiver.destroy();
> {code}
> NPE is thrown here:
> {code:java|title=GatewayReceiverImpl}
> public void destroy() {
> if (receiver.isRunning()) {
> {code}
> because {{receiver}} is not set until the the GatewayReceiver is started.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4744) Allow java.util.Map#get in OQL when security is enabled
[
https://issues.apache.org/jira/browse/GEODE-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-4744:
-
Fix Version/s: 1.5.0
> Allow java.util.Map#get in OQL when security is enabled
> ---
>
> Key: GEODE-4744
> URL: https://issues.apache.org/jira/browse/GEODE-4744
> Project: Geode
> Issue Type: Improvement
> Components: querying
>Affects Versions: 1.3.0
>Reporter: Masaki Yamakawa
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> I am migrating from GemFire 7.x to Geode. After migration, An exception is
> now thrown in OQL when security is enabled.
> The OQL in which the exception occurs is as follows:
> {code:sql}
> select * from /RegionA a where a['intData']=1 and a['strData1']='ABC' and
> a.get(1)=98 and a.get('strData2')='DEF'
> {code}
> {code:sql}
> select * from /RegionB where mapField.get('mapData1')='ZZZ' and
> mapField.get(0)=123
> {code}
> * The value of Region A is java.util.Map, the value of Region B is its domain
> object, and it holds the public field of java.util.Map called mapField.
> I would like to allow java.util.Map#get in OQL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
Diane Hardman created GEODE-4913: Summary: gfsh start server cmd is not recognizing local properties and cache.xml, instead using default Key: GEODE-4913 URL: https://issues.apache.org/jira/browse/GEODE-4913 Project: Geode Issue Type: Bug Components: configuration, gfsh Reporter: Diane Hardman The attached tarfile contains scripts to start up 2 clusters and connect them with a WAN gateway. The script for starting the servers for the first cluster (ln) fail because the default 40404 port is being used for each server. Instead, the start server command should be using the local cache.xml files found under config/gemfire-XX-hub.xml which contain: This should force gfsh to choose the next available port, rather than the default 40404. It appears that the default cache.xml is being used instead. This problem does not exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
[ https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4913: - Attachment: geode-script_10-31-2016.tgz > gfsh start server cmd is not recognizing local properties and cache.xml, > instead using default > -- > > Key: GEODE-4913 > URL: https://issues.apache.org/jira/browse/GEODE-4913 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Diane Hardman >Priority: Major > Attachments: geode-script_10-31-2016.tgz > > > The attached tarfile contains scripts to start up 2 clusters and connect them > with a WAN gateway. > The script for starting the servers for the first cluster (ln) fail because > the default 40404 port is being used for each server. Instead, the start > server command should be using the local cache.xml files found under > config/gemfire-XX-hub.xml which contain: > > This should force gfsh to choose the next available port, rather than the > default 40404. > It appears that the default cache.xml is being used instead. This problem > does not exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
[ https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4913: - Description: The attached tarfile contains scripts to start up 2 clusters and connect them with a WAN gateway. The script for starting the servers for the first cluster (ln) fail because the default 40404 port is being used for each server. Instead, the start server command should be using the local cache.xml files found under config/gemfire-XX-hub.xml which contain: This should force gfsh to choose the next available port, rather than the default 40404. It appears that the default cache.xml is NOT being used instead. This problem does not exist with Geode 1.4.0. was: The attached tarfile contains scripts to start up 2 clusters and connect them with a WAN gateway. The script for starting the servers for the first cluster (ln) fail because the default 40404 port is being used for each server. Instead, the start server command should be using the local cache.xml files found under config/gemfire-XX-hub.xml which contain: This should force gfsh to choose the next available port, rather than the default 40404. It appears that the default cache.xml is being used instead. This problem does not exist with Geode 1.4.0. > gfsh start server cmd is not recognizing local properties and cache.xml, > instead using default > -- > > Key: GEODE-4913 > URL: https://issues.apache.org/jira/browse/GEODE-4913 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Diane Hardman >Priority: Major > Attachments: geode-script_10-31-2016.tgz > > > The attached tarfile contains scripts to start up 2 clusters and connect them > with a WAN gateway. > The script for starting the servers for the first cluster (ln) fail because > the default 40404 port is being used for each server. Instead, the start > server command should be using the local cache.xml files found under > config/gemfire-XX-hub.xml which contain: > > This should force gfsh to choose the next available port, rather than the > default 40404. > It appears that the default cache.xml is NOT being used instead. This problem > does not exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
[ https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4913: - Description: The attached tarfile contains scripts to start up 2 clusters and connect them with a WAN gateway. The script for starting the servers for the first cluster (ln) fail because the default 40404 port is being used for each server. Instead, the start server command should be using the local cache.xml files found under config/gemfire-XX-hub.xml which contain: This should force gfsh to choose the next available port, rather than the default 40404. It appears that the default cache.xml is being used. This problem does not exist with Geode 1.4.0. was: The attached tarfile contains scripts to start up 2 clusters and connect them with a WAN gateway. The script for starting the servers for the first cluster (ln) fail because the default 40404 port is being used for each server. Instead, the start server command should be using the local cache.xml files found under config/gemfire-XX-hub.xml which contain: This should force gfsh to choose the next available port, rather than the default 40404. It appears that the default cache.xml is NOT being used instead. This problem does not exist with Geode 1.4.0. > gfsh start server cmd is not recognizing local properties and cache.xml, > instead using default > -- > > Key: GEODE-4913 > URL: https://issues.apache.org/jira/browse/GEODE-4913 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Diane Hardman >Priority: Major > Attachments: geode-script_10-31-2016.tgz > > > The attached tarfile contains scripts to start up 2 clusters and connect them > with a WAN gateway. > The script for starting the servers for the first cluster (ln) fail because > the default 40404 port is being used for each server. Instead, the start > server command should be using the local cache.xml files found under > config/gemfire-XX-hub.xml which contain: > > This should force gfsh to choose the next available port, rather than the > default 40404. > It appears that the default cache.xml is being used. This problem does not > exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
[ https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4913: - Affects Version/s: 1.6.0 > gfsh start server cmd is not recognizing local properties and cache.xml, > instead using default > -- > > Key: GEODE-4913 > URL: https://issues.apache.org/jira/browse/GEODE-4913 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Affects Versions: 1.6.0 >Reporter: Diane Hardman >Priority: Major > Attachments: geode-script_10-31-2016.tgz > > > The attached tarfile contains scripts to start up 2 clusters and connect them > with a WAN gateway. > The script for starting the servers for the first cluster (ln) fail because > the default 40404 port is being used for each server. Instead, the start > server command should be using the local cache.xml files found under > config/gemfire-XX-hub.xml which contain: > > This should force gfsh to choose the next available port, rather than the > default 40404. > It appears that the default cache.xml is being used. This problem does not > exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
[ https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4913: - Affects Version/s: 1.5.0 > gfsh start server cmd is not recognizing local properties and cache.xml, > instead using default > -- > > Key: GEODE-4913 > URL: https://issues.apache.org/jira/browse/GEODE-4913 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Affects Versions: 1.5.0, 1.6.0 >Reporter: Diane Hardman >Priority: Major > Attachments: geode-script_10-31-2016.tgz > > > The attached tarfile contains scripts to start up 2 clusters and connect them > with a WAN gateway. > The script for starting the servers for the first cluster (ln) fail because > the default 40404 port is being used for each server. Instead, the start > server command should be using the local cache.xml files found under > config/gemfire-XX-hub.xml which contain: > > This should force gfsh to choose the next available port, rather than the > default 40404. > It appears that the default cache.xml is being used. This problem does not > exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default
[ https://issues.apache.org/jira/browse/GEODE-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4913: - Priority: Critical (was: Major) > gfsh start server cmd is not recognizing local properties and cache.xml, > instead using default > -- > > Key: GEODE-4913 > URL: https://issues.apache.org/jira/browse/GEODE-4913 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Affects Versions: 1.5.0, 1.6.0 >Reporter: Diane Hardman >Priority: Critical > Attachments: geode-script_10-31-2016.tgz > > > The attached tarfile contains scripts to start up 2 clusters and connect them > with a WAN gateway. > The script for starting the servers for the first cluster (ln) fail because > the default 40404 port is being used for each server. Instead, the start > server command should be using the local cache.xml files found under > config/gemfire-XX-hub.xml which contain: > > This should force gfsh to choose the next available port, rather than the > default 40404. > It appears that the default cache.xml is being used. This problem does not > exist with Geode 1.4.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4962) Fix typo and output format from 'list gateways' gfsh command
Diane Hardman created GEODE-4962: Summary: Fix typo and output format from 'list gateways' gfsh command Key: GEODE-4962 URL: https://issues.apache.org/jira/browse/GEODE-4962 Project: Geode Issue Type: Bug Components: gfsh, wan Reporter: Diane Hardman The output printed from `list gateways` command needs some TLC: Sample output: ``` Cluster-2 gfsh>list gateways Gateways GatewaySender GatewaySender Id | Member | Remote Cluster Id | Type | Status | Queued Events | Receiver Location | | - | | --- | - | - ny | 10.118.19.46(server-ln-1:31527):1026 | 1 | Parallel | Running | 0 | 10.118.19.46:5248 ny | 10.118.19.46(server-ln-2:31545):1027 | 1 | Parallel | Running | 0 | 10.118.19.46:5269 GatewayReceiver Member | Port | Sender Count | Sender's Connected | | | 10.118.19.46(server-ln-1:31527):1026 | 5407 | 7 | [Ljava.lang.String;@7deec2d6 10.118.19.46(server-ln-2:31545):1027 | 5071 | 7 | [Ljava.lang.String;@6baa580f ``` Note: 'Sender's Connected' should instead be 'Senders Connected' Also, need to pretty-print the String[] for Senders Connected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-7198) C++ authinitialize example hangs
Diane Hardman created GEODE-7198: Summary: C++ authinitialize example hangs Key: GEODE-7198 URL: https://issues.apache.org/jira/browse/GEODE-7198 Project: Geode Issue Type: Bug Components: native client Reporter: Diane Hardman After building geode-native from develop branch on my mac, I then followed the instructions to build the geode-native examples found here: [https://github.com/apache/geode-native/tree/develop/examples] Trying to run the authinitialize example resulted in a hang. 1. First I needed to correct the startserver.sh script to remove spaces around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. 2. Running cpp-authinitialize seems to hang when executing GetCredentials: dhardman$ ./cpp-authinitialize ExampleAuthInitialize::ExampleAuthInitialize called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called libc++abi.dylib: terminating with uncaught exception of type apache::geode::client::NotConnectedException: : not connected to Geode Abort trap: 6 Expected: The README file indicates the following output ExampleAuthInitialize::ExampleAuthInitialize called ExampleAuthInitialize::getCredentials called a = 1 b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7203) C++ examples need to be updated
Diane Hardman created GEODE-7203: Summary: C++ examples need to be updated Key: GEODE-7203 URL: https://issues.apache.org/jira/browse/GEODE-7203 Project: Geode Issue Type: Bug Components: examples, native client Reporter: Diane Hardman After reviewing the C++ native client examples I found several problems: # Transaction - README should be updated to indicate random output; currently it says to expect the following output, but this will be different each time: Created cache Created region 'exampleRegion' Rolled back transaction - retrying(4) Rolled back transaction - retrying(3) Rolled back transaction - retrying(2) Committed transaction - exiting # functionexecution - this is the only example that spins up a server named 'the-server'; the startserver.sh script should be updated to reflect the same name used in all other examples 'server'. # pdxserializable - either the README needs to change to show the actual output of running the client app, or main.cpp should be changed to produce the same output presented in the README. The second get (of Customer2) is currently not formatted for printing like the first get (of Customer1). # All examples: stopserver.sh should cleanup leftover directories locator/, server/, and any *.gfs. If there is any reason to keep these around for failing tests, then a separate cleanup.sh script should do this. # authinitialize - startserver.sh fails due to extra spaces around '=' when setting RESOLVEDPATH and AUTHENTICATOR. This example also fails to run, instead hangs when executing getCredentials, but this was filed as GEODE-7198. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928949#comment-16928949 ] Diane Hardman commented on GEODE-7198: -- After modifying main.cpp to set log-level to 'debug', I am seeing the following exception in server.log file: Security exception: org.apache.geode.security.AuthenticationFailedException: javaobject.SimpleAuthenticator, caused by: java.lang.ClassNotFoundException: javaobject.SimpleAuthenticator > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Diane Hardman >Priority: Major > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928951#comment-16928951 ] Diane Hardman commented on GEODE-7198: -- Another issue, why is this labeled as a warning in the server log? [warn 2019/09/12 16:50:54.616 PDT tid=0x3e] Server connection from [identity(0.0.0.0(default_GeodeDS:51001:loner):2:Native_cdgdecdece51001:default_GeodeDS,connection=1; port=58813]: Security exception: org.apache.geode.security.AuthenticationFailedException: javaobject.SimpleAuthenticator, caused by: java.lang.ClassNotFoundException: javaobject.SimpleAuthenticator > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Diane Hardman >Priority: Major > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7198: - Attachment: server.log > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Diane Hardman >Priority: Major > Attachments: server.log > > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7426) Integration tests segfault on MacOs with geode-native
[ https://issues.apache.org/jira/browse/GEODE-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7426: - Fix Version/s: (was: 1.12.0) 1.11.0 > Integration tests segfault on MacOs with geode-native > - > > Key: GEODE-7426 > URL: https://issues.apache.org/jira/browse/GEODE-7426 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > A segfault occurs on MacOS when running any of the integration tests. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7451) Add certificate & private key in correct order to avoid exception
[ https://issues.apache.org/jira/browse/GEODE-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7451: - Fix Version/s: (was: 1.12.0) 1.11.0 > Add certificate & private key in correct order to avoid exception > - > > Key: GEODE-7451 > URL: https://issues.apache.org/jira/browse/GEODE-7451 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When using TLS, geode native client throws an exception due to wrong order on > method calling: > "Exception while querying locator: apache::geode::client::SslException: > Invalid SSL keystore password." > This is due to in SSLImpl.cpp constructor, the private key is added before > the certificate. According to ACE documentation, we should reverse order due > to when the private key is added it is verified against the certificate. So > we should call sslctx->private_key after calling sslctx->certificate > http://www.aoc.nrao.edu/php/tjuerges/ALMA/ACE-5.8.1/html/ace/a00493.html#a5fa01171382ad69ac372dae7e3860211 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7419: - Fix Version/s: (was: 1.12.0) 1.11.0 > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7347) Race condition between Cache and ClientMetadataService
[ https://issues.apache.org/jira/browse/GEODE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7347: - Fix Version/s: 1.11.0 > Race condition between Cache and ClientMetadataService > -- > > Key: GEODE-7347 > URL: https://issues.apache.org/jira/browse/GEODE-7347 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Assignee: Michael Oleske >Priority: Major > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > It was discovered that the ClientMetadataService would call into CacheImpl, > which contains a backreference to Cache, and this could occur in the middle > of a Cache move, where the pimpl pointer was updated, but not the > backreference. > The solution will be to guard the pimpl during the move, so the Cache can > update it's pimpl and the backreference. There exists > CacheImpl::doIfDestroyNotPending that locks the pimpl while executing a > function to facilitate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7429) Chocolatey install of active Perl times out
[ https://issues.apache.org/jira/browse/GEODE-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7429: - Fix Version/s: 1.11.0 > Chocolatey install of active Perl times out > --- > > Key: GEODE-7429 > URL: https://issues.apache.org/jira/browse/GEODE-7429 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It is timing out when using packer buuld-windows.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7285) Several Examples Don't Work on Windows
[ https://issues.apache.org/jira/browse/GEODE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7285: - Fix Version/s: 1.11.0 > Several Examples Don't Work on Windows > -- > > Key: GEODE-7285 > URL: https://issues.apache.org/jira/browse/GEODE-7285 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The list of examples below do not work do to a mismatch between the server > start/stop scripts and the code. Specifically, several scripts create/destroy > a region of one name, but the example code tries to use a region of a > different name. > Broken examples: > * continuousquery (Windows) > * dataserializable (Windows) > * pdxserializable (Windows) > * pdxserializer (Windows) > * transaction (Windows) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7235) Disable new Clang warnings to fix build for now
[ https://issues.apache.org/jira/browse/GEODE-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7235: - Fix Version/s: 1.11.0 > Disable new Clang warnings to fix build for now > --- > > Key: GEODE-7235 > URL: https://issues.apache.org/jira/browse/GEODE-7235 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Apple pushed an XCode update a couple of days ago to version ` > Apple clang version 11.0.0 (clang-1100.0.33.8)`. This version flags some new > warnings in our code, and since we have warnings-as-errors turned on we blow > up. Fixing these warnings is non-trivial, so we need to disable them in the > top-level CMakeLists.txt and file another Jira issue to do the real fix. > * Steps to repro: > Sync up to the latest `develop` branch of Native Client on a Mac and build > * Expected Result: > Geode Native builds, and produces our libraries > * Actual Result: > Clang warns about "implicitly deleted copy/move ctors declared as default" in > a product header, gives a warning about UTF-8 string literals in test code, > then build fails. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7225) Update OpenSSL download URL in Windows Packer script
[ https://issues.apache.org/jira/browse/GEODE-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7225: - Fix Version/s: 1.11.0 > Update OpenSSL download URL in Windows Packer script > > > Key: GEODE-7225 > URL: https://issues.apache.org/jira/browse/GEODE-7225 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The Windows build of OpenSSL has bumped from 1.1c to 1.1d, and our download > script for Windows is now failing with 404 errors. Just need to change one > character in the URL and we're good to go. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7207) FIx Remaining LGTM "Error" level alerts
[ https://issues.apache.org/jira/browse/GEODE-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7207: - Fix Version/s: 1.11.0 > FIx Remaining LGTM "Error" level alerts > --- > > Key: GEODE-7207 > URL: https://issues.apache.org/jira/browse/GEODE-7207 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > We're down to a manageable number of these now, it should be fairly short > work to fix the remaining issues. > > Acceptance criteria: > When a PR is submitted and LGTM scans the code base, the report for this PR > shows 12 alerts fixed, all of which are "error" level alerts, and no new > alerts introduced. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7203) C++ examples need to be updated
[ https://issues.apache.org/jira/browse/GEODE-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7203: - Fix Version/s: 1.11.0 > C++ examples need to be updated > --- > > Key: GEODE-7203 > URL: https://issues.apache.org/jira/browse/GEODE-7203 > Project: Geode > Issue Type: Bug > Components: examples, native client >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > After reviewing the C++ native client examples I found several problems: > # Transaction - README should be updated to indicate random output; > currently it says to expect the following output, but this will be different > each time: Created cache > Created region 'exampleRegion' > Rolled back transaction - retrying(4) > Rolled back transaction - retrying(3) > Rolled back transaction - retrying(2) > Committed transaction - exiting > # functionexecution - this is the only example that spins up a server named > 'the-server'; the startserver.sh script should be updated to reflect the same > name used in all other examples 'server'. > # pdxserializable - either the README needs to change to show the actual > output of running the client app, or main.cpp should be changed to produce > the same output presented in the README. The second get (of Customer2) is > currently not formatted for printing like the first get (of Customer1). > # All examples: stopserver.sh should cleanup leftover directories locator/, > server/, and any *.gfs. If there is any reason to keep these around for > failing tests, then a separate cleanup.sh script should do this. > # authinitialize - startserver.sh fails due to extra spaces around '=' when > setting RESOLVEDPATH and AUTHENTICATOR. This example also fails to run, > instead hangs when executing getCredentials, but this was filed as GEODE-7198. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7429) Chocolatey install of active Perl times out
[ https://issues.apache.org/jira/browse/GEODE-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7429: - Fix Version/s: (was: 1.11.0) > Chocolatey install of active Perl times out > --- > > Key: GEODE-7429 > URL: https://issues.apache.org/jira/browse/GEODE-7429 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > It is timing out when using packer buuld-windows.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7198: - Fix Version/s: (was: 1.11.0) > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.8.0 >Reporter: Diane Hardman >Assignee: Charlie Black >Priority: Major > Attachments: server.log > > Time Spent: 20m > Remaining Estimate: 0h > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7182) TcpSslConn.cpp does not compile with gcc 8.3
[ https://issues.apache.org/jira/browse/GEODE-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7182: - Fix Version/s: (was: 1.11.0) 1.10.0 > TcpSslConn.cpp does not compile with gcc 8.3 > > > Key: GEODE-7182 > URL: https://issues.apache.org/jira/browse/GEODE-7182 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Owen Nichols >Priority: Major > Fix For: 1.10.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > I tried to build native client using: > $ gcc --version > gcc (Debian 8.3.0-6) 8.3.0 > $ cmake --version > cmake version 3.13.4 > $ openssl version > OpenSSL 1.1.1c 28 May 2019 > and got: > cppcache/src/TcpSslConn.cpp:60: error: catching polymorphic type 'class > std::exception' by value > The BUILDING.md states that I should be able to use "GCC 5 or newer". > Fixing the code to resolve this warning is a straightforward 1-character > change and a good idea anyway even if the official pipelines continue to > compile using older compilers that don't generate this warning yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6312) Missing Prerequisite in BUILDING.md
[ https://issues.apache.org/jira/browse/GEODE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6312: - Fix Version/s: (was: 1.12.0) 1.11.0 > Missing Prerequisite in BUILDING.md > --- > > Key: GEODE-6312 > URL: https://issues.apache.org/jira/browse/GEODE-6312 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The BUILDING.md prerequisites for the native client is missing the JDK, which > is required for building the server side java functions used in some of the > integration tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7451) Add certificate & private key in correct order to avoid exception
[ https://issues.apache.org/jira/browse/GEODE-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7451: - Fix Version/s: (was: 1.11.0) 1.12.0 > Add certificate & private key in correct order to avoid exception > - > > Key: GEODE-7451 > URL: https://issues.apache.org/jira/browse/GEODE-7451 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When using TLS, geode native client throws an exception due to wrong order on > method calling: > "Exception while querying locator: apache::geode::client::SslException: > Invalid SSL keystore password." > This is due to in SSLImpl.cpp constructor, the private key is added before > the certificate. According to ACE documentation, we should reverse order due > to when the private key is added it is verified against the certificate. So > we should call sslctx->private_key after calling sslctx->certificate > http://www.aoc.nrao.edu/php/tjuerges/ALMA/ACE-5.8.1/html/ace/a00493.html#a5fa01171382ad69ac372dae7e3860211 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6312) Missing Prerequisite in BUILDING.md
[ https://issues.apache.org/jira/browse/GEODE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6312: - Fix Version/s: (was: 1.11.0) 1.12.0 > Missing Prerequisite in BUILDING.md > --- > > Key: GEODE-6312 > URL: https://issues.apache.org/jira/browse/GEODE-6312 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The BUILDING.md prerequisites for the native client is missing the JDK, which > is required for building the server side java functions used in some of the > integration tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7419: - Fix Version/s: (was: 1.11.0) 1.12.0 > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.12.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7511) Support Long DNS Names
[ https://issues.apache.org/jira/browse/GEODE-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7511: - Fix Version/s: (was: 1.11.0) 1.12.0 > Support Long DNS Names > -- > > Key: GEODE-7511 > URL: https://issues.apache.org/jira/browse/GEODE-7511 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.12.0 > > Time Spent: 50m > Remaining Estimate: 0h > > NodeJS client was failing on PCC 1.9.1. Long DNS was introduced in PCC 1.9.1 > for locator and server members. The spec for DNS says names can be up to > approximately 256 characters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7619) Confusing error message when cryptoImpl is not on the path
Diane Hardman created GEODE-7619: Summary: Confusing error message when cryptoImpl is not on the path Key: GEODE-7619 URL: https://issues.apache.org/jira/browse/GEODE-7619 Project: Geode Issue Type: Bug Components: native client Reporter: Diane Hardman When following the example sslputget on Linux, if I don't have LD_LIBRARY_PATH set to the location where libcryptoImpl.so resides, when the app does it's first put, the error is ambiguous and caused me to question if I was referencing an incorrect locator IP address. Here is the error message generated: terminate called after throwing an instance of 'std::_Nested_exception' what(): : No locators available Aborted (core dumped) Prefer a more specific error message such as "Could not connect to locator configured with SSL; could not find libcryptoImpl.so. Is LD_LIBRARY_PATH set?" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-5082) Rolling Upgrade tests for Lucene reindex
[ https://issues.apache.org/jira/browse/GEODE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5082: - Component/s: docs > Rolling Upgrade tests for Lucene reindex > > > Key: GEODE-5082 > URL: https://issues.apache.org/jira/browse/GEODE-5082 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario 1: > Status : The system has a new member and others which do not support reindex. > Action: The Apache Geode developer tries to create the index on the new > member (supports reindex) after the region has been created. > Accepted result : An exception must be thrown preventing the creation of the > lucene index. > > Scenario 2: > Status : The system has a mix of new members and old members which do not > support Lucene reindex. > Action: The Apache Geode developer creates the region on the new member, and > then creates the Lucene index. > The old members are now rolled to the new version which supports Lucene Index. > Create lucene index first on the freshly rolled members and then create > region. > Result: This operation must be successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5082) Rolling Upgrade tests for Lucene reindex
[ https://issues.apache.org/jira/browse/GEODE-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451399#comment-16451399 ] Diane Hardman commented on GEODE-5082: -- Note for docs: Scenario 2 described above is how Lucene indexing is supported today (since Geode 1.2.0) and should continue to work during a rolling upgrade. Scenario 1 is new behavior (ability to add a Lucene index on an existing region with data) and this will be blocked until the rolling upgrade is complete. In the code we detect that members in the cluster have different Geode versions and block adding the Lucene index until all members are at the same version. > Rolling Upgrade tests for Lucene reindex > > > Key: GEODE-5082 > URL: https://issues.apache.org/jira/browse/GEODE-5082 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Scenario 1: > Status : The system has a new member and others which do not support reindex. > Action: The Apache Geode developer tries to create the index on the new > member (supports reindex) after the region has been created. > Accepted result : An exception must be thrown preventing the creation of the > lucene index. > > Scenario 2: > Status : The system has a mix of new members and old members which do not > support Lucene reindex. > Action: The Apache Geode developer creates the region on the new member, and > then creates the Lucene index. > The old members are now rolled to the new version which supports Lucene Index. > Create lucene index first on the freshly rolled members and then create > region. > Result: This operation must be successful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5141) Add Geode version reference to LuceneIndexFactory javadocs for setLuceneSerializer method
Diane Hardman created GEODE-5141: Summary: Add Geode version reference to LuceneIndexFactory javadocs for setLuceneSerializer method Key: GEODE-5141 URL: https://issues.apache.org/jira/browse/GEODE-5141 Project: Geode Issue Type: Bug Components: lucene Reporter: Diane Hardman The setLuceneSerializer method for LuceneIndexFactory was added in Geode 1.4.0. This needs to be added to the javadocs so users know which versions support this method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4172) GEODE-4172 : [CI failure] org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest - testMatchingCQsWithMultipleServers
[
https://issues.apache.org/jira/browse/GEODE-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman resolved GEODE-4172.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> GEODE-4172 : [CI failure]
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest -
> testMatchingCQsWithMultipleServers
> -
>
> Key: GEODE-4172
> URL: https://issues.apache.org/jira/browse/GEODE-4172
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: nabarun
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Stacktrace
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest$10.run in VM 1
> running on Host 3580a85a1bde with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
> at
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest.validateMatchingCqs(CqPerfUsingPoolDUnitTest.java:952)
> at
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest.testMatchingCQsWithMultipleServers(CqPerfUsingPoolDUnitTest.java:804)
> 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.
[jira] [Created] (GEODE-5414) Create a geode-example for WAN replication
Diane Hardman created GEODE-5414: Summary: Create a geode-example for WAN replication Key: GEODE-5414 URL: https://issues.apache.org/jira/browse/GEODE-5414 Project: Geode Issue Type: Improvement Components: examples Reporter: Diane Hardman Create a simple example for implementing WAN replication between 2 Geode clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5414) Create a geode-example for WAN replication
[ https://issues.apache.org/jira/browse/GEODE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman reassigned GEODE-5414: Assignee: Diane Hardman > Create a geode-example for WAN replication > -- > > Key: GEODE-5414 > URL: https://issues.apache.org/jira/browse/GEODE-5414 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Diane Hardman >Assignee: Diane Hardman >Priority: Major > > Create a simple example for implementing WAN replication between 2 Geode > clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5421) Creating region with gateway sender immediately after creating the gateway sender in gfsh unexpectedly fails.
Diane Hardman created GEODE-5421: Summary: Creating region with gateway sender immediately after creating the gateway sender in gfsh unexpectedly fails. Key: GEODE-5421 URL: https://issues.apache.org/jira/browse/GEODE-5421 Project: Geode Issue Type: Bug Components: gfsh, wan Reporter: Diane Hardman In the attached gfsh script I am attempting to start up a single cluster that includes gateway senders and receivers on each server for the example-region. After starting the locator and 2 servers, I create the gateway receivers and senders. If I then try to create the region 'example-region' and associated it with the gateway sender, I get the following error: There are no GatewaySenders defined currently in the system. If I create the region in a different script, it works. This is unexpected and I would like to have this all in a single startup script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5421) Creating region with gateway sender immediately after creating the gateway sender in gfsh unexpectedly fails.
[ https://issues.apache.org/jira/browse/GEODE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5421: - Attachment: start-ln.gfsh > Creating region with gateway sender immediately after creating the gateway > sender in gfsh unexpectedly fails. > - > > Key: GEODE-5421 > URL: https://issues.apache.org/jira/browse/GEODE-5421 > Project: Geode > Issue Type: Bug > Components: gfsh, wan >Reporter: Diane Hardman >Priority: Major > Attachments: start-ln.gfsh > > > In the attached gfsh script I am attempting to start up a single cluster that > includes gateway senders and receivers on each server for the example-region. > After starting the locator and 2 servers, I create the gateway receivers and > senders. If I then try to create the region 'example-region' and associated > it with the gateway sender, I get the following error: > There are no GatewaySenders defined currently in the system. > If I create the region in a different script, it works. This is unexpected > and I would like to have this all in a single startup script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5421) Creating region with gateway sender immediately after creating the gateway sender in gfsh unexpectedly fails.
[ https://issues.apache.org/jira/browse/GEODE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5421: - Affects Version/s: 1.6.0 > Creating region with gateway sender immediately after creating the gateway > sender in gfsh unexpectedly fails. > - > > Key: GEODE-5421 > URL: https://issues.apache.org/jira/browse/GEODE-5421 > Project: Geode > Issue Type: Bug > Components: gfsh, wan >Affects Versions: 1.6.0 >Reporter: Diane Hardman >Priority: Major > Attachments: start-ln.gfsh > > > In the attached gfsh script I am attempting to start up a single cluster that > includes gateway senders and receivers on each server for the example-region. > After starting the locator and 2 servers, I create the gateway receivers and > senders. If I then try to create the region 'example-region' and associated > it with the gateway sender, I get the following error: > There are no GatewaySenders defined currently in the system. > If I create the region in a different script, it works. This is unexpected > and I would like to have this all in a single startup script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5414) Create a geode-example for WAN replication
[ https://issues.apache.org/jira/browse/GEODE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547235#comment-16547235 ] Diane Hardman commented on GEODE-5414: -- Initial version of this new WAN example can be found here: https://github.com/dihardman/geode-examples/tree/feature/GEODE-5414 > Create a geode-example for WAN replication > -- > > Key: GEODE-5414 > URL: https://issues.apache.org/jira/browse/GEODE-5414 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Diane Hardman >Assignee: Diane Hardman >Priority: Major > > Create a simple example for implementing WAN replication between 2 Geode > clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6800) CacheableFileName linker error
[
https://issues.apache.org/jira/browse/GEODE-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6800:
-
Fix Version/s: 1.10.0
> CacheableFileName linker error
> --
>
> Key: GEODE-6800
> URL: https://issues.apache.org/jira/browse/GEODE-6800
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Ivan Godwin
>Assignee: Ivan Godwin
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When building a program using CacheableFileName, linker errors are
> encountered. This has only been observed with certain versions of gcc and
> clang.
> {code:c++}undefined reference to `VTT for
> apache::geode::client::CacheableFileName'{code}
> Adding the ppa:ubuntu-toolchain-r/test respository to Ubuntu 16.04, GCC 5.5.0
> is installable and may be used to reproduce.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-2484) Remove ACE from native client dependencies
[ https://issues.apache.org/jira/browse/GEODE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-2484: - Fix Version/s: 1.9.0 > Remove ACE from native client dependencies > -- > > Key: GEODE-2484 > URL: https://issues.apache.org/jira/browse/GEODE-2484 > Project: Geode > Issue Type: Task > Components: native client >Reporter: David Kimura >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 10.5h > Remaining Estimate: 0h > > Remove ACE from native client dependencies. > Replace ACE usage with C++11 and/or Boost 1.63+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-3287) Remove Assert.hpp
[ https://issues.apache.org/jira/browse/GEODE-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-3287: - Fix Version/s: 1.10.0 > Remove Assert.hpp > - > > Key: GEODE-3287 > URL: https://issues.apache.org/jira/browse/GEODE-3287 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Assignee: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h > Remaining Estimate: 0h > > replace with std::assert -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-3287) Remove Assert.hpp
[ https://issues.apache.org/jira/browse/GEODE-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-3287: - Fix Version/s: (was: 1.10.0) > Remove Assert.hpp > - > > Key: GEODE-3287 > URL: https://issues.apache.org/jira/browse/GEODE-3287 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Assignee: Blake Bender >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > replace with std::assert -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-3415) Add support for certificate chain files in SSL configuration
[ https://issues.apache.org/jira/browse/GEODE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-3415: - Fix Version/s: 1.10.0 > Add support for certificate chain files in SSL configuration > > > Key: GEODE-3415 > URL: https://issues.apache.org/jira/browse/GEODE-3415 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Priority: Major > Fix For: 1.10.0 > > Time Spent: 3h > Remaining Estimate: 0h > > Native client does not support certificate chain files so certificates signed > by intermediates may not be trusted if the intermediate is not explicitly > trusted by the destination servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4339) Geode Native C++ Example (SSL example)
[ https://issues.apache.org/jira/browse/GEODE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4339: - Fix Version/s: 1.9.0 > Geode Native C++ Example (SSL example) > -- > > Key: GEODE-4339 > URL: https://issues.apache.org/jira/browse/GEODE-4339 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Assignee: Ivan Godwin >Priority: Major > Fix For: 1.9.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > This is example should show how to set up a secure connection between a > client and the cluster. The example should still have a start cluster and > build client script with instruction on how to run the client. The example > should not include its own certificates. Rather, there should be a directory > where the user can drop certs from https://letsencrypt.org/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4340) Geode Native C++ Example (Authentication)
[ https://issues.apache.org/jira/browse/GEODE-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4340: - Fix Version/s: 1.9.0 > Geode Native C++ Example (Authentication) > - > > Key: GEODE-4340 > URL: https://issues.apache.org/jira/browse/GEODE-4340 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > It's easy to get Authentication and securing a connection with SSL confused > because they almost always go hand in hand. This example shows how to require > username and password to perform actions on a specific region. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4348) Geode Native C# Example (SSL example)
[ https://issues.apache.org/jira/browse/GEODE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4348: - Fix Version/s: 1.9.0 > Geode Native C# Example (SSL example) > - > > Key: GEODE-4348 > URL: https://issues.apache.org/jira/browse/GEODE-4348 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Fix For: 1.9.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4841) Switch declaration of HashMapOfPools to 'using' in PoolManagerImpl
[ https://issues.apache.org/jira/browse/GEODE-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4841: - Fix Version/s: 1.9.0 > Switch declaration of HashMapOfPools to 'using' in PoolManagerImpl > -- > > Key: GEODE-4841 > URL: https://issues.apache.org/jira/browse/GEODE-4841 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently this is a convenience typedef in the header file, and comes with > all the associated baggage - pollutes the global namespace, etc. We should > be good C++11 citizens and remove the typedef, replacing it with a 'using' > statement at class scope closer to where we actually need the type. Or, just > declare variables of this type as 'auto' in PoolManagerImpl, even more > convenient. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-5708) Memory corruption in c++ client
[ https://issues.apache.org/jira/browse/GEODE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5708: - Fix Version/s: 1.9.0 > Memory corruption in c++ client > --- > > Key: GEODE-5708 > URL: https://issues.apache.org/jira/browse/GEODE-5708 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jorge Perez Burgos >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Attachments: > fix-memory-allocation-d0ff5d7e393f17955f54d3fe0bdf2694c78e9a7e.patch > > Time Spent: 50m > Remaining Estimate: 0h > > When using partition regions there is a double free the ends corrupting the > client process. This is caused because instead of assigning shared pointers > directly the content of a shared pointer is assign to another shared pointer > so the reference count is messed up. I attach a tentative fix/workaround that > copies the content although the best option is possibly to create a new or > modify a constructor in VersionedCacheableObjectPartList class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-5957) Unexpected exception when executing an unknown function.
[ https://issues.apache.org/jira/browse/GEODE-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5957: - Fix Version/s: 1.9.0 > Unexpected exception when executing an unknown function. > > > Key: GEODE-5957 > URL: https://issues.apache.org/jira/browse/GEODE-5957 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::MessageException: : message from server could not be > handled -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6007) Fix LGTM complaints in NC code base
[ https://issues.apache.org/jira/browse/GEODE-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6007: - Fix Version/s: 1.11.0 > Fix LGTM complaints in NC code base > --- > > Key: GEODE-6007 > URL: https://issues.apache.org/jira/browse/GEODE-6007 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 2h > Remaining Estimate: 0h > > This is showing stuff that is bad practice in general, and may open us up to > maliciousness. There are two main situations in which we find lots of usage > of snprintf with raw char buffers, which are: > * formatting messages for exceptions > * formatting messages for logging > For the exception messages, we should switch to something known to be safe - > a vsxprintf implementation, boost::format, std::stringstream, whatever. As > long as we stop declaring raw char buffers on the stack, it's all good > > For logging, the situation is even dumber. The various LOG* macros in the > code _already_ take a format string and varargs, so as far as I know we > essentially need to move the printf-style arguments into the logging macro > and get rid of the other nonsense. We may even buy a tiny performance > improvement due to the fact that that logging macros can be compiled out of > the code. > > UPDATE: Report from running LGTM on our code may be found at > [https://lgtm.com/projects/g/apache/geode-native/alerts/?mode=list.] This > report has issues with tons of printf-style format specifiers, so it catches > most of the snprintf stuff pointed out above. MANY OF THESE ARE BUFFER > OVERFLOW ISSUES, and must be addressed in the name of security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6054) Make geode-native build with VS 2017 runtime
[ https://issues.apache.org/jira/browse/GEODE-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6054: - Fix Version/s: 1.9.0 > Make geode-native build with VS 2017 runtime > > > Key: GEODE-6054 > URL: https://issues.apache.org/jira/browse/GEODE-6054 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 5h > Remaining Estimate: 0h > > Just need to configure cmake locally with VS 2017 runtime, build and run > tests and make sure everything is copacetic. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6114) C++ examples can't be built individually if they need a jar file
[ https://issues.apache.org/jira/browse/GEODE-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6114: - Fix Version/s: 1.9.0 > C++ examples can't be built individually if they need a jar file > > > Key: GEODE-6114 > URL: https://issues.apache.org/jira/browse/GEODE-6114 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Our documentation says to cd into the individual example directory, aka > cpp/<>, and run cmake commands from there to build. If you do > this for an example that requires example.jar, the utilities directory is not > built, so there is no jar file to deploy, thus you can't run the example. If > an example requires example.jar, it needs to ensure the utilities directory > is built in its CMakeLists.txt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6139) Fix rat complaints about files for 1.8 release
[ https://issues.apache.org/jira/browse/GEODE-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6139: - Fix Version/s: 1.9.0 > Fix rat complaints about files for 1.8 release > -- > > Key: GEODE-6139 > URL: https://issues.apache.org/jira/browse/GEODE-6139 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Rat is griping about the missing license headers in a few of the source > files, so these need to be added. It's also complaining about a few config > files which do NOT need license headers, so these need to be added to > .ratignore. We also saw some leftover stuff in a cmake-build-debug folder, > so we need to make sure the directory is git cleaned before the release > manager runs cpack. Lastly, one file was mysteriously absent from the > documentation in the final package, so we need to verify that this was > spurious or get the file properly added. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6165) Need a workaround to install Doxygen on Windows AMI
[ https://issues.apache.org/jira/browse/GEODE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6165: - Fix Version/s: 1.9.0 > Need a workaround to install Doxygen on Windows AMI > --- > > Key: GEODE-6165 > URL: https://issues.apache.org/jira/browse/GEODE-6165 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Our install-dependencies.ps1 script that runs when we create a Windows build > image is failing because the underlying URL for the Doxygen Chocolatey > installer has gone bad, and the Chocolatey package isn't being actively > updated. Until the package is fixed, we need a way to install Doxygen on our > AMIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6160) CPack ignore syntax isn't properly escaped
[
https://issues.apache.org/jira/browse/GEODE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6160:
-
Fix Version/s: 1.9.0
> CPack ignore syntax isn't properly escaped
> --
>
> Key: GEODE-6160
> URL: https://issues.apache.org/jira/browse/GEODE-6160
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In our .cpackignore file, we have lines of the form "\.foo", for example, but
> the regex syntax also has to be escaped like a C string for some reason, aka "
> .foo".
>
> Repro steps:
> * Configure using cmake in a clean repo
> * cd into cmake build dir
> * run 'cpack -G TGZ ---config CPackSourceConfig.cmake' to generate a source
> package
> Expected result
> * Source package generated without complaints
> Actual result
> * Source package generated
> * cpack complains about syntax, for example:
> {code:java}
> CMake Warning (dev) at
> /Users/pivotal/Workspace/cmake-build-debug/geode-native/CPackSourceConfig.cmake:74
> (set):
> Syntax error in cmake code at
>
>
> /Users/pivotal/Workspace/cmake-build-debug/geode-native/CPackSourceConfig.cmake:74
>
> when parsing string
>
>
> /\.git/;/\.DS_Store;/build-./;/build/;/\.settings/;/\.cproject;/\.project;/\.idea/;\.vs/;\.vscode/;/examples/dotnet/./bin/;/examples/dotnet/.*/obj/;\.ruby-version
>
> Invalid escape sequence \.
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6211) Geode Native C# Example (Exception Handling)
[ https://issues.apache.org/jira/browse/GEODE-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6211: - Fix Version/s: 1.9.0 > Geode Native C# Example (Exception Handling) > > > Key: GEODE-6211 > URL: https://issues.apache.org/jira/browse/GEODE-6211 > Project: Geode > Issue Type: Sub-task > Components: examples, native client >Reporter: Charlie Black >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > As a user, I would like to see an example of how to handle a common exception > thrown by Geode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6199) Remove pdxautoserializer from contrib
[ https://issues.apache.org/jira/browse/GEODE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6199: - Fix Version/s: 1.9.0 > Remove pdxautoserializer from contrib > - > > Key: GEODE-6199 > URL: https://issues.apache.org/jira/browse/GEODE-6199 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This code was moved to contrib in preparation for removal, and no longer > compiles. Time to get rid of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6210) Geode Native C++ Example (Transaction with Retry)
[ https://issues.apache.org/jira/browse/GEODE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6210: - Fix Version/s: 1.9.0 > Geode Native C++ Example (Transaction with Retry) > - > > Key: GEODE-6210 > URL: https://issues.apache.org/jira/browse/GEODE-6210 > Project: Geode > Issue Type: Sub-task > Components: examples, native client >Reporter: Charlie Black >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > As an end user, I would like to see an example of how to handle a common > exception thrown by Geode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6226) The release file naming should be congruent with core
[
https://issues.apache.org/jira/browse/GEODE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6226:
-
Fix Version/s: 1.9.0
> The release file naming should be congruent with core
> -
>
> Key: GEODE-6226
> URL: https://issues.apache.org/jira/browse/GEODE-6226
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Charlie Black
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the release file naming it looks like we are not in compliance with the
> core.
> {{
> apache-geode-1.8.0-src.tgz
> apache-geode-1.8.0-src.tgz.asc
> apache-geode-1.8.0-src.tgz.sha256
> apache-geode-1.8.0.tgz
> apache-geode-1.8.0.tgz.asc
> apache-geode-1.8.0.tgz.sha256
> apache-geode-examples-1.8.0.tar.gz
> apache-geode-examples-1.8.0.tar.gz.asc
> apache-geode-examples-1.8.0.tar.gz.sha256
> apache-geode-examples-1.8.0.zip
> apache-geode-examples-1.8.0.zip.asc
> apache-geode-examples-1.8.0.zip.sha256
> apache-geode-native-1.8.0-Source.tar.gz
> apache-geode-native-1.8.0-Source.tar.gz.asc
> apache-geode-native-1.8.0-Source.tar.gz.sha512}}
> In this example, we would need to change "Source" to src. Also any reason we
> are 512 and the core is 256 if there isn't a reason make the sha the same
> number of bits.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6240) Fix rat complaints
[
https://issues.apache.org/jira/browse/GEODE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6240:
-
Fix Version/s: 1.9.0
> Fix rat complaints
> --
>
> Key: GEODE-6240
> URL: https://issues.apache.org/jira/browse/GEODE-6240
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{packer/ubuntu/files/etc/systemd/system/update-hosts.service}} and
> {{packer/ubuntu/files/usr/local/bin/update-hosts.sh}} are missing licenses
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6229) Need an Ubuntu Packer image
[ https://issues.apache.org/jira/browse/GEODE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6229: - Fix Version/s: 1.9.0 > Need an Ubuntu Packer image > --- > > Key: GEODE-6229 > URL: https://issues.apache.org/jira/browse/GEODE-6229 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h > Remaining Estimate: 0h > > As a user of NC, I need to be able to build/run on Ubuntu in addition to > RedHat. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6249) Port AttributesMutator test to new framework
[ https://issues.apache.org/jira/browse/GEODE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6249: - Fix Version/s: 1.9.0 > Port AttributesMutator test to new framework > > > Key: GEODE-6249 > URL: https://issues.apache.org/jira/browse/GEODE-6249 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 2h > Remaining Estimate: 0h > > As a developer on NC, I would very much like to be able to debug my > integration tests in an IDE. As a matter of course we're going to port all > existing tests to the new framework and delete the old code. The new > framework is simpler and uses gtest, so we can debug it in the CLion IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6245) Fix microsoft specific pragma compiler warnings.
[ https://issues.apache.org/jira/browse/GEODE-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6245: - Fix Version/s: 1.9.0 > Fix microsoft specific pragma compiler warnings. > > > Key: GEODE-6245 > URL: https://issues.apache.org/jira/browse/GEODE-6245 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6250) Port testCache tests to new integration framework
[ https://issues.apache.org/jira/browse/GEODE-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6250: - Fix Version/s: 1.9.0 > Port testCache tests to new integration framework > - > > Key: GEODE-6250 > URL: https://issues.apache.org/jira/browse/GEODE-6250 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > As a developer on NC, I would very much like to be able to debug my > integration tests in an IDE. As a matter of course we're going to port all > existing tests to the new framework and delete the old code. The new > framework is simpler and uses gtest, so we can debug it in the CLion IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6262) Cppcache Unit Tests Don't Support Multiple Iterations
[ https://issues.apache.org/jira/browse/GEODE-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6262: - Fix Version/s: 1.9.0 > Cppcache Unit Tests Don't Support Multiple Iterations > - > > Key: GEODE-6262 > URL: https://issues.apache.org/jira/browse/GEODE-6262 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > TcrMessageTest uses some funky macros to create compare strings for gtest > EXPECT_MESSAGE. The compare strings don't work when multiple iterations of > the tests, the sequence number causes overflow of the field. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6300) Assertion in CLI tests re: bad AppDomain
[
https://issues.apache.org/jira/browse/GEODE-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6300:
-
Fix Version/s: 1.9.0
> Assertion in CLI tests re: bad AppDomain
>
>
> Key: GEODE-6300
> URL: https://issues.apache.org/jira/browse/GEODE-6300
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> From the ci logs
> (http://concourse-nativeclient.gemfire.pivotal.io/teams/main/pipelines/build-develop/jobs/cli-test-windows-debug/builds/64):
>
> System.ArgumentException: Cannot pass a GCHandle across AppDomains.
> Parameter name: handle
> at System.Runtime.InteropServices.GCHandle.InternalCheckDomain(IntPtr handle)
> at System.Runtime.InteropServices.GCHandle.FromIntPtr(IntPtr value)
> at gcroot ^>.\{dtor}(gcroot* )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.\{dtor}(ManagedDataSerializablePrimitive*
> )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.__vbaseDtor(ManagedDataSerializablePrimitive*
> )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.__vecDelDtor(ManagedDataSerializablePrimitive*
> , UInt32 A_0)
> at
> std._Ref_count._Destroy(_Ref_count*
> )
> errorlevel 0
> + exitcode=1
> + echo exitcode=1
> exitcode=1
> + exit 1
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6469) Remove cryptoimpl.lib from nativeclient release
[ https://issues.apache.org/jira/browse/GEODE-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6469: - Fix Version/s: 1.9.0 > Remove cryptoimpl.lib from nativeclient release > --- > > Key: GEODE-6469 > URL: https://issues.apache.org/jira/browse/GEODE-6469 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We build and ship a sample SSL encryption library called cryptoimpl, which is > a dependency of the nativeclient. On Windows, our install currently includes > the cryptoimpl.dll and cryptoimpl.lib. The cryptoimpl.lib is an import > library and should not be part of the release artifacts -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6491) Can't Run ASP.NET apps that use geode-native with authentication
[ https://issues.apache.org/jira/browse/GEODE-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6491: - Fix Version/s: 1.9.0 > Can't Run ASP.NET apps that use geode-native with authentication > > > Key: GEODE-6491 > URL: https://issues.apache.org/jira/browse/GEODE-6491 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > If authentication is not used, ASP.NET apps that use geode-native work just > fine. However, when we run such apps using geode-native with authentication, > a .NET System.ArgumentException is thrown with this message: "Can't pass > GCHandle across appDomains". > > This is being marked as a Major bug, since to run apps in Pivotal Cloud > Foundry requires using authentication. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6507) Move all clangformat projects into subfolder
[ https://issues.apache.org/jira/browse/GEODE-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6507: - Fix Version/s: 1.9.0 > Move all clangformat projects into subfolder > > > Key: GEODE-6507 > URL: https://issues.apache.org/jira/browse/GEODE-6507 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Improve readability of the solution by moving all clangformat projects into a > clangformat subdir. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6538) Update Geode Native docs for v1.9
[ https://issues.apache.org/jira/browse/GEODE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6538: - Fix Version/s: 1.9.0 > Update Geode Native docs for v1.9 > - > > Key: GEODE-6538 > URL: https://issues.apache.org/jira/browse/GEODE-6538 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update the version number in doc sources for the geode-native user guide -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6547) Geode-Native User Guide - document 'sslputget' example
[ https://issues.apache.org/jira/browse/GEODE-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6547: - Fix Version/s: 1.9.0 > Geode-Native User Guide - document 'sslputget' example > -- > > Key: GEODE-6547 > URL: https://issues.apache.org/jira/browse/GEODE-6547 > Project: Geode > Issue Type: Sub-task > Components: docs, native client >Reporter: Dave Barnes >Priority: Major > Fix For: 1.9.0 > > > Document the 'sslputget' example. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6567) Geode native doesn't compile with gcc 8.x
[ https://issues.apache.org/jira/browse/GEODE-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6567: - Fix Version/s: 1.9.0 > Geode native doesn't compile with gcc 8.x > - > > Key: GEODE-6567 > URL: https://issues.apache.org/jira/browse/GEODE-6567 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jorge Perez Burgos >Priority: Minor > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Geode driver cannot compile with gcc 8.x due to several warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6575) Windows configuration 'RelWithDebInfo' doesn't build properly
[ https://issues.apache.org/jira/browse/GEODE-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6575: - Fix Version/s: 1.9.0 > Windows configuration 'RelWithDebInfo' doesn't build properly > - > > Key: GEODE-6575 > URL: https://issues.apache.org/jira/browse/GEODE-6575 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Several .net projects in the tree don't currently have this configuration, so > we need to add them. Going forward it's going to be critical to be able to > generate optimized Windows builds with debug symbols. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6597) ClientMetaDataService Causes Can't Pass GCHandle Across AppDomains Error
[ https://issues.apache.org/jira/browse/GEODE-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6597: - Fix Version/s: 1.9.0 > ClientMetaDataService Causes Can't Pass GCHandle Across AppDomains Error > > > Key: GEODE-6597 > URL: https://issues.apache.org/jira/browse/GEODE-6597 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Background thread used by ClientMetaDataService is used to update the native > client's meta. This thread was missed in the fix for solving appdomain > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6624) SIGABRT Due to nested exceptions when value returned that can't be deserialized
[ https://issues.apache.org/jira/browse/GEODE-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6624: - Fix Version/s: 1.10.0 > SIGABRT Due to nested exceptions when value returned that can't be > deserialized > --- > > Key: GEODE-6624 > URL: https://issues.apache.org/jira/browse/GEODE-6624 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > This gets a little weird, but in a nutshell: > * a client app needs to deploy a jar file containing a custom > DataSerializable object _without_ a default constructor, and a server > function that returns a value of this type > * Then, the app needs to call execute on a function service on a region (or > maybe a server, we're not sure it's relevant) to call the function that > returns the value of the class that's missing the default dtor > * In response, the server will send back a payload with dscode=45 > (DataSerializable), then a byte field for the type, which will be set to > dscode 43 (Class), then a string which is the name of the class, then the > bytes resulting from a call to toData() on that class instance > * The native client cannot correctly interpret this message, so the worker > thread that is trying to decode the message stores an exception to throw > later. > * Later on in the main thread, an exception gets thrown in > TcrMessage::readMessageChunked, but on the way out of readMessageChunked the > dtor for the contained FinalizeProcessChunk object gets called, which calls > m_reply.processChunk, which _also_ throws an exception, at which point the > process aborts because of the nested exceptions > We need to eat the 2nd exception, and throw the 1st, so that client apps can > catch the exception _and_ get an accurate message about what went wrong. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6642) CacheAttributes header was left in the public header collection
[
https://issues.apache.org/jira/browse/GEODE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6642:
-
Fix Version/s: 1.10.0
> CacheAttributes header was left in the public header collection
> ---
>
> Key: GEODE-6642
> URL: https://issues.apache.org/jira/browse/GEODE-6642
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.8.0
>Reporter: Jacob Barrett
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{CacheAttributes}} is not longer necessary and was inadvertently left in the
> public headers. The factory, {{CacheAttributesFactory}} was removed prior to
> the first release. All public APIs using {{CacheAttributes}} were removed
> prior to the first release.
> It should be safe to remove the header completely and cleanup internal usage
> of this class without effecting the public API and ABI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
