Hi everyone,
I have just finally diagnosed a problem that initially looks like a Tomcat
problem but turns out to the an OS misconfiguration. The problem is that
doing a Google search comes up with a lot of fixes that imply it is a Tomcat
problem but it actually isn't it just uses the same error
Thanks Chuck! Update now in FAQ under Linux/Unix.
Bill
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: May 12, 2011 2:24 PM
To: Tomcat Users List
Subject: RE: Is there a method to submit a useful tidbit of knowledge?
From: Bill Miller
Both formats are perfectly valid, the only difference is how you're looking up
the logger in your code.
To use log4j.logger.de.simplicit.vjdbc=DEBUG, A1, your code would be calling
the lookup with de.simplicit.vjdbc.
To use log4j.logger.vjdbc=DEBUG, A1, your code would be calling the lookup
Using a filter would insert the entry point of the Servlet into an entire path
with the option of allowing/not allowing it to continue down the call chain.
--FilterA-FilterB-RealServlet
|
+-SomethingInteresting
FilterA will have the ability to examine the request and pass it to some
If you want to work with threads in tomcat you need to know about the Tomcat
org.apache.catalina.LifecycleListener interface. If you implement the interface
and register your
class within server.xml your class will be notified of Tomcat life cycle events
(Start, Stop,
etc...). You can then do
It's also possible that there were no more iNodes available for that directory.
It will give false volume full type of errors when it's actually just too
many files/folders within a directory.
(This used to happen a LOT in the ancient DOS days in the root directory... max
file count=255!!)
Enlighten me: what is the reason that this is common practice?
The most obvious reason for having HTTP server in front of an Application
Server (Tomcat) is that there are many things that you can do at/in the HTTP
server that you don't have available to you inside Tomcat. Things like:
-Caching
Have a good look at the /etc/hosts.conf file, it needs to contain something
like order hosts, bind
(AIX=netsvc.conf). If that is misconfigured then you will have exactly the
problems you're
describing. I found this exact behaviour on an AIX system that was
misconfigured. Keep working on
the
The problem is undoubtedly your .dll or .so is not in the correct directory.
Normally you need to
place those files in /tomcat but that assumes that /tomcat is your current
directory when you
startup. Essentially you need to ensure that you are starting tomcat from the
base directory that
also
The problem is obviously that the thread within the Timer needs time to
properly shutdown, the
non-obvious part is how long does it need, and how do you detect it's done?.
Normally you would do
a Thread.join() to ensure a thread has stopped before continuing, but as you
mentioned before you
paths that may
not be correct in
100% of situations are the path to problems.
Bill
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: July 12, 2011 2:27 PM
To: Tomcat Users List
Subject: Re: JNA class path with tomcat
Bill Miller wrote:
The problem is undoubtedly
I'd like to add a little bit specifically around setting the parameters for a
Windows service.
It can be done, but as Chris pointed out, it's not easy. There are at least 2
ways I can think of off the top of my head to change the Windows service
properties:
1. Write JNI code to call the
I agree; we have reproducible instances where PermGen is not set to our
requirements on the Tomcat startup parameters and it will cause a lockup
every time. Do some JMX monitoring and you may discover a memory spike
that's killing Tomcat.
Bill
-Original Message-
From: Jeff MAURY
Do you have the ability to have multiple client-server connections open? You
could have a second channel to the server that can communicate the status to
the client and when/if there is a problem indicate through that status channel
that the download has been truncated. Not the greatest idea
14 matches
Mail list logo
