Any indication of when 1.4.6 will be out & whether it will solve the bug regarding
passivation?
Anybody have a workaround for the problem? Or should we deploy with someone else
then?
We have Orion in at the pilot site & allmost went live. Now we struggle & get on top
of that we get no replies when mailing Orion-support directly.
Regards
Jaco van Rooijen
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jens Stutte
Sent: 01 February 2001 15:02
To: Orion-Interest
Subject: AW: Out Of Memory Problem / Passivation Error
They said, that there is a limit in the new 1.4.6 version, but unfortunately
it's not avaliable yet, it seems. We are struggeling heavily with the same
Problem here.
Regards,
Jens Stutte
> -----Ursprüngliche Nachricht-----
> Von: Jaco van Rooijen [mailto:[EMAIL PROTECTED]]
> Gesendet am: Donnerstag, 1. Februar 2001 12:35
> An: Orion-Interest
> Betreff: Out Of Memory Problem / Passivation Error
>
> Hi
>
> We urgently need a solution to the following problem:
>
> We get java.lang.OutOfMemoryErrors with our application. We
> increased the
> amount of allocated memory to the heap, with the result that
> the application
> just took a bit longer to run out of memory.
>
> We then ran a test program that creates a simple entity bean
> in an infinite
> loop and then releases the reference of this entity bean. It
> turns out that
> even though memory seems to be running out, orion does not
> passivate the
> beans that are not being used anymore. Is this correct
> behavior? Shouldn't
> unused active beans be passivated at some point?
>
> Is it possible to limit the pool size of an entity bean?
>
> We are using JDK 1.3 and OrionServer 1.4.5.
>
> Thanks
> Jaco
>
>
