> > > to the event dispatcher (first i changed the defaultvalue > > from _MAXEVENTTASKS (2) up to 10.) > Why did you do this? Do you want to run more than one Event Dispatcher > in parallel?
i thought we need a higher value for every event to catch. next time, i will read the manual more closely. :)) > > > event with name OUTOFSESSIONS not dispatched (count 1) > > event with name OUTOFSESSIONS not dispatched (count 2) > > > > maybe we did something wrong, which events are activated?! > You found a bug in the event_list command. Priority of OUTOFSESSIONS > event is HIGH, not MEDIUM. BTW, there is no need to specify the event > priority in your case. If you want to dispatch all > OUTOFSESSIONS events, > it's enough to just specify the event name. fine, it works without specifying the PRIORITY ... > > > event with name DISPERR:DBCRASH not dispatched (count 1) > > event with name DISPINFO:DISPSTOP not dispatched (count 2) > > Event Dispatcher termination > > > > what is the problem for OUTOFSESSIONS and what is the reason > > for DISPERR:DBCRASH ? > You found a bug in the Event Dispatcher. The kernel does not > crash on a > db_restart. in which conditions will the event dispatcher terminated? i got still the problem, that the event dispatcher terminates in certain conditions (bring server to ONLINE or OFFLINE). -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
