|
Home > Archive > BizTalk Server Orchestration > May 2006 > Problem using the delay shape in a loop
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 |
Problem using the delay shape in a loop
|
|
|
| I would appreciate help on this problem:
The orchestration is looping and sending IDOCs (RFQs) to SAP. It seems to be
too fast for SAP, so we need to introduce a delay between each IDOC sent (10
seconds for example).
I am having a problem with the delay shape. I get the error below most of
the time. If I use the debugger, it works sometimes!
I have made the orchestration to be a LONG RUNNING transaction, just in case
it is a persistence issue (dehydration/rehydration). But still it is the same
problem.
Are there any special requirements for using the Delay Shape?
Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10034
Date: 5/22/2006
Time: 1:31:47 PM
User: N/A
Computer: ADG-DEV-BPM
Description:
Uncaught exception terminated service
EBidding_SAP_Inbound.orcSAPInbound(561d99fa-0dec-dc96-267c-5a2c178e94fc),
instance 4f9303f2-3bf8-4860-a8d0-2c6386bc1522
Object reference not set to an instance of an object.
Exception type: NullReferenceException
Source: BizTalkXML
Target Site: System.Xml.XmlNode Item(Int32)
Help Link:
Additional error information:
| |
| Eric Stott 2006-05-23, 1:15 am |
| I am not sure that it is the delay shape that is causing the problem.
Are you filtering/making decisions based on sometimes optional promoted
properties?
Eric
http://stottcreations.com/blog
"Fady" <Fady@discussions.microsoft.com> wrote in message
news:97EB62C2-D575-44A2-9E57-222803C99DBB@microsoft.com...
>I would appreciate help on this problem:
>
> The orchestration is looping and sending IDOCs (RFQs) to SAP. It seems to
> be
> too fast for SAP, so we need to introduce a delay between each IDOC sent
> (10
> seconds for example).
>
> I am having a problem with the delay shape. I get the error below most of
> the time. If I use the debugger, it works sometimes!
>
> I have made the orchestration to be a LONG RUNNING transaction, just in
> case
> it is a persistence issue (dehydration/rehydration). But still it is the
> same
> problem.
>
> Are there any special requirements for using the Delay Shape?
>
>
> Event Type: Error
> Event Source: XLANG/s
> Event Category: None
> Event ID: 10034
> Date: 5/22/2006
> Time: 1:31:47 PM
> User: N/A
> Computer: ADG-DEV-BPM
> Description:
> Uncaught exception terminated service
> EBidding_SAP_Inbound.orcSAPInbound(561d99fa-0dec-dc96-267c-5a2c178e94fc),
> instance 4f9303f2-3bf8-4860-a8d0-2c6386bc1522
>
> Object reference not set to an instance of an object.
>
> Exception type: NullReferenceException
> Source: BizTalkXML
> Target Site: System.Xml.XmlNode Item(Int32)
> Help Link:
> Additional error information:
| |
|
| No I am not.
Basically, I have a master document that contains a number of sub documents.
I loop through the sub documents and send each one of them to SAP. This is
happening too fast for SAP, so I need to have a delay between each document
sent to SAP of about 10 seconds. To achieve that I am using the delay shape
(BizTalk 2004) inside the loop. However, the Orchestration fails after
hitting the delay shape with error "NullReferenceException". If there is no
delay shape in the loop, it works just fine (but SAP can not handle it).
I have a feeling that it has to do with the Orchestartion the dehydrated
because of the existence of a delay shape in the loop, but I am not sure.
"Eric Stott" wrote:
> I am not sure that it is the delay shape that is causing the problem.
> Are you filtering/making decisions based on sometimes optional promoted
> properties?
> Eric
> http://stottcreations.com/blog
>
> "Fady" <Fady@discussions.microsoft.com> wrote in message
> news:97EB62C2-D575-44A2-9E57-222803C99DBB@microsoft.com...
>
>
>
| |
|
| If I may add, a partial screenshot of the orchestration can be viewed at:
http://www.lajolla.com/orch.htm
Thanks
"Fady" wrote:
[vbcol=seagreen]
> No I am not.
>
> Basically, I have a master document that contains a number of sub documents.
> I loop through the sub documents and send each one of them to SAP. This is
> happening too fast for SAP, so I need to have a delay between each document
> sent to SAP of about 10 seconds. To achieve that I am using the delay shape
> (BizTalk 2004) inside the loop. However, the Orchestration fails after
> hitting the delay shape with error "NullReferenceException". If there is no
> delay shape in the loop, it works just fine (but SAP can not handle it).
>
> I have a feeling that it has to do with the Orchestartion the dehydrated
> because of the existence of a delay shape in the loop, but I am not sure.
>
> "Eric Stott" wrote:
>
| |
| Eric Stott 2006-05-23, 1:15 pm |
| What is the logic you have in the delay shape?
"Fady" <Fady@discussions.microsoft.com> wrote in message
news:F1DC9B8F-EE68-4D08-9D2F-F0C5AC53C9EF@microsoft.com...[vbcol=seagreen]
> No I am not.
>
> Basically, I have a master document that contains a number of sub
> documents.
> I loop through the sub documents and send each one of them to SAP. This is
> happening too fast for SAP, so I need to have a delay between each
> document
> sent to SAP of about 10 seconds. To achieve that I am using the delay
> shape
> (BizTalk 2004) inside the loop. However, the Orchestration fails after
> hitting the delay shape with error "NullReferenceException". If there is
> no
> delay shape in the loop, it works just fine (but SAP can not handle it).
>
> I have a feeling that it has to do with the Orchestartion the dehydrated
> because of the existence of a delay shape in the loop, but I am not sure.
>
> "Eric Stott" wrote:
>
| |
|
| Ok, I found out what was the problem.
I was using a custom type which I had created to get around the XmlNodeList
not being serializable. My workaround for this was to create a custom
XmlNodeList that "pretended" to be serializable. Basically, I had the
serializable attribute and the ISerializable interface, but no implementation
code for the interface (because I did not need it at the time).
So, things were working fine until I had to introduce the delay shape. The
delay shape will dehydrate and hydrate the message (i.e. serialization). So,
I was getting the NullReference exception because my custom type did not
really know how to be serialized / deserialized.
So, just by adding the implementation code for the ISerializable interface
in the custom type, the problem was solved.
Jon Flanders talks about this at:
http://www.traceofthought.net/Perma...7a5316e2dd.aspx
Thank you Eric; and thank you Jon.
Fady
========================================
==
"Eric Stott" wrote:
> What is the logic you have in the delay shape?
> "Fady" <Fady@discussions.microsoft.com> wrote in message
> news:F1DC9B8F-EE68-4D08-9D2F-F0C5AC53C9EF@microsoft.com...
>
>
>
|
|
|
|
|