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.
