2013/1/11 Ralph Schaer ralphsch...@gmail.com:
Hi
Tomcat 7.0.34 bumped ecj to version 4.2.1. But the pom file
of tomcat-embed-jasper still points to version 3.7.2 of ecj.
Is it safe to use ecj 3.7.2 with Tomcat 7.0.34?
It's unfortunately not possible to override this, because I haven't found
On 10 Jan 2013, at 20:20, Daniel Mikusa dmik...@vmware.com wrote:
On Jan 10, 2013, at 3:10 PM, Linoma DevTeam wrote:
Thank you everyone for the responses/suggestions.
I did ensure that those were the same during the tests, but had removed
that from the server.xml before sending. Both
Hello:
I am trying to get mod_jk to work, and it works if tomcat is listening on port
8080, but I try to shut down port 8080 from tomcat and configure it in an
Apache vhost, but apache dies. I think I am following the rules, but obviously
I am missing something fundamental. Would appreciate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 1/10/13 10:35 PM, Martin Gainty wrote:
its a simple question what does ciphers parameter in Connector
have anything to do with the supported ciphers from the key itself
the 2 are disconnected
Supported ciphers may be set in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 1/10/13 11:00 PM, Martin Gainty wrote:
http://security.stackexchange.com/questions/7440/what-ciphers-should-i-use-in-my-web-server-after-i-configure-my-ssl-certificate
With a RSA key you can nominally use the RSA and DHE_RSA cipher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vic,
On 1/11/13 9:53 AM, vi...@thepenguin.org wrote:
I am trying to get mod_jk to work, and it works if tomcat is
listening on port 8080, but I try to shut down port 8080 from
tomcat and configure it in an Apache vhost, but apache dies. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Radek,
On 1/10/13 6:28 AM, Radek Szamrej wrote:
Thank you for the great tip,
with your help I was able to find it (and confirmed it works):
To summarize:
Setting for the Host in sever.xml is called
backgroundProcessorDelay (value
Nothing is listening on port 8080 now. That is what confused me. It should be,
right?
-Original Message-
From: Christopher Schultz ch...@christopherschultz.net
Sent: Friday, January 11, 2013 11:11am
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Change port that apache runs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vic,
On 1/11/13 11:48 AM, vi...@thepenguin.org wrote:
Nothing is listening on port 8080 now. That is what confused me. It
should be, right?
Did you actually configure Apache httpd to listen on port 8080? Simply
doing VirtualHost *:8080 doesn't
Thanks the problem was that the changes I was making in ports.conf were not
being included in the apache config. I added an include in httpd.conf and now
it works. Such a silly thing to miss.
Thanks,
CaptainVic
-Original Message-
From: Christopher Schultz ch...@christopherschultz.net
-Original Message-
From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
Subject: docBase
Tomcat 7.0.34
Java 1.6.0_35
Can the document base of a context be an administrative share?
Ex:
\\servername\share$\somedirectoryfile:///\\servername\share$\somedire
ctory
I run tomcat
On 1/11/2013 3:24 PM, Leo Donahue - RDSA IT wrote:
Tomcat 7.0.34
Java 1.6.0_35
Can the document base of a context be an administrative share?
Ex: \\servername\share$\somedirectoryfile:///\\servername\share$\somedirectory
I run tomcat as a service using a local account on webserver1, that same
On 1/11/2013 3:28 PM, Leo Donahue - RDSA IT wrote:
-Original Message-
From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
Subject: docBase
Tomcat 7.0.34
Java 1.6.0_35
Can the document base of a context be an administrative share?
Ex:
-Original Message-
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: docBase
On 1/11/2013 3:28 PM, Leo Donahue - RDSA IT wrote:
-Original Message-
From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
Subject: docBase
Tomcat 7.0.34
Java 1.6.0_35
Can
1. The ciphers parameter in Connecter determines the enabled cipher suites
in the SSLSocket. See SSLSocket.setEnabledCipherSuites(). That in turn
restricts which actual cipher suite can be negotiated with the client,
depending also on the client's cipher suites and how JSSE chooses among
those
1. The ciphers parameter in Connecter determines the enabled cipher suites
in the SSLSocket. See SSLSocket.setEnabledCipherSuites(). That in turn
restricts which actual cipher suite can be negotiated with the client,
depending also on the client's cipher suites and how JSSE chooses among
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 1/11/13 9:26 PM, Martin Gainty wrote:
1. The ciphers parameter in Connecter determines the enabled
cipher suites in the SSLSocket. See
SSLSocket.setEnabledCipherSuites(). That in turn restricts which
actual cipher suite can be
17 matches
Mail list logo