> I suggest you have a read here:
> https://tomcat.apache.org/tomcat-10.0-doc/config/http.html#SSL_Support
> The documentation covers the details you need to correctly configure
Tomcat
> and SSL and links to a related page about SSL configuration.
> Notice the line:
> Each secure connector must d
On Tue, Mar 16, 2021, 11:46 Robert Turner wrote:
> I suggest you have a read here:
> https://tomcat.apache.org/tomcat-10.0-doc/config/http.html#SSL_Support
> The documentation covers the details you need to correctly configure Tomcat
> and SSL and links to a related page about SSL configuration.
I suggest you have a read here:
https://tomcat.apache.org/tomcat-10.0-doc/config/http.html#SSL_Support
The documentation covers the details you need to correctly configure Tomcat
and SSL and links to a related page about SSL configuration.
Notice the line:
Each secure connector must define at leas
> If you look at the stack trace, it tells you what the problem is:
> Caused by: java.lang.IllegalArgumentException: No SSLHostConfig
> element was found with the hostName [_default_] to match the
> defaultSSLHostConfigName for the connector [https-openssl-nio-8443]
> So it no longer looks like
If you look at the stack trace, it tells you what the problem is:
Caused by: java.lang.IllegalArgumentException: No SSLHostConfig
element was found with the hostName [_default_] to match the
defaultSSLHostConfigName for the connector [https-openssl-nio-8443]
So it no longer looks like you are hi
> Please provide full stacktrace
Please find full catlina log and I have already shared server.xml in trail
mail
16-Mar-2021 21:26:54.263 WARNING [main]
org.apache.tomcat.util.digester.SetPropertiesRule.begin Match
[Server/Service/Connector] failed to set property [compressableMimeType]
to
[
Please provide full stacktrace
On Tue, 16 Mar 2021 at 22:49, wrote:
>
> >> Your more recent exception log didn't include the "caused by" exception
> > --
> >> which is the actual failure details. Double-check that and make sure
> > it's
> >> the same issue.
> >>
> >> Also, use netstat to confirm
>> Your more recent exception log didn't include the "caused by" exception
> --
>> which is the actual failure details. Double-check that and make sure
> it's
>> the same issue.
>>
>> Also, use netstat to confirm you aren't using the ports already.
> Changing
>> it may just find another conflict (a
On 3/16/21 3:57 PM, dku...@ccilindia.co.in wrote:
Your more recent exception log didn't include the "caused by" exception
--
which is the actual failure details. Double-check that and make sure
it's
the same issue.
Also, use netstat to confirm you aren't using the ports already.
Changing
i
> Your more recent exception log didn't include the "caused by" exception
--
> which is the actual failure details. Double-check that and make sure
it's
> the same issue.
>
> Also, use netstat to confirm you aren't using the ports already.
Changing
> it may just find another conflict (although l
Your more recent exception log didn't include the "caused by" exception --
which is the actual failure details. Double-check that and make sure it's
the same issue.
Also, use netstat to confirm you aren't using the ports already. Changing
it may just find another conflict (although less likely). T
> Deepak,
> You already have some service listening on port 80 (IIS maybe?)
>
>
> from mobile (sorry for typos ;)
>
> We have changed the port still getting same error
> Maybe you have the same port configured twice in your conf/server.xml?
> Please post *all* elements from your conf/server.x
Deepak,
On 3/16/21 09:03, dku...@ccilindia.co.in wrote:
You already have some service listening on port 80 (IIS maybe?)
from mobile (sorry for typos ;)
We have changed the port still getting same error
Maybe you have the same port configured twice in your conf/server.xml?
Please post *all*
You already have some service listening on port 80 (IIS maybe?)
from mobile (sorry for typos ;)
We have changed the port still getting same error
16-Mar-2021 18:09:38.299 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
["http-nio-81"]
16-Mar-2021 18:09:38.363
You already have some service listening on port 80 (IIS maybe?)
from mobile (sorry for typos ;)
On Tue, Mar 16, 2021, 18:36 wrote:
> Dear All,
>
> Unable to start tomcat 10.0.4 and getting error Failed to initialize
> component.
> /conf/server.xml configuration as below.
>
> minSpare
It's saying port 80 is already in use. Make sure another process (like IIS)
isn't using the port already, or change your configuration to a different
port.
You can use 'netstat' (with options) to determine which process is using
the port already.
On Tue., Mar. 16, 2021, 07:36 , wrote:
> Dear Al
16 matches
Mail list logo
