tomcat8

问题 Now that I upgraded my webapp to Java 8, I'm running into strange classloading problem with an axis webservice that is running in Tomcat 8. The very first call to the webservice after installing the webapp will cause a RuntimeException and a "No compiler found in your classpath! (you may need to add 'tools.jar')" fault. All following calls to that webservice work correctly (apparently tools.jar is there after all?). The behaviour is reproducable by deleting the exploded webapp folder in the

问题 I'm trying to run elementary spring-4 web-mvc application without xml configuration at all. I've looked spring documentation and examples, but it didn't work for me. My controller: package com.nikolay.exam.controller; import org.springframework.stereotype.Controller; import org.springframework.web.bind.annotation.RequestMapping; import org.springframework.web.bind.annotation.RequestMethod; import org.springframework.web.bind.annotation.ResponseBody; @Controller public class HomeController {

问题 I recently upgraded my jersey jars from version 1 to 2 . With jersey-1 my web.xml mappings were as follows <servlet> <servlet-name>Restful App</servlet-name> <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Restful App</servlet-name> <url-pattern>/rest/*</url-pattern> </servlet-mapping> I have other applications talking to this application through rest calls. After upgrading to

问题 I recently upgraded my jersey jars from version 1 to 2 . With jersey-1 my web.xml mappings were as follows <servlet> <servlet-name>Restful App</servlet-name> <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Restful App</servlet-name> <url-pattern>/rest/*</url-pattern> </servlet-mapping> I have other applications talking to this application through rest calls. After upgrading to

问题 I am currently working on cloud migration activities. We have installed a new “Apache Tomcat/8.0.43” in cloud server and transferred the war files from local to cloud. while starting the tomcat server I’m getting below error : WARNING [localhost-startStop-1] org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan [file:/usr/share/java/tomcat8/gdk_custom.jar] from classloader hierarchy java.io.FileNotFoundException: /usr/share/java/tomcat8/gdk_custom.jar (No such file or directory)

问题 I've just upgraded from Java 7 to Java 8, Tomcat 8 has a single app running inside, which seems to have no problems, but inside /var/log/tomcat8/catalina.out I found the following error messages: INFORMACIÓN: Server startup in 7681 ms abr 01, 2017 9:40:51 AM org.apache.jasper.compiler.JDTCompiler$1 findType GRAVE: Compilation error org.eclipse.jdt.internal.compiler.classfmt.ClassFormatException at org.eclipse.jdt.internal.compiler.classfmt.ClassFileReader.<init>(ClassFileReader.java:372) at

问题 i have install tomcat 8(ssl support) with java 1.8. When start tomcat catalina out write javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) at sun.security.ssl.Handshaker.activate(Handshaker.java:503) at sun.security.ssl.SSLEngineImpl.kickstartHandshake(SSLEngineImpl.java:729) at sun.security.ssl.SSLEngineImpl.beginHandshake(SSLEngineImpl.java:756) at org.apache.tomcat.util.net.SecureNioChannel.reset(SecureNioChannel.java:94)

问题 I have the following warning in Tomcat 8.5 I'm not sure I can ignore WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [AppName] appears to have started a thread named [pool-20-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.socketRead(SocketInputStream.java:116) java.net

问题 I have docker image which I create from my docker file. When I run the image it has able to run the tomcat server then the command prompt come back. That mean the process is terminated and I think the container stops. So when I see http://localhost:8080 no tomcat page is appear. So I am not able find actual what is the problem. I am actually trying to to build custom java8, tomcat8 and maven as environment and I want to deploy my maven project in that tomcat server. Bellow is the Dockerfile

问题 I am using Grails 3.3.0 (which by default is using Tomcat 8.5.15). Whenever any controller (or say any other class ) tries to refer or instantiate a class ( e.g. non Spring Bean class), there is large delay for the first time access only. From thread dump it seems that jar is getting inflated while loading the class definition. Hence there is a large delay. I am aware of a issue related to unpackWARs as false in tomcat 8.0.xxx. But I am not sure whether this applies to GRAILS 3.3.0 also? We