8.1.6 + EJB = crash

Simple..
I can deploy EJB's just fine (1.0 that is, waiting with patience for 8.1.7), and they're working just great too.. except for perfomance, wich according to my test, show to be a factor 7 slower than my previous JDBC architecture, however That may change when the number of users grow, Oracle claims their JVM will excell under these circumstances.. The tricky part is, if I close my client somehwere between a lookup and create, i can trash the bean on Oracle, litteraly destroy it. Succesive call to it gives a marshallexception, and some 'error reading object'.. Then i reboot the system bearing oracle 8.1.6 but the bean is still trashed!!! the only way to get it working again is to redeploy the bean.

Now im thinking.. hmm.. suppose my users are going to 'accidently' close the client program like i have tried, the whole damn thing is going down.

Anyone with similar experiences ? It doesnt seem very robust to me, am i not doing this right ?

Any pointers would be nice.

Thank you. Received on Wed Nov 22 2000 - 00:48:06 CST