Thanks everyone, this has been very informative.
On 4/4/2014 5:52 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 4/4/14, 1:09 PM, Jeffrey Janner wrote:
-Original Message- From: Jeffrey Janner
[mailto:jeffrey.jan...@polydyne.com] Sent: Friday, April 04, 2014
12:04 PM To: 'Tomcat Users List'
> From: jeffrey.jan...@polydyne.com
> To: users@tomcat.apache.org
> Subject: RE: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does not work
> Date: Fri, 4 Apr 2014 17:33:08 +
>
> > -Original Message-
> > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> > Sent: Friday
Chris,
On 4.4.2014 16:27, Christopher Schultz wrote:
So they don't have a big "Daddy" certificate that has signed all of
their intermediate certificates? Boo. That would fix nearly everything.
Actually, having different root certificates, one for SHA-1, and one for
SHA-2 is recommended migrat
Mark,
On 4.4.2014 23:54, Mark Thomas wrote:
The CA that signed your certificate might not be one of the root CAs
trusted by the user agent. Most likely it is an intermediate CA. The
root CA will have signed the intermediate CA's certificate and the
intermediate CA will have signed your certifica
Mark,
On 4.4.2014 23:00, Mark Murphy wrote:
So let me try to understand what is going on here. I generate a keystore
using keytool, that contains a key. At this point it is equal to a self
signed certificate, and it works, but the browser complains that there is
no CA.
(Standard on this list i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 4/4/14, 1:09 PM, Jeffrey Janner wrote:
>> -Original Message- From: Jeffrey Janner
>> [mailto:jeffrey.jan...@polydyne.com] Sent: Friday, April 04, 2014
>> 12:04 PM To: 'Tomcat Users List' Subject: RE: AW: AW:
>> tomcat-connectors-
On 04/04/2014 22:00, Mark Murphy wrote:
> So let me try to understand what is going on here. I generate a keystore
> using keytool, that contains a key. At this point it is equal to a self
> signed certificate, and it works, but the browser complains that there is
> no CA. I then need to create a c
Another option I normally use that may work for you (just confirmed it for
myself with tomcat):
1. Copy your private key and signed public certificate in PEM format into a
single file looking like this:
-BEGIN RSA PRIVATE KEY-
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,F2CCC247E25D
Sorry for the dumb questions, I am new to SSL, and want to understand what
I am doing, not just run these instructions, and it should work.
On Fri, Apr 4, 2014 at 5:00 PM, Mark Murphy wrote:
> So let me try to understand what is going on here. I generate a keystore
> using keytool, that contain
All,
First of all, I apologize for the question on "catalina.out" being empty in
v7.0.23. That's because I am using log4j for Tomcat logging, and the level
was set to "ERROR".
Here is an interesting finding between v7.0.23 and v7.0.52. It appears
that a 3 second delay occurs in v7.0.52 as the d
So let me try to understand what is going on here. I generate a keystore
using keytool, that contains a key. At this point it is equal to a self
signed certificate, and it works, but the browser complains that there is
no CA. I then need to create a certificate request ad send that off to
goDaddy.
Thanks Konstantin! Makes sense, I will switch over to manually installing
the release.
Best Regards,
Sean
On Fri, Apr 4, 2014 at 12:10 PM, Konstantin Kolinko
wrote:
> 2014-04-04 21:59 GMT+04:00 Sean Winterberger >:
> > We just updated to tomcat 7.0.52 using the JSR356 implementation for
> > w
On Apr 4, 2014, at 4:42 PM, Mark Murphy wrote:
> I saw something on StackOverflow that said the key type in the keystore
> needs to be PrivateKeyEntry and not trustedCertEntry. Is this true? When I
> look at my keystore, it is trustedCertEntry for all the certs.
>
> But when I look at the type
On 04/04/2014 21:42, Mark Murphy wrote:
> I saw something on StackOverflow that said the key type in the keystore
> needs to be PrivateKeyEntry and not trustedCertEntry. Is this true? When I
> look at my keystore, it is trustedCertEntry for all the certs.
>
> But when I look at the type for the se
On Apr 4, 2014, at 4:34 PM, Mark Murphy wrote:
> 1.5.0_15
Any chance you could try a more recent JVM? Java 6 or preferably Java 7.
That’s really old.
Dan
>
> On Fri, Apr 4, 2014 at 3:23 PM, Daniel Mikusa wrote:
>> On Apr 4, 2014, at 2:52 PM, Mark Murphy wrote:
>>
>>> Created my keystore
I saw something on StackOverflow that said the key type in the keystore
needs to be PrivateKeyEntry and not trustedCertEntry. Is this true? When I
look at my keystore, it is trustedCertEntry for all the certs.
But when I look at the type for the self signed certificate (which works),
it shows keyE
1.5.0_15
On Fri, Apr 4, 2014 at 3:23 PM, Daniel Mikusa wrote:
> On Apr 4, 2014, at 2:52 PM, Mark Murphy wrote:
>
>> Created my keystore according to the directions here:
>> http://support.godaddy.com/help/article/5239/generating-a-csr-and-installing-an-ssl-certificate-in-tomcat-4x5x6x7x
>
> Ok.
On Apr 4, 2014, at 2:52 PM, Mark Murphy wrote:
> Created my keystore according to the directions here:
> http://support.godaddy.com/help/article/5239/generating-a-csr-and-installing-an-ssl-certificate-in-tomcat-4x5x6x7x
Ok. Good start.
> This is what I see in Chrome:
>
> SSL Connection Error
Created my keystore according to the directions here:
http://support.godaddy.com/help/article/5239/generating-a-csr-and-installing-an-ssl-certificate-in-tomcat-4x5x6x7x
This is what I see in Chrome:
SSL Connection Error
Unable to make a secure connection to the server. This may be a
problem wit
Thanks for the timely response Dan, much appreciated! Ill bring it up with
the debian mailing list and use the manual install for now.
On Fri, Apr 4, 2014 at 12:11 PM, Daniel Mikusa wrote:
> On Apr 4, 2014, at 1:59 PM, Sean Winterberger
> wrote:
>
> > We just updated to tomcat 7.0.52 using the
On Apr 4, 2014, at 1:59 PM, Sean Winterberger
wrote:
> We just updated to tomcat 7.0.52 using the JSR356 implementation for
> websockets. This implementation is using the annotated class method of
> setting up the websocket server endpoint.
>
> On a local install of the system (windows7) the t
2014-04-04 21:59 GMT+04:00 Sean Winterberger :
> We just updated to tomcat 7.0.52 using the JSR356 implementation for
> websockets. This implementation is using the annotated class method of
> setting up the websocket server endpoint.
>
> On a local install of the system (windows7) the tomcat lib
On Apr 4, 2014, at 1:24 PM, Mark Murphy wrote:
> I am trying to set up SSL on tomcat with a CA certificate from goDaddy.
>
> I am unable to load the Web Page using HTTPS.
What exactly happens when you try to access it? Please include browser
behavior and any errors / messages it gives you abo
We just updated to tomcat 7.0.52 using the JSR356 implementation for
websockets. This implementation is using the annotated class method of
setting up the websocket server endpoint.
On a local install of the system (windows7) the tomcat lib directory
contains tomcat7-websocket.jar and websocket-a
> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Sent: Friday, April 04, 2014 12:10 PM
> To: 'Tomcat Users List'
> Subject: RE: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does
> not work
>
> > -Original Message-
> > From: Jeffrey Janner [m
I am trying to set up SSL on tomcat with a CA certificate from goDaddy.
I am unable to load the Web Page using HTTPS.
When I try to use a self signed certificate, everything works as expected,
but when I change the keystore to point to the one with the CA certificate
in it, I get nothing. There i
> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Sent: Friday, April 04, 2014 12:04 PM
> To: 'Tomcat Users List'
> Subject: RE: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does
> not work
>
> > -Original Message-
> > From: Christopher Schul
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, April 04, 2014 10:20 AM
> To: Tomcat Users List
> Subject: Re: [OT] AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis
> does not work
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA2
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, April 04, 2014 10:23 AM
> To: Tomcat Users List
> Subject: Re: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does
> not work
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
Hi Chris,
Thanks you for the note!
On Thu, Apr 3, 2014 at 12:40 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Shanti,
>
>
> They work the same way. Are you launching them differently for
> different versions?
>
Yes, actua
Im sorry about that. The reason I did not post same day was that through
the messages in this thread someone suggested adding a debug statement to
debug WebappClassLoader, and I wanted to wait to see if it happened again
so I could see the debug output, then I came up with the idea in my last
messa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 4/4/14, 10:50 AM, Jeffrey Janner wrote:
>> -Original Message- From: André Warnier
>> [mailto:a...@ice-sa.com] Sent: Thursday, April 03, 2014 5:27 PM To:
>> Tomcat Users List Subject: Re: AW: AW:
>> tomcat-connectors-1.2.39-window
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 4/4/14, 10:50 AM, Jeffrey Janner wrote:
> I've not followed the complete thread, but if the server is a *nix
> implementation, the better diag tool might be dig.
No, you haven't been following it well. The subject pretty much
rules-out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Elias,
On 4/4/14, 11:03 AM, Elias Kopsiaftis wrote:
> Ive done some more research into this problem with my co developer,
> and we have a question. Is it possible that memory leaks would
> cause tomcat to crash?
Yes, but you'll likely get an OutOfM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 4/4/14, 8:57 AM, Daniel Mikusa wrote:
> On Apr 4, 2014, at 8:22 AM, Saurabh Saraswat
> wrote:
>
>> Dear Dan,
>>
>> Thanks for your response!
>>
>> I have cross checked the user / password configuration. All is
>> correct.
>
> If you’
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurabh,
On 4/4/14, 1:19 AM, Saurabh Saraswat wrote:
> I am doing connection pooling with tomcat 7.0.39 and MySQL
> 5.5.After searching on google and with your help i have done the
> below things. Even i am able to get the connection successfully
>
Ive done some more research into this problem with my co developer, and we
have a question. Is it possible that memory leaks would cause tomcat to
crash? Silly question I know, but heres technically what the situation is.
We did not add code to shut down all threads when application is undeployed
t
Hi,
On 04/02/2014 04:54 PM, bjoern.bec...@easycash.de wrote:
-Ursprüngliche Nachricht-
Von: André Warnier [mailto:a...@ice-sa.com]
Gesendet: Mittwoch, 2. April 2014 16:35
An: Tomcat Users List
Betreff: Re: grab hostname from tomcat manager
bjoern.bec...@easycash.de wrote:
Hello,
I nee
> -Original Message-
> From: André Warnier [mailto:a...@ice-sa.com]
> Sent: Thursday, April 03, 2014 5:27 PM
> To: Tomcat Users List
> Subject: Re: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does
> not work
>
> Christopher Schultz wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Neeraj,
On 4/4/14, 3:46 AM, Neeraj Sinha wrote:
> On 3 April 2014 23:06, Christopher Schultz
> wrote:
>
> Neeraj,
>
> On 4/2/14, 4:23 AM, Neeraj Sinha wrote:
I am trying to start tomcat on linux and I am getting
LifecycleException excep
Hi Konstantin,
On 04/02/2014 12:01 PM, Konstantin Kolinko wrote:
2014-04-02 5:21 GMT+04:00 Frederik Nosi :
On 04/02/2014 12:21 AM, Christopher Schultz wrote:
On 3/26/14, 9:32 PM, Frederik Nosi wrote:
My scenario is Apache httpd + mod_jk + N Tomcat's in. The default
behaviour of load balanced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ognjen,
On 4/4/14, 4:14 AM, Ognjen Blagojevic wrote:
> On 4.4.2014 5:23, Toby Lazar wrote:
>>> I've run my client program with the -Djavax.net.debug=all
>>> option. First it listed out all of the trusted authorities.
>>> Mine is GoDaddy and this is
-Original Message-
From: Saurabh Saraswat [mailto:ssaras...@pivotalindia.com]
Sent: Friday, April 04, 2014 7:23 AM
To: Tomcat Users List
Subject: Re: SQLNestedException in Connection Pooling With Tomcat 7.0.39
Dear Dan,
Thanks for your response!
I have cross checked the user / passwor
On Apr 4, 2014, at 8:22 AM, Saurabh Saraswat wrote:
> Dear Dan,
>
> Thanks for your response!
>
> I have cross checked the user / password configuration. All is correct.
If you’re getting “Access Denied” exceptions, there is only one cause and
that’s bad credentials (or host + credentials, be
On 4/4/2014 8:22 AM, Saurabh Saraswat wrote:
Dear Dan,
Thanks for your response!
I have cross checked the user / password configuration. All is correct. As
i mentioned that initially i am getting the object of connection but after
some time (After few hits to database from application) my web a
Dear Dan,
Thanks for your response!
I have cross checked the user / password configuration. All is correct. As
i mentioned that initially i am getting the object of connection but after
some time (After few hits to database from application) my web app goes to
slow and than it stops working i i g
On Apr 4, 2014, at 1:19 AM, Saurabh Saraswat wrote:
> Dear All,
>
> I am doing connection pooling with tomcat 7.0.39 and MySQL 5.5.After
> searching on google and with your help i have done the below things.
> Even i am able to get the connection successfully using this but getting
> some troubl
Ognjen,
You were correct. The GoDaddy GA2 certificate was not in the root
distributions. I re-keyed it to GA1 and that fixed the problems.
Thank you all.
Jeff Crump
Sent from Windows Mail
From: Ognjen Blagojevic
Sent: Friday, April 4, 2014 3:14 AM
To: Tomcat Users List
I once received similar exception while starting tomcat, but i was trying
to modify the web.xml with incorrect tags.
Try to get the thread dumps and track the changes that were performed
before your attempt to start tomcat.
On Wed, Apr 2, 2014 at 1:53 PM, Neeraj Sinha wrote:
> I am trying to sta
On 4.4.2014 5:23, Toby Lazar wrote:
I've run my client program with the -Djavax.net.debug=all option. First it
listed out all of the trusted authorities. Mine is GoDaddy and this is the
record:
That one is not the issuer of your certificate. GoDaddy has many issuing
certificates. The GoDaddy
Chris,
On 3 April 2014 23:06, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Neeraj,
>
> On 4/2/14, 4:23 AM, Neeraj Sinha wrote:
> > I am trying to start tomcat on linux and I am getting
> > LifecycleException exception whose snippet is below:
> >
> > Apr 2, 2
52 matches
Mail list logo
