Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of baetz.alexander@googlemail.com)
Date: Mon, 17 Oct 2011 02:45:08 -0700 (PDT)
From: Laures <baetz.alexander@googlemail.com>
To: users@activemq.apache.org
Message-ID: <1318844708787-3911512.post@n4.nabble.com>
Subject: Broker Flooded by unconsumed Advisory.TempQueue messages
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

i'm still following a memory problem in my broker network.
According to JConsole the ActiveMQ.Advisory.TempQueue is taking up 99% of
the configured memory when the broker starts to block messages.

The webconsole shows something like 1974234 enqueued and 45345 dequeued
messages at 30 consumers (6 brokers, one consumer and the rest is clients
that use the java connector). As far as i know the dequeue count should be
not much smaller than: enqueued*consumers. so im my case a big bunch of
advisories is not consumed and starts to fill my temp message space.

Since none client actively uses temp queues i find this very strange. After
taking a look at the temp queue i'm even more confused. Most of the messages
look like this (msg.toString):

ActiveMQMessage {commandId = 0, responseRequired = false, messageId =
ID:srv007210-36808-1318839718378-1:1:0:0:203650, originalDestination = null,
originalTransactionId = null, producerId =
ID:srv007210-36808-1318839718378-1:1:0:0, destination =
topic://ActiveMQ.Advisory.TempQueue, transactionId = null, expiration = 0,
timestamp = 0, arrival = 0, brokerInTime = 1318840153501, brokerOutTime =
1318840153501, correlationId = null, replyTo = null, persistent = false,
type = Advisory, priority = 0, groupID = null, groupSequence = 0,
targetConsumerId = null, compressed = false, userID = null, content = null,
marshalledProperties = org.apache.activemq.util.ByteSequence@45290155,
dataStructure = DestinationInfo {commandId = 0, responseRequired = false,
connectionId = ID:srv007210-36808-1318839718378-2:2, destination =
temp-queue://ID:srv007211-47019-1318835590753-11:9:1, operationType = 1,
timeout = 0, brokerPath = null}, redeliveryCounter = 0, size = 0, properties
= {originBrokerName=broker.coremq-behaviortracking-675-mq-01-master,
originBrokerId=ID:srv007210-36808-1318839718378-0:1,
originBrokerURL=stomp://srv007210:61612}, readOnlyProperties = true,
readOnlyBody = true, droppable = false}

do i understand correctly that the origin of the message is a stomp
connection?
if yes, how can a stomp connection create temp queues?

is there a simple reason why the advisories are not consumed?

Thanks in advance,
Laures

--
View this message in context: http://activemq.2283324.n4.nabble.com/Broker-Flooded-by-unconsumed-Advisory-TempQueue-messages-tp3911512p3911512.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.