Hello everyone,
I hope I am adressing the issue at the right place.
I am using grizzly comet for a rather large project at the
University of Bielefeld (Germany) and am currently stuck at
the same line of code for the last 50 hours.
Quickly said, I am calling this:
cometEvent.getCometContext().resumeCometHandler(this)
Which executes fine in @onEvent
But I am using an external event queue for managing events
that occur, when the comet is busy delivering an event.
Now, once a new handler returns, I query that event queue
in @onInitialize.
I retrieve the event and then, I call:
cometEvent.getCometContext().resumeCometHandler(this)
inside the onInitialize method.
This executes without error.
However, this really really baffles me, @onInterrupt is called
afterwards (after the timeout) and my event is never actually
transmitted.
I spend a horrible number of hours on debugging this issue and
I cannot find a single bit wrong with my code. I cannot however,
look too deeply into the grizzly code, so I am pretty much grasping
at straws here to see if anyone had this happen, or can tell me
how I can either fix or work around this issue...
Hopefully,
Janik Jaskolski
-------------
Citec - Cognitive Interaction Center of Excellence
Technical Faculty
University of Bielefeld