Hi,

Could you try something.

If you have a test environment that you can delete, then delete anything in the "webapps" dir of tomcat, and then create a dir "webapps/ROOT"
Then extract the war file into the "webapps/ROOT" dir in tomcat.

To make sure it extracted in the right place, you should see the paths like

~/tomcat/webapps/ROOT/META-INF
~/tomcat/webapps/ROOT/WEB-INF

etc..

Then restart tomcat.

Hi Gurminder,

thank you for your answer. To extend my use case I want to install seldon on AWS (without using the seldon AMI, at least not yet :)). Unfortunately I didn't work either. I have tried different options with no luck yet:

• Option1:
  • Steps:
    • Copy VM tomcat folder to an AWS instance and run tomcat there.
  • Outcome: Tomcat seems to start properly but get stuck at trying to deploy the ROOT context (seldon server --> /~/seldon/apache-tomcat-7.0.61/webapps/ROOT)
• Option2:
  • Steps:
    • Copy VM tomcat folder to an AWS instance
    • Clean webapps/ROOT
    • Copy one fresh tomcat configuration on webapps/ROOT
    • Compile seldon-server from github and deploy within the webapps folder
  • Outcome: Seems everything fine but cannot access (tomcat itself gets stuck here)
  • Log trace: Setting state for [Pipeline[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/seldon-server-1.2]]] to [STARTED]
• Option 3:
  • Steps:
    • Install a fresh instance of Tomcat
    • Copy war file to webapps folder
    • Start tomcat
  • Outcome: TLDs error
  • Log trace: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
• Option 4 (the option you've suggested :)):
  • Steps:
    • Install a fresh instance of Tomcat
    • Clean ROOT folder
    • Uncompress seldon-server war on it
  • Outcome: TLDs error
  • Log trace: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

Other thoughts about it:

1. Initially I thought that it was a Tomcat configuration error as new Tomcat installations give TLD errors.
2. However I tried copying the whole tomcat folder (option 1) in my own AWS instance (I didn't installed seldon VM on it) and although no errors have been raised, seldon server was not up and running either. If I clean the ROOT folder and put a fresh web.xml configuration, other apss as movie-demo, swagger, ... start properly (with no REST API obviously)
3. Confing folder within the tomcat folder in the seldon VM is not different for a fresh tomcat installation (besides some comments ...), so it seems that this is not the error either.

Thanks for your investigations.

Are you sure this message is an error that is stopping the successful deploy of the application rather than just an INFO message? There are no Tag Libraries in seldon or JSP functionality.

Hi Clive,

thank you for answering me. I'm afraid so ... I've also tried to use the same JDK that is installed on the VM with no success.

Once I have removed it from ROOT folder or seldon-server-1.2 folder after uncompress war file, tomcat has run sucessfully (for example, movie-demo context has been loaded as usual).

I'm trying now with the Seldon AWS AMI (m3.2xlarge) and gets stuck at the same level:

ubuntu@ip-***********:~/apps/apache-tomcat-7.0.61$ bin/startup.sh
Using CATALINA_BASE:   /home/ubuntu/apps/apache-tomcat-7.0.61
Using CATALINA_HOME:   /home/ubuntu/apps/apache-tomcat-7.0.61
Using CATALINA_TMPDIR: /home/ubuntu/apps/apache-tomcat-7.0.61/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /home/ubuntu/apps/apache-tomcat-7.0.61/bin/bootstrap.jar:/home/ubuntu/apps/apache-tomcat-7.0.61/bin/tomcat-juli.jar
Tomcat started.

and log from catalina output:

INFO: Deploying web application directory /home/ubuntu/apps/apache-tomcat-7.0.61/webapps/ROOT
Mar 07, 2016 11:29:14 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/home/ubuntu/apps/apache-tomcat-7.0.61/webapps/ROOT/WEB-INF/lib/servlet-api-2.5-20081211.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class
Mar 07, 2016 11:29:14 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/home/ubuntu/apps/apache-tomcat-7.0.61/webapps/ROOT/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class

Trying to get access to tomcat from web browser it is not possible :(

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale