No, in two cases, the tomcat configuration is identical. Only, I observe via
JMX as the manager is not correct. There is only the declaration of the XSD
in web.xml which changes.
server.xml : the first cluster
Server port=8005 shutdown=SHUTDOWN
Listener
2012/2/22 Lucas Pouzac lucas.pouzac@gmail.com:
No, in two cases, the tomcat configuration is identical. Only, I observe via
JMX as the manager is not correct. There is only the declaration of the XSD
in web.xml which changes.
server.xml : the first cluster
(...)
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 7.0.26
This release is primarily a bug fix release and includes numerous
bug fixes compared to version 7.0.25. The notable bug fixes include:
* Improved code@HandlesTypes/code processing which no longer loads
all
The worst offender (in my opinion) is
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html.
By the way, for the page in question, my HTML-checker lists 147 errors (not
warnings), the few first of which being :
line 59 column 5 - Error: end tag for element P which is not open
line 78
You have to balance that against the minimal cost of today's
memory (even ECC RAM is under $10 per GiB).
True, RAM is relatively cheap, but servers are not. We like to stack as
many instances of tomcat on a server as possible while maintaining good
performance. Some of our 8-core 32GB
All,
I have a deployment on Windows 2003 Server using Apache 2.2.16, Tomcat 5.5.30
and mod_jk 1.2.31. Apache and Tomcat reside on the same machine. The
communication is fine for days / weeks, but at some point all requests to the
server (to Apache) that use mod_jk return HTTP 503.
The error
Hi all,
I am having trouble using FORM based authentication against an LDAP server.
I have configured my web.xml and server.xml and created a Login.jsp
page and can can successfully authenticate against a simple
tomcat-users.xml file. Therefore I am confident my basic
configurations are okay
Ofer Israeli wrote:
All,
I have a deployment on Windows 2003 Server using Apache 2.2.16, Tomcat 5.5.30
and mod_jk 1.2.31. Apache and Tomcat reside on the same machine. The
communication is fine for days / weeks, but at some point all requests to the
server (to Apache) that use mod_jk return
I do know that I am successfully binding to the LDAP server when
Tomcat starts. If I change mypassword to an invalid password then I
get a ConnectException due to the connection being refused. I also see
this connection using a network monitoring tool - it is initiated at
startup and then
Hmm. Am I to understand this is fixed now? I tried it and it still seems
to have problems. However, the other versions ( 7.0) seem to be working
much better (I thought they too had problems when I tried in the past).
Also, I appreciate everyone jumping in quickly to fix this.
Jim
Hi,
The user I bind cannot check user's passwords but it can browse the
LDAP tree and see all the available users. I have used ldap.exe with
the same connection/bind and can traverse the LDAP tree.
As far as after the initial connection is made, no I don't see any
packets or new connections after
The user I bind cannot check user's passwords but it can browse the
LDAP tree and see all the available users. I have used ldap.exe with
the same connection/bind and can traverse the LDAP tree.
As far as after the initial connection is made, no I don't see any
packets or new connections
André Warnier wrote:
Ofer Israeli wrote:
All,
I have a deployment on Windows 2003 Server using Apache 2.2.16,
Tomcat 5.5.30 and mod_jk 1.2.31. Apache and Tomcat reside on the
same machine. The communication is fine for days / weeks, but at
some point all requests to the server (to Apache)
From: Ofer Israeli [mailto:of...@checkpoint.com]
Subject: RE: Tomcat with mod_jk becomes irresponsive after working for awhile
I am in the situation where the server is giving 503s for
all incoming requests, so I did a capture now to see what
the situation is and as mentioned above I see
From: Caldarale, Charles R
Subject: RE: Tomcat with mod_jk becomes irresponsive after working for awhile
You might want to take a thread dump of Tomcat and see just
what is going on.
Also look in the Tomcat logs (there are several) to see if errors are being
reported there.
- Chuck
I have been getting the ThreadLocal cleanup warning messages appearing in
the Tomcat log for some time now. I finally got around to investigating
these and cleaning it all up. Most of the ThreadLocals I removed, because
they were being abused. However, some needed to hang around, so I used them
We've been using parallel deployment for some time now with tomcat 7.0.25. For
the most part the parallel deployment is a really nice idea, particularly
because we don't have sessions serialised and clustered across all running
instances.
However, we've had mysterious problems for some time
17 matches
Mail list logo
