Connection manager objects - waiting for resource issue

I posted a few days ago about a 'blocking' problem i am getting on a
connection manager object when it is being used by a web service
function call.

I've tried various things to work around the problem but without any
luck.

The process that gets locked out reports a connection status of
'waiting for resource', what exactly does this refer to?

My other question is, is it a good/better/bad/possible to use separate
connection manager objects connecting to the same IP for separate
processess within the same application albeit running on separate
threads? Is it even possible to force a socket or web service object to
use a specific connection manager?

Chris