You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by bill richard <bi...@126.com> on 2008/10/24 11:25:07 UTC
What this means? Urgent!!
2008-10-24 17:07:04,998 [91.249.93:31885] WARN RegionBroker
- Failed to send ActiveMQTextMessage {commandId = 5, responseRequired =
true, messageId = ID:nwdellsrv3-31125-1224836545198-1:117:1:1:1,
originalDestination = null, originalTransactionId = null, producerId =
ID:nwdellsrv3-31125-1224836545198-1:117:1:1, destination = topic:/Job,
transactionId = null, expiration = 1224836778820, timestamp = 1224836587945,
arrival = 0, brokerInTime = 1224839224998, brokerOutTime = 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@15545e1, marshalledProperties =
org.apache.activemq.util.ByteSequence@15eb776, dataStructure = null,
redeliveryCounter = 0, size = 0, properties = null, readOnlyProperties =
false, readOnlyBody = false, droppable = false, text = null} to dead letter
queue
same sender code,machine A and B the same setting,
If the sender is running on the same machine with ActiveMQ(Machine A), the
receivers on machine A and B can receive the messages. But if the sender is
not collocated with ActiveMQ(Sender on machine B),the AMQ will print the
above WARNs and receivers can not receive any message!
--
View this message in context: http://www.nabble.com/What-this-means--Urgent%21%21-tp20146952p20146952.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: What this means? Urgent!!
Posted by Bruce Snyder <br...@gmail.com>.
On Fri, Oct 24, 2008 at 3:25 AM, bill richard <bi...@126.com> wrote:
>
> 2008-10-24 17:07:04,998 [91.249.93:31885] WARN RegionBroker
> - Failed to send ActiveMQTextMessage {commandId = 5, responseRequired =
> true, messageId = ID:nwdellsrv3-31125-1224836545198-1:117:1:1:1,
> originalDestination = null, originalTransactionId = null, producerId =
> ID:nwdellsrv3-31125-1224836545198-1:117:1:1, destination = topic:/Job,
> transactionId = null, expiration = 1224836778820, timestamp = 1224836587945,
> arrival = 0, brokerInTime = 1224839224998, brokerOutTime = 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@15545e1, marshalledProperties =
> org.apache.activemq.util.ByteSequence@15eb776, dataStructure = null,
> redeliveryCounter = 0, size = 0, properties = null, readOnlyProperties =
> false, readOnlyBody = false, droppable = false, text = null} to dead letter
> queue
>
> same sender code,machine A and B the same setting,
> If the sender is running on the same machine with ActiveMQ(Machine A), the
> receivers on machine A and B can receive the messages. But if the sender is
> not collocated with ActiveMQ(Sender on machine B),the AMQ will print the
> above WARNs and receivers can not receive any message!
It looks like the messages are going into the dead letter queue (DLQ)
because they're expiring. Notice the expiration = 1224836778820 in the
output (which is actually Fri Oct 24 02:26:18 MDT 2008). An expiration
is only set if the timeToLive is being set on the messages and then
the task of delivery is taking long enough that the messages are
expiring and being sent to the DLQ. This is correct behavior because
the timeToLive is being set.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Blog: http://bruceblog.org/