Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <771905290912211317v7834af08g54025f8d6c73b682@mail.gmail.com>
References: <771905290912211317v7834af08g54025f8d6c73b682@mail.gmail.com>
Date: Mon, 21 Dec 2009 14:44:53 -0800
Message-ID: <160274c80912211444l35ea398arbaec3c4202f2d1a0@mail.gmail.com>
Subject: Re: Performance issue on Stax not reproducible locally
From: Spike Washburn <spike@washburnnet.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=000e0cd5c9e6826e7f047b44d6aa

--000e0cd5c9e6826e7f047b44d6aa
Content-Type: text/plain; charset=ISO-8859-1

Markus,

If you created the New Relic account directly on the new relic site (as
opposed to using the Stax wizard), make sure your New Relic account has API
access enabled.

On Stax performance, are you thinking this is a DB-layer issue or an
Appserver issue?  I saw Dick mentioned that performance was fine when
running in the beta cloud.  If you try switching the deployment
configuration back to using the Stax Beta Cloud environment instead of the
dedicated EC2 environment, that would narrow the issue to the type of
deployment which we could help debug.

-Spike

---
Spike Washburn
Stax Networks

On Mon, Dec 21, 2009 at 1:17 PM, Markus Kohler <markus.kohler@gmail.com>wrote:

> Hi all,
> I just updated my local ESME to the latest SVN version and it's really
> fast.
>
> I tried to enable New Relic on the stax performance instance, but it
> wouldn't work. When I enter my license key I only get an "unknown error" or
> something similar meaningless.
> Not sure whether just entering the license key is enough, or whether I have
> to install something.
>
>
> Regards,
> Markus
>
>
> "The best way to predict the future is to invent it" -- Alan Kay
>

--000e0cd5c9e6826e7f047b44d6aa--