Bug ID: 6495567 CR 4964288 (sound, Unexpected IAE raised while getting TargetData) is not fixed in windows-amd64 JDK

6495567 : CR 4964288 (sound, Unexpected IAE raised while getting TargetData) is not fixed in windows-amd64 JDK

Details

Type:	Bug	Submit Date:	2006-11-20
Status:	Closed	Updated Date:	2012-03-22
Project Name:	JDK	Resolved Date:	2006-12-14
Component:	client-libs	OS:	windows_xp
Sub-Component:	javax.sound	CPU:	x86
Priority:	P2
Resolution:	Fixed
Affected Versions:	5.0u11,6
Fixed Versions:	6u1

Related Reports

Backport:	JDK-2144759 - CR 4964288 (sound, Unexpected IAE raised while getting TargetData) is not fixed in windows-amd64 JDK
Backport:	JDK-2144760 - CR 4964288 (sound, Unexpected IAE raised while getting TargetData) is not fixed in windows-amd64 JDK
Backport:	JDK-2191423 - CR 4964288 (sound, Unexpected IAE raised while getting TargetData) is not fixed in windows-amd64 JDK
Relates:	JDK-4964288 - Unexpected IAE raised while getting TargetDataLine
Relates:	JDK-6498661 - api/javax_sound/sampled/TargetDataLine/index.html#TargetDataLine fails

Sub Tasks

Description

JCK            : JCK6.0 b35
J2SE           : FAIL - mustang b104 windows-amd64 . PASS - mustang b104 windows-i586 on the same hardware.
Platform[s]    : FAIL - windows x64. 
switch/Mode    : FAIL - with defaut keys

Five tests:

api/javax_sound/sampled/AudioInputStream/index.html#Ctor[Ctor003]
api/javax_sound/sampled/AudioSystem/index.html#getLine[getLine001]
api/javax_sound/sampled/AudioSystem/index.html#getLine[getLine004]
api/javax_sound/sampled/Mixer/index.html#Mixer[Mixer2002]
api/javax_sound/sampled/Mixer/index.html#getLine[getLine002]

fail with windows-amd64 JDK build 104 and pass for windows-i586 jdk b104. Looks like CR  4964288 was not fixed for windows-amd64 (originally targeted for tiger). Example from CR 4964288 works just as it was described in this CR.

Problem found on windows XP amd64 (stt-14.russia) and windows 2003 amd64 (vmsqe-jds-01.russia)

Comments

SUGGESTED FIX

With Remote Desktop input (recording) devices are not accessible, but waveInGetNumDevs() function reports actual number of input devices installed in the system.
To detect the case fix tries to query default device (if default device is unaccessible, then system has no accessible devices).

2006-11-30

EVALUATION

Additional investigation shown that tests fail if test run is started from Windows Remote Desktop session. Apparently windows is using some kind of substitution sound driver for Remote Desktop Sessions. This driver lacks sound recording device and MIDI playback device.

2006-11-29

EVALUATION

Problem in old implementation that is used for windows-amd64.
JavaSound should be switched to using DirectSound mixers on the platform (like windows-i586 implementation).

2006-11-22

SELECT A COUNTRY/REGION
Africa Operation Argentina Australia Austria Bahrain Bangladesh Belgium & Luxembourg Belize Bhutan Bolivia Bosnia & Herzegovina Brasil Brunei Bulgaria Cambodia Canada - English Canada - French Chile China Colombia	Costa Rica Croatia Cyprus Czech Republic Denmark Ecuador Egypt Estonia Finland France Germany Greece Guatemala Honduras Hong Kong Hungary India Indonesia Iraq Ireland	Israel Italy Japan Jordan Kazakhstan Korea Kuwait Laos Latvia Lebanon Lithuania Malaysia Maldives Malta Mexico Moldova Nepal Netherlands New Zealand Nicaragua	Norway Oman Pakistan Panama Paraguay Peru Philippines Poland Portugal Puerto Rico Qatar Romania Russia Saudi Arabia Serbia & Montenegro Singapore Slovakia Slovenia South Africa Spain	Sri Lanka Sweden Switzerland -- French Switzerland -- German Taiwan Thailand Turkey Ukraine United Arab Emirates United Kingdom United States Uruguay Venezuela Vietnam Yemen

Hardware and Software, Engineered to Work Together