fix(informix): make INFORMIXSERVER URL rewrite idempotent to avoid ever-growing JDBC URL on reconnect - #2289
Merged
Conversation
…er-growing JDBC URL on reconnect (code review follow-up)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
InformixDBManager.getConnectionappended":INFORMIXSERVER=<service>"toconnectInfo.urlon every call.ConnectInfois shared and reused across reconnects, so each reconnect appended anotherINFORMIXSERVERsegment — the JDBC URL grew without bound (...:INFORMIXSERVER=a:INFORMIXSERVER=a:...) and eventually broke connectivity.Fix
Append the server attribute only when the URL does not already contain
INFORMIXSERVER=, and only mutateconnectInfoin that case — making the rewrite idempotent.Tests
New
InformixDBManagerTest(3 tests) covers first-connect append and idempotent reconnect.mvn teston chat2db-community-informix: 3/3 pass.Verified on fork HandSonic#13 (meaningful CI checks green; dependency-review/project-sync jobs are fork-permission noise). Regression tests pass; adversarial review cleared.