Discussion:
Differernce b/w suspended and dehydrated messages in BizTalk Messa
(too old to reply)
tenacious
2008-07-13 03:04:00 UTC
Permalink
Hi

Can someone give me a comprehensive idea of all the differences between a
suspended and dehydrated message.
Tomas Restrepo [MVP]
2008-07-13 13:32:24 UTC
Permalink
Post by tenacious
Can someone give me a comprehensive idea of all the differences between a
suspended and dehydrated message.
Suspended messages are instances completely stopped. Either they will be
non-resumable (in which case you can only save the message and terminate the
service instance) or resumable, in which case you can "force" the message to
retry processing but requiring manual intervention for this to happen.

Dehydrated messages are just temporarily stopped until some condition is
triggered. For example, a send port that failed to delivered a message but
has no exhausted its retry count settings, will have the failed messages
dehydrated until the retry interval passes and the transmission is attempted
again.
--
Tomas Restrepo
http://www.devdeo.com/
http://www.winterdom.com/weblog/
Yossi Dahan [MVP]
2008-07-19 08:45:19 UTC
Permalink
One thing to note is that sometimes the two are related.
if you have an orchestration that is dehydrated for a long time, it could
be - for example - that it is waiting for a response from an
orchestartion/port that got suspended, but - of course - as Tomas
explained - dehydrated does not necessary means a problem, where supspended
most often does.
--
Yossi Dahan
http://www.sabratech.co.uk/blogs/yossidahan
Post by Tomas Restrepo [MVP]
Post by tenacious
Can someone give me a comprehensive idea of all the differences between a
suspended and dehydrated message.
Suspended messages are instances completely stopped. Either they will be
non-resumable (in which case you can only save the message and terminate
the service instance) or resumable, in which case you can "force" the
message to retry processing but requiring manual intervention for this to
happen.
Dehydrated messages are just temporarily stopped until some condition is
triggered. For example, a send port that failed to delivered a message but
has no exhausted its retry count settings, will have the failed messages
dehydrated until the retry interval passes and the transmission is
attempted again.
--
Tomas Restrepo
http://www.devdeo.com/
http://www.winterdom.com/weblog/
samadkhan
2008-08-21 14:39:00 UTC
Permalink
Hi Tenacious,

If a service instance is dehydrated it means it’s been written to disk (e.g.
to the MessageBox) and suspended means the service instance has been
suspended (may be do to failure) and the message has been queued until the
service instance resumes processing.

Enjoy,
Samad

Loading...