Mark Thomas wrote:
>
>
>Josh Gooding wrote:
>
>>Igor,
>>
>>I figured it out. If you set the deployOnStartup attribute to true,
>>but
>>the autoDeploy attribute to false, the war files that are in the
>>webapps
>>folder at the time of startup will load. Then you can run the manager
>>via
>>sc
Josh Gooding wrote:
>Igor,
>
>I figured it out. If you set the deployOnStartup attribute to true,
>but
>the autoDeploy attribute to false, the war files that are in the
>webapps
>folder at the time of startup will load. Then you can run the manager
>via
>script (command line). Simply pass th
> From: Josh Gooding [mailto:josh.good...@gmail.com]
> Subject: Tomcat 7 manager quirk?
> Is there a way that I can get tomcat to NOT start auto-deploying
> immediately when the manager is invoked with a deploy / update command?
> When I run the command: curl -k --upload-file ROOT.war
The usual
On 27/10/2012 11:22 AM, "Gabriel Huerta Araujo"
wrote:
>
> Is it enough with putting a line into this file like this?:
>
> 192.168.30.73 logangha
>
> Where 192.168.30.73 is my IP
>
192.168.30.73 logangha THE-DOMAIN-NAME-FROM-THE-CERTIFICATE
This should work.eg:
192.168.30.73 logangha mydomai.co
Igor,
I figured it out. If you set the deployOnStartup attribute to true, but
the autoDeploy attribute to false, the war files that are in the webapps
folder at the time of startup will load. Then you can run the manager via
script (command line). Simply pass the undeploy command to the manager
Is it enough with putting a line into this file like this?:
192.168.30.73 logangha
Where 192.168.30.73 is my IP
- Original Message -
From: "Gabriel Huerta Araujo"
To: "Tomcat Users List"
Sent: Friday, October 26, 2012 7:15:26 PM
Subject: Re: Implementing SSL and error invocating https:
This is my hosts file's content:
10.254.5.1 sigcbd01#10.192.19.1 sigc
10.254.4.63 sdswbd01#10.192.17.66sadigeo
10.254.2.248nsisba01
None of these IP's is my domain. How do I configure dns resolution for such
name on my computer to point to
the ip of my laptop? As I
Thanks for the advice.
Would set Jarskipping break any web apps (non of them using servlet 3.0
features)?
It would have helped if there is a v6 compatible setting for this.
There are quite a few jar skip setting. is there a way to set a single
param
all web apps are non-3.0 apps?
On 10/26/2
On 27/10/2012 10:09 AM, "Gabriel Huerta Araujo"
wrote:
>
> I used logangha(which is my computer name) instead of localhost but again
I had to click the Information bar to display the content (not recommended).
>
So you got the cert for logangha??? Again, you should match the name of the
domain yo
I used logangha(which is my computer name) instead of localhost but again I had
to click the Information bar to display the content (not recommended).
Regards.
- Original Message -
From: "Igor Cicimov"
To: "Tomcat Users List"
Sent: Friday, October 26, 2012 5:41:59 PM
Subject: Re: Imp
On 27/10/2012 9:37 AM, "Gabriel Huerta Araujo"
wrote:
>
> I have followed below steps:
>
> 1.- Erase keytore
> keytool -delete -keystore .keystore -storepass x_men_gha
>
> 2.- List to verify if it has been deleted.
> keytool -list -storepass x_men_gha
> Tipo de almacÚn de claves: JKS
> Proveedor
On 27/10/2012 5:27 AM, "Josh Gooding" wrote:
>
> Hey group,
>
> I'm working with Tomcat 7's manager application for text deployments. I
am
> having a bit of a quirky issue here. I am deploying a web application
that
> is approx 75MB as a war file that uses Tomcat's ROOT context.
>
> Is there a w
I have followed below steps:
1.- Erase keytore
keytool -delete -keystore .keystore -storepass x_men_gha
2.- List to verify if it has been deleted.
keytool -list -storepass x_men_gha
Tipo de almacÚn de claves: JKS
Proveedor de almacÚn de claves: SUN
Su almacÚn de claves contiene 0 entradas
3.-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriel,
On 10/26/12 11:57 AM, Gabriel Huerta Araujo wrote:
> Regarding password I run keytool indicating my password which is
> the same as the indicated in my connector section:
>
> keytool -list -keystore .keystore -storepass x_men_gha Tipo de
> a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 10/26/12 12:15 PM, Pid wrote:
> On 26/10/2012 13:53, Martin Gainty wrote:
>>
>> Hi Dan
>>
>> if you reference this simple test.jsp does every version of every
>> browser accept the cert as CA cert and properly installs your
>> certificate?
>
Hey group,
I'm working with Tomcat 7's manager application for text deployments. I am
having a bit of a quirky issue here. I am deploying a web application that
is approx 75MB as a war file that uses Tomcat's ROOT context.
Is there a way that I can get tomcat to NOT start auto-deploying
immedia
Hi Andre
I also am a newbie with this stuff
But something that I saw about my .keystore file and my certificate from a
Certificate Authority(I got this certificate from
http://getacert.com/signacert.html):
I run below command with its respective output for my keystore file which I
have genera
On 26/10/2012 13:53, Martin Gainty wrote:
>
> Hi Dan
>
> if you reference this simple test.jsp does every version of every browser
> accept the cert as CA cert and properly installs your certificate?
>
> <%@ page contentType="text/html"%>
>
>
>
> http://DanMachine:8080/Danwebapp/Dan
Haha, Scott you're here too?
On Thu, Oct 25, 2012 at 2:06 PM, Scott Carlson wrote:
> We've setup TC 7.0.32 with Clustering and Tomcat Container Managed
> Authentication. HTTPSessions and SSOSessions are clustered across the
> wire. With logging turned way up, I can see the synchronization and
Thinking I am running Tomcat on Windows
I have changed keystoreFile parameter below way:
keystoreFile="C:\Users\Gabriel Huerta\.keystore"
And it generates same error log.
This way:
keystoreFile="${user.home}\.keystore"
Again same error log.
Regarding password
I run keytool indicating my password
Hi Christopher
I do not understand what you mean with "other reply", but
I tried
openssl s_client -host logangha -port 8443
connect: Connection refused
connect:errno=111
Also I tried
openssl s_client -connect logangha:8443
And generates same output:
connect: Connection refused
connect:er
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 10/26/12 5:11 AM, Brian Burch wrote:
> I have another system with java-7-openjdk-i386, but I haven't yet
> done any work on it. This openjdk does not ship with a keytool
> program, and so I presume it will use openssl.
I dunno about the i38
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriel,
On 10/25/12 5:32 PM, Gabriel Huerta Araujo wrote:
>
> My web.xml's connector section originally was:
>
> disableUploadTimeout="true" enableLookups="false" maxThreads="25"
> port="8443" keystoreFile="${user.home}/.keystore"
> keystorePass=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriel,
On 10/25/12 5:42 PM, Gabriel Huerta Araujo wrote:
> Sorry I forgot to include what below command generates:
>
> openssl c_client -connect host:8443
Oops. That should have been s_client, but you already figured that out:
> I had to run it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ted,
On 10/25/12 7:24 PM, Ted Smith wrote:
> After upgrading to 7, deploying a new war file often results in
> PermGen error, much more often than in 6.(with identical JVM
> settings) I have tried all those JVM settings for perm memory but
> no help.
Hi Dan
if you reference this simple test.jsp does every version of every browser
accept the cert as CA cert and properly installs your certificate?
<%@ page contentType="text/html"%>
http://DanMachine:8080/Danwebapp/DanCertificate.cer";>
Martin Gainty
On Oct 26, 2012, at 5:11 AM, Brian Burch wrote:
> My production tomcat 7.0.26 (and its predecessors back as far as tc 5) have
> been running with its original SSL server certificate in a JKS keystore for
> many years.
>
> I decided to retire my ancient java-based Certificate Authority and creat
Gabriel Huerta Araujo wrote:
...
GRAVE: Failed to initialize end point associated with ProtocolHandler
["http-bio-8443"]
java.io.IOException: La configuración SSL no es válida debido a No available
certificate or key corresponds to the SSL cipher suites which are enabled.
at
org.apache
My production tomcat 7.0.26 (and its predecessors back as far as tc 5)
have been running with its original SSL server certificate in a JKS
keystore for many years.
I decided to retire my ancient java-based Certificate Authority and
create a new CA using openssl 1.0.1 under ubuntu linux.
I fo
29 matches
Mail list logo
