I've noticed that if stop is called for an CBR application before it is started the TimerHandler returns the error 'Attempting to cancel timer at %p which is not scheduled', but for an FTP application the same action sequence is not considered an error. I'm using ns-2.1b8a.
Should this be considered a bug?
And if so, is the bug in the CBR application that calls timer.cancel()
at stop or is it in the TimerHandler which doesn't ignore a stop for a
not started application?
I've encountered the problem when running a script for different periods of time, and in the script starting a number of applications more or less randomly and stops all at the same time, i.e. when running the script for a short period some applications haven't been started when the simulation ends and stop is called.
The problem was posted earlier here without a reply:
http://www.isi.edu/nsnam/archive/ns-users/webarch/1999/msg01298.html
With regards
/Håkan
-- Håkan Byström, Operax +46 920 755 07, office +46 70 374 03 24, cellular