Thanks for all the help.

Best regards,
Paulo Cavaleiro

On Wed, Oct 29, 2008 at 2:47 PM, Ian Springer <ian.springer@redhat.com> wrote:
We generally don't recommend deploying any production applications to the RHQ AS instance. An example of why this is bad is if the application had a memory leak and caused the AS JVM to run out of memory, then RHQ would not be able to alert you, because it would have gone down itself, since it was running in the same app server.


On 10/29/2008 10:05 AM, Paulo Cavaleiro wrote:
Hi Ian,

What is intended is to have all in one machine, the RHQ server (JOPR
distribution) and the war application that is intended to monitor.
So to have only one JBoss AS running it would be better to deploy all

Paulo Cavaleiro

On Wed, Oct 29, 2008 at 12:54 PM, Ian Springer<ian.springer@redhat.com>wrote:

Hi Paulo,

It would not be easy to do, since we make lots of modifications to the
underlying JBossAS 4.2.1 distribution. To see what I mean, take a look at:


This is the Ant script that starts from a vanilla AS 4.2.1 dist and
adds/removes/tweaks all sorts of things, from deployed apps to

Running the RHQ Server in its own dedicated app server is also desirable,
because it is then guaranteed to not interfere with any other applications,
or vice verse.

Out of curiosity, why were you thinking of deploying the RHQ Server to an
existing AS instance?


On 10/29/2008 8:06 AM, Paulo Cavaleiro wrote:


Is there way of deploying the RHQ Server in an existing JBoss AS?
I wanted to have the RHQ Server running but not using the JBoss AS that
with the distribution.

Best regards,
Paulo Cavaleiro


This SF.Net email is sponsored by the Moblin Your Move Developer's
Build the coolest Linux based applications with Moblin SDK&   win great
Grand prize is a trip for two to an Open Source event anywhere in the

Rhq-user mailing list