On Wed, Oct 29, 2008 at 10:54 PM, Jusa Saari <[EMAIL PROTECTED]> wrote: > On Tue, 28 Oct 2008 14:16:15 +0000, Matthew Toseland wrote: > >> On Tuesday 28 October 2008 10:32, Jusa Saari wrote: >>> [quoted text muted] >> >> I didn't say reinstall, I said run the update script. >> >> What exactly is it that happens? The linux install script doesn't set >> update.sh/update.cmd as executable? You try to reinstall over an existing >> installation and it fails? What? > > I tried a clean install and it failed, due to none of the .sh files > getting their execute bit set, after which the installer complained that > the JVM is buggy and recommended using Sun's JVM, except that I already > was (1.6.0_05, since then I've updated to _10). > >>> [quoted text muted] >> >> It sucks, but the problem is probably in the wrapper's code, and would >> likely take a long time to fix ... if it's not a widespread problem, it's >> better to ignore it, and fix whatever is causing the JVM to hang in the >> first place. >> >> Please file bugs on the bug tracker for your bugs, and include enough >> detail! > > I'm investigating the wrapper issue myself for now. There was also some > complains in wrapper.log about the version of the wrapper's JAR file > (which doesn't seem to exist, BTW), so I got the latest version from > tanukisoftware.com and am now seeing if the problem goes away, or if I at > least can figure out what is happening.
This is expected. nextgen have updated the java part of the wrapper, but not the native binaries. > And it doesn't necessarily take a JVM hang to cause this effect; > hibernating the machine for night also causes the wrapper to restart the > JVM as soon as the machine resumes. > _______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
