activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robparrott <robparr...@gmail.com>
Subject Re: web-console with non-embedded broker
Date Mon, 05 Feb 2007 13:13:37 GMT

HI James,

Can you describe in "lite" detail what would be needed to perform this
refactoring? What classes, etc.?

This would help me (and others, I suppose) assess whether I might take it
on.

thanks,
rob




James.Strachan wrote:
> 
> Currently the Web Console is directly using the embedded broker (as it
> was the simplest way to get started); we'd need to do a bit of
> refactoring to be able to use the web console to connect to a remote
> broker over JMX. It shouldn't be too hard to do if anyone fancies
> taking a stab at a patch?
> 
> http://activemq.apache.org/contributing.html
> 
> On 2/4/07, robparrott <robparrott@gmail.com> wrote:
>>
>> Hi Folks,
>>
>> I'm trying to setup the ActiveMQ web-console with an ActiveMQ broker that
>> is
>> embedded in another application. I've been unable to get this setup
>> working
>> at all.
>>
>> The version of ActiveMQ is 4.1 all around. I'm using Java 1.5 on MacOS X
>> 10.4, and on linux.
>>
>> The embedded Active MQ browser ia at port 61616 on localhost, has name
>> "OMS_BROKER", and has the JMX console enabled.
>>
>> I've modified the
>> activemq-4.1/activemq-web-console/src/main/webapp/WEB-INF
>> files to avoid the collision in port number with the embedded borker in
>> the
>> web-console app as well. (I found that changing the target/* files had no
>> effect when tarting with "mvn jetty:run").
>>
>> In the activemq.xml config file here,
>>
>>   1) I've set useJmx="false" broker element to avoid conflicts with the
>> other broker & JMX
>>   2) changed the openwire transport port to 61617 to avoid conflicts with
>> 61616 of the embedded broker
>>   3) set a network connecter to
>>
>>          <networkConnector name="OMS_BROKER"
>> uri="static://(tcp://localhost:61616)" failover="true"/>
>>
>>      in addition to the multicast connector.
>>
>> I've also turned off the transportConnectors altogether, by commenting
>> out
>> that section of the activemq.xml
>>
>> While these changes allow the web-console to start, I cannot browse the
>> embedded Broker. I see no Topics or queues available.
>>
>> Can someone advise me on how to use the web-console to browse a broker
>> besides the one started by the web-console application?
>>
>> It seems that the web-console would have limitied utility without this
>> ability, and documentation of the procedure.
>>
>> Thanks for any insight you might provide.
>>
>>
>> rob
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/web-console-with-non-embedded-broker-tf3170794.html#a8795680
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> 
> James
> -------
> http://radio.weblogs.com/0112098/
> 
> 

-- 
View this message in context: http://www.nabble.com/web-console-with-non-embedded-broker-tf3170794.html#a8805900
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message