Domino 9 und frühere Versionen > Administration & Userprobleme

maximum currently objects

<< < (4/5) > >>

neuling10:
Hallo,

wenn der Fehler auftritt betrifft es alle Datenbanken. Am Anfang kann man Glück haben und die Datenbank mit der man gerade arbeitet tut es noch ne weile, aber irgendwann kommt dieser Fehler bei allen Datenbanken. Selbst bei den original Notes-Mailschablonen - und die sollten ja eigentlich funktionieren. Es liegt also nicht an irgend welchen selbstgestrickten Datenbanken.

Gruss
   der andere Praktikant

HRaq:
Hi,

Auszug aus der Knowledge Base (allerdings für 4.6)

Number:  162934

Problem
A Domino 4.6x or 4.5x customer receives an error similar to the following in the Notes server log or on the server console:

"Maximum Number of Concurrently Open Objects Has Been Exceeded."

Solution
This error occurs when a combination of the following factors has been exceeded and can happen on very busy servers (There is no pattern as to when the error happens, but usually it is when the servers are used during the peak hours of the day):

Number of Users
Number of Open databases per user
Number of database handles open per user per database

NOTE: Please read the Supporting Information section below for additional explanation.


There are currently 4 workarounds available for the error message:

1. Reduce the number of concurrently open user sessions on the Domino server with the use of the following NOTES.INI parameters:

Server_MaxSessions= numerical value
Server_Session_Timeout = numerical value in minutes


Note: The numbers used for these values are not and should not be taken as a standard value. The appropriate numbers for the NOTES.INI parameters (Server_MaxSessions and Server_Session_Timeout) may change depending on:
The total number of Concurrent Users x (times) The number of databases that each user has open (a session is opened for each user to each cascaded NAB)

Server_MaxSessions=XXX - If the error occurs, lower this number.
(Note: With multiple protocols, the parameter Portname_MaxSessions may be used to limit a specific Notes Port that may be subject to heavy user load)

Server_Session_Timeout=15 is an acceptable number for a mail-only server. The exact number may vary depending on testing done on each Notes Server for end user satisfaction. A combination database and mailfile server will require a higher value.

2. Reduce the number of databases open per user. This typically will come into play when there is a large number of cascaded Name & Address Books (NABs) on a Domino server. Two possible ways to reduce the number of NABs:

Consolidate two (2) or more smaller address books into one.
Remove one (1) or more address books from the cascaded list.
Note: Removing a NAB from a cascaded list eliminates type-ahead and name lookup functionality, which would require users to append the @domain name after the recipients name (for example, Firstname Lastname@domainname).

3. If the server is a mail server, offload mail users onto another, less busy server; if it is an application server, offload databases.

4. Recycle the Domino server once a week, depending upon the server load. The server recycle frequency length may vary from server to server.


NOTE: A memory dump will not help in diagnosing this issue. A memory dump does not show the number of file handles being utilized, rather it shows the total number of MEMORY handles. This issue is specific to file handles.

Supporting Information
The server treats user session initiation handles differently from those that are used for other databases access, caching the handles to speed up the process of re-establishing the session.

Basically, the problem the customer is running into is the limitation of the Notes architecture; it is running out of Notes handles. You may not see this problem if you recycle the Domino server frequently (for example, once a week). This refreshes the handles, rather than continuing to build on top of existing handles and eventually running out of handles.

Lotus Notes Development has addressed this limit in Domino Release 5.

Vielleicht ist Euch damit geholfen....

Gruß Henning

neuling10:
Hallo,

also Punkt 1 haben wir schon mal abgearbeitet ohne Erfolg.
Punkt 2 haben wir nicht.
Punkt 3 - nö, es ist der Application-Server
Punkt 4 - machen wir jeden Morgen, wollen wir aber eigentlich vermeiden.

gruss
  immernoch der andere Praktikant

HRaq:
....auch beim Application-Server ist was zu tun (2. Halbsatz zu Punkt 3).....

neuling10:
Hallo,

wir haben hier schon einen 2. Applicationserver mit der gleichen Hardwareausstattung und als Mailserver fungiert ein dritter. Die Transaktionen (nach dem Notes-Log) halten sich auch auf einem relativ niedrigen Niveau. Er hat selten mehr als 3000. Der Server schafft in Hochzeiten auch über 6000 Transaktionen./Minute. An der Last selbst dürfte es nicht liegen. Auf einem Server befinden sich auch nie mehr als 40 Nutzer von denen die wenigsten mehr als 2 Datenbanken auf haben.

Gruss
   der andere Praktikant

Navigation

[0] Themen-Index

[#] Nächste Seite

[*] Vorherige Sete