Client/server Bad value on output port 'tcp_inet'

[Chandrashekhar Mullaparthi]

Lars,

accsocket:send(#Port<0.119>,{[255,0,0,2]})
accsock:error Reasson einval

You are trying to send a tuple down the socket. It will accept only binaries
and lists.

hth
Chandru

-----Original Message-----
From: Lars H. Larsen, ICCC [mailto:LHL@REDACTED]
Sent: 04 February 2003 10:41
To: erlang-questions@REDACTED
Subject: Client/server Bad value on output port 'tcp_inet'


Hello fabulous Erlang guys 

I'm using OTP R9-0 on a Win32 platform (winsock) W2K and XP

When I run a balanced client-server program ( attached below) the connection
phase is resolved with no problems.
But the data exchange never happens due to some strange error I have been
chasing now for a week or so, 
-until now with no luck.... :-(

in Desperation I loaded the program with debug outputs :  All the debug
output  give approx. this result on both sides when connecting from  'knud2'
to 'lhl-pc'

accsocket init <0.72.0>,knud2 6000 
accsocket: gen_tcp:connect(knud2,6000),{packet, 0},{active, true }
Connect error {reason,econnrefused} 
gen_tcp:listen (6000,[binary, {packet, 0}, {active,true}])
ok,ListenSocket  ListenSocket=#Port<0.118> info ={error,enotconn}
runing initServer got Connect Socket #Port<0.119> Info {ok,{{192,168,2,253},
                                                            6000}}
GETACCTABLE Socket#socket.socket #Port<0.119> Data {[255,0,0,2]}
accsocket:send(#Port<0.119>,{[255,0,0,2]})
accsock:error Reasson einval

=ERROR REPORT==== 4-Feb-2003::11:23:55 ===
Bad value on output port 'tcp_inet'

- the ERROR thing  text is repeated for every data send attempt

<snipped>



 NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.