You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Michael Black (JIRA)" <ji...@apache.org> on 2013/01/14 20:40:14 UTC
[jira] [Created] (AMQ-4255) Negative values in Topic
Michael Black created AMQ-4255:
----------------------------------
Summary: Negative values in Topic
Key: AMQ-4255
URL: https://issues.apache.org/jira/browse/AMQ-4255
Project: ActiveMQ
Issue Type: Bug
Components: Message Store
Affects Versions: 5.7.0
Environment: Scientific Linux 6.3
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
Reporter: Michael Black
Topics list showed negative values for one entry (mirror value of 2 other internal queues)
We're using mkahadb
We've deleted and restarted but have backed up our 15G database which shows this behavior.
Name ↑
Number Of Consumers
Messages Enqueued
Messages Dequeued
Operations
ActiveMQ.Advisory.Consumer.Queue.TwitterIngestQ...
0 2 0 Send To Delete
ActiveMQ.Advisory.Producer.Queue.TwitterIngestE...
0 2 0 Send To Delete
ActiveMQ.Advisory.Producer.Queue.NameResolverEx...
0 1 0 Send To Delete
ActiveMQ.Advisory.MessageDLQd.Topic.AllDocument...
0 17078 0 Send To Delete
ActiveMQ.Advisory.Connection
0 6 0 Send To Delete
ActiveMQ.Advisory.Consumer.Queue.NameResolverQueue
0 1 0 Send To Delete
ActiveMQ.Advisory.Expired.Topic.AllDocumentsTopic
0 17078 0 Send To Delete
ActiveMQ.Advisory.Queue
0 64 0 Send To Delete
ActiveMQ.Advisory.Topic
0 1 0 Send To Delete
AllDocumentsTopic
2 -17078 0 Send To Delete
Subsribers for AllDocumentsTopic showed:
DCDdev DCDdev NOTSET AllDocu... 17102347 0 0 17102347 0 Delete
DCD1 DCD1 NOTSET AllDocu... 14733262 0 0 14733262 0 Delete
Config file
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<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" >
<!--
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="false" memoryLimit="128mb">
<pendingSubscriberPolicy>
<vmCursor />
</pendingSubscriberPolicy>
<subscriptionRecoveryPolicy>
<fixedCountSubscriptionRecoveryPolicy maximumSize="1000"/>
</subscriptionRecoveryPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="false" memoryLimit="128mb">
</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="true"/>
</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" enableIndexWriteAsync="true" enableJournalDiskSyncs="false" />
</persistenceAdapter>
-->
<persistenceAdapter>
<mKahaDB directory="/ocz/activemq/kahadb" >
<filteredPersistenceAdapters>
<filteredKahaDB perDestination="true" >
<persistenceAdapter>
<kahaDB enableIndexWriteAsync="true" enableJournalDiskSyncs="false" />
</persistenceAdapter>
</filteredKahaDB>
</filteredPersistenceAdapters>
</mKahaDB>
</persistenceAdapter>
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="8192 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="256 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="1024 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="openwire" uri="tcp://0.0.0.0:61616"/>
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613"/>
</transportConnectors>
</broker>
<!--
Uncomment to enable Camel
Take a look at activemq-camel.xml for more details
<import resource="camel.xml"/>
-->
<!--
Enable web consoles, REST and Ajax APIs and demos
Take a look at activemq-jetty.xml for more details
-->
<import resource="jetty.xml"/>
</beans>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira