Try to get stack trace by putting “try-catch” block, arround “run” method calling, in your main method, and print stack trace within “catch” as follows. public static void main(String[] args) { try { SpringApplication.run(MyApplication.class, args); } catch (Exception e) { e.printStackTrace(); } }
Java objects reside in an area called the heap, while metadata such as class objects and method objects reside in the permanent generation or Perm Gen area. The permanent generation is not part of the heap. The heap is created when the JVM starts up and may increase or decrease in size while the application … Read more
(First post ever so if it looks like a drunk spider has formatted it then sorry) After using our friend Google, here and I can’t remember where else I managed to achieve something using logrotate (rather than cron or some other equivalent). I have a the following in /var/log/rsync/: -rw-r–r– 1 root root 1.1M Apr … Read more
catalina.sh run starts tomcat in the foreground, displaying the logs on the console that you started it. Hitting Ctrl-C will terminate tomcat. startup.sh will start tomcat in the background. You’ll have to tail -f logs/catalina.out to see the logs. Both will do the same things, apart from the foreground/background distinction. Actually, startup.sh is quite small. … Read more
The earlier answers on this page are correct that you can copy/move the WAR file into place and restart tomcat, but they omit to mention something: you must remove the previously exploded assets (from the previously deployed WAR file) if any are present. # My tomcat webapps are found at /var/lib/tomcat6/webapps # The application I … Read more
I guess it has more to do with the servlet spec the container/netbeans is using rather than being an issue with the container. Your net beans seems to be using the spec 2.5 to construct the servlet mapping and hence you get <servlet-mapping> <servlet-name>fred</servlet-name> <url-pattern>*.jsp</url-pattern> <url-pattern>/url</url-pattern> </servlet-mapping> Read more about this here. It says Previous … Read more
Providing an update to this question. Tomcat 7 has changed it’s manager API. Please refer to: Manager commands Following new URL pattern : http://{host}:{port}/manager/text/{command}?{parameters} Example curl -T “myapp.war” “http://manager:manager@localhost:8080/manager/text/deploy?path=/myapp&update=true” Security Keep in mind the server must be able to accept your remote IP. This is a sample configuration: <Context privileged=”true” antiResourceLocking=”false” docBase=”${catalina.home}/webapps/manager”> <Valve className=”org.apache.catalina.valves.RemoteAddrValve” allow=”127\.0\.0\.1″ … Read more
I had a similar problem. The catalina.out logged this log Message Apr 17, 2013 5:14:46 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Check the localhost.log in the tomcat log directory (in the same directory as catalina.out), to see the exception which caused this error.
This error message in client layer code is a consequence of code hardening following “SSL V3.0 Poodle Vulnerability – CVE-2014-3566” in recent Java updates. And it is a bug – here are work-arounds in case you cannot update your JRE immediately: A first option is to force TLS protocol when establishing HTTPS connection: If you … Read more
Fixed it, turns out the standard logging configuration defines a file logger and also a console logger. The file logger goes to the daily catalina log, and the console logger writes to catalina.out. Fix was to change in conf/logging.properties: .handlers = 1catalina.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler to .handlers = 1catalina.org.apache.juli.FileHandler That stops anything getting written to catalina.out