socket questions

[coloradowebdev]

i am working on basically a proxy server that handles requests via remoting
from clients and executes transactions against a third-party server via TCP.

the remoting site works like a champ. my problem is executing the
transactions against the remote server and returning the response to the
remoting client. i can open the socket fine and, if i am executing one
transaction at a time, everything works great. it's when my proxy server
tries to execute multiple transactions, i'm missing something on the socket
end. i have tried both synchronous and asynchronous, but it just seems that
the socket stops listening after one response is received and ignores the
other pending transactions.

i've tried a number of different approaches, and posted messages on the
forums.microsof t board. i have to believe that someone, somewhere has build
a transaction-type system like this one. but most of the samples and advice
that i have received have all pointed to a server listening for and accepting
multiple clients, instead of one application connecting to a remote server
with a number of concurrent (client) connections.

if anyone has any useful links or suggestions, it would be appreciated.
thanks in advance.

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,
post the code you are using to communicate with the remote TCP server, are
you using multithread? each thread generating a connection ?

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:75******** *************** ***********@mic rosoft.com...

i am working on basically a proxy server that handles requests via remoting
from clients and executes transactions against a third-party server via
TCP.

the remoting site works like a champ. my problem is executing the
transactions against the remote server and returning the response to the
remoting client. i can open the socket fine and, if i am executing one
transaction at a time, everything works great. it's when my proxy server
tries to execute multiple transactions, i'm missing something on the
socket
end. i have tried both synchronous and asynchronous, but it just seems
that
the socket stops listening after one response is received and ignores the
other pending transactions.

i've tried a number of different approaches, and posted messages on the
forums.microsof t board. i have to believe that someone, somewhere has
build
a transaction-type system like this one. but most of the samples and
advice
that i have received have all pointed to a server listening for and
accepting
multiple clients, instead of one application connecting to a remote server
with a number of concurrent (client) connections.

if anyone has any useful links or suggestions, it would be appreciated.
thanks in advance.

[coloradowebdev]

i've actually tried a number of different approaches, which i will try to
summarize below...

synchronous: this works fine for one transaction, but sending any more than
one does not (send while waiting for a response from a previous transaction
causes the read to fail (return nothing))

[Send Synchronous, then]
int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
byte[] response = new byte[i];
Array.Copy(buff er,0,response,0 ,i);
//Console.WriteLi ne("Out of Transact : " +
Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
return response;

asynchronous:

i stripped out the last version of asynchronous reading. basically, it was
sending synchronously while listening asynchronously. when something was
received, if it contained the special terminating character, it would raise
an event with the server response as the event argument. the code was a
combination of asynchronous samples from the MSDN site and other references
on the net that used BeginReceive.

I know it can't be THIS hard. I'm adding TCP functionality to the
application that was previously all serial based. the logic in the serial
based one was check if the port is available, if it is send, lock the port
until something is received, return the response, close the port. i'm not a
big TCP/IP person, but i figure there should be some information out there
that would put me on the right path.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,
post the code you are using to communicate with the remote TCP server, are
you using multithread? each thread generating a connection ?

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:75******** *************** ***********@mic rosoft.com...

i am working on basically a proxy server that handles requests via remoting
from clients and executes transactions against a third-party server via
TCP.

the remoting site works like a champ. my problem is executing the
transactions against the remote server and returning the response to the
remoting client. i can open the socket fine and, if i am executing one
transaction at a time, everything works great. it's when my proxy server
tries to execute multiple transactions, i'm missing something on the
socket
end. i have tried both synchronous and asynchronous, but it just seems
that
the socket stops listening after one response is received and ignores the
other pending transactions.

i've tried a number of different approaches, and posted messages on the
forums.microsof t board. i have to believe that someone, somewhere has
build
a transaction-type system like this one. but most of the samples and
advice
that i have received have all pointed to a server listening for and
accepting
multiple clients, instead of one application connecting to a remote server
with a number of concurrent (client) connections.

if anyone has any useful links or suggestions, it would be appreciated.
thanks in advance.

[Abubakar]

> i've actually tried a number of different approaches, which i will try to

synchronous or asynchronous doesnt matter, if the server is just programmed
to accept one connection than it'll just accpt one connection. It could take
multiple connections but maybe its not programmed that way. Have you
contacted the person who built the server? I think the way it used to work
serially, as you said, its working that same way using tcp and may not take
concurrent users/connections.
Just for your information, If I have to program a server to accept multiple
clients I do something like this:

while ( true )
{
TcpClient client = listening_socke t.AcceptTcpClie nt(); //blocking call
// ... do processing with client, maybe open it in a new thread for
communicating, and come back to listening mode.

}

But it seems that they accept a connection, than communicates with the
client and when the client disconnects 'than' go into listening state
again, so to do one transaction at a time.

Ab.
http://joehacker.blogspot.com

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:B2******** *************** ***********@mic rosoft.com...

i've actually tried a number of different approaches, which i will try to
summarize below...

synchronous: this works fine for one transaction, but sending any more than one does not (send while waiting for a response from a previous transaction causes the read to fail (return nothing))

[Send Synchronous, then]
int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
byte[] response = new byte[i];
Array.Copy(buff er,0,response,0 ,i);
//Console.WriteLi ne("Out of Transact : " +
Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
return response;

asynchronous:

i stripped out the last version of asynchronous reading. basically, it was sending synchronously while listening asynchronously. when something was
received, if it contained the special terminating character, it would raise an event with the server response as the event argument. the code was a
combination of asynchronous samples from the MSDN site and other references on the net that used BeginReceive.

I know it can't be THIS hard. I'm adding TCP functionality to the
application that was previously all serial based. the logic in the serial
based one was check if the port is available, if it is send, lock the port
until something is received, return the response, close the port. i'm not a big TCP/IP person, but i figure there should be some information out there
that would put me on the right path.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,
post the code you are using to communicate with the remote TCP server, are you using multithread? each thread generating a connection ?

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message news:75******** *************** ***********@mic rosoft.com...

i am working on basically a proxy server that handles requests via remoting from clients and executes transactions against a third-party server via TCP.

the remoting site works like a champ. my problem is executing the
transactions against the remote server and returning the response to the remoting client. i can open the socket fine and, if i am executing one transaction at a time, everything works great. it's when my proxy server tries to execute multiple transactions, i'm missing something on the
socket
end. i have tried both synchronous and asynchronous, but it just seems that
the socket stops listening after one response is received and ignores the other pending transactions.

i've tried a number of different approaches, and posted messages on the forums.microsof t board. i have to believe that someone, somewhere has
build
a transaction-type system like this one. but most of the samples and
advice
that i have received have all pointed to a server listening for and
accepting
multiple clients, instead of one application connecting to a remote server with a number of concurrent (client) connections.

if anyone has any useful links or suggestions, it would be appreciated. thanks in advance.

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Are you sure all your variables are local to each thread?
Cause I assume you are using threads when dealing with more than one
connection no?

This is part of the code I use :

Thread listenerThread;

Queue connectionQueue = null;

protected void ListenerMethod( )
{
Thread workingthread;

Queue unsyncq = new Queue();
connectionQueue = Queue.Synchroni zed( unsyncq);

TcpClient socket;
TcpListener listener = new TcpListener( Config.Port);
listener.Start( );
while( true)
{
socket = listener.Accept TcpClient();
connectionQueue .Enqueue( socket);

workingthread = new Thread( new ThreadStart( TheConnectionHa ndler));
workingthread.S tart();
}
}

public void TheConnectionHa ndler()
{

TcpClient socket= (TcpClient)conn ectionQueue.Deq ueue();

}
Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:B2******** *************** ***********@mic rosoft.com...

i've actually tried a number of different approaches, which i will try to
summarize below...

synchronous: this works fine for one transaction, but sending any more
than
one does not (send while waiting for a response from a previous
transaction
causes the read to fail (return nothing))

[Send Synchronous, then]
int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
byte[] response = new byte[i];
Array.Copy(buff er,0,response,0 ,i);
//Console.WriteLi ne("Out of Transact : " +
Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
return response;

asynchronous:

i stripped out the last version of asynchronous reading. basically, it
was
sending synchronously while listening asynchronously. when something was
received, if it contained the special terminating character, it would
raise
an event with the server response as the event argument. the code was a
combination of asynchronous samples from the MSDN site and other
references
on the net that used BeginReceive.

I know it can't be THIS hard. I'm adding TCP functionality to the
application that was previously all serial based. the logic in the serial
based one was check if the port is available, if it is send, lock the port
until something is received, return the response, close the port. i'm not
a
big TCP/IP person, but i figure there should be some information out there
that would put me on the right path.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,
post the code you are using to communicate with the remote TCP server,
are
you using multithread? each thread generating a connection ?

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
message
news:75******** *************** ***********@mic rosoft.com...

>i am working on basically a proxy server that handles requests via
>remoting
> from clients and executes transactions against a third-party server via
> TCP.
>
> the remoting site works like a champ. my problem is executing the
> transactions against the remote server and returning the response to
> the
> remoting client. i can open the socket fine and, if i am executing one
> transaction at a time, everything works great. it's when my proxy
> server
> tries to execute multiple transactions, i'm missing something on the
> socket
> end. i have tried both synchronous and asynchronous, but it just seems
> that
> the socket stops listening after one response is received and ignores
> the
> other pending transactions.
>
> i've tried a number of different approaches, and posted messages on the
> forums.microsof t board. i have to believe that someone, somewhere has
> build
> a transaction-type system like this one. but most of the samples and
> advice
> that i have received have all pointed to a server listening for and
> accepting
> multiple clients, instead of one application connecting to a remote
> server
> with a number of concurrent (client) connections.
>
> if anyone has any useful links or suggestions, it would be appreciated.
> thanks in advance.

[coloradowebdev]

i tried separate threads, as well. the code you posted includes a
tcplistener, which is the server side, right? my proxy server (which is
actually a client at this point) will be the one initiating the conversation
with the remote server, not listening for clients to connect, unless i am
missing something.

i was thinking about it (again) last night, and i think my biggest problem
is that i am trying to make something serial that isn't. with my COM ports,
one port is open, handles the transaction, and is closed. with the socket,
multiple connections use the same socket so it isn't as easy as listening to
one channel for a response. the responses seem to be stepping one each other
when responses are received. i think what i want is a synchronous socket call
where i send something and wait for a response, but i need to be able to do
that with 50 simultaneous calls.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

Are you sure all your variables are local to each thread?
Cause I assume you are using threads when dealing with more than one
connection no?

This is part of the code I use :

Thread listenerThread;

Queue connectionQueue = null;

protected void ListenerMethod( )
{
Thread workingthread;

Queue unsyncq = new Queue();
connectionQueue = Queue.Synchroni zed( unsyncq);

TcpClient socket;
TcpListener listener = new TcpListener( Config.Port);
listener.Start( );
while( true)
{
socket = listener.Accept TcpClient();
connectionQueue .Enqueue( socket);

workingthread = new Thread( new ThreadStart( TheConnectionHa ndler));
workingthread.S tart();
}
}

public void TheConnectionHa ndler()
{

TcpClient socket= (TcpClient)conn ectionQueue.Deq ueue();

}
Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:B2******** *************** ***********@mic rosoft.com...

i've actually tried a number of different approaches, which i will try to
summarize below...

synchronous: this works fine for one transaction, but sending any more
than
one does not (send while waiting for a response from a previous
transaction
causes the read to fail (return nothing))

[Send Synchronous, then]
int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
byte[] response = new byte[i];
Array.Copy(buff er,0,response,0 ,i);
//Console.WriteLi ne("Out of Transact : " +
Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
return response;

asynchronous:

i stripped out the last version of asynchronous reading. basically, it
was
sending synchronously while listening asynchronously. when something was
received, if it contained the special terminating character, it would
raise
an event with the server response as the event argument. the code was a
combination of asynchronous samples from the MSDN site and other
references
on the net that used BeginReceive.

I know it can't be THIS hard. I'm adding TCP functionality to the
application that was previously all serial based. the logic in the serial
based one was check if the port is available, if it is send, lock the port
until something is received, return the response, close the port. i'm not
a
big TCP/IP person, but i figure there should be some information out there
that would put me on the right path.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,
post the code you are using to communicate with the remote TCP server,
are
you using multithread? each thread generating a connection ?

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
message
news:75******** *************** ***********@mic rosoft.com...
>i am working on basically a proxy server that handles requests via
>remoting
> from clients and executes transactions against a third-party server via
> TCP.
>
> the remoting site works like a champ. my problem is executing the
> transactions against the remote server and returning the response to
> the
> remoting client. i can open the socket fine and, if i am executing one
> transaction at a time, everything works great. it's when my proxy
> server
> tries to execute multiple transactions, i'm missing something on the
> socket
> end. i have tried both synchronous and asynchronous, but it just seems
> that
> the socket stops listening after one response is received and ignores
> the
> other pending transactions.
>
> i've tried a number of different approaches, and posted messages on the
> forums.microsof t board. i have to believe that someone, somewhere has
> build
> a transaction-type system like this one. but most of the samples and
> advice
> that i have received have all pointed to a server listening for and
> accepting
> multiple clients, instead of one application connecting to a remote
> server
> with a number of concurrent (client) connections.
>
> if anyone has any useful links or suggestions, it would be appreciated.
> thanks in advance.

[coloradowebdev]

their server does accept multiple connections. i can watch my transactions
being processed on their server, its just that my client (when it tries to
send multiple transactions and wait for a response) doesn't handle the
responses properly (their server tries to send the responses, my client just
stops listening, or whatever).

"Abubakar" wrote:

i've actually tried a number of different approaches, which i will try to

synchronous or asynchronous doesnt matter, if the server is just programmed
to accept one connection than it'll just accpt one connection. It could take
multiple connections but maybe its not programmed that way. Have you
contacted the person who built the server? I think the way it used to work
serially, as you said, its working that same way using tcp and may not take
concurrent users/connections.
Just for your information, If I have to program a server to accept multiple
clients I do something like this:

while ( true )
{
TcpClient client = listening_socke t.AcceptTcpClie nt(); //blocking call
// ... do processing with client, maybe open it in a new thread for
communicating, and come back to listening mode.

}

But it seems that they accept a connection, than communicates with the
client and when the client disconnects 'than' go into listening state
again, so to do one transaction at a time.

Ab.
http://joehacker.blogspot.com

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:B2******** *************** ***********@mic rosoft.com...

i've actually tried a number of different approaches, which i will try to
summarize below...

synchronous: this works fine for one transaction, but sending any more

than

one does not (send while waiting for a response from a previous

transaction

causes the read to fail (return nothing))

[Send Synchronous, then]
int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
byte[] response = new byte[i];
Array.Copy(buff er,0,response,0 ,i);
//Console.WriteLi ne("Out of Transact : " +
Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
return response;

asynchronous:

i stripped out the last version of asynchronous reading. basically, it

was

sending synchronously while listening asynchronously. when something was
received, if it contained the special terminating character, it would

raise

an event with the server response as the event argument. the code was a
combination of asynchronous samples from the MSDN site and other

references

on the net that used BeginReceive.

I know it can't be THIS hard. I'm adding TCP functionality to the
application that was previously all serial based. the logic in the serial
based one was check if the port is available, if it is send, lock the port
until something is received, return the response, close the port. i'm not

a

big TCP/IP person, but i figure there should be some information out there
that would put me on the right path.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,
post the code you are using to communicate with the remote TCP server, are you using multithread? each thread generating a connection ?

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message news:75******** *************** ***********@mic rosoft.com...
>i am working on basically a proxy server that handles requests via remoting > from clients and executes transactions against a third-party server via > TCP.
>
> the remoting site works like a champ. my problem is executing the
> transactions against the remote server and returning the response to the > remoting client. i can open the socket fine and, if i am executing one > transaction at a time, everything works great. it's when my proxy server > tries to execute multiple transactions, i'm missing something on the
> socket
> end. i have tried both synchronous and asynchronous, but it just seems > that
> the socket stops listening after one response is received and ignores the > other pending transactions.
>
> i've tried a number of different approaches, and posted messages on the > forums.microsof t board. i have to believe that someone, somewhere has
> build
> a transaction-type system like this one. but most of the samples and
> advice
> that i have received have all pointed to a server listening for and
> accepting
> multiple clients, instead of one application connecting to a remote server > with a number of concurrent (client) connections.
>
> if anyone has any useful links or suggestions, it would be appreciated. > thanks in advance.

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

You are right about the server side of the communication, sorry for that
mistake. You can use it in case you need it.
Each connection use theirs own particular socket instance , even if they
are connecting to the same remote host/port

in any case multithreading the client is the only possible way of doing
this.

where i send something and wait for a response,
This depends of the protocol the server is using, do you know how it
handles the communication?
but i need to be able to do
that with 50 simultaneous calls.

Ok do this, get rid of the remoting part and just try your tcp code as if
you were receiving several remoting requests.

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:C3******** *************** ***********@mic rosoft.com...i tried separate threads, as well. the code you posted includes a
tcplistener, which is the server side, right? my proxy server (which is
actually a client at this point) will be the one initiating the
conversation
with the remote server, not listening for clients to connect, unless i am
missing something.

i was thinking about it (again) last night, and i think my biggest problem
is that i am trying to make something serial that isn't. with my COM
ports,
one port is open, handles the transaction, and is closed. with the
socket,
multiple connections use the same socket so it isn't as easy as listening
to
one channel for a response. the responses seem to be stepping one each
other
when responses are received. i think what i want is a synchronous socket
call
where i send something and wait for a response, but i need to be able to
do
that with 50 simultaneous calls.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

Are you sure all your variables are local to each thread?
Cause I assume you are using threads when dealing with more than one
connection no?

This is part of the code I use :

Thread listenerThread;

Queue connectionQueue = null;

protected void ListenerMethod( )
{
Thread workingthread;

Queue unsyncq = new Queue();
connectionQueue = Queue.Synchroni zed( unsyncq);

TcpClient socket;
TcpListener listener = new TcpListener( Config.Port);
listener.Start( );
while( true)
{
socket = listener.Accept TcpClient();
connectionQueue .Enqueue( socket);

workingthread = new Thread( new ThreadStart( TheConnectionHa ndler));
workingthread.S tart();
}
}

public void TheConnectionHa ndler()
{

TcpClient socket= (TcpClient)conn ectionQueue.Deq ueue();

}
Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
message
news:B2******** *************** ***********@mic rosoft.com...

> i've actually tried a number of different approaches, which i will try
> to
> summarize below...
>
> synchronous: this works fine for one transaction, but sending any more
> than
> one does not (send while waiting for a response from a previous
> transaction
> causes the read to fail (return nothing))
>
> [Send Synchronous, then]
> int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
> byte[] response = new byte[i];
> Array.Copy(buff er,0,response,0 ,i);
> //Console.WriteLi ne("Out of Transact : " +
> Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
> return response;
>
> asynchronous:
>
> i stripped out the last version of asynchronous reading. basically, it
> was
> sending synchronously while listening asynchronously. when something
> was
> received, if it contained the special terminating character, it would
> raise
> an event with the server response as the event argument. the code
> was a
> combination of asynchronous samples from the MSDN site and other
> references
> on the net that used BeginReceive.
>
> I know it can't be THIS hard. I'm adding TCP functionality to the
> application that was previously all serial based. the logic in the
> serial
> based one was check if the port is available, if it is send, lock the
> port
> until something is received, return the response, close the port. i'm
> not
> a
> big TCP/IP person, but i figure there should be some information out
> there
> that would put me on the right path.
>
> "Ignacio Machin ( .NET/ C# MVP )" wrote:
>
>> Hi,
>>
>>
>> post the code you are using to communicate with the remote TCP
>> server,
>> are
>> you using multithread? each thread generating a connection ?
>>
>> cheers,
>>
>> --
>> Ignacio Machin,
>> ignacio.machin AT dot.state.fl.us
>> Florida Department Of Transportation
>>
>>
>> "coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
>> message
>> news:75******** *************** ***********@mic rosoft.com...
>> >i am working on basically a proxy server that handles requests via
>> >remoting
>> > from clients and executes transactions against a third-party server
>> > via
>> > TCP.
>> >
>> > the remoting site works like a champ. my problem is executing the
>> > transactions against the remote server and returning the response to
>> > the
>> > remoting client. i can open the socket fine and, if i am executing
>> > one
>> > transaction at a time, everything works great. it's when my proxy
>> > server
>> > tries to execute multiple transactions, i'm missing something on the
>> > socket
>> > end. i have tried both synchronous and asynchronous, but it just
>> > seems
>> > that
>> > the socket stops listening after one response is received and
>> > ignores
>> > the
>> > other pending transactions.
>> >
>> > i've tried a number of different approaches, and posted messages on
>> > the
>> > forums.microsof t board. i have to believe that someone, somewhere
>> > has
>> > build
>> > a transaction-type system like this one. but most of the samples
>> > and
>> > advice
>> > that i have received have all pointed to a server listening for and
>> > accepting
>> > multiple clients, instead of one application connecting to a remote
>> > server
>> > with a number of concurrent (client) connections.
>> >
>> > if anyone has any useful links or suggestions, it would be
>> > appreciated.
>> > thanks in advance.
>>
>>
>>

[coloradowebdev]

this is frustrating!

i tried creating a (more simple) client that attempts to send multiple
requests to the remote server. each request is sent and a response is
awaited in its own thread, with the theory being that since each thread has
its own connection to the remote server, everything would work out.

the transactions are all making it to the server, but my client, again, is
losing some of the responses. this is my client thread method. it seems
straight forward: open a TcpClient, send something, wait for something with
the same client, etc. I was using the ManualReset for handling timeouts, but
i'm not even worried about that right now (all of my calls to the remote
server are returning something)...al so, the messages returned from the remote
server are terminated with 0x0d, so that is what i am using to know that a
response is finished. since the thread handles one send and receive, i let it
terminate once the receive loop ends.
private void ClientThread(ob ject data)
{
TcpClient client = null;
NetworkStream netStream = null;

try
{
//TransFlag.Reset ();

Console.WriteLi ne("In client thread");
TCPBaseSettings cs = TCPSettings();
client = new TcpClient(cs.Ho st, cs.Port);
netStream = client.GetStrea m();
netStream.Write ((byte[])data, 0, ((byte[])data).Length);

int totalBytesRcvd = 0;
int bytesRcvd = 0;
const int BufferSize = 256;
// Receive buffer.
byte[] buffer = new byte[BufferSize];
while (true)
{
bytesRcvd = netStream.Read( buffer,0,Buffer Size);
if (bytesRcvd > 0)
{
Console.WriteLi ne("Received Bytes: " +
bytesRcvd.ToStr ing());
if (ContainsCR(buf fer))
{
Console.WriteLi ne("Buffer contains CR");
Console.WriteLi ne("Thread: " +
Thread.CurrentT hread.Name);
RxBytes = new byte[bytesRcvd];
Array.Copy(buff er, 0, RxBytes, 0, bytesRcvd);
//TransFlag.Set() ;
hasresponse = true;
break;
}
else
{
//Console.WriteLi ne("Buffer does not contain CR");
}
}
}

}
catch (Exception ex)
{
Console.WriteLi ne("ClientThrea d Exception: " + ex.Message);
//throw ex;
}
finally
{
netStream.Close ();
client.Close();
}
Console.WriteLi ne("ClientThrea d Exiting: " +
Thread.CurrentT hread.Name);
}
"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

You are right about the server side of the communication, sorry for that
mistake. You can use it in case you need it.
Each connection use theirs own particular socket instance , even if they
are connecting to the same remote host/port

in any case multithreading the client is the only possible way of doing
this.

where i send something and wait for a response,

This depends of the protocol the server is using, do you know how it
handles the communication?

but i need to be able to do
that with 50 simultaneous calls.

Ok do this, get rid of the remoting part and just try your tcp code as if
you were receiving several remoting requests.

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:C3******** *************** ***********@mic rosoft.com...

i tried separate threads, as well. the code you posted includes a
tcplistener, which is the server side, right? my proxy server (which is
actually a client at this point) will be the one initiating the
conversation
with the remote server, not listening for clients to connect, unless i am
missing something.

i was thinking about it (again) last night, and i think my biggest problem
is that i am trying to make something serial that isn't. with my COM
ports,
one port is open, handles the transaction, and is closed. with the
socket,
multiple connections use the same socket so it isn't as easy as listening
to
one channel for a response. the responses seem to be stepping one each
other
when responses are received. i think what i want is a synchronous socket
call
where i send something and wait for a response, but i need to be able to
do
that with 50 simultaneous calls.

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

Are you sure all your variables are local to each thread?
Cause I assume you are using threads when dealing with more than one
connection no?

This is part of the code I use :

Thread listenerThread;

Queue connectionQueue = null;

protected void ListenerMethod( )
{
Thread workingthread;

Queue unsyncq = new Queue();
connectionQueue = Queue.Synchroni zed( unsyncq);

TcpClient socket;
TcpListener listener = new TcpListener( Config.Port);
listener.Start( );
while( true)
{
socket = listener.Accept TcpClient();
connectionQueue .Enqueue( socket);

workingthread = new Thread( new ThreadStart( TheConnectionHa ndler));
workingthread.S tart();
}
}

public void TheConnectionHa ndler()
{

TcpClient socket= (TcpClient)conn ectionQueue.Deq ueue();

}
Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
message
news:B2******** *************** ***********@mic rosoft.com...
> i've actually tried a number of different approaches, which i will try
> to
> summarize below...
>
> synchronous: this works fine for one transaction, but sending any more
> than
> one does not (send while waiting for a response from a previous
> transaction
> causes the read to fail (return nothing))
>
> [Send Synchronous, then]
> int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
> byte[] response = new byte[i];
> Array.Copy(buff er,0,response,0 ,i);
> //Console.WriteLi ne("Out of Transact : " +
> Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
> return response;
>
> asynchronous:
>
> i stripped out the last version of asynchronous reading. basically, it
> was
> sending synchronously while listening asynchronously. when something
> was
> received, if it contained the special terminating character, it would
> raise
> an event with the server response as the event argument. the code
> was a
> combination of asynchronous samples from the MSDN site and other
> references
> on the net that used BeginReceive.
>
> I know it can't be THIS hard. I'm adding TCP functionality to the
> application that was previously all serial based. the logic in the
> serial
> based one was check if the port is available, if it is send, lock the
> port
> until something is received, return the response, close the port. i'm
> not
> a
> big TCP/IP person, but i figure there should be some information out
> there
> that would put me on the right path.
>
> "Ignacio Machin ( .NET/ C# MVP )" wrote:
>
>> Hi,
>>
>>
>> post the code you are using to communicate with the remote TCP
>> server,
>> are
>> you using multithread? each thread generating a connection ?
>>
>> cheers,
>>
>> --
>> Ignacio Machin,
>> ignacio.machin AT dot.state.fl.us
>> Florida Department Of Transportation
>>
>>
>> "coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
>> message
>> news:75******** *************** ***********@mic rosoft.com...
>> >i am working on basically a proxy server that handles requests via
>> >remoting
>> > from clients and executes transactions against a third-party server
>> > via
>> > TCP.
>> >
>> > the remoting site works like a champ. my problem is executing the
>> > transactions against the remote server and returning the response to
>> > the
>> > remoting client. i can open the socket fine and, if i am executing
>> > one
>> > transaction at a time, everything works great. it's when my proxy
>> > server
>> > tries to execute multiple transactions, i'm missing something on the
>> > socket
>> > end. i have tried both synchronous and asynchronous, but it just
>> > seems
>> > that
>> > the socket stops listening after one response is received and
>> > ignores
>> > the
>> > other pending transactions.
>> >
>> > i've tried a number of different approaches, and posted messages on
>> > the
>> > forums.microsof t board. i have to believe that someone, somewhere
>> > has
>> > build
>> > a transaction-type system like this one. but most of the samples
>> > and
>> > advice
>> > that i have received have all pointed to a server listening for and
>> > accepting
>> > multiple clients, instead of one application connecting to a remote
>> > server
>> > with a number of concurrent (client) connections.
>> >
>> > if anyone has any useful links or suggestions, it would be
>> > appreciated.
>> > thanks in advance.
>>
>>
>>

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Are ou sure that the server does support multithreading? and it does it
correctly?

Maybe it's the server where the problems lies.
Also make sure you know the server's protocol
cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in message
news:C5******** *************** ***********@mic rosoft.com...

this is frustrating!

i tried creating a (more simple) client that attempts to send multiple
requests to the remote server. each request is sent and a response is
awaited in its own thread, with the theory being that since each thread
has
its own connection to the remote server, everything would work out.

the transactions are all making it to the server, but my client, again, is
losing some of the responses. this is my client thread method. it seems
straight forward: open a TcpClient, send something, wait for something
with
the same client, etc. I was using the ManualReset for handling timeouts,
but
i'm not even worried about that right now (all of my calls to the remote
server are returning something)...al so, the messages returned from the
remote
server are terminated with 0x0d, so that is what i am using to know that a
response is finished. since the thread handles one send and receive, i let
it
terminate once the receive loop ends.
private void ClientThread(ob ject data)
{
TcpClient client = null;
NetworkStream netStream = null;

try
{
//TransFlag.Reset ();

Console.WriteLi ne("In client thread");
TCPBaseSettings cs = TCPSettings();
client = new TcpClient(cs.Ho st, cs.Port);
netStream = client.GetStrea m();
netStream.Write ((byte[])data, 0, ((byte[])data).Length);

int totalBytesRcvd = 0;
int bytesRcvd = 0;
const int BufferSize = 256;
// Receive buffer.
byte[] buffer = new byte[BufferSize];
while (true)
{
bytesRcvd = netStream.Read( buffer,0,Buffer Size);
if (bytesRcvd > 0)
{
Console.WriteLi ne("Received Bytes: " +
bytesRcvd.ToStr ing());
if (ContainsCR(buf fer))
{
Console.WriteLi ne("Buffer contains CR");
Console.WriteLi ne("Thread: " +
Thread.CurrentT hread.Name);
RxBytes = new byte[bytesRcvd];
Array.Copy(buff er, 0, RxBytes, 0, bytesRcvd);
//TransFlag.Set() ;
hasresponse = true;
break;
}
else
{
//Console.WriteLi ne("Buffer does not contain
CR");
}
}
}

}
catch (Exception ex)
{
Console.WriteLi ne("ClientThrea d Exception: " + ex.Message);
//throw ex;
}
finally
{
netStream.Close ();
client.Close();
}
Console.WriteLi ne("ClientThrea d Exiting: " +
Thread.CurrentT hread.Name);
}
"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

You are right about the server side of the communication, sorry for that
mistake. You can use it in case you need it.
Each connection use theirs own particular socket instance , even if they
are connecting to the same remote host/port

in any case multithreading the client is the only possible way of doing
this.

> where i send something and wait for a response,

This depends of the protocol the server is using, do you know how it
handles the communication?

> but i need to be able to do
> that with 50 simultaneous calls.
>

Ok do this, get rid of the remoting part and just try your tcp code as if
you were receiving several remoting requests.

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
message
news:C3******** *************** ***********@mic rosoft.com...

>i tried separate threads, as well. the code you posted includes a
> tcplistener, which is the server side, right? my proxy server (which
> is
> actually a client at this point) will be the one initiating the
> conversation
> with the remote server, not listening for clients to connect, unless i
> am
> missing something.
>
> i was thinking about it (again) last night, and i think my biggest
> problem
> is that i am trying to make something serial that isn't. with my COM
> ports,
> one port is open, handles the transaction, and is closed. with the
> socket,
> multiple connections use the same socket so it isn't as easy as
> listening
> to
> one channel for a response. the responses seem to be stepping one each
> other
> when responses are received. i think what i want is a synchronous
> socket
> call
> where i send something and wait for a response, but i need to be able
> to
> do
> that with 50 simultaneous calls.
>
> "Ignacio Machin ( .NET/ C# MVP )" wrote:
>
>> Hi,
>>
>> Are you sure all your variables are local to each thread?
>> Cause I assume you are using threads when dealing with more than one
>> connection no?
>>
>> This is part of the code I use :
>>
>> Thread listenerThread;
>>
>> Queue connectionQueue = null;
>>
>> protected void ListenerMethod( )
>> {
>> Thread workingthread;
>>
>> Queue unsyncq = new Queue();
>> connectionQueue = Queue.Synchroni zed( unsyncq);
>>
>> TcpClient socket;
>> TcpListener listener = new TcpListener( Config.Port);
>> listener.Start( );
>> while( true)
>> {
>> socket = listener.Accept TcpClient();
>> connectionQueue .Enqueue( socket);
>>
>> workingthread = new Thread( new ThreadStart( TheConnectionHa ndler));
>> workingthread.S tart();
>> }
>> }
>>
>> public void TheConnectionHa ndler()
>> {
>>
>> TcpClient socket= (TcpClient)conn ectionQueue.Deq ueue();
>>
>> }
>>
>>
>> Cheers,
>>
>> --
>> Ignacio Machin,
>> ignacio.machin AT dot.state.fl.us
>> Florida Department Of Transportation
>>
>> "coloradowebdev " <co************ @discussions.mi crosoft.com> wrote in
>> message
>> news:B2******** *************** ***********@mic rosoft.com...
>> > i've actually tried a number of different approaches, which i will
>> > try
>> > to
>> > summarize below...
>> >
>> > synchronous: this works fine for one transaction, but sending any
>> > more
>> > than
>> > one does not (send while waiting for a response from a previous
>> > transaction
>> > causes the read to fail (return nothing))
>> >
>> > [Send Synchronous, then]
>> > int i = sock.Receive(bu ffer, 0, sock.Available, SocketFlags.Non e);
>> > byte[] response = new byte[i];
>> > Array.Copy(buff er,0,response,0 ,i);
>> > //Console.WriteLi ne("Out of Transact : " +
>> > Comcast.Common. Encoding.HexEnc oder.ToString(r esponse));
>> > return response;
>> >
>> > asynchronous:
>> >
>> > i stripped out the last version of asynchronous reading. basically,
>> > it
>> > was
>> > sending synchronously while listening asynchronously. when
>> > something
>> > was
>> > received, if it contained the special terminating character, it
>> > would
>> > raise
>> > an event with the server response as the event argument. the code
>> > was a
>> > combination of asynchronous samples from the MSDN site and other
>> > references
>> > on the net that used BeginReceive.
>> >
>> > I know it can't be THIS hard. I'm adding TCP functionality to the
>> > application that was previously all serial based. the logic in the
>> > serial
>> > based one was check if the port is available, if it is send, lock
>> > the
>> > port
>> > until something is received, return the response, close the port.
>> > i'm
>> > not
>> > a
>> > big TCP/IP person, but i figure there should be some information out
>> > there
>> > that would put me on the right path.
>> >
>> > "Ignacio Machin ( .NET/ C# MVP )" wrote:
>> >
>> >> Hi,
>> >>
>> >>
>> >> post the code you are using to communicate with the remote TCP
>> >> server,
>> >> are
>> >> you using multithread? each thread generating a connection ?
>> >>
>> >> cheers,
>> >>
>> >> --
>> >> Ignacio Machin,
>> >> ignacio.machin AT dot.state.fl.us
>> >> Florida Department Of Transportation
>> >>
>> >>
>> >> "coloradowebdev " <co************ @discussions.mi crosoft.com> wrote
>> >> in
>> >> message
>> >> news:75******** *************** ***********@mic rosoft.com...
>> >> >i am working on basically a proxy server that handles requests via
>> >> >remoting
>> >> > from clients and executes transactions against a third-party
>> >> > server
>> >> > via
>> >> > TCP.
>> >> >
>> >> > the remoting site works like a champ. my problem is executing
>> >> > the
>> >> > transactions against the remote server and returning the response
>> >> > to
>> >> > the
>> >> > remoting client. i can open the socket fine and, if i am
>> >> > executing
>> >> > one
>> >> > transaction at a time, everything works great. it's when my
>> >> > proxy
>> >> > server
>> >> > tries to execute multiple transactions, i'm missing something on
>> >> > the
>> >> > socket
>> >> > end. i have tried both synchronous and asynchronous, but it just
>> >> > seems
>> >> > that
>> >> > the socket stops listening after one response is received and
>> >> > ignores
>> >> > the
>> >> > other pending transactions.
>> >> >
>> >> > i've tried a number of different approaches, and posted messages
>> >> > on
>> >> > the
>> >> > forums.microsof t board. i have to believe that someone,
>> >> > somewhere
>> >> > has
>> >> > build
>> >> > a transaction-type system like this one. but most of the samples
>> >> > and
>> >> > advice
>> >> > that i have received have all pointed to a server listening for
>> >> > and
>> >> > accepting
>> >> > multiple clients, instead of one application connecting to a
>> >> > remote
>> >> > server
>> >> > with a number of concurrent (client) connections.
>> >> >
>> >> > if anyone has any useful links or suggestions, it would be
>> >> > appreciated.
>> >> > thanks in advance.
>> >>
>> >>
>> >>
>>
>>
>>