Tomcat 9 won't start according to Eclipse

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Tomcat 9 won't start according to Eclipse

Roparzh Hemon
Hello all, in Eclipse Neon.3 Release (4.6.3) I get the following error message :






Any help appreciated.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Mark Eggers
Roparzh,

On 7/27/2017 12:08 AM, Roparzh Hemon wrote:

> Hello all, in Eclipse Neon.3 Release (4.6.3) I get the following error
> message :
>
>
>
> ​
>
>
> Any help appreciated.
> ​
Images are stripped. Please type out the text.

I just tried 9.0.0M22 on Eclipse Oxygen and it worked as expected.

Please also note that there isn't a released version of JBoss Tools for
Eclipse Oxygen. I don't believe that Eclipse Oxygen supports Tomcat 9
out of the box, but I could be wrong.

In order to get JBoss Tools for Eclipse Oxygen, you'll have to use a
nightly build. Those can be obtained from:

http://tools.jboss.org/downloads/jbosstools/oxygen/4.5.0.AM2.html

Or as the instructions on that page state, search for JBoss Oxygen in
the Eclipse marketplace.

If I remember correctly, you're about to teach yourself J2EE development
(or more properly servlet container development). If that's the case, I
would like to recommend a less bleeding edge approach.

1. Eclipse Neon.3 - works, and the plugins are available / stable

Eclipse Oxygen seems to be OK, but you'll have to deal with milestone
plugins.

2. Apache Tomcat 8.5.16 - production-ready Tomcat

Tomcat 9 is great don't get me wrong, but it's flagged as alpha
(probably mostly because servlet spec 4 isn't finished yet).

BTW 8.5.19 is being voted on in the developers' list.

3. Head First Servlets and JSP 2nd Edition - great book

This edition covers servlet specification 2.5. I know, this means that
you don't get annotations, etc. However, I've found it to be a solid
foundation for learning the basics of servlet / jsp programming, along
with a bunch of good habits.

It all comes down to your requirements. I like bleeding edge stuff. I
run Fedora Linux on a laptop. I think that it's a great platform.

However, I would never think of running Fedora Linux as a server. I also
would think long and hard about recommending Fedora Linux to developers
who are a bit uncomfortable with systems and infrastructure.

The same goes for your development environment.

. . . just my two cents
/mde/


signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Roparzh Hemon
On Thu, Jul 27, 2017 at 5:35 PM, Mark Eggers
<[hidden email]> wrote:

> Images are stripped. Please type out the text.

Sorry about that, the full error message said

'Starting Tomcat v9.0 Server at localhost (2)' has encountered a problem
Server Tomcat v9.0 Server at localhost (2) failed to start.

Thanks for all the rest of your feedback. I'll try to switch to
Tomcat 8.15.6 and see if it works.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Mark Eggers
Roparzh,

On 7/28/2017 12:37 AM, Roparzh Hemon wrote:

> On Thu, Jul 27, 2017 at 5:35 PM, Mark Eggers
> <[hidden email]> wrote:
>
>> Images are stripped. Please type out the text.
>
> Sorry about that, the full error message said
>
> 'Starting Tomcat v9.0 Server at localhost (2)' has encountered a
> problem Server Tomcat v9.0 Server at localhost (2) failed to start.
>
> Thanks for all the rest of your feedback. I'll try to switch to
> Tomcat 8.15.6 and see if it works.
That's an annoyingly uninformative error message.

There are two other places to look for error messages that might be more
informative. This all depends on how you've added Tomcat to Eclipse. I
am going to assume that you picked the 'use workspace metadata' option
since it's the default.

1. Console tab

When you start Tomcat, you'll see a bunch of messages in the console tab
at the bottom of the IDE. This appears to be catalina.out.

Try starting Tomcat again, and copy / paste those messages into a mail
message.

2. Any other logs

In the console tab, one of the lines will be something similar to the
following:

-Dcatalina.base=C:\Users\username\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0

This is Eclipse setting $CATALINA_BASE. You' find the entire structure
of Tomcat below the directory listed above. So additional log files will
be found in (for example):

C:\Users\username\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\logs

Since you're on a Macintosh, the path will obviously look different. I
doubt that there are any logs there if Tomcat does not start up, but it
doesn't hurt to look.

My initial guess is that you have Tomcat running as a service left over
from your previous attempts and that it is bound to port 8080 already.
Make sure that your Tomcat service is stopped before you start Tomcat
from within Eclipse.

. . . just my two cents
/mde/



signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Roparzh Hemon
On Fri, Jul 28, 2017 at 5:13 PM, Mark Eggers
<[hidden email]> wrote:

> My initial guess is that you have Tomcat running as a service left over
> from your previous attempts and that it is bound to port 8080 already.

  That seems likely indeed, but 1) Eclipse says it is stopped before
launching it and 2) when I do lsof -i tcp:8080 in my terminal I get an
empty output.

 Below is the long output in the console. The one line I noticed in it
is the following :

The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
[/Users/roparzhhemon/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.]

Console output :

juil. 28, 2017 5:44:55 PM
org.apache.tomcat.util.digester.SetPropertiesRule begin
AVERTISSEMENT: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
Setting property 'source' to 'org.eclipse.jst.jee.server:jupiter' did
not find a matching property.
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Server version:        Apache Tomcat/9.0.0.M22
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Server built:          Jun 21 2017 09:44:18 UTC
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Server number:         9.0.0.0
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: OS Name:               Mac OS X
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: OS Version:            10.11.3
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Architecture:          x86_64
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Java Home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: JVM Version:           1.8.0_131-b11
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: JVM Vendor:            Oracle Corporation
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: CATALINA_BASE:
/Users/roparzhhemon/Documents/Web_Projects/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: CATALINA_HOME:
/Users/roparzhhemon/Documents/Installations/usr/local/apache-tomcat-9.0.0.M22
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Command line argument:
-Dcatalina.base=/Users/roparzhhemon/Documents/Web_Projects/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Command line argument:
-Dcatalina.home=/Users/roparzhhemon/Documents/Installations/usr/local/apache-tomcat-9.0.0.M22
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Command line argument:
-Dwtp.deploy=/Users/roparzhhemon/Documents/Web_Projects/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Command line argument:
-Djava.endorsed.dirs=/Users/roparzhhemon/Documents/Installations/usr/local/apache-tomcat-9.0.0.M22/endorsed
juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
INFOS: Command line argument: -Dfile.encoding=UTF-8
juil. 28, 2017 5:44:55 PM
org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFOS: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
[/Users/roparzhhemon/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.]
juil. 28, 2017 5:44:56 PM org.apache.coyote.AbstractProtocol init
INFOS: Initializing ProtocolHandler ["http-nio-8080"]
juil. 28, 2017 5:44:56 PM org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector
INFOS: Using a shared selector for servlet write/read
juil. 28, 2017 5:44:56 PM org.apache.coyote.AbstractProtocol init
INFOS: Initializing ProtocolHandler ["ajp-nio-8009"]
juil. 28, 2017 5:44:56 PM org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector
INFOS: Using a shared selector for servlet write/read
juil. 28, 2017 5:44:56 PM org.apache.catalina.startup.Catalina load
INFOS: Initialization processed in 3480 ms
juil. 28, 2017 5:44:56 PM org.apache.catalina.core.StandardService startInternal
INFOS: Démarrage du service [Catalina]
juil. 28, 2017 5:44:56 PM org.apache.catalina.core.StandardEngine startInternal
INFOS: Starting Servlet Engine: Apache Tomcat/9.0.0.M22
juil. 28, 2017 5:44:58 PM org.apache.catalina.core.ContainerBase startInternal
GRAVE: A child container failed during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jupiter]]
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:192)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:947)
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:839)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
    at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:258)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:770)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:657)
    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.start(Bootstrap.java:355)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jupiter]]
    at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
    at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)
    ... 21 more
Caused by: java.lang.IllegalArgumentException: L'association de
servlet (servlet mapping) indique un nom de servlet inconnu [Taste]
    at org.apache.catalina.core.StandardContext.addServletMappingDecoded(StandardContext.java:3091)
    at org.apache.catalina.Context.addServletMappingDecoded(Context.java:879)
    at org.apache.catalina.startup.ContextConfig.configureContext(ContextConfig.java:1378)
    at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1190)
    at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
    at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
    at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4993)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    ... 27 more

juil. 28, 2017 5:44:58 PM org.apache.catalina.core.ContainerBase startInternal
GRAVE: A child container failed during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: A child container failed
during start
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:192)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:947)
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:258)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:770)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:657)
    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.start(Bootstrap.java:355)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)
Caused by: org.apache.catalina.LifecycleException: A child container
failed during start
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:956)
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:839)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
    at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)
    ... 13 more

juil. 28, 2017 5:44:58 PM org.apache.catalina.startup.Catalina start
GRAVE: The required Server component failed to start so Tomcat is
unable to start.
org.apache.catalina.LifecycleException: A child container failed during start
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:956)
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:258)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:770)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:657)
    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.start(Bootstrap.java:355)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)

juil. 28, 2017 5:44:58 PM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-nio-8080"]
juil. 28, 2017 5:44:58 PM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["ajp-nio-8009"]
juil. 28, 2017 5:44:58 PM org.apache.catalina.core.StandardService stopInternal
INFOS: Arrêt du service [Catalina]
juil. 28, 2017 5:44:58 PM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-nio-8080"]
juil. 28, 2017 5:44:58 PM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["ajp-nio-8009"]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Konstantin Kolinko
2017-07-28 18:53 GMT+03:00 Roparzh Hemon <[hidden email]>:

> On Fri, Jul 28, 2017 at 5:13 PM, Mark Eggers
> <[hidden email]> wrote:
>
>> My initial guess is that you have Tomcat running as a service left over
>> from your previous attempts and that it is bound to port 8080 already.
>
>   That seems likely indeed, but 1) Eclipse says it is stopped before
> launching it and 2) when I do lsof -i tcp:8080 in my terminal I get an
> empty output.
>
>  Below is the long output in the console. The one line I noticed in it
> is the following :
>
> The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path:
> [/Users/roparzhhemon/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.]
>
> Console output :
>
> juil. 28, 2017 5:44:55 PM
> org.apache.tomcat.util.digester.SetPropertiesRule begin
> AVERTISSEMENT: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
> Setting property 'source' to 'org.eclipse.jst.jee.server:jupiter' did
> not find a matching property.
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Server version:        Apache Tomcat/9.0.0.M22
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Server built:          Jun 21 2017 09:44:18 UTC
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Server number:         9.0.0.0
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: OS Name:               Mac OS X
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: OS Version:            10.11.3
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Architecture:          x86_64
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Java Home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: JVM Version:           1.8.0_131-b11
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: JVM Vendor:            Oracle Corporation
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: CATALINA_BASE:
> /Users/roparzhhemon/Documents/Web_Projects/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: CATALINA_HOME:
> /Users/roparzhhemon/Documents/Installations/usr/local/apache-tomcat-9.0.0.M22
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Command line argument:
> -Dcatalina.base=/Users/roparzhhemon/Documents/Web_Projects/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Command line argument:
> -Dcatalina.home=/Users/roparzhhemon/Documents/Installations/usr/local/apache-tomcat-9.0.0.M22
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Command line argument:
> -Dwtp.deploy=/Users/roparzhhemon/Documents/Web_Projects/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Command line argument:
> -Djava.endorsed.dirs=/Users/roparzhhemon/Documents/Installations/usr/local/apache-tomcat-9.0.0.M22/endorsed
> juil. 28, 2017 5:44:55 PM org.apache.catalina.startup.VersionLoggerListener log
> INFOS: Command line argument: -Dfile.encoding=UTF-8
> juil. 28, 2017 5:44:55 PM
> org.apache.catalina.core.AprLifecycleListener lifecycleEvent
> INFOS: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path:
> [/Users/roparzhhemon/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.]
> juil. 28, 2017 5:44:56 PM org.apache.coyote.AbstractProtocol init
> INFOS: Initializing ProtocolHandler ["http-nio-8080"]
> juil. 28, 2017 5:44:56 PM org.apache.tomcat.util.net.NioSelectorPool
> getSharedSelector
> INFOS: Using a shared selector for servlet write/read
> juil. 28, 2017 5:44:56 PM org.apache.coyote.AbstractProtocol init
> INFOS: Initializing ProtocolHandler ["ajp-nio-8009"]
> juil. 28, 2017 5:44:56 PM org.apache.tomcat.util.net.NioSelectorPool
> getSharedSelector
> INFOS: Using a shared selector for servlet write/read
> juil. 28, 2017 5:44:56 PM org.apache.catalina.startup.Catalina load
> INFOS: Initialization processed in 3480 ms
> juil. 28, 2017 5:44:56 PM org.apache.catalina.core.StandardService startInternal
> INFOS: Démarrage du service [Catalina]
> juil. 28, 2017 5:44:56 PM org.apache.catalina.core.StandardEngine startInternal
> INFOS: Starting Servlet Engine: Apache Tomcat/9.0.0.M22
> juil. 28, 2017 5:44:58 PM org.apache.catalina.core.ContainerBase startInternal
> GRAVE: A child container failed during start
> java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jupiter]]
>     at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>     at java.util.concurrent.FutureTask.get(FutureTask.java:192)
>     at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:947)
>     at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:839)
>     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>     at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)
>     at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>     at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
>     at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
>     at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)
>     at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:258)
>     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>     at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)
>     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>     at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:770)
>     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>     at org.apache.catalina.startup.Catalina.start(Catalina.java:657)
>     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.start(Bootstrap.java:355)
>     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)
> Caused by: org.apache.catalina.LifecycleException: Failed to start
> component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jupiter]]
>     at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441)
>     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
>     at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)
>     at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>     at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
>     at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
>     at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)
>     ... 21 more
> Caused by: java.lang.IllegalArgumentException: L'association de
> servlet (servlet mapping) indique un nom de servlet inconnu [Taste]
>     at org.apache.catalina.core.StandardContext.addServletMappingDecoded(StandardContext.java:3091)
>     at org.apache.catalina.Context.addServletMappingDecoded(Context.java:879)
>     at org.apache.catalina.startup.ContextConfig.configureContext(ContextConfig.java:1378)
>     at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1190)
>     at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:775)
>     at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)
>     at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
>     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4993)
>     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>     ... 27 more

Eclipse by default places <Context> element for web application into
Tomcat's server.xml file.
This is a discouraged practice. A result of such configuration is that
when the application fails to start (due to its own misconfiguration)
this failure is fatal for Tomcat as well.

Double click on the server (in "Servers" view) -> set "[x] Publish
module context to separate XML files".



The FAQ pages have a link to Eclipse FAQ:
https://wiki.apache.org/tomcat/FAQ/Developing#Q6


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

André Warnier (tomcat)
On 28.07.2017 18:18, Konstantin Kolinko wrote:
> Caused by: java.lang.IllegalArgumentException: L'association de
>>servlet (servlet mapping) indique un nom de servlet inconnu [Taste]

This seems to be the underlying problem.
There is a <servlet-mapping> element associating some URL pattern (?) with a
<servlet-name> "Taste", but there is no such servlet.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Roparzh Hemon
On Fri, Jul 28, 2017 at 6:29 PM, André Warnier (tomcat) <[hidden email]> wrote:

> On 28.07.2017 18:18, Konstantin Kolinko wrote:
>>
>> Caused by: java.lang.IllegalArgumentException: L'association de
>>>
>>> servlet (servlet mapping) indique un nom de servlet inconnu [Taste]
>
>
> This seems to be the underlying problem.
> There is a <servlet-mapping> element associating some URL pattern (?) with a
> <servlet-name> "Taste", but there is no such servlet.
>

 You are 100% correct, this was a typo in my web.xml file. I corrected
it and now everything works fine. All in all, this was not a tomcat
issue.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Roparzh Hemon
In reply to this post by Konstantin Kolinko
On Fri, Jul 28, 2017 at 6:18 PM, Konstantin Kolinko
<[hidden email]> wrote:
>
> Eclipse by default places <Context> element for web application into
> Tomcat's server.xml file.
> This is a discouraged practice. A result of such configuration is that
> when the application fails to start (due to its own misconfiguration)
> this failure is fatal for Tomcat as well.

  Which makes people mistake non-Tomcat issues for Tomcat issues, as
happened to me here.

On Fri, Jul 28, 2017 at 6:18 PM, Konstantin Kolinko
<[hidden email]> wrote:
>
> Double click on the server (in "Servers" view) -> set "[x] Publish
> module context to separate XML files".
>

     When I right-click on "Servers" in Project Explorer, I do not see
any "Publish module"
item. I also found a "Server" item in Preferences, which has a
"Audio/Launching/Overlays/Profilers/Runtime environments" submenu.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Konstantin Kolinko
2017-07-28 20:51 GMT+03:00 Roparzh Hemon <[hidden email]>:

> On Fri, Jul 28, 2017 at 6:18 PM, Konstantin Kolinko
> <[hidden email]> wrote:
>>
>> Eclipse by default places <Context> element for web application into
>> Tomcat's server.xml file.
>> This is a discouraged practice. A result of such configuration is that
>> when the application fails to start (due to its own misconfiguration)
>> this failure is fatal for Tomcat as well.
>
>   Which makes people mistake non-Tomcat issues for Tomcat issues, as
> happened to me here.
>
> On Fri, Jul 28, 2017 at 6:18 PM, Konstantin Kolinko
> <[hidden email]> wrote:
>>
>> Double click on the server (in "Servers" view) -> set "[x] Publish
>> module context to separate XML files".
>>
>
>      When I right-click on "Servers" in Project Explorer, I do not see
> any "Publish module"
> item. I also found a "Server" item in Preferences, which has a
> "Audio/Launching/Overlays/Profilers/Runtime environments" submenu.


http://help.eclipse.org/neon/topic/org.eclipse.platform.doc.user/concepts/concepts-5.htm
Help > Workbench User Guide > Concepts > Views

To open the "Servers" view go to menu "Window" > "Show View" > "Other..."

A dialog named "Show View" opens.
Type "ser" in the filter box at the top of the dialog.
Choose "Server" > "Servers", click OK.


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Roparzh Hemon
On Wed, Aug 2, 2017 at 2:30 PM, Konstantin Kolinko
<[hidden email]> wrote:

> 2017-07-28 20:51 GMT+03:00 Roparzh Hemon <[hidden email]>:
>> On Fri, Jul 28, 2017 at 6:18 PM, Konstantin Kolinko
>> <[hidden email]> wrote:
>>>
>>> Double click on the server (in "Servers" view) -> set "[x] Publish
>>> module context to separate XML files".
>>      When I right-click on "Servers" in Project Explorer, I do not see
>> any "Publish module"
>> item. I also found a "Server" item in Preferences, which has a
>> "Audio/Launching/Overlays/Profilers/Runtime environments" submenu.
>
>
> http://help.eclipse.org/neon/topic/org.eclipse.platform.doc.user/concepts/concepts-5.htm
> Help > Workbench User Guide > Concepts > Views
>
> To open the "Servers" view go to menu "Window" > "Show View" > "Other..."
>
> A dialog named "Show View" opens.
> Type "ser" in the filter box at the top of the dialog.
> Choose "Server" > "Servers", click OK.

  This simply sends me back to the Server component in Project
Explorer (which I could attain by simply clicking on it instead of
doing the more complicated sequence of operations you describe). I
repeat, I do not see any "Publish module" item anywhere. All I see is,
for each server, a list consisting of the following files :
catalina.policy, catalina.properties, context.xml, server.out.xml,
server.xml, tomcat-users.xml, web.xml.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Mark Eggers
Roparzh,

On 8/2/2017 10:07 PM, Roparzh Hemon wrote:

> On Wed, Aug 2, 2017 at 2:30 PM, Konstantin Kolinko
> <[hidden email]> wrote:
>> 2017-07-28 20:51 GMT+03:00 Roparzh Hemon <[hidden email]>:
>>> On Fri, Jul 28, 2017 at 6:18 PM, Konstantin Kolinko
>>> <[hidden email]> wrote:
>>>>
>>>> Double click on the server (in "Servers" view) -> set "[x] Publish
>>>> module context to separate XML files".
>>>      When I right-click on "Servers" in Project Explorer, I do not see
>>> any "Publish module"
>>> item. I also found a "Server" item in Preferences, which has a
>>> "Audio/Launching/Overlays/Profilers/Runtime environments" submenu.
>>
>>
>> http://help.eclipse.org/neon/topic/org.eclipse.platform.doc.user/concepts/concepts-5.htm
>> Help > Workbench User Guide > Concepts > Views
>>
>> To open the "Servers" view go to menu "Window" > "Show View" > "Other..."
>>
>> A dialog named "Show View" opens.
>> Type "ser" in the filter box at the top of the dialog.
>> Choose "Server" > "Servers", click OK.
>
>   This simply sends me back to the Server component in Project
> Explorer (which I could attain by simply clicking on it instead of
> doing the more complicated sequence of operations you describe). I
> repeat, I do not see any "Publish module" item anywhere. All I see is,
> for each server, a list consisting of the following files :
> catalina.policy, catalina.properties, context.xml, server.out.xml,
> server.xml, tomcat-users.xml, web.xml.
When you do Window -> Show Views -> Servers and select servers, you'll
get a new pane at the bottom middle of the IDE, labeled servers.

In that pane, you'll see a list of all the servers that you have
configured in your IDE and their states.

If you double-click on one of the servers in the bottom pane, it will
open up the overview in the main editor window. This is a GUI
representation of the main configuration options for that server.

The Server Options will be found in the left hand column at the bottom.
The second checkbox is 'Publish module context to separate XML files'.
Check that box.

Then save the configuration (Ctrl-S or File -> Save) and close the
configuration.

The key here is to double-click (not right-click) the server listed in
the server pane at the bottom center of the IDE.

. . . just my two cents
/mde/


signature.asc (484 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tomcat 9 won't start according to Eclipse

Roparzh Hemon
> The key here is to double-click (not right-click) the server listed in
> the server pane at the bottom center of the IDE.
>

   Absolutely. I finally got it now, thanks for your patience

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...