SourceForge.net
2003-08-21 09:37:25 UTC
Bugs item #788029, was opened at 2003-08-13 06:04
Message generated for change (Comment added) made by rpolepalli
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: Closed
Resolution: Fixed
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...)
----------------------------------------------------------------------
Comment By: Rama Polepalli (rpolepalli)
Date: 2003-08-21 02:37
Message:
Logged In: YES
user_id=849129
I'm using OpenJMS-0.7.4 version. I use postgresql database
for persistence. I'm running the application on Redhat 7.3. If
my subscriber is not started, I get this error repeatedly. Is it
possible to incorporate this fix in my application?
Please let me know
----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2003-08-13 06:35
Message:
Logged In: YES
user_id=557161
Fixed in CVS. Will be available in the 0.7.6 release.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=788029&group_id=54559
Message generated for change (Comment added) made by rpolepalli
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: Closed
Resolution: Fixed
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...)
----------------------------------------------------------------------
Comment By: Rama Polepalli (rpolepalli)
Date: 2003-08-21 02:37
Message:
Logged In: YES
user_id=849129
I'm using OpenJMS-0.7.4 version. I use postgresql database
for persistence. I'm running the application on Redhat 7.3. If
my subscriber is not started, I get this error repeatedly. Is it
possible to incorporate this fix in my application?
Please let me know
----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2003-08-13 06:35
Message:
Logged In: YES
user_id=557161
Fixed in CVS. Will be available in the 0.7.6 release.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=788029&group_id=54559