Glad to hear you are safe, Peter. I'll try the new Glassfish 3.1 final release with MySQL and see if I can reproduce this problem.
- Dave On Fri, Mar 11, 2011 at 10:52 AM, Peter Evans <[email protected]> wrote: > On Wed, Mar 9, 2011 at 5:07 AM, Peter Evans <[email protected]> wrote: >> >> Tried to turn on planet aggregator, it complained about the cache.dir >> (which >> is NOT as the document says) > > What is the problem here? Does the Install Guide use the wrong name > for the "cache.dir" property? > > You're missing the continuous aftershocks here in Tokyo. > > The manual says the default is one thing, the error was: > > rollerdata/roller.log:ERROR 2011-03-09 18:21:00,195 > RomeFeedFetcher:getRomeFetcherCache - Planet cache directory is not > writable: /var/planet/cache > > Which is nothing like the manual's statement. > >> After that, whatever it did was fatal. > >> etc, etc, lots of USELESS traceback that does not actually tell me what I >> did wrong. > > > That's a pretty mysterious error there, RuntimeConfigProperty cannot > be cast to RuntimeConfigProperty. What platform are you running on? > Operating system, Java version, App server, etc. > > solaris express 11, glassfish 3.1, RC4. mysql 5.1.37 (Is that the one with > the left outer join issue??) > > astaria 142> java -version > java version "1.6.0_21" > Java(TM) SE Runtime Environment (build 1.6.0_21-b06) > Java HotSpot(TM) Server VM (build 17.0-b16, mixed mode) > > appears to be from: > developer/java/jdk 0.5.11-0.151.0.1 nstalled > ----- > developer/java/jdk64 0.5.11-0.151.0.1 nstalled > ----- > runtime/java 0.5.11-0.151.0.1 nstalled > ----- > runtime/java/runtime64 0.5.11-0.151.0.1 nstalled > ----- > > > glassfish is running as a regular user on port 8080 with no fancy > privileges, it shouldn't need them. > > Do you have two copies of the Roller jars in your WEB-INF/lib > directory? That could cause this problem. > > Not that I can see. I told glassfish to deploy from another directory > altogether. > redeploy also causes the same disaster, almost as if something it put in > the database > is breaking it. (I can test that I guess, I have a backup of whatever is > in now.) > > P >
