JDK-4745013 : Japanese SunOS: java.net.ConnectException has garbled message
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.3.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2002-09-10
  • Updated: 2002-09-12
  • Resolved: 2002-09-12
Related Reports
Duplicate :  
Description

Name: pa48320			Date: 09/10/2002


"uname -a" output:
SunOS jpsun2084 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-Enterprise

This is a Japanese Solaris machine.  Using the following test code:

package mypackage1;
import java.net.Socket;
public class Class1 {
  public static void main(String[] args) throws Exception {
     //  Throws exception with garbled message.
     new Socket( "jpsun2084.jp.oracle.com", 23791 );
  }
}

This code correctly throws a ConnectException, but the message attached to the ConnectException is garbled in Japanese:

Exception in thread "main" java.net.ConnectException: ????????????????????????????????????????????????????????????
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:355)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:142)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:129)
	at java.net.Socket.<init>(Socket.java:273)
	at java.net.Socket.<init>(Socket.java:100)
	at mypackage1.Class1.main(Class1.java:6)

This kind of Socket code is used in an application server client which then displays the (unreadable) exception message to the user.
(Review ID: 164302) 
======================================================================

Comments
WORK AROUND Name: pa48320 Date: 09/10/2002 No known work-around. ======================================================================
11-06-2004

EVALUATION This is dup of 4258198 - already fixed in hopper. ###@###.### 2002-09-11
11-09-2002