Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Domino
Categories Integration
Created by Guest
Created on Feb 27, 2026

A warning message when java.policy is being modified

Goal:

The objective is to implement a warning notification during the Domino update process, alerting users that the java.policy file will be modified and detailing the specific changes to be applied.


Enhanced Steps to Reproduce

Preconditions:

HCL Domino [Current Version, e.g., 12.0.2] is installed and running.

  • Custom permissions have been added to the java.policy file (located in the JVM security directory).

    • Example addition: permission java.lang.management.ManagementPermission "monitor";

Environment:

  • OS: [e.g., Windows Server 2022 / RHEL 8]

  • Software: HCL Domino Server

  • Target Update: [e.g., FixPack 3]


Steps to reproduce the issue:

  1. Modify Configuration: Open the java.policy file in the Domino JVM directory and add a custom security setting (e.g., a specific permission for a third-party agent).

  2. Verify Baseline: Start the Domino server and confirm that no AccessControlException errors appear in the console.

  3. Execute Upgrade: Run the installer for the latest Domino Fixpack on the existing server. Observation: Note that the installer proceeds without warning the user about overwriting configuration files.

  4. Restart Service: Once the installation completes, restart the Domino server.

  5. Check Logs: Monitor the console output and the console.log file.


Actual Results on why this is happening:

The java.policy file is overwritten by the installer, reverting to the default version. This triggers an immediate flood of java.security.AccessControlException: Access denied errors in the console, causing log files to grow rapidly. Below is the error message example:

[010809:000746-00007F2445E0D700] 02/17/2026 04:18:08 PM HTTP JVM: java.security.AccessControlException: Access denied ("java.lang.management.ManagementPermission" "monitor")


Enhancement Needed:

The system must trigger a notification upon any modification to java.policy, including the absolute path of the modified file.

Example:

Warning: The java.policy file has been modified.

Location: /path/to/directory/java.policy



  • Attach files