Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 8.1 Update 4 CR2, 8.1 Update 4
Affects Version/s: None
Component/s: Patching
Labels:
- regression_test_only

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

8.1.z.GA
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/1585
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

When the server is updated using a JBoss CLI session via "installer" high level command, the standard output of the jboss-eap-installation-manager is stored in management-cli-installer-out.log file by redirecting its standard output and error to the log file using the ">>" operator.

Under such circumstances, even if the console character is configured to UTF-8, the character encodings chosen by JDK21 is the System's default character encoding. That generates an issue for certain server translations. To avoid problems like this, the encoding of the standard output/error, should be UTF-8.

is cloned by

WFCORE-7449 Non-UTF-8 characters can appear in the management-cli-installer-out.log with JDK21

Resolved

JBEAP-31687 [GSS](8.0.z) Non-UTF-8 characters can appear in the management-cli-installer-out.log with JDK21

Ready for QA

is incorporated by

JBEAP-31543 [GSS](8.1.z) Upgrade WildFly Core from 27.1.3.Final-redhat-00001 to 27.1.4.Final-redhat-00001

Resolved

Assignee:: Yeray Borges Santana

Reporter:: Yeray Borges Santana

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/12/10 6:34 PM

Updated:: 2025/12/18 9:18 PM

Resolved:: 2025/12/17 3:56 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates