Lotus Notes / Domino Sonstiges > Companion Products

Sametime Community Server 8.5 - Stabilitätsprobleme

<< < (6/6)

hallo.dirk:
bei mir steht das hier:

[STLinks]
STLINKS_MAX_OPEN_CONNECTION_TIME=600000
STLINKS_MAX_USERS=2500
STLINKS_VM_ARGS=-Xmx128m -Xgcpolicy:optavgpause

eknori:

--- Zitat ---Thanks for providing the debug logs we requested last week. Our initial findings are as follows;

1) stlinks.txt exceptions;

STLinks SA Logged out, Reason: 0x80000019

and from Sametime_20100725.log;
I STLinks    25/Jul/10, 02:48:37  Logged out, Reason 0x80000019

1.1) Please try the workaround from;

Title:        STLinks service fails to start with error "Logged out, Reason 0x80000207"
Doc #:        1096848
URL:        http://www.ibm.com/support/docview.wss?uid=swg21096848

We found from your sametime.ini, that there was no existing STLINKS_HOST entry.

--- Ende Zitat ---


[Connectivity]
STLINKS_HOST=dewvst01.domain.de

eknori:
Und zum LDAP:


--- Zitat ---2) For question; "Is it possible that the LDAP task was not possible to handle the requests because it was overloaded?"

This could have been possible, we're aware VP_LDAP_TRACE=1 was enabled on the ST Server, this should have resulted in generation of  STUser debug
in the trace folder of the Sametime Server, that should indicate any exceptions/errors that could confirm if LDAP was overloaded.

Please provide any STUser files for us to check.

Note: To improve load and response times, the following parameters can be added to the Sametime.ini under the [Directory] section.  The values in the example below are the default values as assigned by the server

[Directory]                     
ST_DB_LDAP_CONNECTIONS_NUMBER=1
ST_DB_LDAP_KEEPALIVE_INTERVAL=1
ST_DB_LDAP_PENDING_LOW=5
ST_DB_LDAP_PENDING_MAX=10
ST_DB_LDAP_RESPRAY_INTERVAL=0
ST_DB_LDAP_MAX_RESULTS=1000
ST_DB_LDAP_MIN_WILDCARD=0

as outlined in

Title:        Optimizing LDAP connections and queries on a Sametime server
Doc #:        1200143
URL:        http://www.ibm.com/support/docview.wss?uid=swg21200143

You could start with increasing ST_DB_LDAP_CONNECTIONS_NUMBER to a maximum of 5, to see if that improves LDAP response times ?

--- Ende Zitat ---

Navigation

[0] Themen-Index

[*] Vorherige Sete