If you search the mail archive for 'Admin Memory' you will find
references to the ApplicationAdministator which can be used
to flush the cache. I believe this was a work-around.
I'm currently running my batchupdates with the earlier proposed
workaround:
>import com.evermind.server.administration.*;
><snip>
>Context context = new InitialContext();
>Object o = context.lookup("java:comp/Administrator");
>ApplicationAdministrator admin =
>(ApplicationAdministrator)javax.rmi.PortableRemoteObject.narrow(obj,
>ApplicationAdministrator.class);
><snip>
>admin.flushEJBCache("name of your entity-bean");
><snip>
>
>This works perfectly. Only 1 entity bean instance gets created. CPU
>usage wich earlier was at 100% corrently stays around 53% and
>significantly less memory is used.
>
>sven
Cheers,
Brett
