=ERROR REPORT= Got invalid data on distribution channel, offending packet is:

suresh saragadam <>
Mon Oct 25 08:23:51 CEST 2004


 
> Got invalid data on distribution channel, offending packet is:
 
Hi Tony,
 
Certenly the approach you made helped me to think of what error it is,
 
when a 'mutex' is created before sending data from c node (here i am using vc++) problem is solved perfectly,
i have not gone through the problem what it is exactly, 
luckly implementing mutex solved the problem 
 
regards
 
suresh saragadam 
 
 

Tony Rogvall <> wrote:

torsdagen den 21 oktober 2004 kl 13.48 skrev suresh saragadam:

> Hi ,
>  
> I have established a connection between erlang node and c node using 
> erl_interface.
> If is running fine,
>  
> but some times at erlang node this error is reflected and c node is 
> killed,
> i found that erlang processes are running fine,
>  
> =ERROR REPORT==== 21-Oct-2004::16:53:23 ===
> Got invalid data on distribution channel, offending packet is: 
> <<112,131,104,4,9
> 7,6,103,100,0,10,99,49,64,99,111,109,109,115,118,114,0,0,7,4,0,0,0,0,1, 
> 100,0,0,1
> 00,0,13,101,110,111,100,101,114,101,99,101,105,118,101,114,0,0,0,71,112 
> ,131,104,
> 4,97,6,103,100,0,10,99,49,64,99,111,109,109,115,118,114,0,0,7>>
>  
> what is this error, and can any one tell what may be the problem
>  
Probably means that you sent some badly formated data.

doing binary_to_term on the data (skipping 112, 131 is the magic for 
external format) gives
you
{6,<5806.1796.0>,'',enodereceiver}

6 is the the distribution op called DOP_REG_SEND.

The above says send ??? to registered process enodereceiver from pid 
<5806.1796.0>
with the nowadays not used cookie ''. In other words the 
message is missing!
There is also an extra byte 112 form somewhere else ...

Hope it helps you to track the problem

Regards

/Tony


		
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20041024/7847f91b/attachment.html>


More information about the erlang-questions mailing list