Question BAM Continuation Issue

  • jeudi 10 mai 2012 14:30
     
     

    I am currently developing a new BAM solution where i have 3 Orchestration. 1 Parent calls one child and the child calls another child. This all happens in one flow sequentially.

    I have exception handling in both child orchestration where am throwing using Throw shape from the child to parent orchestration.

    I am using Continuation (using InterchageID) in TPE. (I am using OrchestationEventStream, dragging shapes from orchestration in TPE).

    Now, when ever any exception occurs in child orchetation, the continuation is not getting completed. It receids in the ActiveTable. However, in case if there are no errors, it completes successfully without any issues.

    Thanks


    SKGuru

Toutes les réponses

  • jeudi 10 mai 2012 14:34
     
     

    Have you set BAM configuration (with TPE) in catch instruction in order to preserve continuation ?

    I would also suggest to use orchestration debugger to ensure process is running well in expected shapes.


    Christophe BRANDO...If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

  • jeudi 10 mai 2012 15:13
     
     

    Thanks, Yes my orchestration runs perfectly fine. Its an existing application where we are incorporating BAM solution. I cannot updated the orchestration to benefit just for BAM.

    "Have you set BAM configuration (with TPE) in catch instruction in order to preserve continuation ?"

    I am not sure what do you mean by this.

    Those child orchestration calls a service where i am capturing the start and end time and corresponding message id. If everything goes fine, i am able to track all the details and it moves to the Completed table.

    Incase of any service failure, it still tracks but the data recised in the Active table and the Continuation is not complete because it goes directly to the exception block where i am throwing the exception.

    I am not sure why this behaviour. Is there any workaround for this.

    Thanks


    SKGuru

  • jeudi 10 mai 2012 15:20
     
     

    May BAM engine doesn't capture data when an exception is thrown by an orchestration ?

    I think that BAM data (exception using BAM API in catch shape for instance) are only collected when port or orchestration instances are well executed. This could not be the case when exception is thrown by orchestration.

    Using BAM API would be one of the solutions.


    Christophe BRANDO...If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.


  • jeudi 10 mai 2012 17:26
     
     
    Is there any solution without using BAM API calls?

    SKGuru

  • jeudi 10 mai 2012 19:44
     
     

    May BAM engine doesn't capture data when an exception is thrown by an orchestration ?

    I think that BAM data (exception using BAM API in catch shape for instance) are only collected when port or orchestration instances are well executed. This could not be the case when exception is thrown by orchestration.

    Using BAM API would be one of the solutions.


    Christophe BRANDO...If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.


    Actually, the data is captured but the Continuation is not getting closed. I could see one entry in the Continuation table. Can anyone tell me how this continuation works. Because as per my knowledge, whenever you initiate Cotinuation using Continuation folder and the ContinuationID folder matches, it should complete despite of error in the called orchestration.

    Basically am using Call orchestration shape to call the child orchestration and mapping the InterchangeID of the call shape to Continuation Folder and the Construct shape InterchangeID of the called orchestration shape is mapped to the ContinuationID folder. According to me, since the call is complete, the Continucation should complete. But it is not.

    Now, some exception occurs in my called orchestration and throws error back to the parent orchestration. So, it should not have an impact on the Continuation which is already over.

    Any thoughts.

    Thanks


    SKGuru

  • vendredi 11 mai 2012 13:12
     
     

    Has anyone come across this issue? What am looking for is whether this is achievable or not?

    Thanks


    SKGuru


    • Modifié SKGuru vendredi 11 mai 2012 13:13
    •