TCP/IP adapter + BizTalk with aysnchnrous request

Question

This is my scenario:
I have a Console App A which is Asynchronous Client(get the link from http://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110).aspx).It is sending a
NCPDP message to a another Console App B which is Asynchronous Server(get the http://msdn.microsoft.com/en-us/library/fx6588te(v=vs.110).aspx).
I am getting the NCPDP message from database.
Now I want to send this NCPDP message to BizTalk Server through TCP/IP adapter.BizTalk will send this message to another Console App C which is Asynchronous Server
(get the http://msdn.microsoft.com/en-us/library/fx6588te(v=vs.110).aspx).This server will send the NCPDP message to a another Console App D which is Asynchronous
Client.This Console App D will get the response(new NCPDP message) from DB according to coming NCPDP message and send it to App C.App C will send this response to
BizTalk Server through TCP/IP adapter.And BizTalk will send this response to App B and App B will send this response to App A.
But the problem is that untill I get the response from BizTalk, I am unable to send another request from console app A to app B.
I want that BizTalk process multiple request at the same time.
I want that My console app A will not wait for BizTalk response to send another request.
How it is possible ?
The code given in msdn :
http://msdn.microsoft.com/en-us/library/bew39x2a(v=vs.110).aspx
http://msdn.microsoft.com/en-us/library/fx6588te(v=vs.110).aspx
will fulfill my requirement or I have to use some another technique ?
Prakash

Answer 1

I have to ask again why you're doing it this way since this is the third or fourth time you've asked about this scenario and the situation really hasn't changed.
I'll first point out that the names of those samples are a bit ambiguous and very easy to misinterpret. 
The first link is not an "Asynchronous Client".  It is a single threaded client that uses an
asynchronous TCP socket.  Big difference.  The client itself as a whole, specifically the StartClient() method is a synchronous operations, note the three ManualResetEvents.
For clarity, this is not a problem with BizTalk.
To get what you want, your main client program would have to create and manage multiple instances of AsynchronousClinent, each managing a connection internally.  However, at that point, it's important to note that the Synchronous Client
Socket sample will give you the same behavior since the request/response pattern is by nature a synchronous operation.
I will also restate my recommendation to take the functionality of the socket Server and implement it in BizTalk directly.