Thanks for tips, I found the troubles in application, they occurs only when exceptions occured and don't released resources. :-[
Do you have any idea about follow Message?
MsgID: 53214 Label: B*TREE Message-Text: SET READ ONLY: 1A00 FFFFFFFFFFFF0605
There is place that I can find descriptions about Messages in knldiag?
Regards
Clovis
Schroeder, Alexander wrote:
Hello Clovis,
each database session will need its own 'User Task'. So check your application whether it forgets to close connections, and keep them hanging around. Each 'User Task' will also need shared resources, some of them only if the load increases, some of them from beginning.
See a previous mail at http://listserv.sap.com/pipermail/sapdb.general/2002-October/008942.html
on what you may do (as it can be assumed that 150 MAXUSERTASKS will
blow the setting, and make the kernel crash).
BTW, usually not only the 'suspect' lines but the overall context in the knldiag is of interest - it may tell what happened around the time the error appeared, if there is one, also the possible stack backtrace in knldiag in the event of a crash (or the note of the absense of a stack backtrace ...).
Anyway, if your application is loosing connections by forgetting them, no value of MAXUSERTASKS is sufficient to cover it over the time ... so try to use the appropriate client trace (JDBC/ODBC/Precompiler) to
check where and how often the application does open and close connections.
Regards
Alexander Schr�der
SAP DB, SAP Labs Berlin
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
