Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

time zone jvm prop edits #7336

Merged
merged 3 commits into from
May 17, 2024
Merged

time zone jvm prop edits #7336

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
988eee6
add time zone jvm prop example
dmuelle May 14, 2024
ca34685
Update server-configuration-overview.adoc
dmuelle May 14, 2024
ec3383a
add timezone info to logging page
dmuelle May 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions modules/ROOT/pages/log-trace-configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,13 @@ A server has the following four primary log files:
- `verbosegc.XXX.log` - These files contain verbose garbage collection output from the JVM and are created by default when the Java implementation is either IBM Java or IBM Semeru Runtimes. Up to 10 rolling log files are created in your log directory, with 1024 GC cycles per file, where `XXX` represents the sequence number of the log file. Custom configurations take precedence over the default behavior. To disable the verbose garbage collection logs, add `VERBOSEGC=false` to the `server.env` file. For more information, see the https://eclipse.dev/openj9/docs/vgclog[Verbose garbage collection logs].
You can use the `user.timezone` JVM property to set the time zone for your application environments. Set the `user.timezone` property in the `jvm.properties` file. The updated time zone information is displayed in the `messages.log` and `trace.log` files. The following example shows how to set the time zone.

[subs=+quotes]
----
-Duser.timezone=_time_zone_code_
----

The following sections provide more information about configuring your Open Liberty logs:

* <<#configuaration,Logging configuration>>
Expand Down
12 changes: 7 additions & 5 deletions modules/reference/pages/config/server-configuration-overview.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,15 +166,17 @@ If no `jvm.options` files exist in these locations, then the server script looks
Common uses of `jvm.options` files include:

* Setting JVM memory limits
* Enabling Java Agents that are provided by monitoring products
* Setting Java System Properties
* Enabling Java agents that are provided by monitoring products
* Setting Java system properties
* Setting time zones
The `jvm.options` file format uses one line per JVM option, as shown in the following example:

[source,properties]
[subs=+quotes]
----
-Xmx512m
-Dmy.system.prop=This is the value.
-Dmy.system.prop=_property_value_
-Duser.timezone=_time_zone_code_
----

You don’t need to escape special characters, such as spaces.
Expand Down Expand Up @@ -222,7 +224,7 @@ The `configDropins` directory offers a convenient method for adding or modifying
* Defaults (`usr/servers/server_name/configDropins/defaults`): This directory is for setting defaults for configuration elements that are not specified in `server.xml`. It allows `server.xml` to remain the primary configuration source, with other default settings provided through this directory.
Changes to the configuration files placed in either the `configDropins/overrides` or `configDropins/defaults` directories are dynamically monitored. Additions, removals, or updates are reflected in the runtime configuration automatically.
Changes to the configuration files placed in either the `configDropins/overrides` or `configDropins/defaults` directories are dynamically monitored. Additions, removals, or updates are reflected in the runtime configuration automatically.

Configurations in the `configDropins/overrides` directory take precedence over configurations in the `server.xml` file, which in turn take precedence over configurations in the `configDropins/defaults` directory. The configurations in `configDropins/overrides` and `configDropins/defaults` supersede any default settings a feature specifies.

Expand Down