Did somebody already has experiences with the event dispatcher of maxdb?
I`m running into some problems:
I want to catch the event OUTOFSESSIONS, so i add this event to the event
dispatcher (first i changed the defaultvalue from _MAXEVENTTASKS (2) up to 10.)
dbmevtdisp add <foo.cfg> Name == OUTOFSESSIONS Priority == MEDIUM Command ==
"bash -c \"do something \""
Result is:
OK
okay, let see what the eventconfigfile says:
dbmevtdisp list <foo.cfg>
ID 0
condition: ((Name == "OUTOFSESSIONS") && (Priority == MEDIUM))
Command: bash -c "do something"
okay, force the database with too many user-requests and look what happend:
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?!
dbmcli -d <FOODB> -u <USER,PASS> event_list
OK
result:
...
UPDSTATWANTED LOW At least one table needs new optimizer
statistics
OUTOFSESSIONS MEDIUM Maximum number of parallel sessions is
running
ERROR HIGH A system error occured, see knldiag
...
sorry, bu it´s not possible to catch OUTOFSESSIONS. but i tried (events ADMIN,
ONLINE) with no problems! and finally on a restart of the database the event
dispatcher terminates with the following messages (Database state is ONLINE ):
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 ?
tested on SuSe Linux with kernel 2.6.8-24.16 and MaxDB 7.6.00.16
regards ingo
--
Ingo Trapphagen
IOn Aktiengesellschaft
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
