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.
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.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2013-01-23T12:30:04Z by SystemAdmin
Pinned topic SOAP Outstanding Requests.
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-23T12:30:04Z at 2013-01-23T12:30:04Z by SystemAdmin
WISAdeveloperWorks 27000049QC6 Posts
SystemAdmin 110000D4XK4179 PostsACCEPTED ANSWER
Re: SOAP Outstanding Requests.2013-01-23T12:30:04Z in response to KSurajIm 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)