Topic
2 replies Latest Post - ‏2013-01-23T12:30:04Z by SystemAdmin
KSuraj
KSuraj
11 Posts
ACCEPTED ANSWER

Pinned topic SOAP Outstanding Requests.

‏2012-09-07T17:06:54Z |
In WMB v7, we saw a situation where in the incoming SOAP requests were not being responded to by the WMB flow. The EG listener port was up but the requests didnt make it to the Message flows. Later we found that all the SOAP Requests were stuck on the HTTPConnector. We did a mqsireportproperties and saw the following.

DefaultConnector
port='51609'
URLRegistration='/vc/Payables/'
nodeLabel='SOAP Input'
outstandingRequests='29'
This indicates there were 29 requests stcuk without being delivered to the Message flow. Does anybody know where these messages are held internally in WMB.
Updated on 2013-01-23T12:30:04Z at 2013-01-23T12:30:04Z by SystemAdmin
  • WISAdeveloperWorks
    WISAdeveloperWorks
    6 Posts
    ACCEPTED ANSWER

    Re: SOAP Outstanding Requests.

    ‏2012-09-24T12:15:08Z  in response to KSuraj
    Hi,

    Could you provide the full mqsireportproperties command you used to get the information? Are you using the broker-wide listener por the EG embedded one?
  • SystemAdmin
    SystemAdmin
    4179 Posts
    ACCEPTED ANSWER

    Re: SOAP Outstanding Requests.

    ‏2013-01-23T12:30:04Z  in response to KSuraj
    Im facing the same... have you figured out why its stuck their ? however the flow is tested locally and working as expected...
    also regarding large data, how can I prepare the HTTPConnector to accept such large data (about 4 to 5 MBs)