Skip to content

QPIDJMS-616: enhance error message to include additional info from errorCondition#55

Open
vm-karthik wants to merge 2 commits into
apache:mainfrom
vm-karthik:QPIDJMS-616
Open

QPIDJMS-616: enhance error message to include additional info from errorCondition#55
vm-karthik wants to merge 2 commits into
apache:mainfrom
vm-karthik:QPIDJMS-616

Conversation

@vm-karthik
Copy link
Copy Markdown

Enhance error message to include additional info from errorCondition

@vm-karthik vm-karthik closed this Nov 7, 2025
@vm-karthik vm-karthik reopened this Nov 7, 2025
@vm-karthik vm-karthik closed this Nov 7, 2025
@vm-karthik vm-karthik reopened this Nov 7, 2025
@vm-karthik vm-karthik closed this Apr 8, 2026
@vm-karthik vm-karthik reopened this Apr 8, 2026
@vm-karthik
Copy link
Copy Markdown
Author

Hello @gemmellr, Can you please review this ? I have already created a JIRA Bug for this : https://issues.apache.org/jira/browse/QPIDJMS-616

Please pardon me if I am tagging a wrong person of if correct process has not been followed here. Kindly let me know the process, if wrong..

if (info != null && !info.isEmpty()) {
messageWithInfo = message + " [info = " + info + "]";
}
return messageWithInfo;
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Is there any chance that the map returned by the errorCondition.getInfo() contains privileged information? Specifically contents of something read from disk or unobfuscated passwords or access tokens or similar?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wouldnt expect that, but its up to the peer to decide what they put in there so its impossible to say what might be in there. Typically nothing, hence whey no client I know of thus far does whats proposed.

@gemmellr
Copy link
Copy Markdown
Member

gemmellr commented Jun 2, 2026

I have previously looked at this. I dont think its a good idea adding the arbitrary map toString to the exception message, especially not just because a particular service has decided not to use either of the two other more direct ways to usefully describe the actual reason they are erroring, in form of the error description and condition (and to boot whilst misusing the core spec not-allowed condition). I have not had time to look at alternatives.

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.

4 participants