From: Craig L Russell <Craig.Russell_at_Sun.COM>
Date: Mon, 10 Jul 2006 12:11:48 -0700

Hi Joerg,

To help problem determination here, (without actually sending a
complete test case) can you please provide:

A description of the artificial home (what's artificial about it?)
The methods or technique used for transaction completion
The type of EntityManagerFactory
The transaction attributes of the business methods you call
The way you remove the entity
The way you acquire the EntityManager in the business methods

Thanks,

Craig

On Jul 10, 2006, at 8:33 AM, Joerg Lauer wrote:

> Hi,
>
> while running some performance tests I noticed that some entities
> weren't removed, when they were created in the same transaction.
>
> The entities were persisted, in another business method of another
> bean, and afterwards removed. (I was using a fake home interface,
> for this test)
>
> After the transaction finished, the removed entities were inserted
> into the database.
>
> If I skip the artificial home and persist and remove in the same
> method (or even call methods on the same bean) everything works okay.
>
> I'd like to know whether I'm making a fundamental mistake, or it's
> an issue in toplink or glassfish.
>
> I'm currently running Appserver 9, but glassfish v2 Build 08 showed
> the same problem, both using toplink and JavaDB.
>
> Regards
>
> Joerg Lauer

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell_at_sun.com
P.S. A good JDO? O, Gasp!