[
https://issues.apache.org/jira/browse/AMQ-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782984#comment-13782984
]
Claus Ibsen commented on AMQ-4762:
----------------------------------
This is what you see when starting ActiveMQ in standalone mode
{code}
davsclaus:/opt/apache-activemq-5.9-SNAPSHOT$ bin/activemq console
INFO: Using default configuration
(you can configure options in one of these file: /etc/default/activemq
/Users/davsclaus/.activemqrc)
INFO: Invoke the following command to create a configuration file
bin/activemq setup [ /etc/default/activemq | /Users/davsclaus/.activemqrc ]
INFO: Using java
'/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/bin/java'
INFO: Starting in foreground, this is just for debugging purposes (stop process
by pressing CTRL+C)
Java Runtime: Oracle Corporation 1.7.0_25
/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre
Heap sizes: current=1004928k free=994439k max=1004928k
JVM args: -Xms1G -Xmx1G -Djava.util.logging.config.file=logging.properties
-Dhawtio.authenticationEnabled=false -Dcom.sun.management.jmxremote
-Djava.awt.headless=true -Djava.io.tmpdir=/opt/apache-activemq-5.9-SNAPSHOT/tmp
-Dactivemq.classpath=/opt/apache-activemq-5.9-SNAPSHOT/conf;
-Dactivemq.home=/opt/apache-activemq-5.9-SNAPSHOT
-Dactivemq.base=/opt/apache-activemq-5.9-SNAPSHOT
-Dactivemq.conf=/opt/apache-activemq-5.9-SNAPSHOT/conf
-Dactivemq.data=/opt/apache-activemq-5.9-SNAPSHOT/data
Extensions classpath:
[/opt/apache-activemq-5.9-SNAPSHOT/lib,/opt/apache-activemq-5.9-SNAPSHOT/lib/camel,/opt/apache-activemq-5.9-SNAPSHOT/lib/optional,/opt/apache-activemq-5.9-SNAPSHOT/lib/web,/opt/apache-activemq-5.9-SNAPSHOT/lib/extra]
ACTIVEMQ_HOME: /opt/apache-activemq-5.9-SNAPSHOT
ACTIVEMQ_BASE: /opt/apache-activemq-5.9-SNAPSHOT
ACTIVEMQ_CONF: /opt/apache-activemq-5.9-SNAPSHOT/conf
ACTIVEMQ_DATA: /opt/apache-activemq-5.9-SNAPSHOT/data
Loading message broker from: xbean:activemq.xml
INFO | Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@60356eb0:
startup date [Tue Oct 01 16:24:25 CEST 2013]; root of context hierarchy
INFO |
PListStore:[/opt/apache-activemq-5.9-SNAPSHOT/data/localhost/tmp_storage]
started
INFO | Using Persistence Adapter:
KahaDBPersistenceAdapter[/opt/apache-activemq-5.9-SNAPSHOT/data/kahadb]
INFO | Apache ActiveMQ 5.9-SNAPSHOT (localhost,
ID:davsclaus.air-50551-1380637466269-0:1) is starting
INFO | Listening for connections at:
tcp://davsclaus.air:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO | Connector openwire Started
INFO | Listening for connections at:
amqp://davsclaus.air:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600
INFO | Connector amqp Started
INFO | Apache ActiveMQ 5.9-SNAPSHOT (localhost,
ID:davsclaus.air-50551-1380637466269-0:1) started
INFO | For help or more information please see: http://activemq.apache.org
WARN | Store limit is 102400 mb, whilst the data directory:
/opt/apache-activemq-5.9-SNAPSHOT/data/kahadb only has 75851 mb of usable space
- resetting to maximum available disk space: 75851 mb
INFO | Welcome to hawtio 1.2-M19 : http://hawt.io/ : Don't cha wish your
console was hawt like me? ;-)
INFO | Starting hawtio authentication filter, JAAS authentication disabled
INFO | Using file upload directory:
/opt/apache-activemq-5.9-SNAPSHOT/tmp/uploads
INFO | jolokia-agent: Using access restrictor classpath:/jolokia-access.xml
INFO | Web console type: embedded
INFO | ActiveMQ WebConsole initialized.
INFO | Initializing Spring FrameworkServlet 'dispatcher'
{code}
> ActiveMQ in standalone mode - Have it output the urls for web consoles and JMX
> ------------------------------------------------------------------------------
>
> Key: AMQ-4762
> URL: https://issues.apache.org/jira/browse/AMQ-4762
> Project: ActiveMQ
> Issue Type: Wish
> Reporter: Claus Ibsen
> Fix For: 5.10.0
>
>
> When you start ActiveMQ in standalone mode, you can see something about Web
> console type embedded etc. But you cannot see what the http url is for
> accessing the console. It would be great if we could add a log to point
> people to a http url to access. For example if 8161 port is used they can
> access the welcome page at
> http://localhost:8161/
> And we should possible make the welcome page non secure, so they do not need
> to login to see that page. As the links on that welcome page points to the
> embedded consoles which is secure.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
