Re: No data received on client socket

I could finally get back the query result by modifying the original script like this:

my $oSocket = IO::Socket::INET->new(PeerAddr => $HostName,            
+                                               
                                    PeerPort => $Port,                
+                                       
                                    Timeout => $SocketTimeout,
                                    Type => SOCK_STREAM);

my $sSend = "<?xml version=\"1.0\"?> <request>" .
"<connectionstring>" . $ConnectionString .
"</connectionstring>" .
"<sql><![CDATA[" . $sSQL . "]]></sql></request>";                     
+                         

local *FH = $oSocket;
print  FH $sSend;
while (<FH>) { print $_ };
[download]

I'd really be grateful if someone can explain me what is not working in the other ways (my original one and the suggested modifications), and how the other ones should be modified in order to work.
Thanks a lot.

Update This way it works fine:

...
local *FH = $oSocket;
print  FH $sSend;

while (1) {
    sysread($oSocket, $data_read, 4096,length($data_read));
    $sRet .= $data_read;
    last if ($data_read =~ /<\/xml>/i);

};
close (FH);
print $sRet;
[download]

Comment on Re: No data received on client socket Select or Download Code

Replies are listed 'Best First'.
Re^2: No data received on client socket by ikegami (Patriarch) on Sep 21, 2006 at 15:52 UTC
Which change fixed it? Did using `while (<FH>)` or fixing the options passed to the constructor fix it? `SOCK_STREAM` is 1, but 'SOCK_STREAM' probably got treated as 0. If that's the problem, you should go back to using `sysread`/`syswrite`. By the way, what's with `local *FH = $oSocket;`? Everywhere you use `FH`, you can put `$oSocket`. (e.g. `print $oSocket ...`, `while (<$oSocket>)`, `sysread($oSocket, ...)`, etc)	[reply] [d/l] [select]
Re^3: No data received on client socket by rbi (Monk) on Sep 21, 2006 at 16:07 UTC
It worked when I put `while(<FH>)` and kept working when I forced the while condition to be true. Thanks for the correction on directly using the `$oSocket`. The same code accessing the same SQL server has a different behavior on different Linux boxes.. I hope this fix will work on the old ones :)	[reply] [d/l] [select]