Technote (FAQ)
Question
How does IBM solidDB event queuing mechanism work when there are multiple connections waiting for the same set of events ?
Answer
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 } |
WAIT
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:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.