locked
Anomalous fail of call to BTSHTTPReceive.dll RRS feed

  • Question

  • User-1684906711 posted

    I have a "thin" asmx service which receives messages and simply calls the Biztalk HTTP Adapter implemented as an ISAPI extension. The web service is called from a WebSphere-implemented JAX-RPC web service.  The WAS service reads a table for seed info, builds a message and fires it.  No metering.

    Problem: anomalously, and not under load, the asmx will attempt to call the BTHTTPReceive.dll and fail. 

    IIS Logs:

    Successful receive/call: 

    206.194.129.173 POST /AOC.eTrip.JINDEXIntegration.JINDEXWebService/JINDEXService.asmx - 80 - 206.194.129.240 IBM+WebServices/1.0 200 0 0
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 2 2148074254
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 1 0
    2008-11-21 06:06:03 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 COURTS\SVC_JinDexAppPool 127.0.0.1 - 200 0 0

    Failed receive/call:

    W3SVC1 206.194.129.173 POST /AOC.eTrip.JINDEXIntegration.JINDEXWebService/JINDEXService.asmx - 80 - 206.194.129.240 IBM+WebServices/1.0 200 0 0
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 2 2148074254
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 1 0
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /AOC.eTrip.JindexIntegration.WebServices/JINDEXService.asmx - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 200 0 0
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /AOC.eTrip.JindexIntegration.WebServices/JINDEXService.asmx - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 200 0 0
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 COURTS\SVC_JinDexAppPool 127.0.0.1 - 200 0 0

     My suspicion is that the BTSHTTPReceive.dll is faulty in some sense in either implementation or configuration within IIS. I note that the Recycling is set to 1740 minutes (?!)...this seems a useless value...

    Q:

    What is a reasonable interval for recycling (particularly this ISAPI extension)?

    Are there any know issues with IIS and BTSHTTPReceive.dll and IIS?

    Would it be a request buffering setting or ????

    FWIW, I'm just learning IIS/Biztalk

    Thanks,

    Michael 

     

     

     

     

     

     

     

     

     

    call:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

    Monday, November 24, 2008 7:15 PM

Answers

  • User157784788 posted

    Here is what I see in Failure and Successful Posts: 

    Failure
    =====
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 2 2148074254

    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 1 0

    Success
    =======
    2008-11-21 06:06:03 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 COURTS\SVC_JinDexAppPool 127.0.0.1 - 200 0 0

    In the successful post, You can see the credentials have been passed successfully whereas in failed ones, I don’t see any identity.

    You will need to find out what authentication the biztalk app needs and how it has been configured i.e. is it impersonating the app pool identity or the authenticated user.

    So above is just one thing that you could verify. Other than that, you will need to check if there is a Hang in BTSHTTPReceive.dll - Try browsing it directly. If it hangs, take manual hang dump using debug diag.

    As this fails intermitantly, this might be related to NIC/Networking/SQL connectivity/Response,etc. You will need to take different troubleshooting apporaches to isolate this further.You can find clues in event logs for the failure errors. At the time of the issue, check what events are logged in biztalk. My guess is, you may see SQL connectivity related errors. Have a look at this KB - http://support.microsoft.com/kb/899599

    HTH.

    ~ Ganesh

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, November 26, 2008 12:19 AM

All replies

  • User157784788 posted

    Here is what I see in Failure and Successful Posts: 

    Failure
    =====
    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 2 2148074254

    2008-11-21 06:06:02 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 - 127.0.0.1 - 401 1 0

    Success
    =======
    2008-11-21 06:06:03 W3SVC1 127.0.0.1 POST /BizTalkHTTPReceive/BTSHTTPReceive.dll AOC_ReceiveAOC 80 COURTS\SVC_JinDexAppPool 127.0.0.1 - 200 0 0

    In the successful post, You can see the credentials have been passed successfully whereas in failed ones, I don’t see any identity.

    You will need to find out what authentication the biztalk app needs and how it has been configured i.e. is it impersonating the app pool identity or the authenticated user.

    So above is just one thing that you could verify. Other than that, you will need to check if there is a Hang in BTSHTTPReceive.dll - Try browsing it directly. If it hangs, take manual hang dump using debug diag.

    As this fails intermitantly, this might be related to NIC/Networking/SQL connectivity/Response,etc. You will need to take different troubleshooting apporaches to isolate this further.You can find clues in event logs for the failure errors. At the time of the issue, check what events are logged in biztalk. My guess is, you may see SQL connectivity related errors. Have a look at this KB - http://support.microsoft.com/kb/899599

    HTH.

    ~ Ganesh

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, November 26, 2008 12:19 AM
  • User-1684906711 posted

    Thank you, Ganesh...

    I'm a bit unclear about this bit: "..Hang in BTSHTTPReceive.dll...try browsing it directly"..

    .I'm not sure how you mean to "browse it directly" and what is a "hang dump"...Is this something peculiar to DLL? ** Please, can you flesh this out a bit?**

    (I'm very suspicious that the adapter dll is starving for threads and needs process recycle...but I thought the DLL , if properly written, would automatically respond to server "pings" with an "ISAPI UNHEALTHY" or some such, automatically causing a process recycle)

    Again, thank you very much,

    M

    Wednesday, November 26, 2008 11:08 AM