Hi,
I have an issue where ActiveMQ stop routing messages to clients after about
12 hours of running, which I would really appreciate some help with.
When the problem occurs, clients can connect to the server fine. When they
subscribe to a topic, they get the a old message if using retroactive, but
no new messages come though.
I have noticed that when this happens, we get a few thousand 'Discarding
message' entries in the debug log, such as the following:
2011-11-07 16:53:21,981 | DEBUG | Discarding message ActiveMQTextMessage {
commandId = 3746315, responseRequired = false,
messageId = ID:mario-33102-1320656586932-2:55752:-1:1:3746313,
originalDestination = null,
originalTransactionId = null, producerId =
ID:mario-33102-1320656586932-2:55752:-1:1,
destination = topic://ip/43/image, transactionId = null, expiration = 0,
timestamp = 1320684793974,
arrival = 0, brokerInTime = 1320684793974, brokerOutTime = 0, correlationId
= null, replyTo = null,
persistent = false, type = null, priority = 4, groupID = null, groupSequence
= 0,
targetConsumerId = null, compressed = false, userID = null, content = null,
marshalledProperties = null, dataStructure = null, redeliveryCounter = 0,
size = 1117,
properties =
{link=http://www.classicfm.co.uk/on-air/programmes/john-brunning-evening/,
trigger-time=NOW},
readOnlyProperties = true, readOnlyBody = true, droppable = false,
text = SHOW http://slides.musicradio.com/Classic_FM/...pg?bearer=ip}
| org.apache.activemq.broker.region.TopicSubscription | ActiveMQ Transport:
tcp:///10.15.81.142:34978
I noticed this happening with a snapshot of 5.6 from July. I upgraded to a
snapshot from 27/10/2011 and this has the same issue.
The server is running Ubuntu 10.4 using Sun Java 1.6.0_26. There are about
200 non-durable topics, with around 1,000 clients connected at any time.
Messages are a few hundred characters, sent every 8-10 seconds on each
topic.
The configuration file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<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";>
<broker xmlns="http://activemq.apache.org/schema/core"; brokerName="mario"
dataDirectory="/usr/share/activemq/data" persistent="false" useJmx="false">
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry alwaysRetroactive="true" optimizedDispatch="true"
producerFlowControl="false" topic=">">
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1"/>
</pendingMessageLimitStrategy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
<transportConnectors>
<transportConnector enableStatusMonitor="true" name="stomp-61613"
uri="stomp://0.0.0.0:61613?transport.closeAsync=false"/>
</transportConnectors>
</broker>
</beans>
I understand that messages are dropped on queues with slow consumers and on
topics with no subscribers, but I don't believe that to be the case here.
If somebody could clarify why messages are being discarding and how to
change the config to resolve this issue, it would be very much appreciated.
Currently I am having to restart ActiveMQ every 10-12 hours.
Many thanks,
Pete Redhead
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Confused-by-ActiveMQ-Discarding-message-on-Topics-tp4007870p4007870.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
