On 06.07.2018 19:49, Chris Cheshire wrote:
On Jul 6, 2018, at 12:56 PM, James H. H. Lampert
wrote:
Forgive the top-post.
The reason why this particular case of an extremely slow Manager upload sticks
out is because we've done, by now, hundreds of uploads of this same WAR file
(or earlier
> On Jul 6, 2018, at 12:56 PM, James H. H. Lampert
> wrote:
>
> Forgive the top-post.
>
> The reason why this particular case of an extremely slow Manager upload
> sticks out is because we've done, by now, hundreds of uploads of this same
> WAR file (or earlier versions of it), via Manager
Forgive the top-post.
The reason why this particular case of an extremely slow Manager upload
sticks out is because we've done, by now, hundreds of uploads of this
same WAR file (or earlier versions of it), via Manager, on over a dozen
different installations, most of them AS/400s, and none of
On 06.07.2018 01:23, James H. H. Lampert wrote:
Earlier this week, on a customer AS/400 installation (Tomcat 7.0.67), we
experienced the
slowest WAR file upload we've ever encountered: several HOURS to install a
roughly 100M
WAR file (we customarily increase the max-file-size and max-request-si
If you are not remote, can you just copy them to the IFS folder?
On 6 July 2018 at 00:23, James H. H. Lampert
wrote:
> Earlier this week, on a customer AS/400 installation (Tomcat 7.0.67), we
> experienced the slowest WAR file upload we've ever encountered: several
> HOURS to install a roughly 1
On 10/19/17, 10:02 AM, Christopher Schultz wrote:
The browser tells the server what cipher suites it supports during the
initial handshake, and the server decides which algorithm to use. The
client doesn't try multiple different connections to see which one
sticks. The server either replies sayin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 10/16/17 2:35 PM, James H. H. Lampert wrote:
> I just got finished going through 20 other customer Tomcat
> installations we administer.
>
> First, I found that most of them were accepting the DHE ciphers
> I'd disabled on the problem ins
I just got finished going through 20 other customer Tomcat installations
we administer.
First, I found that most of them were accepting the DHE ciphers I'd
disabled on the problem installation, and SSLLabs was giving them bad
ratings for doing so.
Second, I found that two of the other instal
On 16/10/17 17:57, James H. H. Lampert wrote:
> Can somebody explain what just happened?
>
> This morning, we got a call from a customer whose Tomcat server (on
> their own hardware) we administer.
>
> It seems that suddenly, and without any advance warning, all but the
> oldest browsers were ref
Well, I said it would be DUH!, didn't I.
Thanks a lot guys.
Have a good weekend,
Ken
Caldarale, Charles R wrote:
From: Ken Bowen [mailto:[EMAIL PROTECTED]
Subject: Re: Weird problem: Two apparent copies of app started
If I put my context element in META-INF/context.xml, how is it
assoc
Ken Bowen wrote:
> how does one ensure (if one can?) that myapp is an application running
> in Host2,
> but not in Host1 ??
Each host has its own appBase.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscr
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Re: Weird problem: Two apparent copies of app started
>
> If I put my context element in META-INF/context.xml, how is it
> associated with a particular virtual HOST?
>
> But if:
> conf/server.xml defines t
Chuck, PID:
Thanks for the replies and pointers -- they're a real help.
Now, I'm sure the following is going to turn out to be a DUH! moment for
me, BUT:
If I put my context element in META-INF/context.xml, how is it
associated with a
particular virtual HOST?
It's obvious how this happens i
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Re: Weird problem: Two apparent copies of app started
>
> So what I'm confused about is this: Exactly what should
> appear in Host and what in META-INF/context.xml??
> The "A Word on Contexts" in
>
> From: Pid [mailto:[EMAIL PROTECTED]
> Subject: Re: Weird problem: Two apparent copies of app started
>
> DO NOT use the path or docBase attribute in a Context defined
> outside of server.xml.
One exception to that: if the webapp is placed outside of the
appBase directory, y
Ken Bowen wrote:
> Sorry about thatsome kind of sloppiness on my part.
>
> I've realize the problem must lie in the relationship between my app's
> META-INF/context.xml and what is configured in Tomcat's conf/server.xml.
> IIn the latter, found there was an old Context entry in the Host eleme
Sorry about thatsome kind of sloppiness on my part.
I've realize the problem must lie in the relationship between my app's
META-INF/context.xml and what is configured in Tomcat's conf/server.xml.
IIn the latter, found there was an old Context entry in the Host element:
autoDeploy="true">
> From: Ken Bowen [mailto:[EMAIL PROTECTED]
> Subject: Weird problem: Two apparent copies of app started
>
> strongbrain/WEB-INF/lib/servlet-api.jar
One obvious error: you must not put the servlet-api.jar inside your
webapp - the container supplies that. Remove it and see if it helps.
- Chuck
Leucht, Axel wrote:
> Hi,
>
> I'm currently in desparate search for a problem I'm facing...
Please provide the context and host configuration for this web app.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To un
You are right. If I remove xercesImpl.jar from the class path then it works
also.
But there is another observation which is weird. Its that if I have my
application anywhere on C: drive then it works. It also works if I have it
on D:\Program Files\. If I have it on D:\ then it gives this error. W
Hi,
javax.xml.parsers.FactoryConfigurationError loads a implementation of
xml parsers using a J2SE discovery mecanism. This discovery mecanism
uses hints provided in .jars META-INF/ folder. Since you exploded your
jar of XercesImpl, this JAR does not take part anymore in the discovery
mecanism and
When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this makes your new message appear as part
of the old thread. Thi
22 matches
Mail list logo
