I can only shed a tiny little bit of light on some of these errors but not a whole lot.
Over all, what I’ve observed is sometimes it takes a little longer than expected to install all the bindings but OH forges ahead in starting up meaning that stuff starts running before OH is read. I usually see this as “no handler for application/javascript” and the like.
I don’t know what a “weaving” is but this appears to come from the JS Scripting add-on or, perhaps a problem caused by the add-on not yet being fully installed.
This looks to be related to the previous exception. The first OH class in the stack is org.openhab.automation.jsscripting.internal.scriptengine.DelegatingScriptEngineWithInvocableAndCompilableAndAutocloseable.eval(DelegatingScriptEngineWithInvocableAndCompilableAndAutocloseable.java:54) ~[?:?]
Something that Jetty, the internal web server, depends upon is not yet there.
I would guess this is related to the previous.
These are normal and usually seen when you have an instance of MainUI up and connected to OH during an OH restart.
This one is again coming from the JS Scripting add-on, only this time it’s related to a transformation instead of a rule.
This too comes from the JS Scripting add-on.
In short, I think your errors only show two problems.
- Jetty came up in an error state or otherwise didn’t fully come up. Or at least it only partially came up.
- JS Scripting didn’t fully come online or only partially came online.
What ever caused the problems resolved on the restart.