[jira] [Commented] (GEODE-4322) Locator fails to start with NPE during join to the distributed system
[ https://issues.apache.org/jira/browse/GEODE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335448#comment-16335448 ] Vahram Aharonyan commented on GEODE-4322: - Hi [~bschuchardt], Unfortunately we don't have a way to quickly test this with Geode 1.3. We have setups only with 1.1.0 and 1.2.0. Do you know what is the status of the test mentioned in GEODE-2542 in case of GEODE 1.3 branch? I see that stacktraces from fails are pretty similar to what we are observing. Thanks, Vahram. > Locator fails to start with NPE during join to the distributed system > - > > Key: GEODE-4322 > URL: https://issues.apache.org/jira/browse/GEODE-4322 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.2.0 >Reporter: Vahram Aharonyan >Assignee: Bruce Schuchardt >Priority: Major > > Found out that after setting security-udp-dhalgo=AES:128 in prorperties files > sometimes locator is failing to come online with the following Exception: > [severe 2018/01/19 04:22:12.194 PST tid=0x45] > Exception in processing request from 10.144.248.41 > java.lang.RuntimeException: Not found public key for member > 16nodedata6(d4b4f5d4-47d2-44b1-a07c-6a7f5755e52d:11493):10002 > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:177) > at > org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.getPublicKey(JGroupsMessenger.java:1365) > at > org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:271) > at > org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1256) > at > org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:401) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.NullPointerException > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258) > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175) > ... 7 more > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.NullPointerException > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258) > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175) > ... 7 more > Please note, that generally this issue is hit after cluster restart. This is > important, as during poweroff locator can go offline first and one of other > members will become coordinator and update view file accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3391) eval shared_ptr usage in CacheListener/CacheLoader/CacheTransactionMgr/CacheWriter
[ https://issues.apache.org/jira/browse/GEODE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison resolved GEODE-3391. Resolution: Done > eval shared_ptr usage in > CacheListener/CacheLoader/CacheTransactionMgr/CacheWriter > -- > > Key: GEODE-3391 > URL: https://issues.apache.org/jira/browse/GEODE-3391 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > evaluate shared_ptr usage and change to reference > virtual void afterRegionDisconnected(Region& region) > virtual CacheablePtr load(Region& rp, const CacheableKeyPtr& key, > const UserDataPtr& aCallbackArgument) = 0; > virtual void close(Region& rp); > virtual void resume(const TransactionId& transactionId) > virtual const TransactionId& getTransactionId() = 0; > virtual void close(Region& rp); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4315) Convert JSONWrapper to an interface
[ https://issues.apache.org/jira/browse/GEODE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335299#comment-16335299 ] ASF subversion and git services commented on GEODE-4315: Commit aabad5f895f67c9432e2e4da0518346687188bad in geode's branch refs/heads/feature/GEODE-3967 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=aabad5f ] GEODE-4315 Convert JSONWrapper to an interface JSONWrapper is now an interface. JSONWrapperImpl is what will be returned by the experimental driver but it will accept anything implementing JSONWrapper as input. > Convert JSONWrapper to an interface > --- > > Key: GEODE-4315 > URL: https://issues.apache.org/jira/browse/GEODE-4315 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.5.0 > > > The experimental Protobuf driver has a JSONWrapper class to hold JSON > documents. It would be nice if this can be changed to be an interface so > that I can write my own wrapper. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4332) Gfsh start locator should not retrieve cluster status when --connect=false
[
https://issues.apache.org/jira/browse/GEODE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335292#comment-16335292
]
ASF subversion and git services commented on GEODE-4332:
Commit 8d0224742c5308a13df0e2e344df9e6f9ed2ea94 in geode's branch
refs/heads/feature/GEODE-3967 from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8d02247 ]
GEODE-4332: Gfsh start locator should not retrieve cluster status when
--connect=false (#1315)
> Gfsh start locator should not retrieve cluster status when --connect=false
> --
>
> Key: GEODE-4332
> URL: https://issues.apache.org/jira/browse/GEODE-4332
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
> Fix For: 1.5.0
>
>
> When user starts locator with --connect=false, it should not retrieve
> cluster-configuration service status.
> {noformat}
> gfsh>start locator --name=locator1 --connect=false
> Starting a Geode Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1...
> ...
> Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1 on
> 10.118.19.26[10334] as locator1 is currently online.
> Process ID: 21762
> Uptime: 2 seconds
> Geode Version: 1.5.0-SNAPSHOT
> Java Version: 1.8.0_151
> Log File:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-core-1.5.0-SNAPSHOT.jar:/Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-dependencies.jar
> Cluster configuration service is up and running.{noformat}
> As you can see that it retrieves the status and displays cluster
> configuration service is running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4138) Skipped DistributedTest ShutdownCommandDUnitTest fails over http
[
https://issues.apache.org/jira/browse/GEODE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335296#comment-16335296
]
ASF subversion and git services commented on GEODE-4138:
Commit 051349b0992cd374bb6e3323d625812ca2deb709 in geode's branch
refs/heads/feature/GEODE-3967 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=051349b ]
GEODE-4138: Move http related test to geode-web (#1320)
> Skipped DistributedTest ShutdownCommandDUnitTest fails over http
>
>
> Key: GEODE-4138
> URL: https://issues.apache.org/jira/browse/GEODE-4138
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, tests
>Reporter: Patrick Rhomberg
>Assignee: Jens Deppe
>Priority: Major
>
> Test fails in {{gfsh.connectAndVerify}} dependent on environment. Similar to
> GEODE-4136.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335295#comment-16335295 ] ASF subversion and git services commented on GEODE-3554: Commit ec53f620359f85b4d3c0063b34ec5911e84c50c9 in geode's branch refs/heads/feature/GEODE-3967 from [~agingade] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ec53f62 ] GEODE-3554: Add additional javadoc about how to get Cache. > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > Fix For: 1.5.0 > > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4306) TTL (time to live) expiration not working properly in client side
[ https://issues.apache.org/jira/browse/GEODE-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335298#comment-16335298 ] ASF subversion and git services commented on GEODE-4306: Commit ea7721613a4d3ccde904a3ad820ecd2b4f9f5527 in geode's branch refs/heads/feature/GEODE-3967 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ea77216 ] GEODE-4306: Added concurrent checks enabled test to event time > TTL (time to live) expiration not working properly in client side > - > > Key: GEODE-4306 > URL: https://issues.apache.org/jira/browse/GEODE-4306 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4015) CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335291#comment-16335291
]
ASF subversion and git services commented on GEODE-4015:
Commit b690cfad68c95e60b237ebc9d316420be692998d in geode's branch
refs/heads/feature/GEODE-3967 from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b690cfa ]
GEODE-4015: Rewrite queue conflation tests (#1312)
* Refactored HARegionQueue to allow unit testing
> CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with
> AssertionError
> --
>
> Key: GEODE-4015
> URL: https://issues.apache.org/jira/browse/GEODE-4015
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
>
> Both testTwoRegionsTwoWriters and testTwoRegionsOneWriter failed with the
> same AssertionError:
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsTwoWriters FAILED
> java.lang.AssertionError: Test failed due to exception
> at org.apache.geode.test.dunit.Assert.fail(Assert.java:66)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:155)
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$193/1316585270.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:153)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms:
> null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsTwoWriters$bb17a952$10(ConflationDUnitTest.java:153)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsOneWriter FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$221/1553950035.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsOneWriter(ConflationDUnitTest.java:183)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms: null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsOneWriter$bb17a952$10(ConflationDUnitTest.java:183)
> {noformat}
> ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506) is
> waiting for {{counterUpdate == 2}}.
> I think this is a timing issue. The first line of the test sets
> CacheClientProxy.isSlowStartForTesting to true. This causes the
> MessageDispatcher to not send messages immediately. Instead, it waits for 5
> seconds before sending. This allows the queue to conflate the events. If I
> remove the slow start setting, the test fails every time because conflation
> doesn't happen.
> Unfortunately, the description returns null (the null in the AssertionError
> messages above), so we don't know anything about why the assertion is
> failing. If it were changed to return the actual value of counterUpdate, that
> would be helpful.
> With that change and the boolean not set in the test, I see:
> {noformat}
> Caused by: java.lang.AssertionError: Event never occurred after 6 ms:
> Expected counterUpdate to be 2. Instead it was 6
> {noformat}
> My guess is that between the time the MessageDispatcher is told to wait and
> the test actually runs, at least 5 seconds elapses, and the conflation
>
[jira] [Commented] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335294#comment-16335294 ] ASF subversion and git services commented on GEODE-3554: Commit 7fc5d6e93c66f3a3b0bd4a4cfec5f9a5c20425d2 in geode's branch refs/heads/feature/GEODE-3967 from [~agingade] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7fc5d6e ] GEODE-3554: Add javadoc warning about getAnyInstance in CacheCallback > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > Fix For: 1.5.0 > > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4136) Skipped IntegrationTest QueryCommandTest fails under HTTP
[
https://issues.apache.org/jira/browse/GEODE-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335297#comment-16335297
]
ASF subversion and git services commented on GEODE-4136:
Commit 4d829959d435740fb06f88f3b186290da328a803 in geode's branch
refs/heads/feature/GEODE-3967 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4d82995 ]
GEODE-4136: Move http related test to geode-web (#1319)
> Skipped IntegrationTest QueryCommandTest fails under HTTP
> -
>
> Key: GEODE-4136
> URL: https://issues.apache.org/jira/browse/GEODE-4136
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Jens Deppe
>Priority: Major
>
> These tests can fail at {{gfsh.connectAndVerify}}, dependent on testing
> environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4333) AbstractRegionMap destroy needs unit tests
[ https://issues.apache.org/jira/browse/GEODE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335293#comment-16335293 ] ASF subversion and git services commented on GEODE-4333: Commit 4f0c0b1f32d86aad4595c33c679e20799c5dbaeb in geode's branch refs/heads/feature/GEODE-3967 from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f0c0b1 ] GEODE-4333: add unit tests for AbstractRegionMap.destroy (#1314) > AbstractRegionMap destroy needs unit tests > -- > > Key: GEODE-4333 > URL: https://issues.apache.org/jira/browse/GEODE-4333 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.5.0 > > > The destroy method on AbstractRegionMap needs unit test coverage. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3967) if put hits concurrent modification exception should still notify serial gateway sender
[ https://issues.apache.org/jira/browse/GEODE-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335283#comment-16335283 ] ASF subversion and git services commented on GEODE-3967: Commit ece79d0bdda2dc221f5d8a5de00bf637c8c89ca2 in geode's branch refs/heads/feature/GEODE-3967 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ece79d0 ] GEODE-3967: when ConcurrentCacheModificationException happened. GatewaySenderEventImpl should save the status and notify gatewaysender anyway. SerialGatewaySender will handle it. In AbstractUpdateOperation's doPutOrCreate's 3 tries of basicUpdate, the 3rd one should allow both create and update. > if put hits concurrent modification exception should still notify serial > gateway sender > --- > > Key: GEODE-3967 > URL: https://issues.apache.org/jira/browse/GEODE-3967 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > > In serial gateway sender, the event arrives at secondary will be put into > unprocessedMap and wait for event from primary queue to distribute over, then > remove it from the unprocessedMap. > If the put at primary member (member with primary queue) failed with CME, the > event in unprocessedMap will never be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4358) If internalDestory is called on a QueueConnectionImpl followed by internalClose, an NPE will occur
[
https://issues.apache.org/jira/browse/GEODE-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335264#comment-16335264
]
ASF subversion and git services commented on GEODE-4358:
Commit 9e0f248312e91538612ff9fabbf3c66e61bc80e6 in geode's branch
refs/heads/feature/GEODE-4358 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9e0f248 ]
GEODE-4358: Added check for null updater
> If internalDestory is called on a QueueConnectionImpl followed by
> internalClose, an NPE will occur
> --
>
> Key: GEODE-4358
> URL: https://issues.apache.org/jira/browse/GEODE-4358
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
>
> {{QueueConnectionImpl internalDestroy}} sets {{updater = null}}, but
> {{internalClose}} does not check for null before attempting to call {{close}}
> on the updater.
> A warning like below occurs in this case:
> {noformat}
> [warning 2017/05/30 20:13:55.512 PDT
> edgegemfire5_rs-qnqTesting-client-7_27065 tid=0xc3]
> Error destroying client to server connection to rs-qnqTesting-client-7:20606
> java.lang.NullPointerException
> at
> org.apache.geode.cache.client.internal.QueueConnectionImpl.internalClose(QueueConnectionImpl.java:76)
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.addToConnectionList(QueueManagerImpl.java:1031)
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.recoverPrimary(QueueManagerImpl.java:897)
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl$RedundancySatisfierTask.run2(QueueManagerImpl.java:1467)
> at
> org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1315)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4306) TTL (time to live) expiration not working properly in client side
[ https://issues.apache.org/jira/browse/GEODE-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335217#comment-16335217 ] ASF subversion and git services commented on GEODE-4306: Commit ea7721613a4d3ccde904a3ad820ecd2b4f9f5527 in geode's branch refs/heads/feature/GEODE-4142 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ea77216 ] GEODE-4306: Added concurrent checks enabled test to event time > TTL (time to live) expiration not working properly in client side > - > > Key: GEODE-4306 > URL: https://issues.apache.org/jira/browse/GEODE-4306 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4315) Convert JSONWrapper to an interface
[ https://issues.apache.org/jira/browse/GEODE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335218#comment-16335218 ] ASF subversion and git services commented on GEODE-4315: Commit aabad5f895f67c9432e2e4da0518346687188bad in geode's branch refs/heads/feature/GEODE-4142 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=aabad5f ] GEODE-4315 Convert JSONWrapper to an interface JSONWrapper is now an interface. JSONWrapperImpl is what will be returned by the experimental driver but it will accept anything implementing JSONWrapper as input. > Convert JSONWrapper to an interface > --- > > Key: GEODE-4315 > URL: https://issues.apache.org/jira/browse/GEODE-4315 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.5.0 > > > The experimental Protobuf driver has a JSONWrapper class to hold JSON > documents. It would be nice if this can be changed to be an interface so > that I can write my own wrapper. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4322) Locator fails to start with NPE during join to the distributed system
[ https://issues.apache.org/jira/browse/GEODE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335204#comment-16335204 ] Bruce Schuchardt commented on GEODE-4322: - Hi [~vaharonyan], have you tested with Geode 1.3? The NPE occurred when the locator was processing a "find coordinator" request during restart. A lot of the code concerning that processing was revised in 1.3 and I'd like to know if the problem still existed after those changes. > Locator fails to start with NPE during join to the distributed system > - > > Key: GEODE-4322 > URL: https://issues.apache.org/jira/browse/GEODE-4322 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.2.0 >Reporter: Vahram Aharonyan >Assignee: Bruce Schuchardt >Priority: Major > > Found out that after setting security-udp-dhalgo=AES:128 in prorperties files > sometimes locator is failing to come online with the following Exception: > [severe 2018/01/19 04:22:12.194 PST tid=0x45] > Exception in processing request from 10.144.248.41 > java.lang.RuntimeException: Not found public key for member > 16nodedata6(d4b4f5d4-47d2-44b1-a07c-6a7f5755e52d:11493):10002 > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:177) > at > org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.getPublicKey(JGroupsMessenger.java:1365) > at > org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:271) > at > org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1256) > at > org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:401) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.NullPointerException > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258) > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175) > ... 7 more > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.NullPointerException > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258) > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175) > ... 7 more > Please note, that generally this issue is hit after cluster restart. This is > important, as during poweroff locator can go offline first and one of other > members will become coordinator and update view file accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4359) Remove std::enable_shared_from_this from PdxSerializable
Jacob S. Barrett created GEODE-4359: --- Summary: Remove std::enable_shared_from_this from PdxSerializable Key: GEODE-4359 URL: https://issues.apache.org/jira/browse/GEODE-4359 Project: Geode Issue Type: Improvement Components: native client Reporter: Jacob S. Barrett Internal serialization behavior requires that PdxSerializable classes extend std::enable_shared_from_this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3138) Add function execution on Region to new protocol
[ https://issues.apache.org/jira/browse/GEODE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan reassigned GEODE-3138: --- Assignee: Galen O'Sullivan Description: As a Geode user, I want to be able to call server-side functions on a Region. this should include parameters and handle function execution exceptions and error cases. (was: As a Geode user, I want to be able to call server-side functions with parameters (such as a Region name to run a function against). Expand function execution to include functions with parameters.) > Add function execution on Region to new protocol > > > Key: GEODE-3138 > URL: https://issues.apache.org/jira/browse/GEODE-3138 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Assignee: Galen O'Sullivan >Priority: Major > > As a Geode user, I want to be able to call server-side functions on a Region. > this should include parameters and handle function execution exceptions and > error cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-3138) Add function execution on Region to new protocol
[ https://issues.apache.org/jira/browse/GEODE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan reopened GEODE-3138: - Changing to be execution on a Region, since that's really what should come first. > Add function execution on Region to new protocol > > > Key: GEODE-3138 > URL: https://issues.apache.org/jira/browse/GEODE-3138 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Assignee: Galen O'Sullivan >Priority: Major > > As a Geode user, I want to be able to call server-side functions on a Region. > this should include parameters and handle function execution exceptions and > error cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3138) Add function execution on Region to new protocol
[ https://issues.apache.org/jira/browse/GEODE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Galen O'Sullivan updated GEODE-3138: Summary: Add function execution on Region to new protocol (was: Add function execution *with parameters* to new protocol) > Add function execution on Region to new protocol > > > Key: GEODE-3138 > URL: https://issues.apache.org/jira/browse/GEODE-3138 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Priority: Major > > As a Geode user, I want to be able to call server-side functions with > parameters (such as a Region name to run a function against). > Expand function execution to include functions with parameters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4358) If internalDestory is called on a QueueConnectionImpl followed by internalClose, an NPE will occur
Barry Oglesby created GEODE-4358:
Summary: If internalDestory is called on a QueueConnectionImpl
followed by internalClose, an NPE will occur
Key: GEODE-4358
URL: https://issues.apache.org/jira/browse/GEODE-4358
Project: Geode
Issue Type: Bug
Components: client queues
Reporter: Barry Oglesby
{\{QueueConnectionImpl internalDestroy}} sets \{{updater = null}}, but
\{{internalClose}} does not check for null before attempting call \{{close}} on
the updater.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4350) Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
[
https://issues.apache.org/jira/browse/GEODE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett resolved GEODE-4350.
-
Resolution: Fixed
> Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
> ---
>
> Key: GEODE-4350
> URL: https://issues.apache.org/jira/browse/GEODE-4350
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>
> {{overrides a member function but is not marked 'override'}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4350) Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
[
https://issues.apache.org/jira/browse/GEODE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335088#comment-16335088
]
ASF subversion and git services commented on GEODE-4350:
Commit 1c0c819abdf38d47f7e3e8b6ac9aaa4e009a9f94 in geode-native's branch
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=1c0c819 ]
GEODE-4350: Adds override qualifier to listener methods.
> Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
> ---
>
> Key: GEODE-4350
> URL: https://issues.apache.org/jira/browse/GEODE-4350
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>
> {{overrides a member function but is not marked 'override'}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4282) createKey, createValue functions missing for many Serializable types.
[ https://issues.apache.org/jira/browse/GEODE-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-4282. - Resolution: Fixed > createKey, createValue functions missing for many Serializable types. > - > > Key: GEODE-4282 > URL: https://issues.apache.org/jira/browse/GEODE-4282 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > Serializable/CacheableKey::create method needs namespace functions > createValue/createKey for each of the supported primitive types. Many of > these types are missing as a result of bad refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4332) Gfsh start locator should not retrieve cluster status when --connect=false
[
https://issues.apache.org/jira/browse/GEODE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335052#comment-16335052
]
ASF subversion and git services commented on GEODE-4332:
Commit 8d0224742c5308a13df0e2e344df9e6f9ed2ea94 in geode's branch
refs/heads/feature/GEODE-4142 from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8d02247 ]
GEODE-4332: Gfsh start locator should not retrieve cluster status when
--connect=false (#1315)
> Gfsh start locator should not retrieve cluster status when --connect=false
> --
>
> Key: GEODE-4332
> URL: https://issues.apache.org/jira/browse/GEODE-4332
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
> Fix For: 1.5.0
>
>
> When user starts locator with --connect=false, it should not retrieve
> cluster-configuration service status.
> {noformat}
> gfsh>start locator --name=locator1 --connect=false
> Starting a Geode Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1...
> ...
> Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1 on
> 10.118.19.26[10334] as locator1 is currently online.
> Process ID: 21762
> Uptime: 2 seconds
> Geode Version: 1.5.0-SNAPSHOT
> Java Version: 1.8.0_151
> Log File:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-core-1.5.0-SNAPSHOT.jar:/Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-dependencies.jar
> Cluster configuration service is up and running.{noformat}
> As you can see that it retrieves the status and displays cluster
> configuration service is running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4333) AbstractRegionMap destroy needs unit tests
[ https://issues.apache.org/jira/browse/GEODE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335053#comment-16335053 ] ASF subversion and git services commented on GEODE-4333: Commit 4f0c0b1f32d86aad4595c33c679e20799c5dbaeb in geode's branch refs/heads/feature/GEODE-4142 from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f0c0b1 ] GEODE-4333: add unit tests for AbstractRegionMap.destroy (#1314) > AbstractRegionMap destroy needs unit tests > -- > > Key: GEODE-4333 > URL: https://issues.apache.org/jira/browse/GEODE-4333 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.5.0 > > > The destroy method on AbstractRegionMap needs unit test coverage. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335054#comment-16335054 ] ASF subversion and git services commented on GEODE-3554: Commit 7fc5d6e93c66f3a3b0bd4a4cfec5f9a5c20425d2 in geode's branch refs/heads/feature/GEODE-4142 from [~agingade] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7fc5d6e ] GEODE-3554: Add javadoc warning about getAnyInstance in CacheCallback > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > Fix For: 1.5.0 > > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4136) Skipped IntegrationTest QueryCommandTest fails under HTTP
[
https://issues.apache.org/jira/browse/GEODE-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335057#comment-16335057
]
ASF subversion and git services commented on GEODE-4136:
Commit 4d829959d435740fb06f88f3b186290da328a803 in geode's branch
refs/heads/feature/GEODE-4142 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4d82995 ]
GEODE-4136: Move http related test to geode-web (#1319)
> Skipped IntegrationTest QueryCommandTest fails under HTTP
> -
>
> Key: GEODE-4136
> URL: https://issues.apache.org/jira/browse/GEODE-4136
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Jens Deppe
>Priority: Major
>
> These tests can fail at {{gfsh.connectAndVerify}}, dependent on testing
> environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335055#comment-16335055 ] ASF subversion and git services commented on GEODE-3554: Commit ec53f620359f85b4d3c0063b34ec5911e84c50c9 in geode's branch refs/heads/feature/GEODE-4142 from [~agingade] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ec53f62 ] GEODE-3554: Add additional javadoc about how to get Cache. > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > Fix For: 1.5.0 > > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4142) When processing the beforeCompletion message, transaction should check if the transaction has been completed already
[
https://issues.apache.org/jira/browse/GEODE-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335058#comment-16335058
]
ASF subversion and git services commented on GEODE-4142:
Commit 943ec077c00d9d5254f1117631ec9b849cb4b960 in geode's branch
refs/heads/feature/GEODE-4142 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=943ec07 ]
Merge remote-tracking branch 'origin/develop' into feature/GEODE-4142
> When processing the beforeCompletion message, transaction should check if the
> transaction has been completed already
>
>
> Key: GEODE-4142
> URL: https://issues.apache.org/jira/browse/GEODE-4142
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> The following NPE could occur if the JTA has been committed but client
> connection was lost. The client retries the afterCompletion on another node.
> Needs to check if the JTA has been completed/committed already.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.JtaBeforeCompletionMessage.operateOnTx(JtaBeforeCompletionMessage.java:66)
> at
> org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:88)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:374)
> at
> org.apache.geode.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:432)
> at
> org.apache.geode.distributed.internal.DistributionManager.scheduleIncomingMessage(DistributionManager.java:3554)
> at
> org.apache.geode.distributed.internal.DistributionManager.handleIncomingDMsg(DistributionManager.java:3188)
> at
> org.apache.geode.distributed.internal.DistributionManager$MyListener.messageReceived(DistributionManager.java:4363)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.dispatchMessage(GMSMembershipManager.java:1127)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.handleOrDeferMessage(GMSMembershipManager.java:1045)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$MyDCReceiver.messageReceived(GMSMembershipManager.java:408)
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.receive(DirectChannel.java:715)
> at
> org.apache.geode.internal.tcp.TCPConduit.messageReceived(TCPConduit.java:875)
> at
> org.apache.geode.internal.tcp.Connection.dispatchMessage(Connection.java:3967)
> at
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3553)
> at
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1829)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1690)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4138) Skipped DistributedTest ShutdownCommandDUnitTest fails over http
[
https://issues.apache.org/jira/browse/GEODE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335056#comment-16335056
]
ASF subversion and git services commented on GEODE-4138:
Commit 051349b0992cd374bb6e3323d625812ca2deb709 in geode's branch
refs/heads/feature/GEODE-4142 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=051349b ]
GEODE-4138: Move http related test to geode-web (#1320)
> Skipped DistributedTest ShutdownCommandDUnitTest fails over http
>
>
> Key: GEODE-4138
> URL: https://issues.apache.org/jira/browse/GEODE-4138
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, tests
>Reporter: Patrick Rhomberg
>Assignee: Jens Deppe
>Priority: Major
>
> Test fails in {{gfsh.connectAndVerify}} dependent on environment. Similar to
> GEODE-4136.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4031) Update CacheSnapshotService javadocs for .gfd requirement
[ https://issues.apache.org/jira/browse/GEODE-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335050#comment-16335050 ] ASF subversion and git services commented on GEODE-4031: Commit c1cf5d1505f35d6352d43969ef6f74a2fcb6b516 in geode's branch refs/heads/feature/GEODE-4142 from [~nreich] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c1cf5d1 ] GEODE-4031: Update javadocs to include .gfd snapshot extension requirement (#1311) > Update CacheSnapshotService javadocs for .gfd requirement > - > > Key: GEODE-4031 > URL: https://issues.apache.org/jira/browse/GEODE-4031 > Project: Geode > Issue Type: Sub-task > Components: snapshot >Affects Versions: 1.3.0 >Reporter: Fred Krone >Assignee: Nick Reich >Priority: Minor > Fix For: 1.5.0 > > > Would like to note in the documentation > http://geode.apache.org/docs/guide/13/managing/cache_snapshots/exporting_a_snapshot.html > that "The file must have an extension of .gfd" -- just like in the import / > export docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4015) CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335051#comment-16335051
]
ASF subversion and git services commented on GEODE-4015:
Commit b690cfad68c95e60b237ebc9d316420be692998d in geode's branch
refs/heads/feature/GEODE-4142 from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b690cfa ]
GEODE-4015: Rewrite queue conflation tests (#1312)
* Refactored HARegionQueue to allow unit testing
> CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with
> AssertionError
> --
>
> Key: GEODE-4015
> URL: https://issues.apache.org/jira/browse/GEODE-4015
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
>
> Both testTwoRegionsTwoWriters and testTwoRegionsOneWriter failed with the
> same AssertionError:
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsTwoWriters FAILED
> java.lang.AssertionError: Test failed due to exception
> at org.apache.geode.test.dunit.Assert.fail(Assert.java:66)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:155)
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$193/1316585270.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:153)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms:
> null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsTwoWriters$bb17a952$10(ConflationDUnitTest.java:153)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsOneWriter FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$221/1553950035.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsOneWriter(ConflationDUnitTest.java:183)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms: null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsOneWriter$bb17a952$10(ConflationDUnitTest.java:183)
> {noformat}
> ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506) is
> waiting for {{counterUpdate == 2}}.
> I think this is a timing issue. The first line of the test sets
> CacheClientProxy.isSlowStartForTesting to true. This causes the
> MessageDispatcher to not send messages immediately. Instead, it waits for 5
> seconds before sending. This allows the queue to conflate the events. If I
> remove the slow start setting, the test fails every time because conflation
> doesn't happen.
> Unfortunately, the description returns null (the null in the AssertionError
> messages above), so we don't know anything about why the assertion is
> failing. If it were changed to return the actual value of counterUpdate, that
> would be helpful.
> With that change and the boolean not set in the test, I see:
> {noformat}
> Caused by: java.lang.AssertionError: Event never occurred after 6 ms:
> Expected counterUpdate to be 2. Instead it was 6
> {noformat}
> My guess is that between the time the MessageDispatcher is told to wait and
> the test actually runs, at least 5 seconds elapses, and the conflation
>
[jira] [Created] (GEODE-4357) Cleanup AbstractRegionMap and its subclasses
Kirk Lund created GEODE-4357: Summary: Cleanup AbstractRegionMap and its subclasses Key: GEODE-4357 URL: https://issues.apache.org/jira/browse/GEODE-4357 Project: Geode Issue Type: Improvement Components: regions Reporter: Kirk Lund This carries on with what we started in GEODE-4333. The initial focus is to improve code coverage so that we can start to refactor AbstractRegionMap and ultimately add new behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4282) createKey, createValue functions missing for many Serializable types.
[ https://issues.apache.org/jira/browse/GEODE-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335042#comment-16335042 ] ASF subversion and git services commented on GEODE-4282: Commit e3ebdd8f4106e78d368c92975ef80243bce1f0a2 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e3ebdd8 ] GEODE-4282: Remove createKey/Value templates. (#189) - Use Serializable::create to specialize for creating cacheable objects. - Use CacheableKey::create to specialize for creating key objects. > createKey, createValue functions missing for many Serializable types. > - > > Key: GEODE-4282 > URL: https://issues.apache.org/jira/browse/GEODE-4282 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > Serializable/CacheableKey::create method needs namespace functions > createValue/createKey for each of the supported primitive types. Many of > these types are missing as a result of bad refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4267) PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId fails intermittently due to DistributedSystemDisconnectedException suspect string
[
https://issues.apache.org/jira/browse/GEODE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barry Oglesby updated GEODE-4267:
-
Attachment: GEODE-4267-standard-output.txt
> PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId
> fails intermittently due to DistributedSystemDisconnectedException suspect
> string
> --
>
> Key: GEODE-4267
> URL: https://issues.apache.org/jira/browse/GEODE-4267
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Kirk Lund
>Priority: Major
> Labels: Flaky
> Attachments: GEODE-4267-standard-output.txt
>
>
> {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.RuntimeException:
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> This connection to a distributed system has been disconnected.
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1443
> [error 2017/12/16 00:50:26.778 UTC
> tid=0x1b]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4267) PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId fails intermittently due to DistributedSystemDisconnectedException suspect string
[
https://issues.apache.org/jira/browse/GEODE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335023#comment-16335023
]
Barry Oglesby commented on GEODE-4267:
--
This occurred again. I attached the entire standard output from the test run:
[^GEODE-4267-standard-output.txt]
> PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId
> fails intermittently due to DistributedSystemDisconnectedException suspect
> string
> --
>
> Key: GEODE-4267
> URL: https://issues.apache.org/jira/browse/GEODE-4267
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Kirk Lund
>Priority: Major
> Labels: Flaky
> Attachments: GEODE-4267-standard-output.txt
>
>
> {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.RuntimeException:
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> This connection to a distributed system has been disconnected.
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1443
> [error 2017/12/16 00:50:26.778 UTC
> tid=0x1b]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3967) if put hits concurrent modification exception should still notify serial gateway sender
[
https://issues.apache.org/jira/browse/GEODE-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334986#comment-16334986
]
xiaojian zhou commented on GEODE-3967:
--
{noformat}
There are following race conditions contribute together to the bug:
1) When ConcurrentModificationException happened:
* if tag's timestamp is higher, then notifyGateSender with
UPDATE_VERSION_STAMP, which is creating a new event id.
* if tag's timestamp is lower, then do nothing.
In either way, the event for original event id not sent to the Gateway queue.
If this member happened to host the primary queue, the event in second queue
will not get a chance to cleanup. We should notify gatewaySender for event with
CME
2) UPDATE_VERSION_STAMP will have new event id. If this member happened to be a
secondary queue, then the event will stay there long or forever. We should
check if queue's primary, only enqueue UPDATE_VERSION_STAMP event when queue is
primary.
3) AUO.doPutOrCreate() will call basicUpdate() 3 times, or 3 tries: create,
update, create.
There's race that between update(2nd try) and create (3rd try), other thread
delete the entry caused the 2nd try failed, then before 3rd try, a create jump
in cause the 3rd try failed silently (no log and no exception, not to
notifyGatewaySender).
As the last try, it should use ifNew=false, ifOld=false to apply the put()
anyway.
{noformat}
> if put hits concurrent modification exception should still notify serial
> gateway sender
> ---
>
> Key: GEODE-3967
> URL: https://issues.apache.org/jira/browse/GEODE-3967
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
>
> In serial gateway sender, the event arrives at secondary will be put into
> unprocessedMap and wait for event from primary queue to distribute over, then
> remove it from the unprocessedMap.
> If the put at primary member (member with primary queue) failed with CME, the
> event in unprocessedMap will never be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4142) When processing the beforeCompletion message, transaction should check if the transaction has been completed already
[
https://issues.apache.org/jira/browse/GEODE-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334912#comment-16334912
]
ASF subversion and git services commented on GEODE-4142:
Commit ae5fc65c019090cebcc38c939931c1bfd7225730 in geode's branch
refs/heads/feature/GEODE-4142 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ae5fc65 ]
GEODE-4142: save commit message for failover after jta commit.
check if the jta has completed before retrying the beforeCompeltion and
afterCompletion in failover cases.
> When processing the beforeCompletion message, transaction should check if the
> transaction has been completed already
>
>
> Key: GEODE-4142
> URL: https://issues.apache.org/jira/browse/GEODE-4142
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> The following NPE could occur if the JTA has been committed but client
> connection was lost. The client retries the afterCompletion on another node.
> Needs to check if the JTA has been completed/committed already.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.geode.internal.cache.JtaBeforeCompletionMessage.operateOnTx(JtaBeforeCompletionMessage.java:66)
> at
> org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:88)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:374)
> at
> org.apache.geode.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:432)
> at
> org.apache.geode.distributed.internal.DistributionManager.scheduleIncomingMessage(DistributionManager.java:3554)
> at
> org.apache.geode.distributed.internal.DistributionManager.handleIncomingDMsg(DistributionManager.java:3188)
> at
> org.apache.geode.distributed.internal.DistributionManager$MyListener.messageReceived(DistributionManager.java:4363)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.dispatchMessage(GMSMembershipManager.java:1127)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.handleOrDeferMessage(GMSMembershipManager.java:1045)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$MyDCReceiver.messageReceived(GMSMembershipManager.java:408)
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.receive(DirectChannel.java:715)
> at
> org.apache.geode.internal.tcp.TCPConduit.messageReceived(TCPConduit.java:875)
> at
> org.apache.geode.internal.tcp.Connection.dispatchMessage(Connection.java:3967)
> at
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3553)
> at
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1829)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1690)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone resolved GEODE-3554. --- Resolution: Fixed Fix Version/s: 1.5.0 > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > Fix For: 1.5.0 > > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4138) Skipped DistributedTest ShutdownCommandDUnitTest fails over http
[
https://issues.apache.org/jira/browse/GEODE-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334895#comment-16334895
]
ASF subversion and git services commented on GEODE-4138:
Commit 051349b0992cd374bb6e3323d625812ca2deb709 in geode's branch
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=051349b ]
GEODE-4138: Move http related test to geode-web (#1320)
> Skipped DistributedTest ShutdownCommandDUnitTest fails over http
>
>
> Key: GEODE-4138
> URL: https://issues.apache.org/jira/browse/GEODE-4138
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh, tests
>Reporter: Patrick Rhomberg
>Assignee: Jens Deppe
>Priority: Major
>
> Test fails in {{gfsh.connectAndVerify}} dependent on environment. Similar to
> GEODE-4136.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4355) ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation fails intermittently in CI
[
https://issues.apache.org/jira/browse/GEODE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334881#comment-16334881
]
Kirk Lund commented on GEODE-4355:
--
I see in the test code what causes the flakiness:
{noformat}
// assert
verify(requestHandler, timeout(TEN_MINUTES_MILLIS)).handleRequest();
assertThat(file).doesNotExist();
{noformat}
Should change to:
{noformat}
// assert
verify(requestHandler, timeout(TEN_MINUTES_MILLIS)).handleRequest();
await().atMost(10, MINUTES).until(() -> assertThat(file).doesNotExist());
{noformat}
> ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation
> fails intermittently in CI
> -
>
> Key: GEODE-4355
> URL: https://issues.apache.org/jira/browse/GEODE-4355
> Project: Geode
> Issue Type: Bug
> Components: gfsh, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: Flaky
>
> This test usually passes but failed in these CI runs:
> *
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/98
> *
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/123
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-4355) ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation fails intermittently in CI
[ https://issues.apache.org/jira/browse/GEODE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-4355: Assignee: Kirk Lund > ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation > fails intermittently in CI > - > > Key: GEODE-4355 > URL: https://issues.apache.org/jira/browse/GEODE-4355 > Project: Geode > Issue Type: Bug > Components: gfsh, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: Flaky > > This test usually passes but failed in these CI runs: > * > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/98 > * > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/123 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4355) ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation fails intermittently in CI
Kirk Lund created GEODE-4355: Summary: ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation fails intermittently in CI Key: GEODE-4355 URL: https://issues.apache.org/jira/browse/GEODE-4355 Project: Geode Issue Type: Bug Components: gfsh, tests Reporter: Kirk Lund This test usually passes but failed in these CI runs: * https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/98 * https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/123 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4355) ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation fails intermittently in CI
[ https://issues.apache.org/jira/browse/GEODE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4355: - Labels: Flaky (was: ) > ControlFileWatchdogIntegrationTest.invokesRequestHandler_afterFileCreation > fails intermittently in CI > - > > Key: GEODE-4355 > URL: https://issues.apache.org/jira/browse/GEODE-4355 > Project: Geode > Issue Type: Bug > Components: gfsh, tests >Reporter: Kirk Lund >Priority: Major > Labels: Flaky > > This test usually passes but failed in these CI runs: > * > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/98 > * > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/123 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334820#comment-16334820 ] ASF subversion and git services commented on GEODE-3554: Commit ec53f620359f85b4d3c0063b34ec5911e84c50c9 in geode's branch refs/heads/develop from [~agingade] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ec53f62 ] GEODE-3554: Add additional javadoc about how to get Cache. > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334819#comment-16334819 ] ASF subversion and git services commented on GEODE-3554: Commit 7fc5d6e93c66f3a3b0bd4a4cfec5f9a5c20425d2 in geode's branch refs/heads/develop from [~agingade] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7fc5d6e ] GEODE-3554: Add javadoc warning about getAnyInstance in CacheCallback > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2546) RollingUpgradeDUnitTest fails intermittently with ClusterConfigurationNotAvailableException
[
https://issues.apache.org/jira/browse/GEODE-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dodge resolved GEODE-2546.
--
Resolution: Fixed
The fix for GEODE-4140 should fix this, too.
> RollingUpgradeDUnitTest fails intermittently with
> ClusterConfigurationNotAvailableException
> ---
>
> Key: GEODE-2546
> URL: https://issues.apache.org/jira/browse/GEODE-2546
> Project: Geode
> Issue Type: Bug
> Components: configuration, locator
>Reporter: Kirk Lund
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: Flaky
>
> This test might be hitting GEODE-2238. If we change the test to await cluster
> config readiness it should fix this.
> {noformat}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest >
> testRollServersOnPartitionedRegion_dataserializable[1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest$3.run
> in VM 0 running on Host e41dd4960b22 with 4 VMs with version 110
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:292)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.invokeRunnableInVMs(RollingUpgradeDUnitTest.java:333)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.doTestRollAll(RollingUpgradeDUnitTest.java:177)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.testRollServersOnPartitionedRegion_dataserializable(RollingUpgradeDUnitTest.java:129)
> Caused by:
> java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> Caused by:
> java.lang.reflect.InvocationTargetException
> 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.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.createCache(RollingUpgradeDUnitTest.java:722)
> Caused by:
> org.apache.geode.GemFireConfigException: cluster
> configuration service not available
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1067)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1200)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:798)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:783)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:178)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:218)
> ... 5 more
> Caused by:
>
> org.apache.geode.internal.process.ClusterConfigurationNotAvailableException:
> Unable to retrieve cluster configuration from the locator.
> at
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:245)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1029)
> ... 10 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-2546) RollingUpgradeDUnitTest fails intermittently with ClusterConfigurationNotAvailableException
[
https://issues.apache.org/jira/browse/GEODE-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334793#comment-16334793
]
Michael Dodge commented on GEODE-2546:
--
GEODE-4140 is now marked as resolved so I'm going to mark this as resolved, too.
> RollingUpgradeDUnitTest fails intermittently with
> ClusterConfigurationNotAvailableException
> ---
>
> Key: GEODE-2546
> URL: https://issues.apache.org/jira/browse/GEODE-2546
> Project: Geode
> Issue Type: Bug
> Components: configuration, locator
>Reporter: Kirk Lund
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: Flaky
>
> This test might be hitting GEODE-2238. If we change the test to await cluster
> config readiness it should fix this.
> {noformat}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest >
> testRollServersOnPartitionedRegion_dataserializable[1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest$3.run
> in VM 0 running on Host e41dd4960b22 with 4 VMs with version 110
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:292)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.invokeRunnableInVMs(RollingUpgradeDUnitTest.java:333)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.doTestRollAll(RollingUpgradeDUnitTest.java:177)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.testRollServersOnPartitionedRegion_dataserializable(RollingUpgradeDUnitTest.java:129)
> Caused by:
> java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> Caused by:
> java.lang.reflect.InvocationTargetException
> 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.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.createCache(RollingUpgradeDUnitTest.java:722)
> Caused by:
> org.apache.geode.GemFireConfigException: cluster
> configuration service not available
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1067)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1200)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:798)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:783)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:178)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:218)
> ... 5 more
> Caused by:
>
> org.apache.geode.internal.process.ClusterConfigurationNotAvailableException:
> Unable to retrieve cluster configuration from the locator.
> at
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:245)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1029)
> ... 10 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4333) AbstractRegionMap destroy needs unit tests
[ https://issues.apache.org/jira/browse/GEODE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-4333. - Resolution: Fixed Fix Version/s: 1.5.0 > AbstractRegionMap destroy needs unit tests > -- > > Key: GEODE-4333 > URL: https://issues.apache.org/jira/browse/GEODE-4333 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Fix For: 1.5.0 > > > The destroy method on AbstractRegionMap needs unit test coverage. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4333) AbstractRegionMap destroy needs unit tests
[ https://issues.apache.org/jira/browse/GEODE-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334768#comment-16334768 ] ASF subversion and git services commented on GEODE-4333: Commit 4f0c0b1f32d86aad4595c33c679e20799c5dbaeb in geode's branch refs/heads/develop from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f0c0b1 ] GEODE-4333: add unit tests for AbstractRegionMap.destroy (#1314) > AbstractRegionMap destroy needs unit tests > -- > > Key: GEODE-4333 > URL: https://issues.apache.org/jira/browse/GEODE-4333 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > The destroy method on AbstractRegionMap needs unit test coverage. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3644) Add function execution on specific keys
[ https://issues.apache.org/jira/browse/GEODE-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-3644: Description: As a Geode developer using the new client/server protocol, I need the ability to execute server-side functions on specific keys. Add function execution on specific keys to the new protocol, verifying users can execute functions and receive expected results on both replicate and partitioned regions. was: As a Geode developer using the new client/server protocol, I need the ability to execute server-side functions on specific keys. Add function execution on specific keys in a partitioned region to the new protocol, verifying users can execute functions and receive expected results on both replicate and partitioned regions. > Add function execution on specific keys > --- > > Key: GEODE-3644 > URL: https://issues.apache.org/jira/browse/GEODE-3644 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Priority: Major > > As a Geode developer using the new client/server protocol, I need the ability > to execute server-side functions on specific keys. > Add function execution on specific keys to the new protocol, verifying users > can execute functions and receive expected results on both replicate and > partitioned regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3644) Add function execution on specific keys
[ https://issues.apache.org/jira/browse/GEODE-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-3644: Description: As a Geode developer using the new client/server protocol, I need the ability to execute server-side functions on specific keys. Add function execution on specific keys in a partitioned region to the new protocol, verifying users can execute functions and receive expected results on both replicate and partitioned regions. was: As a Geode developer using the new client/server protocol, I need the ability to execute server-side functions on specific keys in a partitioned region. Add function execution on specific keys in a partitioned region to the new protocol, verifying users can execute functions and receive expected results. Summary: Add function execution on specific keys (was: Add function execution on specific keys in a partitioned region) > Add function execution on specific keys > --- > > Key: GEODE-3644 > URL: https://issues.apache.org/jira/browse/GEODE-3644 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Priority: Major > > As a Geode developer using the new client/server protocol, I need the ability > to execute server-side functions on specific keys. > Add function execution on specific keys in a partitioned region to the new > protocol, verifying users can execute functions and receive expected results > on both replicate and partitioned regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Fred Krone updated GEODE-4250: -- Description: 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. was: 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. > 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
[jira] [Resolved] (GEODE-4332) Gfsh start locator should not retrieve cluster status when --connect=false
[
https://issues.apache.org/jira/browse/GEODE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda resolved GEODE-4332.
Resolution: Fixed
Fix Version/s: 1.5.0
> Gfsh start locator should not retrieve cluster status when --connect=false
> --
>
> Key: GEODE-4332
> URL: https://issues.apache.org/jira/browse/GEODE-4332
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
> Fix For: 1.5.0
>
>
> When user starts locator with --connect=false, it should not retrieve
> cluster-configuration service status.
> {noformat}
> gfsh>start locator --name=locator1 --connect=false
> Starting a Geode Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1...
> ...
> Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1 on
> 10.118.19.26[10334] as locator1 is currently online.
> Process ID: 21762
> Uptime: 2 seconds
> Geode Version: 1.5.0-SNAPSHOT
> Java Version: 1.8.0_151
> Log File:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-core-1.5.0-SNAPSHOT.jar:/Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-dependencies.jar
> Cluster configuration service is up and running.{noformat}
> As you can see that it retrieves the status and displays cluster
> configuration service is running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4297) User Guide: Clarify logging from developer's perspective
[ https://issues.apache.org/jira/browse/GEODE-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327993#comment-16327993 ] Dave Barnes edited comment on GEODE-4297 at 1/22/18 6:27 PM: - [also from Mark Secrist] I think there may be some inaccuracies here: http://geode.apache.org/docs/guide/13/managing/logging/configuring_log4j2.html related to use of LogWriter, which I believe is deprecated was (Author: dbarnes97): [also from Mark Secrist] I think there may be some inaccuracies here: https://gemfire.docs.pivotal.io/geode/managing/logging/configuring_log4j2.html related to use of LogWriter, which I believe is deprecated > User Guide: Clarify logging from developer's perspective > > > Key: GEODE-4297 > URL: https://issues.apache.org/jira/browse/GEODE-4297 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Priority: Major > > [Request from Mark Secrist] > I find the documentation doesn’t go far enough to cover how to do logging - > particularly on the server side from a developer perspective. > I figured out how to set up logging by jumping through GemFire code and found > something like the following > ```Logger logger = LogService.getLogger() ``` > This is the recommended way, but it's not covered in the docs. Also - the > logging doesn’t tend to have the level of detail I like (ex class & method). > I realize this has to do with how the overall appender is configured. I’m > curious if we have recommended ways of overriding this in certain situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4025) Write functional tests with external DB
[ https://issues.apache.org/jira/browse/GEODE-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone resolved GEODE-4025. --- Resolution: Won't Fix > Write functional tests with external DB > --- > > Key: GEODE-4025 > URL: https://issues.apache.org/jira/browse/GEODE-4025 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Fred Krone >Priority: Major > > We will need an operational test infrastructure to do integration testing > with an external database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-4025) Write functional tests with external DB
[ https://issues.apache.org/jira/browse/GEODE-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone closed GEODE-4025. - > Write functional tests with external DB > --- > > Key: GEODE-4025 > URL: https://issues.apache.org/jira/browse/GEODE-4025 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Fred Krone >Priority: Major > > We will need an operational test infrastructure to do integration testing > with an external database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2505) create region command should verify region attributes
[
https://issues.apache.org/jira/browse/GEODE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334675#comment-16334675
]
Barbara Pruijn commented on GEODE-2505:
---
New Jira is
https://issues.apache.org/jira/browse/GEODE-4354
> create region command should verify region attributes
> -
>
> Key: GEODE-2505
> URL: https://issues.apache.org/jira/browse/GEODE-2505
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Fix For: 1.4.0
>
>
> The gfsh {{create region}} command tries to be idempotent. If I try to create
> the same region twice I get the below message:
> {noformat}
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.
> {noformat}
> However, when a user is using a gfsh script to configure a cluster, and
> inadvertently changes the region attributes the {{create region}} command
> will still succeed.
> {noformat}
> gfsh>create region --name=foo --type=REPLICATE
> Member | Status
> -- |
> serv1 | Region "/foo" created on "serv1"
> gfsh>create region --name=foo --type=PARTITION
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.
> {noformat}
> We should verify the region attributes, and if the attributes don't match we
> should log an error asking the user to export the data from the existing
> region, destroy the region, create the region again with new attributes and
> import the data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4354) On create region command change option --skip-if-exists to --if-not-exist
[
https://issues.apache.org/jira/browse/GEODE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334673#comment-16334673
]
Barbara Pruijn commented on GEODE-4354:
---
This is related to
https://issues.apache.org/jira/browse/GEODE-2505
> On create region command change option --skip-if-exists to --if-not-exist
> -
>
> Key: GEODE-4354
> URL: https://issues.apache.org/jira/browse/GEODE-4354
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> The gfsh {{create region}} command tries to be idempotent. If I try to create
> the same region twice I get the below message:
> {noformat}
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.{noformat}
> Currently, there is a
> {{--skip-if-exists}}
> option. This should be consistent with other gfsh commands and should be
> rename
> {{--if-not-exists}}
> This option should also be added the {{help create region}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4354) On create region command change option --skip-if-exists to --if-not-exist
Barbara Pruijn created GEODE-4354:
-
Summary: On create region command change option --skip-if-exists
to --if-not-exist
Key: GEODE-4354
URL: https://issues.apache.org/jira/browse/GEODE-4354
Project: Geode
Issue Type: Improvement
Components: docs, gfsh
Reporter: Barbara Pruijn
The gfsh {{create region}} command tries to be idempotent. If I try to create
the same region twice I get the below message:
{noformat}
Member | Status
-- | --
serv1 | Skipping "serv1". Region "foo" already exists.{noformat}
Currently, there is a
{{--skip-if-exists}}
option. This should be consistent with other gfsh commands and should be rename
{{--if-not-exists}}
This option should also be added the {{help create region}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4332) Gfsh start locator should not retrieve cluster status when --connect=false
[
https://issues.apache.org/jira/browse/GEODE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334667#comment-16334667
]
ASF subversion and git services commented on GEODE-4332:
Commit 8d0224742c5308a13df0e2e344df9e6f9ed2ea94 in geode's branch
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8d02247 ]
GEODE-4332: Gfsh start locator should not retrieve cluster status when
--connect=false (#1315)
> Gfsh start locator should not retrieve cluster status when --connect=false
> --
>
> Key: GEODE-4332
> URL: https://issues.apache.org/jira/browse/GEODE-4332
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>
> When user starts locator with --connect=false, it should not retrieve
> cluster-configuration service status.
> {noformat}
> gfsh>start locator --name=locator1 --connect=false
> Starting a Geode Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1...
> ...
> Locator in
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1 on
> 10.118.19.26[10334] as locator1 is currently online.
> Process ID: 21762
> Uptime: 2 seconds
> Geode Version: 1.5.0-SNAPSHOT
> Java Version: 1.8.0_151
> Log File:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/bin/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-core-1.5.0-SNAPSHOT.jar:/Users/sai/workspace/debug/apache-geode-1.5.0-SNAPSHOT/lib/geode-dependencies.jar
> Cluster configuration service is up and running.{noformat}
> As you can see that it retrieves the status and displays cluster
> configuration service is running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4353) Deprecate security-client-dhalgo property
Dan Smith created GEODE-4353:
Summary: Deprecate security-client-dhalgo property
Key: GEODE-4353
URL: https://issues.apache.org/jira/browse/GEODE-4353
Project: Geode
Issue Type: Bug
Components: client/server
Reporter: Dan Smith
{{security-client-dhalgo}}{{ should be deprecated in favor of using the ssl-*
settings.}}
[{{https://gemfire.docs.pivotal.io/geode/managing/security/encrypting_with_diffie_hellman.html}}]{{}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4031) Update CacheSnapshotService javadocs for .gfd requirement
[ https://issues.apache.org/jira/browse/GEODE-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Reich resolved GEODE-4031. --- Resolution: Fixed Fix Version/s: 1.5.0 > Update CacheSnapshotService javadocs for .gfd requirement > - > > Key: GEODE-4031 > URL: https://issues.apache.org/jira/browse/GEODE-4031 > Project: Geode > Issue Type: Sub-task > Components: snapshot >Affects Versions: 1.3.0 >Reporter: Fred Krone >Assignee: Nick Reich >Priority: Minor > Fix For: 1.5.0 > > > Would like to note in the documentation > http://geode.apache.org/docs/guide/13/managing/cache_snapshots/exporting_a_snapshot.html > that "The file must have an extension of .gfd" -- just like in the import / > export docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3138) Add function execution *with parameters* to new protocol
[ https://issues.apache.org/jira/browse/GEODE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-3138. - Resolution: Duplicate > Add function execution *with parameters* to new protocol > > > Key: GEODE-3138 > URL: https://issues.apache.org/jira/browse/GEODE-3138 > Project: Geode > Issue Type: Sub-task > Components: client/server >Reporter: Brian Baynes >Priority: Major > > As a Geode user, I want to be able to call server-side functions with > parameters (such as a Region name to run a function against). > Expand function execution to include functions with parameters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4180) Tests should not mutate system property "user.dir"
[
https://issues.apache.org/jira/browse/GEODE-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-4180:
-
Summary: Tests should not mutate system property "user.dir" (was:
Reference to locator view file and/or its contents are not cleaned up properly
during cache close)
> Tests should not mutate system property "user.dir"
> --
>
> Key: GEODE-4180
> URL: https://issues.apache.org/jira/browse/GEODE-4180
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.4.0
>Reporter: Kirk Lund
>Priority: Major
>
> We temporarily set the member-timeout to max value to allow us to step
> through some code in the debugger. We noticed that if we run all 4 tests
> together, tests 2-3 were hanging.
> After removing the member-timeout setting, we found that all of the tests
> after the 1st test are all trying to connect to the non-existent locator from
> the 1st test. This causes all tests after the 1st test to take ~2 seconds
> longer to run when run together than if you run them by individually.
> After digging a bit more, I discovered that even though the test is deleting
> the entire directory containing the locator0view.dat file, some code
> somewhere must still have an open connection or stream to it because its
> contents from the 1st test continue to be read for each subsequent test even
> after the file itself and its directory have been deleted.
> I believe some static code somewhere is keeping a reference to the file
> and/or its contents. So each test continues to read the same content even
> though the file no longer exists on disk.
> The following shows the relevant messages logged by 4 tests in a DUnit test
> that shows tests 2-3 find and using the file and/or its contents from test 1.
> Note that I used IntelliJ debugger to confirm that this occurs even after
> test 1 deletes the file and its directory.
> 1) createsRegionMappingOnceOnly
> {noformat}
> [vm0] [info 2017/12/29 10:59:30.826 PST
> tid=20] recovery file not found:
> /var/folders/28/m__9dv1906n60kmz7t71wm68gn/T/junit543979839291182624/vm-0-createsRegionMappingOnceOnly/locator0view.dat
> [vm0] [info 2017/12/29 10:59:31.135 PST
> tid=20] received new view: View[192.168.1.18(58582:locator):32770|0]
> members: [192.168.1.18(58582:locator):32770]
> [vm0] old view is: null
> {noformat}
> 2) createsRegionMappingWithMinimumParams
> {noformat}
> [vm0] [info 2017/12/29 10:59:34.580 PST
> tid=20] Peer locator recovering from
> /var/folders/28/m__9dv1906n60kmz7t71wm68gn/T/junit107641374957435/vm-0-createsRegionMappingWithMinimumParams/locator0view.dat
> [vm0] [info 2017/12/29 10:59:34.580 PST
> tid=20] Peer locator recovered membership is
> View[192.168.1.18(58582:locator):32770|-1] members:
> [192.168.1.18(58580):32771{lead}]
> {noformat}
> 3) createsRegionMappingInService
> {noformat}
> [vm0] [info 2017/12/29 10:59:40.538 PST
> tid=20] Peer locator recovering from
> /var/folders/28/m__9dv1906n60kmz7t71wm68gn/T/junit8253504123764665822/vm-0-createsRegionMappingInService/locator0view.dat
> [vm0] [info 2017/12/29 10:59:40.538 PST
> tid=20] Peer locator recovered membership is
> View[192.168.1.18(58582:locator):32770|-1] members:
> [192.168.1.18(58580):32771{lead}]
> {noformat}
> 4) recreatesCacheFromClusterConfigWithRegionMapping
> {noformat}
> [vm0] [info 2017/12/29 10:59:46.495 PST
> tid=20] Peer locator recovering from
> /var/folders/28/m__9dv1906n60kmz7t71wm68gn/T/junit1056719983598139185/vm-0-recreatesCacheFromClusterConfigWithRegionMapping/locator0view.dat
> [vm0] [info 2017/12/29 10:59:46.496 PST
> tid=20] Peer locator recovered membership is
> View[192.168.1.18(58582:locator):32770|-1] members:
> [192.168.1.18(58580):32771{lead}]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4352) All instances of new File should use System.getProperty("user.dir") as parent File
[
https://issues.apache.org/jira/browse/GEODE-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-4352.
--
Resolution: Won't Fix
> All instances of new File should use System.getProperty("user.dir") as parent
> File
> --
>
> Key: GEODE-4352
> URL: https://issues.apache.org/jira/browse/GEODE-4352
> Project: Geode
> Issue Type: Sub-task
>Reporter: Kirk Lund
>Priority: Major
>
> Since some Geode tests manipulate the system property "user.dir", all uses of
> "new File(...)" must use System.getProperty("user.dir") as the parent File.
> Otherwise the wrong path can end up being used.
> Note, this spans ALL of the Geode product code. Should we file a separate but
> identical ticket for every API package or list every Component in this Jira
> ticket?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4351) All instances of new File should use absolute path instead of relative "."
[ https://issues.apache.org/jira/browse/GEODE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-4351. -- Resolution: Won't Fix > All instances of new File should use absolute path instead of relative "." > -- > > Key: GEODE-4351 > URL: https://issues.apache.org/jira/browse/GEODE-4351 > Project: Geode > Issue Type: Sub-task >Reporter: Kirk Lund >Priority: Major > > Since some Geode tests manipulate the system property "user.dir", all uses of > "new File(...)" must use absolute path. Otherwise the wrong path can end up > being logged or reported. > Note, this spans ALL of the Geode product code. Should we file a separate but > identical ticket for every API package or list every Component in this Jira > ticket? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4351) All instances of new File should use absolute path instead of relative "."
[ https://issues.apache.org/jira/browse/GEODE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4351: - Component/s: (was: wan) (was: transactions) (was: statistics) (was: snapshot) (was: serialization) (was: rest (dev)) (was: rest (admin)) (was: regions) (was: redis) (was: pulse) (was: persistence) (was: offheap) (was: memcached) (was: membership) (was: management) (was: lucene) (was: logging) (was: locator) (was: jmx) (was: gfsh) (was: general) (was: functions) (was: extensions) (was: expiration) (was: eviction) (was: distributed lock service) (was: cq) (was: core) (was: configuration) (was: compression) (was: client/server) (was: client queues) > All instances of new File should use absolute path instead of relative "." > -- > > Key: GEODE-4351 > URL: https://issues.apache.org/jira/browse/GEODE-4351 > Project: Geode > Issue Type: Sub-task >Reporter: Kirk Lund >Priority: Major > > Since some Geode tests manipulate the system property "user.dir", all uses of > "new File(...)" must use absolute path. Otherwise the wrong path can end up > being logged or reported. > Note, this spans ALL of the Geode product code. Should we file a separate but > identical ticket for every API package or list every Component in this Jira > ticket? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4351) All instances of new File should use absolute path instead of relative "."
[ https://issues.apache.org/jira/browse/GEODE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4351: - Component/s: wan transactions statistics snapshot serialization rest (dev) rest (admin) regions redis pulse persistence offheap memcached membership management lucene logging locator jmx gfsh general functions extensions expiration eviction distributed lock service cq core configuration compression client/server client queues > All instances of new File should use absolute path instead of relative "." > -- > > Key: GEODE-4351 > URL: https://issues.apache.org/jira/browse/GEODE-4351 > Project: Geode > Issue Type: Sub-task > Components: client queues, client/server, compression, > configuration, core, cq, distributed lock service, eviction, expiration, > extensions, functions, general, gfsh, jmx, locator, logging, lucene, > management, membership, memcached, offheap, persistence, pulse, redis, > regions, rest (admin), rest (dev), serialization, snapshot, statistics, > transactions, wan >Reporter: Kirk Lund >Priority: Major > > Since some Geode tests manipulate the system property "user.dir", all uses of > "new File(...)" must use absolute path. Otherwise the wrong path can end up > being logged or reported. > Note, this spans ALL of the Geode product code. Should we file a separate but > identical ticket for every API package or list every Component in this Jira > ticket? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4335) Geode Native C++ Example (Put/get custom PDX objects that implements PDXSerializable
[ https://issues.apache.org/jira/browse/GEODE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4335: --- Summary: Geode Native C++ Example (Put/get custom PDX objects that implements PDXSerializable (was: Geode Native C++ Example (Put/get custom objects requiring custom serialization)) > Geode Native C++ Example (Put/get custom PDX objects that implements > PDXSerializable > > > Key: GEODE-4335 > URL: https://issues.apache.org/jira/browse/GEODE-4335 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4352) All instances of new File should use System.getProperty("user.dir") as parent File
[
https://issues.apache.org/jira/browse/GEODE-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-4352:
-
Description:
Since some Geode tests manipulate the system property "user.dir", all uses of
"new File(...)" must use System.getProperty("user.dir") as the parent File.
Otherwise the wrong path can end up being used.
Note, this spans ALL of the Geode product code. Should we file a separate but
identical ticket for every API package or list every Component in this Jira
ticket?
was:Since some Geode tests manipulate the system property "user.dir", all
uses of "new File(...)" must use System.getProperty("user.dir") as the parent
File. Otherwise the wrong path can end up being used.
> All instances of new File should use System.getProperty("user.dir") as parent
> File
> --
>
> Key: GEODE-4352
> URL: https://issues.apache.org/jira/browse/GEODE-4352
> Project: Geode
> Issue Type: Sub-task
>Reporter: Kirk Lund
>Priority: Major
>
> Since some Geode tests manipulate the system property "user.dir", all uses of
> "new File(...)" must use System.getProperty("user.dir") as the parent File.
> Otherwise the wrong path can end up being used.
> Note, this spans ALL of the Geode product code. Should we file a separate but
> identical ticket for every API package or list every Component in this Jira
> ticket?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4351) All instances of new File should use absolute path instead of relative "."
[ https://issues.apache.org/jira/browse/GEODE-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4351: - Description: Since some Geode tests manipulate the system property "user.dir", all uses of "new File(...)" must use absolute path. Otherwise the wrong path can end up being logged or reported. Note, this spans ALL of the Geode product code. Should we file a separate but identical ticket for every API package or list every Component in this Jira ticket? was:Since some Geode tests manipulate the system property "user.dir", all uses of "new File(...)" must use absolute path. Otherwise the wrong path can end up being logged or reported. > All instances of new File should use absolute path instead of relative "." > -- > > Key: GEODE-4351 > URL: https://issues.apache.org/jira/browse/GEODE-4351 > Project: Geode > Issue Type: Sub-task >Reporter: Kirk Lund >Priority: Major > > Since some Geode tests manipulate the system property "user.dir", all uses of > "new File(...)" must use absolute path. Otherwise the wrong path can end up > being logged or reported. > Note, this spans ALL of the Geode product code. Should we file a separate but > identical ticket for every API package or list every Component in this Jira > ticket? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4352) All instances of new File should use System.getProperty("user.dir") as parent File
[
https://issues.apache.org/jira/browse/GEODE-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-4352:
-
Description: Since some Geode tests manipulate the system property
"user.dir", all uses of "new File(...)" must use System.getProperty("user.dir")
as the parent File. Otherwise the wrong path can end up being used.
> All instances of new File should use System.getProperty("user.dir") as parent
> File
> --
>
> Key: GEODE-4352
> URL: https://issues.apache.org/jira/browse/GEODE-4352
> Project: Geode
> Issue Type: Sub-task
>Reporter: Kirk Lund
>Priority: Major
>
> Since some Geode tests manipulate the system property "user.dir", all uses of
> "new File(...)" must use System.getProperty("user.dir") as the parent File.
> Otherwise the wrong path can end up being used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4352) All instances of new File should use System.getProperty("user.dir") as parent File
Kirk Lund created GEODE-4352:
Summary: All instances of new File should use
System.getProperty("user.dir") as parent File
Key: GEODE-4352
URL: https://issues.apache.org/jira/browse/GEODE-4352
Project: Geode
Issue Type: Sub-task
Reporter: Kirk Lund
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4283) Improved Geode Native examples based on updated api
[ https://issues.apache.org/jira/browse/GEODE-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4283: --- Description: The goal of this ticket is to update the Geode Native examples. Geode Native has been standardizing its C++ API on C++ 11 that also includes changes to things like Cache creation and pooling. These examples should live in the geode-examples repo rather than geode-native /examples. The examples should include: C++ & C# API examples for * Cache creation, pooling, put/get/remove of basic types * Put/get of custom objects requiring custom serialization * OQL example * Server-side Function execution * Continuous query * SSL example * Authentication example C# API specific example * Put/get of custom objects using the PDXAutoserializaer All examples should include a start_server.sh, and a way to build the client code (vs project or cmake file) was: The goal of this ticket is to update the Geode Native examples. Geode Native has been standardizing its C++ API on C++ 11 that also includes changes to things like Cache creation and pooling. These examples should live in the geode-examples repo rather than geode-native /examples. The examples should include: C++ & C# API examples for * Cache creation, pooling, put/get/remove of basic types * Put/get of custom objects requiring custom serialization * OQL example * Server-side Function execution * Continuous query * SSL example * Authentication example C# API specific example * Put/get of custom objects using the PDXAutoserializaer All examples should include a start_server.sh or start_server.bat script, and a way to build the client code (vs project or cmake file) > Improved Geode Native examples based on updated api > --- > > Key: GEODE-4283 > URL: https://issues.apache.org/jira/browse/GEODE-4283 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > > The goal of this ticket is to update the Geode Native examples. Geode Native > has been standardizing its C++ API on C++ 11 that also includes changes to > things like Cache creation and pooling. These examples should live in the > geode-examples repo rather than geode-native /examples. > The examples should include: > C++ & C# API examples for > * Cache creation, pooling, put/get/remove of basic types > * Put/get of custom objects requiring custom serialization > * OQL example > * Server-side Function execution > * Continuous query > * SSL example > * Authentication example > C# API specific example > * Put/get of custom objects using the PDXAutoserializaer > All examples should include a start_server.sh, and a way to build the client > code (vs project or cmake file) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4351) All instances of new File should use absolute path instead of relative "."
Kirk Lund created GEODE-4351: Summary: All instances of new File should use absolute path instead of relative "." Key: GEODE-4351 URL: https://issues.apache.org/jira/browse/GEODE-4351 Project: Geode Issue Type: Sub-task Reporter: Kirk Lund Since some Geode tests manipulate the system property "user.dir", all uses of "new File(...)" must use absolute path. Otherwise the wrong path can end up being logged or reported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4322) Locator fails to start with NPE during join to the distributed system
[ https://issues.apache.org/jira/browse/GEODE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334622#comment-16334622 ] Anthony Baker commented on GEODE-4322: -- [~vaharonyan] thanks for the information. Normally we don't assign a target FixVersion without discussion on the dev list to confirm that someone is willing to commit to fixing the issue. We have already cut the release branch for 1.4.0 and I wouldn't be surprised to see a release candidate coming in the next day or so. Perhaps it would make sense to fix this bug in a patch release that follows soon after. > Locator fails to start with NPE during join to the distributed system > - > > Key: GEODE-4322 > URL: https://issues.apache.org/jira/browse/GEODE-4322 > Project: Geode > Issue Type: Bug > Components: membership >Affects Versions: 1.2.0 >Reporter: Vahram Aharonyan >Priority: Major > > Found out that after setting security-udp-dhalgo=AES:128 in prorperties files > sometimes locator is failing to come online with the following Exception: > [severe 2018/01/19 04:22:12.194 PST tid=0x45] > Exception in processing request from 10.144.248.41 > java.lang.RuntimeException: Not found public key for member > 16nodedata6(d4b4f5d4-47d2-44b1-a07c-6a7f5755e52d:11493):10002 > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:177) > at > org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.getPublicKey(JGroupsMessenger.java:1365) > at > org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:271) > at > org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1256) > at > org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:401) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.NullPointerException > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258) > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175) > ... 7 more > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.NullPointerException > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258) > at > org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175) > ... 7 more > Please note, that generally this issue is hit after cluster restart. This is > important, as during poweroff locator can go offline first and one of other > members will become coordinator and update view file accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2505) create region command should verify region attributes
[
https://issues.apache.org/jira/browse/GEODE-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-2505.
---
Resolution: Fixed
Fix Version/s: 1.4.0
The command already fails if the name exists. With the --skip-if-exists, the
command will succeed and skips creating region.
Creating new Jira ticket to change option --skip-if-exists to --if-not-exist.
> create region command should verify region attributes
> -
>
> Key: GEODE-2505
> URL: https://issues.apache.org/jira/browse/GEODE-2505
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Fix For: 1.4.0
>
>
> The gfsh {{create region}} command tries to be idempotent. If I try to create
> the same region twice I get the below message:
> {noformat}
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.
> {noformat}
> However, when a user is using a gfsh script to configure a cluster, and
> inadvertently changes the region attributes the {{create region}} command
> will still succeed.
> {noformat}
> gfsh>create region --name=foo --type=REPLICATE
> Member | Status
> -- |
> serv1 | Region "/foo" created on "serv1"
> gfsh>create region --name=foo --type=PARTITION
> Member | Status
> -- | --
> serv1 | Skipping "serv1". Region "foo" already exists.
> {noformat}
> We should verify the region attributes, and if the attributes don't match we
> should log an error asking the user to export the data from the existing
> region, destroy the region, create the region again with new attributes and
> import the data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4238) CI failure: RegionExpirationDUnitTest.testRegionTTLInvalidate
[
https://issues.apache.org/jira/browse/GEODE-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-4238.
--
Resolution: Fixed
Fix Version/s: 1.5.0
> CI failure: RegionExpirationDUnitTest.testRegionTTLInvalidate
> -
>
> Key: GEODE-4238
> URL: https://issues.apache.org/jira/browse/GEODE-4238
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Reporter: Nick Reich
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> {noformat}
> org.apache.geode.cache30.RegionExpirationDUnitTest > testRegionTTLInvalidate
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.RegionExpirationDUnitTest$6.run in VM 1 running on
> Host cad33bfaeb5e 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.cache30.RegionExpirationDUnitTest._testRegionTTL(RegionExpirationDUnitTest.java:217)
> at
> org.apache.geode.cache30.RegionExpirationDUnitTest.testRegionTTLInvalidate(RegionExpirationDUnitTest.java:96)
> Caused by:
> java.lang.AssertionError
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3981) Cache should not provide access to internal regions from public APIs
[ https://issues.apache.org/jira/browse/GEODE-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone resolved GEODE-3981. --- Resolution: Won't Fix > Cache should not provide access to internal regions from public APIs > > > Key: GEODE-3981 > URL: https://issues.apache.org/jira/browse/GEODE-3981 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Fred Krone >Priority: Major > Labels: geode-150 > > We should protect the user from accidentally modifying an internal region. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-3554: Assignee: Anilkumar Gingade (was: Kirk Lund) > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: cache, geode-150, pull-request-available > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks
[ https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-3554: Assignee: Kirk Lund > Document not invoking CacheFactory.getAnyInstance() from user callbacks > --- > > Key: GEODE-3554 > URL: https://issues.apache.org/jira/browse/GEODE-3554 > Project: Geode > Issue Type: New Feature > Components: core >Reporter: Fred Krone >Assignee: Kirk Lund >Priority: Major > Labels: cache, geode-150, pull-request-available > > As long as the product continues to invoke user plug-in callbacks during > startup (and with the main thread), we probably need to document a warning > not to use CacheFactory.getAnyInstance() as the API call is common in > plug-ins and this will freeze startup. > We are planning on deprecating and removing CacheFactory.getAnyInstance() > anyway. > Documentation should recommend using preferred APIs: > * FunctionContext.getCache() > * Event.getRegion().getCache() > We could expose Event.getCache() to make it more obvious to users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4015) CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Huynh resolved GEODE-4015.
Resolution: Fixed
> CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with
> AssertionError
> --
>
> Key: GEODE-4015
> URL: https://issues.apache.org/jira/browse/GEODE-4015
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
>
> Both testTwoRegionsTwoWriters and testTwoRegionsOneWriter failed with the
> same AssertionError:
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsTwoWriters FAILED
> java.lang.AssertionError: Test failed due to exception
> at org.apache.geode.test.dunit.Assert.fail(Assert.java:66)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:155)
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$193/1316585270.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:153)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms:
> null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsTwoWriters$bb17a952$10(ConflationDUnitTest.java:153)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsOneWriter FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$221/1553950035.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsOneWriter(ConflationDUnitTest.java:183)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms: null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsOneWriter$bb17a952$10(ConflationDUnitTest.java:183)
> {noformat}
> ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506) is
> waiting for {{counterUpdate == 2}}.
> I think this is a timing issue. The first line of the test sets
> CacheClientProxy.isSlowStartForTesting to true. This causes the
> MessageDispatcher to not send messages immediately. Instead, it waits for 5
> seconds before sending. This allows the queue to conflate the events. If I
> remove the slow start setting, the test fails every time because conflation
> doesn't happen.
> Unfortunately, the description returns null (the null in the AssertionError
> messages above), so we don't know anything about why the assertion is
> failing. If it were changed to return the actual value of counterUpdate, that
> would be helpful.
> With that change and the boolean not set in the test, I see:
> {noformat}
> Caused by: java.lang.AssertionError: Event never occurred after 6 ms:
> Expected counterUpdate to be 2. Instead it was 6
> {noformat}
> My guess is that between the time the MessageDispatcher is told to wait and
> the test actually runs, at least 5 seconds elapses, and the conflation
> doesn't occur. I'll make these changes to the test so that next time it
> happens, we can see if thats the case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4015) CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334546#comment-16334546
]
ASF subversion and git services commented on GEODE-4015:
Commit b690cfad68c95e60b237ebc9d316420be692998d in geode's branch
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b690cfa ]
GEODE-4015: Rewrite queue conflation tests (#1312)
* Refactored HARegionQueue to allow unit testing
> CI failure: ConflationDUnitTest.testTwoRegionsTwoWriters fails with
> AssertionError
> --
>
> Key: GEODE-4015
> URL: https://issues.apache.org/jira/browse/GEODE-4015
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
>
> Both testTwoRegionsTwoWriters and testTwoRegionsOneWriter failed with the
> same AssertionError:
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsTwoWriters FAILED
> java.lang.AssertionError: Test failed due to exception
> at org.apache.geode.test.dunit.Assert.fail(Assert.java:66)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:155)
> Caused by:
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$193/1316585270.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsTwoWriters(ConflationDUnitTest.java:153)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms:
> null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsTwoWriters$bb17a952$10(ConflationDUnitTest.java:153)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest >
> testTwoRegionsOneWriter FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest$$Lambda$221/1553950035.run
> in VM 2 running on Host 6b07584084c4 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.ConflationDUnitTest.testTwoRegionsOneWriter(ConflationDUnitTest.java:183)
> Caused by:
> java.lang.AssertionError: Event never occurred after 6 ms: null
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506)
> at
> org.apache.geode.internal.cache.tier.sockets.ConflationDUnitTest.lambda$testTwoRegionsOneWriter$bb17a952$10(ConflationDUnitTest.java:183)
> {noformat}
> ConflationDUnitTest.assertCounterSizes(ConflationDUnitTest.java:506) is
> waiting for {{counterUpdate == 2}}.
> I think this is a timing issue. The first line of the test sets
> CacheClientProxy.isSlowStartForTesting to true. This causes the
> MessageDispatcher to not send messages immediately. Instead, it waits for 5
> seconds before sending. This allows the queue to conflate the events. If I
> remove the slow start setting, the test fails every time because conflation
> doesn't happen.
> Unfortunately, the description returns null (the null in the AssertionError
> messages above), so we don't know anything about why the assertion is
> failing. If it were changed to return the actual value of counterUpdate, that
> would be helpful.
> With that change and the boolean not set in the test, I see:
> {noformat}
> Caused by: java.lang.AssertionError: Event never occurred after 6 ms:
> Expected counterUpdate to be 2. Instead it was 6
> {noformat}
> My guess is that between the time the MessageDispatcher is told to wait and
> the test actually runs, at least 5 seconds elapses, and the conflation
> doesn't
[jira] [Commented] (GEODE-4315) Convert JSONWrapper to an interface
[ https://issues.apache.org/jira/browse/GEODE-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334515#comment-16334515 ] ASF subversion and git services commented on GEODE-4315: Commit 6af617091b7e3da1bf1813e33b5c40f1806cd8b6 in geode's branch refs/heads/feature/GEODE-4315 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6af6170 ] GEODE-4315 Convert JSONWrapper to an interface JSONWrapper is now an interface. JSONWrapperImpl is what will be returned by the experimental driver but it will accept anything implementing JSONWrapper as input. > Convert JSONWrapper to an interface > --- > > Key: GEODE-4315 > URL: https://issues.apache.org/jira/browse/GEODE-4315 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > > The experimental Protobuf driver has a JSONWrapper class to hold JSON > documents. It would be nice if this can be changed to be an interface so > that I can write my own wrapper. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4345) Remove current geode-native examples
[ https://issues.apache.org/jira/browse/GEODE-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4345: --- Summary: Remove current geode-native examples (was: Remove Quickstarts) > Remove current geode-native examples > > > Key: GEODE-4345 > URL: https://issues.apache.org/jira/browse/GEODE-4345 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4282) createKey, createValue functions missing for many Serializable types.
[ https://issues.apache.org/jira/browse/GEODE-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334510#comment-16334510 ] ASF subversion and git services commented on GEODE-4282: Commit c6b424670a13015d44ce594b7e5e175c259bbbd9 in geode-native's branch refs/heads/wip/createValue-2 from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c6b4246 ] GEODE-4282: Remove createKey/Value templates. - Use Serializable::create to specialize for creating cacheable objects. - Use CacheableKey::create to specialize for creating key objects. > createKey, createValue functions missing for many Serializable types. > - > > Key: GEODE-4282 > URL: https://issues.apache.org/jira/browse/GEODE-4282 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > Serializable/CacheableKey::create method needs namespace functions > createValue/createKey for each of the supported primitive types. Many of > these types are missing as a result of bad refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4350) Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
[
https://issues.apache.org/jira/browse/GEODE-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett reassigned GEODE-4350:
---
Assignee: Jacob S. Barrett
> Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
> ---
>
> Key: GEODE-4350
> URL: https://issues.apache.org/jira/browse/GEODE-4350
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>
> {{overrides a member function but is not marked 'override'}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4031) Update CacheSnapshotService javadocs for .gfd requirement
[ https://issues.apache.org/jira/browse/GEODE-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334503#comment-16334503 ] ASF subversion and git services commented on GEODE-4031: Commit c1cf5d1505f35d6352d43969ef6f74a2fcb6b516 in geode's branch refs/heads/develop from [~nreich] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c1cf5d1 ] GEODE-4031: Update javadocs to include .gfd snapshot extension requirement (#1311) > Update CacheSnapshotService javadocs for .gfd requirement > - > > Key: GEODE-4031 > URL: https://issues.apache.org/jira/browse/GEODE-4031 > Project: Geode > Issue Type: Sub-task > Components: snapshot >Affects Versions: 1.3.0 >Reporter: Fred Krone >Assignee: Nick Reich >Priority: Minor > > Would like to note in the documentation > http://geode.apache.org/docs/guide/13/managing/cache_snapshots/exporting_a_snapshot.html > that "The file must have an extension of .gfd" -- just like in the import / > export docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4350) Fix testThinClientRIwithlocalRegionDestroy warnings regarding override.
Jacob S. Barrett created GEODE-4350:
---
Summary: Fix testThinClientRIwithlocalRegionDestroy warnings
regarding override.
Key: GEODE-4350
URL: https://issues.apache.org/jira/browse/GEODE-4350
Project: Geode
Issue Type: Improvement
Components: native client
Reporter: Jacob S. Barrett
{{overrides a member function but is not marked 'override'}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-2443) Update to CMake 3.8
[ https://issues.apache.org/jira/browse/GEODE-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-2443: --- Priority: Minor (was: Major) > Update to CMake 3.8 > --- > > Key: GEODE-2443 > URL: https://issues.apache.org/jira/browse/GEODE-2443 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Minor > > Cmake has RC'd 3.8 with support for C# - this needs to be looked to see if it > works well and to see what (if any) changes we need to make in order to > migrate to 3.8 > Currently we configurate csproj.in files, this presumably would go away > We would need to update CI images to have cmake 3.8. > Fixes issues with detecting CPU counts on Solaris. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4323) CI failure: DestroyAsyncEventQueueCommandDUnitTest > destroyAeqOnGroup_returnsSuccess FAILED
[
https://issues.apache.org/jira/browse/GEODE-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334465#comment-16334465
]
Jens Deppe commented on GEODE-4323:
---
I think this just needs a slight timeout increase.
> CI failure: DestroyAsyncEventQueueCommandDUnitTest >
> destroyAeqOnGroup_returnsSuccess FAILED
>
>
> Key: GEODE-4323
> URL: https://issues.apache.org/jira/browse/GEODE-4323
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Jens Deppe
>Priority: Minor
> Labels: ci
>
> {noformat}
> org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest
> > destroyAeqOnGroup_returnsSuccess FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.MemberVM$$Lambda$43/1844085674.run in VM 0
> running on Host b7b8ffa56166 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.test.dunit.rules.MemberVM.waitTillAsyncEventQueuesAreReadyOnServers(MemberVM.java:125)
> at
> org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest.destroyAeqOnGroup_returnsSuccess(DestroyAsyncEventQueueCommandDUnitTest.java:128)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.geode.test.junit.rules.MemberStarterRule was not
> fulfilled within 2 seconds.
> {noformat}
> From the log file:
> {noformat}
> [vm1] [info 2018/01/18 02:27:15.410 UTC
> tid=0x28b] Initializing region gatewayEventIdIndexMetaData
> [vm1] [info 2018/01/18 02:27:15.414 UTC
> tid=0x28b] Initialization of region gatewayEventIdIndexMetaData completed
> [vm1] [info 2018/01/18 02:27:15.420 UTC
> tid=0x28b]
> SerialGatewaySender{id=AsyncEventQueue_queue1,remoteDsId=-1,isRunning
> =false,isPrimary =false} : Starting as primary
> [vm1] [info 2018/01/18 02:27:15.420 UTC
> tid=0x28b]
> SerialGatewaySender{id=AsyncEventQueue_queue1,remoteDsId=-1,isRunning
> =false,isPrimary =false} : Becoming primary gateway sender
> [vm1] [info 2018/01/18 02:27:15.427 UTC
> tid=0x28b] Created disk store DEFAULT with unique id
> f0647d731b4d4cb8-b0bc4687e0e76601
> [vm1] [info 2018/01/18 02:27:15.429 UTC
> tid=0x28b] recovery region initialization took 0 ms
> [vm1] [info 2018/01/18 02:27:15.430 UTC
> tid=0x28b] Initializing region
> AsyncEventQueue_queue1_SERIAL_GATEWAY_SENDER_QUEUE
> [vm1] [info 2018/01/18 02:27:15.432 UTC
> tid=0x28b] Initialization of region
> AsyncEventQueue_queue1_SERIAL_GATEWAY_SENDER_QUEUE completed
> [vm1] [info 2018/01/18 02:27:15.433 UTC
> tid=0x28b] Started
> SerialGatewaySender{id=AsyncEventQueue_queue1,remoteDsId=-1,isRunning
> =true,isPrimary =true}
> [vm1] [info 2018/01/18 02:27:15.449 UTC
> tid=0x28b] XmlEntity:searchString: //cache:async-event-queue[@id='queue1']
> Command result for --listener=org.apache.geode.internal.cache.wan.MyAsyncEventListener>:
> Member | Status
> | ---
> server-1 | Success
> [vm0] [info 2018/01/18 02:27:15.507 UTC
> tid=0x1e] Received method:
> org.apache.geode.test.dunit.rules.MemberVM$$Lambda$62/1255991289.run with 0
> args on object:
> org.apache.geode.test.dunit.rules.MemberVM$$Lambda$62/1255991289@2a4f3731
> [vm0] [info 2018/01/18 02:27:17.522 UTC
> tid=0x1e] Got result: EXCEPTION_OCCURRED
> [vm0] org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.geode.test.junit.rules.MemberStarterRule was not
> fulfilled within 2 seconds.
> [vm0] at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> [vm0] at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> [vm0] at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> [vm0] at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> [vm0] at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:785)
> [vm0] at
> org.apache.geode.test.junit.rules.MemberStarterRule.waitTillAsyncEventQueuesAreReadyOnServers(MemberStarterRule.java:274)
> [vm0] at
> org.apache.geode.test.dunit.rules.MemberVM.lambda$waitTillAsyncEventQueuesAreReadyOnServers$f5a8cdec$1(MemberVM.java:126)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0]
[jira] [Created] (GEODE-4349) Geode Native C# Example (Authentication)
Addison created GEODE-4349: -- Summary: Geode Native C# Example (Authentication) Key: GEODE-4349 URL: https://issues.apache.org/jira/browse/GEODE-4349 Project: Geode Issue Type: Sub-task Components: native client Reporter: Addison -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4347) Geode Native C# Example (Continuous Query)
Addison created GEODE-4347: -- Summary: Geode Native C# Example (Continuous Query) Key: GEODE-4347 URL: https://issues.apache.org/jira/browse/GEODE-4347 Project: Geode Issue Type: Sub-task Components: native client Reporter: Addison -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4348) Geode Native C# Example (SSL example)
Addison created GEODE-4348: -- Summary: 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4346) Geode Native C# Example (Server-side function example)
Addison created GEODE-4346: -- Summary: Geode Native C# Example (Server-side function example) Key: GEODE-4346 URL: https://issues.apache.org/jira/browse/GEODE-4346 Project: Geode Issue Type: Sub-task Components: native client Reporter: Addison -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4345) Remove Quickstarts
Addison created GEODE-4345: -- Summary: Remove Quickstarts Key: GEODE-4345 URL: https://issues.apache.org/jira/browse/GEODE-4345 Project: Geode Issue Type: Sub-task Components: native client Reporter: Addison -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4344) Geode Native C# Example (QQL)
Addison created GEODE-4344: -- Summary: Geode Native C# Example (QQL) Key: GEODE-4344 URL: https://issues.apache.org/jira/browse/GEODE-4344 Project: Geode Issue Type: Sub-task Reporter: Addison -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4343) Geode Native C# Example (put/get of custom objects using PDXAutoserializer)
Addison created GEODE-4343: -- Summary: Geode Native C# Example (put/get of custom objects using PDXAutoserializer) Key: GEODE-4343 URL: https://issues.apache.org/jira/browse/GEODE-4343 Project: Geode Issue Type: Sub-task Components: native client Reporter: Addison -- This message was sent by Atlassian JIRA (v7.6.3#76005)
