Just wondering but are you allocating any of that GB to orion or are you
letting the box allocate the memory itself?
I think that the box gives a default amount of memory to java and so that
could be the reason you are running out of memory
You can allocate by giving param setting on the startup
Be sure of cleaning all your ejbs when you remove them. Set all
attributes and global variables to null. We have had a very similar
problem, and this was one of the reasons.
mars wrote:
Dear orion user :
I got a problem I have a Orion Appcation Server Run on Linux
run the http service
The amount of memory in the box won't make much difference if the VM is not
configured to use it...It's default settings are rather low, you'll need to
check the startup script to see how much stack space it's putting
aside...this is also related to performance issues as the VM will take
longer
You are probably running the server on the jdk JVM which is VERY limited
on memory. You can up it with a -Xmx param when you are firing it up
from the command line but most likely you need to use the JRE.
Try changing your path to be /usr/opt/java122/jre/bin rather than
/usr/opt/java122/bin.
, and the second
one could be something like total memory.
- Original Message -
From: Puthezhath, Rajeev (TWII Boston) [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Friday, June 08, 2001 11:28 PM
Subject: RE: java.lang.OutOfMemoryError;
Sorry.I didnt get what you meant.could
inline
-Original Message-
From: Puthezhath, Rajeev (TWII Boston) [mailto:[EMAIL PROTECTED]]
Sent: Viernes, 08 de Junio de 2001 14:42
To: Orion-Interest
Subject: java.lang.OutOfMemoryError;
Hi ,
We get java.lang.OutOfMemoryError; on production server
frequetly.I
Sorry.I didnt get what you meant.could you please explain
Thanks
Rajeev
-Original Message-
From: Juan Lorandi (Chile) [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 4:26 PM
To: Orion-Interest
Subject: RE: java.lang.OutOfMemoryError;
inline
-Original Message-
From
We found we could force passivation in the later orion
builds - not sure exactly whch builds it works in, but
its OK in 1.4.7.
Create a directory called orion in the root of your ejb jar
(i.e. as a sibling of your META-INF directory).
In the orion folder, create a file orion-ejb-jar.xml
(The
This is beacause Orion doesn't free unused beans
you need to use the inactivity-timeout attribute in the orion-ejb-jar.xml
file
it serves to free unused beans :
entity-deployment ... validity-timeout=2000 ...
H.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
When I looked at your client, I found that you have a loop that creates
100,000 instances of the EJB and have never free any. Thus, your client now
has 100,000 EJB's that will not be passivated until you leave the for loop.
This type of code will break most app servers.
SnowWolf Wagner
This is a known bug. A workaround was posted a while back. I have since
moved to another company and dont have an installation of orion here so
Im going from memory here. there should be some class in the orion API
like com.evermind.Administrator which has a function flush() (static I
As per the suggestion, I am doing the following in an
attempt to flush the cache after every 10,000 object
creation. Watching the "free memory", simultaneously,
I was expecting this free memory-count to jump up
every 10,000 objects - but, I am not seeing that. The
"free memory" count
Hi Suresh,
I am not having any problems, I was replying to someone else who was
having
an out of memory problem. I have not encountered any out of memory problems
but
I remembered sven posting something some time ago on the
ApplicationAdministator, which
i had saved, so I reposted it.
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
Could it be that Orion does not passivate entity
beans, thus running out of virtual memory? I was able
to restart the ProductClient and continue adding to
the table.
Does anybody know of a solution better than having to
stop and restart?
Thanks
--- Globetrot Communications [EMAIL PROTECTED]
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 t
16 matches
Mail list logo