> > I believe I haven't seen the crashes since that time, but I'll watch > > this week to be sure. Since my Hackystat plugin is older, I'd suspect > > Jupiter more, but it is equally likely to be something else...we'll > > see. > > Is this Jupiter plug-in or Jupiter sensor plug-in? it is reported that > there was a case that Eclipse seems hang up 10 seconds on Eclipse > startup after Jupiter was installed. I guess it would be the server ping > problem to check the new version of the plugn-in (the thread is waiting > for the ping reponse so that it seems hanging up for a while, I > definately need to move the update checking funciton to another thread > so that users would be happy).
It's just Jupiter, not the Jupiter sensor. Server ping. Hmm. That's quite possible. Our Hackystat server's on a box with a ton of other stuff, and it sometimes takes forever to wake up. Server pings can be slow or never return. I also disabled the Jupiter auto-update since I frequently have connectivity problems to the update server, and it has to wait for the socket to timeout. I think pushing all off-box-communication (Hackystat data transmission, sensor update checks, etc.) for all three Eclipse plugins (Hackystat, Jupiter, Jupiter sensor) would be really appreciated. :-) Thanks. Tim
