Skip to content

Add clue to error log when flash is unavailable after server restart without session persistence#5566

Merged
BalusC merged 2 commits into4.0from
issue__5552
May 25, 2025
Merged

Add clue to error log when flash is unavailable after server restart without session persistence#5566
BalusC merged 2 commits into4.0from
issue__5552

Conversation

@BalusC
Copy link
Copy Markdown
Contributor

@BalusC BalusC commented Feb 16, 2025

@BalusC BalusC requested review from arjantijms and mnriem February 16, 2025 13:55
Copy link
Copy Markdown

@DGuhr DGuhr left a comment

Choose a reason for hiding this comment

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

LGTM, if I may give my 2c as issue starter. One optional thing:
Would it make sense to add a guard-clause to


so there's no NPE thrown? I'm not very sure if there are other situations where this could happen, for me it was the JSF1094 though, so maybe throw that one, then, instead?

@BalusC
Copy link
Copy Markdown
Contributor Author

BalusC commented Feb 23, 2025

I added an unit test and sorted out the NPE.

static final String FLASH_NOW_REQUEST_KEY = FLASH_ATTRIBUTE_NAME + "n";

private enum CONSTANTS {
enum CONSTANTS {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why is private being removed?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

So it's accessible from ELFlashTest in same package.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

As I don't remember so I am just going to ask. Would this impact the signature tests?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No idea. How do I run them so I can verify?

@BalusC BalusC merged commit f66c9b1 into 4.0 May 25, 2025
3 checks passed
@BalusC BalusC deleted the issue__5552 branch May 25, 2025 15:44
@BalusC BalusC added this to the 4.0.12 milestone May 25, 2025
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.

3 participants