Skip to content

Commit 6fb4f74

Browse files
committed
Cherry-pick branch 'wlstdocupdate' into 'release/4.1'
1 parent 28c2a77 commit 6fb4f74

File tree

2 files changed

+26
-1
lines changed
  • documentation/site/content/managing-domains

2 files changed

+26
-1
lines changed

documentation/site/content/managing-domains/accessing-the-domain/wlst.md

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,26 @@ You can use the `kubectl exec` command to start an interactive WLST session
2525
within a pod or to remotely run a WLST script on a pod.
2626
Typically, this is the preferred method.
2727

28+
**NOTE**: The WLST script uses the value of the environment variable `USER_MEM_ARGS` to control the heap settings of the JVM process. If you have set the environment variable
29+
`USER_MEM_ARGS` in the domain resource YAML, the WLST process will inherit the memory settings. For example,
30+
if you have `USER_MEM_ARGS` value set to `-Xms2048m -Xmx2048m`, the WebLogic server JAVA process will use this heap settings, and if you run the WLST script in the server pod,
31+
the WLST script JAVA process will also use this heap settings. This may cause unexpected behavior in the server pod due to additional memory usage.
32+
33+
In order to change the memory settings, you must do the following
34+
35+
36+
```shell
37+
USER_MEM_ARGS="" $ORACLE_HOME/oracle_common/common/bin/wlst.sh
38+
```
39+
This will unset the `USER_MEM_ARGS` and let the WLST to use the default heap size `-Xms32m -Xmx1024m`, and this only affect the WLST script process.
40+
41+
If you want to use different memory settings, you can adjust it by
42+
43+
```shell
44+
USER_MEM_ARGS="-Xms128m -Xmx128m" $ORACLE_HOME/oracle_common/common/bin/wlst.sh
45+
```
46+
47+
2848
For example, if a `domainUID` is `sample-domain1`,
2949
its Administration Server is named `admin-server` and is configured with default port `7001`,
3050
and its pods are running in namespace `sample-domain1-ns`,
@@ -34,7 +54,7 @@ then you can start an interactive WLST session this way:
3454
3555
$ kubectl -n sample-domain1-ns exec -it sample-domain1-admin-server /bin/bash
3656
37-
[oracle@sample-domain1-admin-server oracle]$ wlst.sh
57+
[oracle@sample-domain1-admin-server oracle]$ USER_MEM_ARGS="" $ORACLE_HOME/oracle_common/common/bin/wlst.sh
3858
3959
Initializing WebLogic Scripting Tool (WLST) ...
4060

documentation/site/content/managing-domains/domain-on-pv/overview.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,11 @@ The `initializeDomainOnPv` section:
2626
- Creates the RCU schema, if needed.
2727
- Creates the WebLogic domain home on the persistent volume based on the provided WDT models.
2828

29+
{{% notice note %}}
30+
If you are running WebLogic Scripting Tool (WLST) inside a server pod, then
31+
please refer to [Use kubectl exec]({{< relref "/managing-domains/accessing-the-domain/wlst#use-kubectl-exec">}}) in the WLST documentation for very important information related to memory usage.
32+
{{% /notice %}}
33+
2934
### High-level use case
3035

3136
The typical Domain on PV use case is for an application life cycle that requires persisting changes to the permanent file system.

0 commit comments

Comments
 (0)