Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2D988200D29 for ; Wed, 11 Oct 2017 19:58:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2C1DC1609BB; Wed, 11 Oct 2017 17:58:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 70F05160BE3 for ; Wed, 11 Oct 2017 19:58:05 +0200 (CEST) Received: (qmail 24165 invoked by uid 500); 11 Oct 2017 17:58:04 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 24144 invoked by uid 99); 11 Oct 2017 17:58:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2017 17:58:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 910CCDB19D for ; Wed, 11 Oct 2017 17:58:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 5iPivFhJZSFy for ; Wed, 11 Oct 2017 17:58:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C83BD60FA3 for ; Wed, 11 Oct 2017 17:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 410E5E0FCE for ; Wed, 11 Oct 2017 17:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 828BA253A2 for ; Wed, 11 Oct 2017 17:58:00 +0000 (UTC) Date: Wed, 11 Oct 2017 17:58:00 +0000 (UTC) From: "Jason Huynh (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEODE-3809) Invalid OQL result to region with entry-idle-time setting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 11 Oct 2017 17:58:06 -0000 [ https://issues.apache.org/jira/browse/GEODE-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200684#comment-16200684 ] Jason Huynh commented on GEODE-3809: ------------------------------------ It looks like the entry is getting it's last access time updated in the local client cache. That is why the gets continue to work. However the server does not have its last access time updated and then expires the entry. That is why the query is no longer returning a value but the client still is able to do a get. If you change the client cache to PROXY instead of LOCAL, the query 3 will now return the correct value because the gets would have updated the servers last access time for that entry. If you go back to the LOCAL configuration (and let's ignore queries at this time), you will still have the scenario where you do gets on the client cache and the server doesn't get accessed. The server will expire the entry same as before, but if you register interest from the client, the client would at least receive the destroy and the local gets would now return null. Queries, currently, do not update the last access time for the entry. I've opened GEODE-3811: Queries should update the access time of an entry. > Invalid OQL result to region with entry-idle-time setting > --------------------------------------------------------- > > Key: GEODE-3809 > URL: https://issues.apache.org/jira/browse/GEODE-3809 > Project: Geode > Issue Type: Bug > Components: querying > Reporter: Masaki Yamakawa > > I am setting the expiration of entry-idle-time to Region. Despite periodic access to the region, I discovered an event that data can not be get with OQL after the time set by entry-idle-time has elapsed. I am using Geode in the production, so I want you to solve this problem as soon as possible. > The cache.xml of the server is as follows: > {code:xml} > > > > > > > > > > > {code} > The source code of the client is as follows: > {code:java} > private static final Integer KEY = 1; > public static void main(String[] args) throws Exception { > Properties props = new Properties(); > props.setProperty("cache-xml-file", "clientcache.xml"); > ClientCacheFactory factory = new ClientCacheFactory(props); > ClientCache cache = factory.create(); > Region region = cache.getRegion("Data"); > region.put(KEY, "InitialValue"); > Thread.sleep(7000); > System.out.println("Get Result1=" + region.get(1)); > Pool pool = PoolManager.find("ClientPool"); > Query query = pool.getQueryService().newQuery("select k from /Data.keySet k"); > // Normal OQL result > SelectResults result = SelectResults.class.cast(query.execute()); > System.out.println("Get Result2=" + region.get(1)); > System.out.println("Query Result2=" + result.size() + ", value=" + result.iterator().next()); > Thread.sleep(5000); > // Invalid OQL result!!! > result = SelectResults.class.cast(query.execute()); > System.out.println("Get Result3=" + region.get(1)); > System.out.println("Query Result3=" + result.size() + ", value=" + (result.isEmpty() ? null : result.iterator().next())); > System.out.println("Get Result4=" + region.get(1)); > cache.close(); > System.exit(0); > } > {code} > {code:xml} > > > > > > > > > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)