cause a clean shutdown for InstantDB, but doesn't. I still have
to answer 'yes' to the fix up question. There is a property that
I could set, something along the lines of 'automatically fix up' but
I haven't pursed it's where-abouts.
Roland Kamsika wrote:
I am having the same problem. Did you find a solution to this?
Regards,
Roland Kamsika <mailto:[EMAIL PROTECTED]>
> -----Original Message-----
> From: Rich Johns [mailto:[EMAIL PROTECTED]]
> Sent: 02 May 2000 14:54
> To: [EMAIL PROTECTED]
> Subject: InstantDB not terminating cleanly
>
>
> nt4.0
> jonas2.0
>
> In running the eb.ClientAccount example I'm using InstantDB.
> It works fine. I shut EJBServer down using JonasAdmin (stop) in
> interactive
> mode. All seems fine. Later, I run EJBServer again, and when I run
> eb.ClientAccount the EJBServer reports that InstantDB is in a
> bad state
> and offers to fix it, which it does. But, it seems that there is a bug
> someplace
> where the EJBServer is not communicating a shutdown to InstantDB.
>
> Is this the missing ejbPassivate() logic? Given this example, who's
> responsible for
> releasing InstantDB? I'm using the AccountImplHome which is container
> managed so perhaps it is the container's responsibility?
>
