On Wed, Aug 02, 2006 at 11:14:46PM +0200, Roman Rokytskyy wrote:

> Hi,
>
> > I'm developing an application that make (intensive) use of the wonderful
> > Event API. I'm at the finishing stage and I encountered a little problem
> > that seems IMHO a little bug:
>
> Thanks for the report. That is definitely a bug, since it should not thow
> runtime exceptions anyway.
>
> Can you please create a new ticket in our new tracker
> (http://tracker.firebirdsql.org)? Later we can use the ticket number in CVS
> commit message, which will bind the ticket to the modified sources, thus
> providing better overview.

Could you also provide a runnable test case that can replicate this
issue, if possible?

It is indeed a bug in the code, but I'm more curious about the situation
that is causing it. It appears that an event notification is sent from
the server, without any information about the number of occurences of
the event. In order to really correct this bug, the issue has to be
replicated to ensure that the event-handling thread is left in a
consistent state if this situation occurs.

Regards,
Gabriel