Hello,
thank you all for your answers!
Because of this and some other problems, I decided to switch the
provider and I have now an other machine running an 32bit OS.
Using the same default settings as on the other two machines, tomcat is
now running very fine. I don't know the reason, but I
Well, the log messages you see, are all based on timeouts.
If your system has a load average of 12, unless you have a 12-way
machine, that is very high, and could be the cause of your timeouts.
You will need to figure out what is causing the high load average.
Filip
On 12/18/2009 01:30 AM,
Hi.
Bill, Mark,
I have more patches to submit for LocalStrings_fr.properties files, in
the various sub-directories of Tomcat6.
I also have a couple of new ones, for sub-dirs where no French version
existed.
Do I keep submitting this on Bugzilla, one by one ?
Or is there some better way ?
Hello,
I've always spoke of a servlet as a female name. Think about an applet, for
instance. But that's only my opinion.
Regards,
Pierre
On Sun, Dec 20, 2009 at 3:02 PM, André Warnier a...@ice-sa.com wrote:
Hi.
Bill, Mark,
I have more patches to submit for LocalStrings_fr.properties
Pierre Goupil wrote:
Hello,
I've always spoke of a servlet as a female name. Think about an applet, for
instance. But that's only my opinion.
Opinions is what this is all about.
So, what about a first round of informal voting ?
le servlet est initialisé ? y/n
la servlet est initialisée ? y/n
Mark Thomas wrote:
On 19/12/2009 10:45, André Warnier wrote:
...
To get back to the main issue, as long as I anway get the hang of this
stuff, and have checked out the SVN of Tomcat anyway,
where in the /valves stuff do I find where it actually checks the
remote IP against which
On 20/12/2009 14:02, André Warnier wrote:
Hi.
Bill, Mark,
I have more patches to submit for LocalStrings_fr.properties files, in
the various sub-directories of Tomcat6.
I also have a couple of new ones, for sub-dirs where no French version
existed.
Do I keep submitting this on
On 20/12/2009 16:04, André Warnier wrote:
In other words : it seems that quite early in the request process, a
decision is taken to *replace* the remote IP address as obtained from
the socket, by the ultimate IP of the client for which this proxy
request is being processed. This casts a doubt
Mark Thomas wrote:
...
This is one of those times where the solution will depend on the
protocol you are using.
The AJP connectors will report the client's IP address so you need an
alternative solution. Using the request.secret attribute is probably
the simplest fix although keep in mind that
Mark Thomas wrote:
...
If I recall correctly you are using Tortoise SVN. If you generate the
patch from the root of the svn checkout, you will get all of the patches
in a single file. You can then attach that to a new bugzilla entry.
You do recall correctly, and it did generate a single patch
On 20.12.2009 21:00, André Warnier wrote:
Mark Thomas wrote:
...
This is one of those times where the solution will depend on the
protocol you are using.
The AJP connectors will report the client's IP address so you need an
alternative solution. Using the request.secret attribute is probably
On 20.12.2009 21:24, André Warnier wrote:
Mark Thomas wrote:
...
If I recall correctly you are using Tortoise SVN. If you generate the
patch from the root of the svn checkout, you will get all of the patches
in a single file. You can then attach that to a new bugzilla entry.
You do recall
I have just upgraded my Debian server to unstable, and now find that
attempt to connect to my tomcat via ajp fails.
It appears from netstat is tomcat is listing on 8009 but only on ipv6
I have been unable to find out how to change this. Can someone give me
a clue.
--
Alan Chandler
Alan Chandler wrote:
I have just upgraded my Debian server to unstable, and now find that
attempt to connect to my tomcat via ajp fails.
It appears from netstat is tomcat is listing on 8009 but only on ipv6
I have been unable to find out how to change this. Can someone give me
a clue.
As
Rainer Jung wrote:
...
They might not have existed at the time the original translation was
done (or the original author is still thinking about the right french
servlet grammar ...).
Der, die oder das servlet ? oder Servlet ?
;-)
Mark Thomas wrote:
And for everyone else, Tomcat currently has partial translations for
German, Spanish and Japanese. Contributions to extend or correct those
translations - or to add completely new translations - are always
welcome. If you have the language skills but aren't sure how to get
André Warnier wrote:
Alan Chandler wrote:
I have just upgraded my Debian server to unstable, and now find that
attempt to connect to my tomcat via ajp fails.
It appears from netstat is tomcat is listing on 8009 but only on ipv6
I have been unable to find out how to change this. Can someone
When I run embedded Tomcat my jsps 404, but my servlets work.
When I run standard (by putting my war on the Tomcat/webapps directory) my
servlets 404 but my jsps work (without any css).
Can anyone shed some light on this?
My startup script for embedded is here: http://gist.github.com/259737
Oh, and no errors in the logs.
On 12/20/09 8:32 PM, Clay McCoy cmc...@acteksoft.com wrote:
When I run embedded Tomcat my jsps 404, but my servlets work.
When I run standard (by putting my war on the Tomcat/webapps directory) my
servlets 404 but my jsps work (without any css).
Can anyone shed
2009/12/21 Clay McCoy cmc...@acteksoft.com:
When I run embedded Tomcat my jsps 404, but my servlets work.
I guess that you do not have the Jsp servlet configured. See conf/web.xml.
-
To unsubscribe, e-mail:
Mark Thomas ma...@apache.org wrote in message
news:4b2e4e77.3000...@apache.org...
On 20/12/2009 16:04, André Warnier wrote:
In other words : it seems that quite early in the request process, a
decision is taken to *replace* the remote IP address as obtained from
the socket, by the ultimate
Thank you, this got me closer. I have two questions:
1) My current web.xml didn't configure the jsp servlet. I haven't had do
configure that for a number of other containers. I don't understand why I had
to do this specifically for Tomcat. It also seems bizarre that the jsps worked
Apparently Groovy 1.7 rc2 uses an outdated jsp api (2.0) and Tomcat 6 uses 2.1
This conflict was causing me problems. Of all the libraries, I was very
surprised to see the conflict between the latest Tomcat and Groovy.
Things still aren't right, but I don't know how to report what I am seeing
2009/12/21 Clay McCoy cmc...@acteksoft.com:
Thank you, this got me closer. I have two questions:
1) My current web.xml didn't configure the jsp servlet. I haven't had do
configure that for a number of other containers. I don't understand why I
had to do this specifically for Tomcat.
24 matches
Mail list logo
