Re: Multiple TCPConnects

This WebDNA talk-list message is from

2002

It keeps the original formatting. numero = 42349
interpreted = N
texte = I guess we have a different situation. Here's what was said after my co-worker read your response:>That's not it.>We've created our own method of communications. crlf ends the post >from WebDna. Then RB sends every thing and closes it itself.Guess we've reached a dead end?>Turns out I was not closing the connection properly in the telnet session ..>I needed to add a QUIT followed by CRLF combination at the end of the>TCPSend .. This was needed for the Communigate CLI to end the session ..>Otherwise it just hung until the connection timed out ..>>> Was it the fault of WebDNA or Communigate Pro that the connection>> wasn't closed properly? Were you able to fix it, and if so, how?>>>>> I had the same problem with Communigate Pro on the same server .. Turns out>>> the connections was not closed properly ..>>>>>> Get them to check again ..>>>>>>> Posting on behalf of some exasperated co-workers... first of all,>>>> the vitals:>>>> WebDNA 4.5 (Commerce Edition), Mac OS X (10.1.5), 1.2 GB G4, >>>>Apache 1.3.26.>>>>>>>> They're doing some consecutive [TCPConnect]s to a RealBasic>>>> application running on the same server, through port 2000; there's>>>> only a single [TCPSend] within each. Trouble is, it appears to>>>> hang after the first TCPConnect. They're adamant that the socket>>>> opened by the first TCPConnect is being closed before the next one is>>>> opened.>>>>>>>> Anyone encounter this before, or know how to fix it? Any help would>>>> be appreciated!>>>>>>>>> ------------------------------------------------------------->>> This message is sent to you because you are subscribed to>>> the mailing list .>>> To unsubscribe, E-mail to: >>> To switch to the DIGEST mode, E-mail to>>> >>> Web Archive of this list is at: http://search.smithmicro.com/>>>>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >>Web Archive of this list is at: http://search.smithmicro.com/-- Daryl MitchellE-Business Specialist, PW GroupSaskatoon, SK CANADATel: (306) 665-3557Toll-free: (800) 291-9935Fax: (306) 653-1255E-Mail: d.mitchell@pwgroup.ca-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Multiple TCPConnects (Daryl Mitchell 2002)
Re: Multiple TCPConnects (Jesse Williams-Proudman 2002)
Re: Multiple TCPConnects (Daryl Mitchell 2002)
Re: Multiple TCPConnects (Alain Russell 2002)
Re: Multiple TCPConnects (Daryl Mitchell 2002)
Re: Multiple TCPConnects (Alain Russell 2002)
Multiple TCPConnects (Daryl Mitchell 2002)

I guess we have a different situation. Here's what was said after my co-worker read your response:>That's not it.>We've created our own method of communications. crlf ends the post >from WebDna. Then RB sends every thing and closes it itself.Guess we've reached a dead end?>Turns out I was not closing the connection properly in the telnet session ..>I needed to add a QUIT followed by CRLF combination at the end of the>TCPSend .. This was needed for the Communigate CLI to end the session ..>Otherwise it just hung until the connection timed out ..>>> Was it the fault of WebDNA or Communigate Pro that the connection>> wasn't closed properly? Were you able to fix it, and if so, how?>>>>> I had the same problem with Communigate Pro on the same server .. Turns out>>> the connections was not closed properly ..>>>>>> Get them to check again ..>>>>>>> Posting on behalf of some exasperated co-workers... first of all,>>>> the vitals:>>>> WebDNA 4.5 (Commerce Edition), Mac OS X (10.1.5), 1.2 GB G4, >>>>Apache 1.3.26.>>>>>>>> They're doing some consecutive [tcpconnect]s to a RealBasic>>>> application running on the same server, through port 2000; there's>>>> only a single [tcpsend] within each. Trouble is, it appears to>>>> hang after the first TCPConnect. They're adamant that the socket>>>> opened by the first TCPConnect is being closed before the next one is>>>> opened.>>>>>>>> Anyone encounter this before, or know how to fix it? Any help would>>>> be appreciated!>>>>>>>>> ------------------------------------------------------------->>> This message is sent to you because you are subscribed to>>> the mailing list .>>> To unsubscribe, E-mail to: >>> To switch to the DIGEST mode, E-mail to>>> >>> Web Archive of this list is at: http://search.smithmicro.com/>>>>>------------------------------------------------------------->This message is sent to you because you are subscribed to> the mailing list .>To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >>Web Archive of this list is at: http://search.smithmicro.com/-- Daryl MitchellE-Business Specialist, PW GroupSaskatoon, SK CANADATel: (306) 665-3557Toll-free: (800) 291-9935Fax: (306) 653-1255E-Mail: d.mitchell@pwgroup.ca-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Daryl Mitchell

DOWNLOAD WEBDNA NOW!

Re: Multiple TCPConnects

2002

Top Articles:

Related Readings: