Skip to content

Fix inconsistent maxWait value in DB2 and PostgreSQL DB pool config samples#6196

Closed
BimsaraBodaragama wants to merge 3 commits into
wso2:masterfrom
BimsaraBodaragama:fix/maxwait-db2-postgresql
Closed

Fix inconsistent maxWait value in DB2 and PostgreSQL DB pool config samples#6196
BimsaraBodaragama wants to merge 3 commits into
wso2:masterfrom
BimsaraBodaragama:fix/maxwait-db2-postgresql

Conversation

@BimsaraBodaragama

Copy link
Copy Markdown
Member

Summary

The maxWait value in the sample DB pool configurations for DB2 and PostgreSQL documentation was set to 360000 ms (6 minutes), while all other database type documentation used 60000 ms (1 minute). This PR unifies the value to 60000 ms across all affected versions.

Affected versions: IS 5.10.0 – 7.3.0 (+ next)

Files changed (16):

  • change-to-ibm-db2.md — 5.10.0, 5.11.0, 6.0.0, 6.1.0, 7.0.0, 7.1.0, 7.2.0, 7.3.0, next
  • change-to-postgresql.md — 6.0.0, 6.1.0, 7.0.0, 7.1.0, 7.2.0, 7.3.0, next

Note: PostgreSQL docs for 5.10.0 and 5.11.0 already had the correct value (60000) and were not modified.

Fixes: wso2/product-is#27975

Update maxWait from 360000 ms (6 min) to 60000 ms (1 min) to match
all other database type documentation. Affects IS 5.10.0 – 7.2.0 and next.

Fixes: wso2/product-is#27975
Update maxWait from 360000 ms (6 min) to 60000 ms (1 min) to match
all other database type documentation. Affects IS 6.0.0 – 7.2.0 and next.

Fixes: wso2/product-is#27975
Update maxWait from 360000 ms (6 min) to 60000 ms (1 min) in the
IS 7.3.0 DB2 and PostgreSQL documentation pages.

Fixes: wso2/product-is#27975
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@BimsaraBodaragama, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 51 minutes and 58 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: ab5c6115-2fee-47ff-a076-07c02ffcf9ba

📥 Commits

Reviewing files that changed from the base of the PR and between 3331dfb and a1aebe9.

📒 Files selected for processing (16)
  • en/identity-server/5.10.0/docs/setup/changing-to-ibm-db2.md
  • en/identity-server/5.11.0/docs/setup/changing-to-ibm-db2.md
  • en/identity-server/6.0.0/docs/deploy/change-to-ibm-db2.md
  • en/identity-server/6.0.0/docs/deploy/change-to-postgresql.md
  • en/identity-server/6.1.0/docs/deploy/change-to-ibm-db2.md
  • en/identity-server/6.1.0/docs/deploy/change-to-postgresql.md
  • en/identity-server/7.0.0/docs/deploy/configure/databases/carbon-database/change-to-ibm-db2.md
  • en/identity-server/7.0.0/docs/deploy/configure/databases/carbon-database/change-to-postgresql.md
  • en/identity-server/7.1.0/docs/deploy/configure/databases/carbon-database/change-to-ibm-db2.md
  • en/identity-server/7.1.0/docs/deploy/configure/databases/carbon-database/change-to-postgresql.md
  • en/identity-server/7.2.0/docs/deploy/configure/databases/carbon-database/change-to-ibm-db2.md
  • en/identity-server/7.2.0/docs/deploy/configure/databases/carbon-database/change-to-postgresql.md
  • en/identity-server/7.3.0/docs/deploy/configure/databases/carbon-database/change-to-ibm-db2.md
  • en/identity-server/7.3.0/docs/deploy/configure/databases/carbon-database/change-to-postgresql.md
  • en/identity-server/next/docs/deploy/configure/databases/carbon-database/change-to-ibm-db2.md
  • en/identity-server/next/docs/deploy/configure/databases/carbon-database/change-to-postgresql.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@BimsaraBodaragama

Copy link
Copy Markdown
Member Author

Closing this PR — the fix has been re-raised as #6197 with a cleaner commit structure. All 16 file changes are identical; only the commit history has been reorganised. Please track progress in #6197.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sample "maxWait" value in DB2 & PostgreSQL documentation is different to other database type configurations

1 participant