forum.bitel.ru http://forum.bitel.ru/ |
|
ActiveMQ 5.4.1 - перестал работать http://forum.bitel.ru/viewtopic.php?f=22&t=4815 |
Страница 1 из 1 |
Автор: | sda0 [ 22 ноя 2010, 17:29 ] |
Заголовок сообщения: | ActiveMQ 5.4.1 - перестал работать |
Добрый день. почти месяц гоняю в тестовом режиме БГ. всё работало замечательно. система работает под виртуалбоксом под убунтой. на основном диске кончилось место и виртуалбокс подзавис. после перезагрузки виртуальной машины перестал работать activemq. вот вырезка последних строк логов: activemq.log Код: 2010-11-22 16:09:45,874 | INFO | ActiveMQ Message Broker (localhost, null) is shutting down | org.apache.activ emq.broker.BrokerService | WrapperSimpleAppMain 2010-11-22 16:09:45,875 | INFO | Connector nio Stopped | org.apache.activemq.broker.TransportConnector | Wrapp erSimpleAppMain 2010-11-22 16:09:45,906 | INFO | JobSchedulerStore:../../data/localhost/scheduler stopped | org.apache.activem q.broker.scheduler.JobSchedulerStore | WrapperSimpleAppMain 2010-11-22 16:09:45,907 | INFO | PListStore:../../data/localhost/tmp_storage stopped | org.apache.activemq.store.kahadb.plist.PListStore | WrapperSimpleAppMain 2010-11-22 16:09:45,907 | INFO | Stopping async queue tasks | org.apache.activemq.store.kahadb.KahaDBStore | WrapperSimpleAppMain 2010-11-22 16:09:45,907 | INFO | Stopping async topic tasks | org.apache.activemq.store.kahadb.KahaDBStore | WrapperSimpleAppMain 2010-11-22 16:09:45,907 | INFO | Stopped KahaDB | org.apache.activemq.store.kahadb.KahaDBStore | WrapperSimple AppMain 2010-11-22 16:09:45,998 | INFO | ActiveMQ JMS Message Broker (localhost, null) stopped | org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain wrapper.log Код: INFO | jvm 1 | 2010/11/22 16:09:46 | at org.apache.activemq.broker.BrokerFilter.start(BrokerFilter.j ava:157) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.apache.activemq.broker.BrokerFilter.start(BrokerFilter.j ava:157) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.apache.activemq.broker.TransactionBroker.start(Transacti onBroker.java:112) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.apache.activemq.broker.BrokerService$3.start(BrokerServi ce.java:1786) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.apache.activemq.broker.BrokerService.start(BrokerService .java:496) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.apache.activemq.xbean.XBeanBrokerService.afterProperties Set(XBeanBrokerService.java:60) INFO | jvm 1 | 2010/11/22 16:09:46 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) INFO | jvm 1 | 2010/11/22 16:09:46 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39) INFO | jvm 1 | 2010/11/22 16:09:46 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25) INFO | jvm 1 | 2010/11/22 16:09:46 | at java.lang.reflect.Method.invoke(Method.java:597) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.springframework.beans.factory.support.AbstractAutowireCa pableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1536) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.springframework.beans.factory.support.AbstractAutowireCa pableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1477) INFO | jvm 1 | 2010/11/22 16:09:46 | at org.springframework.beans.factory.support.AbstractAutowireCa pableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) INFO | jvm 1 | 2010/11/22 16:09:46 | ... 33 more STATUS | wrapper | 2010/11/22 16:09:48 | <-- Wrapper Stopped конфиг: Код: <beans
xmlns="http://www.springframework.org/schema/beans" xmlns:amq="http://activemq.apache.org/schema/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd"> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> <property name="locations"> <value>file:${activemq.base}/conf/credentials.properties</value> </property> </bean> <!-- The <broker> element is used to configure the ActiveMQ broker. --> <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true"> <!-- For better performances use VM cursor and small memory limit. For more information, see: http://activemq.apache.org/message-cursors.html Also, if your producer is "hanging", it's probably due to producer flow control. For more information, see: http://activemq.apache.org/producer-flow-control.html --> <destinationPolicy> <policyMap> <policyEntries> <policyEntry topic=">" producerFlowControl="true" memoryLimit="1mb"> <pendingSubscriberPolicy> <vmCursor /> </pendingSubscriberPolicy> </policyEntry> <policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb"> <!-- Use VM cursor for better latency For more information, see: http://activemq.apache.org/message-cursors.html <pendingQueuePolicy> <vmQueueCursor/> </pendingQueuePolicy> --> </policyEntry> </policyEntries> </policyMap> </destinationPolicy> <!-- The managementContext is used to configure how ActiveMQ is exposed in JMX. By default, ActiveMQ uses the MBean server that is started by the JVM. For more information, see: http://activemq.apache.org/jmx.html --> <managementContext> <managementContext createConnector="false"/> </managementContext> <!-- Configure message persistence for the broker. The default persistence mechanism is the KahaDB store (identified by the kahaDB tag). For more information, see: http://activemq.apache.org/persistence.html --> <persistenceAdapter> <kahaDB directory="${activemq.base}/data/kahadb"/> </persistenceAdapter> <!-- The systemUsage controls the maximum amount of space the broker will use before slowing down producers. For more information, see: http://activemq.apache.org/producer-flow-control.html <systemUsage> <systemUsage> <memoryUsage> <memoryUsage limit="20 mb"/> </memoryUsage> <storeUsage> <storeUsage limit="1 gb"/> </storeUsage> <tempUsage> <tempUsage limit="100 mb"/> </tempUsage> </systemUsage> </systemUsage> --> <!-- The transport connectors expose ActiveMQ over a given protocol to clients and other brokers. For more information, see: http://activemq.apache.org/configuring-transports.html --> <transportConnectors> <transportConnector name="nio" uri="nio://127.0.0.1:61616"/> </transportConnectors> </broker> <!-- Enable web consoles, REST and Ajax APIs and demos It also includes Camel (with its web console), see ${ACTIVEMQ_HOME}/conf/camel.xml for more info Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details --> <import resource="jetty.xml"/> </beans> |
Автор: | Phricker [ 22 ноя 2010, 18:27 ] |
Заголовок сообщения: | Re: ActiveMQ 5.4.1 - перестал работать |
тут было написано про то что лучше использовать версию указанную в документации |
Автор: | sda0 [ 22 ноя 2010, 18:45 ] |
Заголовок сообщения: | Re: ActiveMQ 5.4.1 - перестал работать |
да, читал, знаю... просто хотелось более свежий софт юзать. сейчас попробовал 5,3,2 - работает с конфигом из доки. под 5,4,1 даже конфиг с документации не подошёл. пришлось немного напильником пройтись.. а вообще есть в планах 5,4,х завести и что бы работало без сбоев? з.ы. всё же хотелось бы ответа разработчиков - почему мог отказать 5,4,1 ? |
Автор: | Amir [ 27 ноя 2010, 20:49 ] |
Заголовок сообщения: | Re: ActiveMQ 5.4.1 - перестал работать |
У него баг - при перезапуске падает пока не удалить каталог data; при определенной конфигурации баг исчезает. Обещали исправить в 5.4.2. Если интересно, на тестовом сервере сейчас с такой конфигурацией работает: Код: <beans xmlns="http://www.springframework.org/schema/beans" xmlns:amq="http://activemq.apache.org/schema/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd"> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> <property name="locations"> <value>file:${activemq.base}/conf/credentials.properties</value> </property> </bean> <!-- The <broker> element is used to configure the ActiveMQ broker. --> <broker xmlns="http://activemq.apache.org/schema/core" brokerName="activeMQ" dataDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true" useShutdownHook="true" schedulerSupport="false"> <!-- For better performances use VM cursor and small memory limit. For more information, see: http://activemq.apache.org/message-cursors.html Also, if your producer is "hanging", it's probably due to producer flow control. For more information, see: http://activemq.apache.org/producer-flow-control.html --> <destinationPolicy> <policyMap> <policyEntries> <policyEntry topic=">" producerFlowControl="true" memoryLimit="20mb"> <pendingSubscriberPolicy> <vmCursor /> </pendingSubscriberPolicy> </policyEntry> <policyEntry queue=">" producerFlowControl="true" memoryLimit="20mb"> <!-- <pendingQueuePolicy> <vmQueueCursor/> </pendingQueuePolicy> --> </policyEntry> </policyEntries> </policyMap> </destinationPolicy> <!-- The managementContext is used to configure how ActiveMQ is exposed in JMX. By default, ActiveMQ uses the MBean server that is started by the JVM. For more information, see: http://activemq.apache.org/jmx.html --> <managementContext> <managementContext createConnector="false"/> </managementContext> <networkConnectors> <networkConnector uri="multicast://default" dynamicOnly="true" networkTTL="3" prefetchSize="1" decreaseNetworkConsumerPriority="true" /> </networkConnectors> <!-- Configure message persistence for the broker. The default persistence mechanism is the KahaDB store (identified by the kahaDB tag). For more information, see: http://activemq.apache.org/persistence.html --> <persistenceAdapter> <kahaDB directory="${activemq.base}/data/kahadb"/> <!-- <amqPersistenceAdapter syncOnWrite="false" directory="${activemq.base}/data" maxFileLength="40 mb"/> --> <!-- <kahaDB directory="${activemq.base}/data/kahadb" enableIndexWriteAsync="true"/> --> </persistenceAdapter> <plugins> <simpleAuthenticationPlugin> <users> <authenticationUser username="bill" password="bgbilling" groups="user"/> <authenticationUser username="listener" password="listener" groups="anonymous"/> </users> </simpleAuthenticationPlugin> <!-- lets configure a destination based authorization mechanism --> <authorizationPlugin> <map> <authorizationMap> <authorizationEntries> <authorizationEntry queue="BG.Event.>" read="user" write="user" admin="user" /> <authorizationEntry topic="BG.Event.>" read="user, anonymous" write="user" admin="user" /> <authorizationEntry topic="ActiveMQ.Advisory.>" read="user, anonymous" write="user, anonymous" admin="user, anonymous"/> </authorizationEntries> <!-- let's assign roles to temporary destinations. comment this entry if we don't want any roles assigned to temp destinations --> <!-- <tempDestinationAuthorizationEntry> <tempDestinationAuthorizationEntry read="tempDestinationAdmins" write="tempDestinationAdmins" admin="tempDestinationAdmins"/> </tempDestinationAuthorizationEntry> --> </authorizationMap> </map> </authorizationPlugin> </plugins> <!-- The maximum about of space the broker will use before slowing down producers --> <systemUsage> <systemUsage> <memoryUsage><memoryUsage limit="40 mb"/></memoryUsage> <storeUsage><storeUsage limit="1 gb"/></storeUsage> <tempUsage><tempUsage limit="100 mb"/></tempUsage> </systemUsage> </systemUsage> <!-- The transport connectors expose ActiveMQ over a given protocol to clients and other brokers. For more information, see: http://activemq.apache.org/configuring-transports.html --> <transportConnectors> <transportConnector name="nio" uri="nio://mq.office.bitel.ru:61616" discoveryUri="multicast://default"/> </transportConnectors> </broker> <!-- Enable web consoles, REST and Ajax APIs and demos It also includes Camel (with its web console), see ${ACTIVEMQ_HOME}/conf/camel.xml for more info Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details --> <import resource="jetty.xml"/> </beans> Цитата: destroyApplicationContextOnStop="true"
useShutdownHook="true" schedulerSupport="false"> |
Страница 1 из 1 | Часовой пояс: UTC + 5 часов [ Летнее время ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |