You need to use system properties to define how to connect to the broker.
See here for more info

http://activemq.apache.org/web-console.html#WebConsole-ConfigureusingSystemProperties

<http://activemq.apache.org/web-console.html#WebConsole-ConfigureusingSystemProperties>In
order to authenticate JMS part of the console you need to add

webconsole.jms.user

and

webconsole.jms.password

system properties

Regards
-- 
Dejan Bosanac
-----------------
FuseSource - The experts in open source integration and messaging.
Email: dej...@fusesource.com
Web: http://fusesource.com
Twitter:  http://twitter.com/dejanb
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Wed, Mar 30, 2011 at 2:40 AM, TheFarmer <matt_g...@yahoo.com> wrote:

> I have the console running in its own Jetty server.  I downloaded this a
> week
> ago so it was the latest version then.  It all works fine until I turn on
> authentication in the ActiveMQ server.  Then I can list queues but browsing
> them fails with userName/password error.  (My client works fine with
> authentication so I know the ActiveMQ config is good)
>
> I followed the directions in the Web Console section of
> http://activemq.apache.org/security.html and no difference - still
> userName/password error.  The ActiveMQ server log showed a null userName.
>
> I put bad xml in webconsole-embedded.xml and got no errors making me think
> that file is not used.
>
> I followed the same directions but changed the webconsole-properties.xml
> file and then I was able to browse a queue but the list was empty even
> though there are messages pending in the queue.  This also resulted in the
> following error in the web server log and then it looked like it tried to
> start ActiveMQ in Jetty.  Doesn't make any sense to me.
>
> Did something change recently with how the web console is configured?
>
> 2011-03-29 18:34:20,185 [JMX connector  ] WARN  ManagementContext
> -
>  Failed to start jmx connector: Cannot bind to URL
> [rmi://localhost:1099/jmxrmi]
> : javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
> java.rmi.Alr
> eadyBoundException: jmxrmi]
> 2011-03-29 18:34:20,263 [tp-1759557365-7] INFO  PListStore
> -
>  PListStore:activemq-data\localhost\tmp_storage started
> 2011-03-29 18:34:20,266 [tp-1759557365-7] INFO  BrokerService
> -
>  Using Persistence Adapter:
> KahaDBPersistenceAdapter[activemq-data\localhost\Kah
> aDB]
> 2011-03-29 18:34:20,814 [tp-1759557365-7] INFO  MessageDatabase
> -
>  KahaDB is version 3
> 2011-03-29 18:34:20,845 [tp-1759557365-7] INFO  MessageDatabase
> -
>  Recovering from the journal ...
> 2011-03-29 18:34:20,846 [tp-1759557365-7] INFO  MessageDatabase
> -
>  Recovery replayed 1 operations from the journal in 0.016 seconds.
> 2011-03-29 18:34:20,858 [tp-1759557365-7] INFO  BrokerService
> -
>  ActiveMQ 5.4.2 JMS Message Broker (localhost) is starting
> 2011-03-29 18:34:20,858 [tp-1759557365-7] INFO  BrokerService
> -
>  For help or more information please see: http://activemq.apache.org/
> 2011-03-29 18:34:21,119 [JMX connector  ] WARN  ManagementContext
> -
>  Failed to start jmx connector: Cannot bind to URL
> [rmi://localhost:1099/jmxrmi]
> : javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
> java.rmi.Alr
> eadyBoundException: jmxrmi]
> 2011-03-29 18:34:21,123 [tp-1759557365-7] INFO  BrokerService
> -
>  ActiveMQ JMS Message Broker (localhost,
> ID:IPC-DEN-NTB-237-50540-1301445260878-
> 0:1) started
> 2011-03-29 18:34:21,127 [tp-1759557365-7] INFO  TransportConnector
> -
>  Connector vm://localhost Started
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Having-trouble-using-Administration-Console-with-Authentication-tp3416709p3416709.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Reply via email to