On 29.11.2017 08:45, jose luis Calvo wrote:
Tomcat version: 7.0.82-0113
Operating System: Synology DSM 6.1.4-15217 Update 2
Model: DS414
Subject: After install component from Package Center Tomcat is ready
to configure but only there are three initial folders "docs"
"host-manager" and
it's incredible! what is happening in support teams? I need help please.
Dear André, firstly thank you for your quickly response. I can
understand what happen because Synology Service told me that (all
consersation are below):
Dear Customer,
Thank you for contacting Synology. We will get back
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Don,
On 11/28/17 4:55 PM, Don Flinn wrote:
>>> In fact, I think you are using PEM-encoded DER files and not a
>>> packaged keystore, even though your SSLHostConfig's
>>> keystoreType is set to "PKCS12".
>
> Yes, I am using PEM files. Got to read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Big Papa,
On 11/29/17 12:06 AM, TurboChargedDad . wrote:
> So.. Thank you for those help me understand the NIO vs BIO in
> tomcat 7..
So now all you have to do is upgrade to Tomcat 8.0 or, even better,
Tomcat 8.5 :)
> I made those changes things
Hola Jose,
On 29/11/17 08:45, jose luis Calvo wrote:
Tomcat version: 7.0.82-0113
Operating System: Synology DSM 6.1.4-15217 Update 2
Model: DS414
Subject: After install component from Package Center Tomcat is ready
to configure but only there are three initial folders "docs"
"host-manager"
On 29.11.2017 10:54, jose luis Calvo wrote:
it's incredible! what is happening in support teams? I need help please.
We know that, and we're trying. But we can't know what is in the package of the various
OS distributions. Those are made by different people than the Tomcat developers.
It
On 30/11/2017 06:53, Naga Ramesh wrote:
> Team,
>
> We are facing some issues on security level testing time, so please
> check the below mentioned issues and suggest me the changes on tomcat
> level ASAP.
>
> 1. *Session Cookie do not contain secure attribute:* for this
> what are
Hi Mark,
Please find my comments here & PFA diagram.
User > AWS > Tomcat
(HTTPS)(HTTPS)
User-HTTPS request> AWS-ELB(https-443) re-direct to tomcat connector
port-8080
What is the (expected) path when the user makes an HTTPS request? Is it:
User > AWS
>> So now all you have to do is upgrade to Tomcat 8.0 or, even better,
>>Tomcat 8.5 :)
That's the plan but it's kind of like pulling teeth.
>>Can you expand on the "weirdness"? I see you have some more details
>>below but I think you could be more specific.
Let's say that there are 12 users
It should also be noted that if I bounce one of the larger instances.
Everyone suffers during the time to startup. The connection counts raise
in the same way although I am not sure at this time if there is an actual
outage experienced by anyone. I will have to do some testing to determine
10 matches
Mail list logo
