Re: asgard tomcat application 404
Ok guys. Got it! Thanks for your input. I'll follow up with the Asgard list, assuming I can find it. Thanks On Fri, Feb 16, 2018 at 2:40 PM, Olaf Kock <tom...@olafkock.de> wrote: > > On 15.02.2018 23:39, Tim Dunphy wrote: > >> I'm trying to get Netflix Asgard tomcat app working. I'm using tomcat 9. >> I'm using windows. >> [...] >> > Tomcat is about as much involved in this as is Windows. To second > Christopher's OT answer: This is a problem of the deployed application, not > of Tomcat. You should look for help in the Asgard community. Tomcat doesn't > use spring, thus there's not even common ground. > > Olaf > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
asgard tomcat application 404
I'm trying to get Netflix Asgard tomcat app working. I'm using tomcat 9. I'm using windows. I can load up the tomcat management and other interfaces no problem. But when I navigate to /asgard I get a 404 error: HTTP Status 404 – Not Found Type Status Report Message /asgard/ Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. Apache Tomcat/9.0.5 I have JAVA_HOME set to C:\Program Files\Java\jdk1.8.0_162 I placed the asgard.war file in the tomcat\webapps directory. This is what I have in my catalina logs: 15-Feb-2018 15:59:30.048 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars 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. 15-Feb-2018 15:59:33.402 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file 15-Feb-2018 15:59:33.404 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/asgard] startup failed due to previous errors I have this in the asgard.log file: [2018-02-15 15:59:33,389] [main] springframework.web.context.ContextLoaderContext initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pluginManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException: Cannot invoke method getAt() on null object at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) Caused by: java.lang.NullPointerException: Cannot invoke method getAt() on null object ... 5 more [2018-02-15 15:59:33,397] [main] grails.web.context.GrailsContextLoaderError initializing the application: Error creating bean with name 'pluginManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException: Cannot invoke method getAt() on null object org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pluginManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException: Cannot invoke method getAt() on null object at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) Caused by: java.lang.NullPointerException: Cannot invoke method getAt() on null object ... 5 more [2018-02-15 15:59:33,401] [main] grails.web.context.GrailsContextLoaderError initializing Grails: Error creating bean with name 'pluginManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException: Cannot invoke method getAt() on null object org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pluginManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException: Cannot invoke method getAt() on null object at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) Caused by: java.lang.NullPointerException: Cannot invoke method getAt() on null object And this is what I have in the localhost log: 15-Feb-2018 15:59:30.077 INFO [main] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath 15-Feb-2018 15:59:31.319 INFO [main] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext 15-Feb-2018 15:59:33.402 SEVERE [main]
tomcat management interface gives 403 forbidden error
I've had to configure two tomcat servers recently. I've setup one tomcat server using using version 8.5.13 and that works fine. I can access Server Status, Manager App and Host Manager web interfaces with no problem. But when I tried setting up a new tomcat server running tomcat version 8.5.14 by copying the same configs from the from the 8.5.13 server I'd built I get access denied 403 on the Server Status and Manager app. But oddly only the Host Manager web interface works correctly. I can access that. I need to figure out why the same configs that work on the first server, give me 403 denied on the second server. This is what I have on each: Working server Java: java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) Non working server have a newer java: java version "1.8.0_131" Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) Everything else is identical in terms of configuration. Both have java and tomcat variables setup in /etc/profile: JAVA_HOME='/usr/lib/jvm' CATALINA_HOME='/usr/local/tomcat' export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE HISTCONTROL JAVA_HOME CATALINA_HOME Both servers have the same config files, copied from the 1st working server to the 2nd non working server. Tomcat users config: cat /usr/local/tomcat/conf/tomcat-users.xml The context configuration file has this: cat /usr/local/tomcat/conf/context.xml And the webapps context.xml config for both tomcats has this: cat /usr/local/tomcat/webapps/host-manager/META-INF/context.xml Why is tomcat server 1 (version 8.5.13) working and the newer tomcat version (8.5.14) on server 2 not working? Thanks in advance! -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
