Hehe. Is that true? :-)
Sounds like a bug in the JVM or Window's socket handling :-)
It is using the system clock to detect idle connections and doesn't notice
you changed it.
But seriously, my question is whether it is a configuration issue. If so, I can just change some uil2 params. But judging from your reply, this is more of an UIL2 impl issue because it is using absolute time from the system to detect idle connections vs using relative times.
So I guess the way to work around this "implementation feature" of UIL2 is to just add an exception listener and reconnect and reestablish all my publishers and listeners, right?
I am having the same error.
Did you manage to fix it ?
Any solutions/tips/hints ?
Maybe you shouldn't change your system time in Windows?