OK, I double clicked. Can you give me some more details on choosing root
folder and webapps folder? I see three radio buttons that are all greyed
out. I don't know how to click on them.
Use workspace metadata (dones not modify Tomcat installation)
Use the tomcat installation (takes control
On 14/02/2013 02:22, Steve van Loben Sels wrote:
Greetings.
I recently upgraded from Tomcat 6.0.36 to 7.0.35 with the native APR
connector, and I ran into a problem with numbers in my access Log. I use
the %D (Time taken to process the request, in millis) to measure the
service delivery
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 2/13/13 4:47 PM, Giuseppe Sacco wrote:
I have an application deployed on tomcat 6.0.35 and linux/amd64
with a JSSE https connector. When I try to connect to this site
with default iPad browser, I always get an error message about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 2/13/13 4:04 PM, Thomas, Steve wrote:
A coworker just found this:
http://stackoverflow.com/questions/14167508/intermittent-sslv3-alert-handshake-failure-under-python
Interesting.
I wonder if this has to do with renegotiation: that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Terrence,
On 2/14/13 1:23 AM, Terence M. Bandoian wrote:
I probably should have said there is a potential for lost
knowledge. Here are a couple of anecdotal examples that I hope
will help illustrate what I mean.
- I was told recently by a
On Thu, Feb 14, 2013 at 11:38 AM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 2/13/13 4:47 PM, Giuseppe Sacco wrote:
iPad does try a few times, changing the version number, but it
fails every time and eventually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mike,
On 2/14/13 9:51 AM, Mike Wilson wrote:
I can see that even if you specify URIEncoding=UTF-8 in
server.xml, calls to HttpServletRequest.getRequestURI() will still
return an undecoded String. (This is probably because of the
specification
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/14/13 5:22 AM, Mark Thomas wrote:
On 14/02/2013 02:22, Steve van Loben Sels wrote:
Greetings.
I recently upgraded from Tomcat 6.0.36 to 7.0.35 with the native
APR connector, and I ran into a problem with numbers in my
access Log.
Hello;
I've been struggling with this for a couple of weeks now. I've searched
web sites, forums and lists, but I can't seem to find the information I
want.
We have two web sites on a Tomcat 5.5 server (virtual hosts?). I didn't
set up the server, but I've been tasked to password protect
The easy way is to use a reverse proxy as apache2 in front-side, in another
words, use the traditional apache2 with modproxy to display the tomcat6
pages. Its very easy to do it!
2013/2/14 Dennis Gormley gorm...@hslc.org
Hello;
I've been struggling with this for a couple of weeks now. I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dennis,
On 2/14/13 3:22 PM, Dennis Gormley wrote:
We have two web sites on a Tomcat 5.5 server (virtual hosts?).
You should upgrade as soon as possible: Tomcat 5.5 is not longer
supported. You should move to Tomcat 7.0 at your earliest
Dennis Gormley wrote:
Hello;
I've been struggling with this for a couple of weeks now. I've searched
web sites, forums and lists, but I can't seem to find the information I
want.
We have two web sites on a Tomcat 5.5 server (virtual hosts?). I didn't
set up the server, but I've been
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Thursday, February 14, 2013 11:41 AM
To: Tomcat Users List
Subject: Re: Tomcat upgrade -SSL handshake failure?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 2/13/13 4:04 PM, Thomas,
Tomcat by default should accept all the enabled cipher suites in an
SSLSocket, unless it has been configured to do differently. That list is far
longer than either of the client lists supplied.
-Original Message-
From: Giuseppe Sacco [mailto:giuse...@eppesuigoccas.homedns.org]
Sent:
Phillipe
ajp_send_request::jk_ajp_common.c (1630):
(nodeYY) connecting to backend failed. Tomcat is probably not started or is
listening on the wrong port (errno=115)
indicate that you might have a misconfig on jk.properties ...check out host and
port attributes here
Hi Carrillo
Thanks for the answer. I will certainly look into clustering
options once I know the maximum connection limit achievable from a single
instance of tomcat. I was wondering if anyone else has done the same thing
and could help with required configurations and provide his
Hi Amit,
I do not want to top post on this issue. But I do have the same problem. If
you come across the solution, please post the solution so that I can also
benefit from it.
Thanks,
Vijaya
-Original Message-
From: Amit Bhagra
Sent: Friday, February 15, 2013 8:41 AM
To: 'Tomcat
Thank you, we'll double check
On Friday, February 15, 2013, Martin Gainty wrote:
Phillipe
ajp_send_request::jk_ajp_common.c (1630):
(nodeYY) connecting to backend failed. Tomcat is probably not started or is
listening on the wrong port (errno=115)
indicate that you might have a misconfig
18 matches
Mail list logo
