Return-Path: 
 <derby-dev-return-95012-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-derby-dev-archive@www.apache.org
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BB11D9ED5
	for <apmail-db-derby-dev-archive@www.apache.org>;
 Fri, 20 Apr 2012 20:52:08 +0000 (UTC)
Received: (qmail 39917 invoked by uid 500); 20 Apr 2012 20:52:08 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 39882 invoked by uid 500); 20 Apr 2012 20:52:08 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 39875 invoked by uid 99); 20 Apr 2012 20:52:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2012 20:52:08 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of msatoor@gmail.com designates
 209.85.210.172 as permitted sender)
Received: from [209.85.210.172] (HELO mail-iy0-f172.google.com)
 (209.85.210.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2012 20:52:02 +0000
Received: by iazz13 with SMTP id z13so16915633iaz.31
        for <derby-dev@db.apache.org>; Fri, 20 Apr 2012 13:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=kC60O7W3M+Y30Pbh2Jl2QPaaheNDEzp31E9MC77r7Z0=;
        b=bsv1hpZRT0uVoAHejeyDiSvlo5rXQubZm4eXUWuWOYGXFn4/SOjyB3/+PAKzpz+RPI
         E89BwK2CIEK1JO782HObQc8NaYT02wwh8Lkwh3nAGwGZKWZ8TSnIQc74ospQ0C1GF46x
         Wbxvba5Izz60ukBviHMdxSBZw7xkovuKFVb5Y0rdG92LKi16c2yWj5A9zL9YbWz0v2PM
         6gVEwcR9xgZ/wx0/WGrU6xuLr/HpXg2nkwhasr4Q+WD/Q5jwqdwfp9hV9PnJFLynNDsv
         HqK9NO2jZcW9LVMAJJA2kPqt1Gx9q9AB8cm4bsWNUQ3eA0CnDlKa3TM7FH3SCJc95CIU
         2cRw==
MIME-Version: 1.0
Received: by 10.50.183.225 with SMTP id ep1mr4095055igc.1.1334955101680; Fri,
 20 Apr 2012 13:51:41 -0700 (PDT)
Received: by 10.231.80.9 with HTTP; Fri, 20 Apr 2012 13:51:41 -0700 (PDT)
In-Reply-To: <4F91C9B0.9050201@sbcglobal.net>
References: 
 <CAFy7pk9w5p+resQqJCpQq+zsDwqHQZ8r9YGeSpj1ysrQDseu=Q@mail.gmail.com>
	<4F91C9B0.9050201@sbcglobal.net>
Date: Fri, 20 Apr 2012 13:51:41 -0700
Message-ID: 
 <CAFy7pk-bZUKhtmQwDaHaTCneBYn8_mqPrhi=JLn1_D9XuJsEtA@mail.gmail.com>
Subject: Re: Is anyone else experiencing problems accessing jira?
From: Mamta Satoor <msatoor@gmail.com>
To: derby-dev@db.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Looks like jira is back

On Fri, Apr 20, 2012 at 1:40 PM, Katherine Marsden
<kmarsdenderby@sbcglobal.net> wrote:
> On 4/20/2012 1:14 PM, Mamta Satoor wrote:
>>
>> Hi,
>>
>> I am unable to create a new jira or access an existing one.
>
>
> I cannot access Jira either. At the moment the error is 502 Bad Gateway but
> I have had some others including the one you had in the last 15 minutes or
> so. The fact that the error is changing makes me hopeful someone is working
> on it :-)
>