How does solidDB Event queuing mechanism actually work?

Technote (FAQ)


How does IBM solidDB event queuing mechanism work when there are multiple connections waiting for the same set of events ?


Every connection waiting on events has its own separate event queue in main memory. When the connection starts to wait for an event(s), it is implicitly registered for those events after which all events it has registered for are placed in the event queue. Registering, Un-registering and waiting for events can also be done through the command

ADMIN EVENT 'command'
command_name ::=
REGISTER { event_name [ , event_name ... ] | ALL } |
UNREGISTER { event_name [ , event_name ... ] | ALL } |
event_name ::= the name of a system event
Note: Connections need to explicitly register or wait on events to receive them and get placed in the event queue for that connection if the connection is busy processing some other events, and there is no size limit for this in-memory event queue.

Rate this page:

(0 users)Average rating

Add comments

Document information

More support for:

IBM solidDB

Software version:

4.5, 6.0, 6.1, 6.3

Operating system(s):

AIX, HP Itanium, HP-UX, Linux, Solaris, Windows

Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation