Messages that are sent to the receive location are not suspended when the receive location is disabled in BizTalk Server 2004 (873232)



The information in this article applies to:

  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition

SYMPTOMS

After you publish an orchestration as a Web service in Microsoft BizTalk Server 2004 and the receive location is disabled, the messages that are sent to the receive location are not suspended. The Web service client receives a successful HTTP status code 202 (Accepted).

CAUSE

This problem occurs because the Web Service Publishing Wizard always sets the OneWay attribute to TRUE. This behavior is designed to decouple the ultimate processing of the message. If this behavior did not occur, the client would have to wait synchronously for a response from the service.

RESOLUTION

To resolve this issue, modify the Web Services Description Language (WSDL) code to set the OneWay attribute to FALSE.

MORE INFORMATION

Steps to reproduce the problem

  1. In BizTalk Server 20004, create an orchestration that uses a one-way request/response port, and then publish the orchestration as a Web service.
  2. Disable the receive location. To do this, follow these steps:
    1. Click Start, point to All Programs, point to Microsoft BizTalk Server 2004, and then click BizTalk Server Administration.
    2. In the BizTalk Administration console, expand the Microsoft BizTalk Server 2004 (local) node, and then click Receive Locations.
    3. Right-click your receive location, and then click Disable.
  3. Send a message from the Web service client to the Web service.

    The messages that are sent to the receive location are not suspended. The Web Service client receives a successful HTTP status code.

REFERENCES

For more information, visit the following Microsoft Developer Network (MSDN) Web site:

Modification Type:MajorLast Reviewed:8/16/2004
Keywords:kbBTSMessaging kbBTSOrchestration kbprb kbbug KB873232 kbAudDeveloper