Add extra debug to facilitate diagnosing of QA test failures

The test rawresources01_2b RawResources01_2b_Test081 (part of narayana QA test suite) was seen to fail because the port that the object adapter (for the recovery manager) wants to listen on is in use. Our logging does not indicate which process/test originally opened the port so we need a little bit of extra debug to get the state of all sockets (using netstat) and we need to ensure that each test logs the pid of each CORBA server and client used in the test. Then we should be able to identify which test originally opened the socket.

i di

I am attaching a test log that shows an example of the kind of failure we would like to debug (I did take a copy of all of the qa artifacts which I will keep for a limited time period).