Randomly thrown exceptions when starting to play a sound

Troubleshooting sound
1

about one time out of 20, i get this error:

27.09.2008 16:59:53 class com.jmex.audio.openal.OpenALAudioTrack play()
SCHWERWIEGEND: Exception
org.lwjgl.openal.OpenALException: OpenAL error: Invalid Operation (40964)
at org.lwjgl.openal.Util.checkALError(Util.java:56)
at org.lwjgl.openal.AL10.alSourcei(AL10.java:755)
at com.jmex.audio.openal.OpenALMemoryAudioPlayer.play(OpenALMemoryAudioPlayer.java:112)
at com.jmex.audio.AudioTrack.play(AudioTrack.java:113)
at hstar.hhexen.entity.usableitems.weapon.Weapon$1.onWeaponUsed(Weapon.java:124)
at hstar.hhexen.entity.event.Events.onWeaponUsed(Events.java:191)
at hstar.hhexen.entity.usableitems.weapon.Weapon.activate(Weapon.java:166)
at hstar.hhexen.entity.decorators.logic.WeaponUsage.applyBeforeStaticCollisions(WeaponUsage.java:35)
at hstar.hhexen.entity.decorators.logic.WeaponUsage.applyBeforeStaticCollisions(WeaponUsage.java:14)
at hstar.hhexen.entity.decorators.Decorations.handleBeforeStaticCollisions(Decorations.java:91)
at hstar.hhexen.entity.decorators.Decorations.handleDecorations(Decorations.java:77)
at hstar.hhexen.entity.DecoratedEntity.onTick(DecoratedEntity.java:101)
at hstar.hhexen.entity.MoveableEntity.onTick(MoveableEntity.java:91)
at hstar.hhexen.entity.ControllableEntity.onTick(ControllableEntity.java:440)
at hstar.hhexen.entity.BaseActor.onTick(BaseActor.java:382)
at hstar.hhexen.entity.actors.DefaultHumanControlledActor.onTick(DefaultHumanControlledActor.java:117)
at hstar.hhexen.engine.core.entities.Entities.executeHooks(Entities.java:203)
at hstar.hhexen.engine.core.entities.Entities.onTick(Entities.java:247)
at hstar.hhexen.engine.core.Core.onTick(Core.java:237)
at hstar.hhexen.engine.AbstractHhexen.update(AbstractHhexen.java:89)
at com.jme.app.BaseGame.start(BaseGame.java:79)
at hstar.hhexen.Main.main(Main.java:33)



any ideas?
2

First check was LWJGL forum:

This error has popped up on at least one occasion on the lwjgl openAl board. Here is the thread I found. It seems that they stopped looking for a reason or solution and just wrote a try/catch around it and ignored the error. A hack for sure but supposedly resolves this.



Google returned a surprising result - this has also popped up in jMe before  :smiley:

Related jME thread



And google returned actually a number of hits on this error message, so if the links I posted dont help and you want to keep investigating this error, at least there is something to go on.