Skip to content

Trace update to ApplicationManager.java#34891

Open
tbitonti wants to merge 1 commit into
OpenLiberty:integrationfrom
tbitonti:app-manager-extract-log
Open

Trace update to ApplicationManager.java#34891
tbitonti wants to merge 1 commit into
OpenLiberty:integrationfrom
tbitonti:app-manager-extract-log

Conversation

@tbitonti
Copy link
Copy Markdown
Member

Preperatory changes for updating how the extraction log is managed.

################################################################################################

Delete this section and fill in the remaining info from the template

ATTENTION, READ THIS: Updated July 2024

Read and understand this completely, then delete the static part of the template.

If a reviewer or merger sees this template, they should fail the review or merge.

If this code change is fixing a user-visible bug in previously released code, it MUST
have an associated issue mentioned in the PR text or description.

  • That Issue also MUST be labelled “release bug”

    This directs automation to scrape this fix for inclusion in the next release's
    list of bugs fixed.

  • The linkage between PR and Issue should use the Fixes #... syntax rather than a manual
    link via the Development widget.

Otherwise, a link to an issue or specific issue labels are optional.

For full details, please see this wiki page: https://github.com/OpenLiberty/open-liberty/wiki/Open-Liberty-Conventions
################################################################################################

Preperatory changes for updating how the extraction log is managed.
// TODO: This check for a class cast exception seems unnecessary:
// Configuration metadata type should always put properly
// typed values.
value = deflt;
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.

Is this needed? Why not keep T value = deflt; from the original

writeCase = "Removing unused extraction log";

// TODO: Is this correct? Discarding the log forces the
// applications to be re-expanded.
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.

Looks right, only happens if we have the extractsLog file but autoExpand is false. Shouldn't have the extractsLog file in this case

if ( prop != null ) {
value = prop;
} else {
value = deflt; // Assign the default if present and null.
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.

redundant if you just keep T value = deflt from the original

*
* This is used for normal activation and for configuration updates.
*
* TODO: Enabling auto-expand does NOT cause the extraction data
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.

Going from autoExpand=false to autoExpand=true means no extractedLog file, so no issue there

@rsherget rsherget removed their assignment May 14, 2026
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.

2 participants