|
Home > Archive > BizTalk Server Orchestration > December 2005 > message delivered to WebService but 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 |
message delivered to WebService but not consumed
|
|
| PeterW 2005-12-14, 7:49 am |
| I add a WebReference to a WebService and make calls from Biztalk successfully.
The orchestration uses a priming message to start processing and then enters
a timed loop that runs indefinitely. It then makes a sysnchronous WebService
call and returns the response. This works fine.
Changes are made to the WebService (added extra WebMethods). Recompiled. In
the orchestration, using either WebReference update, or Delete and add new,
then make the changes to the messages to reflect the changed Webreference.
Update expressions shapes as necessary to reflect results.
Reattach messages to shapes, recompile and redeploy. Configure and bind ports.
Bind orchestration and start. Drop priming message.
Now instead of a webMethod call resulting in a response, HAT reveals that
the message was delivered, but not consumed.
There are no errors reported, the orchestration just does not seem to get
any return from the WebMethod call.
Does anyone have any ideas why this might be.
We have also created a simple test WebService with simple webMethods that
send a string and returns a string where we have also added webMethods but
everything keeps working.
Any pointers would be very much appreciated.
cheers
--
PeterW
| |
| Leo Gan 2005-12-19, 8:49 pm |
| Any events? (In Event Viewer)
--
Regards,
Leonid Ganeline,
BizTalk Developer
Vancouver
http://public.fotki.com/leogan/
"PeterW" <nspw@noemail.nospam> wrote in message
news:280C63DE-D754-4452-99EA-C2E63BAF5E60@microsoft.com...
>I add a WebReference to a WebService and make calls from Biztalk
>successfully.
> The orchestration uses a priming message to start processing and then
> enters
> a timed loop that runs indefinitely. It then makes a sysnchronous
> WebService
> call and returns the response. This works fine.
>
> Changes are made to the WebService (added extra WebMethods). Recompiled.
> In
> the orchestration, using either WebReference update, or Delete and add
> new,
> then make the changes to the messages to reflect the changed Webreference.
> Update expressions shapes as necessary to reflect results.
>
> Reattach messages to shapes, recompile and redeploy. Configure and bind
> ports.
> Bind orchestration and start. Drop priming message.
>
> Now instead of a webMethod call resulting in a response, HAT reveals that
> the message was delivered, but not consumed.
>
> There are no errors reported, the orchestration just does not seem to get
> any return from the WebMethod call.
>
> Does anyone have any ideas why this might be.
>
> We have also created a simple test WebService with simple webMethods that
> send a string and returns a string where we have also added webMethods but
> everything keeps working.
>
> Any pointers would be very much appreciated.
>
> cheers
> --
> PeterW
| |
| PeterW 2005-12-20, 5:54 pm |
| I figured it out.
I had changed the url for the WebReference and not done the same when
binding the physical WebPort.
cheers
--
PeterW
"Leo Gan" wrote:
> Any events? (In Event Viewer)
>
> --
> Regards,
>
> Leonid Ganeline,
> BizTalk Developer
> Vancouver
> http://public.fotki.com/leogan/
> "PeterW" <nspw@noemail.nospam> wrote in message
> news:280C63DE-D754-4452-99EA-C2E63BAF5E60@microsoft.com...
>
>
>
|
|
|
|
|