JDK-8074544 : webstart app fails with CouldNotLoadArgumentException when account in Japanese
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 8u40
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_8
  • CPU: x86
  • Submitted: 2015-03-06
  • Updated: 2018-03-30
  • Resolved: 2015-04-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9
8u144Fixed 9 b61Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
Java HotSpot(TM) Client VM (build 25.40-b25, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.2.9200]

A DESCRIPTION OF THE PROBLEM :
It has been announced that the issue JDK-8051420 and JDK-8054904 duplicate and have been already resolved on 7u71.
But when Windows logon account name is Japanese, home directry is Japanese also.
And when this user activate application from Java Web Start, "CouldNotLoadArgumentException" occures and cannot start. 

REGRESSION.  Last worked in version 7u65

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Log in on administrator account 
2. Chose Japanese language from the Language bar
3. Create user ���������������
4. Set "Current language for non-Unicode programs" to Japanese (Japan) inside:
Control Panel -> Clock, Language, and Region -> Region and Language ->
Administrative (tab) -> Language for non-Unicode programs -> Change system locale
5. Log in on ��������������� account
6. Input URL into browser and start with jacaws.
 http://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp 
7. 4. Error occures.
CouldNotLoadArgumentException[ ������������������������������������URL������������������������������������: C:\Users\������~1\AppData\Local\Temp\javaws2]
	at com.sun.javaws.Main.launchApp(Unknown Source)
	at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
	at com.sun.javaws.Main.access$000(Unknown Source)
	at com.sun.javaws.Main$1.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Application us loaded correctly and start.
ACTUAL -
"CouldNotLoadArgumentException" occures and cannot start.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
CouldNotLoadArgumentException[ ������������������������������������URL������������������������������������: C:\Users\������~1\AppData\Local\Temp\javaws2]
	at com.sun.javaws.Main.launchApp(Unknown Source)
	at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
	at com.sun.javaws.Main.access$000(Unknown Source)
	at com.sun.javaws.Main$1.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
Create logon account with single-byte characters and switch logon account only when using the application.
This is not a realistic workaround as it is too much of work. 


Comments
stack trace of the original exception java.io.FileNotFoundException: C:\Users\������~1\AppData\Local\Temp\javaws7 (The system cannot find the path specified) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(Unknown Source) at java.io.FileInputStream.<init>(Unknown Source) at java.io.FileInputStream.<init>(Unknown Source) at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source) at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main.access$000(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
20-03-2015

removing the regression keyword and changing synopsis to "webstart app fails with CouldNotLoadArgumentException when account in Japanese"
19-03-2015

7u65 fails with the same exception. Is this a regression?
18-03-2015

Reproducible to me too with user ��������������� Tested with 8u40 b10
18-03-2015

I try to reproduce it with 8u40 b25 and the test works fine in my environment. Tested with account name in cyrillics. Also tested with 8u40 b10 (JDK-8054904) - it also worked fine and looks like I couldn't reproduce the original issue. Could you please provide more info about the failure - please attach deployment trace logs - can you please confirm that this issue is specific to Asian languages or it's also still reproducible with other languages too (for example, Serbian from the bug report). That is, does the fix for JDK-8054904 improves the situation and something has been fixed?
12-03-2015

It also happens in win7 zh_CN, when the account has Chinese character. The bug may have higher priority, because in Asian windows like ja and zh_CN, if user account has native character, JNLP will not work.
09-03-2015

It may not be a true regression but JDK-8054904 might have failed.
06-03-2015