SourceForge.net
2003-08-13 13:04:39 UTC
Bugs item #788029, was opened at 2003-08-13 23:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=788029&group_id=54559
Category: message engine
Group: v0.7.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: Could not get message for handle error
Initial Comment:
The "Could not get message for handle error" reported a
number of times (e.g
https://sourceforge.net/forum/forum.php?
thread_id=886169&forum_id=181831), is occurring due
to a race condition between the closure and
resubscription of an asynchronous durable topic
subscriber.
It is compounded by the TopicConsumerEndpoint re-
adding the failed handle back in the message cache via
returnMessage() so that the same error occurs multiple
times.
ConsumerEndpoint needs to change so that it
synchronizes on the termination of the asynchronous
message delivery thread.
TopicConsumerEndpoint needs to change so that it
doesn't put the message back in the cache if it can't be
resolved.
(NB: this is not easy to reproduce...)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=788029&group_id=54559
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=788029&group_id=54559
Category: message engine
Group: v0.7.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: Could not get message for handle error
Initial Comment:
The "Could not get message for handle error" reported a
number of times (e.g
https://sourceforge.net/forum/forum.php?
thread_id=886169&forum_id=181831), is occurring due
to a race condition between the closure and
resubscription of an asynchronous durable topic
subscriber.
It is compounded by the TopicConsumerEndpoint re-
adding the failed handle back in the message cache via
returnMessage() so that the same error occurs multiple
times.
ConsumerEndpoint needs to change so that it
synchronizes on the termination of the asynchronous
message delivery thread.
TopicConsumerEndpoint needs to change so that it
doesn't put the message back in the cache if it can't be
resolved.
(NB: this is not easy to reproduce...)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=788029&group_id=54559