I just updated from the CVS last night
and got the same thing.
Sun Jdk 1.3 on Mandrake Linux 7.2
> -----Original Message-----
> From: Jonaki Ray [mailto:JRay@gw.libofmich.lib.mi.us]
> Sent: Tuesday, April 03, 2001 9:46 AM
> To: ozone-users@ozone-db.org; falko@smb-tec.com
> Subject: Re: revisiting the vanishing user (in Windows)
>
>
> Hi,
>
> I made the changes in the required files by checking the cvs
> repository on the web. But now, I have a problem while
> starting the server.
> This is what I see (on the server side):
> ..the usual stuff ..
> [info] (499) Env: checking memory...
> [info] (499) Env: total: 64749568
> [info] (499) Env: free : 64582000
> [info] (499) Env: keep : 4000000
> [info] (499) KeyGenerator: startup...
> [info] (499) ClassManager: startup...
> [info] (499) UserManager: startup...
> [info] (499) UserManager: No state properties found. Initializing...
> [info] (499) UserManager: admin user: jray
> [info] (499) TransactionManager: startup...
> [info] (499) WizardStore: startup...
> [info] (499) WizardStore: checking for pending shadow clusters...
> [info] (499) WizardStore: error while starting up...
> [info] (499) WizardStore: recovering...
> [info] (499) WizardStore: cleaning ID table...
> [info] (499) WizardStore: cleaning name table...
> [info] (499) WizardStore: 0 IDs, 0 name(s))
> [info] (499) AdminManager: startup...
> [info] (499) AdminManager: No admin object found. Initializing...
> [info] (499) ClusterStore: loadCluster(): load cluster from disk: 101
> [info] (499) AdminManager: Admin object created.
> [info] (499) Server: Shutdown hook successfully added.
> [info] (499) Env: User jray already exists.
> [info] (499) Env: shutdown...
> [info] (499) TransactionManager: shutdown...
> [info] (499) TransactionManager: there are 0 pending
> transaction(s)
> [info] (499) TransactionManager: acquire count total:2
> [info] (499) WizardStore: shutdown...
> [info] (499) IDTable: Statistics:
> [info] (499) IDTable: sub-table accesses: 2 hits: 2 loads: 0
> [info] (499) IDTable: cache accesses: 1 hits: 0
> [info] (499) UserManager: shutdown...
> [info] (499) ClassManager: shutdown...
> [info] (499) KeyGenerator: shutdown...
> [error](499) (null): Env.shutdown():
> java.lang.ClassCastException: org.ozoneDB.c
> ore.TransactionManager
> java.lang.ClassCastException: org.ozoneDB.core.TransactionManager
> at org.ozoneDB.core.Env.storeSetup(Env.java:368)
> at org.ozoneDB.core.Env.shutdown(Env.java:280)
> at org.ozoneDB.core.Server.main(Server.java:181)
>
> I am working on Windows 2000 using ozone-0.6.1.
>
> I don't understand why it is printing shutdown in the first
> place and of course have no idea about this error.
> Any help would be greatly appreciated - thanks!
>
> Jonaki
>
> >>> falko@smb-tec.com 04/01/01 02:42PM >>>
> On Sun, 01 Apr 2001, Falko Braeutigam wrote:
> > On Sun, 01 Apr 2001, Reason wrote:
> > > On creating a database in Windows, a user is
> automatically created with the
> > > current account user name (I assume from
> System.getProperty("user.name") --
> > > can't think of anywhere else it'd be coming from). This
> user works just
> > > fine. You can shut down the database server and restart
> it on the same
> > > database and the user is still there.
> > >
> > > However, if you shut down the ozone server and then
> reboot the machine, the
> > > user is no longer in evidence the next time the ozone
> server is started for
> > > that database. This is somewhat interesting.
> > >
> > > I've scanned over code in *Database.java and
> UserManager.java but can't see
> > > anything immediately out of place. Any insight from those
> who know the code
> > > better than I do?
> >
> > This is a bug. I'm half way done (hopefully) to fix this.
>
> I had to rewrite the entire server but it seems that I
> managed to fix this ;)
> It's in CVS. Please check this.
>
>
> Falko
> --
> ______________________________________________________________________
> Falko Braeutigam
> mailto:falko@smb-tec.com
> SMB GmbH
> http://www.smb-tec.com
>
>