Return-Path: X-Original-To: apmail-bloodhound-user-archive@www.apache.org Delivered-To: apmail-bloodhound-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1DA1C1037E for ; Thu, 30 Jan 2014 01:46:03 +0000 (UTC) Received: (qmail 75786 invoked by uid 500); 30 Jan 2014 01:46:02 -0000 Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org Received: (qmail 75764 invoked by uid 500); 30 Jan 2014 01:46:02 -0000 Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bloodhound.apache.org Delivered-To: mailing list user@bloodhound.apache.org Received: (qmail 75750 invoked by uid 99); 30 Jan 2014 01:46:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 01:46:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryan.ollos@wandisco.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 01:45:58 +0000 Received: by mail-ob0-f175.google.com with SMTP id wn1so2848681obc.20 for ; Wed, 29 Jan 2014 17:45:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wandisco.com; s=gapps; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Scc5KkzB+gDEMa0LxMZ2705DwEgY3RzwylB9dnToGSk=; b=oluwfv5C/FlKXmRHiy2xxRgXKn4xAtqo5Ww8w3Cg8JgDQznD9BkOLBgmU8dFrVy1N8 aFEN0EaVt8bVRqbe/mnB4vQZi+N1GNMW5K9u3G0dsuQRopH8VQ3pgCw8Gde2JA32gum+ qXi1iGMom6ZyKaGUpCD0bhezCKuuRqBQzjXL8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Scc5KkzB+gDEMa0LxMZ2705DwEgY3RzwylB9dnToGSk=; b=hzY+mDlbaf3VCRt/q1km4G81WVoVoXM0uOSs/m1GusB7kqauD8D4o6bNtJAqjfWKaA N3h7gyedE5+dhBtpQGRiGBW++pmxVobMkPdBT06yHVAiZFPEoRMn4nvOlhu/Fgo9U8/g C8NB8DhtohSahbG2CbIp4uewitO0m1cs1imPmvhwAxOx4FszEscYYzbQHeX7sGSIzOtF Ut1gGLDGuJARoDFQ8KJ25HYzGaDVh/DvKpDAjMXHV756OlwOeoeiv0R2gNoRs3IHqAMf 01MPglssjzGMl9fgRz7W7iNIc14CLQvxWf7Qju0IvlKp0ZLc56dWvsMWOf/Q3kAJsfz+ BLDg== X-Gm-Message-State: ALoCoQnExvu+KQtzbVRZYVGmsw1jfeI/rsNQZNfU299vXKpKIlxrzsN/mnqPHH5LlS7ipgtKc0Z1 MIME-Version: 1.0 X-Received: by 10.60.159.133 with SMTP id xc5mr9075157oeb.37.1391046336291; Wed, 29 Jan 2014 17:45:36 -0800 (PST) Received: by 10.60.103.237 with HTTP; Wed, 29 Jan 2014 17:45:36 -0800 (PST) In-Reply-To: <52E768A6.5020009@asygn.com> References: <52E67EFA.5080001@asygn.com> <52E768A6.5020009@asygn.com> Date: Wed, 29 Jan 2014 17:45:36 -0800 Message-ID: Subject: Re: Reload product configuration From: Ryan Ollos To: user@bloodhound.apache.org Content-Type: multipart/alternative; boundary=047d7bd6c620bdb8ae04f12636fc X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd6c620bdb8ae04f12636fc Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 28, 2014 at 12:21 AM, Eric Jouffrey wrote: > I used the solution in #695, but maybe not the version that you send 10 > days ago. I'm going check differences see if there is some improvement. > > My repository was defined using web configuration and it's linked to a > product. > > I'm going to try the repository_sync_per_request option. By reload > configuration I was thinking that's basically what's happen when you change > the log level for example (what resync all changeset) > And in our configuration we're using a SQLite database. I've also add some > no-cache pragma to templates headers for be sure it wasn't any browser > cache issues. And for the "kill -s HUP $PID", it don't seem to do the > trick. > > I've already done few more tests. And maybe there is something similar on > granting right for a product. When I grant new right for a user or a group > at product level, each refresh of permission page display randomly that new > right or not. Granting right for global level is perfect. > The issue you've reported can be tracked in ticket #748, https://issues.apache.org/bloodhound/ticket/748 Thank you for your careful and detailed description. --047d7bd6c620bdb8ae04f12636fc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Tue, Jan 28, 2014 at 12:21 AM, Eric Jouffrey <eric.jouffrey@asygn= .com> wrote:
=20 =20 =20
I used the solution in #695, but maybe not the version that you send 10 days ago. I'm going check differences se= e if there is some improvement.

My repository was defined using web configuration and it's linked to a product.

I'm going to try the repository_sync_per_request option. By reloa= d configuration I was thinking that's basically what's happen w= hen you change the log level for example (what resync all changeset)
And in our configuration we're using a SQLite database. I've = also add some no-cache pragma to templates headers for be sure it wasn't any browser cache issues. And for the "
kill -s HUP =A0$PID&q= uot;, it don't seem to do the trick.

I've already done few more tests. And maybe there is something similar on granting right for a product. When I grant new right for a user or a group at product level, each refresh of permission page display randomly that new right or not. Granting right for global level is perfect.=A0

The issue you've reported can be tracked in ticket #748,
<= div>https://iss= ues.apache.org/bloodhound/ticket/748

Thank you for your careful and detailed description.
--047d7bd6c620bdb8ae04f12636fc--