hi
In case anyone wonders ..
I used another logging.properties in the application to overcome that.
(placed under WEB_INF/classes)
Thanks
-gili
From: Gili B
Sent: Wednesday, May 24, 2017 3:56 PM
To: users@tomcat.apache.org
Subject: tomcat 8 windows service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 5/25/17 10:00 AM, John Palmer wrote:
> On Thu, May 25, 2017 at 7:46 AM, Vidyadhar
> wrote:
>
>> On Thu, 25 May 2017 at 6:01 PM, Dhaval Jaiswal
>> wrote:
>>
>>> How can we avoid defining plain text password in server.xml or
>>> is there
Hi,
Is a HTTP/2 call to Tomcat proxied via IIS / JK Connector (Tomcat Connector)
expected to succeed?
George
Chris,
On 5/24/2017 2:09 PM, Christopher Schultz wrote:
> Mark,
>
> On 5/24/17 11:50 AM, Mark Eggers wrote:
>> True blue-green deployments would take some additional work, but
>> that's not beyond the realm of possibility. I might spend some
>> time doing this with Elastic Beanstalk, since $work
I haven't tested it yet, but if you're on a Windows platform you MAY be
able to tell Tomcat to use the Windows Certificate Store (an thus NOT have
a password in server.xml) by adding something like this to the Java Options:
-Djavax.net.ssl.trustStoreProvider=SunMSCAPI
-Djavax.net.ssl.trustStoreType
On Thu, 25 May 2017 at 6:01 PM, Dhaval Jaiswal
wrote:
> How can we avoid defining plain text password in server.xml or is there a
> way i can encrypt the password in server.xml.
>
There are couple of examples on https://wiki.apache.org/tomcat/FAQ/Password
--
Regards,
Vidyadhar
How can we avoid defining plain text password in server.xml or is there a
way i can encrypt the password in server.xml.
