I am am experiencing the same thing.
Happens at least once a minute.
2020-06-12 12:37:32.400 [INFO ] [control.internal.WebSocketConnection] - Web Socket error
java.nio.channels.AsynchronousCloseException: null
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:181) ~[?:?]
at java.util.ArrayList.forEach(ArrayList.java:1257) [?:1.8.0_252]
at org.eclipse.jetty.client.AbstractConnectionPool.close(AbstractConnectionPool.java:208) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.DuplexConnectionPool.close(DuplexConnectionPool.java:237) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpDestination.close(HttpDestination.java:385) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpClient.doStop(HttpClient.java:260) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.client.WebSocketClient.doStop(WebSocketClient.java:371) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [bundleFile:?]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection
Same here.
2020-06-12 20:36:24.559 [INFO ] [amazonechocontrol.internal.WebSocketConnection] - Web Socket error
java.nio.channels.AsynchronousCloseException: null
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:181) ~[?:?]
at java.util.ArrayList.forEach(ArrayList.java:1257) [?:1.8.0_232]
at org.eclipse.jetty.client.AbstractConnectionPool.close(AbstractConnectionPool.java:208) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.DuplexConnectionPool.close(DuplexConnectionPool.java:237) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpDestination.close(HttpDestination.java:385) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpClient.doStop(HttpClient.java:260) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.client.WebSocketClient.doStop(WebSocketClient.java:371) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [bundleFile:?]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$2.run(WebSocketConnection.java:184) [bundleFile:?]
at java.util.TimerThread.mainLoop(Timer.java:555) [?:1.8.0_232]
at java.util.TimerThread.run(Timer.java:505) [?:1.8.0_232]
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:181) ~[?:?]
at java.util.ArrayList.forEach(ArrayList.java:1257) [?:1.8.0_252]
at org.eclipse.jetty.client.AbstractConnectionPool.close(AbstractConnectionPool.java:208) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.DuplexConnectionPool.close(DuplexConnectionPool.java:237) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpDestination.close(HttpDestination.java:385) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpClient.doStop(HttpClient.java:260) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.client.WebSocketClient.doStop(WebSocketClient.java:371) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [bundleFile:?]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$2.run(WebSocketConnection.java:184) [bundleFile:?]
at java.util.TimerThread.mainLoop(Timer.java:555) [?:1.8.0_252]
at java.util.TimerThread.run(Timer.java:505) [?:1.8.0_252]
Everything still works… but OH has crashed several times and logs showed increasing numbers of these exceptions before it crashed.
Same error here.
The openhab.log points at amazonechocontrol binding:
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [122:org.openhab.binding.amazonechocontrol:2.5.0.RC_3]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$2.run(WebSocketConnection.java:184) [122:org.openhab.binding.amazonechocontrol:2.5.0.RC_3]
As you can see I run Amazon Echo Control Binding version 2.5.0.RC_3.
On my side this error usually occured previously one time in the night when my router reconnected to my internet provider, but since last reconnect today at 03:30am this error occurs nearly everey minute.
i think a least java!!! zulu, because i use openhabian. maybe all other too.
the last i have done bevor these behaviour is I do an update with:
openhabian-config 03
openhabian-config 10 (all)
BTW That was the first time I saw the info, that you can choose java 64bit for x86 or java 32bit for arm-systems… maybe ther is the problem.
on the other hand, all,of us report the web-socket error coming from java! this is the common point of failure.
openjdk version “1.8.0_252”
openjdk runtime env (zulu 8.46.0.225-ca-linux_aarch32hf) (build 1.8.0_252_b225)
opnejdk client vm (zulu 8.46.0.225-ca-linux_aarch32hf) (build 1.8.0_252_b225, mixed mode, Evaluation)
what else can I report?
i use paperui habminui basicui (also install habpanel but never used and classiui)
service:
hue emulation, openhab cloud
language server (lsp)
bindings:
amazone echo control
exec
hue
icloud
kodi
network
ntp
samsung tv
z-wave
OK
2020-06-13_13:53:12_CEST [openHABian] Optimizing Java to run on low memory single board computers…
$ systemctl daemon-reload
$ systemctl restart openhab2.service
$ java -version
Picked up JAVA_TOOL_OPTIONS: -Dgnu.io.rxtx.SerialPorts=/dev/tty96B0
openjdk version “1.8.0_252”
OpenJDK Runtime Environment (Zulu 8.46.0.225-CA-linux_aarch32hf) (build 1.8.0_252-b225)
OpenJDK Client VM (Zulu 8.46.0.225-CA-linux_aarch32hf) (build 25.252-b225, mixed mode, Evaluation)
2020-06-13_14:00:07_CEST [openHABian] Checking for default openHABian username:password combination… OK (unknown user)
2020-06-13_14:00:07_CEST [openHABian] We hope you got what you came for! See you again soon
What does the first “Optimizing Java to run o…” mean?
And What is “openHABian username:password combination… OK (unknown user)” “unknown user”
?
Sorry for posting so often, but the systtem stocks after a few hours and so the system is not suitable! to controll for examble my hot water system… open a tap and getting showerwater with 80°C is not very funny!!
The variable EXTRA_JAVA_OPTS is set to
EXTRA_JAVA_OPTS=“-Xms16m -Xmx256m
one machines with low memory ( less 900MB ) and to
EXTRA_JAVA_OPTS=”-Xms192m -Xmx320m
on others.
Xms: initial Java heap size
Xmx: maximum heap size
A workaround to have openHAB up and running without memory errors is to stop the amazonechocontrol binding in karaf console, worked for me and other OH users - meanwhile @wikibear opened a ticket, see also here:
thanks for explanation… I can´t undersand these parameters .i´m not familar with java!.. sorry…
But my Tinkerboard has 2GB RAM … So can i set other / maybe better values for my system - but i think this will only spread the time till crash with memory …
BTW to all
I delete Amazon Echo Control Binding version 2.5.0.RC_3 which rossko57 supposed… but bevor i replug the jar-file i get the same web_socket error!!!
2020-06-13 15:50:03.359 [INFO ] [control.internal.WebSocketConnection] - Web Socket error {}
java.nio.channels.AsynchronousCloseException: null
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:181) ~[?:?]
at java.util.ArrayList.forEach(ArrayList.java:1257) [?:1.8.0_252]
at org.eclipse.jetty.client.AbstractConnectionPool.close(AbstractConnectionPool.java:208) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.DuplexConnectionPool.close(DuplexConnectionPool.java:237) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpDestination.close(HttpDestination.java:385) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.client.HttpClient.doStop(HttpClient.java:260) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.websocket.client.WebSocketClient.doStop(WebSocketClient.java:371) [bundleFile:9.4.20.v20190813]
at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [bundleFile:?]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$2.run(WebSocketConnection.java:184) [bundleFile:?]
at java.util.TimerThread.mainLoop(Timer.java:555) [?:1.8.0_252]
at java.util.TimerThread.run(Timer.java:505) [?:1.8.0_252]
So in my eyes it is not amazon RC_3 binding is not the cause! (Maybe a part of it!)
So far as I can understand the other thread, the underlying issue is a problem at the Amazon end.
But the openHAB end doesn’t handle it very gracefully.
Whether that has anything to do with your supposed “memory overflow” issue that I don’t think anyone else has reported, I woul not know.
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
17
Been running this version of the binding since it came out last year w/o issues. OH uses my 15 Echo’s quite a bit every day. It has over 629 downloads against the link.
Why are these lines:
"
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [bundleFile:?]
at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$2.run(WebSocketConnection.java:184) [bundleFile:?]
"
gone in the websocket Info message, when jar-file is deleted and system is rebootet?
As I understand correct the binding or what for hell is “OOM” is still active?
secound… until yesterday fine that it is allready discussed… until yesterday the system crash! That should bring a little more enthusiasm in solution or fixing process!
that´s why you follow the first link in the post:
" Please jump to the Preview and Beta: Amazon Echo Control Binding thread to get the latest features if you want do a beta test."
After cleaning the cache after deinstalltion of Amazon binding the Web socket error is gone…
Now i tried:
org.openhab.binding.amazonechocontrol_2.5.0.-2019-10-23.jar
as suposed by Mr Wiseman.
Same behavior: still web socket error … (Even after several reboots!)
So I think this is the source of the problem… which verion of the amazon binding is a fix for now? -remember after latest updates the system crashes because of web socket error by memory overflow!!!
Cheers
Stef
…I had the same problem.
It seems to be fixed with 2.5.7xx binding (2.5.6 was also NOK):
2.5.7.202006230342 │ openHAB Add-ons :: Bundles :: Amazon Echo Control Binding
Thanks to all for your effort.