I don’t know the exact reason behind this, it could be that WebSocket messages all have timestamps, and that these don’t specify a timezone for example. If so, it would be “the fault of the binding” or Jetty. The best thing to do would probably be to log all the traffic for a short while, and study timestamps and see if something “looks wrong”.
