Re: [Beepcore-c-users] Another Beepcore-c Problem

[David C N. <dc...@ad...>]

On Thu, 25 Mar 2004, Darren New wrote:
> David C Niemi wrote:
> > Is there any implicit assumption that MSGs will be acked with an ANS or 
> > RPY?
> 
> Yes. You can't close the channel before all messages have been replied 
> to. In theory, you shouldn't be processing the second incoming MSG until 
> the first incoming MSG has had a reply of some sort queued for it.

Ah, that does sound like what's happening.  Thanks.


> I don't recall exactly, but grepping the sources for it would probably 
> turn up exactly what's happening. It might be that you're reusing MSG 
> numbers, if you're not getting any answers, in which case you'll get an 
> error when you queue the second MSG with the same number before the 
> first MSG has been answered and retired. How are you generating your 
> message numbers?

They're supposed to be sequential, but it's possible I have some sort of
error there that can occasionally permit duplication.  Or perhaps messages
arriving from two different places to the same profile instance are using
the same message numbers at times.  Is it only necessary to keep message 
numbers unique within a session, or when I have a listener with multiple 
sessions is it necessary for them to be globally unique across multiple 
sessions?

-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------