activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Janne Saikko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2878) Problems with starting ApacheMQ Broker
Date Wed, 25 Aug 2010 13:37:47 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Janne Saikko updated AMQ-2878:
------------------------------

    Description: 
When starting broker, it jams?

I tried to navigate with browser to ****:8161/console/admin/ but i got this error message:

Failed: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
</head>
<body>
<h2>HTTP ERROR: 404</h2>
<p>Problem accessing /console/admin/agent. Reason:
<pre>    Not Found</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>

Below is starting log of broker:

[root@********** bin]# sh activemq console
INFO: Using default configuration
(you can configure options in one of these file: /etc/default/activemq /root/.activemqrc)

INFO: Invoke the following command to create a configuration file
activemq setup [ /etc/default/activemq | /root/.activemqrc ]

INFO: Using java '/usr/bin/java'
INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing
CTRL+C)
Java Runtime: Sun Microsystems Inc. 1.6.0_21 /usr/lib/jvm/java-1.6.0-sun-1.6.0.21.x86_64/jre
  Heap sizes: current=253440k  free=249242k  max=253440k
    JVM args: -Xms256M -Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties
-Dcom.sun.management.jmxremote -Dactivemq.classpath=/opt/progress/apache-activemq-5.4.0-fuse-00-00/conf;
-Dactivemq.home=/opt/progress/apache-activemq-5.4.0-fuse-00-00 -Dactivemq.base=/opt/progress/apache-activemq-5.4.0-fuse-00-00
ACTIVEMQ_HOME: /opt/progress/apache-activemq-5.4.0-fuse-00-00
ACTIVEMQ_BASE: /opt/progress/apache-activemq-5.4.0-fuse-00-00
Loading message broker from: xbean:activemq.xml
 WARN | destroyApplicationContextOnStop parameter is deprecated, please use shutdown hooks
instead
 INFO | PListStore:/opt/progress/apache-activemq-5.4.0-fuse-00-00/data/localhost/tmp_storage
started
 INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/progress/apache-activemq-5.4.0-fuse-00-00/data/kahadb]
 INFO | KahaDB is version 2
 INFO | Recovering from the journal ...
 INFO | Recovery replayed 1 operations from the journal in 0.019 seconds.
 INFO | ActiveMQ 5.4.0-fuse-00-00 JMS Message Broker (localhost) is starting
 INFO | For help or more information please see: http://activemq.apache.org/
 INFO | Scheduler using directory: activemq-data/scheduler
 INFO | Listening for connections at: tcp://saenafuq20.europe.nokia.com:61616
 INFO | Connector openwire Started
 INFO | ActiveMQ JMS Message Broker (localhost, ID:******.******.*****.com-55780-1282743080380-0:0)
started
 INFO | Logging to org.slf4j.impl.JCLLoggerAdapter(org.eclipse.jetty.util.log) via org.eclipse.jetty.util.log.Slf4jLog
 INFO | jetty-7.0.1.v20091125
 INFO | ActiveMQ WebConsole initialized.
 INFO | Initializing Spring FrameworkServlet 'dispatcher'
 INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
 INFO | Initializing Spring root WebApplicationContext
 INFO | Connector vm://localhost Started
 INFO | Camel Console at http://0.0.0.0:8161/camel
 INFO | ActiveMQ Web Demos at http://0.0.0.0:8161/demo
 INFO | RESTful file access application at http://0.0.0.0:8161/fileserver
 INFO | Started SelectChannelConnector@0.0.0.0:8161


  was:
When starting broker, it jams?

I tried to navigate with browser to ****:8161/console/admin/ but i got this error message:

Failed: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
</head>
<body>
<h2>HTTP ERROR: 404</h2>
<p>Problem accessing /console/admin/agent. Reason:
<pre>    Not Found</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>

Below is starting log of broker:

[root@********** bin]# sh activemq console
INFO: Using default configuration
(you can configure options in one of these file: /etc/default/activemq /root/.activemqrc)

INFO: Invoke the following command to create a configuration file
activemq setup [ /etc/default/activemq | /root/.activemqrc ]

INFO: Using java '/usr/bin/java'
INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing
CTRL+C)
Java Runtime: Sun Microsystems Inc. 1.6.0_21 /usr/lib/jvm/java-1.6.0-sun-1.6.0.21.x86_64/jre
  Heap sizes: current=253440k  free=249242k  max=253440k
    JVM args: -Xms256M -Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties
-Dcom.sun.management.jmxremote -Dactivemq.classpath=/opt/progress/apache-activemq-5.4.0-fuse-00-00/conf;
-Dactivemq.home=/opt/progress/apache-activemq-5.4.0-fuse-00-00 -Dactivemq.base=/opt/progress/apache-activemq-5.4.0-fuse-00-00
ACTIVEMQ_HOME: /opt/progress/apache-activemq-5.4.0-fuse-00-00
ACTIVEMQ_BASE: /opt/progress/apache-activemq-5.4.0-fuse-00-00
Loading message broker from: xbean:activemq.xml
 WARN | destroyApplicationContextOnStop parameter is deprecated, please use shutdown hooks
instead
 INFO | PListStore:/opt/progress/apache-activemq-5.4.0-fuse-00-00/data/localhost/tmp_storage
started
 INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/progress/apache-activemq-5.4.0-fuse-00-00/data/kahadb]
 INFO | KahaDB is version 2
 INFO | Recovering from the journal ...
 INFO | Recovery replayed 1 operations from the journal in 0.019 seconds.
 INFO | ActiveMQ 5.4.0-fuse-00-00 JMS Message Broker (localhost) is starting
 INFO | For help or more information please see: http://activemq.apache.org/
 INFO | Scheduler using directory: activemq-data/scheduler
 INFO | Listening for connections at: tcp://saenafuq20.europe.nokia.com:61616
 INFO | Connector openwire Started
 INFO | ActiveMQ JMS Message Broker (localhost, ID:saenafuq20.europe.nokia.com-55780-1282743080380-0:0)
started
 INFO | Logging to org.slf4j.impl.JCLLoggerAdapter(org.eclipse.jetty.util.log) via org.eclipse.jetty.util.log.Slf4jLog
 INFO | jetty-7.0.1.v20091125
 INFO | ActiveMQ WebConsole initialized.
 INFO | Initializing Spring FrameworkServlet 'dispatcher'
 INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
 INFO | Initializing Spring root WebApplicationContext
 INFO | Connector vm://localhost Started
 INFO | Camel Console at http://0.0.0.0:8161/camel
 INFO | ActiveMQ Web Demos at http://0.0.0.0:8161/demo
 INFO | RESTful file access application at http://0.0.0.0:8161/fileserver
 INFO | Started SelectChannelConnector@0.0.0.0:8161



> Problems with starting ApacheMQ Broker
> --------------------------------------
>
>                 Key: AMQ-2878
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2878
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.0
>         Environment: Red Hat 5 x86_64
>            Reporter: Janne Saikko
>            Priority: Blocker
>
> When starting broker, it jams?
> I tried to navigate with browser to ****:8161/console/admin/ but i got this error message:
> Failed: <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
> <title>Error 404 Not Found</title>
> </head>
> <body>
> <h2>HTTP ERROR: 404</h2>
> <p>Problem accessing /console/admin/agent. Reason:
> <pre>    Not Found</pre></p>
> <hr /><i><small>Powered by Jetty://</small></i>
> </body>
> </html>
> Below is starting log of broker:
> [root@********** bin]# sh activemq console
> INFO: Using default configuration
> (you can configure options in one of these file: /etc/default/activemq /root/.activemqrc)
> INFO: Invoke the following command to create a configuration file
> activemq setup [ /etc/default/activemq | /root/.activemqrc ]
> INFO: Using java '/usr/bin/java'
> INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing
CTRL+C)
> Java Runtime: Sun Microsystems Inc. 1.6.0_21 /usr/lib/jvm/java-1.6.0-sun-1.6.0.21.x86_64/jre
>   Heap sizes: current=253440k  free=249242k  max=253440k
>     JVM args: -Xms256M -Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties
-Dcom.sun.management.jmxremote -Dactivemq.classpath=/opt/progress/apache-activemq-5.4.0-fuse-00-00/conf;
-Dactivemq.home=/opt/progress/apache-activemq-5.4.0-fuse-00-00 -Dactivemq.base=/opt/progress/apache-activemq-5.4.0-fuse-00-00
> ACTIVEMQ_HOME: /opt/progress/apache-activemq-5.4.0-fuse-00-00
> ACTIVEMQ_BASE: /opt/progress/apache-activemq-5.4.0-fuse-00-00
> Loading message broker from: xbean:activemq.xml
>  WARN | destroyApplicationContextOnStop parameter is deprecated, please use shutdown
hooks instead
>  INFO | PListStore:/opt/progress/apache-activemq-5.4.0-fuse-00-00/data/localhost/tmp_storage
started
>  INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/progress/apache-activemq-5.4.0-fuse-00-00/data/kahadb]
>  INFO | KahaDB is version 2
>  INFO | Recovering from the journal ...
>  INFO | Recovery replayed 1 operations from the journal in 0.019 seconds.
>  INFO | ActiveMQ 5.4.0-fuse-00-00 JMS Message Broker (localhost) is starting
>  INFO | For help or more information please see: http://activemq.apache.org/
>  INFO | Scheduler using directory: activemq-data/scheduler
>  INFO | Listening for connections at: tcp://saenafuq20.europe.nokia.com:61616
>  INFO | Connector openwire Started
>  INFO | ActiveMQ JMS Message Broker (localhost, ID:******.******.*****.com-55780-1282743080380-0:0)
started
>  INFO | Logging to org.slf4j.impl.JCLLoggerAdapter(org.eclipse.jetty.util.log) via org.eclipse.jetty.util.log.Slf4jLog
>  INFO | jetty-7.0.1.v20091125
>  INFO | ActiveMQ WebConsole initialized.
>  INFO | Initializing Spring FrameworkServlet 'dispatcher'
>  INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
>  INFO | Initializing Spring root WebApplicationContext
>  INFO | Connector vm://localhost Started
>  INFO | Camel Console at http://0.0.0.0:8161/camel
>  INFO | ActiveMQ Web Demos at http://0.0.0.0:8161/demo
>  INFO | RESTful file access application at http://0.0.0.0:8161/fileserver
>  INFO | Started SelectChannelConnector@0.0.0.0:8161

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message