Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
- Managing multiple servlet container processes
Monitoring memory in Service Manager processes
The Service Manager process embeds a Java Virtual Machine (JVM) so that the heap memory provided by the operating system for any process is partitioned into a Java Heap and a Native Heap. The Service Manager process self–monitors these heaps and takes action to prevent a crash.
During startup of a Service Manager process, immediately after the JVM is created, a memory monitor thread is started, which will poll for a low memory condition every 15 seconds.
On every iteration, the memory monitoring thread fetches the current usage of java heap (all platforms) and native heap (Windows only) and set the process global flags
lowMemoryOnJava and lowMemoryOnNative when the usage exceeds 90% of allocated memory in that category.
These flags are unset again when the usage of memory drops below 70%.
To prevent server crashes due to low available heap memory and to avoid disrupting users who are logged on to a Service Manager process, the servletcontainer takes the following actions when the low memory flags are set:
- Writes warning messages to
sm.log. - Notifies LoadBalancer not to send that servlet any new client connections.
- Denies new client sessions (Windows client, web client or web services client) for that servlet. They are sent to another one.
- Does not allow existing clients to open new tabs. However, they can trade the existing tabs for new ones. For example, if you close two tabs, you will be allowed to open two new tabs. If you cannot operate without opening any new tabs you need to logoff and login again.
Normal processing is resumed when the heap usage drops below 70%. The servletcontainer takes the following actions when the low memory flags are unset.
- Writes Info messages to the sm.log file indicating normal memory usage.
- Notifies LoadBalancer to resume sending of new client connections.
Related topics
Monitoring native heap and Java heap memory
Logging memory monitoring
Related topics
Servlet parameters
Debugging parameters
Parameter: log4jDebug
Parameter: memorypollinterval
