Proc: lost reply == generally means the Proc/Net noticed the other sides
VC is READY and quiet so we must have lost the reply.

The messages mean that communication isn't as reliable and that a pid
block on Net didn't seem to get a reply (nor appears to be getting one
anytime soon).  So the OS will kick the blocked task to allow it to make
some progress rather than wait for an event that won't occur.

If they happen infrequently, it is likely "ok" (dropped packets etc) but
a large amount tends to indicate a sick network.


-----Original Message-----
From: bogdan celer [mailto:community-noreply@qnx.com] 
Sent: Wednesday, April 15, 2009 11:40 AM
To: qnx4-community
Subject: messages: Proc: lost reply across net, freeing reply_blk

Hi,

From time to time in our system the following messages apear:

Proc: lost reply across net, freeing reply_blk local pid 002A
Proc: lost reply across net, freeing reply_blk local pid 003C

and sometimes:

Prfc: lost reply across net, freeing reply_blk local pid 002A

The pid=0x2A belongs to "nameloc" while 0x3C comes from our
application called "net_test".

Are these messages danger?
Can I ignore them?


_______________________________________________
QNX4 Community Support
http://community.qnx.com/sf/go/post27082