Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Management2017.11

Integrate > Service Manager integration methods and tools > Web Services > Troubleshooting > Troubleshooting SOAP API > Max sessions exceeded in Web Services

Max sessions exceeded in Web Services

If a Web Services request contains "connection: keep-alive" or it uses HTTP/1.1 without a connection header, the Service Management server will keep the session alive for a predefined interval that is defined by setting the "webservices_sessiontimeout" parameter in the sm.ini file. If a Web Services client does not reuse the session for subsequent requests by providing valid headers, the Service Management server creates a new session for each subsequent request and quickly run out of available sessions.

To avoid running out of available sessions, there are two options to consider:

Option A: Set the HTTP header "connection:closed" so that the Service Managementserver will not keep a Web Services session open after the current request is finished.

Option B: Utilize the Web Services session persistence by doing one of the following to reuse the existing Web Services session on theService Managementserver.

Use connection: keep-alive. If the connection header is missing, it defaults to "keep-alive" for HTTP/1.1.
The Web Services client needs to supply a session cookie with the same user log-in information that created the session.

Note Even with Web Services session persistence, each SOAP API request is stateless, so that requests are handled independently between one another.

Send Help Center feedback