|
Home > Archive > BizTalk Server Orchestration > November 2004 > ....XLANGs.BTXEngine.BTXTimerMessage - Delivered not consumed
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
....XLANGs.BTXEngine.BTXTimerMessage - Delivered not consumed
|
|
| Neal Walters 2004-11-17, 5:48 pm |
| I've got an orchestration that has been "Active" for 15 minutes.
I'm getting the same error a couple of other people have asked about.
From HAT I list all Service Instances. From there, I see the orchestration
that is active and right-click "Service Details". It shows three messages:
It shows three messages:
1) Microsoft.BizTalk.XLANGs.BTXEngine.BTXTimerMessage - Delivered, not
consumed
2) http://Odimo.com/Amazon/schTriggerXML#schTriggerXML - Consumed
3) string - Consumed
I'm NOT doing convoys, no parallel shapes, but I am using a Scope.
The orchestration debugger shows I have just entered the scope and the first
shape in the scope is a Send to a Web-Service (immediately followed by a
Receive from the same Web-Service). The Send is green - and has not
finished.
The SOAP adapter DID return an application error that I found in the
Application EventLog. But typically I get the three retries every 5 minutes,
then the a termination of the orchestration. Instead - my orchestration
still thinks it is active.
Finally, after 15 minutes the orchestration did finish with SOAP error.
The orchestration began at 11:57 and ended at 12:12 (exactly 15 minutes).
The event log does show that it retried every 5 minutes, but the
orchestration did not dehydrate between the 5 minute intervals.
Thanks for your input,
Neal Walters
http://Biztalk-Training.com - Free Biztalk Videos
| |
| Stephen W. Thomas 2004-11-17, 5:48 pm |
| Hello again.
Are you working inside an atomic scope shape?
If so, these will not dehydrate because they have no persistence points and
your calls are probably not Serializable anyway.
The BTXTimerMessages are used for BizTalk internal timers. Since you have a
retry set for 5 minutes you will see this message. I see them pop up all the
time and as far as I can tell they are harmless but annoying. I have yet to
determine exactly why they are Delivered, Not Consumed. I can not see a real
reason for that status on that type of message. In any case, they do not
seem to behave as other Delivered, Not Consumed; meaning they will not
suspend your Orchestration when it finished. Rather, they just seem to go
away.
Hope this helps.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"Neal Walters" wrote:
> I've got an orchestration that has been "Active" for 15 minutes.
> I'm getting the same error a couple of other people have asked about.
>
> From HAT I list all Service Instances. From there, I see the orchestration
> that is active and right-click "Service Details". It shows three messages:
>
> It shows three messages:
> 1) Microsoft.BizTalk.XLANGs.BTXEngine.BTXTimerMessage - Delivered, not
> consumed
> 2) http://Odimo.com/Amazon/schTriggerXML#schTriggerXML - Consumed
> 3) string - Consumed
>
> I'm NOT doing convoys, no parallel shapes, but I am using a Scope.
>
> The orchestration debugger shows I have just entered the scope and the first
> shape in the scope is a Send to a Web-Service (immediately followed by a
> Receive from the same Web-Service). The Send is green - and has not
> finished.
>
> The SOAP adapter DID return an application error that I found in the
> Application EventLog. But typically I get the three retries every 5 minutes,
> then the a termination of the orchestration. Instead - my orchestration
> still thinks it is active.
>
> Finally, after 15 minutes the orchestration did finish with SOAP error.
> The orchestration began at 11:57 and ended at 12:12 (exactly 15 minutes).
> The event log does show that it retried every 5 minutes, but the
> orchestration did not dehydrate between the 5 minute intervals.
>
> Thanks for your input,
> Neal Walters
> http://Biztalk-Training.com - Free Biztalk Videos
>
>
>
>
>
>
>
| |
| Neal Walters 2004-11-18, 5:49 pm |
| No atomic scopes. I have a scope that has "transactiontype=None" and is used
only for the error catching.
Neal
| |
| Stephen W. Thomas 2004-11-18, 8:47 pm |
| I wonder if this has anything to do the NACK’s from the failed SOAP call not
getting sent back correctly… Is the scope marked at synchronized?
This might be way off base, but see if this makes any sense:
If the processing of a request-response message exchange pair fails after
the receive adapter has successfully submitted the request message and the
message is subsequently suspended, a NACK will be routed back to the waiting
two-way receive adapter, the receive adapter may then transmit the fault
message back to the client. Of course this means that the client would
receive a SOAP Fault, what if the client doesn’t understand SOAP Faults? For
these scenarios the SOAP Fault maybe mapped changing the format to one that
the client is expecting and can handle. Also, once the initial request
message is accepted, a processing failure anywhere in the engine resulting in
the message being suspended will result in the NACK being routed back to the
adapter as its response.
(From http://blogs.msdn.com/kevinsmi/arch.../03/172574.aspx)
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"Neal Walters" wrote:
> No atomic scopes. I have a scope that has "transactiontype=None" and is used
> only for the error catching.
>
> Neal
>
|
|
|
|
|