e sslProtocol? You
> presently have this set at "TLSv1", which I do not believe is valid.
>
> http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
>
> --Sal
>
>
>
> On 02/14/2011 02:46 PM, Sean Killeen wrote:
>
>> It doesn't -- it tells me t
It doesn't -- it tells me that a certificate already exists with that alias,
and the import fails.
--
Sean
On Mon, Feb 14, 2011 at 12:54 PM, Mark Thomas wrote:
> On 14/02/2011 14:03, Sean Killeen wrote:
> > The next step seems to throw tomcat off. I believe I need to replace t
Hi all,
I'm hoping someone has run into this problem before.
I'm using VeriSign certs and have imported a certificate correctly before
using keytool. However, the certificate we were using expired, and we
obtained a replacement.
Importing the replacement appears to be more difficult.
Verisign's
that probably solves my issue -- thanks for all the help and
support!
All the best,
Sean
On Fri, Sep 24, 2010 at 9:07 AM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Sean Killeen [mailto:seankill...@gmail.com]
> > Subject: Re: Tomcat 6.0.28 w/ VeriSign S
Thu, Sep 23, 2010 at 3:47 PM, Mark Thomas wrote:
> On 23/09/2010 11:48, Sean Killeen wrote:
> > Sorry for the additional reply but I found some additional information
> that
> > might be relevant:
> >
> > We have a tomcat 6.0 installation that is referring to the sam
the files with Notepad++ and they are pretty much exactly
the same. I pasted my 6.0 connector to replace 6.0.28 default connectors in
the server.xml file.
Given this, any idea what my next steps might be?
--
Sean
On Thu, Sep 23, 2010 at 2:38 PM, Sean Killeen wrote:
> @Kishore: I attempted y
@Kishore: I attempted your fix, but the errors remain so I changed it back.
@Mark: I commented the AprLifecycleListener listener, but the error remains.
The listeners section of server.xml now looks like:
Thanks for the fast responses! Hoping to find a resolution to this soo
Hi all,
Have been going through steps to upgrade a product residing on Tomcat (on
Windows Server 2003) to the newest version. Previously, our upgrade path
went to 6.0 but now we've taken it to 6.0.28 on another server and I'm
encountering errors that I can't seem to trace. I've been all over Googl
