Re: Apache Tomcat 9.x end of life

2023-06-09 Thread Osipov, Michael (SMD IT IN) 

On 2023-06-08 18:17, Mark Thomas wrote:

On 08/06/2023 16:32, Zoltan Balogh wrote:

Dear Apache Team,

I just would like to ask is there any planned EOL for Tomcat 9?


Best guess at the moment (and it is only a guess - no decisions have 
been made) is 3 years after 8.5.x is EOL which gives a date of 31 March 
2027.


It is worth noting that Tomcat major versions track releases of the 
Jakarta Servlet specification and there has been an effort from the 
Jakarta project to increase the release cadence. Delays are also not 
unheard of. The estimate above could easily be a year out in either 
direction.


We are heavily using Java 8 that is supported until 2030, so we expect 
Apache Tomcat 9 will be also support while Java 8 is supported.


That is extremely unlikely at this point.

Important note that Tomcat 9 is the last release that works fine with 
Java 8 along with Java EE. Therefore, it is highly important for us to 
have a maintained Tomcat 9 for Java 8.


Once Tomcat 9.0.x reaches EOL we will provide, assuming there is demand, 
Tomcat 9.10.x which will be Tomcat 10.1.x but with the Java EE 8 API. 
The minimum Java requirement for 9.10.x will be Java 11.


Once Tomcat 10.1.x reaches EOL we will provide Tomcat 9.11.x which would 
be Tomcat 11.0.x but with the Java EE 8 API.


I wonder to what extent this is necessary at all. Baseline is Java EE 8 
and Java 8 and it should stay that way, I guess. If some code is back 
ported, sure it needs to be refitted to Java 8 if necessary, otherwise 
there would no more Java EE 8 capable container on Java 8. Moving to a 
new Java version is one thing, but replacing namespaces is a completely 
different one for people.


M

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Apache Tomcat 9.x end of life

2023-06-08 Thread Zoltan Balogh 
Great, and thanks a lot for sharing this information.

I totally agreee with you that involving the community in this discussion is 
very useful to see the demands.

Kind Regards,

Zoltan Balogh


-Original Message-
From: Mark Thomas  
Sent: Thursday, June 8, 2023 6:18 PM
To: users@tomcat.apache.org
Subject: Re: Apache Tomcat 9.x end of life

On 08/06/2023 16:32, Zoltan Balogh wrote:
> Dear Apache Team,
> 
> I just would like to ask is there any planned EOL for Tomcat 9?

Best guess at the moment (and it is only a guess - no decisions have been made) 
is 3 years after 8.5.x is EOL which gives a date of 31 March 2027.

It is worth noting that Tomcat major versions track releases of the Jakarta 
Servlet specification and there has been an effort from the Jakarta project to 
increase the release cadence. Delays are also not unheard of. The estimate 
above could easily be a year out in either direction.

> We are heavily using Java 8 that is supported until 2030, so we expect Apache 
> Tomcat 9 will be also support while Java 8 is supported.

That is extremely unlikely at this point.

> Important note that Tomcat 9 is the last release that works fine with Java 8 
> along with Java EE. Therefore, it is highly important for us to have a 
> maintained Tomcat 9 for Java 8.

Once Tomcat 9.0.x reaches EOL we will provide, assuming there is demand, Tomcat 
9.10.x which will be Tomcat 10.1.x but with the Java EE 8 API. 
The minimum Java requirement for 9.10.x will be Java 11.

Once Tomcat 10.1.x reaches EOL we will provide Tomcat 9.11.x which would be 
Tomcat 11.0.x but with the Java EE 8 API.

And so on.

All our planning to date has assumed that the primary demand would be for the 
newer features (that require newer JREs) supported by newer Tomcat versions but 
with the Java EE 8 API. If that assumption is incorrect and the primary demand 
is for Tomcat 9.0.x that runs on Java 8 then it is possible that we could just 
keep supporting Tomcat 9.0.x. 
Given that Tomcat 9.0.x will run quite happily on any currently supported 
version of Java (and should continue to do so) the EOL for Java 8 isn't really 
relevant to when we stop supporting Tomcat 9.0.x.

Any change in our plans for ongoing 9.0.x support would need some discussion. 
Input from the community would be especially useful.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 9.x end of life

2023-06-08 Thread Mark Thomas 

On 08/06/2023 16:32, Zoltan Balogh wrote:

Dear Apache Team,

I just would like to ask is there any planned EOL for Tomcat 9?


Best guess at the moment (and it is only a guess - no decisions have 
been made) is 3 years after 8.5.x is EOL which gives a date of 31 March 
2027.


It is worth noting that Tomcat major versions track releases of the 
Jakarta Servlet specification and there has been an effort from the 
Jakarta project to increase the release cadence. Delays are also not 
unheard of. The estimate above could easily be a year out in either 
direction.



We are heavily using Java 8 that is supported until 2030, so we expect Apache 
Tomcat 9 will be also support while Java 8 is supported.


That is extremely unlikely at this point.


Important note that Tomcat 9 is the last release that works fine with Java 8 
along with Java EE. Therefore, it is highly important for us to have a 
maintained Tomcat 9 for Java 8.


Once Tomcat 9.0.x reaches EOL we will provide, assuming there is demand, 
Tomcat 9.10.x which will be Tomcat 10.1.x but with the Java EE 8 API. 
The minimum Java requirement for 9.10.x will be Java 11.


Once Tomcat 10.1.x reaches EOL we will provide Tomcat 9.11.x which would 
be Tomcat 11.0.x but with the Java EE 8 API.


And so on.

All our planning to date has assumed that the primary demand would be 
for the newer features (that require newer JREs) supported by newer 
Tomcat versions but with the Java EE 8 API. If that assumption is 
incorrect and the primary demand is for Tomcat 9.0.x that runs on Java 8 
then it is possible that we could just keep supporting Tomcat 9.0.x. 
Given that Tomcat 9.0.x will run quite happily on any currently 
supported version of Java (and should continue to do so) the EOL for 
Java 8 isn't really relevant to when we stop supporting Tomcat 9.0.x.


Any change in our plans for ongoing 9.0.x support would need some 
discussion. Input from the community would be especially useful.


Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Apache Tomcat 9.x end of life

2023-06-08 Thread Zoltan Balogh 
Dear Apache Team,

I just would like to ask is there any planned EOL for Tomcat 9?

We are heavily using Java 8 that is supported until 2030, so we expect Apache 
Tomcat 9 will be also support while Java 8 is supported.

Important note that Tomcat 9 is the last release that works fine with Java 8 
along with Java EE. Therefore, it is highly important for us to have a 
maintained Tomcat 9 for Java 8.

Thanks for your reply!

Kind Regards,

Zoltan Balogh

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-30 Thread Christopher Schultz 

Piyush,

On 8/24/21 23:47, Piyush Sharma wrote:

On Mon, Aug 23, 2021 at 8:29 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:


Piyush,

On 8/22/21 03:54, Piyush Sharma wrote:

On Fri, Aug 20, 2021 at 10:40 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:


Piyush,

On 8/20/21 06:36, Piyush Sharma wrote:


Hello,

I am using Apache Tomcat 9.0.46 version on docker container.

There is a problem, where the base path was wrongly set by automation
script due to which it starts for few seconds, listen port 8080 and

then

stop, due to that container exit after sometime.



Now how can we debug such issue, which shows any error / problem in

tomcat

configuration.

I tried with "jpda start" or "debug" options, but that didn't help me.

Is

there any option to debug tomcat related issues or problems.

"catalina.sh configtest" will show any error in xml or properties but

will

not help to debug tomcat startup problem.

*Note:* I am just deploying with the helloworld war file. nothing much

in

code as of now.


Maybe just fix your automation script to use the right path?

It's hard to understand what the problem is given the information you
have presented.

-chris



Thanks Chris

I have removed automation and harded everything and created a new docker
image.
Now when I try to start the container, it starts for a few seconds and
stops (port 8080 listens for a while). Nothing in logs.

$ catalina.sh run  (tried with "jpda start" or "debug" options as well)
$ ps aux |grep java --> show the process for few seconds
$ netstat -ntpl |grep 8080 --> shows the port for few seconds

I am wondering if I can debug such issues, when it starts for a few

seconds

and then stops. Is there any memory , config file or any other issues?

Any debug option whether tomcat


What do the logs say?

-chris




Hello Chris,

After starting the container in debug mode, I noticed Exit Code 137 which
seems to be OOM (out of memory) issue. Due to which container exit /
terminate.

Is there any other reason for Exit Code 137 ? as I am just starting hello
world application and given 2 GB RAM.


What do the logs say?

-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-24 Thread Piyush Sharma 
On Mon, Aug 23, 2021 at 8:29 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> Piyush,
>
> On 8/22/21 03:54, Piyush Sharma wrote:
> > On Fri, Aug 20, 2021 at 10:40 PM Christopher Schultz <
> > ch...@christopherschultz.net> wrote:
> >
> >> Piyush,
> >>
> >> On 8/20/21 06:36, Piyush Sharma wrote:
> 
>  Hello,
> 
>  I am using Apache Tomcat 9.0.46 version on docker container.
> 
>  There is a problem, where the base path was wrongly set by automation
>  script due to which it starts for few seconds, listen port 8080 and
> then
>  stop, due to that container exit after sometime.
> 
> >>>
> >>> Now how can we debug such issue, which shows any error / problem in
> >> tomcat
>  configuration.
> 
>  I tried with "jpda start" or "debug" options, but that didn't help me.
> >> Is
>  there any option to debug tomcat related issues or problems.
> 
>  "catalina.sh configtest" will show any error in xml or properties but
> >> will
>  not help to debug tomcat startup problem.
> 
>  *Note:* I am just deploying with the helloworld war file. nothing much
> >> in
>  code as of now.
> >>
> >> Maybe just fix your automation script to use the right path?
> >>
> >> It's hard to understand what the problem is given the information you
> >> have presented.
> >>
> >> -chris
> >>
> >>
> > Thanks Chris
> >
> > I have removed automation and harded everything and created a new docker
> > image.
> > Now when I try to start the container, it starts for a few seconds and
> > stops (port 8080 listens for a while). Nothing in logs.
> >
> > $ catalina.sh run  (tried with "jpda start" or "debug" options as well)
> > $ ps aux |grep java --> show the process for few seconds
> > $ netstat -ntpl |grep 8080 --> shows the port for few seconds
> >
> > I am wondering if I can debug such issues, when it starts for a few
> seconds
> > and then stops. Is there any memory , config file or any other issues?
> >
> > Any debug option whether tomcat
>
> What do the logs say?
>
> -chris
>
>

Hello Chris,

After starting the container in debug mode, I noticed Exit Code 137 which
seems to be OOM (out of memory) issue. Due to which container exit /
terminate.

Is there any other reason for Exit Code 137 ? as I am just starting hello
world application and given 2 GB RAM.



-
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

-- 

*Thanks & Regards,*

*Piyush M Sharma*
My Linux Blog 

http://in.linkedin.com/in/linuxboy

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-23 Thread Piyush Sharma 
On Mon, Aug 23, 2021 at 8:29 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> Piyush,
>
> On 8/22/21 03:54, Piyush Sharma wrote:
> > On Fri, Aug 20, 2021 at 10:40 PM Christopher Schultz <
> > ch...@christopherschultz.net> wrote:
> >
> >> Piyush,
> >>
> >> On 8/20/21 06:36, Piyush Sharma wrote:
> 
>  Hello,
> 
>  I am using Apache Tomcat 9.0.46 version on docker container.
> 
>  There is a problem, where the base path was wrongly set by automation
>  script due to which it starts for few seconds, listen port 8080 and
> then
>  stop, due to that container exit after sometime.
> 
> >>>
> >>> Now how can we debug such issue, which shows any error / problem in
> >> tomcat
>  configuration.
> 
>  I tried with "jpda start" or "debug" options, but that didn't help me.
> >> Is
>  there any option to debug tomcat related issues or problems.
> 
>  "catalina.sh configtest" will show any error in xml or properties but
> >> will
>  not help to debug tomcat startup problem.
> 
>  *Note:* I am just deploying with the helloworld war file. nothing much
> >> in
>  code as of now.
> >>
> >> Maybe just fix your automation script to use the right path?
> >>
> >> It's hard to understand what the problem is given the information you
> >> have presented.
> >>
> >> -chris
> >>
> >>
> > Thanks Chris
> >
> > I have removed automation and harded everything and created a new docker
> > image.
> > Now when I try to start the container, it starts for a few seconds and
> > stops (port 8080 listens for a while). Nothing in logs.
> >
> > $ catalina.sh run  (tried with "jpda start" or "debug" options as well)
> > $ ps aux |grep java --> show the process for few seconds
> > $ netstat -ntpl |grep 8080 --> shows the port for few seconds
> >
> > I am wondering if I can debug such issues, when it starts for a few
> seconds
> > and then stops. Is there any memory , config file or any other issues?
> >
> > Any debug option whether tomcat
>
> What do the logs say?


-chris

>
>

Nothing in logs, also I noticed that tomcat starts after multiple retries..
Means it starts successfully 1 time out of 5 times.

Also, I have commented 8005 and 8009 ports.

Don't know what is happening.. at least it should print any error or info.

I have even been given 2 GB RAM which is I guess more than enough to start.




Thanks
Piyush

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-23 Thread Christopher Schultz 

Piyush,

On 8/22/21 03:54, Piyush Sharma wrote:

On Fri, Aug 20, 2021 at 10:40 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:


Piyush,

On 8/20/21 06:36, Piyush Sharma wrote:


Hello,

I am using Apache Tomcat 9.0.46 version on docker container.

There is a problem, where the base path was wrongly set by automation
script due to which it starts for few seconds, listen port 8080 and then
stop, due to that container exit after sometime.



Now how can we debug such issue, which shows any error / problem in

tomcat

configuration.

I tried with "jpda start" or "debug" options, but that didn't help me.

Is

there any option to debug tomcat related issues or problems.

"catalina.sh configtest" will show any error in xml or properties but

will

not help to debug tomcat startup problem.

*Note:* I am just deploying with the helloworld war file. nothing much

in

code as of now.


Maybe just fix your automation script to use the right path?

It's hard to understand what the problem is given the information you
have presented.

-chris



Thanks Chris

I have removed automation and harded everything and created a new docker
image.
Now when I try to start the container, it starts for a few seconds and
stops (port 8080 listens for a while). Nothing in logs.

$ catalina.sh run  (tried with "jpda start" or "debug" options as well)
$ ps aux |grep java --> show the process for few seconds
$ netstat -ntpl |grep 8080 --> shows the port for few seconds

I am wondering if I can debug such issues, when it starts for a few seconds
and then stops. Is there any memory , config file or any other issues?

Any debug option whether tomcat


What do the logs say?

-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-23 Thread Peter Chamberlain 
On Sun, 22 Aug 2021 at 08:55, Piyush Sharma  wrote:
>
> On Fri, Aug 20, 2021 at 10:40 PM Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> > Piyush,
> >
> > On 8/20/21 06:36, Piyush Sharma wrote:
> > >>
> > >> Hello,
> > >>
> > >> I am using Apache Tomcat 9.0.46 version on docker container.
> > >>
> > >> There is a problem, where the base path was wrongly set by automation
> > >> script due to which it starts for few seconds, listen port 8080 and then
> > >> stop, due to that container exit after sometime.
> > >>
> > >
> > > Now how can we debug such issue, which shows any error / problem in
> > tomcat
> > >> configuration.
> > >>
> > >> I tried with "jpda start" or "debug" options, but that didn't help me.
> > Is
> > >> there any option to debug tomcat related issues or problems.
> > >>
> > >> "catalina.sh configtest" will show any error in xml or properties but
> > will
> > >> not help to debug tomcat startup problem.
> > >>
> > >> *Note:* I am just deploying with the helloworld war file. nothing much
> > in
> > >> code as of now.
> >
> > Maybe just fix your automation script to use the right path?
> >
> > It's hard to understand what the problem is given the information you
> > have presented.
> >
> > -chris
> >
> >
> Thanks Chris
>
> I have removed automation and harded everything and created a new docker
> image.
> Now when I try to start the container, it starts for a few seconds and
> stops (port 8080 listens for a while). Nothing in logs.
>
> $ catalina.sh run  (tried with "jpda start" or "debug" options as well)
> $ ps aux |grep java --> show the process for few seconds
> $ netstat -ntpl |grep 8080 --> shows the port for few seconds
>
> I am wondering if I can debug such issues, when it starts for a few seconds
> and then stops. Is there any memory , config file or any other issues?
>
> Any debug option whether tomcat
>
>
> Thanks
> Piyush

Could it be a clash of port or similar for the shutdown port, or maybe
another port, eg, in server.xml:
Server port="8005"

Best regards, Peter

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-22 Thread Piyush Sharma 
On Fri, Aug 20, 2021 at 10:40 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> Piyush,
>
> On 8/20/21 06:36, Piyush Sharma wrote:
> >>
> >> Hello,
> >>
> >> I am using Apache Tomcat 9.0.46 version on docker container.
> >>
> >> There is a problem, where the base path was wrongly set by automation
> >> script due to which it starts for few seconds, listen port 8080 and then
> >> stop, due to that container exit after sometime.
> >>
> >
> > Now how can we debug such issue, which shows any error / problem in
> tomcat
> >> configuration.
> >>
> >> I tried with "jpda start" or "debug" options, but that didn't help me.
> Is
> >> there any option to debug tomcat related issues or problems.
> >>
> >> "catalina.sh configtest" will show any error in xml or properties but
> will
> >> not help to debug tomcat startup problem.
> >>
> >> *Note:* I am just deploying with the helloworld war file. nothing much
> in
> >> code as of now.
>
> Maybe just fix your automation script to use the right path?
>
> It's hard to understand what the problem is given the information you
> have presented.
>
> -chris
>
>
Thanks Chris

I have removed automation and harded everything and created a new docker
image.
Now when I try to start the container, it starts for a few seconds and
stops (port 8080 listens for a while). Nothing in logs.

$ catalina.sh run  (tried with "jpda start" or "debug" options as well)
$ ps aux |grep java --> show the process for few seconds
$ netstat -ntpl |grep 8080 --> shows the port for few seconds

I am wondering if I can debug such issues, when it starts for a few seconds
and then stops. Is there any memory , config file or any other issues?

Any debug option whether tomcat


Thanks
Piyush

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-20 Thread Christopher Schultz 

Piyush,

On 8/20/21 06:36, Piyush Sharma wrote:


Hello,

I am using Apache Tomcat 9.0.46 version on docker container.

There is a problem, where the base path was wrongly set by automation
script due to which it starts for few seconds, listen port 8080 and then
stop, due to that container exit after sometime.



Now how can we debug such issue, which shows any error / problem in tomcat

configuration.

I tried with "jpda start" or "debug" options, but that didn't help me. Is
there any option to debug tomcat related issues or problems.

"catalina.sh configtest" will show any error in xml or properties but will
not help to debug tomcat startup problem.

*Note:* I am just deploying with the helloworld war file. nothing much in
code as of now.


Maybe just fix your automation script to use the right path?

It's hard to understand what the problem is given the information you 
have presented.


-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 9 | Tomcat starting issue

2021-08-20 Thread Piyush Sharma 
>
> Hello,
>
> I am using Apache Tomcat 9.0.46 version on docker container.
>
> There is a problem, where the base path was wrongly set by automation
> script due to which it starts for few seconds, listen port 8080 and then
> stop, due to that container exit after sometime.
>

Now how can we debug such issue, which shows any error / problem in tomcat
> configuration.
>
> I tried with "jpda start" or "debug" options, but that didn't help me. Is
> there any option to debug tomcat related issues or problems.
>
> "catalina.sh configtest" will show any error in xml or properties but will
> not help to debug tomcat startup problem.
>
> *Note:* I am just deploying with the helloworld war file. nothing much in
> code as of now.
>
> Thanks
> Piyush
>

Re: Updating Oracle JDK or JRE from 1.8.0-1.8.0_291 to 1.8.0-1.8.0_301, Breaks Apache Tomcat 9 Connector Http11AprProtocol

2021-08-03 Thread Ray, Kevin L CIV USN FLEWEACEN NORFOLK VA (USA) 
>>Apache Tomcat 9.0.50 (Also issue with 9.0.44)

>>Oracle JDK and JRE 1.8.0-1.8.0_301

>>Red Hat Enterprise Linux Server release 7.9



>>When updating JDK/JRE from build 1.8.0_291-b10 to 1.8.0_301-b09, Apache

>>Tomcat Connector (org.apache.coyote.http11.Http11AprProtocol) failed to load

>>server key and failed to start. Tomcat ran without issues prior to the

>>upgrade.

>>Issue seems to be tied to the JVM and OpenSSL. We created a connector using

>>org.apache.coyote.http11.Http11Nio2Protocol and JSSE (No OpenSSL) and was

>>able to start without issue. However this configuration does not satisfy all

>>of our requirements.



>>Stack Trace:



>>27-Jul-2021 16:34:12.451 SEVERE [main]

>>org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to

>>initialize component

>> [Connector[org.apache.coyote.http11.Http11AprProtocol-443]]

>>org.apache.catalina.LifecycleException: Protocol handler

>>initialization failed

>>at

>>org.apache.catalina.connector.Connector.initInternal(Connector.java:1049)

>>at

>>org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

>>at

>>org.apache.catalina.core.StandardService.initInternal(StandardService.java:5

>>61)

>>at

>>org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

>>at

>>org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:104

>>9)

>>at

>>org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

>>at

>>org.apache.catalina.startup.Catalina.load(Catalina.java:724)

>>at

>>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

>>at

>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62

>>)

>>at

>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl

>>.java:43)

>>at

>>java.lang.reflect.Method.invoke(Method.java:498)







>>Has anyone else run into this issue and if so, have you been able to resolve

>>the issue?



>>Very Respectfully,

>>Kevin Ray



>Michael 
>Osipov
> Sun, 01 Aug 2021 04:22:28 
>-0700

>https://bugs.openjdk.java.net/browse/JDK-8202837
>https://www.oracle.com/java/technologies/javase/8u301-bugfixes.html

>What now?



Michael,

We have seen the but reports/fixes. We are trying to find if others have run 
into this issue and if so, have they been able to resolve or work around the 
issue?



Thank

Kevin R.

Re: Updating Oracle JDK or JRE from 1.8.0-1.8.0_291 to 1.8.0-1.8.0_301, Breaks Apache Tomcat 9 Connector Http11AprProtocol

2021-08-01 Thread Michael Osipov 

https://bugs.openjdk.java.net/browse/JDK-8202837
https://www.oracle.com/java/technologies/javase/8u301-bugfixes.html

What now?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Updating Oracle JDK or JRE from 1.8.0-1.8.0_291 to 1.8.0-1.8.0_301, Breaks Apache Tomcat 9 Connector Http11AprProtocol

2021-07-28 Thread Ray, Kevin L CIV USN FLEWEACEN NORFOLK VA (USA) 
Apache Tomcat 9.0.50 (Also issue with 9.0.44)

Oracle JDK and JRE 1.8.0-1.8.0_301

Red Hat Enterprise Linux Server release 7.9

 

When updating JDK/JRE from build 1.8.0_291-b10 to 1.8.0_301-b09, Apache
Tomcat Connector (org.apache.coyote.http11.Http11AprProtocol) failed to load
server key and failed to start. Tomcat ran without issues prior to the
upgrade. 
Issue seems to be tied to the JVM and OpenSSL. We created a connector using
org.apache.coyote.http11.Http11Nio2Protocol and JSSE (No OpenSSL) and was
able to start without issue. However this configuration does not satisfy all
of our requirements.

Stack Trace:

27-Jul-2021 16:34:12.053 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache
Tomcat Native library [1.2.14] using APR version [1.4.8].

27-Jul-2021 16:34:12.053 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
capabilities: IPv6 [true], sendfile [true], accept filters [false], random
[true], UDS [false].

27-Jul-2021 16:34:12.053 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL
configuration: useAprConnector [false], useOpenSSL [true]

27-Jul-2021 16:34:12.056 INFO [main]
org.apache.catalina.core.AprLifecycleListener.initializeSSL Already in FIPS
mode; skipping FIPS initialization.

27-Jul-2021 16:34:12.056 INFO [main]
org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]

27-Jul-2021 16:34:12.389 INFO [main] org.apache.coyote.AbstractProtocol.init
Initializing ProtocolHandler ["http-nio-127.0.0.1-8080"]

27-Jul-2021 16:34:12.407 INFO [main] org.apache.coyote.AbstractProtocol.init
Initializing ProtocolHandler ["https-openssl-apr-XXX.XXX.XXX.XXX-443"]

27-Jul-2021 16:34:12.451 SEVERE [main]
org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to
initialize component
[Connector[org.apache.coyote.http11.Http11AprProtocol-443]]

org.apache.catalina.LifecycleException: Protocol handler
initialization failed

at
org.apache.catalina.connector.Connector.initInternal(Connector.java:1049)

at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:5
61)

at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:104
9)

at
org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

at
org.apache.catalina.startup.Catalina.load(Catalina.java:724)

at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62
)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:43)

at
java.lang.reflect.Method.invoke(Method.java:498)

at
org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:305)

at
org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:331)

at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62
)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:43)

at
java.lang.reflect.Method.invoke(Method.java:498)

at
org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:210)

Caused by: java.lang.IllegalArgumentException:
1.2.840.113549.1.5.13 SecretKeyFactory not available

at
org.apache.tomcat.util.net.AprEndpoint.createSSLContext(AprEndpoint.java:461
)

at
org.apache.tomcat.util.net.AprEndpoint.bind(AprEndpoint.java:425)

at
org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint
.java:1208)

at
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1221)

at
org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:603)

at
org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.
java:80)

at
org.apache.catalina.connector.Connector.initInternal(Connector.java:1046)

... 17 more

Caused by: java.security.NoSuchAlgorithmException:
1.2.840.113549.1.5.13 Secret

Re: EOL of Apache Tomcat 9

2020-02-14 Thread Christopher Schultz 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Reneesh,

On 2/14/20 12:27, Reneesh K wrote:
> Thanks again. Last question what is the EOL for 8.5.x?

Also currently unknown. Tomcat 7.0.x is still supported but will
likely have a known EOL date when Tomcat 10 is released "stable".

You have plenty of time for 8.5.x, but I would look toward migrating
to Tomcat 9 over the next few years.

- -chris

> On Fri, Feb 14, 2020 at 8:10 AM Mark Thomas 
> wrote:
>
>> On 14/02/2020 14:08, Reneesh K wrote:
>>> Thank you Mark. And just to confirm the EOL for 8.x is 30 June
>>> 2018?
>>
>> 8.0.x yes.
>>
>> 8.5.x is still supported.
>>
>> Mark
>>
>>
>>>
>>> Best Regards, Reneesh K
>>>
>>>
>>> On Fri, Feb 14, 2020 at 7:56 AM Mark Thomas 
>>> wrote:
>>>
>>>> On 13/02/2020 21:30, Reneesh K wrote:
>>>>> Team,
>>>>>
>>>>> What is the EOL Date for Apache Tomcat 9?
>>>>
>>>> Currently unknown.
>>>>
>>>> EOL for 5.x was 30 Sep 2012 EOL for 6.x was 31 Dec 2016
>>>>
>>>> EOL for 7.x is probably going to be 31 Mar 2021
>>>>
>>>> So roughly, there are ~4 years between EOL for major
>>>> versions. That puts an estimate for EOL of 9.0.x some time in
>>>> 2029.
>>>>
>>>> An additional complication is that Tomcat 9 is the last
>>>> version to support Java EE (Tomcat 10 onwards will support
>>>> Jakarta EE) so the intention is to continue support for
>>>> Tomcat 9 for longer - if there is demand for a Java EE
>>>> platform.
>>>>
>>>> Mark
>>>>
>>>> ---
- --
>>>>
>>>>
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>>> For additional commands, e-mail:
>>>> users-h...@tomcat.apache.org
>>>>
>>>>
>>>
>>
>>
>> -
>>
>>
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl5G6J8ACgkQHPApP6U8
pFhyhhAAqlL7BVBPGvoHU12CibceBELQip34bDjUIK/9tC03AijNicEsjfTswwyA
Nkk4ywP7zNEKswJ6aDlh1uHJXbC6DMRjibkIiOajxo6uvAkIbvSU/KlV0GqVtJ6T
LLF0o2Kt9o4M7PnmBCJa2mLdk8bVUCS++xvsJeQBuv3RRY37IQrX8YaKqFss6/0C
7CE7WKGl1nLQJ/SYvHUwSet3pglELVGbsHglczETliCZhv0Yfj95l80qYlbSLZAW
HFe9ZnOvzdPeIJgM7KVyFwaiS00L9/A115vbxgD5dacfCoCVaOpxxOur/R3k4PQS
osmVQGYeRORmK0HdG2UifBxFRh43MBbrectoIQwZeYBSE99/SN0r5YXD8OnJ3FQX
X4RD1CeoSrQHl/j8ZX94EoemqIo9zGiW30lppf3H5NyG78+S2WfAUjpdymgeQmIC
qw8Ui3Z6O2rFA3WAT+R6kUzEoyCrG1kPsi3lFkwekI6iDEgA9nzXbgi46UfmNQQX
MWtgAwNOTmuX6c6yF6l2/LtyIcM6IhYuakJrfLBSI8h7U4NLBgU1zf1MKROjbLWK
vnqToL4I+GOWQ1Obv2pWyrLBh140LixF3ETEjIjuDtKETK640ogizge63e6H+kYU
lSMyPlup5mMU8shrK6w7W2UfzRPCZY0yVgLjk74NZngRvyrgXfY=
=3zwK
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: EOL of Apache Tomcat 9

2020-02-14 Thread Reneesh K 
Thanks again. Last question what is the EOL for 8.5.x?

Best Regards,
Reneesh K


On Fri, Feb 14, 2020 at 8:10 AM Mark Thomas  wrote:

> On 14/02/2020 14:08, Reneesh K wrote:
> > Thank you Mark. And just to confirm the EOL for 8.x is 30 June 2018?
>
> 8.0.x yes.
>
> 8.5.x is still supported.
>
> Mark
>
>
> >
> > Best Regards,
> > Reneesh K
> >
> >
> > On Fri, Feb 14, 2020 at 7:56 AM Mark Thomas  wrote:
> >
> >> On 13/02/2020 21:30, Reneesh K wrote:
> >>>  Team,
> >>>
> >>> What is the EOL Date for Apache Tomcat 9?
> >>
> >> Currently unknown.
> >>
> >> EOL for 5.x was 30 Sep 2012
> >> EOL for 6.x was 31 Dec 2016
> >>
> >> EOL for 7.x is probably going to be 31 Mar 2021
> >>
> >> So roughly, there are ~4 years between EOL for major versions. That puts
> >> an estimate for EOL of 9.0.x some time in 2029.
> >>
> >> An additional complication is that Tomcat 9 is the last version to
> >> support Java EE (Tomcat 10 onwards will support Jakarta EE) so the
> >> intention is to continue support for Tomcat 9 for longer - if there is
> >> demand for a Java EE platform.
> >>
> >> Mark
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: EOL of Apache Tomcat 9

2020-02-14 Thread Mark Thomas 
On 14/02/2020 14:08, Reneesh K wrote:
> Thank you Mark. And just to confirm the EOL for 8.x is 30 June 2018?

8.0.x yes.

8.5.x is still supported.

Mark


> 
> Best Regards,
> Reneesh K
> 
> 
> On Fri, Feb 14, 2020 at 7:56 AM Mark Thomas  wrote:
> 
>> On 13/02/2020 21:30, Reneesh K wrote:
>>>  Team,
>>>
>>> What is the EOL Date for Apache Tomcat 9?
>>
>> Currently unknown.
>>
>> EOL for 5.x was 30 Sep 2012
>> EOL for 6.x was 31 Dec 2016
>>
>> EOL for 7.x is probably going to be 31 Mar 2021
>>
>> So roughly, there are ~4 years between EOL for major versions. That puts
>> an estimate for EOL of 9.0.x some time in 2029.
>>
>> An additional complication is that Tomcat 9 is the last version to
>> support Java EE (Tomcat 10 onwards will support Jakarta EE) so the
>> intention is to continue support for Tomcat 9 for longer - if there is
>> demand for a Java EE platform.
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: EOL of Apache Tomcat 9

2020-02-14 Thread Reneesh K 
Thank you Mark. And just to confirm the EOL for 8.x is 30 June 2018?

Best Regards,
Reneesh K


On Fri, Feb 14, 2020 at 7:56 AM Mark Thomas  wrote:

> On 13/02/2020 21:30, Reneesh K wrote:
> >  Team,
> >
> > What is the EOL Date for Apache Tomcat 9?
>
> Currently unknown.
>
> EOL for 5.x was 30 Sep 2012
> EOL for 6.x was 31 Dec 2016
>
> EOL for 7.x is probably going to be 31 Mar 2021
>
> So roughly, there are ~4 years between EOL for major versions. That puts
> an estimate for EOL of 9.0.x some time in 2029.
>
> An additional complication is that Tomcat 9 is the last version to
> support Java EE (Tomcat 10 onwards will support Jakarta EE) so the
> intention is to continue support for Tomcat 9 for longer - if there is
> demand for a Java EE platform.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: EOL of Apache Tomcat 9

2020-02-14 Thread Mark Thomas 
On 13/02/2020 21:30, Reneesh K wrote:
>  Team,
> 
> What is the EOL Date for Apache Tomcat 9?

Currently unknown.

EOL for 5.x was 30 Sep 2012
EOL for 6.x was 31 Dec 2016

EOL for 7.x is probably going to be 31 Mar 2021

So roughly, there are ~4 years between EOL for major versions. That puts
an estimate for EOL of 9.0.x some time in 2029.

An additional complication is that Tomcat 9 is the last version to
support Java EE (Tomcat 10 onwards will support Jakarta EE) so the
intention is to continue support for Tomcat 9 for longer - if there is
demand for a Java EE platform.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

EOL of Apache Tomcat 9

2020-02-13 Thread Reneesh K 
 Team,

What is the EOL Date for Apache Tomcat 9?

Best Regards,
Reneesh K

Re: Apache Tomcat 9

2017-03-09 Thread tomcat 

On 10.03.2017 00:24, pina.freder...@gmail.com wrote:

How do I stop it ?


Close the lid of your laptop ?

(Sorry, could not stop myself)



Sent from Mail for Windows 10

From: Caldarale, Charles R
Sent: Thursday, March 9, 2017 6:16 PM
To: Tomcat Users List
Subject: RE: Apache Tomcat 9


From: pina.freder...@gmail.com [mailto:pina.freder...@gmail.com]
Subject: Apache Tomcat 9




I'm trying to teach myself Java Web App Development but can't seem to get this 
issue resolved.



Mar 09, 2017 5:44:17 PM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[localhost:8080]:
java.net.BindException: Address already in use: JVM_Bind


You already have something on your laptop that's using port 8080.  Either stop 
running that program, or configure your Tomcat to use a different port in the 
 element of server.xml.

  - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 9

2017-03-09 Thread calder 
>> From: pina.freder...@gmail.com [mailto:pina.freder...@gmail.com]
>> Subject: Apache Tomcat 9
>
>
>> I'm trying to teach myself Java Web App Development but can't seem to get 
>> this issue resolved.
>
>> Mar 09, 2017 5:44:17 PM org.apache.catalina.core.StandardServer await
>> SEVERE: StandardServer.await: create[localhost:8080]:
>> java.net.BindException: Address already in use: JVM_Bind

>> From: Caldarale, Charles R
>> Sent: Thursday, March 9, 2017 6:16 PM
>> To: Tomcat Users List
> Subject: RE: Apache Tomcat 9
>
> You already have something on your laptop that's using port 8080.  Either 
> stop running that program, or configure your Tomcat to use a different port 
> in the  element of server.xml.
>
>  - Chuck

On Thu, Mar 9, 2017 at 11:24 PM,   wrote:
> How do I stop it ?
>

Please don't top-post. I've fixed your reply.

If the "other" application is running as a Windows Service, then stop
the Service.

If you've run the "other" application from the command-line, then
usually you can do a  at the keyboard to stop the process.

If the application has run off as a rogue process, then use Task
Manager to kill it.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Apache Tomcat 9

2017-03-09 Thread pina.frederick 
How do I stop it ?

Sent from Mail for Windows 10

From: Caldarale, Charles R
Sent: Thursday, March 9, 2017 6:16 PM
To: Tomcat Users List
Subject: RE: Apache Tomcat 9

> From: pina.freder...@gmail.com [mailto:pina.freder...@gmail.com] 
> Subject: Apache Tomcat 9


> I'm trying to teach myself Java Web App Development but can't seem to get 
> this issue resolved.

> Mar 09, 2017 5:44:17 PM org.apache.catalina.core.StandardServer await
> SEVERE: StandardServer.await: create[localhost:8080]: 
> java.net.BindException: Address already in use: JVM_Bind

You already have something on your laptop that's using port 8080.  Either stop 
running that program, or configure your Tomcat to use a different port in the 
 element of server.xml.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Apache Tomcat 9

2017-03-09 Thread Caldarale, Charles R 
> From: pina.freder...@gmail.com [mailto:pina.freder...@gmail.com] 
> Subject: Apache Tomcat 9


> I'm trying to teach myself Java Web App Development but can't seem to get 
> this issue resolved.

> Mar 09, 2017 5:44:17 PM org.apache.catalina.core.StandardServer await
> SEVERE: StandardServer.await: create[localhost:8080]: 
> java.net.BindException: Address already in use: JVM_Bind

You already have something on your laptop that's using port 8080.  Either stop 
running that program, or configure your Tomcat to use a different port in the 
 element of server.xml.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Apache Tomcat 9

2017-03-09 Thread pina.frederick 
Hello ! I’m trying to teach myself Java Web App Development but can’t seem to 
get this issue resolved. Can anyone give me a few hints ? I’m using a Windows 
10 Hope laptop with Eclipse Neon 2 IDE. Thanks. 

Mar 09, 2017 5:44:16 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting 
property 'source' to 'org.eclipse.jst.jee.server:helloworld' did not find a 
matching property.
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version:Apache Tomcat/9.0.0.M17
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:  Jan 10 2017 20:59:20 UTC
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 9.0.0.0
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:   Windows 10
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:10.0
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:  amd64
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home: C:\Program Files\Java\jre1.8.0_121
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:   1.8.0_121-b13
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:Oracle Corporation
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: 
C:\Users\fpina\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: C:\Program Files\Apache Software Foundation\Tomcat 
9.0
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dcatalina.base=C:\Users\fpina\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=C:\Program Files\Apache Software 
Foundation\Tomcat 9.0
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dwtp.deploy=C:\Users\fpina\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=C:\Program Files\Apache 
Software Foundation\Tomcat 9.0\endorsed
Mar 09, 2017 5:44:16 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dfile.encoding=Cp1252
Mar 09, 2017 5:44:16 PM org.apache.catalina.core.AprLifecycleListener 
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal 
performance in production environments was not found on the java.library.path: 
C:\Program 
Files\Java\jre1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Program
 Files/Java/jre1.8.0_121/bin/server;C:/Program 
Files/Java/jre1.8.0_121/bin;C:/Program 
Files/Java/jre1.8.0_121/lib/amd64;C:\Program Files (x86)\Common 
Files\Intel\Shared Files\cpp\bin\Intel64;C:\Program Files 
(x86)\Embarcadero\Studio\18.0\bin;C:\Users\Public\Documents\Embarcadero\Studio\18.0\Bpl;C:\Program
 Files 
(x86)\Embarcadero\Studio\18.0\bin64;C:\Users\Public\Documents\Embarcadero\Studio\18.0\Bpl\Win64;C:\ProgramData\Oracle\Java\javapath;C:\Program
 Files\Microsoft MPI\Bin\;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program 
Files\Intel\iCLS 
Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program
 Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program 
Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files 
(x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program 
Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files 
(x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program 
Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program 
Files\Anaconda3;C:\Program Files\Anaconda3\Scripts;C:\Program 
Files\Anaconda3\Library\bin;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program 
Files (x86)\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files 
(x86)\Microsoft SQL Server\130\DTS\Binn\;C:\Program Files\Microsoft SQL 
Server\130\DTS\Binn\;C:\Program Files\Microsoft SQL Server\Client 
SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\Client 
SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL 
Server\130\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL 
Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL 
Server\120\DTS\Binn\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common 
Files\Intel\Wire

Re: Apache Tomcat 9

2016-05-06 Thread Daniel Savard 
2016-05-06 14:27 GMT-04:00 Frederick Piña :

> Hi ! I'm using Tomcat Controller. It works fine (turning off/on, etc).
> However, after the confirmation page on my browser is shown; from Apache
> Tomcat 9; I still can't get the Java Web Application to load.
>
> Apache Tomcat 9 is working fine... But I'm also getting this error:
>
> *Caused by: java.net.BindException: Address already in use *
>
>
>
Address already in use means what it says. Either another Tomcat process is
already using the IP and port number specified in your server.xml file,
either another process not related to Tomcat is already using this IP and
port number.

It may happen if you start two instances of Tomcat with the same
configuration.

Re: Apache Tomcat 9

2016-05-06 Thread Frederick Piña 
Hi ! I'm using Tomcat Controller. It works fine (turning off/on, etc). 
However, after the confirmation page on my browser is shown; from Apache 
Tomcat 9; I still can't get the Java Web Application to load.


Apache Tomcat 9 is working fine... But I'm also getting this error:

*Caused by: java.net.BindException: Address already in use *

On 5/6/16 2:22 PM, prashant sharma wrote:

On Fri, May 6, 2016 at 7:17 PM, Frederick Piña 
wrote:


I'm having errors:

/usr/local/apache-tomcat-9.0.0.M4/bin/catalina.sh run
Configuration Error: deployment source 'SimpleJavaWebApp:war exploded' is
not valid
[2016-05-06 01:50:26,222] Artifact SimpleJavaWebApp:war exploded: Error
during artifact deployment. See server log for details.
06-May-2016 13:50:30.839 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version:
   Apache Tomcat/9.0.0.M4
06-May-2016 13:50:30.851 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server built:
   Mar 12 2016 11:39:59 UTC
06-May-2016 13:50:30.852 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server number:
  9.0.0.0
06-May-2016 13:50:30.852 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Name:
  Mac OS X
06-May-2016 13:50:30.853 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Version:
   10.11.4
06-May-2016 13:50:30.853 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Architecture:
   x86_64
06-May-2016 13:50:30.853 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Java Home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/jre
06-May-2016 13:50:30.854 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Version:
  1.8.0_91-b14
06-May-2016 13:50:30.855 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:
   Oracle Corporation
06-May-2016 13:50:30.856 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:
/Users/frederickpina/Library/Caches/IntelliJIdea2016.1/tomcat/Tomcat_9_0_0_M4_SimpleJavaWebApp
06-May-2016 13:50:30.856 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:
  /usr/local/apache-tomcat-9.0.0.M4
06-May-2016 13:50:30.858 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Djava.util.logging.config.file=/Users/frederickpina/Library/Caches/IntelliJIdea2016.1/tomcat/Tomcat_9_0_0_M4_SimpleJavaWebApp/conf/logging.properties
06-May-2016 13:50:30.858 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
06-May-2016 13:50:30.858 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcom.sun.management.jmxremote=
06-May-2016 13:50:30.859 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcom.sun.management.jmxremote.port=1099
06-May-2016 13:50:30.859 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcom.sun.management.jmxremote.ssl=false
06-May-2016 13:50:30.860 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcom.sun.management.jmxremote.authenticate=false
06-May-2016 13:50:30.860 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.rmi.server.hostname=127.0.0.1
06-May-2016 13:50:30.860 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Dcatalina.base=/Users/frederickpina/Library/Caches/IntelliJIdea2016.1/tomcat/Tomcat_9_0_0_M4_SimpleJavaWebApp
06-May-2016 13:50:30.871 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.home=/usr/local/apache-tomcat-9.0.0.M4
06-May-2016 13:50:30.871 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.io.tmpdir=/usr/local/apache-tomcat-9.0.0.M4/temp
06-May-2016 13:50:30.872 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based
Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/Users/frederickpina/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
06-May-2016 13:50:31.613 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
["http-nio-8009"]
06-May-2016 13:50:31.679 SEVERE [main]
org.apache.coyote.AbstractProtocol.init Failed to initialize end point
associated with ProtocolHandler ["http-nio-8009"]
  java.net.BindException: Address already in use

I believe that means tomcat is already running on your machine. Can you try
killing all tomcat processes and run it again?

 at sun.nio.ch.Net.bind0(Native Method)

 at sun.nio.ch.Net.bind(Net.java:433)
 at su

Re: Apache Tomcat 9

2016-05-06 Thread prashant sharma 
g ProtocolHandler
> [ajp-nio-50922]
> 06-May-2016 13:50:32.044 INFO [main]
> org.apache.catalina.startup.Catalina.start Server startup in 309 ms
> Connected to server
> Configuration Error: deployment source 'SimpleJavaWebApp:war exploded' is
> not valid
> [2016-05-06 01:50:32,418] Artifact SimpleJavaWebApp:war exploded: Error
> during artifact deployment. See server log for details.
> 06-May-2016 13:50:42.023 INFO [localhost-startStop-1]
> org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
> application directory /usr/local/apache-tomcat-9.0.0.M4/webapps/manager
> 06-May-2016 13:50:42.625 INFO [localhost-startStop-1]
> org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web
> application directory /usr/local/apache-tomcat-9.0.0.M4/webapps/manager has
> finished in 601 ms
>
>
>
> On 5/6/16 2:01 PM, Mark Thomas wrote:
>
>> On 06/05/2016 17:50, Frederick Piña wrote:
>>
>>> Hi ! I'm having an issue with my Apache Tomcat 9 and the new IntelliJ
>>> 2016.1
>>>
>>> It seems that the Tomcat was properly installed, yet I can't compile my
>>> Java Web Application on the server. It's a strange issue.
>>>
>>> Can someone assist me ?
>>>
>> Sure, just as soon as the fog clears in my crystal ball so I can see
>> what error you are getting.
>>
>> Mark
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>

Re: Apache Tomcat 9

2016-05-06 Thread Frederick Piña 
tractHttp11Protocol.java:66)
at 
org.apache.catalina.connector.Connector.initInternal(Connector.java:1010)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at 
org.apache.catalina.core.StandardService.initInternal(StandardService.java:549)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at 
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:873)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.startup.Catalina.load(Catalina.java:606)
at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)

06-May-2016 13:50:31.684 SEVERE [main] 
org.apache.catalina.core.StandardService.initInternal Failed to 
initialize connector [Connector[HTTP/1.1-8009]]
 org.apache.catalina.LifecycleException: Failed to initialize component 
[Connector[HTTP/1.1-8009]]

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:112)
at 
org.apache.catalina.core.StandardService.initInternal(StandardService.java:549)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at 
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:873)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
at org.apache.catalina.startup.Catalina.load(Catalina.java:606)
at org.apache.catalina.startup.Catalina.load(Catalina.java:629)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:311)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:494)
Caused by: org.apache.catalina.LifecycleException: Protocol handler 
initialization failed
at 
org.apache.catalina.connector.Connector.initInternal(Connector.java:1013)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)
... 12 more
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:245)
at 
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:798)

at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:547)
at 
org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:66)
at 
org.apache.catalina.connector.Connector.initInternal(Connector.java:1010)

... 13 more

06-May-2016 13:50:31.686 INFO [main] 
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler 
["ajp-nio-50922"]
06-May-2016 13:50:31.721 INFO [main] 
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a 
shared selector for servlet write/read
06-May-2016 13:50:31.733 INFO [main] 
org.apache.catalina.startup.Catalina.load Initialization processed in 
2461 ms
06-May-2016 13:50:31.997 INFO [main] 
org.apache.catalina.core.StandardService.startInternal Starting service 
Catalina
06-May-2016 13:50:31.997 INFO [main] 
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet 
Engine: Apache Tomcat/9.0.0.M4
06-May-2016 13:50:32.016 INFO [main] 
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
[ajp-nio-50922]
06-May-2016 13:50:32.044 INFO [main] 
org.apache.catalina.startup.Catalina.start Server startup in 309 ms

Connected to server
Configuration Error: deployment source 'SimpleJavaWebApp:war exploded' 
is not valid
[2016-05-06 01:50:32,418] Artifact SimpleJavaWebApp:war exploded: Error 
during artifact deployment. See server log for details.
06-May-2016 13:50:42.023 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
application directory /usr/local/apache-tomcat-9.0.0.M4/webapps/manager
06-May-2016 13:50:42.625 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web 
application directory /usr/local/apache-tomcat-9.0.0.M4/webapps/manager 
has finished in 601 ms



On 5/6/16 2:01 PM, Mark Thomas wrote:

On 06/05/2016 17:50, Frederick Piña wrote:

Hi !

Re: Apache Tomcat 9

2016-05-06 Thread Mark Thomas 
On 06/05/2016 17:50, Frederick Piña wrote:
> Hi ! I'm having an issue with my Apache Tomcat 9 and the new IntelliJ
> 2016.1
> 
> It seems that the Tomcat was properly installed, yet I can't compile my
> Java Web Application on the server. It's a strange issue.
> 
> Can someone assist me ?

Sure, just as soon as the fog clears in my crystal ball so I can see
what error you are getting.

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Apache Tomcat 9

2016-05-06 Thread Frederick Piña 

Hi ! I'm having an issue with my Apache Tomcat 9 and the new IntelliJ 2016.1

It seems that the Tomcat was properly installed, yet I can't compile my 
Java Web Application on the server. It's a strange issue.


Can someone assist me ?

WebEx meeting changed: Apache Tomcat 9: HTTP/2 quick start

2015-11-19 Thread Mark Thomas 

Hello,

Mark Thomas changed the WebEx meeting information.


Apache Tomcat 9: HTTP/2 quick start
Tuesday, 24 November 2015
20:00  |  GMT Time (London, GMT)  |  1 hr


JOIN WEBEX MEETING
https://pivotal.webex.com/pivotal/j.php?MTID=mc659a2f2bf4a68cd94ea0a3e702de9a7
Meeting number: 649 296 162


JOIN BY PHONE
Call-in toll-free number: 1-877-8818371  (US)
Call-in number: 1-617-3374371  (US)
Show global numbers:
https://sites.google.com/a/pivotal.io/pivotal-it/pivotal-conferencing
Attendee access code: 289 459 03



Add this meeting to your calendar:
https://pivotal.webex.com/pivotal/j.php?MTID=m4dbdc76580d9af7383b6468ac36c1a68


Can't join the meeting? Contact support here:
https://pivotal.webex.com/pivotal/mc


IMPORTANT NOTICE: Please note that this WebEx service allows audio and other 
information sent during the session to be recorded, which may be discoverable 
in a legal matter. By joining this session, you automatically consent to such 
recordings. If you do not consent to being recorded, discuss your concerns with 
the host or do not join the session.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

WebEx meeting changed: Apache Tomcat 9: HTTP/2 quick start

2015-11-19 Thread Mark Thomas 

Hello,

Mark Thomas changed the WebEx meeting information.


Apache Tomcat 9: HTTP/2 quick start
Tuesday, 24 November 2015
10:00  |  GMT Time (London, GMT)  |  1 hr


JOIN WEBEX MEETING
https://pivotal.webex.com/pivotal/j.php?MTID=mfa085250004a720ae2cbf026fc2249fa
Meeting number: 646 025 783


JOIN BY PHONE
Call-in toll-free number: 1-877-8818371  (US)
Call-in number: 1-617-3374371  (US)
Show global numbers:
https://sites.google.com/a/pivotal.io/pivotal-it/pivotal-conferencing
Attendee access code: 289 459 03



Add this meeting to your calendar:
https://pivotal.webex.com/pivotal/j.php?MTID=m97cccbc4b3d2a27722a0dcea8377113c


Can't join the meeting? Contact support here:
https://pivotal.webex.com/pivotal/mc


IMPORTANT NOTICE: Please note that this WebEx service allows audio and other 
information sent during the session to be recorded, which may be discoverable 
in a legal matter. By joining this session, you automatically consent to such 
recordings. If you do not consent to being recorded, discuss your concerns with 
the host or do not join the session.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org