JDK-4430838 : merlin-beta runtime stops with exception on w2k Hindi locale
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.4.0
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2001-03-28
  • Updated: 2001-07-17
  • Resolved: 2001-07-17
Related Reports
Duplicate :  
Relates :  
Description
On Windows 2000, set "your locale" to "hindi" at Control Panel/Regional Options
(you probably need to install the necessary "Indic" language support packages),
then just run java for any apps, the runtime stops with exception 

Exception in thread "main" java.lang.NoClassDefFoundError: xxxx

ladybird works fine.

Comments
EVALUATION Please look at text below. Looks like merlin is not handling hindi text correctly. T:\>java -version java version "1.3.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_01) Java HotSpot(TM) Client VM (build 1.3.0_01, mixed mode) T:\>l:\bin\java -version java version "1.3.1-rc1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b21) Java HotSpot(TM) Client VM (build 1.3.1-rc1-b21, mixed mode) T:\>m:\bin\java -version a v a v e r s i o n " 1 . 4 . 0 - b e t a " J a v a ( T M ) 2 R u n t i m e E n v i r o n m e n t , S t a n d a r d E d i t i o n ( b u i l d 1 . 4 . 0 - b e t a - b 5 8 ) n u l l ( b u i l d n u l l , m i x e d m o d e ) Trying to run notepad demo M:\DEMO\JFC\NOTEPAD>m:/bin/java -jar Notepad.jar Exception in thread "main" j a v a . l a n g . E x c e p t i o n I n I n i t i a l i z e r E r r o r C a u s e d b y : j a v a . l a n g . N u l l P o i n t e r E x c e p t i o n a t j a v a . i o . W i n 3 2 F i l e S y s t e m . n o r m a l i z e ( . . / . . / . . / s r c / w i n 3 2 / c l a s s e s / j a v a / i o / W i n 3 2 F i l e S y s t e m . j a v a : 1 6 6 ) a t j a v a . i o . W i n 3 2 F i l e S y s t e m . g e t U s e r P a t h ( . . / . . / . . / s r c / w i n 3 2 / c l a s s e s / j a v a / i o / W i n 3 2 F i l e S y s t e m . j a v a : 2 5 9 ) a t j a v a . i o . W i n 3 2 F i l e S y s t e m . r e s o l v e ( . . / . . / . . / s r c / w i n 3 2 / c l a s s e s / j a v a / i o / W i n 3 2 F i l e S y s t e m . j a v a : 2 7 7 ) a t j a v a . i o . F i l e . g e t C a n o n i c a l P a t h ( . . / . . / . . / s r c / s h a r e / c l a s s e s / j a v a / i o / F i l e . j a v a : 4 5 0 ) a t j a v a . l a n g . C l a s s L o a d e r . l o a d L i b r a r y 0 ( . . / . . / . . / s r c / s h a r e / c l a s s e s / j a v a / l a n g / C l a s s L o a d e r . j a v a : 1 3 4 8 ) a t j a v a . l a n g . C l a s s L o a d e r . l o a d L i b r a r y ( . . / . . / . . / s r c / s h a r e / c l a s s e s / j a v a / l a n g / C l a s s L o a d e r . j a v a : 1 3 1 9 ) a t j a v a . l a n g . R u n t i m e . l o a d L i b r a r y 0 ( . . / . . / . . / s r c / s h a r e / c l a s s e s / j a v a / l a n g / R u n t i m e . j a v a : 7 7 3 ) a t j a v a . l a n g . S y s t e m . l o a d L i b r a r y ( . . / . . / . . / s r c / s h a r e / c l a s s e s / j a v a / l a n g / S y s t e m . j a v a : 8 3 0 ) a t s u n . s e c u r i t y . a c t i o n . L o a d L i b r a r y A c t i o n . r u n ( L o a d L i b r a r y A c t i o n . j a v a : 5 3 ) a t j a v a . s e c u r i t y . A c c e s s C o n t r o l l e r . d o P r i v i l e g e d ( N a t i v e M e t h o d ) a t j a v a . u t i l . z i p . Z i p F i l e . < c l i n i t > ( Z i p F i l e . j a v a : 5 2 ) Not sure but it sounds like we have an internationalization issue here. Re-assigning to localization team to look into further. ------------------------------------------------------------------------------- The localization team doesn't do internationalization. Making sure that functionality works with all required locales is the responsibility of the group owning the functionality (with help from the internationalization team, if needed). Assigning to I/O for further investigation, since that's where the exception occurs. norbert.lindenberg@Eng 2001-04-05 ===================================================== This bug is a duplicate of 4371865, java and appletviewer fail to run with Windows 2000 Unicode Locales. on W2K, Hindi default encoding is Unicode (little-endian). The native code JNU_NewStringPlatform(...) breaks as there is an assumption that a string encoded with the platforms default encoding will not contain any embedded null characters. This assumption breaks down for Unicode/UTF16 encodings. Other locales affected include Georgian, Armenian. Ian.Little@Ireland 4/9/2001. ======================================================================
09-04-2001