Skip to content

Add documentation for SSL profile failure handling at startup #2171

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

Open
ravindu25 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add documentation for SSL profile failure handling at startup #2171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions en/docs/install-and-setup/setup/transport-configurations/multi-https-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -223,3 +223,16 @@ set when you enable dynamic SSL profiles:
|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
| ` filePath ` | The relative/absolute file path of the custom SSL profile configuration XML file. | \- |
| ` fileReadInterval ` | The time interval (in milliseconds) in which configuration updates will be loaded and applied at runtime. This value should be greater than 1 minute. | 3600000 |

## Handling SSL profile load failures at startup

By default, if any custom SSL profile fails to load during startup (e.g., due to a missing keystore, incorrect password, or invalid keystore type), the Micro Integrator will abort the startup process.

To allow the server to start by skipping faulty profiles and logging a warning instead, pass the following JVM parameter at startup:Expand commentComment on lines R160 to R167Resolved
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Remove GitHub review interface artifacts from documentation.

Lines 231 and 234 contain text fragments that appear to be accidentally copied from GitHub's review interface:

  • Line 231: "Expand commentComment on lines R160 to R167Resolved"
  • Line 234: "Expand commentComment on line R170Resolved"

These artifacts should be removed from the documentation.

🧹 Proposed fix to remove artifacts 
-To allow the server to start by skipping faulty profiles and logging a warning instead, pass the following JVM parameter at startup:Expand commentComment on lines R160 to R167Resolved
+To allow the server to start by skipping faulty profiles and logging a warning instead, pass the following JVM parameter at startup:
 
 ```xml
--Dssl.profile.skip.failures=trueExpand commentComment on line R170Resolved
+-Dssl.profile.skip.failures=true
</details>


Also applies to: 234-234

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In
@en/docs/install-and-setup/setup/transport-configurations/multi-https-transport.md
at line 231, Remove the accidentally copied GitHub review artifacts from the
documentation paragraph where the JVM parameter is shown: locate the snippet
containing "-Dssl.profile.skip.failures=true" and remove the stray strings
"Expand commentComment on lines R160 to R167Resolved" and "Expand commentComment
on line R170Resolved" so the parameter stands alone and the surrounding text is
clean; ensure no other occurrences remain near the same paragraph (around the
shown JVM parameter) and update any affected spacing or punctuation.


</details>

<!-- fingerprinting:phantom:triton:puma:8f8bd171-cebf-49a4-b60b-0aee752c3dc5 -->

<!-- This is an auto-generated comment by CodeRabbit -->


```xml
-Dssl.profile.skip.failures=trueExpand commentComment on line R170Resolved
```

!!! Note
When this parameter is enabled, any request routed to a host whose SSL profile failed to load will fall back to the default SSL context. Ensure that such scenarios are handled appropriately in your environment.