I'm not sure if the following will cause this or not. I know I've read this post somewhere, though, and I believe it was written by Jorb.
Basically, Jorb (maybe Loftar) explains how the current certificate system is flawed and how it can be compromised. He also explains this is why SeaTribe doesn't have what is considered a "valid certificate". This means you have to create an exception in your web-based software for it or import the certificate as safe. I'll see if I can find where I read this and edit it in.
The "bug": Java is seeing this self-generated certificate (or lack of a certificate) and instead of just ignoring the exception, it is throwing an exception that isn't handled and is halting the program. It might be possible that a configuration setting is causing the program to just halt. I'm not entirely sure what, if anything, could be changed to fix it. Updating or completely removing and reinstalling Java likely would fix it, but that'd be like replacing the engine to fix the ignition in a car. (Of course, we're talking about time and not expense, so not a great analogy, but I like it anyway.

)
edit: in the middle of my search. I'm finding several possible causes for this other than the wrong system time. Reinstalling Java probably isn't going to help any.
edit2: ok, I'm not finding it right away. It was in a post about adding optionally adding a certificate so that anyone logging into the site doesn't have to go through that whole "invalid security" thing every time. Maybe someone else remembers what I'm trying to talk about. :/
Opinions expressed in this statement are the authors alone and in no way reflect on the game development values of the actual developers.