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-09 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

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: 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,  <pina.freder...@gmail.com> 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

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 sun.nio.ch.Net.bind(Net.java:425)
 at

Re: Apache Tomcat 9

2016-05-06 Thread prashant sharma 
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 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)
>

Re: Apache Tomcat 9

2016-05-06 Thread Frederick Piña 

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
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

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