Russ Kepler wrote on 11/08/2012 09:22:41 AM:
> From: Russ Kepler
> To: Tomcat Users List ,
> Date: 11/08/2012 09:23 AM
> Subject: Re: This is just plain ... odd.
>
> On Thursday, November 08, 2012 01:35:55 PM Lyallex wrote:
> > I have tried everything I can think of to reproduce this behaviou
I'm just starting to work with the new Tomcat class in Tomcat7, but
immediately ran into an apparent limitation of only having a single port.
What options exist for those who need to embed Tomcat 7, but also
configure multiple ports, IP addresses and connector types (HTTP and/or
AJP)?
André Warnier wrote on 08/27/2010 12:32:43 PM:
> Ken Bowen wrote:
> > If you wanted to go down this path, besides the web page for entering
> > the password, you could add sending alerts to the cells of all your
> > sysadmins to improve the probability of the password being entered in
a
> > time
I think Baba wants an acceptCount of 250, but he would like to prevent
certain "rejectable" requests from tying up slots in that acceptCount, so
that it only holds "non-rejectable" requests. Unfortunately, since Tomcat
knows nothing about the requests in the accept queue, it appears the only
w
One cautionary observation about the use of shared SimpleDateFormat
instances: they are not threadsafe.
While it seems like a good idea to create these for various formats and
hold them as class static or instance members, you need to do something to
prevent threading issues.
I have run into p
There may be better ways, but one approach which occurs to me is to set
unique jvmRoute values on the engines in the server.xml. Even though you
aren't using mod_jk, this will result in the provided values being
appended to the sessionid. Assuming that you are establishing sessions,
and that
However, even then, you may find that the requests are not as asynchronous
as you'd like. If the two HTTP requests underlying the AJAX requests
happen to be sent over the same HTTP connection, then the HTTP protocol
dictates that the responses must be returned in the same order, i.e. the
respo
This is not really a Tomcat question, but a matter of Java language
understanding.
Comparators like ==, >, <=, etc. should only be used with java language
primitive types, such as int, byte, boolean, and NOT with Objects, like
String, as you are, UNLESS you actually wish to test whether the two
> queryString : ?id=2345
> id : 2226
One thought that comes to mind is if you are getting the "id" parameter
from the request, but assigning it to a member, or even static variable,
as opposed to a method variable on the stack, then you lose thread safety,
and this could happen.
I apologize fo
If you remove the duplicate jars from the webapp, it will still find the
classes via the same classloader used in the host application, and the
single definition of each class will allow the casts to work.
Please respond to "Tomcat Users List"
To: "'Tomcat Users List'"
cc:
Subject
I'll assume you mean shared between separate web applications, as, within
a single web app. is nothing special. The key is the classloader. In
order for the singleton to be a true singleton, (not one fo reach webapp)
it must be loaded rom a common classloader. So the jar it is loaded from
sh
The "100 Continue" should be handled at a fairly low level within the HTTP
Client, and should never interfere with the receipt of the final response
by the client application. Are you saying that you receive the "100
Continue" within your client application as if it is the final response?
If s
Sorry for top post... limition of Notes e-mail client.
"100 continue" is a documented part of the HTTP 1.1 protocol. Your client
application should either handle the "100 continue" response, or present
itself as an HTTP 1.0 client in the original request, which will suppress
the "100 continue"
If you configure Tomcat to NOT require authentication for this particular
servlet, then your servlet can examine the credentials, and if they are
absent or insufficient, send a 401 - Not Authorized response, which causes
the browser to prompt for id/pass. You can also manipulate the "realm"
i
Sorry for the top post, but no choice with this $%* Notes e-mail client...
Normally, a browser will try to pipeline requests, which means that
multiple requests are sent over a single connection without waiting for
responses. The responses are, however, required to be returned in the
same order
I suspect the problem relates to pipelining of HTTP 1.1 requests over a
single persistent TCP connection. Pipelining is intended to improve
efficiency, allowing the need for multiple images to present a web page be
expressed to a web server one after another, before any of the responses
are
16 matches
Mail list logo
