On 13/10/2017 05:32, wrote:
> On 10/12/17 12:47 PM, wrote:
>> After upgrading Tomcat to 9.0.1, the local webapp can't right
>> work. But in tomcat 7.0.54 is good.
>
> Did you copy your Tomcat 7.0.x configuration file into your Tomcat
> 9.0.x conf/ directory or did you start fresh?
>
>
Chris,
Peter Kreuser
> Am 13.10.2017 um 04:29 schrieb Christopher Schultz
> :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> James,
>
>> On 10/12/17 8:44 PM, James H. H. Lampert wrote:
>> Question:
>>
>> The application we're developing has a suite of web services
>> (RESTful, S
On 10/12/17 12:47 PM, wrote:
> After upgrading Tomcat to 9.0.1, the local webapp can't right
> work. But in tomcat 7.0.54 is good.
Did you copy your Tomcat 7.0.x configuration file into your Tomcat
9.0.x conf/ directory or did you start fresh?
---> no, i only copied the section.
Catalin
On 10/12/17 12:47 PM, wrote:
> After upgrading Tomcat to 9.0.1, the local webapp can't right
> work. But in tomcat 7.0.54 is good.
Did you copy your Tomcat 7.0.x configuration file into your Tomcat
9.0.x conf/ directory or did you start fresh?
--
From: (Carl.li)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurav,
On 10/11/17 8:56 AM, Saurav Sarkar wrote:
> I have got a basic question related to usage of Async servlet with
> tomcat NIO connector.
>
> I want to use Async servlet with Non Block I/O as per servlet spec
> https://docs.oracle.com/javaee/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 10/11/17 5:21 PM, Chris Cheshire wrote:
> Working on a migration from 7 to 8.5, and in it I am now using the
> tomcat dbcp, instead of apache commons dbcp.> I have found that
> with no other changes to the db code (except the factory para
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Harish,
On 10/12/17 10:55 AM, Harish Krishnan wrote:
> Thank you all for the help and responses. We figured out what the
> problem was. What I did was correct in terms of the attribute
> setting, the tomcat version used and the JRE version used. How
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Adam,
On 10/11/17 8:48 PM, Adam Pease wrote:
> Hi Chris and all, I was able to get my system running based on the
> instructions at
> https://community.letsencrypt.org/t/configuring-lets-encrypt-with-tomc
at-6-x-and-7-x/32416
>
>
. I clarified th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Adam,
On 10/9/17 6:13 PM, Adam Pease wrote:
> Hi Chris, Many thanks for the quick response! There's a lot of new
> terminology (to me) to all this and it's quite confusing I'm
> afraid.
>
> I tried Let's Encrypt just now but since I'm running Tomc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
小网,
On 10/12/17 12:47 PM, 小网 wrote:
> After upgrading Tomcat to 9.0.1, the local webapp can't right
> work. But in tomcat 7.0.54 is good.
Did you copy your Tomcat 7.0.x configuration file into your Tomcat
9.0.x conf/ directory or did you start fre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vamsi,
On 10/12/17 11:06 AM, Gali, Vamsi A wrote:
> This issue is now RESOLVED.
Great.
> On IHS (IBM HTTP Server, IBM version of Apache Webserver), we only
> had 2 TLS ciphers that are no compatible with Tomcat TLV1.2. So I
> added '' TLS_ECDHE_RS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 10/12/17 8:44 PM, James H. H. Lampert wrote:
> Question:
>
> The application we're developing has a suite of web services
> (RESTful, Swagger-based), and at least one of them can accept a
> pound sign ("#") as a URL parameter.
>
> Severa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Syam,
On 10/8/17 2:27 PM, Syam Pillai wrote:
> Thanks Chris, yes you are right they messed it up. I will also file
> a complaint with them.
https://forums.aws.amazon.com/thread.jspa?messageID=809159
https://forums.aws.amazon.com/thread.jspa?message
Question:
The application we're developing has a suite of web services (RESTful,
Swagger-based), and at least one of them can accept a pound sign ("#")
as a URL parameter.
Several months ago, with the application and all of its services running
on Tomcat 7, it was accepting a plain, naked #
hi,
After upgrading Tomcat to 9.0.1, the local webapp can't right work. But in
tomcat 7.0.54 is good.
---
server.xml host configure
---
webapp dir.
- htdocs
+ jsp
+ static
---
jsp source file
<%@page language="java" contentType="text/
This issue is now RESOLVED.
On IHS (IBM HTTP Server, IBM version of Apache Webserver), we only had 2 TLS
ciphers that are no compatible with Tomcat TLV1.2. So I added ''
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256" to IHS httpd.conf by looking at this:
https://www.ibm.com/support/knowledgecenter/en/S
Thank you all for the help and responses.
We figured out what the problem was. What I did was correct in terms of the
attribute setting, the tomcat version used and the JRE version used.
However, I did not realize our JRE is running in FIPs mode using RSA BSAFE as
the crypto provider.
When I tes
PLM is over contact Tom cat
On Thursday 12 October 2017, 7:43:23 PM IST, Sanjoy Bhattacharjee
wrote:
Honeywell Softco access the SCR time line 1. Cambridge technology 2. Philips
R&D center 3. Matrix one R&D center 4. Geometric HCL computer 5. TCS Infosys
Capgemini Anish IIM R
O
On 12.10.2017 15:33, Gali, Vamsi A wrote:
:)
IHS is IBM HTTP Server.
Thank you,
Thank you too. I feel a lot less like a dummy now.
And after reading a bit on "IHS" now, it would seem that this is at least 90% Apache httpd
2.2, which may make it clearer to other people that maybe they could he
:)
IHS is IBM HTTP Server.
Thank you,
-Original Message-
From: André Warnier (tomcat) [mailto:a...@ice-sa.com]
Sent: Thursday, October 12, 2017 9:32 AM
To: users@tomcat.apache.org
Subject: Re: FW: [error] SSL0266E: Handshake Failed, Could not establish SSL
proxy connection
And for the
And for the rest of us dummies trying to follow this conversation, what might
"IHS" be ?
Whatever Google returns doesn't seem really relevant.
On 12.10.2017 15:25, Gali, Vamsi A wrote:
Igor,
Thank you for suggesting me to turn on the ssl dubug. We are using Java 1.8 which
by default uses TLS1.
Igor,
Thank you for suggesting me to turn on the ssl dubug. We are using Java 1.8
which by default uses TLS1.2. Looks like both IHS & Tomcat are using tls1.2 but
there is a cipher mismatch. We have Tam directly connecting to Tomcat and the
connectivity works w/o any SSL handshake errors. Hence,
22 matches
Mail list logo