Похожая проблема, только перелезаю с 6.0 на 7.0.
Само ядро перелезло на 7.0 штатно, по инструкции.
Проблема с подключением к MQ. Все версии последние с сайта.
Лог BGInetAccess:
11-25/15:14:27 INFO [EventProcessor-init] EventProcessor - Init EventProcessor MQ connection factory...
11-25/15:14:31 ERROR [main] EventProcessor - Problem with MQ connection! Timeout connecting to the MQ broker!
Лог биллинга:
server 11-25/16:48:39 ERROR [main] EventProcessor - Problem with MQ connection! Timeout connecting to the MQ broker!
Лог MQ сыпется вида:
2016-11-25 16:48:40,781 | WARN | Transport Connection to:
tcp://127.0.0.1:52829 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ NIO Worker 3
Лог wrapper сыпется вида:
INFO | jvm 1 | 2016/11/25 16:48:26 | WARN | Transport Connection to:
tcp://127.0.0.1:52826 failed: java.io.IOException: Wire format negotiation timeout: peer did not send his wire format.
INFO | jvm 1 | 2016/11/25 16:48:26 | WARN | Transport Connection to:
tcp://127.0.0.1:52827 failed: java.io.IOException: Wire format negotiation timeout: peer did not send his wire format.
INFO | jvm 1 | 2016/11/25 16:48:27 | INFO | Initializing Spring FrameworkServlet 'dispatcher'
INFO | jvm 1 | 2016/11/25 16:48:35 | INFO | ActiveMQ Console at
http://0.0.0.0:8161/adminINFO | jvm 1 | 2016/11/25 16:48:35 | INFO | started o.e.j.w.WebAppContext{/demo,file:/opt/activemq/webapps/demo/}
INFO | jvm 1 | 2016/11/25 16:48:35 | INFO | Apache ActiveMQ Web Demo at
http://0.0.0.0:8161/demoINFO | jvm 1 | 2016/11/25 16:48:36 | INFO | started o.e.j.w.WebAppContext{/fileserver,file:/opt/activemq/webapps/fileserver/}
INFO | jvm 1 | 2016/11/25 16:48:36 | INFO | RESTful file access application at
http://0.0.0.0:8161/fileserverINFO | jvm 1 | 2016/11/25 16:48:37 | INFO | Started
SelectChannelConnector@0.0.0.0:8161INFO | jvm 1 | 2016/11/25 16:48:40 | WARN | Transport Connection to:
tcp://127.0.0.1:52829 failed: java.io.EOFException
java - jdk1.8.0_51
cat /opt/activemq/conf/activemq.xml
<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/b ... ns-2.0.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/ ... q-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">
<!--
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 queue=">" optimizedDispatch="true" />
</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"/>
<!--<kahaDB directory="${activemq.base}/data/kahadb" enableJournalDiskSyncs="false" indexWriteBatchSize="10000" indexCacheSize="1000"/>-->
<!--<kahaDB directory="${activemq.base}/data/kahadb" enableIndexWriteAsync="true"/>-->
<!--<amqPersistenceAdapter syncOnWrite="false" directory="${activemq.base}/data" maxFileLength="40 mb"/>-->
</persistenceAdapter>
<plugins>
<!-- drop messages that have been sent to the DLQ -->
<discardingDLQBrokerPlugin dropAll="true"/>
<simpleAuthenticationPlugin>
<users>
<authenticationUser username="${activemq.username}" password="${activemq.password}" 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 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="128 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="10 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="1 gb"/>
</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"/>
<!--<transportConnector name="nio" uri="nio://0.0.0.0: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>
Вход
Регистрация
FAQ
Поиск
