activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac" <>
Subject Re: WebConsole in embedded mode
Date Sun, 10 Jun 2007 12:51:52 GMT

I've recently integrated web console in one of my projects, some of the
impressions are:


* default webconsole-embedded.xml does not do the job (as it is starting its
own broker). As Mario suggested, default invm configuration or version of
embbeded configuration that is included in ActiveMQ assembly process would
do the job.

* I didn't want to use the whole war, but to extract the console inside my
application. I found that most of the JARs are already in my classpath, so I
excluded them in the extraction process. Also, if it is not done so, there
are some classloading problems that I've experienced. If in the assembly
process we create one archive that is prepared for this purpose, more people
would be using it?

* I think that ActiveMQ could benefit from version 2.2 of the maven-assembly
plugin, as it supports excluding of resources from the war archive. It would
make assembly process cleaner (for the purpose of integrating web console).


On 6/9/07, Mario Siegenthaler <> wrote:
> James, you have configured to run the webconsole in the embedded mode
> within the activemq.xml ('standalone' activemq). Why don't we use the
> invm-mode of the webconsole there? I think it's the correct usage of
> this mode as we don't want to start a second broker but use the one
> that's been started in the VM. What is the benefit of the embedded
> mode in this case?
> Aside from that the webconsole-embedded contains an error with the
> queueBrowser and the message query (spring-cleanup does not work and
> it leaves consumers open). I'll submit a patch for this as soon as
> I've got my head cleared about the invm-mode :)
> Thanks for clarifications
> Mario

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message