Thanks Mike - The server restart seems to clean-up hung connections that are causing deliveries behind them to pile up in the PENDING state.
FIX 45 seems to be reallya workaround , not a fix, since it allows deliveries to “bypass” the hung connections (which is good), but does not fix the first problem (the connections hanging).
Rupinder - it’s interesting that FIX 51 solved your problem with empty bizdocs in processing rules. We ran across this problem 2 years back (TN 4, maybe TN 3.6 (?) - I’m not sure). WM could not fix it, and so we’ve run all our processing rules synchronously since then. I think it’s sad if it took WM 2 years to fix async processing rules. It’s wierd how the tn.doc:view seems to cause empty bizdocs to materialize. 
I’ve asked my SR person about using FIX 51 to fix our empty bizdoc problem in delivery services. He’s going to check with PD. In the meantime he recommended I set my watt.net.timeout parameter to timeout network connections in 5 minutes (it’s set to 0 right now)… I’m in two minds about this since I can’t duplicate this problem in testing.
See this mail from Pam - a WM customer on another mailing list - PENDING deliveries is indeed a ‘hot’ issue for them as well.
[url=“http://eai.ittoolbox.com/groups/groups.asp?v=webmethods-l&i=237975”]http://eai.ittoolbox.com/groups/groups.asp?v=webmethods-l&i=237975[/url]
Can anyone share values they’re using for the watt.net.timeout server.cnf parameter ?