Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This seems strange - if you didn't change your own web app this issue must exit in 5.5, too.</p> <p>As @daniel said, your web app is not allowed to have a jar file containing servlet stuff. If i interpret the log correctly, there is a servlet-api in the web app directory. Delete servlet-api completely there.</p> <p>EDIT</p> <ul> <li>What is the directory layout of your application, where do the jars (especially the tomcat jars) live.</li> <li>What is the log output when tomcat starts without the servlet-api in your web app</li> <li>How do you "embedd" tomcat</li> <li>What's the classpath when you start your app</li> </ul> <p>EDIT</p> <p>You MUST separate the environment lets say in</p> <pre> \yourapp | + lib | + webapp | + lib (this is where your webapp lives, WITHOUT servlet-api) </pre> <p>If this has similiarity to standard JavaEE container structure - it is NOT by pure hazard :-)</p> <p>yourapp\lib hosts your application and tomcat libraries. This forms the classpath for starting.</p> <p>The yourapp\webapp\lib jars are never referenced by the classpath, only by the webapp classloader. You must take the correct path to them into account when you configure your builtin tomcat to point to this webapp, otherwise the web app loader may not find them.</p> <p>EDIT</p> <p>Maybe start with something less ambitioned than a JSP. Do you have a simple test servlet deployed?</p> <p>You must take care to which web application context you have deployed your application. In the log i see you use the root context. Is this really true? If for example you said</p> <pre><code> tomcat.addWebapp("foo", appBase); </code></pre> <p>in your embedding, you must request /foo/servlet, not /servlet in your browser.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload