- This topic has 10 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hi all,
I’m facing a weired problem with BizTalk 2006.
The
Problem is that i’m observing sudden termonation of some of the running
orchestrations in BizTalk and i’m not able to define the reason neither
to track the History of the Lost Orchestration.Note that most of the orchestration are passing the whole workflow without any problem but some of them are crashing.
What i require id the see if there are any possibility to track the orchestrations somewhere in BizTalk Databases.
PS: I’m configuring the following Databases:
– BizTalkDTADb
– BizTalkMgmtDb
– BizTalkMsgBox
– BizTalkRuleEngineDbThanks a lot
GMK
-
GMK,
More questions than answers I’m afraid:
- Why do you believe the orchestrations are terminating unexpectedly? Are you seeing suspended orchestration instances in HAT?
- Do you have an errors in the Event Log (BizTalk is pretty good at complaining when it encounters a problem)
- You mention that you’re configuring some of the databases – are you just installing BizTalk, or are you re-configuring your installation? What configuration are you doing?
Nick.
-
Hi Nick,
Concerning your first Question:
I’m integrating BizTalk with K2, the Normal flow of the WorkFlow consists that BizTalk creates a Task in K2 and then K2 Must send a response to BizTalk in order to continue the workflow. In the time BizTalk is waiting the response in K2, the Orchestration is dehydrated. the problem occuring is that when the Task in K2 in created, and once K2 Reponse reachs BizTalk, Routing Failure error take please because the orchestration that should be in the “Dehydrated” status is no long existing in the administration Console, This is how i know that the Biztalk Orchestration in terminated suddenly and without being able to trace it .
Concerning the 2de question:
In the event Log we have fully of errors and they are all similar and there are no significal errors that would give us any idea about the LOST orchestration.
Concerning the Thrid quest:
We are not re-configuring Biztalk, this is the initial installation that took place aroud 1 year ago and we are facing this problem lately.
Thanks a lot
GMK.
-
GMK,
Unfortunately, I’m not that knowledgeable on K2, apart from a basic understanding of what it does – others on this forum maybe able to help.
However, I would suggest that you speak with K2 and their support team or forums to see whether this is a K2 issue.
Rgds, Nick.
-
Hi,
I don’t think it would be a problem from K2.
But what i would like to know is where can i check the “Tracking DataBase in BizTalk” ?
Regds,
GMK
-
GMK,
You will see suspended orchestration instances in the BizTalk Admin Console; terminated instances will not appear as they have completed.
I still believe this could be K2 related as I have never heard (in the last four years) of an orchestration terminating unexpectedly without throwing lots of errors in the Event Log or suspending as non-resumable in the Admin Console.
Nick.
-
-
-
[quote user="gmk51080"]
I’m integrating BizTalk with K2, the Normal flow of the WorkFlow consists that BizTalk creates a Task in K2 and then K2 Must send a response to BizTalk in order to continue the workflow. In the time BizTalk is waiting the response in K2, the Orchestration is dehydrated. the problem occuring is that when the Task in K2 in created, and once K2 Reponse reachs BizTalk, Routing Failure error take please because the orchestration that should be in the “Dehydrated” status is no long existing in the administration Console, This is how i know that the Biztalk Orchestration in terminated suddenly and without being able to trace it .
[/quote]
How do you have your BizTalk Orchestration configured to wait for the response from K2? I have a similar process where I have to wait for 3 files that make up an invoice before continuing the Orchestration. I use the Listen shape to accomplish this. It sounds like your orchetration is sending a message to K2 and then dehydrating before it gets a response back. If you’re not using a listening shape, try that.
Can you break the orchestration up? Can you have 1 orchestration send a message to K2, then terminate and have a second orchestration that listens for response message from K2?
-
Hi,
You are totally right, we are not using listen shapes, all what we are doing is to send a Request to K2 in order to create a new Task in K2 ( using the K2 / BizTalk adapter provided by K2 Team), Once the K2 Task is closed in K2 it send a response to BizTalk in order to continue the orchestration.
The weird issue in this case is that we are not able to reproduce the error when we need it , and we are observing this error on our client’s site and not on our development environment.
Most of the Orchestration do not break and works as it should work and completes normally, suddenly and without being able to understand the reasons some of the orchestration are disapearing.
This is our case that we are facing without being able to describe more about the problem. The Problem is not occurring in a regular way.
We can have aroun 300 orchestration normally completed and 1 or 2 or even 10 orchestrations disapearing.
regards.
GMK
-
[quote user="gmk51080"]
This is our case that we are facing without being able to describe more about the problem. The Problem is not occurring in a regular way.
[/quote]
This sounds like ait could be a timing issue that a Listen shape could fix. Think about it. Sometimes K2 responds quickly and everything works as it should. Other times K2 take a bit too long to respond and the Orchestration dehydrates.
Reproducing this problems is nearly impossible, because it’s not something you can control.
Try using a Listen shape and let us know if it corrects the problem.
-
The problem is that Listen shapes does not solve anything in my
case, when i put a listen shape i have to wait a response from 2
destinations, but in my case i’m waiting response just from K2, so
there are no need for Listen Shapes.Even if we put a
certain delay in the WorkFlow nothing will change since once the
orchestration send the request to K2 it will automatically have the
“Dehydrated” staus. The problem is that we are not able to know if the
Orchestration has disapeared on the moment it was still active or
dehydrated.That’s why we need to search in the History to see at which status it has been disapeared from the administration Console.
Thanks a lot
GMK
-
GMK,
To refer back to my previous point about messages in HAT/BizTalk Admin Console: You will see suspended orchestration instances in the BizTalk Admin
Console; terminated instances will not appear as they have ‘completed’. Furthermore, an orchestration will not terminate unexpectedly without raising some error in the Event Log.I’m presuming that the logical port on the orchestration that calls K2 is a request/response port and that you have a receive shape connected to the response element of the [logical] port? I’m further presuming that the orchestration is dehydrating while waiting for the response to come back in? and that the orchestration is terminating while waiting for the response?
If this is the case and you are experiencing intermittent problems, I would suggest that you are having infrastructure issues – are you seeing anything in the event log to suggest that the orchestrations are being terminated by an external process, are creating zombies or BizTalk is losing its connection to the database?
If you could provide some examples of the errors you are experiencing around the time that the routing failure occurs, that would be helpful.
Cheers, Nick.
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.