2009/3/5 Niclas Hedhman <[email protected]> > On Thu, Mar 5, 2009 at 4:12 PM, Stuart McCulloch <[email protected]> > wrote: > > 2009/3/5 Niclas Hedhman <[email protected]> > > > things I'd check: > > > > * version and path of java > > * local java preferences / policy files > > * firewall settings (just in case) > > Well, look at the Exception. A class "under test" can not be located > by the RegistryImpl, which runs in the same JVM... There is only a > single classpath for that JVM, and shouldn't then it always be found? > I mean, "firewall settings" --> are you serious? The network > connection between the classes in the same JVM works, otherwise the > ServerException would not show in the calling code (which it does). >
the #1 lesson I learned debugging problems is _never_ assume anything ( which is why I tagged that as "just in case" ) from painful experience I've found it saves a lot of time to check these sort of settings (ie. even unlikely ones) because checking them is cheap and a bad assumption is expensive case in point, I helped with an upgrade of a web-server at a major bank a few years ago... we upgraded and ran the tests: fail, so we rolled back the upgrade and re-tested: fail! The customer was going crazy claiming our update had hosed his system, wanted us to check every setting and file turned out one of the NICs had happened to fail around the same time as we did the update (which took a while for various reasons) - swapped in a new piece of hardware and everything was back to normal! > > > you could also turn on RMI debugging: > > > > http://java.sun.com/j2se/1.5.0/docs/guide/rmi/sunrmiproperties.html > > I will. Thanks. > > Cheers > Niclas > -- > http://www.qi4j.org - New Energy for Java > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Cheers, Stuart
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
