Make WebConsole run as a standalone WAR
---------------------------------------
Key: AMQ-1241
URL: https://issues.apache.org/activemq/browse/AMQ-1241
Project: ActiveMQ
Issue Type: Improvement
Affects Versions: 4.2.0
Reporter: Mario Siegenthaler
The WebConsole is a really nice thing, however you should be able to run it as
a standalone war connecting to a remote broker (another vm or another server).
This improves the following (IMO):
* stability of the broker itself as the web-console can f.e. eat up all
available memory (try looking at a large queue) or do other bad things
* deployment (many companys have a standard deployment process for war-files
as well as preconfigured application server to put them into)
* backward-compatibility (webconsole per se does not depend on a 4.2 broker,
it runs just fine with 4.1 and 4.0)
* support for master-slave configurations with auto-failover (f.e. with a
failover jmx syntax as well as the existing failover syntax for the jms
connection)
Related to this bug/improvement is the current mean behaviour of the
web-console with non-default named brokers (sometimes using the web-console
will end up in a second broker beeing started).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
