TCP/IP Server 2.0 still buggy

[Ron]

Yeah, so ? Did i claim to have fixed that yet ? I have not heard from the author of the TCP/IP client 2.0 ( Jay ) as soon as he gets back to me I can fix this problem. Patience people :smile:

[Ron]

I think disabling quiet mode helps ( at least it did on my computer )

[Ron]

For a discussion on this bug see

http://www.girder.nl/phpBB/viewtopic.php?topic=1149&forum=2&18

Glad you found the solution too.

[Ron]

Hmm thats strange this doesn't work for me. Anything you type before that ( linefeeds maybe ?)

[Ron]

Still no luck here, you are still in quiet mode right ?

[Ron]

Darn,.. guess we have to wait for the sourcecode :sad:

[Caffiend]

So I just started using the TCP/IP server again, and the 2.0 version still has the same problem it did before. Whenever I try to use it via a script run from an ASP page (using Ostrosoft's oswinsck.dll) Girder uses 100% of my CPU and doesn't execute the command until I close Girder. The 1.3 version of TCP/IP Server worked great, but I guess I don't really have the option to run it anymore.

-will

[Caffiend]

Ah ha! In "quiet mode" the blank line doesn't disconnect. I was able to recreate the same problem with Quiet Mode on by telnet-ing in and then just closing the session. If you do just a blank line the way the prompted session disconnects, you get a "103: command unknown" error. Guess I'll download Girder 3.0.23 and use the old TCP/IP server from it.

-will

[Caffiend]

Disabling Quiet Mode solves the problem, but it disables my script also. I had mentioned this a long time ago to Jay, but just used v1.3.

However, I have the solution!
I randomly hacked away on the keyboard and "close_session" disconnects from the TCP/IP server. As far as I can tell this is closing it out properly and I don't get the 100% CPU utilization anymore. I'm pretty sure it's not just leaving resources in use.

-will

[Caffiend]

I'm telnet-ing to the server, then I type the password, then I can type "close_session" and I get disconnected. It doesn't work if I haven't typed the password however.
Bah, I'm an idiot. Apparently just "close" works.

-will

[Caffiend]

Yup. Although I just checked my settings and I am in "v1.x Compat mode". I unchecked that and now the blank line disconnects properly. I'm no longer using the "tcp.disconnect" function of oswinsck.dll so hopefully it's closing out when the TCP/IP server disconnects.

-will

[Caffiend]

Ooo! I just became "experienced"!

-will

[Caffiend]

Arrrgghhh!! So that ultimately doesn't work either. It works great for maybe 20 times or so, then quits until I close/restart Girder.
Going back to using Quiet Mode and v1.x Compat Mode seems to work. I can just send "close" then use TCP.Disconnect properly. Without using TCP.Disconnect I could watch Girder's memory usage go up about 12k everytime. After it got to ~6100k it quit responding to TCP commands.

-will

[Caffiend]

In case it matters or interests anyone, here's the VBScript I'm using in my ASP page:


<%
if Request.form("command") <> "" then
dim TCP 'as object
Set TCP = CreateObject("oswinsck.TCP")
if TCP.Connect ("204.238.247.250", 1024) = 0 then
TCP.SendData "girder" & vbCrLf
TCP.SendData Request.form("command") & vbCrLf
TCP.SendData "close" & vbCrLf
TCP.Disconnect
end if
set TCP = nothing
end if
%>

This is using Ostrosoft's oswinsck.dll of course. I have a form that sets the value of command and submits it to this script. This version actually works with the current TCP/IP Server (as far as I can tell so far anyway).

-will

<font size=-1>[ This Message was edited by: Caffiend on 2002-03-04 22:20 ]</font>