Recompiling sources on jdk8 didnt resolve the error?
-Original Message-
From: Seshumadhav Chaturvedula seshumad...@yahoo.com.INVALID
Sent: 16-06-2014 12:15 PM
To: users@tomcat.apache.org users@tomcat.apache.org
Subject: Major Minor Version issue when using jersey 2.9 with tomcat7 +
Hi,
The issue still isnt resolved .I have tried putting in
validationquery,testOnborrow ,and removeabandoned=true.
Are you try
testOnReturn = true
?
Looks like if when Apache Solr closes resources, and it requires to
close the database connection, something has already closed the
ok running on tomcat 8.0.8 with spring 4.0.5 and reactor 1.1.2, my log
within minutes gets filled with these exceptions.
Seems like it could be a tomcat issue after all:
11:35:37,922 ERROR http-nio-80-exec-37
handler.LoggingWebSocketHandlerDecorator:61 - Transport error for SockJS
session
Hi Prashant,
On Tue, Jun 17, 2014 at 2:40 PM, Prashant Deva prashant.d...@gmail.com
wrote:
ok running on tomcat 8.0.8 with spring 4.0.5 and reactor 1.1.2, my log
within minutes gets filled with these exceptions.
Seems like it could be a tomcat issue after all:
This error could be also read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I've been using sticky sessions with mod_jk and I can see that there
is a bit of a problem when attempting to take a backend Tomcat server
out of load-balanced rotation: a user who never (or rarely) restarts
their web browser will keep the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Colin,
On 6/14/14, 10:05 AM, Colin Ingarfield wrote:
On Fri, Jun 13, 2014 at 4:39 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
James,
On 6/13/14, 4:11 PM, James H. H. Lampert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Selvakumar,
On 6/17/14, 2:44 AM, Selvakumar wrote:
Recompiling sources on jdk8 didnt resolve the error?
-Original Message- From: Seshumadhav Chaturvedula
seshumad...@yahoo.com.INVALID Sent: 16-06-2014 12:15 PM To:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 6/16/14, 12:01 PM, Steffen Heil (Mailinglisten) wrote:
Okay, I must have overlooked the keystoreProvider attribute
completely. Sorry for that and thanks a lot for the hint.
However that only solved the loading part of the problem.
Running TC 7.0.54 as a service with JRE 7u60, on Windows Server 2008 R2.
What should I use as a guideline for setting the socketBuffer setting in
server.xml? Should it just be big enough to handle a single response
with a little headroom? Or does it handle more than one response at a time?
2014-06-16 19:44 GMT+04:00 Martin Knoblauch knobis...@gmail.com:
Hi,
my environment is:
OS SuSE SLES11/SP2 64-bit
HTTP frontend: Apache2-2.2.21 (64-bit)
mod_jk: 1.2.37
Problem short: excessive connection timeouts with weird socket ids
Problem long: we frontend 4 Tomcats (7.0.42) using
Hello,
My question is not really Tomcat specific but, as my Webapp is a
Tomcat Webapp, I thought I should post this question here.
Below is what I would like to ask you:
How do you usually protect your Tomcat servers and Webapps from (D)DOS
((Distributed) Denial-of-service) attacks?
At
Léa,
Below is what I would like to ask you:
How do you usually protect your Tomcat servers and Webapps from (D)DOS
((Distributed) Denial-of-service) attacks?
If you allow the DOS traffic to make it all the way up to the
application layer before you detect it, then the DOS will still have
an
We launch Tomcat from a CL program, with a command front-end, and
currently we have the defaults set to 512M for the minimum heap space,
and 2048M for the maximum, running 7.0.47 or 7.0.54, and using the JVM
at /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit.
Any recommendations about heap size,
I recommended you to set up the min Heap Size = Max Heap Size = 2048M.
Don¹t forget to set up proper min and max permanent size as well. If your
Tomcat needs to create a lot threads, think about reducing the stack size
to accommodate more threads in a limit memory. It requires to set up
proper
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 6/17/14, 2:21 PM, James H. H. Lampert wrote:
We launch Tomcat from a CL program, with a command front-end, and
currently we have the defaults set to 512M for the minimum heap
space, and 2048M for the maximum, running 7.0.47 or 7.0.54,
Can i please know when Tomcat 6.0.42 will be released.
If not exact an estimation will also help.
-Thanks
Utkarsh
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
16 matches
Mail list logo