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 DE77A200D28 for ; Mon, 23 Oct 2017 19:53:33 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DCED21609E0; Mon, 23 Oct 2017 17:53:33 +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 2F26C1609DF for ; Mon, 23 Oct 2017 19:53:33 +0200 (CEST) Received: (qmail 28458 invoked by uid 500); 23 Oct 2017 17:53:27 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 28448 invoked by uid 99); 23 Oct 2017 17:53:27 -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; Mon, 23 Oct 2017 17:53:27 +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 A0CCEC6135 for ; Mon, 23 Oct 2017 17:53:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.172 X-Spam-Level: ** X-Spam-Status: No, score=2.172 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972] 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 3nzPoeq70SPy for ; Mon, 23 Oct 2017 17:53:26 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 59B4960DDA for ; Mon, 23 Oct 2017 17:53:25 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 4EE6F26E0C51 for ; Mon, 23 Oct 2017 10:53:23 -0700 (MST) Date: Mon, 23 Oct 2017 10:53:23 -0700 (MST) From: whcmachado To: user@ignite.apache.org Message-ID: <1508781203320-0.post@n6.nabble.com> In-Reply-To: References: <1508506343910-0.post@n6.nabble.com> Subject: Re: Ignite Web Session Clustering MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 23 Oct 2017 17:53:34 -0000 Hello! First, I'm sorry for my late reply. I didn't close my web browser between those tests. But as you talked about cookies, I looked at the cookies on chrome developer tools and for some unknow reason I had a cookie for '/' and '/Ignite-WebApp'. I cleaned those cookies and everything works well now. Now we're going to try to set up Ignite on our main project which uses frameworks like Jboss Seam 2.2.1.CR1, JSF 1.2_15, Facelets 1.1.14, Richfaces 3.3.3, Hibernate 3.3.2, c3p0 0.9.1.2, Spring 3.1.3 and Servlet 2.5 (maybe we can update the Servlet version, but not the others). As we're not using the most recent versions of those frameworks and there are sommething like Seam contexts, do you think that our application is suitable for Ignite Web Session Clustering? Do you have any advice? I really appreciate any help you can provide. Thank you! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/