JDK-6495567 : CR 4964288 (sound, Unexpected IAE raised while getting TargetData) is not fixed in windows-amd64 JDK
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.sound
  • Affected Version: 5.0u11,6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2006-11-20
  • Updated: 2012-03-22
  • Resolved: 2006-12-14
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.
Other JDK 6 JDK 7
1.4.2_15Fixed 6u1 b01Fixed 7Resolved
Related Reports
Relates :  
JDK-6498661 - api/javax_sound/sampled/TargetDataLine/index.html#TargetDataLine fails
Relates :  
JDK-4964288 - Unexpected IAE raised while getting TargetDataLine
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).
30-11-2006
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.
29-11-2006
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).
22-11-2006