|
Home > Archive > BizTalk Server General > July 2004 > Web Service response has only null values
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 |
Web Service response has only null values
|
|
| Christoffer 2004-07-09, 3:31 pm |
| Hello, I've got a slight problem...
I have created an Orchestration and published it as a Web Service. The
Orchestration receives a message and passes it on to a HttpSolicitResponse.
The response from the HttpSolicitResponse is then passed back to the Web
Service.
All this works wonderfully, except when the client calling the Web Service
retrieves the returned message, all values are set to null (or zero). I've
used pretty much every options and feature in the Health and Activity
Tracking application but can not find where the values are set to null.
This said, I don't know if the BizTalk is causing the problem or if it is a
client-side problem. However, I have tested with two types of clients and
both have the same behaviour.
Any help is appreciated!
/Chris
| |
| Christof [MVP] 2004-07-09, 3:31 pm |
| A network trace or the SOAP toolkit intermediary SOAP handler could point
some things out here. You might debug your orchestration as well.
Best regards,
Christof
--
Christof [Microsoft BizTalk Server MVP]
"Christoffer" <christoffer@nospam.com> wrote in message
news:uYJfjIPZEHA.3480@TK2MSFTNGP11.phx.gbl...
> Hello, I've got a slight problem...
>
> I have created an Orchestration and published it as a Web Service. The
> Orchestration receives a message and passes it on to a
HttpSolicitResponse.
> The response from the HttpSolicitResponse is then passed back to the Web
> Service.
>
> All this works wonderfully, except when the client calling the Web Service
> retrieves the returned message, all values are set to null (or zero). I've
> used pretty much every options and feature in the Health and Activity
> Tracking application but can not find where the values are set to null.
>
> This said, I don't know if the BizTalk is causing the problem or if it is
a
> client-side problem. However, I have tested with two types of clients and
> both have the same behaviour.
>
> Any help is appreciated!
>
> /Chris
>
>
| |
| Christoffer 2004-07-09, 3:31 pm |
| Could you please provider more information on how to debug the Web Service
send pipeline and send port?
I've run a couple of tests:
Scenario A, which does not work:
1. Client delivers a message to the Web Service
2. Orchestration delivers message to HttpSolicitResponse
3. Orchestration receives response message from HttpSolicitResponse
4. Orchestration delivers response message to Web Service
5. Client receives response message with null values
Scenario B, which does work:
1. Client delivers a message to the Web Service
2. Orchestration transforms message to a response message
3. Orchestration delivers response message to Web Service
4. Client receives response message with correct values
These scenarios point to the fact that the HttpSolicitResponse is faulty,
however, I've run careful debugging and looked through all the messages and
can't find the problem. So I ran a third test:
Scenario C:
1. Client delivers a message to the Web Service
2. Orchestration delivers message to HttpSolicitResponse
3. Orchestration receives response message from HttpSolicitResponse
4. Orchestration sends reponse message to a File port
4. Orchestration delivers response message to Web Service
5. Client receives response message with null values
Now, if the HttpSolicitResponse were faulty, the result from the File port
should also be null values, but it isn't. The output from the File port is
correct.
This leads me to the conclusion that the Web Service send pipeline or send
port is faulty. I need to trace or debug it but I don't know how to. I'm
just getting started with BizTalk so I'm struggling finding tools and
features  Again, any help is much appreciated!
Regards,
Chris
"Christof [MVP]" <bts2004communityfeedback (at) hotmail (dot) com> skrev i
meddelandet news:O8qgljQZEHA.808@tk2msftngp13.phx.gbl...
> A network trace or the SOAP toolkit intermediary SOAP handler could point
> some things out here. You might debug your orchestration as well.
>
> Best regards,
> Christof
>
> --
> Christof [Microsoft BizTalk Server MVP]
>
> "Christoffer" <christoffer@nospam.com> wrote in message
> news:uYJfjIPZEHA.3480@TK2MSFTNGP11.phx.gbl...
> HttpSolicitResponse.
Service[vbcol=seagreen]
I've[vbcol=seagreen]
is[vbcol=seagreen]
> a
and[vbcol=seagreen]
>
>
|
|
|
|
|