You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by JigarP <ji...@gmail.com> on 2008/08/19 11:38:24 UTC

Received expired message: MessageDispatch getting message in Jetty

Hi All,

    We are using activemq for sending/receiving messages from different
system. we are having jetty activemq listenner which listen for messages 
from MQ. and we have sender which sends messages to MQ.

We have small time gap(around 40 seconds,Jetty's clock is 40 second ahead of
producer clock) between jetty and message sender system. so when we get
message to jetty we are getting below message and our message is not
processed furthur.

15 Aug 2008 05:42:45,651 Received expired message: MessageDispatch
{commandId = 0, responseRequired = false, consumerId =
ID:C31248-110623-1168-1218717655990-1:0:1:1, destination =
topic://BidInitTopic, message = ActiveMQObjectMessage {commandId = 6,
responseRequired = false, messageId =
ID:c31248-110620-1558-1218717606968-1:20:1:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:c31248-110620-1558-1218717606968-1:20:1:1, destination =
topic://BidInitTopic, transactionId =
TX:ID:c31248-110620-1558-1218717606968-1:20:1, expiration = 1218793364875,
timestamp = 1218793324875, arrival = 0, correlationId = null, replyTo =
null, persistent = true, type = null, priority = 4, groupID = null,
groupSequence = 0, targetConsumerId = null, compressed = false, userID =
null, content = org.apache.activemq.util.ByteSequence@2aab4c,
marshalledProperties = null, dataStructure = null, redeliveryCounter = 0,
size = 0, properties = null, readOnlyProperties = true, readOnlyBody = true,
droppable = false}, redeliveryCounter = 0}

but immediately after we synch the times, everything works just fine. So is
it a time synching issue that we have to resolve?? If so, then how can we
configure to get the messages delivered atleast with a delay of 5 minutes
(since we suppose this should be the max gap from the producer to the
consumer).


We're having the following configuration in our Spring XML file

<!-- JMS ConnectionFactory beans -->
        <bean id="jmsFactory"
                class="org.apache.activemq.pool.PooledConnectionFactory">
                <property name="connectionFactory">
                        <bean
                               
class="org.apache.activemq.ActiveMQConnectionFactory">
                                <property name="brokerURL">
                                       
<value>tcp://192.168.30.5:61616?connectionTimeout=0&wireFormat.maxInactivityDuration=0</value>
                                </property>
                        </bean>
                </property>
        </bean>

        <!-- Spring JMS Template -->

        <bean id="myJmsTemplate"
                class="org.springframework.jms.core.JmsTemplate">
                <property name="connectionFactory">
                        <ref local="jmsFactory" />
                </property>
                <property name="destinationResolver"
ref="destinationResolver" />
                <property name="pubSubDomain" value="true" />
                <property name="receiveTimeout" value="20000" />
                <property name="deliveryPersistent" value="true" />
        </bean>


This is our JMS spring listener
<bean id="bidRegistryMessageListenerContainer"
               
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
                <property name="concurrentConsumers" value="1" />
                <property name="connectionFactory" ref="jmsFactory" />
                <property name="pubSubDomain" value="true" />
                <property name="receiveTimeout" value="100000" />
                <property name="destinationName" value="bidRegistryTopic" />
                <property name="destinationResolver"
ref="destinationResolver" />
                <property name="messageListener"
ref="bidRegistryStatusListener" />
        </bean>

Kindly help.

thanks
Jigar
-- 
View this message in context: http://www.nabble.com/Received-expired-message%3A-MessageDispatch--getting-message-in-Jetty-tp19047162p19047162.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.