Subject: RE: [jade-develop] Warning: No mapping found for expired timer
From: Caire Giovanni (Giovanni.Caire@TILAB.COM)
Date: Wed Jan 29 2003 - 10:05:26 MET
Tracing wich agent generates the warning is very simple: In the doTimeout() method of the jade.core.Agent class modify the System.out.println("WARNING:....) instruction by adding the agent name. Of course you have to re-compile JADE.
Let us know if you get any further indication.
From: Manuel Padilha [mailto:firstname.lastname@example.org]
Sent: marted́ 28 gennaio 2003 19.30
To: Caire Giovanni; email@example.com
Subject: Re: [jade-develop] Warning: No mapping found for expired timer
> What JADE version are you using?
> Are blocking for a certain amount of time some child of a Composite
> behaviours (Parallel, Sequential or FSM)?
> Are you using the
> WakerBehaviour or the TickerBehaviour?
No. My behaviours inherit from SimpleBehaviour.
This doesn't show up all the time, just when the system is under heavy load
(above 100% CPU usage), and that makes me think of something like the
typical "lost wakeup" problem, which would mean a race condition somewhere
in JADE's behaviour blocking mechanism...
I'm not saying it's not my fault, it can very well be... the code is a bit
messy, but i am trying to stick with the API at all times and always test
method's return values, so i just can't put my finger on it...
Is there any way i can trace the origin of this? Which agent is causing it?
At this time all my agents reside on the same Container, but this is about
to change in a near future, maybe then i'll be able to say what is causing
Thank you for your support,
--------------------------------- - Manuel Padilha - email: firstname.lastname@example.org - web: http://padilha.ath.cx/ ---------------------------------
This archive was generated by hypermail 2a22 : Wed Jan 29 2003 - 10:05:46 MET