Tomcat 4.1 and LD_ASSUME_KERNEL=2.4.1

[Steven Peterson]

Hi all,
I am having problem where Tomcat 4.1.27 just stops after some random 
period of time.  I am on RH9 and JDK 1.4.2.  This seems to be the same 
problem reported earlier and a recommended fix was to set an environment 
variable LD_ASSUME_KERNEL=2.4.1.  Can I simply put an export 
LD_ASSUME_KERNEL=2.4.1 in my setenv.sh file?

Also, I have heard other recommended values, such as 
LD_ASSUME_KERNEL=2.2.5; how would I find out which one to use?

- Steve
Hello.
Is this the same problem I also asked yesterday about in thread
All threads are busy ... servlet status 75
Somewhere I read about setting the LD_ASSUME_KERNEL to 2.2.5
But I also read somewhere that this didn't help
(www.junlu.com/msg/14450.html)
QM wrote:

 On Thu, Jun 17, 2004 at 03:54:08PM -0400, Bradley Glonka wrote:
 : Tomcat installaion on Red Hat Version 9 intermitnently stops
 : Responding.
 :Kernel 2.4.20-9

 RedHat's custom kernels have backported the NPTL (Native Posix Thread
 Library) routines from 2.5/2.6.  Set the env var LD_KERNEL_ASSUME to
 2.4 to make non-NPTL code (such as your JDK) behave.

 That var may also be called LD_ASSUME_KERNEL, I forget which. ;)

 : Can someone suggest how I can troubleshoot the problem.

 Other than the above: are there differences between the development env
 and production env, other than the OS?  Differences in RAM or JVM heap
 settings can cause different GC behavior between the two.

 Furthermore, what sort of load-testing was done on the app before it
 went live?

 -QM

 --

--
Steven Peterson, President
Frontier Productions, Inc.
310 Wesley Drive
Chapel Hill, NC 27516
Tel: 919-942-1386
Fax: 919-933-2677
Creators of List Pilot
Easier email broadcasting to your many different customers
http://www.listpilot.net

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to see JSP error messages while tomcat is running

[Steven Peterson]

I recently upgraded from tomcat 3 to tomcat 4.1.12 and am having trouble
debugging new jsp pages as I add them.  Whereas tomcat 3 would send the
error output of a jsp to the html page (making it easy to identify the
problem, fix it, and test it again), tomcat 4 sends the output to the
context's log file.  This would not be so bad, but the log file is
locked by my operating system (Windows 98 se) until tomcat is shutdown.
The upshot is that for every error, I have to shut down tomcat to see
what the error was.  Is there any way to see the error output of a jsp
page without shutting down tomcat either by a) having the output sent to
the html stream; or b) having the log file accessible while tomcat is
running; or c) . . . ?

Thanks,

- Steve Peterson

--
Steven Peterson, President
Frontier Productions, Inc.
310 Wesley Drive
Chapel Hill, NC 27516
http://www.frontierproductions.net
Tel: 919-942-1386
Fax: 919-933-2677



--
To unsubscribe, e-mail:   mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org