-
Notifications
You must be signed in to change notification settings - Fork 779
Multiple javasound exceptions at startup #2259
Comments
I get the javasound issue but my cause is different (not sure if that makes a difference to the fix you implemented):
|
The fix should cover your case as well. |
Was this part of last night's build? If so, I'm still getting the same issue |
Nightly ESH, yes. OH2 only picks up ESH stable and the fix was included there a few hours ago only, see https://hudson.eclipse.org/smarthome/job/SmartHomeDistribution-Stable/changes. |
Ah thanks! |
Available now, see https://community.openhab.org/t/basic-ui-tts-and-more/14972. |
@kaikreuzer Unfortunately, I still get the same java sound exceptions (as @mhilbush) with the latest build #524. Can anyone confirm this? Or did I do something wrong? I did an apt-get update && upgrade from my build #512 to #524. |
Are you using OracleJDK or OpenJDK? The log from @mhilbush sounds as if he is using OpenJDK (which is not recommended for OH). |
OracleJDK. I am using openhabian (latest v0.9) for installation of OH2 on my RPi3. I also do think that @mhilbush uses Oracle JDK, as I can see the code 1.8.0_91 many times in his error messages. For me, it was 1.8.0_101 (as this is the latest OracleJDK version). Maybe I'll give it a try and install from scratch. |
Nevermind...I did a clean new install using openhabian. Now the error is gone! |
Ok, perfect! |
I installed build 524, and can confirm that the exceptions are gone. Thanks. I am running OpenJDK, BTW. Haven't noticed any stability issues, and I have plenty of compute capacity (not running on ARM). Nevertheless, I'll likely switch over to Oracle. |
Ok, if you are not on ARM, then OpenJDK might be ok - but there were many issues with it on ARM. |
Good to know. Thanks. That being the case I'll probably stick with openjdk for now, then switch to Zulu openjdk if that becomes the recommendation. I'd also be willing to put Zulu on my test box if you would benefit from some additional testing. |
I'm seeing this at startup in build 512.
The text was updated successfully, but these errors were encountered: