Bug 1011849 - Windows: Unknown codeset (Cp1252), defaulting to ISO-8859-1
Summary: Windows: Unknown codeset (Cp1252), defaulting to ISO-8859-1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB, IIOP
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: David M. Lloyd
QA Contact: Jan Martiska
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-25 08:53 UTC by Jitka Kozana
Modified: 2019-12-16 04:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-29 20:17:57 UTC
Type: Bug


Attachments (Terms of Use)

Description Jitka Kozana 2013-09-25 08:53:54 UTC
EAP 6.2.0.ER3 does not know codeset Cp1252. 

See this log snippet from server.log from windows:

03:41:36,053 WARN  [jacorb.codeset] (MSC service thread 1-10) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

Link to whole server log:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-manu-multinode-startup-different-IPs-win-2/30/jdk=java17_default,label=Win2k8_x86/artifact/target/manu-reports/units/manu.testsuite.eap6.acceptance.multinodeStartup.MultinodeStartupDifferentIPs/server.log-standalone-full-ha.xml-server2.log

Comment 2 Dimitris Andreadis 2013-10-24 18:27:43 UTC
Assigning jpai EJB issues to david.lloyd. Please re-assign to Cheng or others as needed.

Comment 3 Rostislav Svoboda 2014-03-05 12:51:15 UTC
Proposing as blocker as discussed on EAP 6 PM meeting March 4.

This is blocking acceptance tests where we have requirement for issue-less startup & shutdown.

Comment 4 Rostislav Svoboda 2014-03-21 11:35:16 UTC
https://github.com/JacORB/JacORB/blob/R_2_3_2_jboss-branch/src/org/jacorb/orb/giop/CodeSet.java#L223

We would like to hear if WARN is what should be used.

BTW adding "-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8" to JAVA_OPTS helped to suppress the warning, so removing blocker flag.

Comment 5 David M. Lloyd 2014-09-11 15:50:53 UTC
I think the fix is simply to set the encodings to UTF-8 always.  However since this is easily worked around and there's no obvious fix, I'm NAK'ing for 6.4.

Comment 7 Brad Maxwell 2016-08-29 20:17:57 UTC
Closing / Won't Fix as per comment #5


Note You need to log in before you can comment on or make changes to this bug.