Hi,
If you feel that can be outofmemory problem, then you can monitor it
by running JVM with -verbosegc mode. For that you can wirte this otion in
jrun properties file in front of
java.args = -ms32m -mx64m
-verbosegc
Rcommended maximum meomory for JVM is half of your whole system primary
memory.
It will give the all statistics of your memory allocation on $ prompt
itself. I don't for see any problem with JRUN for concurrent requests.
bye
Kumar
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Anil Kumar Phone (Work) 732-389-3295x630
UnixPros Inc. (home) 732-935-1590
10 Industrial Way East
Eatontown, NJ 07724
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Every body have a right to say anything, But some stupid take it for granted
----Original Message-----
From: Lynn Walton [SMTP:[EMAIL PROTECTED]]
Sent: Monday, July 31, 2000 12:02 AM
To: [EMAIL PROTECTED]
Subject: Re: too many concurrent requests
Well, I'm getting this same error. I'm using Solaris2.8, Sun's
java1.2.2.05a and I have
-Xms64m -Xmx128m as an additional argument for the jvm settings for
the jrun server.
Has allaire confirmed that the Sun 1.2.2.05a is safe?
My log files don't give any info at all....
event log has: 07/30 23:32:28 info (license) Enabling unlimited
concurrency for Professional
error.log has nothing ... no out of memory error
This has happened when I'm the only one running it and I haven't
made hardly any requests?
While I know it could be apps, the apps are the same that have been
running fine on Jrun
2.3.3.
I'm supposed to go live in one more week with Jrun3 and now this has
me scared.
Anyone who has had this problem find anything that might help me?
I've noticed quite a few
people
posting about it. Also, would be nice if the Knowledge Base talked
about what to do for
Jrun 3 for this error.
I read the 2.3.3 Faq, but didn't think those things applied.
Lynn
Scott Stirling wrote:
> JRun isn't the problem. Either you have too little memory
allocated to the JVM
> for your application, or there's something else causing you to run
out of memory
> when you shouldn't. You neglected to mention one of the most
important parts of
> your configuration, which usually makes me suspect that a user
hasn't realized
> its significance. What JVM are you using?
>
> You probably have some data in your log files that relates to this
> OutOfMemoryError. That's important. It's tough to debug a problem
with just the
> name of the exception/error to go on.
>
> Scott Stirling
>
> -----Original Message-----
> From: Juan Cabrera [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 21, 2000 3:28 PM
> To: [EMAIL PROTECTED]
> Subject: too many concurrent requests
>
> the following message appears on the site, also a message of too
many
> concurrent request is reported.
>
> 500 Internal Server Error
> com.livesoftware.jsp.JSPServlet:
>
> java.lang.OutOfMemoryError
>
> The site is running on a Compaq DS40 with With Digital True 64 ,
Apache
> 1.3.4 and JRun Pro 2.3.3.
> i 've check the license and is ok in the log file (enabling
concurrency
> message).
> any help please. Thanks
>
>
----------------------------------------------------------------------------
--
> Archives: http://www.egroups.com/group/jrun-interest/
> Unsubscribe:
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
> or send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body.
----------------------------------------------------------------------------
--
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe:
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
