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

Bruce Snyder updated AMQ-2531:
------------------------------

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> ActiveMQ and/or embedded Jetty get stuck after "starting JettyFactoryBean"
> --------------------------------------------------------------------------
>
>                 Key: AMQ-2531
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2531
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.0
>         Environment: AMD Phenom II X2 550
> Windows XP Professional SP3
>            Reporter: T. Gau
>             Fix For: 5.5.0
>
>         Attachments: activemq.log
>
>
> A fresh copy of ActiveMQ does not start up properly on my pc (Phenom II X2 
> 550, WinXP Prof SP3). But it does on my notebook (IBM ThinkPad T61, Centrino 
> Duo, WinXP Prof SP3).
> Comparing the logs of both installations it seems to happen near or after 
> 'DEBUG | starting jettyfactoryb...@183e7de | org.mortbay.log | main'.  While 
> the notebooks proceeds with 'DEBUG | started
> org.mortbay.jetty.nio.selectchannelconnecto...@197871d | org.mortbay.log | 
> main' the computer directly starts with 'DEBUG | Checkpoint started.' and 
> 'DEBUG | Checkpoint done.' cycle. The admin web gui is not available.
> Output of cmd shell of my pc:
> {quote}
> Java Runtime: Sun Microsystems Inc. 1.6.0_14 D:\Runtimes\Java\jdk1.6.0_14\jre
>   Heap sizes: current=5056k  free=4402k  max=520256k
>     JVM args: -Dcom.sun.management.jmxremote -Xmx512M 
> -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logg
> ing.config.file=logging.properties -DDEBUG 
> -Dactivemq.classpath=D:\Entwicklung\apache-activemq-5.3.0\bin\../conf; -Dacti
> vemq.home=D:\Entwicklung\apache-activemq-5.3.0\bin\.. 
> -Dactivemq.base=D:\Entwicklung\apache-activemq-5.3.0\bin\..
> ACTIVEMQ_HOME: D:\Entwicklung\apache-activemq-5.3.0\bin\..
> ACTIVEMQ_BASE: D:\Entwicklung\apache-activemq-5.3.0\bin\..
> Loading message broker from: xbean:activemq.xml
>  INFO | Refreshing 
> org.apache.xbean.spring.context.resourcexmlapplicationcont...@19209ea: 
> display name [org.apache.xbean
> .spring.context.resourcexmlapplicationcont...@19209ea]; startup date [Sun Dec 
> 13 13:33:15 CET 2009]; root of context hie
> rarchy
>  INFO | Loading XML bean definitions from class path resource [activemq.xml]
>  INFO | Loading XML bean definitions from class path resource [jetty.xml]
>  INFO | Bean factory for application context 
> [org.apache.xbean.spring.context.resourcexmlapplicationcont...@19209ea]: or
> g.springframework.beans.factory.support.defaultlistablebeanfact...@125fefa
>  INFO | Loading properties file from URL 
> [file:D:/Entwicklung/apache-activemq-5.3.0/bin/../conf/credentials.properties]
>  INFO | Pre-instantiating singletons in 
> org.springframework.beans.factory.support.defaultlistablebeanfact...@125fefa: 
> de
> fining beans 
> [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,org.apache.activemq.xbean.XBeanBr
> okerService#0,org.mortbay.jetty.xbean.JettyFactoryBean#0]; root of factory 
> hierarchy
>  INFO | Using Persistence Adapter: 
> org.apache.activemq.store.kahadb.kahadbpersistenceadap...@5b8827
>  INFO | Replayed 1 operations from the journal in 0.0 seconds.
>  INFO | ActiveMQ 5.3.0 JMS Message Broker (localhost) is starting
>  INFO | For help or more information please see: http://activemq.apache.org/
>  INFO | Listening for connections at: tcp://echo-1:61616
>  INFO | Connector openwire Started
>  INFO | ActiveMQ JMS Message Broker (localhost, 
> ID:echo-1-1517-1260707596343-0:0) started
>  INFO | Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via 
> org.mortbay.log.Slf4jLog
>  INFO | jetty-6.1.9
>  INFO | Refreshing 
> org.springframework.web.context.support.xmlwebapplicationcont...@130633a: 
> display name [Root WebAppli
> cationContext]; startup date [Sun Dec 13 13:33:16 CET 2009]; root of context 
> hierarchy
>  INFO | Loading XML bean definitions from ServletContext resource 
> [/WEB-INF/webconsole-embedded.xml]
>  INFO | Loading XML bean definitions from ServletContext resource 
> [/WEB-INF/webconsole-query.xml]
>  INFO | Bean factory for application context 
> [org.springframework.web.context.support.xmlwebapplicationcont...@130633a]:
>  org.springframework.beans.factory.support.defaultlistablebeanfact...@12fb0af
>  INFO | Loading properties file from URL 
> [file:D:/Entwicklung/apache-activemq-5.3.0/bin/../conf/credentials.properties]
>  INFO | Pre-instantiating singletons in 
> org.springframework.beans.factory.support.defaultlistablebeanfact...@12fb0af: 
> de
> fining beans 
> [queueBrowser,messageQuery,queueConsumerQuery,connectionQuery,placeholderConfig,brokerQuery,sessionPool,con
> nectionFactory]; root of factory hierarchy
>  INFO | ActiveMQ WebConsole initialized.
>  INFO | Initializing Spring FrameworkServlet 'dispatcher'
>  INFO | FrameworkServlet 'dispatcher': initialization started
>  INFO | Refreshing 
> org.springframework.web.context.support.xmlwebapplicationcont...@d480ea: 
> display name [WebApplication
> Context for namespace 'dispatcher-servlet']; startup date [Sun Dec 13 
> 13:33:16 CET 2009]; parent: org.springframework.we
> b.context.support.xmlwebapplicationcont...@130633a
>  INFO | Loading XML bean definitions from ServletContext resource 
> [/WEB-INF/dispatcher-servlet.xml]
>  INFO | Bean factory for application context 
> [org.springframework.web.context.support.xmlwebapplicationcont...@d480ea]:
> org.springframework.beans.factory.support.defaultlistablebeanfact...@adae91
>  INFO | Pre-instantiating singletons in 
> org.springframework.beans.factory.support.defaultlistablebeanfact...@adae91: 
> def
> ining beans 
> [handlerMapping,/createDestination.action,/deleteDestination.action,/createSubscriber.action,/deleteSubscrib
> er.action,/sendMessage.action,/purgeDestination.action,/deleteMessage.action,/copyMessage.action,/moveMessage.action,exc
> eptionResolver]; parent: 
> org.springframework.beans.factory.support.defaultlistablebeanfact...@12fb0af
>  INFO | FrameworkServlet 'dispatcher': initialization completed in 63 ms
>  INFO | ActiveMQ Console at http://0.0.0.0:8161/admin
>  INFO | Initializing Spring root WebApplicationContext
>  INFO | Root WebApplicationContext: initialization started
>  INFO | Refreshing 
> org.springframework.web.context.support.xmlwebapplicationcont...@5bf624: 
> display name [Root WebApplic
> ationContext]; startup date [Sun Dec 13 13:33:17 CET 2009]; root of context 
> hierarchy
>  INFO | Loading XML bean definitions from ServletContext resource 
> [/WEB-INF/applicationContext.xml]
>  INFO | camel-osgi.jar not detected in classpath
>  INFO | Bean factory for application context 
> [org.springframework.web.context.support.xmlwebapplicationcont...@5bf624]:
> org.springframework.beans.factory.support.defaultlistablebeanfact...@fe2558
>  INFO | Loading properties file from URL 
> [file:D:/Entwicklung/apache-activemq-5.3.0/bin/../conf/credentials.properties]
>  INFO | JMX enabled. Using InstrumentationLifecycleStrategy.
>  WARN | Using a packages element to specify packages to search has been 
> deprecated. Please use a packageScan element ins
> tead.
>  INFO | Pre-instantiating singletons in 
> org.springframework.beans.factory.support.defaultlistablebeanfact...@fe2558: 
> def
> ining beans 
> [placeholderConfig,template,consumerTemplate,camel:beanPostProcessor,camel,activemq];
>  root of factory hierar
> chy
>  INFO | Starting Apache Camel as property ShouldStartContext is true
>  INFO | Apache Camel 2.0.0 (CamelContext:camel) is starting
>  INFO | Connector vm://localhost Started
>  INFO | Apache Camel 2.0.0 (CamelContext:camel) started
>  INFO | Root WebApplicationContext: initialization completed in 750 ms
>  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
> {quote}

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

Reply via email to