Hi Brett,
In first place are using any tool provided by Orion like earassembler.jar or
ejb-assembler.jar?
If you are using it, these kind of problem will persist, this is what I have
experienced. It keeps the Beans in cache, and any changes done to these will
throw you OutOfMemoery error.
U can solve this problem by two ways:
1) U can open the ear.jar, the zip file through winzip(unzip/zip tool)
(don't extract), replace the files need to be changed and close. Initialize
Orion, changeswill be taken w/o throwing the error.
2) Spend some time building the Build.xml, and runthe ant.bat. This will
build a new ear each time u run ant.
Both of the solutions r tested solutions, and works fine.
the 2nd solution is universal, and a better solution.
Suresh Ajja
Java Developer
www.verchaska.com
mailto: [EMAIL PROTECTED]
----- Original Message -----
From: "Brett Lane" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Thursday, January 25, 2001 4:37 AM
Subject: Re: java.lang.OutOfMemoryError in Product Application
> 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
>
>
